In this section:

Verify the IO Configuration Files

This should only be done if the system contains IO cards. If there are no IO cards, do not runthe steps below.

Before upgrading the IO cards, the user must run the health check script for each card. This script verifies the existence of the mp_mtp2.conf.slot files on the IO card as well as its synchronization to the management CPU card. 

Start

  1. Log onto a Management CPU.
  2. Type the following script and press ENTER. 

    health_check_io.sh
  3. Input the I/O card slot number that you would like to check the health of. Press ENTER. 
  4. The script produces a health check result, which is either PASS or ERROR.
    1. If the result is ERROR, proceed to step 5.
    2. If the result is PASS, proceed to step 6. 
  5. If the result is ERROR, the issue is either missing or mismatched files on the IO card. When an issue is detected, the script allows the user to copy the necessary files from the management CPU card to the IO card. If all the files are retrieved successfully, then the result will be PASS. 
  6. If the health check result is PASS, then repeat this procedure with all remaining cards in the system. Once all cards have been verified, continue to Upgrading the Software on the IO Cards.

    Note

    Only proceed to the upgrade IO card progress if the health check result is PASS.

Upgrading the Software on the IO Cards

Tip

View the Alarm Dashboard and note what alarms are present (if any).

Start

  1. At the Linux prompt, enter startmenu and press ENTER.
  2. Select System and press ENTER.
  3. Select Software Revisions and press ENTER.
  4. Select IO Versions and press ENTER.
  5. Enter n to not add a new card, and press ENTER.
  6. If your system is says that your boot code is out-of-date, skip the boot code update, as this will be addressed later. Press ENTER.
  7. Enter the slot number for the I/O card as required and press ENTER.
  8. Enter u and press ENTER.

    Example
    Select action to take, or any other key to cancel: u
    
    Running IO software is out-of-date!
    
    You have opted to update/reboot slot #12, thereby loading
    the current software:
    -Load: stp_sp2k_21_0_3_nb20230118
    -OS: rel_12_00_p07.sp2k.img
    -Servicepack: [none applied]
    
    Pushing image to the IO card in slot #12
    Executing verify_io_image.sh script on IO board in slot #12
    DO NOT INTERRUPT!! THIS MAY TAKE A FEW MINUTES...
    Done: flashed Nexus image to IO board kernel0 and kernel1
    Ensuring internal0 (DHCP) settings in /etc/pticonfig on IO card in slot #12.
    internal0 (DHCP) already disabled in /etc/pticonfig on IO card in slot #12.
    Ensuring internal0 LAG monitoring settings in /etc/pticonfig on IO card in slot #12.
    Ensuring internal1 network value in /etc/pticonfig on IO card in slot #12.
    Chassis Type value on IO: [ CHASSIS_TYPE="14SLOT" ]
    Enter 'y' to continue: 
  9. Enter y and press ENTER.
    The software upgrade for each I/O card takes about 10 minutes.

  10. When prompted, press ENTER to continue.
  11. Once the I/O card completes its reboot, wait a minute for links to recover and all cards appear in the chassis graphic in the GUI (see graphics below). Review the alarm banner and compare with alarms from before this procedure. If any new alarms remain you can review the alarm details as outlined in the Alarms Guide.
    If new alarm remains a concern and cannot be resolved, please contact your next level of support.

    The I/O card disappears from the GUI when it is not yet recovered. When all cards are in the GUI, the card is functional again. The following images depict what all four cards look like in the GUI for a 3U slot chassis, and a 14SLOT or 13U chassis, respectively. 





  12. Repeat this procedure starting at Step 4 for all other I/O cards in the system (as required).
    Make sure that alarms on the Alarm Dashboard are the same as before upgrading, and the system is behaving as expected.
  13. After the software upgrade is completed, make sure that the upgrade was successful and the software was properly installed (see Verify Software is Properly Installed on the IO cards). 

Verify Software is Properly Installed on the IO cards

Start

  1. At the Linux prompt, enter startmenu and press ENTER.
  2. Select System and press ENTER.
  3. Navigate to the Software Revisions screen.
  4. Select IO Versions and press ENTER.
  5. Enter n and press ENTER.

    Note

    There will be an asterisks beside any cards that are running software that is out of date. 


  6. Type u and press ENTER. This will update the boot code for one of the I/O cards. Wait for the card to upgrade and then repeat for each card that is out of date. 
  7. Press ENTER. The following message appears:

    No selection, exiting.
    Press <return> to continue.
  8. Press ENTER.

Optional: Perform test calls as required to make sure that routing through the upgraded I/O cards is successful.

Optional: Log into either MGMT CPU and run the following command where the numbers are relative to the IO cards installed in the system (in this example we use slot12, slot13 and slot22). Verify the Bootcode is correct. 

# for slot in 12 13 22
> do
> echo "SLOT: $slot"
> rsh slot${slot}_0 "pti_info bootrev"
> echo
> done
Example
# for slot in 12 13 22
> do
> echo "SLOT: $slot"
> rsh slot${slot}_0 "pti_info bootrev"
> echo
> done
SLOT: 12
Bootcode Revision   : 810Q0991.13
 
SLOT: 13
Bootcode Revision   : 810Q0991.12
 
SLOT: 22
Bootcode Revision   : 810Q0991.12


  • No labels