NCS 1010 setup and initial configuration | Bring Up Your NCS 1000 Devices | Cisco Optical Automation Solution Workflow, IOS XR Release 26.1.1

This section explains NCS 1010 setup and initial configuration. Use it to understand the purpose, behavior, and dependencies that support the related NCS 1000 platform workflow.

This subsection covers the essential steps to prepare and configure the NCS 1010 device for operation.

Boot the chassis and access the XR console.
Complete day-0 configuration using the recommended manual approach or ZTP.
Configure management, loopback, and neighbor interfaces based on the topology.

NCS1010 bootup process

After installing the hardware, boot the Cisco NCS 1010 system. Connect to the XR console port and power on the system. NCS 1010 completes the boot process using the pre-installed OS image. If no image is available, NCS 1010 can be booted using iPXE or an external bootable USB drive.

Use any one of the tasks to boot the NCS 1010 chassis.

Boot NCS 1010 using Console (Recommended)
Connect Console Port to Terminal: Establish a console connection to the device and follow procedure mention in Day 0 configuration.
Boot NCS 1010 Using USB Drive
Boot Using iPXE

Once booted, please verify the system using the steps in the Cisco NCS 1010 Deployment Guide.

Configure NCS 1010 day-0 settings

Prepare the NCS 1010 for day-1 configuration and network onboarding by completing the day-0 sub tasks.

Procedure

	1.	Complete the manual bring-up workflow. See Manually bring up NCS1000.
	2.	Configure NTP for time synchronization. See NTP server configuration.
	3.	Configure SNMP if monitoring is required. See SNMP configuration (optional).

Manually bring up NCS1010, NCS1014, and NCS1004

Complete the manual day-0 bring-up for NCS1010, NCS1014, and NCS1004 by following the prerequisite setup and configuration tasks in sequence.

NCS1010 supports two different approaches for bring-up: manual and ZTP. This workflow covers the manual approach.

Before you begin

Ensure that the NCS 1010 bring-up configuration is completed on all nodes in the topology before proceeding with this section.
The interfaces come up only after the configuration is applied across all nodes and the fiber connections are completed correctly.

Follow these steps to complete the manual day-0 bring-up for NCS 1010, NCS 1014, and NCS 1004.

Procedure

	1.	Complete prerequisites and access setup. See Prepare access and initial credentials.
	2.	Configure management and loopback addressing. See Configure management and loopback addressing.
	3.	Configure OSPF and verify neighbors. See Configure OSPF and verify neighbors.
	4.	Configure routing policies and BGP, then update OSPF. See Configure routing policies, static routes, and BGP.
	5.	Validate controllers, alarms, and span loss. See Validate controllers and alarms.

The NCS1010/NCS1014/NCS1004 system is brought up to day-0 configuration and ready for downstream workflows.

Prepare access and initial credentials on NCS1010

Establish console access, set root credentials, and apply a hostname so the node can be configured.

Follow these steps to prepare access and initial credentials on the node.

Procedure

	1.	Configure DHCP settings if required for IP address assignment. A DHCP server is required for this configuration. For more details, see Cisco NCS 1010 Deployment Guide, Cisco IOS XR Releases.
	2.	Connect to the node through the console port, configure the root-system username, and use these credentials to log in later. Example: `--------------------- Enter root-system username: xxxxxx Enter secret: Enter secret again: Use the 'configure' command to modify this configuration. User Access Verification Username: Password: xxxxxx ---------------------`
	3.	Assign a hostname to the node. Example: `RP/0/RP0/CPU0:ios#config RP/0/RP0/CPU0:ios(config)#hostname onc-oltc-225-70 RP/0/RP0/CPU0:ios(config)#commit RP/0/RP0/CPU0:ios(config)#end`

The node is accessible with root credentials and has a hostname assigned.

What to do next

Next, complete Configure management and loopback addressing.

Configure management and loopback addressing

Assign management and loopback IP addressing and verify interface status before and after addressing.

Before you begin

