Avaya Cajun P550R How to use

610-0184-095 1
June 14, 2001
Cajun™P550R®/P580/P880/P882
Switch Release Notes v5.2.2
Overview
These release notes support the Cajun switch software version
5.2.2 (v5.2.2) for the Cajun P550R, P580, P880, and P882 switches.
Release notes are periodically updated with pertinent information.
For detailed information about your product, refer to the basic set
of user documentation.
You can download software and access the latest release notes and
other documentation at:
http://www.avayanetwork.com/
These release notes cover the following topics:
■New Hardware and Software Features on page 2
■Supported Product Binaries and Boot Codes on page 4
■Queue Classification and Servicing Features on page 4
■Enabling Option 82 for DHCP on page 12
■Enabling Traps for Unknown Source Addresses on page 14
■Enhancements on page 17
■Changed CLI Commands on page 17
■Corrected Problems on page 17
■Known Problems and Workarounds on page 18
■Functional Restrictions on page 28
■Documentation Updates and Corrections on page 33
■Technical Support on page 34

610-0184-095
2 June 14, 2001
New Hardware and Software Features
Version 5.2.2 provides support for the following new hardware
software features.
Hardware
■80-series, 48-port, 10/100 Ethernet Module with Telco
connectors (M8048R-100TC)
■48-volt power supply for the P580
Software Features
Support for:
■The following Queue Classification and Queue Servicing
features:
—Classification of switch port traffic.
—Classification of layer 2 tagging.
—Classification of layer 3 traffic (by means of an access
control list).
—Queue servicing by means of weighted fair queueing
(WFQ).
For more information about the Queue Classification and
Queue Servicing features that are implemented in this
release, see "Queue Classification and Servicing Features" on
page 4.
■Port mirroring on 80-series modules in fabric mode 2. This
feature makes it possible for you to:
—Monitor traffic that is received and transmitted from a
port.
—Use of up to four monitor (sink) channels for monitoring
traffic.
For more information about the port mirroring on 80-series
module feature that is implemented in v5.2.2, see "Queue
Classification and Servicing Features" on page 4.

3
610-0184-095 June 14, 2001
■Relay Agent Information option (option 82) for Dynamic
Host Configuration Protocol (DHCP). When forwarding
client-originated DHCP packets to a DHCP server, the Cajun
switch inserts this option, which contains information about
the switch. The DHCP server uses this information to
authenticate the client.
For information on how to enable option 82, see "Enabling
Option 82 for DHCP" on page 12 of this document.
■Enhancement of the MAC Address Lock feature. This feature
has been available in all previous releases. If a source MAC
address is locked at a port (statically configured), a frame
with that source MAC will be filtered if received on any other
port on the same VLAN. With the enhancement, the feature
immediately generates traps to identify all unknown source
addresses. If, after sending a trap for an unknown source, the
switch continues to receive traffic from the source, the
feature generates a trap every 30 minutes until the traffic
stops.
* Note: You can set the trap timer within a range of 60 to
1800 seconds (default) in one second intervals.
For information on how to enable the MAC Address Lock
feature and traps for unknown source addresses, see
"Enabling Traps for Unknown Source Addresses" on page 14
of this document.
■Load MIB for the ATM Uplink module, v1.1. This feature
makes it possible for you to use SNMP commands to:
—Upload the startup configuration file of the ATM Uplink
module to a TFTP server
—Download the startup configuration file from a TFTP
server to the ATM Uplink module.
—Download a software image to the ATM Uplink module.

