Problems Resolved in Version 1170 of the PCI Expansion Unit Firmware
Problems Resolved in Version 1170 of the PCI Expansion Unit Firmware
The following table lists the problems resolved in version 1170 of the PCI expansion unit firmware.
| RTI No. | RTIF2-210118-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When "PCI Express lane is degraded" is registered in the error log of the PCI expansion unit, a FRU may be mistakenly displayed as the target. |
| Workaround | There is no effective workaround. Update the PCI expansion unit firmware to 1170 or later, and the XCP firmware to XCP 2220 or later. |
| RTI No. | RTIF2-140902-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If input power for the PCI expansion unit is disconnected (AC OFF) or power failure occurs, a PSU "Information" level error log is supposed to be registered. However, a failure level error log "Alarm" is incorrectly registered. At this point, CHECK LED on the front of the PCI expansion unit lights up, "Faulted" is displayed on the PSU status, and the error message "AC Fail" is displayed. You can check the error message of this phenomenon by executing the showlogs error command, and check the status by executing the showhardconf command. [Error message example] XSCF> showlogs errorDate: Jul 10 16:25:02 JST 2014 Code: 80000400-00d4000000ff0000ff-1100002a0000000000000000 Status: Alarm Occurred: Jul 10 16:24:57.269 JST 2014 FRU: /BB#0/PCI#8/PCIBOX#2003/PSU#1 Msg: AC FAIL[PSU status example] XSCF> showhardconf : PCIBOX#2003; Status:Normal; Ver:1150h; Serial:2121152003; : * PSU#1; Status:Faulted; Serial:FEJD1201000170; |
| Workaround | Update the PCI expansion unit firmware to 1170 or later, and the XCP firmware to XCP 2220 or later. There is no impact on system operation from this phenomenon. |
| RTI No. | RTIF2-140902-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Link card fault may be incorrectly registered if logs related to one PCI expansion unit are registered more than once in a short time (5 to 10 minutes) when one or more physical partitions (PPAR) are operating in the configuration with PCI expansion units connected. For details on how to check this symptom, see "Confirmation Method of RTIF2-140902-002." |
| Workaround | Ignore this error message as it has no effect on the system. |
| RTI No. | RTIF2-131224-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The following error messages related to the link board may be displayed if the link board with Part Number "CA20365-B60X007AD/7061035" is connected to the PCI expansion unit. [Error message example 1] FRU: /BB#0/PCI#3/PCIBOX#1234/IOB,/BB#0/PCI#3/PCIBOX#1234/LINKBD Msg: PCI access error [Error message example 2] FRU: /BB#0/PCI#3/PCIBOX#1234/IOB Msg: PCI access error [Error message example 3] FRU: /BB#0/PCI#3/LINK,/BB#0/PCI#3/LINK/LINKCBL#-,/BB#0/PCI#3/PCIBOX#1234/LINKBD,* Msg: PCI Express lane is degraded The Part Number can be checked in the "Part Num" line upon executing the ioxadm -v list command. [Example] XSCF> ioxadm -v list Location Type FW Ver Serial Num Part Num State --- Omitted --- PCIBOX#9011/LINKBD BOARD - PP134701CJ CA20365-B60X 007AD/7061035 On |
| Workaround | There is no effective workaround. |
Confirmation Method of RTIF2-140902-002
The phenomenon of RTIF2-140902-002 can be checked in the following ways.
- Executing the showlogs error -v command outputs the following.- FRU displays "LINK" or "LINKBD"- Msg displays "TWI access error"- The first byte in the fourth line of the Diagnostic Code is "07"
- [Example of incorrect registration]
XSCF> showlogs error -vDate: Dec 20 10:50:05 JST 2013 Code: 80000480-001f010021ff00cc01-11000057d000000000000000 Status: Alarm Occurred: Dec 20 10:49:59.136 JST 2013 FRU: /MBU/PCI#1/LINK,/MBU/PCI#1/LINK/MGCBL,/MBU/PCI#1/PCIBOX#3001/LINKBD,* Msg: TWI access error Diagnostic Code: 00010000 00000000 0000 00010000 00000000 0000 00013330 30310000 0000 07100000 00000000 00000000 00000000 00000000 00000000 0000 |
- When the showlogs event command or showlogs error command is executed on the same PCI expansion unit within 10 minutes, the multiple logs shown below are registered.- 12 or more event logs related to the PCIe card are registered upon executing the showlogs event command. The number of event logs is calculated as follows depending on the event type.- PCIe card insertion event: 2- Event other than PCIe card insertion: 1For example, if a PCIe card is repeatedly inserted and removed four times, eight message lines are displayed. However, the number of registered event logs is 12, calculated by multiplying three events by four. This applies to this case.
- [Example of PCIe card insertion/removal]
| XSCF> showlogs event Dec 20 10:49:59 JST 2013 Attach operation (/BB#0/PCI#1/PCIBOX#3001/PCI#1) Dec 20 10:49:59 JST 2013 Detach operation (/BB#0/PCI#1/PCIBOX#3001/PCI#1) : |
- - Six or more logs are registered by the PCI expansion unit firmware (the first byte in the third field of Code is 11) upon executing the showlogs error command.
- [Example of log registration by PCI expansion unit firmware]
XSCF> showlogs errorDate: Jun 06 10:55:28 JST 2014 Code: 80000400-00d4000000ff0000ff-1100002a0000000000000000 Status: Alarm Occurred: Jun 06 10:55:28.028 JST 2014 FRU: /BB#0/PCI#1/PCIBOX#3001/PSU#0 Msg: AC FAILDate: Jun 06 10:55:34 JST 2014 Code: 10000400-00d4000000ff0000ff-1100002b0000000000000000 Status: Information Occurred: Jun 06 10:55:34.479 JST 2014 FRU: /BB#0/PCI#1/PCIBOX#3001/PSU#0 Msg: PSU RECOVERY: |
< Previous Page | Next Page >