Internal device ID has unexpectedly changed for ISG Proxy

Products

• Management Center - VA

Issue/Introduction

Management Center reports that the unique Device Identifier has unexpectedly changed on ISG Proxy. When trying to reconcile this, the following error is observed:

Device Identifier cannot be updated, because the same ID is already used by other ISG Proxy.

When trying to add a problematic ISG Proxy to the Management Center you may also see the following error (Device activation failed):

 

Environment

• ISG proxies deployed on SSP appliance 
• ISG proxies are configured to use custom network-definition

Cause

When network-definition assigned to your ISG Proxies does not contain 0:0 interface, all ISG Proxies will share the same Appliance Identifier.

Resolution

1. Stop the application:
   ISG(config-applications)# stop <app-name>
2. Edit the network definition:
   ISG(config-network-definition)# edit <net-def-name> add mode shared interface 0:0
3. Start the application
   ISG(config-applications)# start <app-name>

There's no need to redeploy application. Appliance Identifier will update itself.

Additional Information

To verify Appliance Identifier used by each of your ISG Proxy, you can use the following command:

To check the network definition config, please use the following command:

ISG(config-network-definition)# view
Network Definition: auto
        Interfaces (shared): 0:0 1:0 2:0 3:0
Network Definition: lab
        Interfaces (shared): 1:0 2:0

To check which network-definition is assigned to your applications, please use the following command:

ISG(config-applications)# view
NAME      TYPE  VCPU  MEMORY   DISK SIZE  MODEL      STATUS     LICENSE ID   IMAGE ID             ZTP NETWORK DEFINITION
--------  ----  ----  -------- ---------- ---------- ---------- ------------ -------------------- --- ------------
ProxyISG  SG    2     12 GB    200 GB     C2S        Running    XXXXXXXXXX   sg-7.3.14.1-285017       lab