System Setup and Software Installation Guide for Cisco NCS 1001

Cisco NCS 1001 Overview

Cisco NCS 1001 (NCS1001-K9) is 1 RU chassis that addresses the growing bandwidth needs of data center DWDM applications. It provides a DWDM line system that is optimized for data center environments and is optimized for point-to-point applications at maximum capacity. NCS 1001 supports up to three optical modules. The modules can be amplifiers, protection switching modules, or OTDR modules.

NCS 1001 has the following components:

Removable control card
Four removable fans
Two removable 600W AC power supply modules (PSU)
Three slots for optical modules. The Optical Amplifier Module ( NCS1K-EDFA), Protection Switching Module (NCS1K-PSM), and Optical Time Domain Reflectometer (NCS1K-OTDR) module can be inserted in these slots.

The optical modules can be inserted in slots 1 to 3. The optical modules can be inserted and removed from the slots while the system is operational. In amplified configuration, the Optical Amplifier module can be inserted in any slot. In protected configuration, the protect Optical Amplifier module is inserted in slot 1, Protection Switching Module in slot 2, and working Optical Amplifier module in slot 3. The OTDR line card can be inserted in any slot.

Boot Sequence

The boot sequence in NCS 1001 that you need to follow is:

Boot using SSD (hard disk)
Boot using USB drive
Boot using iPXE

If there is no bootable image in all three boot options, reboot the system.

Boot NCS 1001

Use the console port to connect to NCS 1001. By default, the console port connects to the XR mode. If required, subsequent connections can be established through the management port, after it is configured.

Procedure

Step 1

Connect a terminal to the console port of the RP.

Step 2

Start the terminal emulation program on your workstation.

The console settings are 115200 bps, 8 data bits, 2 stop bits and no parity.

Step 3

Power on the NCS 1001.

To turn on the power shelves, press the power switch up. As NCS 1001 boots up, the boot process details are displayed at the console of the terminal emulation program.

Step 4

Press Enter.

The boot process is complete when the system prompts you to enter the root-system username. If the prompt does not appear, wait for a while to give the NCS 1001 more time to complete the initial boot procedure; then press Enter.

Important

If the boot process fails, it may be because the pre-installed image on the NCS 1001 is corrupt. In this case, the NCS 1001 can be booted using an external bootable USB drive.

Boot NCS 1001 Using USB Drive

The bootable USB drive is used to re-image the NCS 1001 for the purpose of system upgrade or to boot the NCS 1001 in case of boot failure. A bootable USB drive is created by copying a compressed boot file into a USB drive. The USB drive becomes bootable after the contents of the compressed file are extracted.

This task can be completed using the Windows, Linux, or MAC operating systems available on your local machine. The exact operation to be performed for each generic step outlined here depends on the operating system in use.

Before you begin

You need a USB drive with a storage capacity of at least 4 GB.
NCS 1001 software image can be downloaded from this location.
Copy the compressed boot file from the software download page at cisco.com to your local machine. The file name for the compressed boot file is in the format ncs1001-usb-boot-<release_number>.zip. For example, ncs1001-usb-boot-7.1.1.zip.

Procedure

Step 1

Connect the USB drive to your local machine and format it with the FAT32 file system.

Step 2

Copy the compressed boot file to the USB drive.

Step 3

Verify that the copy operation is successful. To verify, compare the file size at source and destination. Also, verify the MD5 checksum value.

Step 4

Extract the content of the compressed boot file by unzipping it in the USB drive. This makes the USB drive a bootable drive.

Note

The content of the zipped file ("EFI" and "boot" directories) must be extracted directly in the root folder of the USB drive. If the unzipping application places the extracted files in a new folder, move the "EFI" and "boot" directories to the root folder of the USB drive.

Step 5

Insert the USB drive in one of the four USB ports of NCS 1001 after unplugging any other USB drive.

Step 6

Reboot NCS 1001 using power cycle or console.

Step 7

Press Esc to enter BIOS.

Step 8

Select the Save & Exit tab of BIOS.

Step 9

Choose UEFI based USB device.

The system detects USB and boots the image from USB.


Admin Console:
GNU GRUB version 2.00
Press F2 to goto grub Menu..
Booting from USB..
Loading Kernel..

Validating End Entity Certificate...

Validating SubCA Certificate...

Validating Root Certificate...
Loading initrd..

Validating End Entity Certificate...

Validating SubCA Certificate...

Validating Root Certificate...
CiscoSec: Image signature verification completed.
XR Console:
CiscoSec: Image signature verified.
[    9.957281] i8042: No controller found
Starting udev
udevd[972]: failed to execute '/etc/udev/scripts/network.sh' '/etc/udev/scripts/network.sh': No such file or directory
Populating dev cache
Running postinst /etc/rpm-postinsts/100-dnsmasq...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
 Removing any system startup links for run-postinsts ...
  /etc/rcS.d/S99run-postinsts
