Configuration Guide for Cisco NCS 1001, IOS XR Release 25.x.x
This topic explains how management interfaces provide device access for configuration, discovery, monitoring, and operational data collection on Cisco NCS 1001.
Management interfaces are device access points that support management connectivity, neighbor discovery, and operational visibility for Cisco NCS 1001.
Dual management Ethernet interfaces are independent Cisco IOS XR interfaces that let you connect the RJ45 and optical SFP management ports to different switches on the same or different subnets.
Starting with release R6.5.1, different ports from the Ethernet switch—MGMT RJ45 and optical SFP MGMT—connect to the CPU. In Cisco IOS XR, the two management Ethernet interfaces correspond to different management ports.
MgmtEth0/RP0/CPU0/0 :RJ45 port.
MgmtEth0/RP0/CPU0/1 :SFP port.
Review these restrictions before you use the optical SFP management interface.
iPXE is not supported over the optical interface during power-on.
Upgrades from earlier releases, which use only the SFP management interface, can lose management connectivity. If connectivity is lost, configure the device through the console port.
Upgrade the BIOS and reload the 0/RP0 location before using both management interfaces.
This example shows the output of the show running-config command for management interfaces.
RP/0/RP0/CPU0:Device#show running-config
interface MgmtEth0/RP0/CPU0/0
ipv4 address 192.0.2.10 255.255.255.0
!
interface MgmtEth0/RP0/CPU0/1
ipv6 address 2001:DB8:1::1/64
ipv6 enable
!
interface MgmtEth0/RP0/OSC1/0
shutdown
!
interface MgmtEth0/RP0/OSC2/0
shutdown
!
interface MgmtEth0/RP0/OSC3/0
shutdown
!Link Layer Discovery Protocol (LLDP) support on management interfaces is a neighbor discovery capability that lets a system advertise and learn neighbor information through the management network.
The system advertises LLDP type-length-value (TLV) details over the management network. Other devices use these details to learn about this device.
LLDP provides neighbor discovery for non-Cisco devices and supports topology discovery for Operations, Administration, and Maintenance (OAM) workflows.
Use this comparison to understand which discovery protocol applies to Cisco and non-Cisco devices.
This table compares Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP) for device discovery purposes.
| Protocol |
Scope |
Purpose |
|---|---|---|
| CDP |
Runs over Layer 2 on Cisco devices such as routers, bridges, access servers, and switches. |
Lets network management applications discover and learn about Cisco devices connected to the network. |
| LLDP |
Runs over Layer 2 and supports systems that use different network layer protocols. |
Lets network management applications discover and learn about non-Cisco devices connected to the network. |
Use these object identifiers (OIDs) to identify LLDP information that the system supports for non-Cisco monitoring tools.
LLDP provides information about physical network connections that monitoring tools can retrieve through Simple Network Management Protocol (SNMP).
The system supports these LLDP OIDs:
1.0.8802.1.1.2.1.4.1.1.4
1.0.8802.1.1.2.1.4.1.1.5
1.0.8802.1.1.2.1.4.1.1.6
1.0.8802.1.1.2.1.4.1.1.7
1.0.8802.1.1.2.1.4.1.1.8
1.0.8802.1.1.2.1.4.1.1.9
1.0.8802.1.1.2.1.4.1.1.10
1.0.8802.1.1.2.1.4.1.1.11
1.0.8802.1.1.2.1.4.1.1.12
Use these requirements to confirm that LLDP behavior and operational data access meet your management interface needs.
LLDP full-stack functionality is supported on all three management interfaces in the Cisco NCS 1001 system.
You can enable or disable LLDP selectively on any management interface.
You can enable or disable LLDP transmit or receive functionality at the management interface level.
Information gathered through LLDP can be stored in the device Management Information Database (MIB) and queried with SNMP.
LLDP operational data is available in both the command-line interface (CLI) and the NETCONF and YANG interface.
Use these values when you configure LLDP globally for management interfaces.
| Attribute |
Default |
Range |
Description |
|---|---|---|---|
| Hold time |
120 seconds |
0 to 65535 seconds |
Specifies how long an LLDP device maintains neighbor information before discarding it. |
| Reinit |
2 seconds |
2 to 5 seconds |
Specifies the delay for LLDP initialization on an interface. |
| Timer |
30 seconds |
5 to 65534 seconds |
Specifies the rate at which LLDP packets are sent. |
Configure LLDP globally to enable transmit and receive operations on all the interfaces that support LLDP.
You can override global LLDP behavior at the interface level to disable receive or transmit operations.
For more information about global attributes, see LLDP global attributes.
| 1. | Enter global configuration mode. Example: |
|
| 2. | Use the lldp management enable command to enable LLDP on management interfaces. Example: |
|
| 3. | Configure LLDP timing attributes. Example: |
|
| 4. | Commit the configuration and exit global configuration mode. Example: |
LLDP is enabled globally for both the MgmtEth0/RP0/CPU0/0 and MgmtEth0/RP0/CPU0/1 management interfaces.
Verify LLDP configuration to confirm that the device advertises and receives management interface neighbor information.
| 1. | Use the show running-config lldp command to display the running LLDP configuration. Example: |
|
| 2. | Use the show lldp interface command to display LLDP interface state. Example: |
|
| 3. | Use the show lldp neighbors command to display LLDP neighbor information. Example: |
The output shows the LLDP interface state and neighbor information for the management interfaces.
Enable LLDP on a management interface to allow the interface to participate in neighbor discovery.
| 1. | Enter global configuration mode. Example: |
|
| 2. | Enter the management interface configuration mode. Example: |
|
| 3. | Use the lldp enable to enable LLDP on the management interface. Example: |
|
| 4. | Commit the configuration and exit interface configuration mode. Example: |
LLDP is enabled on the specified management interface.
Disable LLDP transmit operations to prevent a management interface from advertising local neighbor discovery information.
| 1. | Enter the global configuration mode. Example: |
|
| 2. | Enter the management interface configuration mode. Example: |
|
| 3. | Use the lldp transmit disable command to disable LLDP transmit operations. Example: |
|
| 4. | Commit the configuration and exit interface configuration mode. Example: |
The management interface no longer transmits LLDP advertisements.
Disable LLDP receive operations to prevent a management interface from learning neighbor discovery information.
| 1. | Enter the global configuration mode. Example: |
|
| 2. | Enter the management interface configuration mode. Example: |
|
| 3. | Use the lldp receive disable command to disable LLDP receive operations. Example: |
|
| 4. | Commit the configuration and exit interface configuration mode. Example: |
The management interface no longer receives LLDP advertisements.
Use these commands when you troubleshoot LLDP functionality.
show lldp traffic
debug lldp all
debug lldp errors
debug lldp events
debug lldp packets
debug lldp tlvs
debug lldp trace
debug lldp verbose