Guest

Preview Tool

Cisco Bug: CSCvu13162 - CLMS not re registered in restore operations though registered during backup creation

Last Modified

May 18, 2020

Products (1)

  • Cisco Crosswork Network Automation

Known Affected Releases

3.2.1

Description (partial)

Symptom:
In disaster recover scenario New CrossWork  is not  automatically re registered with CLMS post disaster recover operation with the existing backup file.. The backup file is generated when the product is registered with CLMS and backup has that information captured.

In restore scenario as well the product is not re registered automatically even though the backup file has CLMS registration information captured.

Conditions:
New Crosswork VM not  automatically re registered with CLMS post disaster recover operation

Post restore operation the product is not automatically re registered to CLMS server.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.