Configuring network interfaces... done.

Step 10

Remove the USB drive. The NCS 1001 reboots automatically.


Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Fri Dec 11 20:35:56 UTC 2015: Install EFI on /dev/mb_disk4
Fri Dec 11 20:35:57 UTC 2015: Install finished on mb_disk
Rebooting system after installation ...
[  116.973666] reboot: Restarting system

Version 2.17.1245. Copyright (C) 2015 American Megatrends, Inc.                 
BIOS Date: 11/29/2015 12:02:45 Ver: 0ACBZ1110                                   
Press <DEL> or <ESC> to enter setup.                                            
CiscoSec: Image signature verified.


GNU GRUB version 2.00
Press F2 to goto grub Menu..
Booting from Disk..
Loading Kernel..

Validating End Entity Certificate...

Validating SubCA Certificate...

Validating Root Certificate...
Loading initrd..

Validating End Entity Certificate...

Validating SubCA Certificate...

Validating Root Certificate...
CiscoSec: Image signature verification completed.
Initrd, addr=0xff69a000, size=0x955cb0
[    1.745686] i8042: No controller found

Boot Using iPXE

iPXE is a pre-boot execution environment that is included in the network card of the management interfaces and works at the system firmware (UEFI) level of the chassis. iPXE is used to re-image the system, and boot the chassis in case of boot failure or in the absence of a valid bootable partition. iPXE downloads the ISO image, proceeds with the installation of the image, and finally bootstraps inside the new installation.

Note

The time taken for iPXE to download the ISO image depends on the network speed. Ensure that the network speed is sufficient to complete the image download in less than 10 minutes. The chassis reloads if the image is not downloaded by 10 minutes.

iPXE acts as a boot loader and provides the flexibility to choose the image that the system will boot based on the Platform Identifier (PID), the Serial Number, or the management mac-address. iPXE must be defined in the DHCP server configuration file.

Setup DHCP Server

A DHCP server must be configured for IPv4, IPv6, or both communication protocols.

Note

For DHCPv6, a routing advertisement (RA) message must be sent to all nodes in the network that indicates which method is to be used to obtain the IPv6 address. Configure Router-advertise-daemon (radvd, install using yum install radvd) to allow the client to send the DHCP request. For example:

interface eth3
{
        AdvSendAdvert on;
        MinRtrAdvInterval 60;
        MaxRtrAdvInterval 180;
        AdvManagedFlag on;
        AdvOtherConfigFlag on;
        prefix 2001:1851:c622:1::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
                AdvRouterAddr off;
        };
};

To setup a DHCP server:

Create the dhcpd.conf file (for IPv4, IPv6 or both communication protocols), dhcpv6.conf file (for IPv6) or both in the /etc/ directory. This configuration file stores the network information such as the path to the script, location of the ISO install file, location of the provisioning configuration file, serial number, MAC address of the chassis.

Test the server once the DHCP server is running:

For example, for ipv4:

Use MAC address of the chassis:

host ncs1k 
{
hardware ethernet ab:cd:ef:01:23:45;
fixed-address <ip address>;
filename "http://<httpserver-address>/<path-to-image>/ncs1k-mini-x.iso";
}

Ensure that the above configuration is successful.

Use serial number of the chassis:

host demo {
option dhcp-client-identifier "<chassis-serial-number>";
  filename "http://<IP-address>/<hardware-platform>-mini-x.iso";
  fixed-address <IP-address>;
}

The serial number of the chassis is derived from the BIOS and is used as an identifier.

Example


host 10.89.205.202 {
       hardware ethernet 40:55:39:56:0c:e8;
          if exists user-class and option user-class = "iPXE" {
          filename "http://10.89.205.127/box1/ncs1k-mini-x-7.1.1.iso";
       } else {
           filename "http://10.89.205.127/box1/StartupConfig.cfg";
       }
       fixed-address 10.89.205.202;
    }

Boot Using iPXE

Before you use the iPXE boot, ensure that:

DHCP server is set and is running.
You have logged in to the System Admin console using the admin command.

Run the following command to invoke the iPXE boot process to reimage the chassis:

hw-module location all bootmedia network reload

Example:

sysadmin-vm:0_RP0# hw-module location all bootmedia network reload
Wed Dec 23 15:29:57.376 UTC
Reload hardware module ? [no,yes]

