Alcatel OmniSwitch 6800 Release Notes
  1. Manuals
  2. Brands
  3. Alcatel Manuals
  4. Switch
  5. OmniSwitch 6800
  6. Release notes
Alcatel OmniSwitch 6800 Release Notes

Alcatel OmniSwitch 6800 Release Notes

Release 6.1.3.r01
Hide thumbs Also See for OmniSwitch 6800:
Table of Contents

Advertisement

Quick Links

See also: Troubleshooting Manual
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 load-
ing new software.
Contents
•
•
•
•
•
Supported Hardware/Software Combinations, see
•
•
•
•
•
•
•
•
•
Layer 2, see
•
Layer 3, see
•
•
•
•
System, see
page
•
•

Release Notes

Part Number 032067-10, Rev D
Copyright 2006 Alcatel Internetworking, Inc.
OmniSwitch 6800/6850/9000
page
2.
page
4.
page
4.
page
5.
page
-11.
page
13.
page
37.
page
page
page
44.
page
48.
page
53.
page
65.
page
69.
page
72.
page
74.
78.
page
86.
Release 6.1.3.R01
page
-9.
42.
42.
page
48.
Release Notes
page
4.
page 1

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the OmniSwitch 6800 and is the answer not in the manual?

Questions and answers

Related Manuals for Alcatel OmniSwitch 6800

