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.
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).
■ 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.
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 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.
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.
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.
Configuring Port Mirroring By Using the CLI Use the following CLI commands to configure port mirroring on 80series 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.
Table 2. Port Ranges for 80-Series Port Mirroring Module 4-port gigabit modules Port ranges that you can mirror • 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.
Table 2. Port Ranges for 80-Series Port Mirroring Module 24-port 10/100 modules Port ranges that you can mirror • 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.
* Note: Avaya recommends that you mirror traffic to a port of the same speed or faster than the source port. ■ 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.
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.
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.
2. Enable or disable the suboptions as appropriate in the DHCP Option - Circuit Info and DHCP Option 82 - Agent Info fields.
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).
2. Use the following command to manually add the “permitted” MAC addresses to the Address Forwarding Table (AFT): >(config)# set aft entry vlan portbinding forward 3. Use the following command to disable learning on a port or port range: >(config)# set port allow-learning disable 4.
Table 4. MIB, MIB Items, and OIDs for MAC Address Lock MIB MIB Item OID ProminetMib.txt, 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 version 5.2 2.
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.
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: 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 Desired Rate Web or CLI Setting 80% 10% 40% 5% 20% 2% 10% 1% * Note: Do not use the 20%, 40%, or 80% options of the Web Agent or CLI.
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.
Example: The unicast routing protocol in use on all connected routers is OSPF, and all ports are on the same VLAN. An endstation joins the IP multicast group 226.128.0.5 on port 1. The MAC address for the group is 01:00:5E:00:00:05. IGMP snooping creates a session for this MAC address, with port 1 as the client port. There is a non-multicast OSPF router attached to port 2. OSPF uses the IP multicast link scoped group 224.0.0.5, which also maps to a MAC address of 01:00:5E:00:00:05.
state is set to Enable (all multicasts included). If you do not want to enable rate limiting of multicast traffic on a port, either: ■ Disable Intelligent Multicasting or ■ Disable Rate-limiting on the port. IP The following problems have no workaround: ■ If you create overlapping IP interfaces (interfaces in the same subnet), the state of the second interface is INACTIVE.
Workaround: Flush the L3 Forwarding Table before changing the L3 Forwarding Cache Max Entries value. Option 82 for DCHP The following problems have no workarounds: ■ The switch does not add relay agent information (option 82) to a BOOTP request. ■ The option 82 relay agent does not check frames for the IPSEC authentication header or IPSEC encapsulating security payload. PCMCIA The following problem has no workaround: ■ Text files copied from the PCMCIA card cannot be read.
Port Mirroring 80-Series Modules The following problem has no workaround: ■ Removing a port mirror causes an interface to stay in the “UP” state with no connections to the interface. Problem: If you mirror multiple ports, the switch monitors both transmit and receive traffic regardless of the direction of traffic that you specify.
■ If a router port for intelligent multicasting is mirrored with a piggyback port, the piggyback port is listed instead of the router port. Redundant Switch Controller The following problem has no workaround: ■ Do not enable redundancy unless you have a redundant switch controller. ■ On a P880 with an 80-series supervisor module, the redundant switch controller may not take over when the active switch controller fails.
Problem: If you remove the Public community string from the SNMP Community Management, save the running config to the startup config and then reset the switch, the Public community string you removed is not deleted. Workaround: Change the Public Community string to a different name.
Problem: When the 80-series Supervisor module boots, the switch displays the following error message in the CLI: Undefined Error -- FILE:gqswport.cLINE:449 Value 0xfffffffc: Error changing the GQ ‘port use diffserv’ flag Workaround: Ignore this message. 50-Series Supervisor Module The following problem has no workaround: ■ The display on the P880 switch M5500R-SUPA supervisor module may not initialize properly.
VLAN Issues The following problem has no workaround: ■ If you want a port to use both the VLAN auto-learning feature and VLAN binding type of Bind to Received or Bind to All, make sure that you set the VLAN binding type before you set Auto-learn to Enable or else the port may not be automatically added to the VLAN. Web AFT Issues Problem: The Web Address Forwarding Table (AFT) search does not return all entries that meet your search criteria when you search by status of entries.
Workaround: Either: ■ Disable auto-negotiation ■ Use a patch cable that is longer that 5 meters ■ Enter the following Enhanced CLI command in legacy mode: > port set NationalPhyMode . enable The factory default for the National Phy Mode is Enable. Checksum Error Message Problem: The following checksum error displays after you upgrade from 4.3.x code to v5.x code: Bad file header compressed checksum...transfer cancelled.
Workaround: The Legacy CLI is no longer supported in this release except for the following command that allows you to implement a new configuration to disable the power saving mode of the Phy chip (refer to the Frames Transmitted with Cyclic Redundancy Check (CRC) Errors section on page 3 under Known Problems and Workarounds: > port set DisablePowerSave on Distance Vector Multicast Routing Protocol (DVMRP) The switch may lose a small number of DVMRP neighbor-toneighbor probe messages which may caus
Loopback Tests Loopback tests on ports may fail when traffic is present on the link at start-up. Netscape 6.0 Do not use Netscape 6.0 as a browser with the Cajun Switch Web Agent. Oversized Packets Oversized packets are not counted in itemized statistics if the packet size is between 1519 and 1548 bytes. PCMCIA Only PCMCIA memory cards purchased from Avaya Inc. are supported in the PCMCIA slot of the M800R-SUP supervisor module.
Redundant Controller Support In the event that a Layer 3 redundant switch controller or element fails, the switch resets itself and records an entry of the event in the event log. SNMP To disable SNMP, you must set the access for all community strings to None. You cannot disable SNMP by deleting all community strings because the public community string is restored when you reboot the switch. Software License Keying Field upgradeable software features, such as routing, are supported only by v5.1.
TFTP Download Status Delay It takes a few seconds before the Status button on the TFTP Download screen returns accurate information. VLAN Issues ■ Automatic VLAN creation on P880 50-series supervisor module (M5500R-SUPA) does not work if the port default VLAN is set to “discard”. The switch does not learn VLANs with this setting. ■ Automatic VLAN creation on an 80-series supervisor module (M8000R-SUP) does work if the port default VLAN is set to “discard”.
The steps in ”Modifying OSPF Interfaces” of chapter 11, “Configuring the OSPF Routing Protocol” should read as follows: 1. Administratively disable the interface on which you want to modify OSPF. * Note: You must disable the interface to perform any OSPF modifications to the interface. 2. In the navigation pane of the Web Agent window, expand the Routing > IP > OSPF folders. 3. Click Interfaces. The OSPF Interfaces page opens (Figure 11-4). 4. Modify the OSPF interface parameters.
Appendix A: CLI Commands for Queue Classification and Servicing Overview This appendix contains the CLI commands that you use to configure the Queue Classification and Queue Servicing functionality in Version 5.2 of the Cajun switch software.
where is the slot number. If you specify this parameter, then all ports on the module in slot are set the same way. is a slot and port range in the form of 3/1 or 3/1-5. If you specify this parameter, then only the ports on the module in slot are set. is the priority that you want to assign to the port. Enter a number between 0 and 7. The highest priority is 7.
where is the slot number. If you specify this parameter, then all ports on the module in slot are set the same way. is a slot and port range in the form of 3/1 or 3/1-5. If you specify this parameter, then only ports on the module in slot are set. {on|off} indicates whether you want the port to ignore tag priority. Enter on for the port to ignore the tag priority. Examples ■ To set all ports on the module in slot 3 to ignore the 802.
Examples ■ To display the settings of all of the ports on the module in slot 3, enter: show port 3 ■ To display the settings of ports 1 through 5 on the module in slot 3, enter: show port 3/1-5 ■ To display the settings of ports 1 through 5 on the module in slot 3 and of port 1 on the module in slot 6, enter: show port 3/1-5,6/1 Setting a Rule in an Access Control List Command Use the access list command to set a rule on an access control list.
where: is a unique name that identifies the access control list. is the rule number within the access list. {permit|deny|fwd1|fwd2|fwd3|fwd4|fwd5|fwd6| fwd7|fwd8} is the priority that you want to set. The number following the fwd option specifies the priority. In other words, {permit|deny} are not valid selections. The fwdx arguments are "1" based, while the queue priorities are "0" based.
host is the destination IP address of the host. The destination IP address range is 0 to 255. [{lt|eq|gt|range} []] is a range of destination ports that pass data between two hosts or switches using the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). [established] permits TCP connections to be established that match the rule. * Note: You can also configure access control lists by using the Web Agent.
Setting WFQ Overview Setting the weighted fair queuing (WFQ) service policy involves two commands. In the first command, you specify the queue policy, the modules and ports for which you want to set the policy, and whether you want to set the queue service policy for ingress traffic, egress traffic, or both. In the second command, you specify the queue weights. Command 1 The correct syntax for Command 1 is: > (configure)# set queue-service {|}[...
Command 2 The correct syntax for Command 2 is: > queue weight where is the queue number, which can range from 0 to 7. is the weight that you want to assign to the queue. Weights can range from 0 to 255.
■ To assign a weight of 5 to queue 4, enter: > queue 4 weight 5 ■ To assign a weight of 6 to queue 5, enter: > queue 5 weight 6 ■ To assign a weight of 7 to queue 6, enter: > queue 6 weight 7 ■ To assign a weight of 8 to queue 7, enter: > queue 7 weight 8 Displaying the Queue Service Settings Command Use the show queue-service command to display the settings for queue service. The correct syntax for this command is: > show queue-service {|} [...