The following example shows the output of the command:

 
iPXE 1.0.0+ (3e573) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP TFTP VLAN EFI ISO9660 NBI Menu
Trying net0...
net0: c4:72:95:a6:14:e1 using dh8900cc on PCI01:00.1 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 c4:72:95:a6:14:e1).................. Ok << Talking to DHCP/PXE server to obtain network information
net0: 10.37.1.101/255.255.0.0 gw 10.37.1.0
net0: fe80::c672:95ff:fea6:14e1/64
net0: 2001:1800:5000:1:c672:95ff:fea6:14e1/64 gw fe80::20c:29ff:fefb:b9fe
net1: fe80::c672:95ff:fea6:14e3/64 (inaccessible)
Next server: 10.37.1.235
Filename: http://10.37.1.235/ncs1k/ncs1k-mini-x.iso
http://10.37.1.235/ ... 58% << Downloading file as indicated by DHCP/PXE server to boot install image

Boot NCS 1001 Using Golden ISO

Golden ISO is a feature provided to user for building customized ISO using mini ISO, required SMUs and IOS-XR configuration.

Before the introduction of Golden ISO feature, the user must perform the following three steps, to install a new image.

Step 1 : Boot the system with mini ISO. This can be done using iPXE or USB boot.

Step 2 : Install, add, and activate all the relevant SMUs/optional packages on to NCS 1001. NCS 1001 reloads on reload of any SMUs.

Step 3 : Apply IOS-XR configuration.

Benefits of Golden ISO

Saves installation effort and time.
System gets ready in a single command and single boot.

Golden ISO is built using ‘gisobuild.py’script, which is available at /pkg/bin/gisobuild.py location.

Prerequisites:

The tools 'mount','rm','cp','umount','zcat','chroot','mkisofs' must be available and the user must have privilege to execute these tools.
Python version must be 2.7
The gisobuild.py script can be run either on a Linux machine or a NCS 1001 system. Destination must be an EXT file system. FAT32, NTFS file systems are not supported.
If gisobuild.py is running on a NCS 1001 system, the environment variable PYTHONPATH must be set as export PYTHONPATH = /pkg/bin.
System must have at least 3 GB to 4 GB of free disk space.
Mini iso is mandatory.

argument -r RPMREPO is mandatory.
Kernel version of the system must be greater than 3.16 or the version of kernel of cisco iso.
User must have proper permission for security rpm(k9sec-rpm) in rpm repository, otherwise security rpm would be ignored for Golden ISO creation.

Golden ISO file is created in the following format:

platform-name-golden-x.iso-version.label (does not contain security package(*k9sec*.rpm) rpm)

Example: ncs1001-golden-x-7.1.1.14I-V1.iso

platform-name-goldenk9-x.iso-version.label (contains security package(*k9sec*.rpm) rpm)

Example: ncs1001-goldenk9-x-7.1.1.14I-V1.iso

Boot NCS 1001 using GISO

The following steps are used to boot NCS 1001 using giso image.

Step 1 : Create the giso image using the gisobuild.py script available at /pkg/bin.

Step 2 : Create the usb zip package using the following command.

/create_usb_zip ncs1001 ncs1001xxxxx-giso.iso

Step 3 : Extract and copy the content of zip package and copy in the USB to be used for boot.

Step 4 : Insert the USB in the usb port under test.

Step 5 : Reboot the system and install the new image.

Step 6 : After the system reboots, check the configuration using show running-config command, release using show version command, and the installed packages using show install active command.

Verify Boot Operation

Procedure

Step 1

After the boot operation, reload the NCS 1001.

Step 2

show version

Example:

RP/0/RP0/CPU0:ios# show version


Tue Jan 14 12:31:05.745 CET
Cisco IOS XR Software, Version 7.1.1
Copyright (c) 2013-2019 by Cisco Systems, Inc.
Build Information:
Built By : nkhai
Built On : Tue Jan 7 16:31:55 PST 2020
Built Host : iox-lnx-071
Workspace : /auto/iox-lnx-071-san1/prod/7.1.1/ncs1001/ws
Version : 7.1.1
Location : /opt/cisco/XR/packages/
Label : 7.1.1
cisco NCS-1001 () processor

Compare the displayed version with the boot image version. The versions need to be the same.

Access the System Admin Console

All system administration and hardware management setups are performed from the System Admin console.

Procedure

Step 1

Login to the XR console as the root user.

Step 2

admin

Example:

RP/0/RP0/CPU0:ios# admin


Wed Jul 29 18:05:14.280 UTC

root connected from 127.0.0.1 using console on xr-vm_node0_RP1_CPU0
sysadmin-vm:0_RP0#

After you enter the System Admin console, the prompt changes to:

sysadmin-vm:0_RP0#

Step 3

(Optional) exit

Example:

sysadmin-vm:0_RP0# exit


Wed Jul  29 18:05:15.994 UTC
RP/0/RP0/CPU0:ios#

