User's Manual

864 Appendix E: REPORT EXAMPLES
The following devices returned invalid port information
During the sizing stage the application attempts to determine which
ports are enabled and have a link present since it is only those that can
take an active roll in the topology. For some third party devices it may fail
to obtain any valid ports and this message will be logged. Also, for the
CoreBuilder 9000 and Switch 4007 the application does not support the
scenario where the management port is the port directly connected to
the network. If this is the only connected port then this message will be
logged.
The exact position of the following devices could not be
determined
This is really just a statement of fact. It is likely to be due a problem that
has occurred earlier such as losing communication with one of the
switches, or possibly if no MAC addresses were obtained for the device.
3Com Network Director was unable to write to the following devices, in
order to get them to perform operations that could lead to a more
accurate topology detection.
This is a failure to instruct a device to perform a remote poll. To do this
3Com Network Director performs a write operation using the write
community string. If the write community string is incorrect it is likely that
the attempt will time out.
The configuration of the following devices is not supported by
3Com Network Director
This was originally added when support was included for the switch
4007. Because it was not possible to distinguish between it and other
CoreBuilder 9000 devices, if an non-7-slot CoreBuilder 9000 was
encountered this error would be logged. This should no longer occur as
this restriction has been removed.
The following devices have support for the Spanning Tree Protocol
enabled. Links connected to these devices may in the future be blocked
by the Spanning Tree Protocol. 3Com Network Director may not be able
to detect this occurring.
The following devices have one or more ports that could not be
included in the network topology