Reference Guide

Detailed
Description
The server identified in the message cannot be accessed remotely by iDRAC
because of one or more of the following reasons: 1) iDRAC is not ready. 2)
Lifecycle Controller for of the server is disabled.
Recommended
Response Action
Make sure that the iDRAC on the server identified in the message is operating
properly and that Lifecycle Controller is enabled, and then retry the operation. If
the issue persists, perform a virtual reseat of the server and retry the operation. The
server can be virtually reseated by using the CMC Web GUI interface and selecting
Chassis Overview > Troubleshooting > Reset Components and then selecting
Virtual Reseat from the drop down menu.
Category Configuration (SWC = Software Config)
Severity Severity 2 (Warning)
Filter
Visibility
IPMI
Alert
SNMP
Alert
Email
Alert
Remote System
Log
WS
Eventing
iDRAC ✔
CMC ✔
LC Log LCD OS Log Power
Off
Power
Cycle
Reset Chassis Event
Proxy
iDRAC ✔*
CMC ✔* ✔*
SWC8617
Message Server Profiles: request arg1 for server in slot arg2 was unsuccessful. Returned
fault: arg3 .
Arguments arg1 = wsman method, arg2 = slot number, arg3 = wsman fault
Detailed
Description
The request by the WS-Man method identified in the message for the server in slot
identified slot is unsuccessful.
Recommended
Response Action
Make sure that iDRAC is ready and system is functioning properly. Run the
RACADM command "racadm getversion" to list all the servers and make sure the
iDRAC version is displayed. If the iDRAC is listed as Not Ready then wait until iDRAC
is ready for use. A Virtual Reseat may be required.
Category Configuration (SWC = Software Config)
Severity Severity 1 (Critical)
Filter
Visibility
IPMI
Alert
SNMP
Alert
Email
Alert
Remote System
Log
WS
Eventing
iDRAC ✔
CMC ✔
1813