* Configured State
|
The management state of the device. Options are
-
UNMANAGED—Cisco Crosswork Optimization Engine is not monitoring the device.
-
DOWN—The device is being managed and is down.
-
UP—The device is being managed and is up.
|
Reachability Check
|
Determines whether Cisco Crosswork Optimization Engine performs reachability checks on the device. Options are:
Cisco recommends that you always set this to ENABLE.
|
Credential Profile
|
The name of the credential profile assigned to the device and used to access it for data collection and configuration changes.
For example: nso23 or srpce123.
|
* Inventory Key Type
|
The type of identification key for the device. You must choose one of the available types. In all cases other than UUID, you must enter the corresponding key field with a unique ID value. For example: If you choose HOST_NAME as the * Inventory Key Type, you must fill in the Host Name field with the unique host name of the device.
|
* Host Name
|
The hostname of the device. Required only if * Inventory Key Type is HOST_NAME. Otherwise, Cisco Crosswork Optimization Engine discovers it and updates it.
|
Inventory ID
|
Inventory ID value for the device. Required only if * Inventory Key Type is INVENTORY_ID.
|
UUID
|
Universally unique identifier (UUID) for the device. If you choose UUID as the * Inventory Key Type, leave this field blank.
|
Serial Number
|
Serial number for the device. Required only if * Inventory Key Type is SERIAL_NUMBER.
|
Node IP
|
Node IP value for the device. Required only if * Inventory Key Type is NODE_IP.
|
MAC Address
|
MAC address for the device. Required only if * Inventory Key Type is MAC.
|
* Capability
|
The capabilities that allow collection of device data and that are configured on the device. You must select at least SNMP, as this is a required capability. The device will not be onboarded if SNMP is not configured. Other options are YANG_MDT, TL1, YANG_CLI, and YANG-EPNM. The capabilities you select will depend on the device software type and version.
|
Tags
|
The available tags to assign to the device.
Use device tags to group devices for monitoring, and to provide additional information that might be of interest to other
users, such as the device’s physical location and its administrator’s email ID. For more information, see Manage Device Tags.
|
Connectivity Details
|
Protocol
|
The connectivity protocols used by the device. Choices are: SSH, SNMP, NETCONF, TELNET, HTTP, and HTTPS..
To add more connectivity protocols for this device, click at the end of the first row in the Connectivity Details panel. To delete a protocol you have entered, click shown next to that row in the panel.
You can enter as many sets of connectivity details as you want, including multiple sets for the same protocol. You must enter
details for at least SSH and SNMP. If you do not configure SNMP, the device will not be on-boarded. If you want to manage the device (or you are managing XR devices), you must enter details
for NETCONF. TELNET connectivity is optional.
|
* IPv4 Address / Subnet Mask
|
Enter the device's IPv4 address and CIDR subnet mask.
|
IPv6 Address / Subnet Mask
|
Enter the device's IPv6 address and subnet mask.
|
* Port
|
The port used for this connectivity protocol. Each protocol is mapped to a port, so be sure to enter the port number that
corresponds to the Protocol you chose. The standard port assignments for each protocol are:
-
SSH: 22
-
SNMP: 161
-
NETCONF: 830
-
TELNET: 23
-
HTTP: 80
-
HTTPS: 443
|
Timeout
|
The elapsed time (in seconds) before communication attempts using this protocol will time out. The default value is 30 seconds.
For XE devices using NETCONF, the recommended minimum timeout value is 90 seconds. For all other devices and protocols, the
recommended minimum timeout value is 60 seconds.
|
Routing Info
|
ISIS System ID
|
The device's IS-IS system ID. This ID identifies the router in an IS-IS topology, and is required for SR-PCE integration.
|
OSPF Router ID
|
The device's OSPF router ID. This ID identifies the router in an OSPF topology, and is required for SR-PCE integration.
|
Streaming Telemetry Config
|
Telemetry Interface Source VRF
|
Name of the VRF in whose context Model Driven Telemetry (MDT) traffic is routed.
|
Location
All location fields are optional, with the exception of Longitude and Latitude, which are required for a correct geographical view of your network topology.
|
Longitude, Latitude
|
Entries in these fields are recommended. Without Longitude and Latitude values, the topology map's geographical view shows all devices and links bunched together at the same spot. With these values,
the map can present the correct geographical location of each device and its links to other nodes.
|
Altitude
|
The altitude, in feet or meters, at which the device is located. For example, 123.
|
Providers and Access
|
Local Config: Device Key and Provider
|
This field is mandatory only when mapping an NSO provider. The Device Key will automatically populate and the Credential Profile
appears.
For CSV entry, use ROBOT_PROVIDER_LOCAL_CONFIG and enter the Provider name.
|
Compute Config: Device Key and Provider
|
(Optional) Provider name used for topology computation. Choose a provider from the list.
For CSV entry, use ROBOT_PROVIDER_COMPUTE and enter the Provider name.
|