| Add_workflow_for_techpubs |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca67042e, userName='null'} |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5007d7, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca64041c, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef40cd9, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb870607, userName='null'} |
|---|
| REV2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c820009a, userName='null'} |
|---|
|
| Info |
|---|
|
Re-installing a SBC system from an ".iso" image followed by restoring SBC configuration from a tar.gz backup file may lead to loss of encrypted configuration parameters in the following scenarios: - re-installing a standalone SBC from an ".iso" image followed by restoring SBC configuration from a "tar.gz" backup file
- re-installing both nodes in an HA SBC pair from an ".iso" image followed by restoring SBC configuration from a "tar.gz" backup file
Activities like replacing a single node in an HA pair (as an RMA for example) or re-installing a single node in an HA pair at a time are safe. The node that has just been re-installed will take the current configuration from the active node. For details please refer to Sonus Warning: Warning-17-00022737. |
Perform the following steps to restore the
configuration using CLI:
...