Release Notes OmniSwitch 6800/6850/9000 Release 6.1.3.R01 These release notes accompany release 6.1.3.R01 software for the OmniSwitch 6800, 6850, and 9000 hardware. They provide important information on individual software features and hardware modules. Since much of the information in these release notes is not included in the hardware and software user manuals, it is important that you read all sections of this document before installing new hardware or loading new software.
Related Documentation Related Documentation These release notes should be used in conjunction with the OmniSwitch 6800, 6850, and 9000. The following are the titles and descriptions of the user manuals that apply to the OmniSwitch 6800, 6850, and 9000. Note. User manuals can be downloaded at http://www.alcatel.com/enterprise/en/resource_library/ user_manuals.html.
Related Documentation • OmniSwitch 6800/6850/9000 Series Advanced Routing Configuration Guide Includes network configuration procedures and descriptive information on all the software features and protocols included in the advanced routing software package. Chapters cover multicast routing (DVMRP and PIM), BGP, OSPF, and OSPFv3. • Upgrade Instructions for 6.1.3.R01 Provides instructions for upgrading the OmniSwitch 6800, 6850, 9000 to 6.1.3.R01.
System Requirements System Requirements Memory Requirements • OmniSwitch 6800 Series Release 6.1.3.R01 requires 256 MB of SDRAM and 64MB of flash memory. This is the standard configuration shipped. • OmniSwitch 6850 Series Release 6.1.3.R01 requires 256 MB of SDRAM and 64MB of flash memory. This is the standard configuration shipped. • OmniSwitch 9000 Series Release 6.1.3.R01 requires 256 MB of SDRAM and 128MB of flash memory. This is the standard configuration shipped.
New Hardware Supported New Hardware Supported The following new hardware is supported subject to the feature exceptions and problem reports described later in these release notes. New Chassis The following new OmniSwitch 6850 Series chassis are available in this release. Note. The USB port on the OmniSwitch 6850 Series units is not supported in this release.
New Hardware Supported supports a maximum of four power supplies and up to 384 10/100/1000 copper ports and/or 1000 Mbps fiber ports. It is suitable for wiring closet installations. It can also be equipped with up to 96 10 Gigabit Ethernet ports for use as the core switch. Note. OmniSwitch 9700 NI modules and OmniSwitch 7700 NI modules should not be mixed in the same chassis. See the OmniSwitch 9000 Series Hardware Users Guide for more information on OmniSwitch 9000 hardware features.
New Hardware Supported New Power over Ethernet Components/Enhancements OmniSwitch 9000 OS-IP-SHELF PoE Power Shelf The OS-IP-SHELF unit is the peripheral power shelf for the chassis that provides the electrical current used for PoE ports. Up to four 600W OS-IP-SHELF specific power supply modules are available. These are load sharing modules that can provide up to a maximum of 2400W PoE power source.
New Hardware Supported 100FX Ethernet Transceivers SFP-100-BX20LT - 100Base-BX SFP transceiver with an SC type interface. This bi-directional transceiver is designed for use over single mode fiber optic on a single strand link up to 20KM point-to-point. This transceiver is normally used in the central office (OLT) transmits 1550nm and receives 1310nm optical signal. SFP-100-BX20NU - 100Base-BX SFP transceiver with an SC type interface.
Supported Hardware/Software Combinations Supported Hardware/Software Combinations The following table shows the 6.1 software releases that support each of the listed OS9000, OS6850, and OS6800 module types: Module Type Part Number 6.1.1.R01 6.1.1.R02 6.1.2.R03 6.1.3.
Supported Hardware/Software Combinations To determine the ASIC revision for a specific NI, use the show ni command.
New Software Features New Software Features The following software features and/or the platforms they are supported on are new with the 6.1.3.R01 release, subject to the feature exceptions and problem reports described later in these release notes: Feature Summary Feature Platform Software Package 802.1Q 2005 (MSTP) all base 802.1W (RSTP) Default all base 802.
New Software Features Feature Platform Software Package VLAN Range Support all base VLAN Stacking and Translation OS6850/OS9000 base VRRPv3 OS6850/OS9000 base page 12 OmniSwitch 6800/6850/9000—Release 6.1.3.
Software Supported Software Supported In addition to the new software features introduced with the 6.1.3.R01 release, the following software features are also supported in 6.1.3.R01, subject to the feature exceptions and problem reports described later in these release notes: Feature Summary Feature Platform Software Package 802.1Q all base 802.1d/1w Spanning Tree all base 802.1x Multiple Client Support all base 802.
Software Supported Feature Platform Software Package IPv6 (NPD) all base IPX Routing all base Learned Port Security (LPS) all base Link Aggregation (static & 802.
Software Supported Feature Platform Software Package Text File Configuration all base User Definable Loopback Interface all base VLANs all base VRRP all base Web-Based Management (WebView) all base Feature Descriptions 802.1Q Alcatel-Lucent’s 802.1Q is an IEEE standard for sending frames through the network tagged with VLAN identification. 802.1Q tagging is the IEEE version of VLANs. It is a method of segregating areas of a network into distinct VLANs.
Software Supported Access Control Lists (ACLs) Access Control Lists (ACLs) are Quality of Service (QoS) policies used to control whether or not packets are allowed or denied at the switch or router interface. ACLs are sometimes referred to as filtering lists. ACLs are distinguished by the kind of traffic they filter. In a QoS policy rule, the type of traffic is specified in the policy condition. The policy action determines whether the traffic is allowed or denied.
Software Supported • TCP connection rules—Allows the determination of an established TCP connection by examining TCP flags found in the TCP header of the packet. Two condition parameters are available for defining a TCP connection ACL: established and tcpflags. • Early ARP discard—ARP packets destined for other hosts are discarded to reduce processing over- head and exposure to ARP DoS attacks. No configuration is required to use this feature, it is always available and active on the switch.
Software Supported Authenticated Switch Access Authenticated Switch Access (ASA) is a way of authenticating users who want to manage the switch. With authenticated access, all switch login attempts using the console or modem port, Telnet, FTP, SNMP, or HTTP require authentication via the local user database or via a third-party server. The type of server may be an authentication-only mechanism or an authentication, authorization, and accounting (AAA) mechanism.
Software Supported Basic IPv4 Routing Internet Protocol (IP) is a network-layer (Layer 3) protocol that contains addressing and control information that allow packets to be forwarded on a network. IP is the primary network-layer protocol in the Internet protocol suite. Along with the Transmission Control Protocol (TCP), IP represents the heart of the Internet protocols. IP is associated with several Layer 3 and Layer 4 protocols.
Software Supported BPDU Shutdown Ports It is possible to configure a global UserPorts profile, as described in “ACL & Layer 3 Security”, to monitor BPDU on user ports. Such a profile also determines whether user ports will filter BPDU or will administratively shutdown when BPDU are received on the port. Note that this functionality only applies to ports that are designated as members of the UserPorts port group.
Software Supported • Traffic Suppression—Prevents the flooding of DHCP packets on the default VLAN for a DHCP Snooping port. Note that enabling traffic suppression on a port will prevent DHCP traffic between a DHCP server and client that belong to the same VLAN domain. • IP Source Filtering—Restricts DHCP Snooping port traffic to only packets that contain the client source MAC address and IP address obtained from the DHCP lease information.
Software Supported Ethernet Interfaces Ethernet and Gigabit Ethernet port software is responsible for a variety of functions that support Ethernet, Gigabit, and 10 Gigabit Ethernet ports. These functions include initialization of ports, notifying other software modules when a port goes down, configuration of basic line parameters, gathering of statistics for Ethernet and Gigabit Ethernet ports, and responding to administrative enable/disable requests.
Software Supported Interswitch Protocol (AMAP) Alcatel-Lucent Interswitch Protocols (AIP) are used to discover adjacent switches and retain mobile port information across switches. By default, AMAP is enabled. Alcatel-Lucent Mapping Adjacency Protocol (AMAP) is used to discover the network topology of Alcatel-Lucent switches in a particular installation. Using this protocol, each switch determines which switches are adjacent to it by sending and responding to Hello update packets.
Software Supported IP Multicast Switching (IPMS) - Proxying IP multicast proxying and configuring the IGMP and MLD unsolicited report interval are now available with this implementation of IPMS. Proxying enables the aggregation of IGMP and MLD group membership information and the reduction in reporting queriers. The unsolicited report interval refers to the time period in which to proxy any changed IGMP membership state. The 6.1.3.
Software Supported IPX Routing The Internet Packet Exchange (IPX) protocol, developed by Novell for NetWare, is a Layer 3 protocol used to route packets through IPX networks. (NetWare is Novell’s network server operating system.) This implementation of IPX routing is software based with limited performance. IPX specifies a connectionless datagram similar to the IP packet of TCP/IP networks. An IPX network address consists of two parts: a network number and a node number.
Software Supported Learned Port Security (LPS) Learned Port Security (LPS) provides a mechanism for authorizing source learning of MAC addresses on 10/100/1000, Gigabit, and Gigabit Ethernet ports. Using LPS to control source MAC address learning provides the following benefits: • A configurable source learning time limit that applies to all LPS ports. • A configurable limit on the number of MAC addresses allowed on an LPS port. • Dynamic configuration of a list of authorized source MAC addresses.
Software Supported Multicast boundaries confine scoped multicast addresses to a particular domain. Confining scoped addresses helps to ensure that multicast traffic passed within a multicast domain does not conflict with multicast users outside the domain. PIM PIM-SSM Protocol-Independent Multicast (PIM) is an IP multicast routing protocol that uses routing information provided by unicast routing protocols, such as RIP and OSPF.
Software Supported Partitioned Switch Management A user account includes a login name, password, and user privileges. The privileges determine whether the user has read or write access to the switch, and which command domains and command families the user is authorized to execute on the switch. The privileges are sometimes referred to as authorization; the designation of particular command families or domains for user access is sometimes referred to as partitioned management.
Software Supported Port Mapping Port Mapping is a security feature that controls peer users from communicating with each other. A Port Mapping session comprises a session ID and a set of user ports and/or a set of network ports. User ports within a session cannot communicate with each other and can only communicate via network ports. In a Port Mapping session with user port set A and network port set B, ports in set A can only communicate with ports in set B.
Software Supported QoS is implemented on the switch through the use of policies, created on the switch or stored in PolicyView. While policies may be used in many different types of network scenarios, there are several typical types: • Basic QoS—includes traffic prioritization and bandwidth shaping • 802.
Software Supported Secure Copy (SCP) The scp CLI command is now available for copying files in a secure manner between hosts on the network. The scp utility performs encrypted data transfers using the Secure Shell (SSH) protocol. In addition, scp uses available SSH authentication and security features, such as prompting for a password if one is required.
Software Supported Server Load Balancing (SLB) Alcatel’s Server Load Balancing (SLB) software provides a method to logically manage a group of physical servers sharing the same content (known as a server farm) as one large virtual server (known as an SLB cluster). SLB clusters are identified and accessed at Layer 3 by the use of Virtual IP (VIP) addresses or a QoS policy condition.
Software Supported The switch fabric on the CMM operates independently of the management processor. If there are two CMM modules installed in an OS9700, both fabric modules are normally active. Two CMM modules must be installed in the OS9700 to provide full fabric capacity. However, note that only the one CMM module in the OS9600 provides full fabric capacity.
Software Supported Once the contents of the working directory are established as good files, then these files can be saved to the certified directory and used as the most reliable software to which the switch can be rolled back to in an emergency situation. Spanning Tree In addition to the Q2005 version of MSTP, the Alcatel Spanning Tree implementation also provides support for the 802.1w Rapid Spanning Tree Algorithm and Protocol (RSTP) and the 802.1D Spanning Tree Algorithm and Protocol (STP).
Software Supported User Definable Loopback Interface Loopback0 is the name assigned to an IP interface to identify a consistent address for network management purposes. The Loopback0 interface is not bound to any VLAN, therefore it always remains operationally active. This differs from other IP interfaces, such that if there are no active ports in the VLAN, all IP interfaces associated with that VLAN are not active.
Software Supported Web-Based Management (WebView) The switch can be monitored and configured using WebView, Alcatel-Lucent’s web-based device management tool. The WebView application is embedded in the switch and is accessible via the following web browsers: • Internet Explorer 6.0 and later for Windows NT, 2000, XP, 2003 • Netscape 7.1 for Windows NT, 2000, XP • Netscape 7.0 for Solaris SunOS 5.8 WebView contains modules for configuring all software features in the switch.
Supported Traps Supported Traps The following traps are supported in 6.1.3.R01: No. Trap Name Platforms Description 0 coldStart all The SNMP agent in the switch is reinitiating and its configuration may have been altered. 1 warmStart all The SNMP agent in the switch is reinitiating itself and its configuration is unaltered. 2 linkDown all The SNMP agent in the switch recognizes a failure in one of the communications links configured for the switch.
Supported Traps No. Trap Name Platforms Description 17 healthMonPortTrap all Indicates a port-level threshold was crossed. 18 bgpEstablished all The BGP routing protocol has entered the established state. 19 bgpBackwardTransition all This trap is generated when the BGP router port has moved from a more active to a less active state. 20 esmDrvTrapDropsLink all This trap is sent when the Ethernet code drops the link because of excessive errors.
Supported Traps No. Trap Name Platforms Description 26 stpNewRoot all Sent by a bridge that became the new root of the spanning tree. 27 stpRootPortChange all A root port has changed for a spanning tree bridge. The root port is the port that offers the lowest cost path from this bridge to the root bridge. 28 mirrorConfigError all The mirroring configuration failed on an NI. This trap is sent when any NI fails to configure mirroring. Due to this error, port mirroring session will be terminated.
Supported Traps No. Trap Name Platforms Description 44 unused — 45 unused — 46 unused — 47 pethPsePortOnOff — Indicates if power inline port is or is not delivering power to the a power inline device. 48 pethPsePortPowerMaintenanceStatus — Indicates the status of the power maintenance signature for inline power. 49 pethMainPowerUsageOn — Indicates that the power inline usage is above the threshold.
Supported Traps No. Trap Name Platforms Description 59 gmHwVlanRuleTableOverloadAlert all An overload trap occurs whenever a new entry to the hardware VLAN rule table gets dropped due to the overload of the table. 60 lnkaggAggUp all Indicates the link aggregate is active. This trap is sent when any one port of the link aggregate group goes into the attached state. 61 lnkaggAggDown all Indicates the link aggregate is not active.
Unsupported Software Features Unsupported Software Features CLI commands and Web Management options maybe available in the switch software for the following features. These features are not supported: Feature Platform Software Package OSPF Database Overflow (RFC 1765) all base Flow Control 802.
Unsupported CLI Commands Software Feature Unsupported CLI Commands RIP ip rip redist status ip rip redist ip rip redist metric ip rip redist-filter ip rip redist-filter effect ip rip redist-filter metric ip rip redist-filter route-tag ip rip redist-filter redist-control VLANs vlan router mac multiple enable|disable vlan binding mac-port-protocol vlan binding mac-ip vlan binding ip-port Chassis Supervision show fabric OmniSwitch 6800/6850/9000—Release 6.1.3.
Unsupported MIBs Unsupported MIBs The following MIBs are not supported in this release of the software: MIB Feature Quality of Service (QoS) IETF_P_BRIDGE Flow Control AlcatelIND1Port Unsupported MIB Variables MIB Name Unsupported MIB variables AlcatelIND1AAA aaauProfile AlcatelIND1Bgp alaBgpGlobal alaBgpPeerTable alaBgpAggrTable alaBgpNetworkTable alaBgpRedistRouteTable alaBgpRouteTable alaBgpPathTable alaBgpDampTable alaBgpRouteMapTable alaBgpAspathMatchListTable alaBgpAspathPriMatchListTable a
Unsupported MIBs MIB Name Unsupported MIB variables AlcatelIND1QoS alaQoSPortPdiTable alaQoSSlotPcamTable alaQoSPortProtocolTable alaQoSSlotProtocolTable alaQoSSlotDscpTable alaQoSRuleReflexive alaQoSAppliedRuleReflexive alaQoSActionSourceRewriteIpAddr alaQoSActionSourceRewriteIpAddrStatus alaQoSActionSourceRewriteIpMask alaQoSActionTable alaQoSActionSourceRewriteNetworkGroup alaQoSActionTable alaQoSActionSourceRewriteNetworkGroupStatus alaQoSActionTable alaQoSActionDestinationRewriteIpAddr alaQoSAction
Unsupported MIBs MIB Name Unsupported MIB variables AlcatelIND1VlanManager vlanIpxNet vlanIpxEncap vlanIpxRipSapMode vlanIpxDelayTicks vlanSetMultiRtrMacStatus AlcatelIND1WebMgt alaIND1WebMgtRFSConfigTable alaIND1WebMgtHttpPort alaIND1WebMgtHttpsPort IEEE_802_1X dot1xAuthDiagTable dot1xAuthSessionStatsTable dot1xSuppConfigTable dot1xSuppStatsTable IETF_BGP4 bgpRcvdPathAttrTable bgp bgpPeerTable bgp4PathAttrTabl IETF_BRIDGE dot1dTpPortTable dot1dStaticTable IETF_ENTITY entLogicalTable entLPMapp
Unsupported MIBs MIB Name Unsupported MIB variables IETF_P_BRIDGE dot1dExtBase dot1dPortCapabilitiesTable dot1dPortPriorityTable dot1dUserPriorityRegenTable dot1dTrafficClassTable dot1dPortOutboundAccessPriorityTable dot1dPortGarpTable dot1dPortGmrpTable dot1dTpHCPortTable dot1dTpPortOverflowTable IETF_Q_BRIDGE (RFC 2674) dot1qTpGroupTable dot1qForwardAllTable dot1qForwardUnregisteredTable dot1qStaticMulticastTable dot1qPortVlanStatisticsTable dot1qPortVlanHCStatisticsTable dot1qLearningConstraintsTab
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 106811 Show interface slot/port "SFP/XFP" field output for a port having SFP plugged in cannot differentiate between 100Fx and Bidirectional SFP & between Gig and CWDM SFP on an OS6850. Workaround: There is no known workaround at this time. RMON Problem Reports PR 87683 On an OS6800/OS9000, the RMON object etherStatsPkts65to127Octs and other similar objects from RFC 1757 contain TX and RX packet counts. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 107462 Sflow Datagrams do not use the EMP port on a OS9000 for IPV4 packets. Workaround: Use the ports on the slots. SNMP Problem Reports PR 82635 On an OS9000, there is no display of the number or the status of fan modules on an OmniSwitch via SNMP or WebView. Workaround: The number and status of fans can be displayed via the CLI show fan command only. PR 105290 SNMP and the WebView DVMRP --> Routes page does not display Route Flags.
Open Problem Reports and Feature Exceptions PR 89084 For Partition Management, giving a user routing protocols permission, but no IP permission results in some table data not being displayed in the routing pages. Workaround: Make sure a user gets permission for IP if the user is allowed to view any sort of IP routing protocol pages. PR 96146 When viewing XOS adjacencies with multiple (2 or more) XoS devices connected to an OS9800 using AOS WebView, will return unknown devices with build 4.4.4.188.
Open Problem Reports and Feature Exceptions PR 100607 Accessing WebView > Security > Servers using Netscape, a window may appear asking for user name selection on an OS6850 when adding a new server. Workaround: Close the window and ignore. This window shown is not a WebView pop-up window but a Netscape Form Manager window -- perhaps triggered by the "Server Name" label in the server add windows and being treated as if it was a regular form asking for a user name.
Open Problem Reports and Feature Exceptions PR 107284 Supplicant and non-supplicant are not displayed together on the same front page for 802.1x on an OS6850. Workaround: View the non-supplicants on a different page - 802.1x non supplicant page. Display Issue Only. PR 107315 A duplicate slot in a stack of switches will not display the switch picture in the WebView > Chassis Mgmt > Chassis homepage. Workaround: Remove the duplicate slot.
Open Problem Reports and Feature Exceptions Bridging Problem Reports PR 86261 On an OS6800, Ethernet SNAP packets with non-zero Organizationally Unique Identifiers (OUI) will not be classified using port-protocol rule. Workaround: If applicable, other rules should be used to classify such packets. PR 94269 The OmniSwitch 9000 counts all error packets as unicast packets in the packets received and error counters, regardless of whether the packet is a unicast packet or a multicast packet.
Open Problem Reports and Feature Exceptions Ethernet Interfaces Problem Reports PR 93114 It is not possible to broadcast or multicast oversized ingress packets. Therefore, ingressing oversized layer 2 multicast packets are treated as unicast packets. Workaround: There is no known workaround at this time. PR 94866 Invalid packets with SA or DA set to all 0s continue to be bridged by system. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 105789 The ifMauTable returns object with out of range values for 10 Gig ports on an OS9000. A get call to IETF_MAU MIB ifMauAutoNegSupported object returns a value of 0 (zero) for 10 Gig ports. Value 0 (zero) is out of range because only two values 1 (Autoneg supported) and 2 (Autoneg not supported) are part of this object. Workaround: There is no known workaround at this time. PR 105847 On OS6850-U24x board combo ports with default media preference (i.e.
Open Problem Reports and Feature Exceptions Group Mobility Problem Reports PR 98417 When a MAC is learned on an OS6850 as "Filtered" for one port due to a Group Mobility rule violation, and if the MAC reappears on another port, it will not be updated. The MAC will not be shown as filtered for the new port, but will continue to show filtered in the old port. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 99269 An IGMPv3 or MLDv2 membership report with an exclude filter containing 0.0.0.0 or :: in the source list will potentially disrupt IP Multicast Switching and Routing for the particular group membership being reported. Workaround: Neither 0.0.0.0 or :: are valid source addresses. They should not be used in source filters.
Open Problem Reports and Feature Exceptions Source Learning Problem Reports PR 83087 On an OS6800/OS9000, the MAC aging time can take up to twice the configured value. Workaround: There is no known workaround at this time. PR 94127 On an OS9000, in the Hardware learning mode, the source MACs from control packets (BPDUs) are learned. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 95322 On an OS9000, duplicate MAC is not learned as the "filtered" mode, if the entry has already been configured as a permanent entry on a different port. The side effect is that the packet with this MAC from a different port would still be forwarded or flooded. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 100932 Removing the last member port of a linkAggr while traffic is running can result in MAC addresses learned on that port in the default VLAN of the linkAggr. Workaround: Administratively down all ports that transmit across the linkAgg or link down/up the port after removing it from the linkAggr.
Open Problem Reports and Feature Exceptions PR 107231 A stack of 3 OS6850's (slots 1 & 2 are 48 ports and slot 3 is 24 ports) with a mobile port of 1/35 (Second Asic on Slot 1) and a binding mobile rule. A MAC violating is programmed as filtered. Now, this filtered MAC is programmed on all slots. However, since there is only one ASIC on Slot 3, there is an error and the address is not programmed as filtered on slot 3. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions Workaround: For items 1 and 2 above, there is no known workaround at this time. For item 3, the following workarounds could be applied: 1. Tune the max age (and or max hops in the case of MSTP) parameter to a lower value that is optimal for the network. This will reduce the convergence time and thereby the duration of temporary loops. 2.
Open Problem Reports and Feature Exceptions PR 105788 Some STP entries in the 802.1D standard mib may return out of range or undefined values on an OS9000. This is because we are returning the true values of a newer version of STP (802.1Q 2005), not 802.1D 1998 that the MIB is based on. When a new standard MIB is defined, we can obsolete the old version. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions Layer 3 Basic IP Routing Problem Reports PR 94621 In most cases, routed packets needing fragmentation due to a smaller IP MTU on the egress network will not be fragmented and will be forwarded as-is. Workaround: There is no known workaround at this time. PR 106913 On OS6800 and OS6850, exceeding 20K routes in the FIB can cause system instability, especially if they are all on the same VLAN.
Open Problem Reports and Feature Exceptions PR 106814 When DHCP Snooping is enabled against mobile port, sometimes the mobile port's VLAN ownership is not reflected in the DHCP Snooping port table. Workaround: There is no known workaround at this time. PR 106977 When DHCP Snooping is enabled, binding entry is not created against the new root port when STP topology is changed. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 96061 On an OS6850/OS9000, the IPv6 implementation does not follow ICMPv6 RFC 2463 section 2.2 Message Source Address Determination in regard to anycast addresses. Instead IPv6 uses any unicast address configured on the switch. Workaround: A node that sends an ICMPv6 message has to determine both the source and destination IPv6 addresses in the IPv6 header before calculating the checksum.
Open Problem Reports and Feature Exceptions PR 106213 When using "configuration apply" to apply routing configuration to an OS6850 system that has completed its boot up, parts of the configuration may fail with a "system busy" error. Workaround: 1) Ensure that the protocol is manually loaded prior to applying the configuration file. For example, > ipv6 load ospf > configuration apply ospf3.asc.
Open Problem Reports and Feature Exceptions PR 106942 On OS9000, statistic display of ip-helper (DHCP) and Generic UDP relay are mixed together, but complete statistical information is present. Workaround: There is no known workaround at this time. PR 107204 If the user defines a UDP service and does not assign a VLAN to that service, the service does not show up on the Webview display but does appear when using the CLI to display services. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions DVMRP Problem Reports PR 100130 On an OS6800, when interfaces from two different routers that are physically attached to the same network are changed from native DVMRP interfaces to DVMRP tunnel interface on-the-fly or vice versa, the multicast traffic will stop being routed across this path. Workaround: Disable DVMRP before making the change, and then re-enable it again.
Open Problem Reports and Feature Exceptions PR 105491 Existing inter-area-prefix and inter-area-router LSAs are not originated into areas that are created after initial convergence of the network on an OS9000. For example, the router is running and it originates a set of inter-area-prefix or inter-area-router LSAs into all known areas.
Open Problem Reports and Feature Exceptions PR 106343 High multicast traffic rate on an OS6850 running PIM-SM where the RP is on a remote switch may cause high CPU utilization. This is due to the packets being PIM register-encapsulated which are software routed. The high data rate is causing the Register Stop packets to be dropped. Once the Register Stop packets are received, the register-encapsulation will stop and native forwarding will take over.
Open Problem Reports and Feature Exceptions PR 107232 On OS9000, if a condition is associated with an SLB cluster and a policy rule, it can be deleted in a flush. Workaround: Create separate conditions for SLB and policy rules. Policy Manager Problem Reports PR 94083 Policies, which specify a destination slot/port or destination port group will not be applied to traffic which is routed by the switch, these policies will match only bridged traffic. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 99931 When tagging a link aggregate on an OS6850, QoS does not trust the individual ports of the link aggregate. Workaround: Manually set the trust bit of the underlying ports through QoS (qos port trusted), or set the port default to trusted (qos trust ports). PR 99983 The OS6850 switch cannot boot up properly with a boot.cfg that exceeds the QoS limitation. It is not recommended to manually edit the boot.cfg to configure your QoS.
Open Problem Reports and Feature Exceptions PR 91681 On an OS9000, the following is noted when running a test called "alya.cgi (Backdoors)" in the NESSUS test suite: Security Note: Web mirroring - http (80/tcp) The following CGI have been discovered: Syntax: cginame (arguments [default value]) /web/content/login.html (userName [] password [] B1 [Login]) Workaround: This is the expected behavior for the login pages for WebView and Web-AVLAN authentication. NESSUS is known to provide those bogus reports.
Open Problem Reports and Feature Exceptions PR 100189 On an OS6850, when the MAC address table is full, source learning will not learn MAC addresses dynamically and the non-supplicant table will show more entries because the tables are not synchronized. Workaround: There is no known workaround at this time. PR 100614 On an OS6850, when a device is moved from one 802.1x port to another 802.
Open Problem Reports and Feature Exceptions Authenticated VLANs Problem Reports PR 87642 On an OS6800, the CLI command to specifically disable 802.1x or AVLAN authentication on a port will disable either of the authentication options configured on the port. Workaround: There is no known workaround at this time. PR 98369 DHCP is not supported with port-binding AVLANs on OS6800/OS6850. When DHCP packets are used to trigger the port binding rules, none of the rules work.
Open Problem Reports and Feature Exceptions PR 107086 User with readwrite-scp-sftp privileges is initially queried for authentication and authorization on an OS6850. After login to the scp/sftp shell, only accounting requests are sent to TACACS+ server (if enabled), commands are not queried for authorization. Workaround: There is no known workaround at this time. PR 107278 SNMP variable policyStatsQueryCount always show as zero. Workaround: See policyStatsAccessCount instead.
Open Problem Reports and Feature Exceptions PR 99862 When an over stressed test caused 100% CPU usage on an OS6850, the "Unable to send running checksum" message was displayed, and the switch was rebooted. Workaround: Avoid 100% CPU usage. PR 100127 By default, an OS6850 switch is configured to run in strict-priority. If over-subscription is done on priorities 6 & 7, it will bring down the switch. Workaround: Over-subscription on priorities 6 & 7 is not yet supported on the switch.
Open Problem Reports and Feature Exceptions PR 107139 In a stacked system on an OS6850, if the redundant cable is absent, the primary module could be one of the elements with a higher slot ID on a reboot of the system. Workaround: Use the stacking cables and provide complete redundancy. PR 107276 Swlog does not allow the user to select the TCP destination port. By default, the fixed port of 514 is selected on both OmniVista and the AOS switch.
Open Problem Reports and Feature Exceptions PR 96327 Extra display character in the swlog. No effect on the switch. Workaround: There is no known workaround at this time. PR 96584 On an OS9000, during a reload, when the fabric LED is turned off and on, there is no effect on the switch. Workaround: There is no known workaround at this time.
Open Problem Reports and Feature Exceptions PR 104874 If CPU is at 100% on an OS6800, then the commands "copy working certified" or "copy working certified flash-synchro" can make the system timeout and the primary will crash with pmd. The timeouts are printed on the screen. So, the user can know when it timeouts. User has to be aware of the copy from working to certified process. Workaround: Prevent doing a copy working certified or copy working certified flash-synchro if high CPU or remove CPU load.
Open Problem Reports and Feature Exceptions PR 106065 During the execution of the "update lanpower all" command, it is possible that the update of an individual port on the OS9800 may fail with a message similar to the following example for slot 14: FRI OCT 06 11:51:55 : LANPOWER (108) info message: +++ Shutting down daughter module in slot 14! call failed: RPC: Success PD63000 Programming Failed Slot #14!!!. Workaround: Execute a lanpower update for the specific slot which failed.
Open Problem Reports and Feature Exceptions PR 107287 During "update lanpower all" on a stack of 8 OS6850-P24/48, you might see the following error message: THU OCT 12 14:06:27 : LANPOWER (108) error message: +++ Unable to Read S19 Response! Reset Daughter Module! Done THU OCT 12 14:48:59 : LANPOWER (108) error message: +++ Unable to Read BOOT_SECTION_RESPONSE Response! +++ General Programming Error! Workaround: Do a "lanpower start" on the NI which failed the firmware update.
Open Problem Reports and Feature Exceptions PR 96011 On an OS9000, NIs will not reset on an unsynchronized takeover if those NIs are manually reset between configuration change and takeover. Workaround: There is no known workaround at this time. PR 98992 The copy working certified flash-synchro command display takes a long time on an OS6800 switch. OS6800 does not support tffs (true flash file system) but OS6850 does.
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-6586-1555 Other International 818-878-4507 Email: support@ind.alcatel.
