Specifications

9032277-04 Software Superseded by CS3/MMS3
5-99
Patches Issued Since the CS2/MMS2 Release
--
The problem was that LAN models were not getting created correctly
(or at all in some cases) when modeled through AutoDiscovery. In one
case, a customer used AutoDiscovery to model a SmartSwitch router
8000 as a seed router. The router had 45 ports, six of which had direct
routes in the ipRouteTable. After the discovery, the only pipes to the
router were from a fanout and a 9H421_12. Three LAN containers
were created for one IP; two other LANs had a different IP, and a 6th
LAN had its own IP. SPECTRUM was assuming that all interface
models were one level below the router model, but the SmartSwitch
Router uses the IF stack mib and therefore has several layers of both
physical and logical interfaces.
In another case, the customer had several Cisco 2501's and 7500's
modeled as Rtr_Cisco. These models were modeling either none or
some of the containers which should show up on their interfaces. They
were missing LANs from their ethernet interfaces and WA_Links from
their PPTPS interfaces. No WA_Link models were being created for
virtual interfaces and WA_Link models were not getting correctly
placed on their interfaces in the DevTop view.
The resolution to the respective cases was to modify the
get_interfaces() method so that it first tries the AD_GET_PORT_MH,
then tries the GET_INTERFACES action, and then finally grabs the
models in the HASPART relation. Also, code was changed to let
get_spectrum_if() return the virtual IF model handle and IF index,
instead of physical, if the virtual IF has already been modeled, which
means if the user wants to see the virtual IF in the DevTop view,
SPECTRUM should resolve/model the subnets for these virtual IFs.
--
The problem was that SPECTRUM was not resolving connections
between switches and routers so that a switch could communicate
with a router via any of its ethernet interfaces.
For example, a customer models a router and three switches -- A, B,
and C. The router has three ethernet interfaces -- X, Y, and Z. The
dot1dTpFdbAddress table on switch A knows about ethernet interface
X. The dot1dTpFdbAddress table on switch B knows about ethernet
interface Y. Likewise, C knows about Z. If the customer draws a pipe
from the router to switch A, the router resolves to the correct
interface. If he draws a pipe from the router to switch B or C, he gets