Configuration Guide – Telesur

How to Replace a dead 5166 with an out of the box

chassis (traffic affecting)
Step 1: Deploy default configuration:

config

dhcp-client client mgmtbr0 admin-enable false

dhcpv6-client client mgmtbr0 admin-enable false

dhcp-client client remote admin-enable false

dhcpv6-client client remote admin-enable false

sync global admin-state disabled

no fps

no classifier classifier default-vid-127

ztp admin-state disabled

agg-global global-admin-state enabled

Step 2:

Transferring(download) backup file from server to node:

User can download any configuration backup file from server to node using
below command line:

CN5130> config download filename <local-file-name> remote-filename

<remote-file-name> url s[Link] username <username>
password <password>

Example:

CN5130> config download filename CN5130_backup_05_April_2022 remote-

filename CN5130_backup_05_April_2022 url s[Link]
username test password test
Loading backup file configuration on Node:

Step 1: User can check which user configuration file is loaded on the node and
status of that using below CLI command:

CN5130> show reset-status user-config

Example:

CN5130> show reset-status user-config

+------------------ RTUC-STATUS --------------+
| filename | status |
+-----------------------------+---------------+
| test_backup_05_April_2022 | rtuc-complete |
+-----------------------------+---------------+

Step 2: Now user can load any backup file configuration on the node using
below CLI command:

CN5130> config reset user-config filename <file-name>

Example:

CN5130> config reset user-config filename CN5130_backup_05_April_2022

After entering above command node will reboot(which is service impacting

action) and will take time(around 8-10 Minutes) to reload the configuration from
given backup file.

Step 3: After Node get rebooted, we can check configuration load status using
below command line where it is showing status as "rtuc-inprogress":

CN5130> show reset-status user-config

Example:

CN5130> show reset-status user-config

+----------------- RTUC-STATUS -----------------+
| filename | status |
+-----------------------------+-----------------+
| CN5130_backup_05_April_2022 | rtuc-inprogress |
+-----------------------------+-----------------+
 Step 4: Once configuration get loaded successfully, it will show status as "rtuc-
complete" as below"

CN5130> show reset-status user-config

+---------------- RTUC-STATUS ----------------+
| filename | status |
+-----------------------------+---------------+
| CN5130_backup_05_April_2022 | rtuc-complete |
+-----------------------------+---------------+

1. How to load a backup to a new box

Step 1: To take the backup of device running configuration and save into a file, run below
CLI command in user mode :

CN5130> config backup filename <file-name>

Example:

CN5130> config backup filename CN5130_backup_05_April_2022

Step 2: After creating device configuration backup file, if we do any configuration

changes on node and those changes also we want to include in our backup file, then run
below CLI command :

CN5130> config backup filename <file-name> overwrite

Example:

CN5130> config backup filename CN5130_backup_05_April_2022 overwrite

Step 3: User can check available backup files on Node using below CLI command:

CN5130> show backup filenames

Transferring(upload) backup file from node to server:

User can upload any configuration backup file from Node to any server using below
command line:
CN5130> config upload filename <local-file-name> remote-filename <remote-file-name>
url s[Link] username <username> password <password>

Example:

CN5130> config upload filename CN5130_backup_05_April_2022 remote-filename

CN5130_backup_05_April_2022 url s[Link] username test password
test

Transferring(download) backup file from server to node:

User can download any configuration backup file from server to node using below
command line:

CN5130> config download filename <local-file-name> remote-filename <remote-file-

name> url s[Link] username <username> password
<password>

Example:

CN5130> config download filename CN5130_backup_05_April_2022 remote-filename

CN5130_backup_05_April_2022 url s[Link] username test password
test

Loading backup file configuration on Node:

Step 1: User can check which user configuration file is loaded on the node and status of
that using below CLI command:

CN5130> show reset-status user-config

Example:

CN5130> show reset-status user-config