Complete Prepare access and initial credentials on NCS1010.
Refer to the Table 1 for sample IP address configuration.

Follow these steps to configure management and loopback addressing.

Procedure

View the interface status before addressing.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70#show ipv4 interface brief

Table 1. Interface status before addressing
Interface	IP-Address	Status	Protocol	Vrf-Name
Loopback1	unassigned	Down	Down	default
GigabitEthernet0/0/0/0	unassigned	Down	Down	default
MgmtEth0/RP0/CPU0/0	unassigned	Down	Down	default
PTP0/RP0/CPU0/0	unassigned	Down	Down	default
MgmtEth0/RP0/CPU0/1	unassigned	Down	Down	default
PTP0/RP0/CPU0/1	unassigned	Down	Down	default
MgmtEth0/RP0/CPU0/2	unassigned	Down	Down	default
MgmtEth0/RP0/RCOM0/0	unassigned	Down	Down	default

Assign IP addresses for management, GigabitEthernet, and Loopback interfaces based on the addressing plan.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70#configure
RP/0/RP0/CPU0:onc-oltc-225-70(config)#interface Loopback1
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# ipv4 address 10.58.253.94 255.255.255.255
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# interface MgmtEth0/RP0/CPU0/0
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# ipv4 address 10.58.225.70 255.255.255.0

Configure the management interface.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70(config-if)#interface MgmtEth0/RP0/CPU0/2
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# ipv4 address 192.168.21.2 255.255.255.0

These items outline the management interface design choices by node type for this topology document

OLT: MgmtEth0/RP0/CPU0/2 required for DHCP relay and remote management.
ILA: MgmtEth0/RP0/CPU0/2 required for neighbor connectivity.

This table describes the management interface requirements:

Table 2. Interface requirements
Node type	MgmtEth0/RP0/CPU0/2	Required	Purpose
OLT	Yes	Required	DHCP relay and remote management
ILA	Yes	Required	Neighbor connectivity
TXP shelves	No	Not required	Not applicable

Configure loopback addresses on both NCS 1010 OLTs participating in Cisco Optical Site Manager HA.

Example:


RP/0/RP0/CPU0:onc-oltc-225-58(config)#interface Loopback0
RP/0/RP0/CPU0:onc-oltc-225-58(config-if)#ipv4 address 10.58.253.90 255.255.255.255
RP/0/RP0/CPU0:onc-oltc-225-68(config)#interface Loopback0
RP/0/RP0/CPU0:onc-oltc-225-68(config-if)#ipv4 address 10.58.253.90 255.255.255.255

Example:

Note

These IP address should be same on the NCS 1010 HA hosts.

Configure neighbor connectivity for OLT and ILA nodes.

Not required for TXP shelves for NCS 1014 and NCS 1004.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70(config-if)#interface GigabitEthernet0/0/0/0
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# ipv4 point-to-point
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# ipv4 unnumbered Loopback1
RP/0/RP0/CPU0:onc-oltc-225-70(config-if)# lldp
RP/0/RP0/CPU0:onc-oltc-225-70(config-lldp)#  enable
RP/0/RP0/CPU0:onc-oltc-225-70(config-lldp)#  commit

For ILA nodes, configure the second neighbor interface.

Example:


RP/0/RP0/CPU0:onc-ilac-225-69(config-if)#interface GigabitEthernet0/0/0/2
RP/0/RP0/CPU0:onc-ilac-225-69(config-if)# ipv4 point-to-point
RP/0/RP0/CPU0:onc-ilac-225-69 (config-if)# ipv4 unnumbered Loopback1
RP/0/RP0/CPU0:onc-ilac-225-69 (config-if)# lldp
RP/0/RP0/CPU0:onc-ilac-225-69 (config-lldp)#  enable
RP/0/RP0/CPU0:onc-ilac-225-69 (config-lldp)#  commit
RP/0/RP0/CPU0:onc-ilac-225-69 (config-lldp)#  end

View the interface status after addressing.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70#show ipv4 interface brief

