Specifications

AutoDiscovery
Known AutoDiscovery Anomalies in SPECTRUM 6.5
SPECTRUM Software Release Notice Page 39
Known AutoDiscovery Anomalies in
SPECTRUM 6.5
Problem 1: AutoDiscovery may fail to discover a Token Ring the first time
AutoDiscovery is run. It may find one ring while failing to find another ring.
Solution: Run Ring Discovery, and the missing ring will be found.
Problem 2: On Windows NT, if you run AutoDiscovery and then search for
an IP 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 address this
problem in a future release of SPECTRUM.
Problem 3: When working in JAVA-based applications such as
AutoDiscovery and MibTools, you are able to cut/copy and paste multiple
lines from an Xterm window into JAVA-based text fields that only accepts
one value such as the “IP Address List”, or the “Community String.” When
you do this, you get unwanted results such as lists of text lines or IP
addresses you pasted in, and possibly other strange results. You also
receive the following error message:
Attempt to enter an IP Address that does not conform to
standards, please correct the IP Address entered.
This problem also occurs when using the copy/cut and paste hotkeys.
Solution: Avoid pasting multiple lines of text in fields. This problem will
be fixed in a future release of SPECTRUM.
Problem 4: When performing a router discovery, switches which are
connected to Cisco routers are discovered in addition to the Cisco routers.
This occurs because the Cisco Discovery Protocol includes switches (such
as the Catalyst 5000 and 5005) in its tables and because the Use CDP
Table checkbox setting cannot be deselected.