8.7 Checking the XCP Firmware Version
8.7 Checking the XCP Firmware Version
This section describes the procedure for checking the XCP firmware version after XSCF unit maintenance work.
The XCP firmware version of each chassis in the building block configuration must be the same.
The XCP firmware version of each chassis in the building block configuration must be the same.
- Log in to the XSCF, and confirm that the XCP firmware version is the same as before XSCF unit replacement.
- If the XCP firmware version is different between the maintenance part and the existing system, the message "XSCF firmware update now in progress. BB#xx, please wait for XSCF firmware update complete." appears at login to the XSCF. Then, the XCP firmware version will be automatically matched.
Password: ***** XSCF firmware update now in progress. BB#81, please wait for XSCF firmware update complete. XSCF> |
- The version matching takes about 50 minutes.
If the above message appears, execute the showlogs monitor command, and check for the "XCP firmware version synchronization completed" message. The message indicates the completion of XCP firmware matching. Then, perform the work below.
XSCF> showlogs monitor Jul 7 14:51:43 SPARCM12 Event: SCF:XCP firmware version synchronization started Jul 7 14:51:43 SPARCM12 Event: SCF:XSCF firmware update is started (BB#81) Jul 7 14:51:43 SPARCM12 Information: /XBBOX#81/XSCFU:SCF:SCF Diagnosis initialize RTC (*1) Jul 7 14:51:43 SPARCM12 Alarm: :SCF:Gaps between XBBOX-ID (*2) Jul 7 14:51:44 SPARCM12 Event: SCF:XSCF ready Jul 7 15:28:25 SPARCM12 Event: SCF:Standby XSCF Ready(BB#81) : Jul 7 15:40:17 SPARCM12 Event: SCF:XSCF update has been completed (BBID=81, bank=0) Jul 7 15:40:18 SPARCM12 Event: SCF:XCP update has been completed (XCP version=3080:last version=3090) Jul 7 15:40:18 SPARCM12 Event: SCF:XSCF firmware update has been completed (BB#81) Jul 7 15:40:18 SPARCM12 Event: SCF:XCP firmware version synchronization completed |
*1 If the "SCF:SCF Diagnosis initialize RTC" message appears, ignore the message.
*2 If the "SCF:Gaps between XBBOX-ID" message appears, ignore the message.
*2 If the "SCF:Gaps between XBBOX-ID" message appears, ignore the message.
- Execute the version command to check the firmware version on every crossbar box and SPARC M12-2S/M10-4S.
- The command displays the overall XCP firmware version.
Confirm that the XCP firmware version on each crossbar box and SPARC M12-2S/M10-4S is the same as the master XSCF version.
If they are the same, steps 3 and later are not necessary. If they are not the same, perform steps 3 and later.
XSCF> version -c xcp XBBOX#80-XSCF#0 (Master) CP0 (Current): xxxx CP1 (Reserve): xxxx BBOX#81-XSCF#0 (Standby) CP0 (Current): xxxx CP1 (Reserve): xxxx BB#00-XSCF#0 XCP0 (Current): xxxx XCP1 (Reserve): xxxx BB#01-XSCF#0 XCP0 (Current): xxxx XCP1 (Reserve): xxxx BB#02-XSCF#0 XCP0 (Current): xxxx XCP1 (Reserve): xxxx BB#03-XSCF#0 XCP0 (Reserve): xxxx XCP1 (Current): xxxx |
- If the XCP firmware version is not the same, execute the getflashimage -l command to check whether the XCP image file of the version before XSCF unit replacement is saved on the master XSCF.
- If not saved, import the XCP image file.
The following example imports the XCP image file of the version before XSCFU replacement.
XSCF> getflashimage -l Existing versions: Version Size Date BBXCP3060.tar.gz 107650264 Thu Aug 06 08:54:02 JST 2020 XSCF> getflashimage file:///media/usb_msd/xxxx/BBXCP3080.tar.gz |
- Execute the flashupdate -c sync command to match the XCP firmware version on all crossbar boxes and SPARC M12-2S/M10-4S units.
Match the XCP firmware version with the master XSCF version.
XSCF> flashupdate -c sync XCP update is started. [3600sec] 0..... 30..... 60..... 90.....120.....150.....180.....210.....240..... 270.....300.....330.....360.....390.....420.....450.....480.....510..... |
- Execute the showlogs monitor command, and check for the "XCP update has been completed" message. The displayed message indicates the completion of the XCP firmware update.
XSCF> showlogs monitor Sep 8 13:39:31 SPARCM12 Event: SCF:XCP update is started (XCP version=3080:last version=3080) Sep 8 13:41:55 SPARCM12 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=81, bank=1) Sep 8 13:42:20 SPARCM12 Event: SCF:Updating XCP:Updating XSCF (BBID=81, XSCF version=03080000) Sep 8 13:46:35 SPARCM12 Event: SCF:Updating XCP:XSCF updated (BBID=81, bank=1) Sep 8 13:46:35 SPARCM12 Event: SCF:Updating XCP:XSCF bank has changed (BBID=81, bank=1, XCP version=3080:last version=3090) Sep 8 13:52:32 SPARCM12 Event: SCF:Standby XSCF Ready(BB#81) Sep 8 13:53:16 SPARCM12 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=81, bank=0) Sep 8 13:53:39 SPARCM12 Event: SCF:Updating XCP:Updating XSCF (BBID=81, XSCF version=03080000) Sep 8 13:57:35 SPARCM12 Event: SCF:Updating XCP:XSCF updated (BBID=81, bank=0) Sep 8 14:03:16 SPARCM12 Event: SCF:XCP update has been completed (XCP version=3080:last version=3080) |
- Execute the version command to check the XCP firmware version on every crossbar box and SPARC M12-2S/M10-4S.
XSCF> version -c xcp XBBOX#80-XSCF#0 (Master) XCP0 (Current): xxxx XCP1 (Reserve): xxxx XBBOX#81-XSCF#0 (Standby) XCP0 (Current): xxxx XCP1 (Reserve): xxxx BB#00-XSCF#0 XCP0 (Current): xxxx XCP1 (Reserve) : xxxx ÛB#01-XSCF#0 XCP0 (Current): xxxx XCP1 (Reserve): xxxx BB#02-XSCF#0 XCP0 (Current): xxxx XCP1 (Reserve): xxxx BB#03-XSCF#0 XCP0 (Reserve): xxxx XCP1 (Current): xxxx |
< Previous Page | Next Page >