+------------------ RTUC-STATUS --------------+
| filename | status |
+-----------------------------+---------------+
| test_backup_05_April_2022 | rtuc-complete |
+-----------------------------+---------------+

Step 2: Now user can load any backup file configuration on the node using below CLI
command:
CN5130> config reset user-config filename <file-name>

Example:

CN5130> config reset user-config filename CN5130_backup_05_April_2022

After entering above command node will reboot(which is service impacting action) and
will take time(around 8-10 Minutes) to reload the configuration from given backup file.

Step 3: After Node get rebooted, we can check configuration load status using below
command line where it is showing status as "rtuc-inprogress":

CN5130> show reset-status user-config

Example:

CN5130> show reset-status user-config

+----------------- RTUC-STATUS -----------------+
| filename | status |
+-----------------------------+-----------------+
| CN5130_backup_05_April_2022 | rtuc-inprogress |
+-----------------------------+-----------------+

Step 4: Once configuration get loaded successfully, it will show status as "rtuc-complete"
as below"

CN5130> show reset-status user-config

+---------------- RTUC-STATUS ----------------+
| filename | status |
+-----------------------------+---------------+
| CN5130_backup_05_April_2022 | rtuc-complete |
+-----------------------------+---------------+

Note: Some time configuration loading from backup file may fail where status will show
as "rtuc-failed". this may happen if there is some unwanted configuration lines in that
file or any other reason.

Deleting backup configuration file from node:

User can delete any existing configuration file using below CLI command:

CN5130>config delete backup filename <file-name>

Example:
 CN5130> config delete backup filename CN5130_backup_05_April_2022
Deleting backup file successful.

How to create a service

1. Create a “packet service” and fill out the required fields. Below is an example of what you would
need. This example is for service from 5166suth to 5166ZAN.

2. Ensure you select Unidirectional under the Constrains and uncheck “Allow QinQ segments”
3. Always select the “LSP Type Device Default routing” option after calculating routes as this will
ensure the service protection.

4. Once you create the service, check the service you created and ensure it up and running. The
link between the devices should look blueish.
How to Test a Service using MCP
How to add a new node to the existing ring (No traffic
disruption)

Let’s assume we will introduce the 5166SOUTH as a new node to the existing ring. 5166HTN and
5166HAN are adjacent devices. Below is a configuration template for the provisioning of the box. The
highlighted in red indicates that this setting is unique per device. The highlighted in yellow indicates that
is no unique per device but it can change as needed.
## disable default settings – Any SAOS 10 Device

config

dhcp-client client mgmtbr0 admin-enable false

dhcpv6-client client mgmtbr0 admin-enable false

dhcp-client client remote admin-enable false

dhcpv6-client client remote admin-enable false

sync global admin-state disabled

no fps

no classifier classifier default-vid-127

ztp admin-state disabled

agg-global global-admin-state enabled

## set a hostname

system config hostname 5166STH

## set control plane loopback

oc-if:interfaces interface lb0 config name lb0 role cn-if:management type loopback

management-plane default-source-ip interface lb0

oc-if:interfaces interface lb0 ipv4 addresses address [Link] config ip [Link] prefix-length 32

## create a classifier for Untagged frames

classifiers classifier Untagged filter-entry vtag-stack untagged-exclude-priority-tagged true

## create the ISIS configuration

isis instance 'ISIS-1' net 49.0010.0010.0010.0001.00

isis instance 'ISIS-1' interfaces interface 'lb0' level-type level-2

isis instance 'ISIS-1' level-type level-2

isis instance 'ISIS-1' fast-reroute level level-2 lfa per-prefix-enable true

isis instance 'ISIS-1' fast-reroute level level-2 lfa ti-lfa per-prefix-enable true

isis instance 'ISIS-1' segment-routing srgb 16000 23999

isis instance ISIS-1 mpls-te router-id [Link]

isis instance ISIS-1 mpls-te level-type level-2

isis instance 'ISIS-1' segment-routing enabled true

isis instance ISIS-1 cspf-flag true

