Filter
Top Products
Open Problem Reports and Feature Exceptions
page 74 OmniSwitch 6800/6850/9000—Release 6.1.3.R01
PR 99931
When tagging a link aggregate on an OS6850, QoS does not trust the individual ports of the link aggre-
gate.
Workaround: Manually set the trust bit of the underlying ports through QoS (qos port <slot/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. Booting up with a boot.cfg obtained
from a "write memory" is fine.
The hardware allocation checking is not done during boot up causing QoS configurations to be out of sync
with the hardware capability.
Workaround: To prevent the boot.cfg from going beyond the QoS limitations on a large QoS configura-
tion, proceed as follows: edit a text file with your desired qos configuration, apply the configuration using
"configuration apply text_file", and save the boot.cfg using "write memory".
PR 101223
On an OS6800, if a policy rule specifies the keyword "log" or "log interval", then the policy is rejected.
Workaround: Logging is not supported by the OS6800. The keyword "log" and "log interval" has to be
removed from the policy rule definition.
General
Problem Reports
PR 89262
NESSUS reports bogus “Vulnerabilities”. Basically, NESSUS collects all those known attacks/vulnerabili-
ties into their test suites.
For example, NESSUS sends: http://<switch-address>/cgi/bin/guestbook.cgi
WebView/HTTP-Server’s response: Prompts user for the default switch login page (which is the normal
operation for our embedded server).
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.
Security