Release Notes OmniSwitch 6600/7000/8800 Release 5.1.6.R02 These release notes accompany release 5.1.6.R02 software for the OmniSwitch 6600 family hardware, OmniSwitch 7000 series hardware, and OmniSwitch 8800 hardware. They provide important information on individual software features and hardware modules.
Related Documentation Related Documentation These Release Notes should be used in conjunction with the OmniSwitch 6600, OmniSwitch 7700/7800, and OmniSwitch 8800. The following are the titles and descriptions of the OmniSwitch 6600, OmniSwitch 7700/7800, and OmniSwitch 8800 user manuals: • OmniSwitch 6600 Family Getting Started Guide Describes the hardware and software procedures for getting an OmniSwitch 6600 Family switch up and running.
Related Documentation • OmniSwitch 7700/7800/8800 Switch Management Guide Includes procedures for readying an individual switch for integration into a network. Topics include the software directory architecture, software rollback protections, authenticated switch access, managing switch files, system configuration, using SNMP, and using web management software (WebView). • OmniSwitch 7700/7800/8800 Technical Tips, Field Notices Includes information published by Alcatel’s Customer Support group.
System Requirements System Requirements Memory Requirements • OmniSwitch 6624 Release 5.1.6.R02 requires 128 MB of SDRAM and 32MB of flash memory. This is the standard configuration shipped. • OmniSwitch 6648 Release 5.1.6.R02 requires 128 MB of SDRAM and 32MB of flash memory. This is the standard configuration shipped. • OmniSwitch 6600-U24 Release 5.1.6.R02 requires 128 MB of SDRAM and 32MB of flash memory. This is the standard configuration shipped. • OmniSwitch 6600-P24 Release 5.1.6.
System Requirements Power Supply Requirements The OS7000/8800 power supply requirements vary depending on the number of Network Interface (NI) modules installed in the switch and the power redundancy requirements. Each OS7800/OS8800 chassis contains four slots for power supplies, and the OS7700 chassis has three slots for power supplies. Note.
New Hardware Supported New Hardware Supported No new hardware has been introduced in release 5.1.6.R02. page 6 OmniSwitch 6600/7000/8800—Release 5.1.6.
New Software Supported New Software Supported The following new software features are supported subject to the feature exceptions and problem reports described later in these release notes: Feature Summary Feature Platform Software Package 802.1s Multiple Spanning Tree all base 802.1x Multiclient Support all base 802.
New Software Supported In addition to 802.1s MSTP support, the 802.1D STP and 802.1W RSTP are also available in either the flat or 1x1 mode. The flat mode applies a single spanning tree instance across all VLAN port connections on a switch. However, if using 802.1D or 802.1W in the flat mode, the single spanning tree instance per switch algorithm applies. A new path cost mode command is available to control whether the switch uses a 16-bit port path cost (PPC) or a 32-bit PPC.
New Software Supported Copper Gigabit SFP Support on OmniSwitch 6600 Family In release 5.1.6.R01 and later, copper Gigabit SFPs are now supported on OmniSwitch 6600 Family switches. These SFPs can be used with the built-in Gigabit uplink slots on the OS6602-24 and OS6602-48 switches and on the OS6600-GNI-U2 uplink submodule. Note. Copper Gigabit SFPs on OmniSwitch 6600 Family switches support 1000 Mbps and full duplex. They do not support 10 or 100 Mbps speeds or half duplex mode.
New Software Supported Improved Spanning Tree Support for High Availability VLANs High Availability (HA) VLANs now run on inter switch links in conjunction with spanning tree. All spanning tree modes and protocols are supported (flat, 1x1, 802.1d, 802.1w, and 802.1s). IPv6 IPv6 (documented in RFC 2460) is designed as a successor to IPv4.
New Software Supported By default, the switch will create a data file called “pmonitor.enc” in flash memory. When the 140K limit is reached, the switch will begin overwriting the data starting with the oldest captured data. However, you can configure the switch so it will not overwrite the data file. In addition, you can configure additional port monitoring files as long as you have enough room in flash memory.
Supported Traps Supported Traps The following traps are supported in 5.1.6.R02: No. Trap Name Description 0 coldStart The SNMP agent in the switch is reinitiating and its configuration may have been altered. 1 warmStart The SNMP agent in the switch is reinitiating itself and its configuration is unaltered. 2 linkDown The SNMP agent in the switch recognizes a failure in one of the communications links configured for the switch.
Supported Traps No. Trap Name Description 19 bgpBackwardTransition This trap is generated when the BGP router port has moved from a more active to a less active state. 20 esmDrvTrapDropsLink This trap is sent when the Ethernet code drops the link because of excessive errors. 21 pimNeighborLoss Signifies the loss of adjacency with a neighbor device. This trap is generated when the neighbor time expires and the switch has no other neighbors on the same interface with a lower IP address than itself.
Supported Traps No. Trap Name Description 29 mirrorUnlikeNi The mirroring configuration is deleted due to the swapping of different NI board type. The Port Mirroring session which was active on a slot cannot continue with the insertion of different NI type in the same slot. 30 slPesudoCAMStatusTrap The trap status of the Layer 2 pesudoCAM for this NI. 31 unused 32 unused 33 slbTrapOperStatus A change occurred in the operational status of the server load balancing entity.
Supported Traps No. Trap Name Description 52 ospfVirtNbrStateChange Indicates a state change of the virtual neighbor relationship. 53 httpServerDoSAttackTrap This trap is sent to management station(s) when the HTTP server is under Denial of Service attack. The HTTP and HTTPS connections are sampled at a 15 second interval. This trap is sent every 1 minute while the HTTP server detects it is under attack.
Supported Traps No. Trap Name Description 66 A File Written Trap is sent when the amount of data requested by the user has been written by the port monitoring instance. monitorFileWritten (* See note below) Note. *These are new or enhanced traps. page 16 OmniSwitch 6600/7000/8800—Release 5.1.6.
Unsupported Software Features Unsupported Software Features CLI commands and web management options are available in the switch software for the following features; however, these features are not supported in the current release: Feature Platform Software Package Interswitch Protocols (GMAP) all base IP Multicast Routing OS6600 base OSPF Database Overflow (RFC 1765) all base advanced routing OmniSwitch 6600/7000/8800—Release 5.1.6.
Unsupported CLI Commands Unsupported CLI Commands The following CLI commands are not supported in this release of the software: Software Feature Unsupported CLI Commands Chassis Mac Server mac-range local mac-range duplicate-eeprom mac-range allocate-local-only show mac-range status Hot Swap reload ni [slot #] Interswitch Protocols (GMAP) All Interswitch Protocols (GMAP) CLI Commands on all platforms are unsupported IP Multicast Routing All IP Multicast Routing CLI Commands on OS6600 are unsupport
Unsupported MIBs by Platform Unsupported MIBs by Platform The following MIBs are not supported in this release of the software. MIB Feature Interswitch Protocols (GMAP) All MIBs are unsupported. IP Multicast Routing All MIBs for OS6600 are unsupported. Quality of Service (QoS) IETF_P_BRIDGE Unsupported MIB Variables—All Platforms MIB Name Unsupported MIB variables on All Platforms AlcatelIND1AAA aaauProfile AlcatelIND1Dot1X.
Unsupported MIBs by Platform MIB Name Unsupported MIB variables on All Platforms IETF_MAU (RFC 2668) rpMauTable rpJackTable broadMauBasicTable ifMauFalseCarriers ifMauTypeList ifMauAutoNegCapability ifMauAutoNegCapAdvertised ifMauAutoNegCapReceived IETF_OSPF (RFC 1850) ospfAreaRangeTable IETF_OSPF_TRAP ospfTrapControl IETF-PIM pimRPTable IETF_P_BRIDGE dot1dExtBase dot1dPortCapabilitiesTable dot1dPortPriorityTable dot1dUserPriorityRegenTable dot1dTrafficClassTable dot1dPortOutboundAccessPriorityT
Unsupported MIBs by Platform MIB Name Unsupported MIB variables on All Platforms IETF_SNMP_TARGET (RFC 2573) snmpTargetAddrTable snmpTargetParamsTable snmpTargetSpinLock IETF_SNMP_USER_BASED_SM (RFC 2574) usmUser IETF_SNMP_VIEW_BASED_ACM (RFC 2575) vasmMIBViews NOVELL_IPX ipxStaticRouteTable ipxDestServTable ipxStaticServTable ipxBasicSysConfigSockets ipxBasicSysOpenSocketFails ipxAdvSysInCompressDiscards ipxAdvSysOutCompressDiscards ipxCircDialName ipxCircCompressState ipxCircCompressSlots ipxCir
Unsupported MIBs by Platform Unsupported MIB Variables—OmniSwitch 7000 series MIB Name Unsupported MIB Variables—OmniSwitch 7000 Series AlcatelIND1Port Alcether10GigTable AlcatelIND1VlanManager vlanTagMobilePortStatus AlcatelIND1StackManager alaStackMgrChassisTable alaStackMgrStatsTable alcatelIND1StackMgrMIBObjects Unsupported MIB Variables—OmniSwitch 8800 MIB Name Unsupported MIB Variables—OmniSwitch 8800 AlcatelIND1VlanManager vlanTagMobilePortStatus AlcatelIND1StackManager alaStackMgrChass
Unsupported MIBs by Platform MIB Name Unsupported MIB Variables—OmniSwitch 6600 Series AlcatelIND1Pcam alcatelIND1PCAMMIBObjects alaCoroL3HrePerModeTable alaCoroL3HrePerCoronadoStatsTable alaCoroL3HreChangeTable AlcatelIND1Pimsm alaPimsmGlobalConfig alaPimsmDebugConfig AlcatelIND1QoS alaQoSRuleReflexive alaQoSAppliedRuleReflexive alaQoSActionAlternateGatewayIpAddr alaQoSActionAlternateGatewayIpAddrStatus alaQoSActionPermanentGatewayIpAddr alaQoSActionPermanentGatewayIpAddrStatus alaQoSActionShared a
Unsupported MIBs by Platform MIB Name Unsupported MIB Variables—OmniSwitch 6600 Series AlcatelIND1VlanManager vlanIpxNet vlanIpxEncap vlanIpxRipSapMode vlanIpxDelayTicks IETF_BGP4 bgp bgpPeerTable bgp4PathAttrTabl IETF_PIM pim pimInterfaceTable pimNeighborTable pimIpMRouteTable pimIpMRouteNextHopTable pimRPSetTable pimCandidateRPTable pimComponentTable IETF_IPMROUTE_STD ipMRoute ipMRouteTable ipMRouteNextHopTable ipMRouteInterfaceTable ipMRouteBoundaryTable NOVELL_IPX ipxBasicSysTable ipxAdvSy
Fixed Problem Reports Fixed Problem Reports The fixed problems listed here were reported by customers and fixed in this release. Switch Management Command Line Interface (CLI) Problem Reports PR 91398 On an OS7000 series switch, the bandwidth parameter for High Availability VLANs is not available in CLI. Layer 2 Bridging Problem Reports PR 88192 Decnet frames make the mobility port not to work.
Fixed Problem Reports IPv6 Problem Reports PR 91124 If routes from two different peers have the same network address, but different mask lengths, only one route is created / updated. Quality of Service (includes ACLs and NAT) Problem Reports PR 68906 Sometimes, all the policies do not flush. This applies to all platforms. PR 81620 After the LDAP server is deleted from a switch, there is no way to remove all related policies from the QoS layer.
Fixed Problem Reports Security Authenticated VLANs Problem Reports PR 86129 Authenticated users are lost after a QoS apply. PR 87149 MAC-ADDRESS gets learned on the default VLAN even if AVLAN default traffic is disabled. Policy Server Management Problem Reports PR 68906 Sometimes, all the policies do not flush when flushing from WebView. OmniSwitch 6600/7000/8800—Release 5.1.6.
Open Problem Reports and Feature Exceptions Open Problem Reports and Feature Exceptions The problems listed here include problems known at the time of the product’s release. Any problems not discussed in this section should be brought to the attention of the Alcatel Technical Support organization as soon as possible. Please contact customer support for updates on problem reports (PRs) where no known workaround was available at the time of release.
Open Problem Reports and Feature Exceptions PR 69058 The admin down CLI command on an OS7-GNI-U2 or OS6-GNI-U2 port does not bring the link down on the remote end. Workaround: Unplug the port. PR 77445 The write terminal and show configuration snapshot output may be lost when using Windows 2000 telnet to connect to a switch. Workaround: Use Unix, Windows NT, or Windows XP to connect to the switch.
Open Problem Reports and Feature Exceptions PR 91912 While configuring an OSPF interface with the ?ip ospf interface? command, spaces cannot be used in the interface name. For example, entering the ?ip ospf interface vlan-101? command is valid, but entering the ?ip ospf interface vlan 101? command is not. Workaround: Do not use spaces in the OSPF interface name. PR 92286 Command prompt may disappear after attempting the "show" command not allowed for users. Workaround: Type exit and then login again.
Open Problem Reports and Feature Exceptions PR 50089/53442 When a GetNext request is sent on any object of the trapConfigTable, sessionConfigTable, or trapFilterTable, and if the index value is equal to 4294967295, then the agent does not respond as expected; i.e. the object returned is not lexicographically larger on an OS7000 series switch. Workaround: There is no known workaround at this time. PR 50404 Our system treats user name "admin" differently from other user names.
Open Problem Reports and Feature Exceptions PR 81410 On OS6600 series switches, the SNMP Agent fails to properly handle out of range msgSecurityModel values. Workaround: There is no known workaround at this time. PR 82635 On an OS7000 series switch, there is no SNMP MIB support to display the number and status of fan modules on a switch via SNMP MIB Browsers and WebView. The number and status of fans can be displayed only via the CLI interface's command: show fan.
Open Problem Reports and Feature Exceptions Web-Based Management (WebView) Feature Exceptions • WebView uses signed applets for the automatic IP reconfiguration. Those applets are signed using VeriSign Certificates that expire every year. The certificate used for Internet Explorer and Netscape expires every August. WebView users have to validate a warning indicating that the certificate used by the applet has expired.
Open Problem Reports and Feature Exceptions PR 57944 A warning box appears on the Netscape browser when trying to telnet using HP-UX 11.0 or Sun Solaris’ on an OS7000 series switch. This is due to missing or invalid telnet settings on the applications used by the browser. Workaround: Update your telnet settings as per the instructions below: 1 Click on the "Edit Menu" on the Netscape Browser and select "Preferences".
Open Problem Reports and Feature Exceptions PR 60192 Some WebView screens do not display if Internet Explorer 5.5 is installed without Java Virtual Machine (JVM) on an OS7000 series switch. Current screens affected are Physical-Health-Home, and System-FilesystemMgt-Install. Workaround: The Internet Explorer browser must be installed with Java Virtual Machine (JVM). After the installation of service pack 2 for Internet Explorer 5.
Open Problem Reports and Feature Exceptions PR 65263 A JavaScript error may appear when a session is terminated by a method other than WebView on an OS6624/6648 series switch. Workaround: This is a display issue only. Disregard any warnings / dialog boxes.
Open Problem Reports and Feature Exceptions PR 71891 When adding an accept action on an OS7000 series switch using the Actions > ACL page, if no SLB cluster is provided, the just added action will not show up on the Actions > ACL table. (However, it will be displayed in the Actions > All table.) Workaround: Go to the Actions > All table.
Open Problem Reports and Feature Exceptions PR 80209 WebView health port clear statistics will not clear slot 16 on an OS7000 full chassis. Workaround: Please ignore old information. PR 80236 The Remote System File Management page on OS6600 switches: Applying List Files doesn't display the directory contents in time due to the timing issue. Workaround: The user must click the Refresh button in order to see the directory contents on the screen.
Open Problem Reports and Feature Exceptions PR 81067 WebView's Physical Modules Summary information does not sort the slot column data properly. WebView is using a numerical sort, which is not ideal for data in this column. However, all slot data is displayed. Workaround: There is no known workaround at this time. PR 81316 The Chassis Hardware Information page does not show the Firmware Revision on an OS6600 chassis. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 83829 Whenever you access a WebView page through the browser history list after logging in an OS7000 series switch, the page accessed will display without the usual control frames. Workaround: Refrain from using the history list. ("Site Map" page is available from each home page containing direct links to table and configuration pages.) PR 84031 WebView's "Reload On" function for an OS6600 series switch does not function according to specification.
Open Problem Reports and Feature Exceptions PR 84618 The Policy > Policy > Ports Modify window, returns the error message, "Port enable/disable is not supported”, whenever one tries to make a change. Workaround: Manually set the "Enabled" field to a blank during modification and continue with the rest of the changes. PR 84635 WebView may sort some numerical columns incorrectly. For example, the HRE tables sorted by the firmware revision. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 89093 On an OS6600 series switch, in WebView, Networking > IP Multicast users with only read-write permissions on IPMS, IPMR, and Web Management cannot add a static neighbor/groups/querier due to the VLAN and slot/port drop-downs being empty (insufficient permissions). Workaround: Add read-only permissions to include VLANs and ports, or use corresponding CLI commands (VLAN, slot/port will have to be known as well).
Open Problem Reports and Feature Exceptions PR 92311 In WebView, Networking > IPv6 > Addresses page is missing the ability to add an EUI-64 address to an IPv6 interface. Workaround: There is no known workaround at this time. PR 90790 On an OS8800 switch, adding an IPv6 protocol rule to a VLAN fails with "protocol limit reached". Workaround: An IPv6 protocol Ethertype 0x86dd rule can be added to a VLAN using the CLI.
Open Problem Reports and Feature Exceptions PR 91014 On an OS8800 switch, the force tag internal disable is not working. The original VLAN id in an 802.1q packet ingressing an untagged port is replaced with the default VLAN of the ingress port when this VLAN id is tagged on the egress port. Workaround: There is no known workaround at this time. Bridging Problem Reports PR 75329 On an OS7000 series switch, the user guide has a bug which requires the custom rule mask values to be in nibble patterns (f).
Open Problem Reports and Feature Exceptions PR 89608 On an OS6600 series switch, as per the design of the group mobility rule structure, creation of a DSAPSSAP rule is expected only for the non standard or custom defined DSAP SSAP values. For well known DSAP SSAP values like IPX-SNAP, an IPX-SNAP rule should be configured. Workaround: There is no known workaround at this time. PR 89827 Network rule conflicts are not resolved or prevented at the CLI level.
Open Problem Reports and Feature Exceptions PR 92718 Upon VLAN deletion, there is a sufficient delay for the Group Mobility message to move from the CMM to NI for the deletion of rules associated with this NI. If the switch has live traffic, it continues to apply these rules and classify the frames. If the classification is for discard on a binding rule violation, the existence of the VLAN is not checked.
Open Problem Reports and Feature Exceptions Problem Reports PR 70128 AMAP currently works on the default VLAN for tagged ports only. So, if VLAN 1 (default VLAN) is disabled, AMAP does not work. Workaround: When using AMAP, make sure that VLAN 1 (default VLAN) is not disabled. IP Multicast Switching (IPMS) Problem Reports PR 57746 IP Multicast does not support hardware routing with 802.1Q service on an OS7000 series switch. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 69039 The user cannot achieve wire rate multicast performance between stack elements on an OS6624/6648 series switch. Standalone performance is wire rate. Workaround: There is no known workaround at this time. PR 75172 On an OS7000 series switch, IGMP memberships may be lost if the hosts reside on the NI having high CPU utilization. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 83996 Query Max Response Time cannot be set through CLI or WebView on an OS7000. Workaround: This can be set through SNMP variable igmpInterfaceQueryMaxResponseTime. PR 84009 It is not possible to configure an interface as IGMPv1 through the CLI or WebView on an OS7000 series switch. Workaround: Configure an interface as IGMPv1 through SNMP. PR 89462 Ingress IGMP packets are not mirrored to the destination port.
Open Problem Reports and Feature Exceptions PR 73953 With an LPS (Learned Port Security) configuration is set only to allow a specific MAC on a port, and when the port receives non-authorized traffic (ARP requests), the MAC information shows that the unauthorized host is in a "filtering" state; therefore all traffic should be filtered. However, the ARP table learns the ARP entry for the filtered host. ARPs should not be learned for "filtered" hosts. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 70779 Dynamic link aggregation over 802.1q on an OmniSwitch 8800 switch does not work with Cisco Cat 6509. Workaround: There is no known workaround at this time. PR 70920 There is a warning message displayed when you create multiple system priorities in the same range for link aggregation on an OS6624/6648 series switch. Workaround: The system priorities should be the same.
Open Problem Reports and Feature Exceptions PR 77684 On an OS7000 series switch, replacing second generation NIs with first generation NIs causes ports not to come up. Workaround: If second generation boards are hotswapped with first generation boards, some link aggregate ports may not come up. Replace second generation interfaces with second generation interfaces only.
Open Problem Reports and Feature Exceptions PR 78909 On OS7000 and OS8800 switches, once a second-generation NI port is added to a link aggregate, one cannot add a first-generation NI port. Workaround: 1) Add a first generation NI port first, and then add subsequent second generation ports. 2) Add ports in boot.cfg and reboot. PR 78945 More than 14 link aggregates with size “8” cannot be added. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 81288 On an OS7000 series switch, LACP packets stop being exchanged after enabling the backpressure command. Workaround: Do not run this command with LACP configured. PR 81416 On an OS7000 series switch, changing LACP values on run time makes the ports not join the link aggregate. Workaround: Do not change LACP values on the run time. If needed, delete the port and add again to make a modification.
Open Problem Reports and Feature Exceptions PR 81937 With the optimization enabled command, it is impossible to delete a port from link aggregate. Workaround: Disable the optimization command to delete the ports from link aggregate and re-enable the optimization command. PR 81985 On an OS8800 switch, LACP ports do not join the aggregate if some of the ports are administratively down.
Open Problem Reports and Feature Exceptions Port Mirroring Feature Exceptions • On OS6600 switches, port mirroring is not supported across a stack, i.e. mirrored port on slot 1 and mirroring port on slot 4. • On an OS6648 switch, port mirroring is not supported between lower ports (Fast Ethernet port 1-24 or Gigabit Ethernet port 51-52) and upper port (Fast Ethernet port 25-48 or Gigabit Ethernet port 49-50).
Open Problem Reports and Feature Exceptions PR 68515 Performance of port mirroring is around 3000 packets/second after a hot swap on an OmniSwitch 8800 switch. Workaround: There is no known workaround at this time. PR 71793 Port mirroring is not at wire rate. The mirrored port will drop traffic when port mirroring is enabled on an OS7000 series switch. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 81038 Ingress flood traffic is seen on mirroring port in case of outport mirroring on an OS7000 port. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 90120 IPMS traffic is not captured during a port monitoring session. Workaround: There is no known workaround at this time. Source Learning Feature Exceptions • The number of MAC addresses supported on an OS6600 series switch is 8K. Problem Reports PR 53663 MAC load balancing does not spread out the MACs among 4 ports on an OS7000 series switch. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 59745 Due to the time required for the aging check, the aging-time is not very accurate for small measures of time, i.e. under 1 minute on an OS7000 series switch. Workaround: There is no known workaround at this time. PR 64506 When the amount of MACs on an OS6624/6648 switch reaches 85% of 16K, the fast aging mechanism will start to age out all of the MACs faster. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 80435 On an OS8800 switch, if you change the protocol to 1W in the root switch first, chances are the root switch would still receive 1D BPDUs from other switches, causing the root switch to revert back to 1D. Workaround: Please change the protocol on the non-root switches first, and then do the root switch last.
Open Problem Reports and Feature Exceptions PR 90957 After takeover on an OS6600 series switch, sometimes MACs do not get in sync between the CMM and NI. This can cause some unwanted flooding. Workaround: Applying the command no mac-address-table learned should fix the problem. PR 92317 Traffic with a High Availability VLAN Mac address as a destination address on a port that is NOT configured for HA VLAN is flooded to all ports of the VLAN following the standard flooding path.
Open Problem Reports and Feature Exceptions PR 72119 On an OS7000 series switch, when redundant links are present between two MSTP bridges, the resultant topology will choose a blocking port regardless of the VLAN port mapping on the links. Therefore, if a VLAN is configured on one redundant link, but not the other, the bridge may block the port that the VLAN is configured on. Workaround: This is a known issue with MSTP and the older flat spanning tree.
Open Problem Reports and Feature Exceptions PR 87565 The BPDU switching flag is not applied after reboot. Workaround: After reboot, typing the command again will solve the problem. PR 89086 The force version parameter is not supported. Workaround: Use a protocol identifier, i.e. protocol commands and variables, instead. PR 89316 With every link-up, a BPDU packet with the Root BridgeID of 0xffff is sent to elicit a BPDU reply from the adjacent switch in the current AutoEdge Detection mechanism.
Open Problem Reports and Feature Exceptions Problem Reports PR 54327 If the VLAN ID of the AV-Client dialog box is entered incorrectly twice on an OS7000 series switch, one receives the following error: "Failure during DoSendData () call" and the AV-Client dies. A similar behavior is observed with unsuccessful authentication. For example, unknown user on the remote authentication server. Workaround: Reboot of the PC is required.
Open Problem Reports and Feature Exceptions PR 60125 The tag value cannot be changed from the VLAN number on an OS7000 series switch. This is a hardware limitation. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 62119 The ip-port and mac-ip-port binding rules filter the IP address on a port configured if it does not match on an OS7000 series switch. Once the MAC address is made part of the VLAN targeted by such rules, the IP address can change to another address in the subnet or subnets carried on that VLAN. For example, if an ip-port binding rule is created for VLAN 21 with an IP address of 21.0.0.22 and a port of 2/3, the device has an IP address configured as 22.0.
Open Problem Reports and Feature Exceptions PR 69656 Unicast frames will be flooded on an OmniSwitch 8800 switch until all the MAC addresses are learned in both the source and destination CAMs. Workaround: There is no known workaround at this time. PR 70811 A default VLAN might come up in operational state when it is disabled to accommodate group mobility. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 75199 When using the group mobility custom rule, traffic goes on the default VLAN even though the content (at the offset) of a new stream of traffic (from the same MAC device) is matching the MAC address already learned in the default VLAN. Workaround: Flush the MAC address learned on the default VLAN, then resend the traffic.
Open Problem Reports and Feature Exceptions PR 92573 The configured High Availability VLAN bandwidth is global on a switch and not per VLAN even though the CLI command is on a per VLAN basis. The latest High Availability VLAN bandwidth configured determines the global bandwidth. Workaround: There is no known workaround at this time. PR 92575 The High Availability VLAN Bandwidth is granted on a per ingress slot basis.
Open Problem Reports and Feature Exceptions PR 59599 The number of TCP reset does not match the number of SYN Request packets after doing a show tcp statistics command on an OS7000 series switch. Workaround: There is no known workaround at this time. PR 67799 Performance may drop slightly below wire rate while routing small-sized packets on an OS6624/6648 switch. Workaround: There is no known workaround at this time. PR 71573 An OS6624/6648 switch does not support multiple router MAC address mode.
Open Problem Reports and Feature Exceptions PR 75002 There is no provision to configure per VLAN IP MTU on an OS6624/6648 switch. As a result, once the flow is setup on the OS6624/6648 (meaning both the Src/Dest addresses are learned), if a packet violating the IP MTU is received, it will still be forwarded by the hardware. IP MTU checking is done in software, so it will work for the first packet (that comes to software), i.e. for the first packet, the switch will send back an appropriate ICMP response.
Open Problem Reports and Feature Exceptions PR 80494 On an OmniSwitch 6624/6648 switch, packets routed between IP-SNAP & Ethernet 2 are not translated correctly. The Intel IXE2424 ASIC used in the 6600 platform does not support translations from SNAP to Ethernet II packets. Workaround: There is no known workaround at this time. PR 81354 RIP task traps when more than 2K RIP routes are sent in the OS6600 Router from a RIP peer.
Open Problem Reports and Feature Exceptions PR 92791 Redistributed routes get added to the RIP routing table even though the global rip status is disabled. Workaround: Disable redistribution status. IPv6 Problem Reports PR 86669 IPv6 Router Advertisement decrementing timers are not supported for prefix valid lifetimes or prefix preferred lifetimes. Workaround: Use IPv6 Router Advertisement fixed timers. PR 86959 IPv6 debug packet direction options are ignored.
Open Problem Reports and Feature Exceptions PR 91228 On an OS7000 series switch, the system does not detect IPv6 port scanning, nor other IPv6 denial of service attacks. Workaround: There is no known workaround at this time. PR 91898 It is possible to add two IPv6 configured tunnels with the same source and destination IPv4 addresses. This is discouraged since it may have some unusual consequences. Workaround: Create only a single IPv6 configured tunnel with the same source and destination IPv4 addresses.
Open Problem Reports and Feature Exceptions IPX Problem Reports PR 54290 The switch only changes an IPX network field of zero to the appropriate source network when the first zero packet arrives on an OS7000 series switch. After that point, the IPX packets pass through the HRE, and cannot be changed. Workaround: There is no known workaround at this time. PR 61257 The show ipx interface command displays "WAN processing not enabled on this interface" on an OS7000 series switch.
Open Problem Reports and Feature Exceptions PR 91850 IPX statistics are not correct with WebView or SNMP. Workaround: A show ipx traffic command needs to be executed on CLI, so that the statistics can be retrieved from the NIs. PR 91979 IPX network address cannot be set through SNMP. Workaround: Use either CLI or WebView to set IPX network address. NTP Client Feature Exceptions • NTP is not supported in Server mode.
Open Problem Reports and Feature Exceptions PR 90160 On an OS7000 series switch, when a URL file address is added to an SLB probe, a '/' is added. Workaround: There is no known workaround. This functionality helps when sending the HTTP GET. Since the parameter is an offset to a file on the HTTP server, we made sure there was a '/' for the GET.
Open Problem Reports and Feature Exceptions PR 84592 In certain cases, frames are duplicated with UDP Relay on an OS7000 series switch. Workaround: 1. With VRRP, enabling only on one VRRP router (either master or backup) is desirable for any UDP relay service to avoid UDP frames being duplicated. 2. If there are ECMP routes, enabling on one backbone VLAN is desirable for any UDP relay service. 3. If 802.1Q is configured on multiple switches, UDP relay service only needs to be enabled on one switch.
Open Problem Reports and Feature Exceptions PR 88251 If there is a port tracking policy and a single VLAN on a port, and if the vlan is disabled, spanning tree marks the port as blocked. VRRP is not notified that the port is unusable and the port tracking policy is not invoked. Workaround: Configure tracking policies for both the port and the vlan. PR 89046 With release 5.1.6.R01 the basis for the VRRP implementation is RFC 3768.
Open Problem Reports and Feature Exceptions PR 57836 The policy service group is broken by using "source ip port" with "destination ip port" on an OS7000 series switch. Workaround: There is no known workaround at this time. Service groups can contain either: 1. All source port conditions. 2. All destination port conditions. 3. All source+destination port conditions. PR 57932 ARP packets are not classified by QoS with NAT on an OS7000 series switch. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 61072 Simple NAT rules, on an OS7000 series switch that have conditions whose IP address/subnet overlaps with switch addresses, will match traffic sent from these addresses even if the traffic is bridged. Workaround: Along with the generic NAT rule, a higher precedence, non-NAT rule must be added to match traffic from the switch addresses that overlap with the generic NAT rule. For instance, if you wanted to remap the subnet 124.10.10/24 to 60.0.0.
Open Problem Reports and Feature Exceptions PR 65449 Reflexive policies, on an OS7000 series switch, do not work properly if the drop rule that denies the "reverse" traffic coming from the outside is created first, or has a higher precedence. With qos default routed disposition drop, it works fine. Example Inside Network 10.0.0.0 -- SWITCH -- Outside Network 192.0.0.0 policy condition cOut source ip 192.0.0.
Open Problem Reports and Feature Exceptions PR 67882 The show qos queue command does not display Xmit or Drop Packets for any port queue on an OS6624/ 6648 switch. Workaround: There is no known workaround at this time. PR 68472 OS6624 and OS6648 switches do not prioritize traffic on saturated half-duplex links, possibly allowing data traffic through the phone to cause drops of voice traffic or signaling to the PCX.
Open Problem Reports and Feature Exceptions PR 73767 On an OS7000/8800 switch, when setting a permanent MAC address to filtering, traffic going to this MAC will always be dropped regardless of the QoS rules (even if one permit rule matches this MAC). When setting a permanent MAC address to bridging, traffic going to this MAC will always be accepted at best effort, regardless of the QoS rules.
Open Problem Reports and Feature Exceptions PR 84425 The Drop rule is still enforced when the source MAC or source VLAN is changed in a secure switch access condition on an OS6600 series switch. Workaround: There is no known workaround at this time. PR 90119 On an OS7000 series switch, Ethertype based conditions will only affect Ethernet II encapsulated packets. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions Advanced Routing OS7000/8800 Feature Exceptions • The maximum number of total routes is 65K. • The maximum number of RIP routes is 10K. • The maximum number of OSPF routes is 40K. • The maximum number of BGP routes is 65K. • The maximum number of active traffic flows is 16K (based on the current default cache allocation). OS6600 Feature Exceptions • The max number of total routes is 4K. • The max number of RIP routes is 2K. • The max number of OSPF routes is 4K.
Open Problem Reports and Feature Exceptions DVMRP Problem Reports PR 56990 Tunnel destined flows are not displayed in the show ip multicast forwarding CLI command on an OS7000 series switch. There is simply no room left on the line to display. Workaround: Use the show ip mroute-next-hop CLI command instead, to display tunnel endpoint information.
Open Problem Reports and Feature Exceptions PR 80757 Only a single client on a given port for a given multicast group is shown in the group membership, displays on an OS6600/OS7000 switch. Workaround: This is a result of the way IGMP clients respond to group membership queries. Only a single client will respond in a flooded environment where all clients will see the report.
Open Problem Reports and Feature Exceptions PR 69890 OSPF virtual links will not form an adjacency with gateD switches if MD5 is configured on an OS6600/ OS7000 series switch. Workaround: The MD5 key id for OSPF virtual links is hardcoded to 1. Any switch that uses gateD and MD5 is configured on the virtual link requires that key id is coded accordingly. In this gateD example for an OmniSwitch Router, the ID is set to 1: ospf yes backbone { interface 212.1.1.
Open Problem Reports and Feature Exceptions PR 90742 On the OS6600 series, OSPF ECMP gateways are not correctly computed when there is more than one point-to-point or point-to-multipoint interface between a pair of OSPF routers. Workaround: There is no known workaround at this time. PIM-SM Problem Reports PR 73783 On an OS7000 series switch, a lot of register packets will stress the NI. Everything is going through software and so the NI will be very busy.
Open Problem Reports and Feature Exceptions PR 74881 When a Cisco router is acting as the DR (Designated Router) with spt-switchover enabled, the Cisco router may erroneously send (S,G) prunes to the OmniSwitch 7700/7800’s causing the multicast streams to be disrupted. This seems to be the case when the route to the RP is the same as the route to the source. Workaround: Disable spt-switchover on the Cisco.
Open Problem Reports and Feature Exceptions Security Feature Exceptions • The Mac OS X 10.3.x is supported for AVLAN web authentication using JVM-v1.4.2 General Problem Reports PR 89262 On an OS7000 series switch, NESSUS reports bogus "Vulnerabilities". Basically, NESSUS collects all those known attacks/vulnerablities into their test suites. For Example, NESSUS sends: http:///cgi/bin/guestbook.
Open Problem Reports and Feature Exceptions PR 90855 The no aaa authentication 802.1x CLI command does not work properly. Workaround: Put onex port in the Force Authorized mode first before executing the command. PR 92093 When using the XP service pack 2 native 802.1x client and some version of Steelbelted RADIUS, the XP 802.1x client will not always be able to "successfully" authenticate. Workaround: Use pure XP without any service pack or with Steel-belted RADIUS Service Provider Edition 4.70.661.
Open Problem Reports and Feature Exceptions Authenticated Switch Access PR 59686 If a user kills an HTTP session, the table still displays the session when it automatically refreshes. Workaround: The user must hit the refresh button again, and the table will not display the session. This problem ONLY occurs with a HTTP session. Telnet and FTP sessions are removed from the table properly. PR 63104 During a takeover, switch management sessions (HTTP, FTP, and Telnet) are closed on an OS7000 series switch.
Open Problem Reports and Feature Exceptions PR 58192 If an LDAP server is configured in SSL mode on an OS7000 series switch with a TCP port value equal to a non-SSL port configured on the LDAP server side, then LDAP communication is not possible between the switch and the server. Some resources may remain unfreed in the switch. Workaround: When configuring the SSL port, port numbers are the same on both sides.
Open Problem Reports and Feature Exceptions PR 76820 On an OS6624/6648 switch, when the user configures the IP helper on the second hop, the PC will not be able to get the IP address after authentication. AOS appears not to be able to learn the MAC, when in fact the PC never gets the IP address, and thus there is no traffic from the PC. Workaround: Configure IP helper on the first hop.
Open Problem Reports and Feature Exceptions Policy Server Management Problem Reports PR 63005 The LDAP client architecture does not take advantage of the referral service on the LDAP server on an OS7000 series switch. Workaround: There is no known workaround at this time. PR 74062 On an OS6624/6648 switch, it is not possible to create a L3 ACL on a source network, and another on a destination network, because currently an OS6600 series switch cannot link up the source and destination.
Open Problem Reports and Feature Exceptions System General Problem Reports PR 51067 A Switch based telnet client only supports a single user at a time on an OS7000 series switch. If one user already has started using the telnet client, and a second user attempts to use the switch based telnet client at the same time, a message is generated informing the second user that the client is already in use. The actual message sent is: "Telnet is already in use.
Open Problem Reports and Feature Exceptions PR 60142 When priority 2 and priority 3 traffic is sent at wire rate on all 384 ports of a switch, 40 percent of the traffic is dropped. Workaround: Configure the network applications and the switch QoS parameters so that only the highest priority traffic is sent at priority 3 through the switch. PR 60599 The watch dog does not reboot the switch when the OS7000 locks up, due to a corrupt image file.
Open Problem Reports and Feature Exceptions PR 62067 The Port link may toggle if using a Media Converter (100BASE-TX to 100BASE-FX) on an OS7000 series switch. Workaround: There is no known workaround at this time. PR 63605 Some Fweb* images show up in the "loaded m-code" table before an OS7000 series switch reloads. Workaround: When a switch comes up, the only file that WebView loads is the web.lnk file from Fweb.img. If there is no web access to the switch, nothing else is loaded.
Open Problem Reports and Feature Exceptions PR 67889 IXIA Scriptmate automates auto-negotiation test. Hence, the timing for enabling port (PHY and MAC) between IXIA and an OS8800 switch is different. Since the OS8800 switch does not accumulate statistics before the port is enabled, there is a chance to have statistics mismatch between IXIA and the switch. Workaround: There is no known workaround at this time. PR 68905 ColdStartTrap is sent every time a switch is reset.
Open Problem Reports and Feature Exceptions PR 75615 On an OS6600 series switch, a "continuous Flash synchro" process may occur if the local "working" and "certified" directories are not "certified". Workaround: When any stacks are required to be connected to other stacks, make sure the individual stacks are synchronized between themselves locally (Working and Certified) and within each module of the current stack environment.
Open Problem Reports and Feature Exceptions PR 83669 The chassis will not be able to bootup when the boot flag is set to 0xb8000 on an OS7000 series switch. Workaround: Do not set the boot flag to 0xb8000. PR 84294 The show running-directory command shows Running Configuration as Not Available on an OS6600 series switch. Workaround: This is a display issue only. PR 84601 On an OS7000 series switch, daylight savings time is not accommodated in several time zones. NTP synchronization is off by one hour.
Open Problem Reports and Feature Exceptions PR 91482 On an OS6600 series switch, when max bandwidth rules with either destination ip, source ip, or source network group are applied and modified, we may run into no free BDs issue. Workaround: There is no known workaround at this time. PR 91691 Upgrading the OS8800 FPGA can fail due to insufficient flash space if the user has added files to the flash. Workaround: Upgrade the FPGA via 5.1.5.R04 release or remove all files except those on the original 5.1.6.
Open Problem Reports and Feature Exceptions OmniSwitch 6600 NIs Problem Reports PR 90972 The displayed field "coper" is just a typo of the word "copper" on an OS6600 series switch. Workaround: There is no known workaround at this time. OmniSwitch 7000 NIs Problem Reports PR 34227 Only 32K address seen bits are available to support aging out of the pseudoCAM entries. Workaround: There is no known workaround at this time. PR 35050 Jumbo frames cannot be fragmented when bridged.
Open Problem Reports and Feature Exceptions PR 65197 The qos default queues command may cause the NI to have a different configuration than the CMM. Workaround: The qos default queues command requires a reset of the NI before it takes effect. One can reset the NI by executing the no power ni command, and then the power ni command. One can also execute the reload working no roll-back for the setting to take effect.
Open Problem Reports and Feature Exceptions PR 80710 OS7-ENI-P24 modules have egress flood rates lower than the regular OS7-ENI-C24 modules. Workaround: There is no known workaround at this time. OmniSwitch 8800 NIs OmniSwitch 8800 Feature Exceptions • When a chassis is fully loaded with 5 SFM modules, an Amber light indicates that the module is in the Stand-By mode. Problem Reports PR 66750 The maximum aggregate throughput for an OS8-ENI-C24 (10/100) is 2.0 gigabits/sec.
Open Problem Reports and Feature Exceptions PR 80442 An error message “No Such Object available on this agent” is returned for 10G specific tables. This problem only occurs with the SNMP walk application. Workaround: There is no known workaround at this time. PR 81010 An OS8-GNI-C24 may encounter some packet loss for small size packets if it is wired traffic (100% traffic inflow). Workaround: This is an oversubscription condition. Lower the incoming traffic rate.
Open Problem Reports and Feature Exceptions Redundancy / Hot Swap CMM Redundancy Feature Exceptions for OmniSwitch 7000/8800 • Manual invocation of failover (by user command or Primary pull) should only be done during times when traffic loads are minimal. • Hot standby redundancy or failover to a secondary OS7000/8800 CMM without significant loss of traf- fic is only supported if the secondary is fully flash synchronized with the contents of the primary’s flash.
Open Problem Reports and Feature Exceptions CMM Redundancy / Hot Swap Feature Exceptions • If you do a write memory, and do not do a certify (copy working certified) before doing a takeover or reload primary, you will lose the boot.cfg contents because the secondary will do an automatic restore (copy certified working) when it comes up as the secondary. This allows it to be ready for failovers.
Open Problem Reports and Feature Exceptions PR 67483 The copy flash-synchro command will not work between different release versions of code. Workaround: Both CMMs must have the same release version. If not, do the following: 1. Load each CMM separately with the new release in the "working" directory. When doing this, only one CMM should be plugged into the chassis. 2. Perform reload working no roll-back on each CMM. 3. On each CMM, perform copy working certified. 4. Bring up the chassis with both CMMs. 5.
Open Problem Reports and Feature Exceptions PR 77206 On an OS7000 series switch, during a takeover or failover, due to the IP Stack transition, some of the messages may not be able to log to a remote device if one enables the syslog mechanism. This period may be in the boundary of a second. Workaround: There is no known workaround at this time. PR 79063 Flash Synchronization is successful, but show running shows CMMs NOT SYNC when a new folder is created in /working on an OS7000 series switch.
Open Problem Reports and Feature Exceptions PR 87051 Reload prompt overrides all other session responses on an OS7000 series switch. Workaround: Prior to issuing reload or reboot, ensure all sessions are closed. Use the kill command to remove other sessions. Do not issue reload or reboot prompt without fully committed to action. PR 90540 On an OS8800 switch, after a takeover, a 10G port will not display on the CMM side. Workaround: There are no interruptions on traffic flows.
Technical Support Technical Support Alcatel technical support is committed to resolving our customer’s technical issues in a timely manner. Customers with inquiries should contact us at: Region Phone Number North America 800-995-2696 Latin America 877-919-9526 Europe +33-388-55-69-04 Asia Pacific +65-394-7933 Other International 818-878-4507 Email: support@ind.alcatel.