## create the LDP configuration

ldp instance default lsr-id [Link]

ldp instance default interfaces interface lb0 enable-ipv4 true

##Create MPLS configuraion

mpls interfaces interface 'lb0' label-switching true

#create segment routing configuration – SID should be unique per device

segment-routing connected-prefix-sid-map [Link]/32 interface lb0 value-type absolute start-sid

16001

## configuration for the interface connected to the neighbor device – in this case 5166HTN

fds fd FD_5166HTN mode vpls

oc-if:interfaces interface IF_5166HTN config name IF_5166HTN vrfName default cn-if:type ip mtu 9100
admin-status true underlay-binding config fd FD_5166HTN

oc-if:interfaces interface IF_5166HTN ipv4 addresses address [Link] config ip [Link] prefix-length
30

fps fp 33_5166HTN fd-name FD_5166HTN logical-port 33.1 classifier-list-precedence 100 stats-collection

on classifier-list Untagged
isis instance 'ISIS-1' interfaces interface 'IF_5166HTN' level-type level-2

isis instance 'ISIS-1' interfaces interface 'IF_5166HTN' interface-type point-to-point

ldp instance 'default' interfaces interface 'IF_5166HTN' enable-ipv4 true

mpls interfaces interface 'IF_5166HTN' label-switching true

bfd ip-sh sessions session IF_5166HTN [Link] source-addr [Link] required-min-rx-interval 10000
desired-min-tx-interval 10000 local-multiplier 3 statistics-collection on accelerate true

isis instance 'ISIS-1' interfaces interface 'IF_5166HTN' bfd enable true

## configuration for the interface connected to the neighbor device – in this case 5166HAN

fds fd FD_5166HAN mode vpls

oc-if:interfaces interface IF_5166HAN config name IF_5166HAN vrfName default cn-if:type ip mtu 9100
admin-status true underlay-binding config fd FD_5166HAN

oc-if:interfaces interface IF_5166HAN ipv4 addresses address [Link] config ip [Link] prefix-length
30

fps fp 34_5166HAN fd-name FD_5166HAN logical-port 34.1 classifier-list-precedence 100 stats-collection

on classifier-list Untagged

isis instance 'ISIS-1' interfaces interface 'IF_5166HAN' level-type level-2

isis instance 'ISIS-1' interfaces interface 'IF_5166HAN' interface-type point-to-point

ldp instance 'default' interfaces interface 'IF_5166HAN' enable-ipv4 true

mpls interfaces interface 'IF_5166HAN' label-switching true

bfd ip-sh sessions session IF_5166HAN [Link] source-addr [Link] required-min-rx-interval 10000
desired-min-tx-interval 10000 local-multiplier 3 statistics-collection on accelerate true

isis instance 'ISIS-1' interfaces interface 'IF_5166HAN' bfd enable true

##add LLDP peers – exclude the local loopback, in this example we are excluding 5166SOUTH loopback
[Link]

ldp instance 'default' target-ldp peers '[Link]'

exit

exit
exit

exit

ldp instance 'default' target-ldp peers '[Link]'

exit

exit

exit

exit

ldp instance 'default' target-ldp peers '[Link]'

exit

exit

exit

exit

ldp instance 'default' target-ldp peers '[Link]'

exit

exit

exit

exit

ldp instance 'default' target-ldp peers '[Link]'

exit

exit

exit

exit

ldp instance 'default' target-ldp peers '[Link]'

exit

exit

exit

exit

ldp instance 'default' target-ldp peers '[Link]'

exit
exit

exit

exit

### reboot device so segment routing takes effect

///////////////////////////////////////////Reboot the device/////////////////////////////////////////////

Check commands:

Check if the IP interfaces are in a UP state:

Check if there are ISIS routes – every single device loopback should be in this table

Check the segment routing mapping table – all devices loopback should show in the Entry prefix
Ping over SR-ISIS – ping other device to ensure segment routing is working as expected.