Return to the XR CLI from the System Admin CLI.

Configure Management Interface

To use the management interface for system management and remote communication, you must configure an IP address and subnet mask for the management ethernet interface. To communicate with devices on other networks (such as remote management stations or TFTP servers), you need to configure a default (static) route for the NCS 1001.

The range of supported MTU of management plane is 64 to 1514 bytes.

Before you begin

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

Procedure

Step 1	configure Example: `RP/0/RP0/CPU0:ios# configure` Enters XR Configuration mode.
Step 2	interface mgmtEth `rack/slot/instance/port` Example: `RP/0/RP0/CPU0:ios(config)# interface mgmtEth 0/RP0/CPU0/0` Enters interface configuration mode for the management interface.
Step 3	ipv4 address `ipv4-address` `subnet-mask` Example: `RP/0/RP0/CPU0:ios(config-if)# ipv4 address 10.1.1.1 255.0.0.0` Assigns an IP address and a subnet mask to the interface.
Step 4	no shutdown Example: `RP/0/RP0/CPU0:ios(config-if)# no shutdown` Places the interface in an "up" state.
Step 5	exit Example: `RP/0/RP0/CPU0:ios(config-if)# exit` Exits the Management interface configuration mode.
Step 6	router static address-family ipv4 unicast `0.0.0.0/0default-gateway` Example: `RP/0/RP0/CPU0:ios(config)# router static address-family ipv4 unicast 0.0.0.0/0 12.25.0.1` Specifies the IP address of the default-gateway to configure a static route; this is to be used for communications with devices on other networks.
Step 7	Use the commit or end command. 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.

What to do next

Configure Telnet and Configure SSH.

Configure Telnet

With a terminal emulation program, establish a telnet session to the management interface port using its IP address.

Procedure

Step 1

configure

Example:

RP/0/RP0/CPU0:ios# configure

Enters the Configuration mode.

Step 2

telnet {ipv4 | ipv6} server max-servers limit

Example:

RP/0/RP0/CPU0:ios(config)# telnet ipv4 server max-servers 10

Specifies the number of allowable Telnet servers. Up to 100 Telnet servers are allowed. By default, no Telnet servers are allowed. You must configure this command to enable the use of Telnet servers.

Step 3

Use the commit or end command.

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.

What to do next

Configure SSH

With a terminal emulation program, establish a SSH connection to the management interface port using its IP address.

Before you begin

Install the ncs1001-k9sec package on the NCS 1001. For details about package installation, see Install Packages.
Generate the crypto key for SSH using the crypto key generate dsa command.

Procedure

Step 1	configure Example: `RP/0/RP0/CPU0:ios# configure` Enters the Configuration mode.
Step 2	ssh server v2 Example: `RP/0/RP0/CPU0:ios(config)# ssh server v2` Enables the SSH server to accept only SSHv2 client connections.
Step 3	Use the commit or end command. 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.
Step 4	show ssh session details Example: `RP/0/RP0/CPU0:ios# show ssh session details` Displays a detailed report of the SSHv2 connections to and from NCS 1001.

What to do next

Perform Clock Synchronization with NTP Server

There are independent system clocks for the XR and the System Admin. To ensure that these clocks do not deviate from true time, they need to be synchronized with the clock of a NTP server. In this task you will configure a NTP server for the XR. After the XR clock is synchronized, the System Admin clock automatically synchronizes with the XR clock.

Before you begin

Configure and connect to the management port.

Procedure

Step 1

configure

Example:

RP/0/RP0/CPU0:ios# configure

Enters XR Configuration mode.

Step 2

ntp server server_address

Example:

RP/0/RP0/CPU0:ios# ntp server 64.90.182.55

The XR clock is configured to be synchronized with the specified sever.

Bias-Free Language

Results

Chapter: Bring-up Cisco NCS 1001

Bring-up Cisco NCS 1001

Cisco NCS 1001 Overview

Boot Sequence

Boot NCS 1001

Procedure

Boot NCS 1001 Using USB Drive

Before you begin

Procedure

Boot Using iPXE

Setup DHCP Server

Boot Using iPXE

Boot NCS 1001 Using Golden ISO

Verify Boot Operation

Procedure

Example:

Access the System Admin Console

Procedure

Example:

Example:

Configure Management Interface

Before you begin

Procedure

Example:

Example:

Example:

Example:

Example:

Example:

What to do next

Configure Telnet

Procedure

Example:

Example:

What to do next

Configure SSH

Before you begin

Procedure

Example:

Example:

Example:

What to do next

Perform Clock Synchronization with NTP Server

Before you begin

Procedure

Example:

Example:

Was this Document Helpful?

Contact Cisco