Table 3. Interface status after addressing
Interface	IP-Address	Status	Protocol	Vrf-Name
Loopback1	10.58.253.94	Up	Up	Default
GigabitEthernet0/0/0/0	10.58.253.94	Up	Up	Default
MgmtEth0/RP0/CPU0/0	10.58.225.70	Up	Up	Default
PTP0/RP0/CPU0/0	unassigned	Down	Down	Default
MgmtEth0/RP0/CPU0/1	unassigned	Down	Down	Default
PTP0/RP0/CPU0/1	unassigned	Down	Down	Default
MgmtEth0/RP0/CPU0/2	192.168.21.2	Up	Up	Default
MgmtEth0/RP0/RCOM0/0	unassigned	Down	Down	Default

Configure SSH (secure shell).

Example:


RP/0/RP0/CPU0:onc-oltc-225-70(config)#config
RP/0/RP0/CPU0:onc-oltc-225-70(config)#ssh server rate-limit 600
RP/0/RP0/CPU0:onc-oltc-225-70(config)#ssh server session-limit 110
RP/0/RP0/CPU0:onc-oltc-225-70(config)#ssh server v2
RP/0/RP0/CPU0:onc-oltc-225-70(config)#ssh server vrf default
RP/0/RP0/CPU0:onc-oltc-225-70(config)#ssh server netconf vrf default
RP/0/RP0/CPU0:onc-oltc-225-70(config)#commit

Configure NETCONF-YANG over SSH to enable device management by Cisco Optical Site Manager.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70(config)#netconf agent tty
RP/0/RP0/CPU0:onc-oltc-225-70(config-netconf-tty)#netconf-yang agent
RP/0/RP0/CPU0:onc-oltc-225-70(config-ncy-agent)# ssh
RP/0/RP0/CPU0:onc-oltc-225-70(config)#commit

IP addresses are assigned to the management and loopback interfaces.

What to do next

Next, complete Configure OSPF and verify neighbors.

Configure OSPF and verify neighbors

Configure OSPF on OLT and ILA nodes and verify neighbor adjacencies. The neighbours are visible only after the configuration is applied across all nodes and the fiber connections are completed correctly.

Follow these steps to configure OSPF and verify neighbors.

Procedure

Configure OSPF in NCS1010 OLT nodes.

Example:

RP/0/RP0/CPU0:onc-oltc-225-70(config)#router ospf 1
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# distribute link-state
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# router-id 10.58.253.94
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# network point-to-point
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# area 0
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar)#  interface Loopback1
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar-if)#  interface GigabitEthernet0/0/0/0    
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar-if)#commit
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar-if)# end

Note

router-id must be modified for each node.

Configuring OSPF settings for the interface on the ILA node and commit the changes.

Example:

RP/0/RP0/CPU0:onc-oltc-225-70(config)#router ospf 1
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# distribute link-state
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# router-id 10.58.253.94
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# network point-to-point
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# area 0
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar)#  interface Loopback1
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar-if)#  interface GigabitEthernet0/0/0/0    
RP/0/RP0/CPU0: onc-ilac-225-69(config-ospf-ar-if)#  interface GigabitEthernet0/0/0/2
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar-if)#commit
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf-ar-if)# end

Note

router-id must be modified for each node.

View OSPF neighbors using the show ospf neighbor command.

Example:


RP/0/RP0/CPU0:OLT-R-C-SITE-4#show ospf neighbor 
Mon Jul 25 09:22:58.684 UTC

* Indicates MADJ interface
# Indicates Neighbor awaiting BFD session up
Neighbors for OSPF 1
Total neighbor count: 2


Neighbor ID     Pri    State           Dead Time   Address              Interface
10.58.253.94     1     FULL/  -        00:00:38    10.58.253.94        GigabitEthernet0/0/0/0
    Neighbor is up for 1w1d
10.58.253.91     1     FULL/  -        00:00:38    10.58.253.91        GigabitEthernet0/0/0/2
    Neighbor is up for 3d06h

OSPF is configured and neighbor adjacency is verified.

What to do next

Next, complete Configure routing policies, static routes, and BGP.

Configure routing policies, static routes, and BGP

Configure routing policy, static routes, and BGP (OLT only), then update OSPF redistribution.

Before you begin

Complete Configure OSPF and verify neighbors.
The static routes and IP address need to be updated based on DCN configuration and topology.

Follow these steps to configure routing policies and BGP, then update OSPF.

Procedure

Configure route policy and static routes on OLT and ILA nodes.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70#config
RP/0/RP0/CPU0:onc-oltc-225-70(config)#route-policy pass-all
RP/0/RP0/CPU0:onc-oltc-225-70(config-rpl)# pass    
RP/0/RP0/CPU0:onc-oltc-225-70(config-rpl)#end-policy
RP/0/RP0/CPU0:onc-oltc-225-70(config)#router static
RP/0/RP0/CPU0:onc-oltc-225-70(config-static)# address-family ipv4 unicast
RP/0/RP0/CPU0:onc-oltc-225-70(config-static-afi)# 0.0.0.0/0 10.58.225.1
RP/0/RP0/CPU0:onc-oltc-225-70(config-static-afi)# 10.58.251.0/24 10.58.253.1

Configure BGP for SSH connectivity from DCN on OLT nodes only.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70(config)#router bgp 1
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp)# bgp router-id 10.58.253.94
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp)# address-family ipv4 unicast
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-af)#  redistribute connected
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-af)#  redistribute ospf 1 route-policy pass-all
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-af)#neighbor 192.168.21.1
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-nbr)#  remote-as 100
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-nbr)#  address-family ipv4 unicast
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-nbr-af)#   route-policy pass-all in
RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-nbr-af)#   route-policy pass-all out

Redistribute routes between OSPF and BGP.

Example:


RP/0/RP0/CPU0:onc-oltc-225-70(config-bgp-nbr-af)#router ospf 1
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# default-information originate
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# redistribute connected
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# redistribute bgp 1 route-policy pass-all
RP/0/RP0/CPU0:onc-oltc-225-70(config-ospf)# commit

Routing policy, static routes, and BGP are configured and OSPF redistribution is updated.

What to do next

Next, complete Validate controllers and alarms.

Validate controllers and alarms

Validate controller status, review alarms, and confirm span-loss after bring-up.

Before you begin

Complete Configure routing policies, static routes, and BGP.
Verify that the configuration is applied across all nodes and the fiber connections are completed correctly.

Follow these steps to validate controllers and alarms.

Procedure

Verify the OSC Controller State is UP.

For ILA nodes, check both controllers.

Example:


RP/0/RP0/CPU0:onc-ilac-225-69#show controllers osc 0/0/0/0
Controller State: Up
Transport Admin State: In Service
Laser State: On
Last link flapped: 1w1d
Alarm Status:
-------------
Detected Alarms: None

Alarm Statistics:
-----------------
RX-LOS-P = 0
TX-POWER-FAIL-LOW = 0

Parameter Statistics:
---------------------
Total Tx Power = -7.92 dBm
Total Rx Power = -22.88 dBm
OSNR = 41.50 dB

RP/0/RP0/CPU0:onc-ilac-225-69#show controllers osc 0/0/0/2

Check for active alarms and refer to the troubleshooting guide to clear them if necessary.

Example:


          RP/0/RP0/CPU0:onc-ilac-225-69#sh alarms brief system active
------------------------------------------------------------------------------------
Active Alarms
------------------------------------------------------------------------------------
Location        Severity     Group            Set Time                   Description
------------------------------------------------------------------------------------
0/PM1           Major        Environ          09/19/2025 13:29:25 UTC    Power Module Error (PM_VIN_VOLT_OOR)
0/PM1           Major        Environ          09/19/2025 13:29:25 UTC    Power Module Output Disabled (PM_OUTPUT_DISABLED)
0               Major        Environ          09/19/2025 13:29:25 UTC    Power Group Redundancy lost
0/RP0/CPU0      Minor        Software         09/19/2025 13:31:02 UTC    SW Upgrade is still allowed as SIA Grace Period is remaining
0/RP0/CPU0      Major        Software         09/19/2025 13:31:05 UTC    Communications Failure With Cisco Licensing Cloud
0/0/NXR0        Minor        Software         11/22/2025 11:50:38 UTC    Ots0/0/0/0 - Span Loss Value Out Of Range
0/0/NXR0        Minor        Software         11/24/2025 12:15:35 UTC    Ots0/0/0/2 - Span Loss Value Out Of Range

Verify SSH connectivity to all nodes and check span loss after neighbor or full topology bring-up.

Example:


          RP/0/RP0/CPU0:onc-ilac-225-69#sh olc span-loss
------------------------------------------------------
Controller                                : Ots0/0/0/0
Neighbour RID                             : 10.58.253.94
Rx Span Loss                              : 14.62 dB
Rx OSC Span Loss                          : 14.91 dB
Rx Signal Span Loss                       : 14.62 dB
Rx Span Loss (with pumps off)             : NA
Estimated Rx Span Loss                    : NA
Tx Span Loss                              : 14.96 dB
Tx OSC Span Loss                          : 15.02 dB
Tx Signal Span Loss                       : 14.96 dB
Tx Span Loss (with pumps off)             : NA
Estimated Tx Span Loss                    : NA

Controller                                : Ots0/0/0/2
Neighbour RID                             : 10.58.253.91
Rx Span Loss                              : 14.41 dB
Rx OSC Span Loss                          : 14.59 dB
Rx Signal Span Loss                       : 14.41 dB
Rx Span Loss (with pumps off)             : NA
Estimated Rx Span Loss                    : NA
Tx Span Loss                              : 15.48 dB
Tx OSC Span Loss                          : 15.17 dB
Tx Signal Span Loss                       : 15.48 dB
Tx Span Loss (with pumps off)             : NA
Estimated Tx Span Loss                    : NA

Controllers are up, alarms are reviewed, and span-loss is validated.

NTP server configuration

NTP uses the User Datagram Protocol (UDP) as its transport protocol. All NTP communication uses Coordinated Universal Time (UTC). An NTP network usually receives its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP distributes this time across the network.

An NTP broadcast client listens for broadcast messages sent by an NTP broadcast server at a designated IPv4 address. The client synchronizes the local clock using the first received broadcast message.

Below are the steps for NTP configuration:

Procedure

	1.	Synchronize Clock with NTP Server
	2.	Verify the Status of the External Reference Clock

What to do next

Troubleshoot NTP Issues

SNMP configuration (optional)

SNMP is a framework that provides facilities for managing and monitoring network resources on the Internet. SNMP uses UDP for transport and uses port 161 for SNMP messages like walk and 162 for traps. This document lists the SNMP configuration(s) for monitoring the network if needed by the customer. SNMPv3 for walk and SNMP v2c for traps is covered.

Procedure

	1.	Review the SNMP procedures and supported MIBs. The procedure to configure SNMP on a 1010 device, along with the supported MIBS can be found Configuring SNMP.
	2.	Set up SNMPv3 for secure access. SNMPv3 is the most secure version of the protocol and setting it up can be found in the Setup SNMP Version 3. For retrieving information from the device using snmpwalk, the following configurations are required.
	3.	Configure the SNMP view. Setup SNMP View: The Setup SNMP view command can block the user with only access to limited Management Information Base (MIB). By default, there is no SNMP view entry exists. Example: `RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server view testview 1.3.6.1.2 included RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server view testview ospf excluded`
	4.	Create an SNMP group and users. Create snmp-server group: Create a group to map users with views. Example: `RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server group testgroup v3 priv notify testview read testview` Create snmp users and assign to group. Example: `RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server user snmpuser testgroup v3 auth sha <authpassword> priv aes 128 <privpassword>`
	5.	Verify SNMP configuration and optional tuning. Note: The show running config shows additional key word encrypted for the passwords, followed by encrypted passwords. Example: `RP/0/RP0/CPU0:onc-oltc-225-70#sh run snmp snmp-server user snmpuser testgroup v3 auth sha encrypted 01100F175804575D72 priv aes 128 encrypted 110A1016141D595F50` Below additional configurations are typically used to ensure the queries don’t overload the system and also to retrieve information for long names. Example: `RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server ifmib ifalias long RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server ifindex persist RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server ifmib stats cache RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server logging threshold RP/0/RP0/CPU0:onc-oltc-225-70(config)#oid-processing 1000 RP/0/RP0/CPU0:onc-oltc-225-70(config)#snmp-server logging threshold pdu-processing 2000` Sample configuration for SNMPwalk from the server. Example: snmpwalk -v3 -u snmpuser -l authpriv -a sha -A <authpassword> -x AES -X <privpassword> 10.78.60.234 .1.3.6.1.2 SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS XR Software, Version 25.1.1 (NCS1010) Copyright (c) 2013-2025 by Cisco Systems, Inc. SNMPv2-MIB::sysObjectID.0 = OID: CISCO-SMI::ciscoProducts.3153 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (38083) 0:06:20.83 SNMPv2-MIB::sysContact.0 = STRING: sirius-dt@cisco.com SNMPv2-MIB::sysName.0 = STRING: ios SNMPv2-MIB::sysLocation.0 = STRING: IN, BGL-17-4-Y BLR [12.9629, 77.5775] SNMPv2-MIB::sysServices.0 = INTEGER: 78 IF-MIB::ifNumber.0 = INTEGER: 16 IF-MIB::ifIndex.2 = INTEGER: 2 IF-MIB::ifIndex.3 = INTEGER: 3 IF-MIB::ifIndex.4 = INTEGER: 4 …………. ………..
	6.	Configure SNMP traps. For receiving the automatic notifications from the device via snmp traps the following configurations are required as mentioned in SNMP Traps. Different types of traps can be enabled. Trap types include alarms, configuration changes, authentication framework events, IEEE 802.1X events, and many Cisco-specific notifications. Sample examples: Example: `RP/0/RP0/CPU0:ios(config)#snmp-server traps alarm RP/0/RP0/CPU0:ios(config)#snmp-server traps power RP/0/RP0/CPU0:ios(config)#snmp-server traps config RP/0/RP0/CPU0:ios(config)#snmp-server traps optical RP/0/RP0/CPU0:ios(config)#snmp-server traps optical-ots` For V3 traps, server IP, userid and UDP port are needed as in the example given below. Example: `RP/0/RP0/CPU0:ios(config)#snmp-server host <server-ip> traps version 3 priv <userid> udp-port <port#>` For V2 traps, server IP, protocol 2c, community name and UDP ports are needed. Example: `RP/0/RP0/CPU0:ios(config)#snmp-server host <server-ip> traps version 2c public udp-port <port#> RP/0/RP0/CPU0:ios(config)#snmp-server community snmpcommunity RO`

The following output shows an SNMP trap received after the listener starts waiting for traps:

                                                                                                                                                                                                  

Received SNMPv2c Trap:                                                                                                                                                                                                 
Community: snmpcommunity                                                                                                                                                                                                      
From: 10.78.60.234                                                                                                                                                                                                     
sysUpTimeInstance = 01:13:42.70                                                                                                                                                                                        
snmpTrapOID.0 = clogMessageGenerated                                                                                                                                                                                   
clogHistFacility.0 = SECURITY-SSHD_SYSLOG_PRX                                                                                                                                                                          
clogHistSeverity.0 = info(7)                                                                                                                                                                                           
clogHistMsgName.0 = INFO_GENERAL                                                                                                                                                                                       
clogHistMsgText.0 = sshd[64262]: Connection closed by 10.78.60.234 port 58463                                                                                                                                          
clogHistTimestamp.0 = 01:13:42.00                                                                                                                                                                                      

Received SNMPv2c Trap:                                                                                                                                                                                                 
Community: public                                                                                                                                                                                                      
From: 10.78.60.234                                                                                                                                                                                                     
sysUpTimeInstance = 01:13:42.92                                                                                                                                                                                        
snmpTrapOID.0 = clogMessageGenerated                                                                                                                                                                                   
clogHistFacility.0 = SECURITY-SSHD_SYSLOG_PRX                                                                                                                                                                          
clogHistSeverity.0 = info(7)                                                                                                                                                                                           
clogHistMsgName.0 = INFO_GENERAL                                                                                                                                                                                       
clogHistMsgText.0 = sshd[64760]: Accepted authentication/pam for cisco from 10.78.60.234 port 58685 ssh2                                                                                                               
clogHistTimestamp.0 = 01:13:42.00

Day-1 configuration

Direct operators to Cisco Optical Site Manager workflows for day-1 configuration tasks.

Day-1 configuration is performed in Cisco Optical Site Manager.

Follow the Cisco Optical Site Manager section for detailed workflows.
Ensure node credentials and IP addresses are available.

Typical day-1 activities.

Device onboarding and synchronization.
Topology and service configuration.

Validate the NCS 1010 setup

Confirm that software, hardware, and licensing are operational.

Perform these checks after initial configuration and before day-1 workflows.

Before you begin

Ensure the node is reachable and interfaces are up.

Procedure

	1.	Verify Smart Licensing status. Example: `show license status`
	2.	Run preliminary checks on the default setup. Use the site checklist for preliminary validation items. Refer to preliminary checks for detailed procedures.
	3.	Verify software and hardware status. Example: `show platform show inventory`

The NCS 1010 is ready for operational use or day-1 configuration in Cisco Optical Site Manager (COSM).

Back up the current configuration

The ability to recover from a disaster is an essential part of any system maintenance plan. We recommend you backup the configurations in a secure remote location and verify that the transfer is a success, both before and after upgrade.

Before you begin

Verify connectivity to the local hard disk or remote server.

Procedure

Copy the running configuration to the local hard disk.

Example:

RP/0/RP0/CPU0:ios#copy running-config harddisk:/running_config-<mmddyyyy>
Destination filename [running_config-<mmddyyyy>]?
Building configuration...
[OK]
Verifying checksum... OK

Copy the configuration to a remote server.

Example:

RP/0/RP0/CPU0:ios#scp harddisk:/running_config-<mmddyyyy> <user>:<password>@<ip-address>:<location>

Verify that the backup completed successfully.

Confirm the file exists on the local disk and the remote server.

The configuration backup is available for recovery if needed.

What to do next

Provide this information for Day1 configuration and to bring the network to operational IP’s of individual nodes with credentials.

Troubleshooting

Identify the correct troubleshooting guide based on the symptom.

Troubleshooting coverage areas.

Hardware alarms and platform issues.
Data path and optical application alarms.
Infrastructure alarms and system health.

Table 4. Troubleshooting entry points
Issue type	Primary guide
Troubleshoot NCS 1010 setup and upgrade	NCS 1010 troubleshoot guide
Data path alarms	Data path alarms guide
Optical application alarms	Optical application alarms guide
Infrastructure alarms	Infrastructure alarms guide

Table 5. Command quick reference
Command	Purpose	When to use	Notes
show alarms brief system active	Active alarms	During alarm triage	Check severity and timestamps
show controllers osc 0/0/0/0	Controller status	When OSC issues appear	Verify optical status
show olc span-loss	Span loss	After topology bring-up	Compare with design values
show ospf neighbor	OSPF adjacency	Neighbor device issues	Confirm adjacency state

Table 6. Alarm triage guide
Severity	Action	Notes
Major	Escalate	Follow hardware troubleshooting guide
Minor	Monitor	Review for recurring issues