610-0184-095
4 June 14, 2001
Supported Product Binaries and Boot Codes
Table 1 shows the product binary files and boot codes that are
supported by v5.2.2 of the Cajun switch software.
* Note: Before downloading and running v5.2.2, remove port
mirrors with piggyback ports on 80-series modules.
Table 1. v5.2.2 Product Binary and Boot Files
* Note: The m8000r binary files run the supervisor module
on both the P580 and P882 switches. These files
replace the m8820_vx.x.x files.
Queue Classification and Servicing Features
Overview
Version v5.2.2 contains Queue Classification and Servicing
functionality that you can activate from the switch’s CLI. You can
configure Queue Classification and Servicing functionality for a
module, or for individual ports on a module. The main components
of the Queue Classification and Servicing functionality are:
■A hierarchical classification mechanism that classifies
incoming traffic
■Priority queues through which the switch forwards classified
traffic.
The switch first classifies the traffic and then, based upon the
classification of the traffic, stores it in the appropriate priority queue.
The switch services the queues according to the WFQ algorithm and
assigns queue weights.
Type of Switch Binary File Boot File
P550R m5500r_v5.02.02.bin m550boot_v5.00.01.bin
P580 m8000r_v5.02.02.bin m8000boot_v5.00.01.bin
P880 m8800_v5.02.02.bin m880boot_v5.00.01.bin
P882 m8000r_v5.02.02.bin m8000boot_v5.00.01.bin

5
610-0184-095 June 14, 2001
Classification of Traffic
You can classify traffic by:
■802.1p tag priority (default)
■Physical source port
■IP characteristics of the frame (source address, destination
address, and so forth)
Frames are classified into eight priorities, or classes, ranging in
number from 0 to 7. By default, the switch uses the priority from
the 802.1p tag field, if present, to assign a priority to a frame.
You can alternately set each physical port with a priority that ranges
from 0 to 7. The switch then replaces the default 802.1p tag priority
with the port priority as the priority of the frame.
You can, as a third alternative, set classification to be performed by
the IP characteristics of packets, instead of 802.1 tag priority or port
priority. To classify frames by their IP characteristics, you set a rule
in an access control list (ACL). The rule can set a priority for traffic
with a specific IP source address or with a specific combination of IP
source address, IP destination address, IP protocol, TCP source port,
and TCP destination port.
The priority of a rule in an ACL takes precedence over all other
priorities in Queue Classification and Servicing classification.
Because of this precedence, the switch determines whether a rule in
an ACL exists for an IP frame in the final stage of classification. If a
rule does exist, the priority associated with the rule replaces the
current priority of the frame.
The switch then forwards the frames to the appropriate priority
queue based upon the priority that is assigned to the frames.

610-0184-095
6 June 14, 2001
WFQ Queue-Servicing Algorithm
You can configure the WFQ service policy. The WFQ policy
implemented in the Cajun II Queue Classification and Servicing
sub-system is a variation of the textbook WFQ algorithm. In Cajun II
WFQ, each queue is assigned a weight increment. The weight
increment never varies; however, each queue also maintains an
accumulated weight, which is updated after each queue service
cycle. Queues are serviced based upon their relative accumulated
weights. In each queue service cycle, only the queue with the
highest accumulated weight is serviced. If there is a tie, the queue
with the highest priority (0 – 7 highest) is serviced first. After each
queue service cycle, the accumulated weight for the queue that is
serviced is reset to the value of its weight increment, and the
accumulated weight for the other queues is increased by their
respective weight increments.
When you set a port for WFQ, the switch services priority queues
according to their assigned weight. The queue with the highest
weight is serviced first.
There are two levels to the WFQ command. The first level specifies
the modules/ports to be configured. The second level specifies the
queue weights.
Port Mirroring on 80-Series Modules
The port mirroring on 80-series modules that is implemented in
v5.2.2 provides the ability for the 80-series modules to monitor
traffic that a port transmits and receives. Four channels are provided
for monitoring traffic, so you can monitor four different ports or
port ranges simultaneously.
* Note: Your switch must be in fabric mode 2 to perform 80-series
port mirroring.
You can configure port mirroring on 80-series modules by using
either the command-line interface (CLI) or the Web Agent.

7
610-0184-095 June 14, 2001
Configuring Port Mirroring By Using the CLI
Use the following CLI commands to configure port mirroring on 80-
series modules. You must be in Global Configuration command
mode to enter these commands.
* Note: For information on how to enter Global Configuration
command mode, see “Accessing/Exiting the Command
Modes” in chapter 1 of Cajun P550R/P880/P882 Command
Reference Guide.
Setting Up Port
Mirroring
To set up port mirroring, use the following CLI command:
>(config)# set port mirror fabric_mode2
source-port <mod-port-range> mirror-port
<mod-port-spec> channel <channel> direction
{tx | rx | both} sampling {always | disable |
periodic} [max-packets=sec <max-packets-sec-
value>]
where:
■<mod-port-range> is either the single port or the range of
ports that you want to mirror.
See Table 2 on page 8 for the specific port ranges that you can
mirror.

