Specifications

Corrected and Known Anomalies
AutoDiscovery
Software Release Notes Page 76
Problem 3: Whenever Background Discovery is actively running on behalf
of a LAN or Network container model, the icon representing the model will
temporarily show a condition of blue/initial, even though contact has
previously been established. In addition, if the container model’s own
Topology view is open when the discovery session begins, newly discovered
models will not appear.
Solution: Closing and re-opening the container model’s Topology view
will display any newly discovered models. The container model’s own icon
will revert to the correct condition color soon after the Background
Discovery session concludes.
Problem 4: When AutoDiscovery is run on a network containing two
SmartSwitch routers connected with only a WAN link, the discovery does
not create the WAN_Link between the routers and could appear as LANs.
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 5: On Windows NT, if you search for IP an ATT1000 model, it is
found as a pingable. If you destroy the device and model it by IP, it is
discovered as an ATT_SmartHub.
Solution: This device does not support the necessary MIBs that allow
AutoDiscovery to classify it as an SNMP agent. Aprisma may reconsider
this problem in a future release of SPECTRUM.
Problem 6: ATM Discovery fails to resolve device connections for ATM
edge devices (9a426s, HSIMs, etc.)
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 7: On Windows NT, when you run AutoDiscovery, select LANs
(IP Subnets) and choose Radial for Placement, no autoplace occurs.
Solution: Place the Topology Universe view into Edit mode and perform
Auto Place from the Edit menu. This problem will be fixed in a future
release of SPECTRUM.