For the selected task, the task-name page displays links to the generated discovery results and logs, along with their associated details. The discovery results and logs vary for each discovery method, depending on how discovery is performed and what the devices expose.
The number of results displayed depends on the maximum number of results the task is allowed to store. You specify this value in the Max discovery results field when creating the task.
By default, each result entry in the table has the following attributes:
| Column | Description |
|---|---|
| Name | The auto-generated name of the discovery result. Selecting the result name opens the expanded details section, showing the complete discovery result. For more details on how to understand and interpret the discovery results, refer to About discovery results. |
| Creation time | The time at which the result entry was created. The date is displayed in the format MM DD, YYYY and time is displayed in the format hh:mm:ss AM/PM. |
| Duration | The time taken to complete the task. |
| Log | The name of the discovery log generated for the result. Selecting the log name opens the expanded details section, showing the complete discovery logs generated for the result. |
| Error | The name of the error logs generated for the result, if available. If
no error logs are generated, this column is blank. Selecting the error log name will open the expanded details section, showing the complete error logs generated for the result. |
| Exception | The name of the exception logs generated for the result. If no
exception logs are generated, this column is blank. Selecting the exception log name will open the expanded details section, showing the complete exception logs generated for the result. |
| Actions (vertical ellipsis icon) |
Actions you can perform on the selected task result: view detailed results, delete results, and download results as a zip file. |
About discovery results
To view detailed discovery results for a task, select the result name in the task-name page, or select the vertical ellipsis icon for a result entry, then select View details. The expanded details section opens, displaying the detailed result.
You can also download these results (in JSON) as a zip file by selecting the checkbox for the result and then selecting . Alternatively, select the vertical ellipsis icon for the result, then select Download.
{"address":"172.16.2.4", "fqdn":"172.16.2.4", "id":31, "type":"HOST", "parentId":0},- In v26.1.0: When you run a discovery task on a remote probe
through Address Manager, and the latency between Address Manager and
the remote probe is more than 100 ms, Network Discovery &
Visibility could time out while downloading the discovery result.
This causes a discovery result file to be erroneously created with
the message
Result file is not available or cannot be downloaded, even though Address Manager returns the result successfully. Any associated reconciliation policy cannot be applied because no result was stored. - In v26.1.1: Network Discovery & Visibility allows more time to download the discovery result, accomodating a latency of 300 ms and higher, so results are retrieved faster. If a result still can't be retrieved, the run is shown as Completed without a result file created. The associated logs, creation time, and duration are still displayed. Instead of a placeholder result file, an error log is created with a message indicating that the result file could not be fetched from Address Manager. Additionally, reconciliation policies that use this result are not queued.
[
{"id":1, "parentId":0, "address":"192.0.2.10", "name":"Router", "description":"Cisco IOS Software [Dublin], Virtual XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.11.1a, RELEASE SOFTWARE (fc3)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2023 by Cisco Systems, Inc.Compiled Wed 05-Apr-23 06:54", "location":"", "vendor":"Cisco", "type":"ROUTER", "vendorId":9,
"device-addresses":["198.51.100.10","198.51.100.11","192.0.2.196"],
"interfaces":[
{"ifIndex":1, "connector":"true", "name":"Gi1", "alias":"", "speed":1000000000, "hispeed":0},
{"ifIndex":2, "connector":"true", "name":"Gi2", "alias":"", "speed":1000000000, "hispeed":0},
{"ifIndex":3, "connector":"true", "name":"Gi3", "alias":"", "speed":1000000000, "hispeed":0},
{"ifIndex":4, "connector":"true", "name":"Gi4", "alias":"", "speed":1000000000, "hispeed":0},
{"ifIndex":5, "connector":"false", "name":"Nu0", "alias":"", "speed":4294967295, "hispeed":0}],
"network-interfaces":[
{"ifIndex":1, "description":"GigabitEthernet1", "physAddress":"500000010000", "ifType":6},
{"ifIndex":2, "description":"GigabitEthernet2", "physAddress":"500000010001", "ifType":6},
{"ifIndex":3, "description":"GigabitEthernet3", "physAddress":"500000010002", "ifType":6},
{"ifIndex":4, "description":"GigabitEthernet4", "physAddress":"500000010003", "ifType":6},
{"ifIndex":5, "description":"Null0", "physAddress":"", "ifType":1}],
"vlans":[
{"id":"1.1", "name":"default", "ifIndex":-1}],
"mac-info":[],
"addresses":[
{"address":"198.51.100.10", "hardware":"500000010002", "ifIndex":3, "originalIfIndex":3},
{"address":"198.51.100.11", "hardware":"500000010001", "ifIndex":3, "originalIfIndex":3},
{"address":"192.0.2.1", "hardware":"001C73000099", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.25", "hardware":"005056A88927", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.77", "hardware":"005056A8387D", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.21", "hardware":"005056A855D5", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.196", "hardware":"500000010000", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.71", "hardware":"005056A81682", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.41", "hardware":"005056A81294", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.70", "hardware":"005056A81CB0", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.40", "hardware":"005056A8621A", "ifIndex":1, "originalIfIndex":1},
{"address":"192.0.2.61", "hardware":"005056A80E98", "ifIndex":1, "originalIfIndex":1}],
"route-tables":{
"routing":[]
},
"networks":[
{"network":"198.51.100.0/24", "ifIndex":"3", "destination":"198.51.100.0", "nextHop":"0.0.0.0",
"hosts":[
{"address":"198.51.100.10", "hardware-address":"500000010002", "type":"HOST", "if-index":"3"},
{"address":"198.51.100.11", "hardware-address":"500000CB38C2", "type":"HOST", "if-index":"3"}]},
{"network":"192.0.2.0/24", "ifIndex":"1", "destination":"192.0.2.0", "nextHop":"0.0.0.0",
"hosts":[
{"address":"192.0.2.1", "hardware-address":"001C73000099", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.25", "hardware-address":"005056A88927", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.77", "hardware-address":"005056A8387D", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.21", "hardware-address":"005056A855D5", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.196", "hardware-address":"500000010000", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.71", "hardware-address":"005056A81682", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.41", "hardware-address":"005056A81294", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.70", "hardware-address":"005056A81CB0", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.40", "hardware-address":"005056A8621A", "type":"HOST", "if-index":"1"},
{"address":"192.0.2.61", "hardware-address":"005056A80E98", "type":"HOST", "if-index":"1"}]}]
},
{"address":"0.0.0.0", "message":"the end"}
]| Field/Line | Description |
|---|---|
|
General information of the discovered device. The key
attributes include:
If the device does not expose specific data, the
corresponding field in the discovery result is empty
(that is, the field displays |
"device-addresses":
["198.51.100.10","198.51.100.11","192.0.2.196"] |
The primary IP addresses used to identify and communicate with the discovered network devices. |
"interfaces":[ {"ifIndex":1, "connector":"true",
"name":"Gi1", "alias":"", "speed":1000000000,
"hispeed":0}, |
Interface details exposed by
the device. The key attributes include:
|
"network-interfaces":[ {"ifIndex":1,
"description":"GigabitEthernet1",
"physAddress":"500000010000",
"ifType":6}, |
Additional attributes of the same network interfaces . The key attributes
include:
|
"vlans":[ {"id":"1.1", "name":"default",
"ifIndex":-1}], |
VLANs configured on the device (if any) and exposed for
discovery. The key attributes include:
|
"mac-info": [] |
MAC address table entries. This field may be empty
(that is, the field displays |
"addresses":[ {"address":"198.51.100.10",
"hardware":"500000010002", "ifIndex":3,
"originalIfIndex":3}, |
The IP addresses assigned to device interfaces and the
MAC address mapped to these IP addresses. The key attributes
include:
|
"route-tables":{ "routing":[] }, |
The routing information known to the device. This field
may be empty (that is, the field displays |
"networks":[ {"network":"198.51.100.0/24",
"ifIndex":"3", "destination":"198.51.100.0",
"nextHop":"0.0.0.0", "hosts":[
{"address":"198.51.100.10",
"hardware-address":"500000010002", "type":"HOST",
"if-index":"3"}, {"address":"198.51.100.11",
"hardware-address":"500000CB38C2", "type":"HOST",
"if-index":"3"}]}, |
Networks and subnets discovered through interface and
routing information. The key attributes include:
|
{ "address": "0.0.0.0", "message": "the end"
} |
Indicates the end of discovery output (not part of actual discovered data). |
The following example shows an SSH discovery result for a router:
[
{
"address": "192.0.2.131",
"fqdn": "host131.bluecat.com"
"type": "HOST",
"id": 2,
"parent-id": 1,
},
{
"address": "192.0.2.60",
"fqdn": "192.0.2.60",
"type": "HOST",
"id": 3,
"parent-id": 1,
},
{
"id": 1,
"parentId": 0,
"type": "ROUTER",
"vendorId": "0",
"vendor": "Synthetic_SSH_Discovered_Device",
"address": "192.0.2.10",
"name": "asa_0",
"location": "",
"description": "Cisco Adaptive Security Appliance Software Version 9.18(1)\\r\\nSSP Operating System Version 2.12(0.31)\\r\\nDevice Manager Version 7.18(1)\\r\\n",
"device-address": [],
"vlans": [],
"mac-info": [],
"addresses": [
{
"ifIndex": 1,
"hardware": "00-11-22-AA-BB-CC",
"address": "192.0.2.131",
"originIfIndex": 1,
"type": "arpEntry"
}
],
"network-interfaces": [
{
"ifIndex": 1,
"description": "GigabitEthernet0/0 (outside)"
}
],
"networks": [
{
"network": "192.0.2.0/24",
"ifIndex": 1,
"hosts": [
{
"address": "192.0.2.131",
"type": "HOST"
}
]
}
]
}
]
| Field/Line | Description |
|---|---|
|
Hosts identified from the seed device. The key
attributes include:
|
|
General information of the seed device selected for
SSH discovery. The key attributes include:
If the device does not expose specific data, the corresponding field in the discovery result is empty. |
|
IP address to MAC address mapping, as obtained from the device's ARP table. |
|
The physical and logical interfaces on the seed device. |
|
The subnets associated with the seed device and the hosts detected within these subnets. |
The following example shows a VMware discovery result:
[
{
"id": 1,
"parentId": 0,
"name": "TestEsxi",
"type": "HOST_SYSTEM",
"addresses": [
{ "address": "192.0.2.101", "hardware": "00:0C:29:C1:00:A8" },
{ "address": "fe80::20c:29ff:fec1:a8", "hardware": "00:0C:29:C1:00:A8" },
{ "address": "192.0.2.100", "hardware": "00:0C:29:D5:BB:B9" }
],
"networks": [
{
"network": "198.51.100.0/24",
"ifIndex": -1,
"destination": "198.51.100.0",
"nextHop": "0.0.0.0",
"hosts": [
{ "address": "198.51.100.4", "type": "HOST" }
]
},
{
"network": "192.0.2.0/24",
"ifIndex": -1,
"destination": "192.0.2.0",
"nextHop": "0.0.0.0",
"hosts": [
{ "address": "192.0.2.100", "type": "HOST" },
{ "address": "192.0.2.101", "type": "HOST" }
]
}
]
},
{ "address": "0.0.0.0", "message": "the end" }
]
| Field/Line | Description |
|---|---|
|
The ESXi host which is the starting point of
discovery (identified by parentId being
0). |
|
The IPv4 addresses (192.0.2.x in
this example), IPv6 addresses (fe80::…
in this example), and MAC addresses assigned to the ESXi
host. |
|
The subnets associated with the ESXi host. The key
attributes include:
|
{ "address": "0.0.0.0", "message": "the end"
} |
Indicates the end of discovery output (not part of actual discovered data). |
About discovery logs
Network Discovery & Visibility generates three types of logs for each discovery task run: Discovery logs (task logs and probe logs), error logs (if available), and exception logs (if available). Each line in the log file contains the following fixed fields:
| Field | Description |
|---|---|
| Time | The time the log message was generated. |
| Message Type | A one-character field indicating the type of log message. The
possible values are:
|
| Component | The component reporting the log message. |
| Address | The IPv4 or IPv6 address associated with the log message. The
possible values are host address, subnet address, or
noAddr when the log message is general
(about the system) such as startup messages. |
| Message | The log message. Note: Progress and
Error messages begin with a number to ensure that such
messages are easily identified even when translated to other
languages.
|
-
SNMP discovery logs: SNMP discovery logs show SNMP communication with network devices, including connection attempts, authentication results (success or failure), OID queries, and data retrieval, among others. Some of the most common issues for which you would refer to SNMP logs are authentication failures, timeouts or unreachable devices, missing or unsupported MIB data, and incomplete topology or device information.
-
VMware discovery logs: VMware discovery logs show interactions with the vCenter API, including authentication attempts, API requests and responses, and object retrieval (hosts, clusters, and virtual machines), among others. Some of the most common issues for which you would refer to VMware discovery logs are authentication failures, insufficient API permissions, missing or incomplete objects, API timeouts, and connectivity issues.
-
SSH discovery logs: SSH discovery logs show SSH connection attempts, authentication results (success or failure), and device type detection, among others. Some of the most common issues for which you would refer to SSH logs are connection and authentication failure, unsupported command outputs, and insufficient privileges.
Discovery log storage:
Each discovery task run generates task logs and probe logs. The storage behavior of these logs varies based on the version you’re running:
- If you’re running v26.1.0: Discovery logs persist and aren’t removed automatically.
- If you’re running v26.1.1: Network Discovery & Visibility
automatically deletes the oldest discovery logs until the total size is within
the limit. The default storage limit is 5000 MB (approximately 5 GB). You change
the storage limit in a configuration file
/portal/builtin/workflows/network_discovery/new_nd/config/discovery_logs.json, where you set the value ofstorageLimitMBto the desired storage limit (in MB).Important: For the changes to take effect, you must save the file and then restart the Network Discovery & Visibility container.Logs are removed individually (meaning, a task log or probe log from a discovery task run might remain after the other is removed). Logs and results are managed independently: removing a log doesn’t delete the associated result, and deleting a result doesn’t delete its associated logs.
Additional actions you can perform
In addition to viewing the discovery results and logs, you can perform the following actions from the task-name page:
-
Delete one or more task results—in the expanded details section for the task result, select Delete. Alternatively, select the vertical ellipsis icon for the task result, then select Delete. A confirmation window appears asking you to confirm the deletion. Once you confirm by selecting Delete, the task result is permanently deleted.Note: In v26.1.0, you cannot delete the associated logs manually, and deleting a result doesn’t delete its associated logs automatically. In v26.1.1, Network Discovery & Visibility removes the oldest discovery logs automatically when the storage limit exceeds. For details, refer to Discovery log storage.
- Similar to other tables in Integrity, you can search for specific results in the table by name, sort and customize the table, as well as filter, refresh, and download table data.