Device Info node
A Device Info node stores information about a scanned IP device on the network. For example, an IP device might be one of the following:
- A host computer (desktop, laptop, server, mainframe, mid-range and so forth). In these cases, there will be a corresponding Host node also.
- A router, switch, load balancer, firewall, IP phone, and so forth.
- A printer.
Device Info node lifecycle
The following section describes the scenarios in which a Discovery Info node is created or destroyed. DDD nodes are never updated.
Creation
Whenever BMC Helix Discovery scans an IP address, a Discovery Access node is created. If there is any response to the scan a Discovery Info node is also created. The level of information in the Device Info node will vary depending on the discovered device.
Removal
A Device Info node is removed when the Discovery Access node which it is associated with has been destroyed through the Aging process.
Attributes and relationships of the DeviceInfo node
The attributes of the DeviceInfo node are described in the following table:
UI Name | Description |
---|---|
Discovery Method | Discovery method |
Discovery Duration | Time in seconds spent in discovery |
Request Time | When this request was made |
Failure Reason | Reason for failure, if any |
Failure Cause | Extra details, if any, on reason for failure |
Hostname | Name of host |
Fully Qualified Domain Name | Fully qualified domain name of the host |
Discovered OS | Operating system |
Discovered OS Class | Operating system class |
Discovered OS Type | Operating system type |
Discovered OS Version | Operating system version |
Service Pack | Service pack details |
Discovered OS Architecture | Operating system architecture |
Discovered OS System Directory | Operating system directory |
Discovered OS Edition | Operating system edition |
Discovered OS Update Level | Operating system update level |
Discovered OS Build | Operating system build information |
Discovered OS Vendor | Operating system vendor |
Discovered OS Release | Operating system release |
Discovered OS UBR | Operating system update build revision |
Vendor | Vendor of device |
Platform | Platform scripts used in discovery |
Model | Model of device |
DNS Domain | DNS domain |
NIS/Windows Domain | Windows domain |
Device Type | Device type |
Last Access Method | The last method used to access this device |
Login Authentication Method | How the login session was authenticated - may be 'key' or 'password' |
Last Credential ID | The ID of the last credential used to access this device |
Last Windows Proxy Pool | The name of the last Windows Proxy Pool used to access this device |
Last Windows Proxy | The name of the last Windows Proxy used to access this device |
Other Credentials | List of other credential IDs used to access this device |
Credentials Used | The credentials used to obtain device information |
Last Outpost ID | The ID of the last Outpost used to obtain device information |
SNMP sysname | SNMP sysname |
Name | Name of device |
Capability Ids | Capability Ids |
Capability Types | Capability Types |
SNMP sysObjectId | SNMP sysObjectId |
SNMP sysDescr | SNMP sysDescr |
Serial number | Serial number |
SNMP syscontact | SNMP syscontact |
SNMP syslocation | SNMP syslocation |
SNMP cdpGlobalDeviceId | SNMP cdpGlobalDeviceId |
Virtual | Flag if the device is virtual |
Nexus VDC ID | Cisco Nexus VDC ID |
SNMP v3 Engine Identifier | SNMP v3 Engine Identifier |
Operating system derived from discovery heuristics | Operating system derived from discovery heuristics |
Operating system type derived from discovery heuristics | Operating system type derived from discovery heuristics |
Operating system version derived from discovery heuristics | Operating system version derived from discovery heuristics |
CVE-2011-1785 Vulnerability | CVE-2011-1785 vulnerability flag |
Firmware Version | Firmware version |
Testing Status | Testing status for non Host devices |
Processing Messages | Optional list of processing messages |
Not shown in UI | Flag that this node has command failures linked to it |
Not shown in UI | Flag that this node has script failures linked to it |
Not shown in UI | The name of the script that succeeded in getting this data |
Access Method | The access method used by the script that succeeded in getting this data |
The relationships of the DeviceInfo node are described in the following table:
UI Name | Relationship | Description |
---|---|---|
Data Source Access |
| Related Data Source Access |
Discovery Access |
| Related Discovery Access |
Provider Access |
| Related Provider Access |
Created Business Application |
| Business Application whose existence was inferred from this Device Info |
Created Business Service |
| Business Service whose existence was inferred from this Device Info |
Created Technical Service |
| Technical Service whose existence was inferred from this Device Info |
Created Candidate Software Instance |
| Candidate Software Instance whose existence was inferred from this Device Info |
Created Cloud Provider |
| Cloud Provider whose existence was inferred from this Device Info |
Created Cloud Region |
| Cloud Region whose existence was inferred from this Device Info |
Created Cloud Service |
| Cloud Service whose existence was inferred from this Device Info |
Created Cluster |
| Cluster whose existence was inferred from this Device Info |
Created Coupling Facility |
| Coupling Facility whose existence was inferred from this Device Info |
Created Database |
| Database whose existence was inferred from this Device Info |
Created Database Detail |
| Database Detail whose existence was inferred from this Device Info |
Created Detail |
| Detail whose existence was inferred from this Device Info |
Created Fibre Channel HBA |
| Fibre Channel HBA whose existence was inferred from this Device Info |
Created Fibre Channel Node |
| Fibre Channel Node whose existence was inferred from this Device Info |
Created Fibre Channel Port |
| Fibre Channel Port whose existence was inferred from this Device Info |
Created File System |
| File System whose existence was inferred from this Device Info |
Created Host |
| Host whose existence was inferred from this Device Info |
Created IP Address |
| IP Address whose existence was inferred from this Device Info |
Created MF Part |
| MF Part whose existence was inferred from this Device Info |
Created Mainframe |
| Mainframe whose existence was inferred from this Device Info |
Created Management Controller |
| Management Controller whose existence was inferred from this Device Info |
Created Network Device |
| Network Device whose existence was inferred from this Device Info |
Created Network Interface |
| Network Interface whose existence was inferred from this Device Info |
Created Printer |
| Printer whose existence was inferred from this Device Info |
Created Runtime Environment |
| Runtime Environment whose existence was inferred from this Device Info |
Created SNMP Managed Device |
| SNMP Managed Device whose existence was inferred from this Device Info |
Created Software Component |
| Software Component whose existence was inferred from this Device Info |
Created Software Container |
| Software Container whose existence was inferred from this Device Info |
Created Software Instance |
| Software Instance whose existence was inferred from this Device Info |
Created Storage |
| Storage whose existence was inferred from this Device Info |
Created Storage Collection |
| Storage Collection whose existence was inferred from this Device Info |
Created Storage Device |
| Storage Device whose existence was inferred from this Device Info |
Created Subnet |
| Subnet whose existence was inferred from this Device Info |
Created Unassigned Connections |
| Unassigned Connections whose existence was inferred from this Device Info |
Created Virtual Machine |
| Virtual Machine whose existence was inferred from this Device Info |
Command Failures |
| Command Failures |
Script Failures |
| Script Failures |
Comments
Log in or register to comment.