Upgrade nV Satellite

Available Languages

Updated:March 5, 2015

Document ID:118807

Bias-Free Language

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.

Introduction

Auto-Upgrade

Single-Homed

Dual-Homed

Connectivity Checks

Verify Satellite Status

Check Configuration

Verify Satellite Status (Brief)

Host Priority Change

Change Host-priority

Verify Host-priority Change

Host Upgrade

Satellite Upgrade

Verify a Satellite Upgrade

Appendix

Tips and Tricks

Upgrade Multiple Satellites

Upgrade a Ring of Satellites

Upgrade Multiple Satellites at Once

Satellite Images

9000v

901

Known Issues

Image Download Fails

Image Download Incorrectly Says Completed

5.1.1 Dual-Home Issue

Introduction

This document describes how to upgrade the Network Virtualization (nV) Satellites with minimal downtime when you upgrade a Cisco Aggregation Services Router 9000 Series (ASR9K) that has satellites attached. Special consideration is needed in order to reduce any possible outages due to the host or satellite device upgrade.

Auto-Upgrade

In Versions 5.3.2, 6.0.0, and later, the auto-upgrade feature is supported. In earlier versions, there were three image transfer scenarios:

Image incompatible – This was an automatic force upgrade from the host to the satellite.
Image not latest – This log displayed information about a version mismatch, but it was left to the user to transfer/activate.
Image latest – This allowed the user the choice to force upgrade/downgrade.

With the auto-upgrade feature, you are able to automate the second option, which causes this to act just like the first option and pushes the latest image when the satellite reconnects. The best analogy for the satellite auto-upgrade feature is that of a Field Programmable Device (FPD) auto-upgrade.

The command that is used in order to enable the auto-upgrade feature is upgrade on-connect, which is configured under the nv satellite [satellite ID] config sub-mode:

nv
 satellite 100
  type asr901
  upgrade on-connect
 !

Note: The remainder of this document focuses on manual upgrades of a satellite device.

Single-Homed

In the single-homed scenario, a satellite is only connected to a single ASR9K, which means that two reloads are seen on the satellite. The first satellite reload comes from the host that reloads during a Cisco IOS^® XR upgrade, and the second reload comes from the satellite Cisco IOS software that is upgraded.

For this type of upgrade, complete the steps in the Satellite Upgrade section.

Dual-Homed

If you upgrade a satellite that is connected to two ASR9K hosts, it overcomes some of the challenges posed by a single-homed satellite, but special consideration is needed in order to minimize any traffic outage.

Based on the assumption that both ASR9K hosts are to be updated first and the satellite last, or even at a later time, take these steps in order to minimize any outage:

Check which host each satellite sees as active.
Verify satellite(s) control plane to host 2.
Switch over satellite(s) to host 2.
Verify control and data plane.
Upgrade host 1's XR software.
Verify upgrade of host 1.
Verify satellite(s) control plane to host 1.
Switch over all satellite(s) to host 1.
Verify control and data plane for satellite(s) now on host 1.
Upgrade host 2's XR software.
Verify control plane to host 2
Switch over the satellite(s) as necessary.
Upgrade satellite(s) from either host.
Verify satellite upgrade(s).
Verify control and data plane for satellite(s).

Here are the details for these steps with the repetitive ones omitted.

Connectivity Checks

Verify Satellite Status

This example has a three satellite ring (100, 101, 102) with satellites 100 and 102 active to host 1 (9001-G) and satellite 101 active to host 2 (9001-H).

RP/0/RSP0/CPU0:ASR9001-G#show nv satellite status
Fri Aug 15 21:32:03.274 UTC
Satellite 100
-------------
  Status: Connected (Stable)
  Redundancy: Active (Group: 1)
  Type: asr901
  MAC address: 4c00.8287.1de4
  IPv4 address: 10.0.100.1 (auto)
  Serial Number: CAT1722U21S
  Remote version: Compatible (not latest version)
    ROMMON: 2.1 (Latest)
    FPGA: N/A
    IOS: 1402.20 (Available: 1406.12)
  Configured satellite fabric links:
    GigabitEthernet0/0/0/0
    ----------------------
      Status: Satellite Ready
      Remote ports: GigabitEthernet0/0/0-9

Satellite 101
-------------
  Status: Connected (Stable)
  Redundancy: Standby (Group: 1)
  Type: asr901
  MAC address: 4c00.8287.2e24
  IPv4 address: 10.0.101.1 (auto)
  Serial Number: CAT1723U02B
  Remote version: Compatible (not latest version)
    ROMMON: 2.1 (Latest)
    FPGA: N/A
    IOS: 1402.20 (Available: 1406.12)
  Configured satellite fabric links:
    GigabitEthernet0/0/0/0
    ----------------------
      Status: Satellite Ready
      Remote ports: GigabitEthernet0/0/0-9

Satellite 102
-------------
  Status: Connected (Stable)
  Redundancy: Active (Group: 1)
  Type: asr901
  MAC address: 4c00.8287.2ec4
  IPv4 address: 10.0.102.1 (auto)
  Serial Number: CAT1723U015
  Remote version: Compatible (not latest version)
    ROMMON: 2.1 (Latest)
    FPGA: N/A
    IOS: 1402.20 (Available: 1406.12)
  Configured satellite fabric links:
    GigabitEthernet0/0/0/0
    ----------------------
      Status: Satellite Ready
      Remote ports: GigabitEthernet0/0/0-9

Check Configuration

If these checks show all satellites as connected, then the configuration should be correct. If any satellites are not in the connected state on either ASR9Ks, then additional troubleshooting might be needed.

This configuration is what is used throughout this document.

interface GigabitEthernet0/0/0/0
 nv
  satellite-fabric-link network
   redundancy
    iccp-group 1
   !
   satellite 100
    remote-ports GigabitEthernet 0/0/0-9
   !
   satellite 101
    remote-ports GigabitEthernet 0/0/0-9
   !
   satellite 102
    remote-ports GigabitEthernet 0/0/0-9
   !
  !
 !
!

nv
 satellite 100
  type asr901
  redundancy
   host-priority 0
  !
  serial-number CAT1722U21S
 !
 satellite 101
  type asr901
  redundancy
   host-priority 200
  !
  serial-number CAT1723U02B
 !
 satellite 102
  type asr901
  redundancy
   host-priority 0
  !
  serial-number CAT1723U015
 !
!

Verify Satellite Status (Brief)

RP/0/RSP0/CPU0:ASR9001-H#show nv satellite status brief
Fri Aug 15 13:39:56.271 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -----------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Stby)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Act)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Stby)

If a more condensed output is desired, then the show nv satellite status brief command can be used on both hosts. The connected state indicates that the control channel is operational, while Act and Stby indicates the status of the data plane for each satellite per host.

Host Priority Change

Change Host-priority

The easiest way to failover a satellite to the other ASR9K host is to change the host-priority in the configuration. In this example, the host-priority is set to the highest value (lowest priority) so that all satellites in the ring switch over to host 2.

RP/0/RSP0/CPU0:ASR9001-G#config t
Fri Aug 15 21:39:50.909 UTC
RP/0/RSP0/CPU0:ASR9001-G(config)#nv
RP/0/RSP0/CPU0:ASR9001-G(config-nV)#satellite 100
RP/0/RSP0/CPU0:ASR9001-G(config-satellite)#redundancy
RP/0/RSP0/CPU0:ASR9001-G(config-nV-red)#host-priority 255
RP/0/RSP0/CPU0:ASR9001-G(config-nV-red)#exit
RP/0/RSP0/CPU0:ASR9001-G(config-satellite)#exit
RP/0/RSP0/CPU0:ASR9001-G(config-nV)#satellite 102
RP/0/RSP0/CPU0:ASR9001-G(config-satellite)#redundancy
RP/0/RSP0/CPU0:ASR9001-G(config-nV-red)#host-priority 255
RP/0/RSP0/CPU0:ASR9001-G(config-nV-red)#end
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:y

Verify Host-priority Change

In order to verify this change, the show nv satellite status brief command can be used.

RP/0/RSP0/CPU0:ASR9001-G#show nv satellite status brief
Fri Aug 15 21:40:35.876 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -----------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Stby)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Stby)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Stby)

RP/0/RSP0/CPU0:ASR9001-H#show nv sat stat bri
Fri Aug 15 13:42:15.847 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -----------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Act)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Act)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Act)

Host Upgrade

After you verify which host sees all satellites as active and which host sees all satellites as standby, follow the normal upgrade procedures as documented on Cisco Connection Online (CCO), or as per any tested Method of Procedure (MOP), on the host where all satellites are standby.
After the first host is upgraded and all install post-checks confirmed, follow the Connectivity Checks section in order to verify satellite connectivity to both hosts. Once connectivity is verified, follow the Host Priority Change Section in order to switch satellites over to the upgraded host by lowering the priority.
Once all satellites are connected as standby to host 2, upgrade this host and perform all install verification steps as per the CCO upgrade guide or MOP and all satellite checks as per Connectivity Checks.
Finally, proceed to Satellite Upgrade.

Satellite Upgrade

New satellite (9000v and 901) images are contained in the asr9k-9000v-nV-px-<release>and asr9k-901-nV-px-<release> packages respectfully. Once these packages are activated on the host, a satellite might be upgraded.

In order to download and activate the software image on a satellite, use the install nv satellite command in the EXEC mode.

install nv satellite { satellite id | all } { transfer | activate }

Syntax Description

satellite id	Specifies the unique identifier of the satellite on which the image must be transferred.
all	Performs the operation on all currently active satellites that are not already at the target version.
transfer	Downloads the image from the host to the satellite device.
activate	Performs the install operation on the satellite.

Note: See the Tips and Tricks section for details about how to upgrade advanced topologies such as Simple Ring.

Verify a Satellite Upgrade

After you issue the install nv satellite command and the satellite reloads, the output of show nv satellite status should display that the ROMMON, Field-Programmable Gate Array (FPGA), and Cisco IOS revisions are the latest. If any of these do not say latest, then additional troubleshooting is needed in order to determine why the image was not upgraded.

Note: Check the Satellite Images and Known Issues sections before you contact the Cisco Technical Assistance Center (TAC).

RP/0/RSP0/CPU0:ASR9001-H#show nv satellite status
Fri Aug 15 19:54:26.429 UTC
Satellite 100
-------------
  Status: Connected (Stable)
  Redundancy: Active (Group: 1)
  Type: asr901
  MAC address: 4c00.8287.1de4
  IPv4 address: 10.0.100.1 (auto)
  Serial Number: CAT1722U21S
  Remote version: Compatible (not latest version)
    ROMMON: 2.1 (Latest)
    FPGA: N/A
    IOS: 1402.20 (Available: 1406.12)
  Configured satellite fabric links:
    GigabitEthernet0/0/0/0
    ----------------------
      Status: Satellite Ready
      Remote ports: GigabitEthernet0/0/0-9

Satellite 101
-------------
  Status: Connected (Stable)
  Redundancy: Active (Group: 1)
  Type: asr901
  MAC address: 4c00.8287.2e24
  IPv4 address: 10.0.101.1 (auto)
  Serial Number: CAT1723U02B
  Remote version: Compatible (latest version)
    ROMMON: 2.1 (Latest)
    FPGA: N/A
    IOS: 1406.12 (Latest)
  Configured satellite fabric links:
    GigabitEthernet0/0/0/0
    ----------------------
      Status: Satellite Ready
      Remote ports: GigabitEthernet0/0/0-9

Appendix

Tips and Tricks

Upgrade Multiple Satellites

Multiple satellites can be chosen for the install nv satellite command if you use a range, for example 100-110, or by a comma, for example 100,105,115.

Note: Use the transfer option to transfer all the images in parallel, followed by the activate keyword in order to activate the satellites in sequential or parallel order.

Upgrade a Ring of Satellites

While a satellite in a ring can quickly (typically less than one second) switch over to the backup host, it is a best practice to avoid this if possible and use the host-priority function for a user-invoked switchover instead of an event-triggered switchover.

Considering this, if you upgrade a satellite (SAT101 in this example) in a ring and another satellite's active data path goes through this satellite (SAT102), then there will be a switchover of the active data path for SAT102 when SAT101 reboots to use the new image and a second switchover for SAT102 after SAT101 comes back online.

In order to illustrate this, in these examples this topology is used with all satellites active to 9001H and standby to 9001G.

9001G --- SAT100 --- SAT101 --- SAT102 --- 9001H

Example: Wrong Way to Upgrade

Q: What happens when SAT101 is upgraded from 9001H?

A: When satellite 101 reloads, satellite 100 loses its control link to 9001H and switches over to 9001G. Satellite 102 loses its connection to 9001G but the data plane does not switch over. Once satellite 101 comes back up and the control channel between 9001H and satellite 100 is re-established, this satellite switches over again and begins to use 9001H as its primary data plane path again.

This verifies the data plane status for each satellite, with 9001G as standby and 9001H as active.

RP/0/RSP0/CPU0:ASR9001-G#show nv satellite status brief
Fri Aug 15 21:40:35.876 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -----------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Stby)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Stby)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Stby)

Here is an example of satellite 101 that is upgraded from host 9001H.

Note: Which host initiates the upgrade is not important.

RP/0/RSP0/CPU0:ASR9001-H#install nv satellite 101 activate
Fri Aug 15 18:05:27.899 UTC
The operation will cause an image to be transferred, and then activated on the
 requested satellite.
WARNING: This will take the requested satellite out of service.
Do you wish to continue? [confirm(y/n)] y
Install Op 1: activate: 101
1 configured satellite has been specified for activate.
1 satellite has successfully initiated activate.

When satellite 101 reloads to use its new image the following happens as seen in the below output:

Satellite 100 loses its control and data plane connections to 9001H
Satellite 100 will begin to use 9001G for its active data path
Satellite 102 loses its control connection to 9001G

RP/0/RSP0/CPU0:ASR9001-G#show nv satellite status brief
Sat Aug 16 02:15:44.148 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -------------------------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Act)
101     asr901    10.0.101.1    0000.0000.0000  Discovery Stalled; Conflict:
                                                no Identification received yet
102     asr901    10.0.102.1    0000.0000.0000  Discovery Stalled; Conflict:
                                                no Identification received yet

Once satellite 101 comes back up and the control connection to satellite 100 is re-established to 9001H, all satellites are standby to 9001G again and active to 9001H. This means that satellite 100 performs a second switchover.

RP/0/RSP0/CPU0:Aug 15 18:15:20.280 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
TRANSFER_DONE : Image transfer completed on Satellite 101
RP/0/RSP0/CPU0:Aug 15 18:15:49.775 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 100 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 15 18:15:49.775 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 101 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 15 18:15:49.775 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
INSTALL_DONE : Image install completed on Satellite 101
RP/0/RSP0/CPU0:Aug 15 18:15:49.792 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 100 removed
RP/0/RSP0/CPU0:Aug 15 18:15:49.805 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 101 removed
RP/0/RSP0/CPU0:Aug 15 18:18:31.793 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 101 up
RP/0/RSP0/CPU0:Aug 15 18:18:33.809 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: 
Node 101/ inserted
RP/0/RSP0/CPU0:Aug 15 18:18:35.665 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 100 up
LC/0/0/CPU0:Aug 15 18:18:36.021 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Up
LC/0/0/CPU0:Aug 15 18:18:36.022 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Up
LC/0/0/CPU0:Aug 15 18:18:37.786 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 15 18:18:37.786 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Down
RP/0/RSP0/CPU0:Aug 15 18:18:38.980 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:43.988 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:43.990 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:43.993 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:43.996 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:44.203 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node 
100/ inserted
RP/0/RSP0/CPU0:Aug 15 18:18:50.552 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:55.559 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:55.561 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:55.564 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:55.567 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 15 18:18:55.569 : invmgr[254]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 
SAT101/0/0 GigabitEthernet port_num: 0 is inserted, state: 1
RP/0/RSP0/CPU0:Aug 15 18:18:55.570 : invmgr[254]: %PLATFORM-INV-6-IF_OIROUT : xFP OIR: 
SAT101/0/0 GigabitEthernet port_num: 0 is removed, state: 0
RP/0/RSP0/CPU0:Aug 15 18:18:56.925 : invmgr[254]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 
SAT100/0/0 GigabitEthernet port_num: 0 is inserted, state: 1
RP/0/RSP0/CPU0:Aug 15 18:18:56.927 : invmgr[254]: %PLATFORM-INV-6-IF_OIROUT : xFP OIR: 
SAT100/0/0 GigabitEthernet port_num: 0 is removed, state: 0
RP/0/RSP0/CPU0:Aug 15 18:18:56.931 : invmgr[254]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 
SAT100/0/0 GigabitEthernet port_num: 4 is inserted, state: 1

Once the satellite is upgraded, you should see the same satellite status as before.

RP/0/RSP0/CPU0:ASR9001-H#show nv satellite status brief
Fri Aug 15 18:20:59.515 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -------------------------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Act)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Act)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Act)

Example: Correct Way to Upgrade

With the same topology as the previous example and starting with all satellites that need to be upgraded, this example shows the proper way to upgrade a ring.

Note: Transfers are done in parallel, but some transfers might take longer than others to complete. It is recommended to transfer the image to all satellites first and then systematically initiate the activate portion of the installation in order to save time and prevent unnecessary reloads of a satellite.

Note: This example shows the activation of one satellite at a time as a reference, but all satellites can be activated at once as seen later in this section.

Check the status of the satellites from both hosts and then transfer the images to all satellites.

RP/0/RSP0/CPU0:ASR9001-G#show nv sat stat bri
Fri Aug 22 20:15:59.830 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -----------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Stby)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Stby)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Stby)

RP/0/RSP0/CPU0:ASR9001-H#show nv sat stat bri
Fri Aug 22 12:17:20.811 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -----------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Act)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Act)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Act)

RP/0/RSP0/CPU0:ASR9001-H#install nv satellite 100-102 transfer
Fri Aug 22 12:17:51.647 UTC
Install Op 1: transfer: 100-102
3 configured satellites have been specified for transfer.
3 satellites have successfully initiated transfer.

RP/0/RSP0/CPU0:ASR9001-H#RP/0/RSP0/CPU0:Aug 22 12:23:16.238 : icpe_satmgr[1168]:
 %PKT_INFRA-ICPE_GCO-6-TRANSFER_DONE : Image transfer completed on Satellite 100
RP/0/RSP0/CPU0:Aug 22 12:27:55.990 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
TRANSFER_DONE : Image transfer completed on Satellite 101
RP/0/RSP0/CPU0:Aug 22 12:28:01.876 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
TRANSFER_DONE : Image transfer completed on Satellite 102

After this, because all satellites are active to 9001H, activate satellite 100 first. Due to this, 9001G loses the control connections to all satellites in the ring.

RP/0/RSP0/CPU0:ASR9001-H#install nv satellite 100 activate
Fri Aug 22 12:30:13.088 UTC
WARNING: This will take the requested satellite out of service.
Do you wish to continue? [confirm(y/n)] y
Install Op 2: activate: 100
1 configured satellite has been specified for activate.
1 satellite has successfully initiated activate.
RP/0/RSP0/CPU0:ASR9001-H#
RP/0/RSP0/CPU0:ASR9001-H#RP/0/RSP0/CPU0:Aug 22 12:30:45.639 : icpe_satmgr[1168]: 
%PKT_INFRA-ICPE_GCO-5-SATELLITE_STATUS : Satellite 100 one or more links may 
be down - traffic may be impacted
RP/0/RSP0/CPU0:Aug 22 12:30:45.639 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
INSTALL_DONE : Image install completed on Satellite 100
RP/0/RSP0/CPU0:Aug 22 12:30:45.658 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 100 removed
RP/0/RSP0/CPU0:Aug 22 12:33:28.059 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 100 up
RP/0/RSP0/CPU0:Aug 22 12:33:30.446 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: 
Node 100/ inserted
RP/0/RSP0/CPU0:Aug 22 12:33:30.449 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: 
Node 100/ inserted
LC/0/0/CPU0:Aug 22 12:33:30.495 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Up
LC/0/0/CPU0:Aug 22 12:33:30.497 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Up
LC/0/0/CPU0:Aug 22 12:33:43.498 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 12:33:43.498 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 12:33:45.487 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Up
LC/0/0/CPU0:Aug 22 12:33:45.490 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Up
RP/0/RSP0/CPU0:Aug 22 12:33:48.549 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 22 12:33:53.557 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 22 12:33:53.560 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 22 12:33:53.563 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
RP/0/RSP0/CPU0:Aug 22 12:33:53.568 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: Node  
inserted
LC/0/0/CPU0:Aug 22 12:33:57.750 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 12:33:57.750 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Down
RP/0/RSP0/CPU0:Aug 22 12:34:06.111 : invmgr[254]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 
SAT100/0/0 GigabitEthernet port_num: 0 is inserted, state: 1
RP/0/RSP0/CPU0:Aug 22 12:34:06.113 : invmgr[254]: %PLATFORM-INV-6-IF_OIROUT : xFP OIR: 
SAT100/0/0 GigabitEthernet port_num: 0 is removed, state: 0
RP/0/RSP0/CPU0:Aug 22 12:34:06.118 : invmgr[254]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 
SAT100/0/0 GigabitEthernet port_num: 4 is inserted, state: 1


RP/0/RSP0/CPU0:ASR9001-H#show nv sat stat bri
Fri Aug 22 12:34:13.401 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -------------------------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Act)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Act; Transferred)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Act; Transferred)

Once satellite 100 comes back up, switch its active datapath over to 9001G and continue the upgrade process with an upgrade to satellite 101 and finally satellite 102.

Note: While the satellite reloads, you can also change the host-priority configuration and thus prevent any switchover at all.

RP/0/RSP0/CPU0:ASR9001-G#show run nv satellite 100
Fri Aug 22 20:35:59.435 UTC
nv
 satellite 100
  type asr901
  redundancy
   host-priority 255
  !
  serial-number CAT1722U21S
 !
!
RP/0/RSP0/CPU0:ASR9001-G#config t
Fri Aug 22 20:36:03.839 UTC
RP/0/RSP0/CPU0:ASR9001-G(config)#nv sat 100
RP/0/RSP0/CPU0:ASR9001-G(config-satellite)#redundancy
RP/0/RSP0/CPU0:ASR9001-G(config-nV-red)#host-priority 50
RP/0/RSP0/CPU0:ASR9001-G(config-nV-red)#end
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:y

RP/0/RSP0/CPU0:Aug 22 20:36:18.401 : config[65867]: %MGBL-CONFIG-6-DB_COMMIT :
 Configuration committed by user 'lab'. Use 'show configuration commit changes
 1000000053' to view the changes.
RP/0/RSP0/CPU0:Aug 22 20:36:18.429 : config[65867]: %MGBL-SYS-5-CONFIG_I :
 Configured from console by lab on vty0 (64.102.157.220)
RP/0/RSP0/CPU0:ASR9001-G#LC/0/0/CPU0:Aug 22 20:36:20.291 : ifmgr[208]:
 %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet100/0/0/0, changed state to Up
LC/0/0/CPU0:Aug 22 20:36:20.293 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN :
 Line protocol on Interface GigabitEthernet100/0/0/0, changed state to Up

RP/0/RSP0/CPU0:ASR9001-G#show nv sat stat bri
Fri Aug 22 20:37:19.041 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -------------------------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Act)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Stby)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Stby)
RP/0/RSP0/CPU0:ASR9001-G#

RP/0/RSP0/CPU0:ASR9001-H#show nv sat stat bri
Fri Aug 22 12:40:26.728 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -------------------------------
100     asr901    10.0.100.1    4c00.8287.1de4  Connected (Stby)
101     asr901    10.0.101.1    4c00.8287.2e24  Connected (Act; Transferred)
102     asr901    10.0.102.1    4c00.8287.2ec4  Connected (Act; Transferred)

RP/0/RSP0/CPU0:ASR9001-H#install nv satellite 101 activate
Fri Aug 22 12:40:39.496 UTC
WARNING: This will take the requested satellite out of service.
Do you wish to continue? [confirm(y/n)] y
Install Op 3: activate: 101
1 configured satellite has been specified for activate.
1 satellite has successfully initiated activate.

RP/0/RSP0/CPU0:ASR9001-H#RP/0/RSP0/CPU0:Aug 22 12:41:11.108 : icpe_satmgr[1168]: 
%PKT_INFRA-ICPE_GCO-5-SATELLITE_STATUS : Satellite 100 one or more links may be 
down - traffic may be impacted
RP/0/RSP0/CPU0:Aug 22 12:41:11.108 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 101 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 22 12:41:11.108 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
INSTALL_DONE : Image install completed on Satellite 101
RP/0/RSP0/CPU0:Aug 22 12:41:11.125 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 100 removed
RP/0/RSP0/CPU0:Aug 22 12:41:11.134 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 101 removed
LC/0/0/CPU0:Aug 22 12:41:11.150 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 12:41:11.150 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet100/0/0/0, changed state to Down
RP/0/RSP0/CPU0:Aug 22 12:44:08.154 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 101 up
RP/0/RSP0/CPU0:Aug 22 12:44:10.598 : invmgr[254]: %PLATFORM-INV-6-OIRIN : OIR: 
Node 101/ inserted
RP/0/RSP0/CPU0:Aug 22 12:44:14.031 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 100 up

Because satellite 101 is activated, this happens when it reloads:

SAT 100 being standby to 9001H loses its standby control plane connection to 9001G.
SAT 101 loses its data plane and control plane to both hostss
SAT 102 being standby to 9001G loses its standby control plane connection to 9001G.
The data planes on SAT 100 and 102 have no impact and no switchover.

RP/0/RSP0/CPU0:ASR9001-G#RP/0/RSP0/CPU0:Aug 22 20:39:52.241 : icpe_satmgr[1152]: 
%PKT_INFRA-ICPE_GCO-5-SATELLITE_STATUS : Satellite 101 one or more links may be 
down - traffic may be impacted
RP/0/RSP0/CPU0:Aug 22 20:39:52.241 : icpe_satmgr[1152]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 102 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 22 20:39:52.257 : invmgr[253]: %PLATFORM-INV-6-OIROUT : 
OIR: Node 101 removed
RP/0/RSP0/CPU0:Aug 22 20:39:52.271 : invmgr[253]: %PLATFORM-INV-6-OIROUT : 
OIR: Node 102 removed
RP/0/RSP0/CPU0:Aug 22 20:42:49.285 : icpe_satmgr[1152]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 101 up
RP/0/RSP0/CPU0:ASR9001-G#RP/0/RSP0/CPU0:Aug 22 20:42:51.712 : invmgr[253]: 
%PLATFORM-INV-6-OIRIN : OIR: Node 101/ inserted
RP/0/RSP0/CPU0:Aug 22 20:42:55.166 : icpe_satmgr[1152]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 102 up
RP/0/RSP0/CPU0:Aug 22 20:42:55.539 : invmgr[253]: %PLATFORM-INV-6-OIRIN : OIR: 
Node 102/ inserted

Upgrade Multiple Satellites at Once

You can specify multiple satellites rather than activate one satellite at a time.

Note: This is not recommended for a ring topology.

RP/0/RSP0/CPU0:ASR9001-H#install nv satellite 100-102 activate
Fri Aug 22 13:04:35.604 UTC
The operation will cause an image to be transferred where required, and then 
activate new versions on the requested satellites.
WARNING: This will take the requested satellites out of service.
Do you wish to continue? [confirm(y/n)] y
Install Op 5: activate: 100-102
3 configured satellites have been specified for activate.
3 satellites have successfully initiated activate.

RP/0/RSP0/CPU0:Aug 22 13:05:07.612 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 100 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 22 13:05:07.612 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 101 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 22 13:05:07.612 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
INSTALL_DONE : Image install completed on Satellite 100
RP/0/RSP0/CPU0:Aug 22 13:05:07.612 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
INSTALL_DONE : Image install completed on Satellite 101
RP/0/RSP0/CPU0:Aug 22 13:05:07.630 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 100 removed
RP/0/RSP0/CPU0:Aug 22 13:05:07.640 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 101 removed
LC/0/0/CPU0:Aug 22 13:05:07.653 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 13:05:07.653 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line
protocol on Interface GigabitEthernet100/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 13:05:07.912 : ifmgr[208]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Aug 22 13:05:07.912 : ifmgr[208]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
RP/0/RSP0/CPU0:Aug 22 13:05:07.916 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-5-
SATELLITE_STATUS : Satellite 102 one or more links may be down - traffic may 
be impacted
RP/0/RSP0/CPU0:Aug 22 13:05:07.916 : icpe_satmgr[1168]: %PKT_INFRA-ICPE_GCO-6-
INSTALL_DONE : Image install completed on Satellite 102
RP/0/RSP0/CPU0:Aug 22 13:05:07.934 : invmgr[254]: %PLATFORM-INV-6-OIROUT : OIR: 
Node 102 removed

RP/0/RSP0/CPU0:ASR9001-H#show nv sat stat bri
Fri Aug 22 13:06:12.255 UTC
Sat-ID  Type      IP Address    MAC address     Status
------  --------  ------------  --------------  -------------------------------
100     asr901    10.0.100.1    0000.0000.0000  Discovery Stalled; Conflict: 
                                                interface is down
101     asr901    10.0.101.1    0000.0000.0000  Discovery Stalled; Conflict: 
                                                interface is down
102     asr901    10.0.102.1    0000.0000.0000  Discovery Stalled; Conflict: 
                                                interface is down

Example: Auto-Upgrade of a Satellite

This section provides an example of an upgrade to a later satellite code, and the auto-upgrade feature triggers.

RP/0/RSP1/CPU0:AE(admin)#install activate disk0:asr9k-asr901-nV-px-5.3.2.12I
Thu Jun 18 20:19:21.299 UTC
Install operation 2 '(admin) install activate disk0:asr9k-asr901-nV-px-5.3.2.12I'
Info:     Install Method: Parallel Process Restart
The install operation will continue asynchronously.
Install operation 2: load phase started at 20:19:43 UTC Thu Jun 18 2015.
Info:     The changes made to software configurations will not be persistent
Info:     across system reloads. Use the command '(admin) install commit' to
Info:     make changes persistent.
Info:     Please verify that the system is consistent following the software
Info:     change using the following commands:
Info:         show system verify
Info:         install verify packages


RP/0/RSP1/CPU0:Jun 18 20:19:21.373 : instdir[251]:
 %INSTALL-INSTMGR-6-INSTALL_OPERATION_STARTED : Install operation 2 '(admin)
 install activate mem:asr9k-asr901-nV-px-5.3.2.12I' started by user 'started
 by user 'lab' via CLI at 20:19:21 UTC Thu Jun 18 2015.
lab'
RP/0/RSP1/CPU0:Jun 18 20:19:58.402 : firmware_manager[235]:
 %PLATFORM-UPGRADE_FPD-6-FW_MGR_OPERATION_INFO : AUTO_FPD_UPGRADE_INFO: FW_MGR:
 auto fpd-upgrade CLI not configured. Return!
RP/0/RSP1/CPU0:Jun 18 20:20:01.422 : sysmgr[94]: %OS-SYSMGR-7-INSTALL_NOTIFICATION
 : notification of software installation received
LC/0/0/CPU0:Jun 18 20:20:02.236 : sysmgr[91]: %OS-SYSMGR-7-INSTALL_NOTIFICATION :
 notification of software installation received
LC/0/0/CPU0:Jun 18 20:20:02.250 : sysmgr[91]: %OS-SYSMGR-7-INSTALL_FINISHED :
 software installation is finished
RP/0/RSP1/CPU0:Jun 18 20:20:06.432 : sysmgr[94]: %OS-SYSMGR-7-INSTALL_FINISHED :
 software installation is finished
RP/0/RSP1/CPU0:Jun 18 20:20:18.772 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-4-SATELLITE_UPGRADE_ON_CONNECT_SET : Satellite 100 has been
 configured to auto-update on re-connection and is currently not using a current
 version. If the satellite control session is re-established, then the satellite
 will update and be temporarily out of service.
RP/0/RSP1/CPU0:Jun 18 20:20:23.075 : instdir[251]:
 %INSTALL-INSTMGR-6-INSTALL_OPERATION_COMPLETED_SUCCESSFULLY : Install operation
 2 completed successfully


RP/0/RSP1/CPU0:Jun 18 20:22:04.756 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-6-VERSION_NOTCURRENT : Satellite 100 is running a software
 version which is not current. Auto-upgrade scheduled.
RP/0/RSP1/CPU0:Jun 18 20:22:04.756 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-4-SATELLITE_UPGRADE_ON_CONNECT_SET : Satellite 100 has been
 configured to auto-update on re-connection and is currently not using a current
 version. If the satellite control session is re-established, then the satellite
 will update and be temporarily out of service.
RP/0/RSP1/CPU0:Jun 18 20:22:04.884 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-5-VERSION_AUTOUPGRADE_STARTED : Auto-upgrade started for
 1 satellite.



RP/0/RSP1/CPU0:Jun 18 20:27:22.438 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-6-TRANSFER_DONE : Image transfer completed on Satellite 100
LC/0/0/CPU0:Jun 18 20:27:48.995 : ifmgr[211]: %PKT_INFRA-LINK-3-UPDOWN :
 Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Jun 18 20:27:48.995 : ifmgr[211]: %PKT_INFRA-LINEPROTO-5-UPDOWN :
 Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Down
RP/0/RSP1/CPU0:Jun 18 20:27:48.996 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-6-INSTALL_DONE : Image install completed on Satellite 100
LC/0/0/CPU0:Jun 18 20:27:50.476 : vic_0[367]: %PLATFORM-VIC-4-SIGNAL :
 Interface GigabitEthernet0/0/0/10, Detected Signal failure
LC/0/0/CPU0:Jun 18 20:29:16.741 : ifmgr[211]: %PKT_INFRA-LINK-3-UPDOWN :
 Interface GigabitEthernet0/0/0/10, changed state to Up
LC/0/0/CPU0:Jun 18 20:29:57.670 : ifmgr[211]: %PKT_INFRA-LINK-3-UPDOWN :
 Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Jun 18 20:29:58.213 : vic_0[367]: %PLATFORM-VIC-4-RX_LOS :
 Interface GigabitEthernet0/0/0/10, Detected Rx Loss of Signal
LC/0/0/CPU0:Jun 18 20:29:58.224 : ifmgr[211]: %PKT_INFRA-LINK-3-UPDOWN :
 Interface GigabitEthernet0/0/0/10, changed state to Up
LC/0/0/CPU0:Jun 18 20:30:25.019 : ifmgr[211]: %PKT_INFRA-LINEPROTO-5-UPDOWN :
 Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Up
RP/0/RSP1/CPU0:Jun 18 20:30:28.969 : icpe_satmgr[1154]:
 %PKT_INFRA-ICPE_GCO-5-SATELLITE_STATUS : Satellite 100 up

Satellite Images

Here is a list of expected versioning for a satellite.

9000v

XR Release	First Customer Ship (FCS) or Software Maintenance Upgrade (SMU)	Image Type	Image Version	Notes
4.2.1	FCS	Cisco IOS / Kernel	202.0 (151-3.SVA)	202-209.9
		ROMMON	125
		FPGA	1.13
4.2.3	FCS	Cisco IOS / Kernel	210 (151-3.SVB)	210-219.9
		ROMMON	125
		FPGA	1.13
	CSCuc59715	Cisco IOS / Kernel	211
		ROMMON	125
		FPGA	1.13
	CSCty86900	Cisco IOS / Kernel	212
		ROMMON	125
		FPGA	1.13
	CSCul09549	Cisco IOS / Kernel	213
		ROMMON	125
		FPGA	1.13
4.3.0	FCS	Cisco IOS / Kernel	252 (151-3.SVC)	250-259.9
		ROMMON	125
		FPGA	1.13
4.3.1	FCS	Cisco IOS / Kernel	276 (151-3.SVD)
		ROMMON	125
		FPGA	1.13
	CSCuj97259	Cisco IOS / Kernel	277
		ROMMON	125
		FPGA	1.13
	CSCui77863	Cisco IOS / Kernel	278
		ROMMON	125
		FPGA	1.13
	CSCuj97259	Cisco IOS / Kernel	279
		ROMMON	125
		FPGA	1.13
4.3.2		Cisco IOS / Kernel	285 (151-3.SVF)
		ROMMON	125
		FPGA	1.13
4.3.4		Cisco IOS / Kernel	287 (151-3.SVFa)	It might say 285 available, this is wrong.
		ROMMON	125
		FPGA	1.13
5.1.0		Cisco IOS / Kernel	292 (151-3.SVE)
		ROMMON	125
		FPGA	1.13
5.1.1		Cisco IOS / Kernel	322.6 (151-3.SVG)
		ROMMON	126	In order to use the advanced features, a satellite must run this version.
		FPGA	1.13
5.1.2		Cisco IOS / Kernel	327 (151-3.SVG2)
		ROMMON	127
		FPGA	1.13
5.1.3		Cisco IOS / Kernel	338.1 (151-3.SVI)
		ROMMON	127
		FPGA	1.13
5.2.0		Cisco IOS / Kernel	353 (151-3.SVH)
		ROMMON	127
		FPGA	1.13
5.2.1		Cisco IOS / Kernel	353 (151-3.SVH)
		ROMMON	127
		FPGA	1.13
5.2.2		Cisco IOS / Kernel	378 (151-3.SVH2)
		ROMMON	127
		FPGA	1.13
5.3.0		Cisco IOS / Kernel	530.101 (151-3.SVI)
		ROMMON	127.0
		FPGA	1.13
5.3.1		Cisco IOS / Kernel	531.101
		ROMMON	127.0
		FPGA	1.13
5.3.2		Cisco IOS / Kernel	532.101
		ROMMON	127.0
		FPGA	1.13

901

XR Release	FCS or SMU	Image Type	Image Version	Notes
4.3.0	FCS	Cisco IOS / Kernel	1212.1
		ROMMON	2.1
		FPGA	n/a
4.3.1	FCS	Cisco IOS / Kernel	1304.23
		ROMMON	2.1
		FPGA	n/a
4.3.2	FCS	Cisco IOS / Kernel	1308.18
		ROMMON	2.1
		FPGA	n/a
4.3.4	FCS	Cisco IOS / Kernel	1312.06
		ROMMON	2.1
		FPGA	n/a
5.1.0	FCS	Cisco IOS / Kernel	1308.18
		ROMMON	2.1
		FPGA	n/a
5.1.1	FCS	Cisco IOS / Kernel	1401.13
		ROMMON	2.1
		FPGA	n/a
5.1.2	FCS	Cisco IOS / Kernel	1404.11
		ROMMON	2.1
		FPGA	n/a
5.1.3	FCS	Cisco IOS / Kernel	1408.01
		ROMMON	2.1
		FPGA	n/a
5.2.0	FCS	Cisco IOS / Kernel	1406.12
		ROMMON	2.1
		FPGA	n/a
5.2.1	FCS	Cisco IOS / Kernel	1406.12
		ROMMON	2.1
		FPGA	n/a
5.2.2	FCS	Cisco IOS / Kernel	1409.29
		ROMMON	2.1
		FPGA	n/a
5.3.0	FCS	Cisco IOS / Kernel	1409.29
		ROMMON	2.1
		FPGA	n/a

Known Issues

Image Download Fails

Saw the following message which indicates something blocking the image transfer

SAT9K_IMG_DOWNLOADER-3-TFTP_READ_FAIL: FTP download failure for 4502A1__.FPG with 
error code:-3

Suggestion: Check the Management Plane Protection (MPP) configuration in order to ensure that TFTP is set to allowed for the Inter-Chassis Link (ICL) port.

Image Download Incorrectly Says Completed

In this scenario, the Interface Control Plane Extender (ICPE) reports that the install completes, but when you check the satellite, it does not run the latest version.

RP/0/RSP0/CPU0:asr9k#install  nv satellite 101 transfer  progress
Wed Dec 18 16:36:43.381 CST
1 configured satellite has been specified for transfer.
1 satellite has successfully initiated transfer.
 | Working...RP/0/RSP0/CPU0:Dec 18 16:37:00.072 CST: icpe_gco[1148]:
 %PKT_INFRA-ICPE_
GCO-6-TRANSFER_DONE : Image transfer completed on Satellite 101
Press Ctrl+C at any time to stop displaying the current progress.
Completed.
1 satellite has successfully completed the transfer operation: 101.

RP/0/RSP0/CPU0:asr9k#install  nv  satellite  101 activate  progress
Wed Dec 18 16:37:26.943 CST
WARNING: This will take the requested satellite out of service.
Do you wish to continue? [confirm(y/n)] y
1 configured satellite has been specified for install.
1 satellite has successfully initiated install.
<snip>
RP/0/RSP0/CPU0:Dec 18 16:37:29.962 CST: icpe_gco[1148]:
 %PKT_INFRA-ICPE_GCO-6-INSTALL_DONE : 
Image install completed on Satellite 101
RP/0/RSP0/CPU0:Dec 18 16:37:29.968 CST: invmgr[262]:
 %PLATFORM-INV-6-OIROUT : OIR: Node 101 
removed
Completed.
1 satellite has successfully completed the install operation: 101.

RP/0/RSP0/CPU0:asr9k#show nv satellite  status  satellite 101
Wed Dec 18 16:39:09.258 CST
Satellite 101
-------------
  State: Connected (Stable)
  Type: asr9000v
  MAC address: 8478.ac05.8a14
  IPv4 address: 101.101.101.101
  Configured Serial Number: CAT1733U1K2
  Received Serial Number: CAT1733U1K2
  Remote version: Compatible (not latest version)

    ROMMON: 125.0 (Latest)
    FPGA: 1.13 (Latest)
    IOS: 210.0 (Available: 292.0)

What to examine:

MPP configuration (see previous section).
If the progress keyword is used in the install CLI, do NOT use the progress keyword prior to Version 5.1.2 or 5.2.0.
Ensure that TFTP homedir is NOT set (for example, tftp vrf default ipv4 server homedir disk0:).
If the satellite is an ASR901, the installation might fail due to space limitations. The recommendation is to delete non-nV images from the 901 flash and execute sqeeze flash: in order to free space.

Note: Image transfer should take approximately five minutes.

5.1.1 Dual-Home Issue

There is a known issue when you upgrade from Version 5.1.1 to Version 5.1.2 or when you downgrade that might cause the upgrade to fail, which is documented in Cisco bug ID CSCuo41004.

<B>Symptom:</B>

During an upgrade from 5.1.1 or downgrade to 5.1.1 scenario, both hosts of a dual 
head satellite configuration become the standby host for the satellite. This 
stops traffic.

<B>Conditions:</B>

A dual head topology for nV ICPE configuration and one of the hosts being 5.1.1, with 
the other being a later version.

<B>Workaround:</B>

Ensure that the secondary host is the host that is running 5.1.1. So during an upgrade 
from 5.1.1, then upgrade the primary host first; during a downgrade to 5.1.1, then 
downgrade the secondary host first.

The primary host can be identified using the <cmdBold>show nv satellite protocol 
redundacy<noCmdBold> command.

An alternative option (if only a few satellites have been configured) is to explicitly 
configure host priorities for the 2 hosts.

<B>Further Problem Description:</B>

The dual system will recover when both systems have the same version.

If testing between versions is required, then the user must explicitly configure host 
priorities.

Revision History

Revision	Publish Date	Comments
1.0	21-Apr-2016	Initial Release

Contributed by Cisco Engineers

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

This Document Applies to These Products

ASR 9000 Series Aggregation Services Routers

Upgrade nV Satellite

Available Languages

Bias-Free Language

Contents

Introduction

Auto-Upgrade

Single-Homed

Dual-Homed

Connectivity Checks

Verify Satellite Status

Check Configuration

Verify Satellite Status (Brief)

Host Priority Change

Change Host-priority

Verify Host-priority Change

Host Upgrade

Satellite Upgrade

Verify a Satellite Upgrade

Appendix

Tips and Tricks

Upgrade Multiple Satellites

Upgrade a Ring of Satellites

Example: Wrong Way to Upgrade

Example: Correct Way to Upgrade

Upgrade Multiple Satellites at Once

Example: Auto-Upgrade of a Satellite

Satellite Images

9000v

901

Known Issues

Image Download Fails

Image Download Incorrectly Says Completed

5.1.1 Dual-Home Issue

Revision History

Contributed by Cisco Engineers

Was this Document Helpful?

Contact Cisco

This Document Applies to These Products