Vdx/vcs discovery – Brocade Network Advisor SAN + IP User Manual v12.1.0 User Manual
Page 141
74
Brocade Network Advisor SAN + IP User Manual
53-1002949-01
VDX/VCS discovery
4
VDX/VCS discovery
NOTE
Discovery of a VDX device requires Network OS 2.1.0 or later.
NOTE
Discovery a VCS fabric requires that the seed switch must be running Network OS 2.1.0 or later;
however, the fabric can include members running Network OS 2.0.0.
NOTE
VDX/VCS discovery requires read and write IP Discovery privilege. For more information about
privileges, refer to
NOTE
You must have the All IP Products AOR (area of responsibility) in your user account to discover new
products. For more information about user accounts, refer to
Network OS devices can only be discovered from the IP tab. You can discover a standalone VDX or
VCS-enabled devices as well as VCS fabrics. VDX/VCS devices display in the Network Objects,
L2 Topology, Ethernet Fabrics, IP Topology, and VLAN Topology views.
VDX device and VCS fabric discovery uses the Read/Write Login Prompt credentials for
authentication (refer to
on page 89). You cannot discover VDX devices
using root level privileges. If you do not provide discovery credentials, the Management application
uses the default switch credentials for the admin account. You can edit the credentials for multiple
VDX/VCS devices when they all have same firmware version (refer to
VCS fabrics display in a tree structure with member nodes. When you discover a new fabric and
initial discovery is complete, the fabric automatically tracks the fabric members. Subsequently, if a
member is removed from the fabric, a minus (-) icon displays (see table below) next to the product
icon.
RFC 4133
ENTITY-MIB
entPhysicalTable
entAliasMappingTable (if available)
For module (line card) information:
Entire entPhysicalTable
Entire entAliasMappingTable, if available
RFC 4293
IP-MIB
mib2.ip.ipAddressTable For
ip
address and subnet information
ipAddressAddrType
ipAddressAddr
ipAddressIfIndex
ipAddressType
ipAddressPrefix
TABLE 24
Required MIB support for third-party devices (Continued)
IETF standard
MIB name
Required MIB object
Data collected
TABLE 25
Device Removed