R11.0a-March2023
Fine Tune Network Issues
Creating and maintaining a domain with all devices properly discovered and accessible is the key to keeping system data up-to-date, ensuring data accuracy, and using many features, such as path and map.
Fine Tune provides an overview of how devices are discovered and where you can get started to fix all the access issues. The devices listed in each category are updated as soon as a discovery task or a benchmark task is completed, including both the on-demand and scheduled discovery/benchmark. It's recommended to check and maintain the Fine Tune at least once a week or whenever a discovery/benchmark task is completed.
- Log in to the Domain Management page, and then click Fine Tune on the Start Page.
- Resolve the issues under the following categories:
- Fully Accessed via CLI — the devices discovered successfully during a discovery/benchmark and do not need further actions to tune or rediscover.
- Latest CLI configuration Retrieval Failed — Discovered devices that NetBrain successfully retrieved configurations via CLI before but failed to retrieve CLI configuration in the last Discover/Benchmark task.
- SNMP-Only Devices — the devices accessed by SNMP only but failed to be accessed via Telnet/SSH.
- Missed Devices — the devices existing in the current domain but failed to be verified during a discover/benchmark task.
- Unknown SNMP SysObjectID — the devices whose SysObjectIDs are not defined in the Vendor Model table.
- Unknown IP — the IP addresses that cannot be accessed via Telnet/SSH and SNMP in the Discover via Seed Routers method during a discover/benchmark task.
- SSH Fingerprint Check Failed — the devices whose current fingerprint keys differ from the latest ones retrieved during live access.
- MPLS Cloud — used to enable A-B path across an MPLS network not managed by your organization.
- Hostname-Changed Device — the device whose hostname is changed and exists with more than one hostname in a domain.
See also: