This document describes how to perform a scripted rack-by-rack upgrade or activate a reload Software Maintenance Upgrade (SMU) on an ASR 9000 Series Aggregation Services Router nV Edge cluster. A rack-by-rack upgrade might be used to install a new software release or a software patch (SMU) on each rack one at a time. Packet loss is minimized in the software upgrade for network topologies that incorporate cabling redundancy to each rack in the cluster.
As of the initial publication date of this document, May 2014, there are three supported methods to upgrade or activate a SMU on a cluster:
Method three is discussed in this document.
Packet loss varies based on scale and features, but is expected to be anywhere from 8s <> 180s.
Cisco recommends that you have knowledge of these topics:
The information in this document is based upon two ASR 9001s, Cisco IOS XR Release 4.3.2 to 5.1.0, and an Ubuntu Linux workstation.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Enter into KSH and copy the script to disk0:
From exec mode type 'run' to enter KSH.
Copy the file from /pkg/bin/ folder using the following command:
cp /pkg/bin/nv_edge_upgrade.exp <destination>
eg: cp /pkg/bin/nv_edge_upgrade.exp /disk0:
After this the script can be copied off the router and modified.
sudo yum install expect
or
sudo apt-get install expect
root@ubuntu:~$ whereis expect
expect: /usr/bin/expect /usr/bin/X11/expect /usr/share/man/man1/expect.1.gz
root@ubuntu:~$
#!/usr/bin/expect -f
set rack0_addr "172.18.226.153"
set rack0_port "2049"
set rack0_stby_addr "172.27.152.19"
set rack0_stby_port "2004"
set rack1_addr "172.18.226.153"
set rack1_port "2050"
set rack1_stby_addr "172.27.152.19"
set rack1_stby_port "2007"
set router_username "cisco"
set router_password "cisco"
set image_list "disk0:asr9k-mini-px-5.1.0 \
disk0:asr9k-fpd-px-5.1.0 \
disk0:asr9k-mpls-px-5.1.0 \
disk0:asr9k-mgbl-px-5.1.0 \
disk0:asr9k-bng-px-5.1.0 \ "
or the reload SMU(s) to be activated.
set image_list "disk0:asr9k-px-5.1.0-CSCxxXXXXX-1.0.0 \ "
set irl_list {{TenGigE 0/0/2/0} {TenGigE 0/0/2/1} {TenGigE 1/0/2/0} {TenGigE 1/0/2/1} }
proc router_disconnect { } {
global debug_mode
global connected_rack
if {$debug_mode == 1} { return }
send -- "\35"
sleep 1
expect -exact "telnet> "
send -- "quit\r"
expect eof
set connected_rack -1
sleep 5
admin
install add tar ftp://cisco:cisco@10.118.12.236/5.1.0.tar sync
root@ubuntu:~/nV$ expect nv_edge_upgrade.exp
########################
This CLI Script performs a software upgrade on
an ASR9k Nv Edge system, using a rack-by-rack
parallel reload method. This script will modify
the configuration of the router, and will incur
traffic loss.
Do you wish to continue [y/n] y
Use this section to confirm that your configuration works properly.
The progress of the script/upgrade is visible from the Linux workstation. The rack-by-rack upgrade takes about 45 to 60 minutes to complete.
On the ASR 9000, complete these steps in order to confirm the software upgrade/SMU activation and nV Edge system status:
RP/0/RSP0/CPU0:ASR9006#show install active summary
Mon Mar 31 12:43:43.825 EST
Default Profile:
SDRs:
Owner
Active Packages:
disk0:asr9k-fpd-px-5.1.0
disk0:asr9k-mgbl-px-5.1.0
disk0:asr9k-mpls-px-5.1.0
disk0:asr9k-mini-px-5.1.0
disk0:asr9k-bng-px-5.1.0
disk0:asr9k-px-5.1.0-CSCxxXXXXX-1.0.0
RP/0/RSP0/CPU0:ASR9006#show install committed summary
Mon Mar 31 12:44:07.250 EST
Default Profile:
SDRs:
Owner
Committed Packages:
disk0:asr9k-fpd-px-5.1.0
disk0:asr9k-mgbl-px-5.1.0
disk0:asr9k-mpls-px-5.1.0
disk0:asr9k-mini-px-5.1.0
disk0:asr9k-bng-px-5.1.0
disk0:asr9k-px-5.1.0-CSCxxXXXXX-1.0.0
show nv edge data forwarding location all
<Snippet>
-----------------node0_RSP0_CPU0------------------
nV Edge Data interfaces in forwarding state: 4
TenGigE0_0_1_3 <--> TenGigE1_0_0_3
TenGigE0_1_1_3 <--> TenGigE1_1_0_3
TenGigE0_2_1_3 <--> TenGigE1_2_0_3
TenGigE0_3_1_3 <--> TenGigE1_3_0_3
<Snippet>
In this output, the IRLs should show in the forwarding state.
show nv edge control control-link-protocols location 0/RSP0/CPU0
<Snippet>
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement - Single neighbor detected
Priority lPort Remote_lPort UDLD STP
======== ===== ============ ==== ========
0 0/RSP0/CPU0/0 1/RSP0/CPU0/0 UP Forwarding
1 0/RSP0/CPU0/1 1/RSP1/CPU0/1 UP Blocking
2 0/RSP1/CPU0/0 1/RSP1/CPU0/0 UP On Partner RSP
3 0/RSP1/CPU0/1 1/RSP0/CPU0/1 UP On Partner RSP
From this output, the 'Current bidirectional state' should show as Bidirectional and only one of the ports should be in the Forwarding state.
RP/0/RSP0/CPU0:ASR9006#admin show dsc
---------------------------------------------------------
Node ( Seq) Role Serial State
---------------------------------------------------------
0/RSP0/CPU0 ( 0) ACTIVE FOX1613G35U PRIMARY-DSC
0/RSP1/CPU0 (10610954) STANDBY FOX1613G35U NON-DSC
1/RSP0/CPU0 ( 453339) STANDBY FOX1611GQ5H NON-DSC
1/RSP1/CPU0 (10610865) ACTIVE FOX1611GQ5H BACKUP-DSC
This command displays both the DSC (inter rack) status and the redundancy role (intra rack) for all Route Switch Processors (RSPs) in the system.
In this example:
There is currently no specific troubleshooting information available for this configuration.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
10-Jul-2014 |
Initial Release |