Filter
Top Products
Open Problem Reports and Feature Exceptions
page 72 OmniSwitch 6800/6850/9000—Release 6.1.3.R01
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.
Workaround: Avoid register-encapsulation by configuring the RP to be on the same switch as the source.
General
Problem Reports
PR 105380
If there is no arp entry for the destination, routed traffic matching a drop policy gets dropped in software
by the CPU instead of being dropped by the OS6800.
Workaround: There is no known workaround at this time.
PR 105496
Rules that match multicast traffic do not get logged properly on an OS9000.
Workaround: There is no known workaround at this time.
PR 105764
Due to the method QoS handles condition groups (network, services, etc.), the flushing of conditions
corrupts the linkages between the condition and the groups. The condition remain attached to the SLB
cluster. However, the group pointers in the condition are invalid. Because of this, the group parameters are
restricted.
Workaround: There is no known workaround at this time.
PR 107091
On OS9000, QoS currently will not accept names of 23 character from SLB.
Workaround: Use names of 22 characters or less.
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.
Quality of Service (includes ACLs)