# Last Modified Date: 11/15/19-01:51:14
################################################################################
#
# Readme for SMU asr9k-x64-6.6.2.CSCvr50987
#
# Copyright (c) 2019 by Cisco Systems, Inc.
# All rights reserved.
#
################################################################################

Date Generated:          Wed Oct 30 08:08:36 PDT 2019

Owner:                   sajshah

Name:                    asr9k-x64-6.6.2.CSCvr50987

Package(s):              iosxr-mgbl

Compressed File Size:    22288145 bytes

Uncompressed File Size:  22288145 bytes

DDTS:                    CSCvr50987

Description:             Socket Bind/Attach error on scale 100 IPSLA ICMP echo sessions

RPMS: 
	asr9k-mgbl-x64-2.0.0.2-r662.CSCvr50987.x86_64.rpm f22151b45fb3f31004337ae6ec965bab
	
Pre-requisites:          None

Supercedes:              
          asr9k-x64-6.6.2.CSCvp73437   Full

Incompatibility:         

Restart Type:            dependent

Cards:                   None

MD5:                     f22151b45fb3f31004337ae6ec965bab

SMU Install Impact:      Hitless;

**********************************************************
CONSTITUENT SMU DETAILS:

Name:                    iosxr-mgbl
Pre-requisites:          
Incompatibility:         
Restart Type:            dependent
Cards:                   
MD5:                     f22151b45fb3f31004337ae6ec965bab


SMU Install Questions:
----------------------
1- Console/error messages during SMU activation/deactivation?  Please specify the safe messages to ignore
RP/0/RSP0/CPU0:ios#install activate id 4 synchronous 
Mon Oct 28 08:01:57.147 UTC
Oct 28 08:01:58 Install operation 5 started by lab:
  install activate id 4 synchronous 
Oct 28 08:01:58 Package list:
Oct 28 08:01:58     asr9k-mgbl-x64-2.0.0.2-r662.CSCvr50987.x86_64
Oct 28 08:02:02 Action 1: install prepare action started
Oct 28 08:02:06 The prepared software is set to be activated with process restart
Oct 28 08:02:18 Start preparing software for local installation
Oct 28 08:02:29 Action 1: install prepare action completed successfully
Oct 28 08:02:30 Action 2: install activate action started
Oct 28 08:02:30 The software will be activated with process restart
Oct 28 08:02:31 Activating XR packages
Oct 28 08:04:16 0 processes affected at node 0/RSP0/CPU0
Oct 28 08:04:49 0 processes affected at node 0/3/CPU0
Oct 28 08:05:02 Action 2: install activate action completed successfully
Oct 28 08:05:36 Install operation 5 finished successfully
Oct 28 08:05:36 Ending operation 5
RP/0/RSP0/CPU0:Oct 28 08:05:36.607 UTC: sdr_instmgr[1213]: %INSTALL-INSTMGR-2-OPERATION_SUCCESS : Install operation 5 finished successfully 
RP/0/RSP0/CPU0:ios#


RP/0/RSP0/CPU0:ios#install deactivate asr9k-mgbl-x64-2.0.0.2-r662.CSCvr50987 s$
Wed Oct 30 08:39:55.063 UTC
Oct 30 08:39:56 Install operation 7 started by lab:
  install deactivate pkg asr9k-mgbl-x64-2.0.0.2-r662.CSCvr50987 synchronous 
Oct 30 08:39:56 Package list:
Oct 30 08:39:56     asr9k-mgbl-x64-2.0.0.2-r662.CSCvr50987
Oct 30 08:39:57 Action 1: install deactivate action started
Oct 30 08:40:14 The software will be deactivated with process restart
Oct 30 08:40:15 De-activating XR packages
Oct 30 08:41:03 1 processes affected at node 0/RSP0/CPU0
Oct 30 08:41:03   ipsla_sa                (unchanged)
Oct 30 08:41:37 0 processes affected at node 0/3/CPU0
Oct 30 08:41:50 Action 1: install deactivate action completed successfully

Oct 30 08:42:21 Install operation 7 finished successfully
Oct 30 08:42:21 Ending operation 7
RP/0/RSP0/CPU0:Oct 30 08:42:21.752 UTC: sdr_instmgr[1213]: %INSTALL-INSTMGR-2-OPERATION_SUCCESS : Install operation 7 finished successfully 
RP/0/RSP0/CPU0:ios#

2- Are there any side effects to this SMU that require workaround? (for example AAA SMU requiring exit out of current session and reconnecting after install).  If so what?
No side effects and no workaround needed.

SMU Caveats:
- Process restart ipsla_sa happens during SMU activation and deactivation.
- When the reachability between IPSLA sender and the peer is down, the socket fd exhaustion problem will begin again. This is because the optimisation will not apply when the reachability is down. To avoid the fd exhaustion, either restore reachability, or stop ipsla operations. 
 
 
 