610-0184-095
8 June 14, 2001
Table 2. Port Ranges for 80-Series Port Mirroring
Module Port ranges that you can mirror
4-port gigabit modules • 1–2
• 3–4
• Any single port
You can mirror any four single
ports simultaneously (one port per
channel). However you cannot
mirror a port range and a single
port within that range
simultaneously.
Example: You can mirror port 1
on channel 1, port 2 on channel 2,
and port 3 on channel 3
simultaneously. However, you
cannot mirror ports 1 through 2 on
channel 1 and port 2 on channel 2
simultaneously.
8-port gigabit modules • 1–4
• 5–8
• Any single port
You can mirror any four single
ports simultaneously (one port per
channel). However you cannot
mirror a port range and a single
port within that range
simultaneously.
Example: You can mirror port 1
on channel 1, port 2 on channel 2,
and port 3 on channel 3
simultaneously. However, you
cannot mirror ports 1 through 4 on
channel 1 and port 2 on channel 2
simultaneously.

9
610-0184-095 June 14, 2001
* Note: You cannot mirror transmit traffic of multiple
source ports to one mirror port.
■<mod-port-spec> is the port to which you want to mirror
traffic.
Both the source port and mirror port must either:
—Be on the same vlan and have the same vlan binding
or
—Have vlan binding set to bind to all
24-port 10/100 modules • 1–12 — any 1 port or the
entire range.
• 13–24 — any 1 port or the
entire range.
If you mirror a single port, you can
mirror only 1 port per range at a
time.
Example: You can mirror port 1
on channel 1 and port 13 on
channel 2 simultaneously.
However, you cannot mirror port 1
on channel 1 and port 2 on
channel 2 simultaneously.
48-port 10/100 modules • 1–12 — any 1 port or the
entire range.
• 13–24 — any 1 port or the
entire range.
• 25–36 — any 1 port or the
entire range.
• 36–48 — any 1 port or the
entire range.
If you mirror a single port, you can
mirror only 1 port per range at a
time.
Example: You can mirror port 1
on channel 1 and port 13 on
channel 2 simultaneously.
However, you cannot mirror port 1
on channel 1 and port 2 on
channel 2 simultaneously.
Table 2. Port Ranges for 80-Series Port Mirroring
Module Port ranges that you can mirror

610-0184-095
10 June 14, 2001
* Note: Avaya recommends that you mirror traffic to a port
of the same speed or faster than the source port.
■<channel> is the mirror channel that you want to use (1-4).
■{TX| RX |Both} is the direction of traffic that you want to
mirror.
* Note: You can mirror transmit traffic of only one source
port to the mirror port. You cannot mirror transmit
traffic of multiple source ports to one mirror port.
■{always | disable | periodic} is how often you
want the mirror port to receive traffic samples.
■<max-packets-sec-value> is the maximum number of
packets per second that you want the mirror port to receive.
(Enter a value for this variable only if you set the sampling to
periodic.)
Removing Port
Mirroring
To remove port mirroring, use the following CLI command:
>(config)# clear port mirror fabric_mode2
channel <channel>
where <channel> is the mirror channel that you want to remove.
Viewing
Information
about Port
Mirroring
To view information about port mirroring, use the following CLI
command:
>(config)# show port mirror fabric_mode2
This command displays the source ports, mirror port, direction being
mirrored, sampler type, and maximum packet per second for all port
mirrors that are currently set up.

11
610-0184-095 June 14, 2001
Configuring Port Mirroring By Using the Web Agent
Setting Up Port
Mirroring
To use the Web Agent to set up port mirroring:
1. Expand the Modules & Ports folder.
2. Click Port Mirroring.
The Port Mirroring Information page opens.
3. In the Source Port column, select the port that you want to
mirror.
4. In the Mirror Port column, select the port to which you want to
mirror traffic.
Both the source port and mirror port must either:
—Be on the same vlan and have the same vlan binding
or
—Have vlan binding set to bind to all
5. In the Direction column, select the direction of traffic that you
want to mirror.
6. In the Sampler Type column, select how often you want the
mirror port to receive traffic samples.
7. Do one of the following:
8. Click Apply.
IF you select . . . THEN . . .
Periodic in the Sampler
Type column
In the Max Packets per
Second column, enter the
maximum number of packets
per second that you want the
mirror port to receive.
Disable or Always in the
Sampler Type column
Go to step 8.

