User guide

Open Problem Reports and Feature Exceptions
page 90 OmniSwitch 6600/7000/8800—Release 5.1.6.R02
PR 69890
OSPF virtual links will not form an adjacency with gateD switches if MD5 is configured on an OS6600/
OS7000 series switch.
Workaround: The MD5 key id for OSPF virtual links is hardcoded to 1. Any switch that uses gateD and
MD5 is configured on the virtual link requires that key id is coded accordingly. In this gateD example for
an OmniSwitch Router, the ID is set to 1:
ospf yes
backbone { interface 212.1.1.194 { priority 2; };
virtuallink neighborid 196 transitarea 3
{ auth md5 key “hawkVL” id 1;
hellointernal 10;
routerdeadinterval 40; } ;
} ;
PR 69893
OSPF Area Summary ranges no longer have an "enabled/disabled" status. The presence or absence of a
range itself is equivalent to the "enabled/disabled" state on an OS7000 series switch.
Workaround: If a range is to be disabled, it should be deleted with the no ip osp area summary range
command. On creating a range, it is automatically in the enabled state.
PR 72040
On an OS7000 series switch, RIP and OSPF MD5 authentication is not interoperable between AOS and
XOS (GateD) & OmniCore.
Workaround: Use Clear Text or SIMPLE authentication.
PR 81856
On OS6600 series switches, the WebView OSPF Routes page does not display the aggregated summary
route entry corresponding to the active address range configured for the area.
Workaround: There is no known workaround at this time.
PR 82004
With Catalina versions prior to 1.3, the number of collisions are capped at 5 in the Layer 3 PCAM table.
As a result, there may be some thrashing of IPMS PCAM entries, possibly leading to OSPF instability.
The version of the Catalina is determined by running the show ni command.
Workaround: The immediate workaround is to disable the limitation.