Two-disk ISG proxy application is unresponsive after SSP appliance reboot

Products

• ISG Proxy

Issue/Introduction

- SSP (ISG OS) appliance is booted to previous version after power outage. Two-disk (marked as -B) ISG proxy become inaccessible after reboot.  

- CLI command show applications does not show any details for ISG proxy:

isg# show applications

 

NAME TYPE VCPU MEMORY DISK SIZE MODEL STATUS LICENSE ID IMAGE ID ZTP NETWORK DEFINITION

-----------------------------------------------------------------------------------------------------------

proxySG - - - - - - - - - -

 

- Any attempt to stop and restart application fails with error "Error: Invalid command, current application status does not allow stop"

isg(config)# applications stop proxySG
Error: Invalid command, current application status does not allow stop
isg(config)# applications restart proxySG
Error: Invalid command, current application status does not allow stop

- Attach console command is failing  with following error:

isg# applications attach-console proxySG
Invalid command, current application status does not allow attach-console.

 

Environment

-  Two-disk ISG proxy (marked as -B) is running on top of SSP platform. 

Cause

- Two-disk models of ISG proxies are supported under 2.4.7.1 and later versions. In case if  SSP appliance boots to previous versions prior 2.4.7.1, two-disk proxies won't run.  

 

Resolution

- Verify installed ISG OS versions using cli command "installed-systems view".

isg# installed-systems view
1. Version : 2.4.7.1, Release ID : XXXXXX, Locked : false, Booted : true
Boot Status : Last boot failed, BuildType : Release, CreationTime : XXXX-XX-XXTXX:XX:XX+0000
BootTime : XXXX-XX-XXTXX:XX:XX+0000, DisplayName : ISG 2.4.7.1

2. Version : 2.4.3.1, Release ID : XXXX, Locked : false, Booted : true
Boot Status : Last boot succeeded, BuildType : Release, CreationTime : XXXX-XX-XXTXX:XX:XX+0000
BootTime : XXXX-XX-XXTXX:XX:XX+0000, DisplayName : ISG 2.4.3.1

- Stop all applications using cli command "application stop <application_name>". 

- Set default version to 2.4.7.1 and reboot the appliance using cli  command "installed-systems default 1".

- Verify changes using cli command "installed-systems view". You should see "Default system to run on next hardware restart: 1":

- Restart the SSP appliance using cli command "restart"