610-0184-095
12 June 14, 2001
Removing Port
Mirroring
To use the Web Agent to remove port mirroring:
1. Expand the Modules & Ports folder.
2. Click Port Mirroring.
The Port Mirroring Information page opens.
3. In the Source Port column, select None for the port mirror that
you want to remove.
4. Click Apply.
Viewing
Information
about Port
Mirroring
To use the Web Agent to view information about port mirroring:
1. Expand the Modules & Ports folder.
2. Click Port Mirroring.
The Port Mirroring Information page opens. This page displays
information about all port mirrors that are setup.
Enabling Option 82 for DHCP
Option 82 for DHCP includes two suboptions:
■Suboption 1 identifies the slot and physical port number from
which the DHCP request was received.
■Suboption 2 identifies the IP address and, if available, the
system name of the switch.
By default, both of these suboptions are enabled. You can change
the status of either or both suboptions by using the Web Agent,
Command Line Interface (CLI), or SNMP.
Changing the Status of Option 82 by Using the Web Agent
To use the Web Agent to change the status of option 82:
1. Open the IP Global Configuration page.
For information on how to open this page, see “Enabling IP
Routing” in chapter 9 of Cajun P550R/P880/P882 Switch User
Guide Version, v5.0.

13
610-0184-095 June 14, 2001
2. Enable or disable the suboptions as appropriate in the DHCP
Option - Circuit Info and DHCP Option 82 - Agent Info fields.
Changing the Status of Option 82 by Using the CLI
To use the CLI to change the status of option 82, enter Global
Configuration mode and use the following commands:
■To enable suboption 1, use the following command:
>(config)# ip dhcp circuit-info
■To enable suboption 2, use the following command:
>(config)# ip dhcp agent-info
■To disable suboption 1, use the following command:
>(config)# no ip dhcp circuit-info
■To disable suboption 2, use the following command:
>(config)# no ip dhcp agent-info
* Note: For information on how to enter Global Configuration
command mode, see “Accessing/Exiting the Command
Modes” in chapter 1 of Cajun P550R/P880/P882 Command
Reference Guide.
Changing the Status of Option 82 by Using SNMP
To change the status of option 82 by using SNMP, use the MIB items
that are listed in Table 3. These MIB items are defined in
cjnipv4serv.mib.
Table 3. MIB, MIB Items and OIDs for Option 82
MIB MIB Item OID
cjnipv4serv.mib cjnDHCPOpt82Sub1Enabled 1.3.6.1.4.1.1751.2.43.2.5.5.1
cjnDHCPOpt82Sub2Enabled 1.3.6.1.4.1.1751.2.43.2.5.5.2

610-0184-095
14 June 14, 2001
Enabling Traps for Unknown Source Addresses
To enable traps for unknown source addresses, you must first enable
the MAC Address Lock feature. You can enable this feature and
traps for unknown source addresses by using the Web Agent, CLI, or
SNMP.
Enabling MAC Address Lock and Traps by
Using the Web Agent
To use the Web Agent to enable the MAC Address Lock feature and
traps for unknown source addresses:
1. Manually add the “permitted” MAC addresses to the Address
Forwarding Table (AFT).
For information on how to manually add MAC address to the
AFT, see “Adding Entries to the AFT Manually” in chapter 6 of
Cajun P550R/P880/P882 Switch User Guide, Version v5.0.
2. Enter the following information on the Switch Port
Configuration page for the port:
a. Set the Allow Learning field to Disable.
b. Set the Known Mode field to Enable.
Note: To prevent flooding of frames from unknown source
addresses, set the Known Mode field to Enable for all ports
on the same VLAN as the port for which you are enabling
MAC address lock.
c. Set the Intrusion Trap field to Enable.
d. Adjust the trap timer, if desired.
See “Configuring Switch Port Parameters” in chapter 5 of Cajun
P550R/P880/P882 Switch User Guide Version 5.0, for
information on how to perform these procedures.
Enabling MAC Address Lock and Traps by Using the CLI
To use the CLI to enable the MAC Address Lock feature and traps for
unknown source addresses:
1. Enter Global Configuration mode.
The CLI displays the >(config)# prompt.

