Specifications
6
Troubleshooting
130
RPT is incomplete; not all FRUs
present in the shelf have
associated Resources.
1. Initiate a discovery operation using the CLI command rediscoverShelf, using the saHpiDiscover()
function, or using the SNMP saHpiDiscover.0 variable. This will initiate a fresh discovery of the shelf and
create Resources for any FRU that was not already present in the RPT.
2. If the discovery fails to complete the RPT and Resources are missing for a FRU, try extracting that FRU and
re-inserting it in the shelf.
3. The IPMI bus may be locked up or too busy. Try removing other modules from the shelf that may be
causing IPMI bus errors. Then try running a discovery operation again.
4. Check if the FRU is in the Inactive hot-swap state (hot-swap LED is solid blue). The HPI server is not able
to detect complete FRU information when in this state and thus cannot create an associated resource for it.
Open and close the hot-swap ejector latch to activate full management access to the FRU, thus enabling
the HPI server to create the resource.
Sensor list in the RDR of a FRU’s
resource is incomplete; not all
expected sensors were found
Due to a communication error with the FRU during its activation phase, not all sensor data records (SDRs)
could be loaded from it. Extract the FRU and re-insert it to freshly create the resource.
The LCD panel on the ATCA-6000
shelf’s SDP is not updating, and
there is no backlight.
• The HPI server might still be initializing and going through a discovery process. Open a session on the HPI
server. If a SA_ERR_HPI_BUSY error code is returned, the server is still initializing and will start updating
the LCD with system health information once initialization is done.
• Check if there is a resource for the virtual SPM. The ResourceIds are listed in Table 13 on page 95.
If the virtual SPM resource is not present, check for the individual SPM resources. If they do not exist,
initiate a discovery operation using the CLI command rediscoverShelf, using the saHpiDiscover()
function, or using the SNMP saHpiDiscover.0 variable. If discovery fails to create Resources for the SPMs,
extract and re-insert the SPMs.
• If the SPM resource is present, communication between the SPM and SDP may have broken down. Send
some custom text to the LCD using control 0x9 on the SPM resource and determine if the LCD gets
updated with the text. If not, a shelf power cycle is required to re-enable the SDP LCD.
Cannot initiate hot-swap or power
management commands
Determine if the session from which the commands are being sent is opened on the SCM running the active
Shelf Manager. Take the following steps to ascertain if the current HPI service is running on the active Shelf
Manager:
1. Use the saHpiResourceIdGet() function to find the resource upon which the current HPI service is running.
2. Then check the reading from sensor 0x1002 in the Shelf Manager resource (ResourceId 0x2) using
saHpiSensorReadingGet() with SensorNum=0x1002 and ResourceId=0x2.
If the ResourceId from step1 does not match the sensor reading from step 2, then the current HPI service is
not the active instance. Close the current session and open a new session on the active HPI server using
the correct IP address of the active Shelf Manager as DomainID. See Chapter 4, Changing Shelf Settings
Using HPI, on page 53 for details on opening sessions on the HPI server running with the active Shelf
Manager.
• Determine if the resource is in the ResourceFailed state by checking the ResourceFailed flag in the RPT
entry. Extracting and re-inserting the FRU in such a condition can help re-establish management access to
it.
HPI commands on a particular
resource are failing.
Error code:
SA_ERR_HPI_NO_RESPONSE
Determine if the resource is in the ResourceFailed state by checking the ResourceFailed flag in the RPT entry.
If set to SAHPI_TRUE, the FRU associated with the resource is in a communication lost state with the Shelf
Manager. Extracting and re-inserting the FRU in such a condition can help re-establish management access to
it.
Table 15. Symptom/response for Shelf Manager problems (continued)
Symptom Response