System Setup and Software Installation Guide for Cisco NCS 1010, IOS XR Releases

PDF

Pre-setup requirements for Cisco NCS 1010

Updated: June 17, 2026

Want to summarize with AI?

Provides pre-setup requirements for Cisco NCS 1010, including console access, management interface preparation, and required setup tasks before boot verification.

Complete these prerequisite tasks to prepare the NCS 1010 for seamless setup.

Figure 1. Pre-setup Workflow for the Cisco NCS 1010

Connect the console port to a terminal

Connect your terminal or PC to the Cisco NCS 1010 console port and configure terminal settings for direct device access.

The console port allows you to log into the NCS 1010 without a network connection, using an emulation program such as HyperTerminal.

Procedure

Connect the console (or rollover) cable to the console port on the NCS 1010.

Use the correct adapter to connect the other end of the cable to your terminal or PC.

Launch the terminal session.

In the COM1 Properties window, select Port Settings tab, and enter these settings:


Setting	Value
Speed	9600
Data Bits	8
Parity	None
Stop bits	1
Flow Control	None

Click OK.

You should see a blinking cursor in the HyperTerminal window indicating successful connection to the console port.

The terminal or PC is connected to the console port, and the terminal session is ready for initial access.

Configure the management interface

Use this procedure to configure the management interface.

The management interface can be used for system management and remote communication. To use the management interface for system management, you must configure an IP address and subnet mask. To use the management interface for remote communication, you must configure a static route. Use this procedure when NCS 1010 chassis is not booted using ZTP.

Before you begin

Consult your network administrator to procure IP addresses and a subnet mask for the management interface.
Ensure that the management interface is connected to the management network.

Procedure

	1.	Enter configuration mode. configure Example: `RP/0/RP0/CPU0:ios#configure` Enters IOS XR configuration mode.
	2.	Enter management interface configuration mode. interface mgmtEth 0/RP0/CPU0/0 Example: `RP/0/RP0/CPU0:ios(config)#interface mgmtEth 0/RP0/CPU0/0` Enters interface configuration mode for the management interface.
	3.	Configure the IPv4 address and subnet mask. ipv4 address 192.0.2.254 255.255.255.0 Example: `RP/0/RP0/CPU0:ios(config-if)#ipv4 address 192.0.2.254 255.255.255.0` Assigns an IP address and a subnet mask to the management interface.
	4.	Enable the interface. no shutdown Example: `RP/0/RP0/CPU0:ios(config-if)#no shutdown` Places the management interface in an "up" state.
	5.	Exit interface configuration mode. exit Example: `RP/0/RP0/CPU0:ios(config-if)#exit` Exits the management interface configuration mode.
	6.	Configure a static route. ncs1010 static address-family ipv4 unicast 0.0.0.0/0 198.51.100.4 Example: `RP/0/RP0/CPU0:ios(config)#ncs1010 static address-family ipv4 unicast 0.0.0.0/0 198.51.100.4` Specifies the IP address of the default gateway to configure a static route. This IP address must be used for communication with devices on other networks.
	7.	Save or exit the configuration session. commit -Saves the configuration changes and remains within the configuration session. end -Prompts user to take one of these actions: Yes-Saves configuration changes and exits the configuration session. No-Exits the configuration session without committing the configuration changes. Cancel-Remains in the configuration session without committing the configuration changes.

The configure the management interface task is complete.

What to do next

Connect the management interface to the Ethernet network. Establish a Configure SSH or Configure Telnet connection to the management interface using its IP address.

LLDP support on the management interface

The Link Layer Discovery Protocol (LLDP) support on management interface feature requires a system to form LLDP neighbor relationship over the system management interface, through which it advertises and learns LLDP neighbor information. This information about neighbors used to learn about the neighbors and in turn the topology of the devices for Operations, Administration, and Maintenance (OAM) purposes.

Advantages of LLDP

Provides support on non-Cisco devices.
Enables neighbor discovery between non-Cisco devices.

Limitation

When you disable LLDP globally, the LLDP gets disabled on all the interfaces.

Note

By default, LLDP is enabled for NCS 1010. But when you enable and disable LLDP in the global configuration mode, LLDP gets disabled on all the interfaces.

Workaround: You must enable LLDP globally or reload the NCS1010.

Cisco Discovery Protocol (CDP) vs LLDP