15
610-0184-095 June 14, 2001
2. Use the following command to manually add the “permitted”
MAC addresses to the Address Forwarding Table (AFT):
>(config)# set aft entry <mac address> vlan <vlan-id> port-
binding forward <mod-port-spec>
3. Use the following command to disable learning on a port or port
range:
>(config)# set port allow-learning <mod-
swport-range> disable
4. Use the following command to enable known-mode on a port
or port range:
>(config)# set port known-mode <mod-swport-range> enable
* Note: To prevent any flooding of frames from unknown
source addresses, enter all ports on the same
VLAN as the port for which you are enabling MAC
address lock.
5. Use the following command to enable intrusion traps on a port
or port range:
>(config)# set port intrusion-trap <mod-swport-range> enable
6. Use the following command to set the intrusion trap timer to
other than the default setting:
>(config)# set port intrusion-trap-timer <mod-swport-range>
<intrusion-trap-timer-value>
Enabling MAC Address Lock and Traps by Using SNMP
The MIB items that you use to perform this procedure are located in
ProminetMib.txt, version 5.2.
To use SNMP to enable the MAC Address Lock feature and traps for
unknown source addresses:
1. Use the MIB items that are listed in Table 4 to manually add the
“permitted” MAC addresses to the AFT.

610-0184-095
16 June 14, 2001
2. Use the MIB item that is listed in Table 5 to disable learning on a
port.
.
3. Use the MIB item that is listed in Table 6 to enable known mode
on a port.
4. Use the MIB item that is listed in Table 7 to enable intrusion traps
on a port.
Table 4. MIB, MIB Items, and OIDs for MAC Address Lock
MIB MIB Item OID
ProminetMib.txt,
version 5.2
promL2AddressControlIndex 1.3.6.1.4.1.2167.5.1.4.3.1.1
promL2AddressControlMacAddress 1.3.6.1.4.1.2167.5.1.4.3.1.2
promL2AddressControlPortBinding 1.3.6.1.4.1.2167.5.1.4.3.1.3
promL2AddressControlVlanID 1.3.6.1.4.1.2167.5.1.4.3.1.4
promL2AddressControlPriority 1.3.6.1.4.1.2167.5.1.4.3.1.5
promL2AddressControlPersistence 1.3.6.1.4.1.2167.5.1.4.3.1.6
Table 5. MIB, MIB item, and OID for Disabling Learning
MIB MIB Item OID
ProminetMib.txt,
version 5.2
promSwitchPortLearningMode 1.3.6.1.4.1.2167.5.2.1.1.4
Table 6. MIB, MIB item, and OID for Enabling Known Mode
MIB MIB Item OID
ProminetMib.txt,
version 5.2
promSwitchPortKnownMode 1.3.6.1.4.1.2167.5.2.1.1.7
Table 7. MIB, MIB Items, and OIDs for MAC Address Lock and Traps
MIB MIB Item OID
ProminetMib.txt,
version 5.2
promSwitchPortIntrusionTrap 1.3.6.1.4.1.2167.5.2.1.1.19

17
610-0184-095 June 14, 2001
Enhancements
The following events are now logged in the event log:
■Saving the running configuration to the startup configuration
■Creating an IP interface
■Modifying an IP interface
■Deleting an IP interface
Changed CLI Commands
■The get Fabric_mode command replaces the get
Cajun_mode command.
■The set Fabric_mode command replaces the set
Cajun_mode command.
Corrected Problems
The following problems have been corrected in this release:
■Pulling the base port on a hunt group no longer causes traffic
to lose duplexity and broadcast to all ports within the VLAN.
■The SNMP error message no longer displays when you
perform a LOADMIB operation.
■You can now create a row in the GenAppFile table in the
LOAD MIB.
■A software modification has been implemented for the LEDS
on the 24-port, 10/100 Ethernet module with RJ45
connectors. The LEDs no longer illuminate when nothing is
connected to them.
■The switch no longer stops learning remote MAC addresses
over the ATM link when 36 or more virtual switch ports
(VSPs) are configured.
■When running AppleTalk Network Assistance, the switch no
longer stops forwarding layer 3 traffic.

