Previous Behavior: During a vPGW software upgrade from one Hermes version to another, the card lock status appears as UNKNOWN when using the show card info CLI command for all the cards in chassis. However, during a non-Hermes to Hermes upgrade, the status is displayed as Card Locked .

The preceeding example displays sthe Hermes to Hermes version upgrade output:

[local]laas-setup# show card info | grep "Card Lock"
  Card Lock               : UNKNOWN!!
  Card Lock               : UNKNOWN!!
  Card Lock               : UNKNOWN!!
  Card Lock               : UNKNOWN!!
  Card Lock               : UNKNOWN!!
  Card Lock               : UNKNOWN!!
[local]laas-setup#
[local]laas-setup#
[local]laas-setup#
[local]laas-setup# show card info | grep "CPU"
[local]laas-setup#

New Behavior: When upgrading both Hermes and non-Hermes software versions to the latest Hermes version, the card lock status will be displayed as NA and an additional CPU information for grep status is shown.

The preceeding example displays the Card Lock and grep status with CPU information:

[local]laas-setup# show card info | grep "Card Lock"
  Card Lock               : NA
  Card Lock               : NA
  Card Lock               : NA
  Card Lock               : NA
  Card Lock               : NA
  Card Lock               : NA
[local]laas-setup#
[local]laas-setup#
[local]laas-setup#
[local]laas-setup# show card info | grep "CPU"
  CPU 0                   : Diags/Kernel Running, Tasks Running
  CPU 0                   : Diags/Kernel Running, Tasks Running
  CPU 0                   : Diags/Kernel Running, Tasks Running
  CPU 0                   : Diags/Kernel Running, Tasks Running
  CPU 0                   : Diags/Kernel Running, Tasks Running
  CPU 0                   : Diags/Kernel Running, Tasks Running
[local]laas-setup#