3Com 3C15500 - Network Director - PC, Руководство пользователя

Страница: 150 / 924

146 C
HAPTER
4: D
ISCOVERING THE
N
ETWORK
3Com Network Director was unable to obtain information from
the following NBX devices
This is likely to occur if incorrect usernames or passwords were provided
in the wizard. Note that even if you specified in the wizard that you do
not have an NBX voice system, if 3Com Network Director detects an NCP
device during the discovery process it will attempt to retrieve phone
information from it.
3Com Network Director was unable to read the information from
the following NBX devices
This is due to the fact that 3Com Network Director does not support the
version of software running on the NBX unit. A service pack may be
available for 3Com Network Director on the 3Com web site that supports
this version.
Topology Section
The potential issues that may be detected and reported in the discovering
links phase of discovery are listed below, along with their potential
causes.
The following devices stopped responding while 3Com Network
Director attempted to read topology information from them
This can actually occur at various points of the discovery process,
including the
sizing stage of detecting devices phase, but the error is only
logged once for each faulty device. The device(s) must have responded at
some point for this error to be logged. If the problem appears to occur
multiple times on a specific subnet, try increasing the timeout/retry values
for that subnet in the
Network Discovery wizard. Alternatively you can
increase them globally using the Tools > Options dialog box.
The following devices returned invalid port information
As part of sizing, 3Com Network Director attempts to determine which
ports are enabled and have a link present since it is only those that can
take an active role in the topology. For third party devices it attempts to
do this using standard MIBs. However, not all devices implement these
MIBs and some implement slight variations of them. This can result in
3Com Network Director not being able to establish the ports that are
used in topology. Consequently such devices are treated as end stations
by the topology process. Older agent versions of certain 3Com devices
may also exhibit this problem, in which case there may be additional
messages in this report indicating that the agent version is not supported.