610-0184-095
18 June 14, 2001
Known Problems and Workarounds
The following known problems and workarounds apply to Cajun
P550R, P580, P880, and P882 switches that are running switch
software, v5.2.2. If a known problem has a viable workaround, it
immediately follows the Problem statement. If the known problem
has no viable workaround, it is listed as a bulleted statement.
ARP
Problem: 50-Series and 80-Series modules lose ARPs after you perform an
initialization of NVRAM (NVRAM init).
Workaround: Reboot the switch twice after performing an NVRAM init.
ATM Uplink Modules
The following problem has no workaround:
■The 50-series ATM Uplink modules do not work in slot 16 or
slot 17 if you are using an 80-Series Supervisor module in a
Cajun P882 switch.
Command Line Interface (CLI)
The following problem has no workaround
■The “!” character, when used as part of a CLI command, is
considered a comment by the Cajun switch software:
—If you type “!” BEFORE a CLI command, the switch
ignores the command and returns you to the CLI prompt.
—If you type “!” after a CLI command, the switch displays
an Invalid Command or Syntax Error error message.
Flood Rate Limiting
Problem: The options for setting flood rate limiting on 80-series, 10/100
Ethernet modules and on 80-series, 100 Base-FX Ethernet modules
are incorrect. The correct rates are not available from the Web Agent
or CLI.

19
610-0184-095 June 14, 2001
Workaround: Use the following table to determine the option that corresponds to
the rate that you want to set.
Table 8. Flood Rate Limiting on 80-Series 10/100 Modules
* Note: Do not use the 20%, 40%, or 80% options of the Web
Agent or CLI.
Frames Transmitted with Cyclic Redundancy Check (CRC)
Errors
Problem: For certain revisions of the Cajun P550R/P580/P880/P882 switch
12- and 20-port module (Model M5520-100TX, module Type 9,
revision level A or B and M5512-100TX, Revision A), a temperature
sensitivity problem has been found when operating at 10 Mbps. This
sensitivity results in the port transmitting frames with CRC errors.
These frames, since they have CRC errors, are then dropped by the
receiving station.
Workaround: The following legacy-cli command allows you to implement a new
configuration to disable the power saving mode of the Phy chip. This
has the same effect as moving the port’s operational temperature
past the problem range. The new configuration is saved only in
NVRAM:
> port set DisablePowerSave <port> on
* Note: Except for this command, the Legacy-CLI is not
supported by the Cajun Switch.
Desired Rate Web or CLI Setting
80% 10%
40% 5%
20% 2%
10% 1%

610-0184-095
20 June 14, 2001
Hot Swap Modules
The following problems have no workaround:
■Hot swapping 50-series modules may cause SEPROM and
SMAC panic messages to appear in the event log. These
messages are for informational purposes only and should be
ignored.
■When you insert a module into the switch, traffic may be
affected for up to seven seconds while the module performs
its hardware diagnostics.
IGMP Group Membership Table
Problem: The IGMP Group Membership Table does not display all members
when viewed from the Web Agent if the members are on different
interfaces.
Workaround: Use the following CLI command in User mode to view the members
of IGMP groups:
> show ip igmp groups
Intelligent Multicasting
The following problem has no workaround:
■Layer 2 Multicast data is not forwarded on slot 17 in the P882
chassis.
Problem: Intelligent Multicasting can block protocols to non-multicast
routers. If you have enabled Intelligent Multicasting and have
configured a VLAN to one or more non-multicast routers or
multicast-capable endstations, Intelligent Multicasting configures
router ports where multicast-enabled routers reside. These multicast
router ports allow all multicast packets to the adjacent multicast
routers. Ports connected to non-multicast enabled routers are not
considered router ports and do not receive multicast traffic. The
problem can arise when multiple IP multicast addresses are mapped
to the same multicast MAC address, resulting in protocol packets not
being sent to the adjacent non-multicast enabled routers.