Summary of Contents for Alcatel OmniSwitch 6800

  • Page 1: Table Of Contents

    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 load- ing new software.

  • Page 2: 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.
  • Page 3 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. Technical Tips, Field Notices • Contracted customers can visit our customer service website at: http://eservice.ind.alcatel.com.

  • Page 4: System Requirements

    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.

  • Page 5: New Hardware Supported

    SFP ports, two (2) 10 Gigabit XFP slots, as well as two combo ports individually configurable to be 10/100/1000 Base-T ports. Note. OmniSwitch 6850 units and OmniSwitch 6800 units should not be mixed in the same stack. See the OmniSwitch 6850 Series Hardware Users Guide for more information on OmniSwitch 6850 hardware features.
  • Page 6 New Network Interface (NI) Modules The following NI modules are available in this release: OS9-GNI-P24 Provides 24 auto-sensing twisted-pair Power over Ethernet (PoE) ports, individually configurable as 10BaseT, 100BaseTX, or 1000BaseT. OS9-XNI-U6 Provides six 10 Gigabit XFP slots. page 6 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 7 10km at Gigabit speed and 100Mbit speed. Note: at 100Mbit speed, this SFP can interoperate with SFP-100-LC-SM15 or similar transceiver. • at Gigabit speed, this SFP can interoperate with SFP-GIG-LX or similar transceiver. • OmniSwitch 6800/6850/9000—Release 6.1.3.R01 New Hardware Supported page 7...

  • Page 8: Fx Ethernet Transceivers

    Combo Ports Ports supported supported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported unsupported OmniSwitch 6800/6850/9000—Release 6.1.3.R01 OS6850-U24X OS9-GNI-U24 supported supported supported supported supported supported supported unsupported supported unsupported supported unsupported supported unsupported supported unsupported...

  • Page 9: Supported Hardware/Software Combinations

    OS6850-24X OS6850-48X OS6850-P24 OS6850-P48 OS6850-P24X OS6850-P48X OS6850-U24X OS6850-24L OS6850-48L OS6850-P24L OS6850-P48L OS6800-24 OS6800-48 OS6800-24L OS6800-48L OS6800-U24 OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Supported Hardware/Software Combinations 6.1.1.R01 6.1.1.R02 902369 supported supported 902444 supported supported 902492 not supported not supported 902367 supported supported 902370 supported...
  • Page 10 Power Control Checksum: MAC Address: page 10 OS9-GNI-C24, 10-1000 RJ45, 902394-40, C13, G1511279, MAY 03 2006, POWER ON, 0x0, 00:d0:95:e6:54:80, BCM56504_B2 0005/00 6.1.1.167.R02 No Miniboot OS9700-CFM, FABRIC BOARD, 902444-10, C11, G1810128, MAY 08 2006, POWER ON, 0x0, 00:d0:95:e0:6c:ac, OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 11: New Software Features

    Port Mirroring (1:128) Power over Ethernet (PoE) Redirection Policies (Port and Link Aggregate) Secure Copy (SCP) Server Load Balancing (SLB) SSH Public Key Authentication Syslog to Multiple Hosts OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Platform Software Package base base OS9000 base OS6850/OS9000 base...
  • Page 12 New Software Features Feature VLAN Range Support VLAN Stacking and Translation VRRPv3 page 12 Platform Software Package base OS6850/OS9000 base OS6850/OS9000 base OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 13: Feature Summary

    Dynamic VLAN Assignment (Mobility) DVMRP End User Partitioning Ethernet Interfaces Flood/Storm Control Health Statistics HTTP/HTTPS Port Configuration Interswitch Protocols (AMAP) IP Multicast Switching (IPMS) IPv6 Multicast Switching (MLD) OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Platform Software Package base base base base base base OS6850/OS9000...
  • Page 14 Software Package base base base base base base base base base base base base OS6850/OS9000 base OS6800 base base OS6850/OS9000 base base OS6850/OS9000 base base base base base base base OS6850/OS9000 base base base base base base base OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 15: Feature Descriptions

    The 6.1.3.R01 release provides support for this feature on the OmniSwitch 6800 Series, OmniSwitch 6850 Series, and OmniSwitch 9000 Series.
  • Page 16 IPv6 interfaces. Note. IPv6 ACLs are not supported on A1 NI modules. Use the show ni command to verify the version of the NI module. Contact your Alcatel-Lucent support representative if you are using A1 boards. ACL & Layer 3 Security...
  • Page 17 ACL logging extensions to display Layer 2 through 4 packet information associated with an ACL. • ACLMAN is supported on the OmniSwitch 6850 Series. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 9000 Series. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Software Supported page 17...

  • Page 18: Authenticated Switch Access

    Enabling AVC on the switch is another way to prevent undesirable ports from becoming the root for an MSTI. page 18 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 19: Bgp Graceful Restart

    There are three versions of the BGP protocol— versions 2, 3, and 4. The Alcatel-Lucent implementation supports BGP version 4 as defined in RFC 1771. The Alcatel-Lucent implementation of BGP is designed for enterprise networks, specifically for border routers handling a public network connection, such as the organization’s Internet Service Provider (ISP)

  • Page 20: Dhcp Relay

    Option-82 data and then forward the packet to the server. DHCP Option-82 is supported on the OmniSwitch 6800 Series and OmniSwitch 6850 Series. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 9000 Series.

  • Page 21: Dns Client

    Rate Limiting—Limits the number of DHCP packets on a port. This functionality is provided using • the QoS application to configure ACLs for the port. DHCP Snooping is supported on the OmniSwitch 6800 Series and OmniSwitch 6850 Series. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 9000 Series. DNS Client A Domain Name System (DNS) resolver is an internet service that translates host names into IP addresses.

  • Page 22: Ethernet Interfaces

    (e.g., NBNS/NBDD, DNS, TFTP, and TACACS) or destined for a user-defined service port can be forwarded to a maximum of 256 VLANs on the switch. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 6800 Series, OmniSwitch 6850 Series, and OmniSwitch 9000 Series.
  • Page 23 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 Alca- tel-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.
  • Page 24 IGMP membership state. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 6800 Series, OmniSwitch 6850 Series, and OmniSwitch 9000 Series. IPv6 IPMS Proxying is not supported on the OmniSwitch 6800 Series.

  • Page 25: Ipx Routing

    16K per module and up to 64K per OmniSwitch 9000 chassis. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 9000 Series; increasing the MAC address table size is not supported on the OmniSwitch 6800 Series and OmniSwitch 6850 Series. L2 Static Multicast Addresses Static multicast MAC addresses are used to send traffic intended for a single destination multicast MAC address to multiple switch ports within a given VLAN.

  • Page 26: Multicast Routing

    • Link Aggregation (static & 802.3ad) Alcatel-Lucent’s link aggregation software allows you to combine several physical links into one large virtual link known as a link aggregation group. Using link aggregation can provide the following benefits: Scalability. You can configure up to 32 link aggregation groups that can consist of 2, 4, or 8 Ethernet- •...

  • Page 27: Ntp Client

    Graceful (Hitless) Support During Failover, which is the time period between the restart and the rees- • tablishment of adjacencies after a planned (e.g., the users performs the takeover) or unplanned (e.g., the primary management module unexpectedly fails) failover. OSPF adjacencies over non broadcast links. • OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Software Supported page 27...
  • Page 28 Policy Server Management Policy servers use Lightweight Directory Access Protocol (LDAP) to store policies that are configured through Alcatel-Lucent’s PolicyView network management application. PolicyView is an OmniVista application that runs on an attached workstation. The Lightweight Directory Access Protocol (LDAP) is a standard directory server protocol. The LDAP policy server client in the switch is based on RFC 2251.

  • Page 29: Port Mirroring

    Network Ports of different sessions can communicate with each other. Port Mapping is supported on the OmniSwitch 6800 Series and OmniSwitch 6850 Series. The 6.1.3.R01 release provides support for this feature on the OmniSwitch 9000 Series.
  • Page 30 By default, local routes always have precedence. In the CLI use the ip route-pref command to configure the routing prefer- ence. page 30 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 31: Secure Shell (Ssh) Public Key Authentication

    It is now possible to enforce the use of public key authentication only on the switch. By default, both password and public key authentication are allowed. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Supported Operating Systems...

  • Page 32: Server Load Balancing (Slb)

    The sFlow collector makes use of SNMP to communicate with an sFlow agent in order to configure sFlow monitoring on the device (switch). Smart Continuous Switching - OmniSwitch 6800/OmniSwitch 6850 In stacked configurations, one switch is designated as the primary “management module” for the stack.

  • Page 33: Software Rollback

    Should the configuration or images files prove to be less reliable than their older counterparts in the certified directory, then the switch can be rebooted from the certified directory, and “rolled back” to an earlier version. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 33...

  • Page 34: Text File Configuration

    You can invoke the switch’s CLI snapshot command to capture the switch’s current configuration into • a text file. You can use the switch’s text editor to create or make changes to a configuration file. • page 34 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 35 Up to 4094 VLANs for Flat Spanning Tree mode and 252 VLANs for 1x1 Spanning Tree mode are supported. In addition, it is now possible on the OmniSwitch 6800/6850/9000 to specify a range of VLAN IDs when creating or deleting VLANs and/or configuring VLAN parameters, such as Spanning Tree bridge values.
  • Page 36 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 •...

  • Page 37: Supported Traps

    OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Supported Traps Platforms Description The SNMP agent in the switch is rein- itiating and its configuration may have been altered. The SNMP agent in the switch is rein- itiating itself and its configuration is unaltered.
  • Page 38 NMS station running RMON. An Ethernet statistical variable has dipped below its falling threshold. The variable’s falling threshold and whether it will issue an SNMP trap for this condition are configured by an NMS station running RMON. OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 39 OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Supported Traps Platforms Description Sent by a bridge that became the new root of the spanning tree. A root port has changed for a span- ning tree bridge. The root port is the port that offers the lowest cost path from this bridge to the root bridge.
  • Page 40 — There are no pass through slots avail- able to be assigned to an element that is supposed to enter the pass through mode. OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 41 OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Supported Traps Platforms Description An overload trap occurs whenever a new entry to the hardware VLAN rule table gets dropped due to the overload of the table. Indicates the link aggregate is active.

  • Page 42: Unsupported Software Features

    OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Software Package base base...
  • Page 43 Software Feature VLANs Chassis Supervision OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Unsupported CLI Commands 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...

  • Page 44: Unsupported Mibs

    Table alaCoroL3HreChangeTable esmPortCfgLongEnable alcether10GigTable esmPortCfgRuntEnable esmPortCfgRuntSize esmPortPauseSlotTime esmPortCfgFLow OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 45 MIB Name Alcatel IND1QoS Alcatel IND1Slb Alcatel IND1StackManager Alcatel IND1SystemService OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Unsupported MIB variables alaQoSPortPdiTable alaQoSSlotPcamTable alaQoSPortProtocolTable alaQoSSlotProtocolTable alaQoSSlotDscpTable alaQoSRuleReflexive alaQoSAppliedRuleReflexive alaQoSActionSourceRewriteIpAddr alaQoSActionSourceRewriteIpAddrStatus alaQoSActionSourceRewriteIpMask alaQoSActionTable alaQoSActionSourceRewriteNetworkGroup alaQoSActionTable alaQoSActionSourceRewriteNetworkGroupStatus alaQoSActionTable alaQoSActionDestinationRewriteIpAddr alaQoSActionTable alaQoSActionDestinationRewriteIpAddrStatus alaQoSActionTable alaQoSActionDestinationRewriteIpMask alaQoSActionTable alaQoSActionDestinationRewriteNetworkGroup alaQoSActionTable alaQoSActionDestinationRewriteNetworkGroupStatus...
  • Page 46 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 47 IETF_RS_232 (RFC 1659) IETF_SNMPv2 IETF_SNMP_ COMMUNITY (RFC 2576) IETF_SNMP_ NOTIFICATION (RFC 2576) IETF_SNMP_PROXY (RFC 2573) IETF_SNMP_TARGET (RFC 2573) IETF_SNMP_USER_BASED_SM (RFC 2574) IETF_SNMP_VIEW_BASED_ACM (RFC 2575) OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Unsupported MIB variables dot1dExtBase dot1dPortCapabilitiesTable dot1dPortPriorityTable dot1dUserPriorityRegenTable dot1dTrafficClassTable dot1dPortOutboundAccessPriorityTable dot1dPortGarpTable dot1dPortGmrpTable dot1dTpHCPortTable dot1dTpPortOverflowTable...

  • Page 48: Open Problem Reports And Feature Exceptions

    When using the CLI "show ni" command, the display of XFP and SFP Model name and Description displays the manufacturer's name. These fields should display the Model Name and device description. Workaround: There is no known workaround at this time. page 48 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 49: Problem Reports

    When replacing an NI with a different type of NI, the sFlow configuration is not deleted correctly for the ports which do not exist anymore. Workaround: Delete the sFlow configuration before swapping different NI types. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 49...
  • Page 50 In WebView > Health > LED page, the XFP1 and XFP2 LEDS are not displayed. Workaround: XFP1 and XFP2 LEDs are for realtime packet traffic activity indications. For precise reflection of the Rx/Tx activity, please refer to the corresponding Rx/Tx statistics all through the WebView > Health pages. page 50 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 51 Virtual Machine SDK version is less than 1.2. Workaround: Upgrade the Java Virtual Machine browser plug-in to a more recent version. PR 105205 Reloading the switch using in and at times fails in WebView. Workaround: Use the CLI for timed reloads. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 51...
  • Page 52 WebView is not showing this information and will only see as authenticated. Workaround: Look at which vlan the supplicant is authorized and that can tell if the supplicant learned on the user defined "failed" VLAN. page 52 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 53: Layer 2

    100Mbps link partner and can detect a false link UP. Traffic may not pass in this condition. Workaround: Enable autonegotiation for this copper port and configure desired speed and duplex settings. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 53...
  • Page 54 On an OS6800/OS6850, binding rules that require a port number to be specified as part of the rule can no longer be deleted if the port is not set to be mobile. Workaround: Make the port mobile before deleting the rule. page 54 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 55 To use a copper combo port, then set the mode to Forced-Copper. To use the Gig copper SFP in the corresponding copper port, then set the mode of the port to Forced-Fiber. Workaround: There is no known workaround at this time. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 55...
  • Page 56 Workaround: There is no known workaround at this time. PR 108631 MIB Walk of HybridPort fails on OS6850 Lite 48port having combo ports (both upgraded and non- upgraded version). Workaround: There is no known workaround at this time. page 56 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 57 Workaround: There is no known workaround at this time. PR 98869 On an OS6800, egressing IP Multicast traffic onto a mobile VLAN from a 6800's mobile port will not remove the 802.1Q frame. Workaround: There is no known workaround at this time.

  • Page 58: Link Aggregation

    An OS6800/OS9000 preserves the INGRESS tag format of the packet for EGRESS mirroring, which makes the mirror packet go out tagged though the real egress packet is not tagged. Workaround: There is no known workaround at this time. page 58 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 59 On an OS9000, the MAC address of an untagged packet does not get learned in the default VLAN with "filtering" and with "accept only" tagged frames. Workaround: There is no known workaround at this time. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 59...
  • Page 60 On an OS9000, disabling a linkAggr port while traffic is running might leave some MAC addresses learned on the primary member port of the linkAggr. Workaround: Administratively down all ports that transmit across the linkAggr or link down/up the primary port after disabling the link aggregate. page 60 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 61 Workaround: Wait until MAC ages or perform a manual MAC flush. PR 106781 On OS9000, sometimes max 16k macs do not learn across linkagg in chassis-distributed. Workaround: Do not use chassis-distributed mode with linkagg and many MACs. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 61...
  • Page 62 This happens due to the inconsistent spanning tree topology during the convergence and stops entirely once the network converges. page 62 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 63 Enabling Spanning Tree on an OS9000 in flat mode after disabling does not work when VLAN 1 is disabled. Workaround: Enable VLAN 1, enable STP and disable VLAN 1. Step1: disable Spanning Tree -> vlan 1 stp disable OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 63...

  • Page 64: Vlan Stacking

    An error message is received on an OS6850 console after assigning a range of tagged vlans to an aggre- gate from CLI. Workaround: This message can be ignored since it does not affect the actual assignment of the VLANs in the range. page 64 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 65: Dhcp Snooping

    DHCP Snooping port list. Workaround: Added the q-tag port to the VLAN first, then enable DHCP Snooping against the VLAN. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 65...
  • Page 66 MTU. Therefore, even if the configured IPv6 interface MTU is smaller, packets will still be forwarded instead of being dropped and “a packet too big” message returned to the sender. This can cause problems with path MTU discovery. Workaround: There is no known workaround at this time. page 66 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 67 Workaround: The active gateway for all routes (redistributed and otherwise) is available in the IP route- manager routing table. Use the show ipv6 router database CLI command to display the IP route-manager routing table. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 67...

  • Page 68: Udp Relay

    Workaround: There is no known workaround at this time. UDP Relay Problem Reports PR 97666 TCP does not send an RST after receiving an unacceptable ACK in SYN-RCVD state on OS6800 and OS6850. Workaround: There is no known workaround at this time. page 68 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 69: Advanced Routing

    OS6850 or OS9000, they are not consistently translated into IPRM route-maps that handle the redistri- bution. Workaround: Do not attempt to restore more than 185 redistribution filters from a boot.cfg file gener- ated from an earlier release. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 69...
  • Page 70 IETF draft MIB. This affects all hardware platforms that support OSPFv3. Workaround: The CLI can display the routing table (show ipv6 ospf routes) and border router table (show ipv6 ospf border-routers) for OSPFv3. page 70 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 71 "write memory" command and a reboot. To also free up any memory possibly used by the disabled module, edit the boot.cfg file using the "vi" command to delete the "ip load <module>" command along with any non-default configuration lines associated with the module. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 71...

  • Page 72: Quality Of Service

    PR 107190 SLB will return an error if the configured ping period is out of range on an OS9000. However, the ping period will still be updated. Workaround: Change the ping period to a correct value. page 72 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 73 Workaround: The policy will match traffic which matches the policy criteria even if the packet is not Ethernet-II if the policy specifies only one of the following: source slot/port, destination slot/port, source MAC or destination MAC. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 73...

  • Page 74: Security

    Since our HTTP server replies with some form of an HTTP response, NESSUS mistakenly concludes that the HTTP server is vulnerable to this attack. Workaround: There is no known workaround at this time. page 74 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 75 On an OS6850, not all MAC addresses will be learned when testing with a traffic generator to simulate traffic with incremental MAC addresses. Workaround: There is no known workaround at this time. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions page 75...
  • Page 76 SNMP MIB walk on aaaAcctCmdTable returns empty even when the table is set. Workaround: There is no known workaround at this time. PR 107085 Accounting log for scp-sftp displays user IP address as 0.0.0.0 on an OS6850. Workaround: There is no known workaround at this time. page 76 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 77 PC has traffic coming out with VLAN x's subnet and thus device classification task will classify the supplicant on VLAN x again. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions...

  • Page 78: System

    Workaround: There is no known workaround at this time. PR 97213 On an OS9000, in all CPU exceptions, a Trace Buffer dump is offered at the beginning of the exception. Workaround: There is no known workaround at this time. page 78 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 79 The "update default miniboot" is still supported on OS6850 even though there is no default or backup miniboot. Workaround: This command will still cause the miniboot to be updated properly. PR 106649 The “update miniboot” command is not working on OS-9000. Workaround: Use the “update uboot-miniboot” command to update the miniboot. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 79...
  • Page 80 On an OS9000, the "+++ i2cReadRemoteCMM: Error writing starting address!" error message is seen on the secondary after the primary crashes and a takeover is in progress. However, the system functions normally and takeover still occurs. Workaround: There is no known workaround at this time. page 80 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 81 Workaround: Do not remove multiple stacking cables at the same time. PR 100244 Installing 6.1.3.R01 images on an OmniSwitch 6800 that is running 5.3.1.R02 code returns an error. Workaround: The code base has changed significantly from 5.3.1 to 6.1.2. This is especially true of Jos.img.

  • Page 82: Power Over Ethernet

    OS6850 POE units support either 510 or 360 Watt power supplies. If unlike power supplies are mixed, or if an unsupported power supply, such as a 120-Watt power supply are used, a console message and a trap are generated. Workaround: There is no known workaround at this time. page 82 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 83 (this is the preferred method) or the configuration file may be edited (this should only be performed by an individual extremely familiar with configuration files and PoE configuration as the ENTIRE unit configuration may be changed, or damaged). page 83 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 84 The whole chassis will reload if more than half of NIs are hot swapped in and out of the chassis at roughly the same time. Workaround: If hot swap of NIs is required, a user may have to wait until a previous NI has been booted first, and then hot swap the next NI. page 84 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...
  • Page 85 Upon unsynchronized takeover in Fuji 16 slot chassis, some NIs don't come up gracefully after resetting. Workaround: Power cycle the NIs that are not UP and ready. page 85 does. So an OS6800 switch takes much OS6850 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

  • Page 86: Technical Support

    Severity 2 Segment or Ring is down or intermittent loss of connectivity across network. Severity 3 Network performance is slow or impaired—no loss of connectivity or data. Severity 4 Information or assistance on product feature, functionality, configuration, or installation. page 86 Phone Number 800-995-2696 877-919-9526 +33-388-55-69-04 +65-6586-1555 818-878-4507 OmniSwitch 6800/6850/9000—Release 6.1.3.R01...

This manual is also suitable for:

Omniswitch 6850Omniswitch 9000

Table of Contents

Save PDF