The CDP is a device discovery protocol that runs over Layer 2. Layer 2 is also known as the data link layer that runs on all Cisco devices, such as routers, bridges, access servers, and switches. This protocol allows the network management applications to automatically discover and learn about other Cisco devices that connect to the network.

The LLDP is also a device discovery protocol that runs over Layer 2. This protocol allows the network management applications to automatically discover and learn about other non-Cisco devices that connect to the network.

Interoperability between non-Cisco devices using LLDP

LLDP is also a neighbor discovery protocol that is used by network devices to advertise information about themselves to other devices on the network. This protocol runs over the data link layer, which allows two systems running different network layer protocols to learn about each other.

With LLDP, you can also access the information about a particular physical network connection. If you use a non-Cisco monitoring tool (through SNMP), LLDP helps you identify the Object Identifiers (OIDs) that the system supports. These OIDs are supported:

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

Neighbor Discovery

System advertises the LLDP TLV (Type Length Value) details over the management network using which other devices in the management network can learn about this device.

Configuring LLDP

LLDP full stack functionality is supported on all three management interfaces that are supported in NCS 1010.
You can selectively enable or disable LLDP on any of the management interfaces on demand.
You can selectively enable or disable LLDP transmit or receive functionality at the management interface level.
Information gathered using LLDP can be stored in the device Management Information Database (MIB) and queried with the Simple Network Management protocol (SNMP).
LLDP operational data is available in both CLI and netconf-yang interface.

Enabling LLDP Globally

When you enable LLDP globally, all interfaces that support LLDP are automatically enabled for both transmit and receive operations.

Note

You can override this default operation at the interface to disable receive or transmit operations.

This table describes the global LLDP attributes that you can configure:

Table 1.
Attribute	Default	Range	Description
Holdtime	120	0-65535	Specifies the holdtime (in sec). Holdtime refers to the time or duration that an LLDP device maintains the neighbor information before discarding.
Reinit	2	2-5	Delay (in sec) for LLDP initialization on any interface
Timer	30	5-65534	Specifies the rate at which LLDP packets are sent (in sec)

Configure LLDP globally

Enable LLDP globally on all three management interfaces.

When you enable LLDP globally, all interfaces that support LLDP are automatically enabled for both transmit and receive operations.

Note

You can override this default operation at the interface to disable receive or transmit operations.

Procedure

	1.	Enter global configuration mode. configure terminal Example: `RP/0/RP0/CPU0:ios#configure terminal`
	2.	Enable LLDP on the management interfaces. lldp management enable Example: `RP/0/RP0/CPU0:ios(config)#lldp management enable`
	3.	Set the LLDP holdtime. lldp holdtime 30 Example: `RP/0/RP0/CPU0:ios(config)#lldp holdtime 30`
	4.	Set the LLDP reinitialization delay. lldp reinit 2 Example: `RP/0/RP0/CPU0:ios(config)#lldp reinit 2`
	5.	Commit the configuration. commit Example: `RP/0/RP0/CPU0:ios(config)#commit`

The global LLDP configuration enables LLDP on all the three management interfaces.

Verify LLDP configuration and data

Verify the LLDP configuration and operational data.

Procedure

Verify the LLDP running configuration.

show running-config lldp

Example:

RP/0/RP0/CPU0:ios#show running-config lldp
Tue Dec 10 10:36:11.567 UTC
lldp
timer 30
reinit 2
holdtime 120
management enable
!

Verify the LLDP interface data.

show lldp interface

Example:

RP/0/RP0/CPU0:ios#show lldp interface
Mon Nov 11 14:33:58.982 IST


MgmtEth0/RP0/CPU0/0:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


MgmtEth0/RP0/CPU0/2:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


GigabitEthernet0/0/0/0:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME

Verify the LLDP neighbor data.

show lldp neighbors

Example:

RP/0/RP0/CPU0ios:M-131#show lldp neighbors 
Mon Dec 9 14:57:55.915 IST
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

Device ID Local Intf Hold-time Capability Port ID
P1C_DT_01.cisco.com GigabitEthernet0/0/0/0 120 R GigabitEthernet0/0/0/0
NCS1004-HH-10 MgmtEth0/RP0/CPU0/2 60 R MgmtEth0/RP0/CPU0/2

Total entries displayed: 2

