A network device object in BMC Atrium Discovery represents a switch, a router, a route and firewall, and so forth. Network devices are discovered using SNMP credentials. A valid credential is required to create a NetworkDevice node.
Possible duplication of network devices
You should either discover or import network devices. Doing both will result in duplicates where a discovered network device is also imported.
A typical example of a discovered network device is illustrated in the following screen.
The information fields for a discovered network device object are arranged in the following groups:
You can also display provenance information by clicking the Show Provenance button. Provenance information is meta-information describing how the other information came to exist. For more information, see Provenance Information.
The full list of information fields which may be displayed in the General Details group for a network device are described in the following table.
Field Name |
Details |
---|---|
Name |
The name of the network device. If no name is discovered then this is the IP address of the device. |
Type |
The type of the network device, such as Switch, Router, and so forth. |
Vendor |
The vendor of the network device. |
Model |
The model name of the network device. |
Status |
Whether the exact SNMP device has been tested by BMC. This may be either: |
The full list of information fields that may be displayed in the Identity group for a network device object are detailed in the following table.
Field Name |
Details |
---|---|
Serial ID |
The serial number of the network device. |
System Name |
The |
System Object ID |
The SNMP System Object ID of the network device. |
Nexus VDC ID |
The virtual device context ID (VDC ID) of Cisco Nexus devices. |
The full list of information fields that may be displayed in the Operating System group for a network device object are detailed in the following table.
Field Name |
Details |
---|---|
Discovered OS Class |
The discovered operating system class for the network device (for example, Embedded). |
Discovered OS Type |
The discovered operating system type for the network device (for example, IOS). |
Discovered OS Version |
The discovered operating system version for the network device (for example, 12.1). |
Discovered OS Vendor |
The vendor of the discovered operating system (for example, Cisco). |
The full list of information fields that may be displayed in the Infrastructure group for a network device object are detailed in the following table.
Field Name |
Details |
---|---|
Networking Interfaces |
Provides the following details for each network interface: |
IPv4 Addresses |
Provides the following details for the IPv4 addresses: |
IPv6 Addresses |
Provides the following details for the IPv6 addresses: |
In BMC Atrium Discovery version 9.0 SP3, if you enable network device virtual interface discovery, the following new information may be displayed:
The full list of information fields which may be displayed in the Inference group for a network device object are displayed in the following table.
Field Name |
Details |
---|---|
Discovery Access |
Lists Discovery Accesses for the network device, grouped by scan date. When an endpoint is scanned, a Discovery Access node is created. The Discovery Access node records information such as the start time, end time, the Discovery Run that the scan is part of, and the previous Discovery Access to simplify troubleshooting. Clicking a Discovery Access displays the DiscoveryAccess Page for that Discovery Access. Where a Discovery Access is about to be deleted as part of DDD aging, a trash can icon is displayed next to the Discovery Access. |
Field Name |
Details |
---|---|
Last successful CMDB sync |
The time and date when the network device was last successfully synchronized into the CMDB. |
Last failed CMDB sync |
The time and date when the network device was last unsuccessfully synchronized into the CMDB. |
CMDB sync duration |
The time (in seconds) spent performing the last CMDB synchronization for the network device . |
CMDB CI count |
The number of CIs corresponding to the network device at the last CMDB synchronization. |
CMDB Relationship count |
The number of relationships to CIs corresponding to the network device at the last CMDB synchronization. |
A network device object in BMC Atrium Discovery can also represent an imported switch.
A typical example of an imported network device is shown below.
The information fields for a typical imported network device are described in the following table.
Field Name |
Details |
---|---|
Name |
Name of the network device. |
Port Details |
The following details are provided for each port on the network device: Port, Speed, Duplex, Negotiation, IP Address, Connected Host, and Description. This also highlights any performance affecting mismatches. See #Network device/host mismatch for more information. |
Connected Hosts |
List of connected hosts. The following details are provided for each connected host. Name, Discovered OS, Hardware Vendor, Virtual (whether the host is a virtual host), Organisational Unit, Location, and Status. |
Data Quality Issues |
List of any missing fields. |
A number of context-sensitive reports are available for network devices. See Switch Reports for additional information and examples of these network device-related reports.
The View Object page of a network device displays attributes and relationships that are already set for that network device. In the Port Details row, it also displays information on the connection settings for the ports on the network device.
The Port Details row is divided into fields. Of these, the speed, duplex, and negotiation fields reflect whether there is a performance affecting mismatch, or whether insufficient information is available to establish whether a mismatch exists.
If a mismatch is detected, or information is missing so that the correct configuration cannot be confirmed, then the field is filled with a background color.
Hyper-V Windows virtual machines always report NIC speed as 10 GBps
Hyper-V Windows virtual machines always report NIC speed as 10 GBps regardless of the actual speed. Consequently, for ports connected to Hyper-V Windows VMs, the network device and switch mismatch field shows incorrect results.