Filter
Top Products
Open Problem Reports and Feature Exceptions
page 80 OmniSwitch 6800/6850/9000—Release 6.1.3.R01
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. On some setups, the OmniVista port needs to be changed
and the switch can not send to this new port.
Workaround: Use the default TCP port setting of OmniVista or set a third party syslog server to port 514.
PR 107033
When port 1/1 on the system has software learning enabled...either by the port being mobile or authenti-
cated and if there is a linkagg configured on the switch, the internal mac 0x0020da999999 is seen in the
output of show mac-address table learned as being learnt on port 1/1.
Workaround: There is no known workaround at this time.
Chassis Supervision
Problem Reports
PR 94404
Mixing OS7000 and OS9000 CMMs in any chassis is not supported.
Workaround: There is no known workaround at this time.
PR 95320
On an OS9000, the Unix mv command does not update a file's time stamp. Therefore, the check sum will
not detect the change.
Workaround: Use the cp command instead.
PR 96225
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.