where [DISABLED] shows that the LLDP is disabled on the interface MgmtEth0/RP0/CPU0/0.

Note

If the RCOM interface is enabled, the output of show lldp neighbors command would include the entries for both LLDP neighbours and remote connect neighbours.

The LLDP running configuration, interface data, and neighbor data are verified.

Configure LLDP on a management interface

Enable LLDP at the management interface level.

Procedure

	1.	Enter the management interface configuration mode. interface mgmtEth 0/RP0/CPU0/X Example: `RP/0/RP0/CPU0:ios(config)#interface mgmtEth 0/RP0/CPU0/X`
	2.	Enable LLDP on the management interface. lldp enable Example: `RP/0/RP0/CPU0:ios(config-if)#lldp enable`
	3.	Commit the configuration. commit Example: `RP/0/RP0/CPU0:ios(config-if)#commit`

LLDP is configured at the management interface level.

Disable LLDP transmit and receive operations

Disable LLDP transmit operations, receive operations, or both at a specified management interface.

Procedure

	1.	Enter the management interface configuration mode. interface mgmtEth 0/RP0/CPU0/X Example: `RP/0/RP0/CPU0:ios(config)#interface mgmtEth 0/RP0/CPU0/X`
	2.	Disable LLDP transmit operations at the specified management interface. lldp transmit disable Example: `RP/0/RP0/CPU0:ios(config-if)#lldp transmit disable`
	3.	Disable LLDP receive operations at the specified management interface. lldp receive disable Example: `RP/0/RP0/CPU0:ios(config-if)#lldp receive disable`
	4.	Commit the configuration. commit Example: `RP/0/RP0/CPU0:ios(config-if)#commit`

LLDP transmit or receive operations are disabled at the specified management interface.

LLDP traffic and debug commands

Use these commands for debugging issues in the LLDP functionality.

Table 2. LLDP troubleshooting commands
Command	Description
show lldp traffic	Displays statistics for LLDP traffic.
debug lldp all	Enables all LLDP debugging information.
debug lldp errors	Enables debugging information for LLDP errors.
debug lldp events	Enables debugging information for LLDP events.
debug lldp packets	Enables debugging information for LLDP packets.
debug lldp tlvs	Enables debugging information for LLDP TLVs.
debug lldp trace	Enables LLDP trace debugging information.
debug lldp verbose	Enables verbose LLDP debugging information.

Configure Telnet

Use this procedure to configure Telnet.

This procedure allows you to establish a telnet session to the management interface using its IP address. Use this procedure when NCS 1010 chassis is not booted using ZTP.

Before you begin

Ensure that two xr-telnet-* rpms are installed. .

Procedure

	1.	Enter configuration mode. configure Example: `RP/0/RP0/CPU0:ios#configure` Enters the configuration mode.
	2.	Specify the number of allowable Telnet servers. telnet ipv4 server max-servers 10 Example: `RP/0/RP0/CPU0:ios(config)#telnet ipv4 server max-servers 10` Specifies the number of allowable telnet servers (up to 100). By default, telnet servers are not allowed. You must configure this command to enable the use of telnet servers.
	3.	Save or exit the configuration session. commit -Saves the configuration changes and remains within the configuration session. end -Prompts user to take one of these actions: Yes-Saves configuration changes and exits the configuration session. No-Exits the configuration session without committing the configuration changes. Cancel-Remains in the configuration session without committing the configuration changes.

The configure Telnet task is complete.

Configure SSH

Use this procedure to configure SSH.

This procedure allows you to establish an SSH session to the management interface using its IP address. Use this procedure when NCS 1010 chassis is not booted using ZTP.

Before you begin

Generate the crypto key for SSH using the crypto key generate dsa command.

Procedure

	1.	Enter configuration mode. configure Example: `RP/0/RP0/CPU0:ios#configure` Enters the configuration mode.
	2.	Enable SSH server version 2. ssh server v2 Example: `RP/0/RP0/CPU0:ios(config)# ssh server v2` Enables the SSH server to accept only SSHv2 client connections.
	3.	Save or exit the configuration session. commit -Saves the configuration changes and remains within the configuration session. end -Prompts the user to take one of these actions: Yes-Saves configuration changes and exits the configuration session. No-Exits the configuration session without committing the configuration changes. Cancel-Remains in the configuration session without committing the configuration changes.

The configure SSH task is complete.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.