Filter
Top Products
Open Problem Reports and Feature Exceptions
OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 71
PR 105491
Existing inter-area-prefix and inter-area-router LSAs are not originated into areas that are created after
initial convergence of the network on an OS9000. For example, the router is running and it originates a set
of inter-area-prefix or inter-area-router LSAs into all known areas. Later, another area is added, the new
area will not have any of the inter-area-prefix or inter-area-router LSAs that exist in the other areas prior
to the creation of the new area.
Workaround: When adding an area to OSPFv3 after it has been running for a while, it should be globally
disabled and then re-enabled using the "ipv6 ospf status disable/enable" command.
PR 105770
Point-to-point interfaces are not supported in OSPFv3 at this time; therefore, 6to4 tunnels cannot be used
with OSPFv3.
Workaround: There is no known workaround at this time.
PR 107353
OSPFv3 will leak memory in either of the following two cases on an OS9000: 1) During SPF runs. 2)
During adjacency formation.
Workaround: There is no workaround that will eliminate this leak. However, it's effect can be somewhat
mitigated by trying to minimize the causal events (namely SPF calculations and new adjacency forma-
tions) between reboots.
PIM
Problem Reports
PR 102501
Currently, there is no support for an "ip unload" command. This can be a problem for customers who have
loaded a DRC loadable module and executed a "write memory" command to update the boot.cfg file. Then
decided that they wanted the module permanently removed.
Workaround: To permanently disable a module, execute the module's "disable" command followed by
another "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.