Cajun P550R /P880/P882 Switch Release Notes - Version 5.0.1

Transcription

1 Cajun P550R /P880/P882 Switch Release Notes - Version Overview This set of release notes support the Cajun P550R/P880/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 access the latest release notes and other documentation at: These release notes cover the following topics: Important Information on page 2 Version Software Code on page 2 Known Problems and Workarounds on page 3 Functional Restrictions on page 11 Corrected Problems on page 17 Technical Support on page 19 1

2 Important Information This section contains information that is crucial to know before proceeding to install or use the Cajun switches. Please review the following Cautions before continuing. CAUTION * Note: The v5.0.1 P550R/P880/P882 switch code requires the v5.0.1 Help files. * Note: If you are using Netscape to view the online help, you cannot use a proxy server. Version Software Code Version software code is a maintenance release for software code v5.0: Supported Product Binaries and Boot Codes Table 1 shows the supported product binary files and boot codes that are supported by release v * Note: You must download the new boot code first, then download the new binary file. Table 1. v5.0.1 Product Binary and Boot Files Type of Switch Binary File Boot File P550R m5500r_v bin m550boot_v bin P880 m8800_v bin m880boot_v bin P882 m8820_v bin m882boot_v bin You can download the latest Cajun Switch software bootcode and code from the following FTP site: ftp:ftp.avayactc.com/avayactc/software 2

3 Known Problems and Workarounds ATM Uplink Module Command Line Interface (CLI) The following known problems and workarounds apply to the Cajun P550R/P880/P882 switch, v In some cases, the Known Problem is listed as a bulletized statement. In others, the Known Problem is immediately followed by a viable Workaround. The ATM Uplink module does not work in slot 16 if you are using an 80-Series Supervisor module. The! character is considered a comment by the Cajun P550R/P880/P882 switch software when used as part of a CLI command. If you type this character BEFORE a CLI command, the command is ignored and you are returned to the CLI prompt If you type this character after a CLI command, an Invalid Command or Syntax Error error message displays. Frames Transmitted with Cyclic Redundancy Check (CRC) Errors For certain revisions of the P550R/P880/P882 switch 12- and 20-port module (Model M TX, module Type 9, revision level A or B and M TX, 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. 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 <slot>.<port> on * Note: The Legacy-CLI is no longer supported as of this release except for this command. 3

4 Hot Swap Modules Intelligent Multicasting The following problems exist with no workaround: 80-Series Modules If you hot-swap a 24-port 10/100 TX module, errors will display in the error log. 50-Series Modules Hot swapping 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 a module is inserted into the switch, traffic may be affected for up to seven seconds while the module performs its hardware diagnostics. Layer 2 Multicast data is not forwarded on slot 17 in the P880 chassis. 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. 4

5 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 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 , which also maps to a MAC address of 01:00:5E:00:00:05. Because port 2 is not considered a router port, and it is not part of the 01:00:5E:00:00:05 session, the switch only passes OSPF messages out port 1. Other protocols, such as the Service Location Protocol (RFC 2608), use and , which can be blocked by endstations joining sessions that map to the same MAC address. Check that all ports that are connected to the router are configured as router ports. This prevents all router-to-router messages from being blocked. If other non-router protocols, such as the Server Location Service, are in use, create static sessions as needed. Do not create static sessions that conflict with the protocols used on your network. Refer to the following web site for a complete list of internet multicast addresses recognized by the IANA: multicast-addresses * Note: Enable is the default state for Rate Limiting on 10/100 Mbps ports. Multicast traffic is rate-limited (to 20%) on 10/100 Mbps ports. Multicast traffic is rate-limited unless Intelligent Multicasting is enabled. Multicast traffic for which the Intelligent Multicast session was created is not subject to rate limiting unless the rate limiting 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. 5

6 IP If you create overlapping IP interfaces (interfaces in the same subnet), the state of the second interface is INACTIVE. If you enter a non-numeric value in either the Network Address or Mask fields on the IP Static Route page, all of the numbers are rejected and the field converts back to 0. IPX IPX routed frames are sometimes padded in such a way that they are incompatible and discarded by older IPX clients and drivers. Use newer client software (v2.5 or later) or use a frame format other than (Avaya Inc. recommends that you use format 802.2). If you cannot use new client software or a newer frame format, you can use the following CLI commands to allow IPX clients to connect: IP Forward Set IPX Forward Get Refer to the Cajun P550R/P880/P882 Switch Command Line Reference guide for more details about these new commands. PCMCIA Booting from PCMCIA is not supported on 80-Series Supervisor (M8000R-SUP) modules in this release. Port Mirroring 80-Series Modules Port Mirroring is not supported on 80-Series modules for this release 50-Series Modules 6

7 When you try to mirror a blocked port, the Web Agent displays the port as forwarding, but it is blocked. When you remove the blocked port from being mirrored, you receive panic messages on the console. The problem does not interrupt traffic or cause any other problems in the network. If a standby supervisor module installed in slot 2 has become the Active supervisor (CPU) due to a failover, the web agent shows the supervisor module in slot 1as available for mirroring during a port mirroring operation. This is incorrect. This problem does not affect traffic running in the network. * Note: The Supervisor module should not be configured for port mirroring even if it displays as available for port mirroring. If a router port for intelligent multicasting is mirrored with a piggyback port, the piggyback port is listed instead of the router port. Point-to-Point Protocol (PPP) and Telnet A Telnet session to the serial port via PPP may time out during attempts to transfer large files, such as executable images, to a Trivial File Transfer Protocol (TFTP) server. This does not terminate the file transfer. An in-progress TFTP file transfer ends only after the file transfer is completed. A new baud rate may take effect before the current PPP connection is terminated if the baud rate change command is entered more than once. This results in the termination of the PPP connection. This requires re-establishment of a PPP connection. 7

8 Remote Monitoring (RMON) 30 minute RMON statistics always show utilization as 0 on a heavily used Gigabit Ethernet port. Statistics for unicast frames do not work when using multilayer (ISL) tagging. Simple Network-Management Protocol (SNMP) The following problems do not have workarounds: Cold start traps cannot be transmitted out of inband interfaces after you enable Spanning Tree. ipaddrtable does not display inactive interfaces (VLANs). An inactive interface occurs when there are no active ports on a VLAN. 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 is not deleted. Do not reset the switch after you delete any community strings. Supervisor Module 80-Series Supervisor Module Panic messages display on the CLI and on the Primary Supervisor LED readout after you install a second Supervisor module for redundancy. Ignore these messages. To successfully synchronize two 80-Series Supervisor module (M8000R-SUP), both must be in Cajun 2 mode In Cajun 2 mode, if you install an 80-series supervisor module (M8000R-SUP) as the redundant supervisor in slot 2 in a switch without backplane redundancy, the switch will continuously reboot. This will also occur after you power the switch off then on. 8

9 50-Series Supervisor Module The display on the P880 switch M5500R-SUPA supervisor module may not initialize properly. However, if it becomes the active supervisor module, the display becomes functional and displays the proper information. Switch Ports The following problem has no workaround: While switch port parameters are reflected across all ports of a Hunt group, spanning tree parameters are not. If you change the spanning tree priority of the flood port of a Hunt group, but that port does not come up first when bringing up the Hunt group, the spanning tree priority for the group reverts to the default. If a switch port is moved from Bind to Receive to Static, all previously bound VLANs are not removed. * Note: This is NOT a problem with the Bind to All setting. Remove VLANs manually from a port when changing a switch port connection from Bind to Receive to Static. RIP Configuring a RIP V1/V2 interface sends V2 packets to a V1 interface. If the corresponding interface is in RIP v1, configure your interface to RIP v1. 24-Port TX Module If you hot-swap a 24-port 10/100 TX module from your chassis with seven or more 24-port TX modules installed, you will no longer be able to change port settings. Reset the software after you hot-swap a 24-port TX module if you have seven or more 24-port TX modules installed and need to make port setting changes. 9

10 Temperature The backplane temperature incorrectly reads -1C on the P882 chassis. 3Com Binding 3Com binding is not supported for this release. VLAN Issues Configuring VLANs Duplicate VLAN Error Message The following problems have no workarounds: If you are using both the VLAN auto-learning feature and the Binding Type Bind to Received or Bind to All, make sure that you set the binding type before you set Auto-learn to Enable or else the port may not be automatically added to the VLAN. The following problem has no workaround: You may receive an error message after you add a VLAN and refresh your browser stating that the VLAN name is already in use. VRRP Web AFT Table Issues The following combinations do not support VRRP on v5.0.1: P550R - M5500R supervisor module with any layer 3 80-series modules P series supervisor module with layer 3 80-series Gigabit modules. The Web AFT table search does not return accurate address information. Use the CLI AFT table to get accurate address information. 10

11 Functional Restrictions Auto-Negotiation This section provides the functional restrictions for Release v5.0.1 switch software. M5520-TX (P/N M TX) boards manufactured with a Quality Phy do not auto-negotiate with Xircom brand adapter cards. If you are having this problem, disable autonegotiation on the affected ports, and set the port speed and duplex state manually. You may experience difficulties with auto-negotiation between some releases of the 10/100Base-TX Module (M TX, M TX, M5510R-100TX, M5512R-100TX) and adapter cards using physical interfaces manufactured by National Semiconductor. The symptom is loss of connectivity. Either: Checksum Error Message 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 <slot>.<port> enable The factory default for the National Phy Mode is Enable. The following checksum error displays after you upgrade 4.3.x code to v5.0.x code: Bad file header compressed checksum...transfer cancelled. Ignore the checksum error and reboot the switch to upgrade the software. 11

12 Legacy CLI The Legacy CLI setup command does not save information that you enter. The Legacy CLI is no longer supported in this release except for the: > port set DisablePowerSave <slot>.<port> on 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. Distance Vector Multicast Routing Protocol (DVMRP) The switch may lose a small number of DVMRP neighbor-toneighbor probe messages which may cause multicast routing instability under heavy loads. Gigabit Ports that Do Not Perform Auto-Negotiation The 50-Series Gigabit Ethernet ports operate at 1 Gbps full-duplex and have been widely tested for interoperability with other devices. Certain gigabit modules do not support auto-negotiation. To determine if a gigabit module supports the auto-negotiation feature, you can check the hardware revision of your gigabit module by viewing the Name field in the Modules and Ports dialog box on the Web Agent. Table 2 lists the 50-Series Gigabit modules that do not support the auto-negotiation feature: Table Series Gigabit Modules that do not Support Auto-Negotiation Model Number M SX-F M LX-F M SLX-F Hardware Revision M or earlier M or earlier F or earlier 12

13 Table Series Gigabit Modules that do not Support Auto-Negotiation Model Number M SX-F M LX-F M SLX-F M5502R-1000SX-F M5502R-1000LX-F M5502R-1000SLX-F Hardware Revision H or earlier H or earlier H or earlier J or earlier J or earlier H or earlier * Note: If a 50-Series Gigabit module does not support the autonegotiation feature and a device that supports autonegotiation is connected to it, you must disable autonegotiation to ensure proper operation. IEEE 802.1Q Packets When a tagged IEEE 802.1Q packet arrives on a port that is set to bind-to-all and the VLAN does not exist on the switch, the packet is forwarded to that port s default VLAN. To prevent unintended forwarding of unknown VLAN traffic to the port s default VLAN, configure the port default VLAN to discard. However, please note that automatic VLAN creation does not work if the port default VLAN is discard, because the switch does not learn this VLAN. IPC IPC restarts wile LANE traffic is running. The following error message displays: Log entry 194 by event 2 at 01-Feb-02 08:34:05 : Informative(20) Description: Range Error -- FILE:inbndipc.c LINE: 1408 Value 0X4 :IPC may have restarted, resend MACs. 13

14 Layer 3 Forwarding Cache Statistics You cannot clear Layer 3 forwarding cache statistics on 80-series modules Cache Configuration: The maximum system Entries are not configurable even though it appears to be from the web agent. The value will remain at Media Card Support Older versions of certain 50-series media cards restrict the number of usable slots that can be used in the Cajun P550R/P880/P882 switches to 13. Table 3 lists specific 50-series media cards and the minimum revision required to allow you to use up to 16 slots. Media cards not listed in Table 3 do not have a minimum revision requirement. Table Series Media Card Revisions that Provide 16-Slot Support Model Number Description M5512R-100TX L3 12 Port 10/100 Rev J M5510R-100FX L3 10 Port Fiber Rev N M5502R-1000SX-F L3 2 Port Gigabit Short Rev J M5502R-1000LX-F L3 2 Port Gigabit Long Rev J M5502R-1000SLX-F L3 2 Port Gigabit Super Long Required Revision to Support 16 Slots in a P880 Switch Rev H M SX-F L2 4 Port Gigabit Short Rev H M LX-F L2 4 Port Gigabit Long Rev H M SLX-F L2 4 Port Gigabit Super Long Rev H Hunt Groups Hunt groups can only consist of all layer 2 or all layer 3 modules. Hunt groups do not support a mixture of layer 2 and layer 3 modules. 14

15 Link Status When a large number of VLANs or endstations are on a Hunt group, it may take several seconds for the link status LED to change upon failure. Loopback Tests Loopback tests on ports may fail when there is traffic present on the link at start-up. 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 supervisor module s PCMCIA slot. Port Mirroring Redundant Controller Support Spanning Tree Protocol (STP) Port mirroring in Cajun 2 mode causes the source port to stop transmitting. If you use port mirroring, the port Frame Tag field on the Switch Port Configuration dialog box must be set to Use frames (default). In the event that the redundant switch controller or element fails, the switch resets itself and records an entry of the event in the event log. In release 4.1 and later, the STP Port Priority range has been changed. The values are now 1 to 15. If you changed the default range in an earlier release, you should verify that the priority is within the allowed range. 15

16 When the STP mode is set to IEEE 802.1D, Bridge Port Data Units (BPDUs) are sent out ports that are configured as Clear (non-trunked) even if the port is configured as a trunk (3Com, IEEE 802.1Q, or Dual-Layer) port. To alleviate this problem, disable STP for that port. TFTP File Naming Standard for Embedded NVRAM File System TFTP Download Status Delay VLAN Issues * Note: All NVRAM files must use an 8.3 format for file names. When downloading code to the NVRAM file system, use standard 8.3 file naming conventions. It takes a few seconds before the Status button on the TFTP Download screen returns accurate information. Automatic VLAN creation on P 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. If you set a port s VLAN trunking mode to Clear, you must keep the VLAN Binding Type to Static (default). 16

17 Corrected Problems The following problems have been corrected from release v The forwarding statistics on the Layer 3 Forwarding Cache now work. Previously, trying to open the Layer 3 Forwarding Stats would lock the router. The display continued to scroll but the web and serial interfaces were inaccessible. The router also stopped exchanging routing information. Previously, port configuration was not saved in config files. Port settings to any port other than port 1 were not reflected in the running config and thus could not be saved onto the startup config file. If the port settings for port 1 on a module were changed, n entries (the number of ports on that module) were seen in the running config for that change. When port 1 is set to Half-Duplex mode, the running config now correctly displays Full-Duplex mode for the port (the corresponding port auto-negotiates to Half-Duplex). * Note: The code fix does NOT affect a "broken" start-up config file. Unfortunately, you will still have to reset the port physical configurations AFTER you upgrade to the new software. This causes a new, corrected running configuration to be generated. You must then copy the new running config to the start-up config. You can then safely reboot the switch at any time. Flushing PRE cache no longer hangs the switch while sending traffic that was being routed on a module with PRE (L3 module). Error message now includes the slot number for the problem module. If it can get the slot number, it prints out the following panic messages: Log entry 12 by event 2 at 01-Feb-02 08:34:30 : Error(80) Description: Undefined Error--FILE:pre.cpp LINE: 2024 Value 0X4 : fabric port. Couldn t convert fabric port to slot. 17

18 Log entry 13 by event 2 at 01-Feb-02 08:34:30 : Error(80) Description: Undefined Error--FILE:pre.cpp LINE: 2025 Value 0X3 : slot. Memory allocation failure occurred during execution of last command. When the following error message displayed in the event log, degraded switch performance occurred: Error message pre.cpp LINE: Malloc The PRE that was getting more traffic got MemAllocFail messages. This caused the following error message to display: ====> Undefined Error--FILE:pre.cpp LINE:2053 Value 0X6 : Memory allocation failure occurred during execution of the last command. The command has now been changed to read: Error(80) 6====> Undefined Error-- FILE:pre.cpp LINE:2053 Value 0X6 : A slot 4 PRE reported dmalloc, lookup memory, may be approaching full. Fast Ethernet module cache entries can be set too high. The maximum number of cache entries that may be set for either the web or the enhanced CLI is The switch cannot handle that many entries. In this release, Cajun 1 mode now supports a maximum of entries, and Cajun 2 mode now supports a maximum of entries. ESR no longer proxies for the MAC address that it learned through the ATM Uplink module port. The switch would proxy for a MAC address that it learned through the ATM uplink module port. If the ATM Uplink module was reset without clearing the AFT table, the switch would then proxy for all of the learned MAC addresses in the AFT, even the MAC that was learned through the ATM Uplink module port. The switch would then answer an LE-ARP request for those MAC addresses so the other clients would have the MAC to NSAP mapping in their LE-ARP cache. 18

19 Technical Support To contact Avaya s technical support: * Note: These are new phone numbers as of October 1, From the United States: From North America: Outside North America: Contact your distributor 19