DiscoveryAccess page
A DiscoveryAccess is a single access to a Discovery Endpoint. When an endpoint is scanned, a DiscoveryAccess node is created which records information on the interaction that BMC Atrium Discovery has with that endpoint. When BMC Atrium Discovery is unable to access a host, the DiscoveryAccess is a good starting point for troubleshooting.
To view a DiscoveryAccess page
You can view DiscoveryAccesses from a number of places in the user interface.
From a Host Node
From the view page for a host node:
- Scroll down to the Inference section
- Click the main link in that section, for example: 172.17.3.116 SUCCESS 09/12/2008 10:48 - 09/12/2008 10:55
The Example DiscoveryAccess is shown.
From the Discovery Recent Runs page
From the Recent Runs tab of the Discovery Status page:
- Click a discovery run.
- Scroll down to the Endpoint field.
- Click the DiscoveryAccess link. If it is a link to a single DiscoveryAccess, then that Example DiscoveryAccess is shown. If there are multiple DiscoveryAccesses, then a list page is displayed.
- Click a DiscoveryAccess line to view the Example DiscoveryAccess.
Example DiscoveryAccess
The following screens show DiscoveryAccess pages for a Unix host, a Windows host, a network device, and a mainframe computer.
Attribute | Description |
---|---|
Endpoint Section | |
Endpoint | The endpoint (IP address) scanned in this discovery access. |
Start Time | The time at which the scan started. |
End Time | The time at which the scan finished. |
Total Duration | The time it took to discover and process the data, that is, the time between Start Time and End Time. |
Discovery Run | A link to the Discovery Run that this DiscoveryAccess is part of. |
Previous Discovery Access | A link to the previous DiscoveryAccess with the same endpoint. Not displayed if this is the first in a list. |
Next Discovery Access | A link to the next DiscoveryAccess with the same endpoint. Not displayed if this is the last in a list. |
Device Summary | An read-only summary showing the Host Type, Discovered OS Type, and Discovered OS Version. For example, Unix Server, Debian Linux, 4.0. |
Host | A link to the host that was created or updated as part of the scan. Not displayed if no host was created or updated. |
Status Section | |
State | The current state of the DiscoveryAccess. This may be Started or Finished. |
End State | The end state of the discovery run. This may be one of the following: |
Result | The result of the DiscoveryAccess. This may be Skipped, NoResponse, Success, NoAccess, or Error. |
Errors | If there were any errors detected by the ECA engine during discovery this will link to those errors. Examples are:
|
Session Results | If there were any failures attempting to get a session on the endpoint this will link to a list of failures and successes. See below for details. |
Discovery Details Section | |
Data Source | Does this Discovery Access originate from this appliance, come from a scanning file, or was it consolidated from a scanning appliance. |
Credential Used | A link to the Windows proxy or Credential used to in this Discovery Access. The link name is a hash of details of the credential; it does not provide the credential itself. You are not shown the Credential pages if you do not have permissions to view them. This field is not displayed as a link on the consolidation appliance for scans which have been consolidated from a scanning appliance. |
Discovery Start Time | The time at which discovery started on the scanning appliance. This field is only displayed on the consolidation appliance for scans which have been consolidated from a scanning appliance. |
Discovery End Time | The time at which discovery completed on the scanning appliance. This field is only displayed on the consolidation appliance for scans which have been consolidated from a scanning appliance. |
Session Establishment Duration | The time it took to establish the session, that is, to log onto the host. |
Total Discovery Duration | The time taken to establish a session and run commands. |
On Hold Since | If the discovery is currently paused, the time at which it was paused. |
On Hold Duration | If the discovery has been paused, the elapsed time since it was paused. |
Standard Discovery | |
Method | The discovery method used. This is one of: getDeviceInfo, getHostInfo, getInterfaceList, getProcessList, getPackageList, getPatchList, getNetworkConnectionList, getHBAInfo, and getNames. |
Status | The status of the discovery access for the method. This is OK or the failure reason. |
Script | The name of the script used, if any. |
Access | The access method used to connect to the endpoint (for example, ssh, telnet, rlogin, and so on. |
Result | A link to the node or nodes created by this discovery method. |
Additional Discovery | |
Method | The additional discovery method used. These are discovery methods called by patterns, for example:
|
Status | The status of the discovery access for the method. This is OK or the failure reason summarised into links. |
Script | The name of the script used. |
Access | The access method used to connect to the endpoint. For example: ssh, telnet, rlogin, etc. |
Result | A link to the node or nodes created by this discovery method. |
DiscoveryAccess state
The following table shows the possible discovery scenarios and the resulting end_state
and result
attributes of the DiscoveryAccess node:
In addition to end_state
and result
attributes on the DiscoveryAccess there is also a reason
attribute that contains further details. There is no fixed set of values for reason
.
The following state diagram and table may be of use understanding the results of an attempted access.
Discovery Scenario | Resulting State of DiscoveryAccess |
---|---|
IP Injected → In Exclude list |
|
IP Injected → Already Processing this IP |
|
IP Injected → Second Scan Optimization (Best IP) |
|
IP Injected → No IP Response |
|
IP Injected → IP Response |
|
IP Injected → IP Response → Device Type not supported |
|
IP Injected → IP Response → No HostInfo recovered |
|
IP Injected → IP Response → No InterfaceList recovered |
|
IP Injected → IP Response → HostInfo and InterfaceList recovered |
|
IP Injected → IP Response → HostInfo and InterfaceList recovered → First Scan Optimization |
|
IP Injected → IP Response → HostInfo and InterfaceList recovered → First Scan Optimization not needed |
|
IP Injected → Traceback captured |
|
IP Consolidated when originally optimized on Discovery Appliance |
|
Troubleshooting using session results
There are three scenarios that are highlighted using Session Results:
- Initial scan and successful connection: a number of unsuccessful connection attempts followed by a successful connection shows BMC Atrium Discovery selecting credentials.
- Failure to connect: BMC Atrium Discovery was unable to connect. Typical problems could be failed credentials or poor network connectivity.
- Failure at start of scan before successful connection: this can occur when a credential fails (expiry) but a later credential is successful.
Checking credentials after a failure
- From the Discovery Access, click the session results link.
- Click the Connection timed out rows to display the SessionResult page for that specific login attempt.
This page shows information on the attempted login, including a credential link and a link to the DiscoveryAccess. The credential link is a hash of the credential name which links to that credential in the Login Credentials page only if you have sufficient permissions to view the credentials. - Click the test button.
If the credential tests successfully, it is likely that a transient network problem caused the connection time-out. Alternatively, you can navigate back to the Discovery Access page and rescan from the Discovery Actions menu.
Comments