Nortel BayStack 460 Switch Device Management Manual Download Page 3

Policy management on the Nortel Ethernet Switch 460, Ethernet Switch 470, and BPS

3

If you are working with a maintenance release in the EPM 4-series (i.e. post-4.1), 
it may have been tested against a newer version of the device software. To verify 
the absolute latest supported device software versions, refer to the 

Release Notes 

for Enterprise Policy Manager

 manual.

Configuring the device for policy management

In order for an Ethernet Switch 460, Ethernet Switch 470, or Business Policy 
Switch unit to receive policy configuration from EPM, the devices themselves 
must be configured to communicate with the EPM Policy Server. Detailed 
instructions for accomplishing this task are included below. Once this is 
completed, the devices will report to the EPM Policy Server and they will appear 
as icons in the management console. The roles they report are also displayed. 
Policy management can be initiated by associating a policy with the device’s 
reported role(s).

You must open the Web interface for the device and specify the address and port 
number of the EPM Policy Server. You can specify more than one Policy Server. 
You must also enable QoS configuration on the device and define its role 
combinations.

You must know the IP address and COPS-PR Client Port values for your Policy 
Server. You can obtain these values by right-clicking the Policy Server object in 
the EPM management console and choosing Properties from the menu.

To configure an Ethernet Switch or BPS unit to accept policy configuration, 
follow these steps:

1

Launch the Web interface for the device you want to configure. Open a Web 
browser and go to the IP address of the device.

2

In the Access list, navigate to the following location:

Application > COPS > Configuration

3

In the COPS Client Creation area, do the following:

a

Type the IP address of your EPM Policy Server in the IP Address field.

b

Type the Policy Server COPS-PR Client Port number (specified in EPM) 
in the TCP Port field. The default value for this field is 3288.

Summary of Contents for BayStack 460 Switch

Page 1: ...ating to the configuration of the Nortel Ethernet Switch 460 formerly BayStack 460 Ethernet Switch 470 formerly BayStack 470 and Business Policy Switch BPS to receive policy configuration from Nortel Enterprise Policy Manager EPM It also includes information on the devices compatibility with various policy management objects This guide covers the following subjects ...

Page 2: ...course of 2004 The transition simplifies product naming in order to make it easier for customers to understand the Nortel product and services portfolio Table 1 lists the names of rebranded Nortel products mentioned in this publication Full details of the Nortel product rebranding process can be obtained from http www nortel com products announcements rebranding index html faqs Supported software ...

Page 3: ...iated by associating a policy with the device s reported role s You must open the Web interface for the device and specify the address and port number of the EPM Policy Server You can specify more than one Policy Server You must also enable QoS configuration on the device and define its role combinations You must know the IP address and COPS PR Client Port values for your Policy Server You can obt...

Page 4: ...ce Group Creation area do the following a Type a name for a role combination in the Role Combination field Do not use spaces in role combination names The role combination is a common identifier that is used to enforce a specific set of policies on specific network entities for example the print server the Web server employee workstations etc EPM includes a set of preconfigured roles with policy o...

Page 5: ... Policy Setup view drag a policy from the Available Policy Components tree to the role that is being reported by the device Enable the policy from the Options menu For example you can choose the Mark WWW Traffic Best Effort During Lunch policy to match all Web traffic between 11 30 am and 1 30 pm You can remove the schedule from the policy to make it active all of the time 2 Click the Deploy Chang...

Page 6: ...device Maximum 14 802 traffic conditions per device Devices with limited memory may not be able to achieve the limitations stated above The BPS 2 x series has a special limit of 24 traffic conditions that specify the same source IP address To avoid device limitations Avoid assigning multiple traffic conditions with overlapping traffic criteria to a single policy This will result in excessive numbe...

Page 7: ...ayRS devices Note The information displayed here reflects the most up to date information available at the time of the EPM 4 1 release Policy filter support capabilities may change for individual device types as their software is upgraded Check your device documentation for current policy support capabilities Filtering capability Ether Type VLAN ID Inbound User Priority Protocol Inbound DSCP Port ...

Page 8: ... and networking devices Remote access to the directory requires HTTP port 80 default The Policy Server uses LDAP port 389 default to communicate with the directory server It uses COPS PR port 3288 default and SNMP ports 161 and 162 to communicate with networking devices and the Interface Manager The Interface Manager uses LDAP port 389 default to communicate with the directory server It uses COPS ...

Page 9: ...y management right click its object in the EPM management console and then choose Disable For Policy Management from the menu To enable a device for policy management right click its object in the EPM management console and then choose Enable For Policy Management from the menu Fixed device reset issue Q01038174 BoSS version 3 1 3 had a problem that caused the device to reset repeatedly when runni...

Page 10: ...port is suspect Therefore the DSCP field of any traffic that enters the BPS from an untrusted port is always re marked Any policies instructing the BPS to not set the value of the DSCP field on an untrusted port will generate errors Only policies with Meter Mark and Drop actions are permitted on untrusted ports Unrestricted ports do not assume anything about the origin of the incoming traffic You ...

Page 11: ...re version Untrusted Trusted Unrestricted BPS 2 0 3 0 3 1 Layer 3 Mark Mark Update DSCP with value 0 63 Ignore Ignore Ignore DSCP All All All actions allowed Layer 2 Tagged Ignore Ignore Ignore UnTagged Ignore Ignore Ignore Table 3 User Priority Update action behavior underlined text denotes EPM default setting where multiple options exist Device software version Untrusted Trusted Unrestricted BPS...

Page 12: ...e options exist DSCP Ignore DSCP Mark Drop Update User Priority Update 0 7 Egress Map Ignore Update 0 7 Update user priority with value 0 7 Egress Map Use COS value from DSCP to COS mapping based on DSCP from incoming packet Ignore Ignore user priority Defaults Defaults Use COS value from DSCP to COS mapping based on DSCP value in action Ignore Table 5 Drop Precedence Update action behavior underl...

Page 13: ...Egress Map Use COS value from DSCP to COS mapping based on DSCP from incoming packet Ignore Ignore drop precedence Table 6 Allowable Drop Precedence actions underlined text denotes EPM default setting where multiple options exist DSCP Ignore DSCP Mark Drop Update Drop Precedence Update 1 8 Egress Map Ignore Update 1 8 Update drop precedence with value of 1 8 Egress Map Use COS value from DSCP to C...

Page 14: ... before the 802 1p User Priority value can be known Ignore or Drop actions cannot include shaping functionality Only Mark actions can include shaping functionality Table 7 Shaper limitations on BPS ports Device software version Untrusted Trusted Unrestricted BPS 2 0 3 0 3 1 Layer 3 Supported with Mark action only Mark Update DSCP with value 0 63 Not supported Supported with Mark action only Layer ...

Reviews: