Specifications

Patches Issued Since the CS2/MMS2 Release

Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1

5-64 CS3 and MMS3

9A128_01. All these devices are used to connect Ethernet, token ring

and FDDI (conventional networks) to ATM Networks.

This was happening because the GET_ATM_PORT_LIST action was

not able to respond to devices using the CtATMConﬁgMib model type

versus the ATMClientApp model type.

The resolution was to attach an inference handler to the

CtATMConﬁgMib modeltype so that devices using it will respond to

the GET_ATM_PORT_LIST action.

The problem was network during Range Test Discovery all network

models were being placed in the Universe View as opposed to their

appropriate LAN models. A SmartSwitch Router 8000 was used as

the seed router. It was found that the problem was with the SSR

ipRouteTable. If the SSR has a default gateway conﬁgured in the the

routing table, then one more instance is added to ipRouteDest.

However, no other instances were created in the routing table (ie.

ipRouteMask, and ipRouteNextHop). When this occurs a

misalignment happens when Spectrum reads the IP table.

The resolution was to correct how AutoDiscovery reads SSR

ipRouteTable. It will recognize when a default gateway address is

added to the ipRouteTable and align the rest of the instances

accordingly. Network models discovered while an SSR acts as a seed

router will now be placed in the correct LAN models.

The problem was a memory leak was found associated with the

CsIHRelayFunction. Purify had been installed and a trace was made

available.

The resolution was to remove the memory leaks from the code

pinpointed by the Purify traces.

The problem was the SpectroGRAPH core dumped while multiple

models and alarms were being created. A dbx core trace was made

available.