- Notes, cautions, and warnings
- Introduction
- Preinstallation setup
- Installing iDRAC Service Module
- Initial installation of iDRAC Service Module through iDRAC Enterprise or Datacenter or iDRAC Express on Microsoft Windows and Linux
- Installing iDRAC Service Module on Microsoft Windows operating systems
- Silent installation of iDRAC Service Module on Microsoft Windows
- Modifying iDRAC Service Module components on Microsoft Windows operating systems
- Repairing iDRAC Service Module running on Microsoft Windows operating systems
- Uninstalling iDRAC Service Module running on Microsoft Windows operating systems
- Installing iDRAC Service Module on VMware ESXi
- Preinstallation requirements for VMware ESXi
- Installing iDRAC Service Module on VMware ESXi using CLI
- Installing iDRAC Service Module using the vSphere CLI
- Installing iDRAC Service Module using VMware Update Manager
- Upgrading iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module using vSphere Lifecycle Manager in vSphere Client
- Using the Power CLI
- Uninstalling iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module on supported Linux operating systems
- Installing iDRAC Service Module when System Configuration Lockdown mode is enabled in iDRAC
- Configuring iDRAC Service Module
- Security configurations and compatibility
- Features
- S.M.A.R.T monitoring
- Operating system information
- Lifecycle Controller log replication into operating system
- Automatic system recovery
- Windows Management Instrumentation Providers
- Prepare to remove a NVMe PCIe SSD device
- Remote iDRAC hard reset
- iDRAC access via Host OS
- Accessing iDRAC via GUI, WS-Man, Redfish, and Remote RACADM
- In-Band support for iDRAC SNMP alerts
- Mapping iDRAC Lifecycle Logs to OMSA and OMSS SNMP alerts
- Enable WS-Man remotely
- Autoupdating iSM
- FullPowerCycle
- SupportAssist on the box
- Configuring the In-Band SNMP Get feature—Linux
- Configuring the In-Band SNMP Get feature—Windows
- iDRAC GUI Launcher
- Single sign-on to iDRAC UI from host operating system administrators desktop
- IPv6 communication between iSM and iDRAC over OS to iDRAC Pass-through
- Isolation of OS to iDRAC Pass-through Independent feature
- Software RAID
- Frequently asked questions
- Linux and Ubuntu installer packages
- Resources and support
- Contacting Dell EMC
Dell EMC iDRAC Service Module 4.2.0.0 User’s Guide
FullPowerCycle
FullPowerCycle is a calling interface function that provides a way to reset the server auxiliary power. An increasing amount of server hardware runs on server auxiliary power. Troubleshooting of some server issues requires you to physically unplug the server power cable to reset the hardware running on auxiliary power.
The FullPowerCycle feature enables the administrator to connect or disconnect auxiliary power remotely without visiting the data center. This feature is supported on PowerEdge yx5x servers.
When a FullPowerCycle Request is issued through this interface, system power is not immediately affected. Instead, a flag is set that is queried when the system transitions to S5. For the FullPowerCycle feature to take effect, after issuing the request command you must also issue system shutdown command. If the flag is set on S5 entry, the system is temporarily forced into a lower power state, similar to removing and replacing AC. The flag can be cleared using the Cancel function anytime the system is in the S0 state prior to the system entering the S5 state.
You can avail different options of FullPowerCycle on your system. Use the following commands to request, get status, and cancel the FullPowerCycle on your system:
For Windows Operating systems, shortcut menus are available for the FullPowerCycle Activate (request), FullPowerCycle Cancel, and FullPowerCycle get status operations.
| Commands to run in the power shell console | Descriptions |
|---|---|
| Invoke-FullPowerCycle — request | To request FullPowerCycle on your system.
NOTE A message is displayed that the VirtualAC Power Cycle operation is triggered by the server operating system.
|
| Invoke-FullPowerCycle - get status | To get the status of the FullPowerCycle on your system.
NOTE A message is displayed that the system is going for turn off at the scheduled date and time.
|
| Invoke-FullPowerCycle - cancel | To cancel the FullPowerCycle on your system. |
For Linux and VMware ESXi operating systems, shortcut menus are available for the FullPowerCycle Activate (request), FullPowerCycle Cancel and FullPowerCycle get status operations.
| Commands to run in the power shell console | Descriptions |
|---|---|
| /opt/dell/srvadmin/iSM/bin/Invoke-FullPowerCycle request | To request FullPowerCycle on your system. |
| /opt/dell/srvadmin/iSM/bin/Invoke-FullPowerCycle cancel | To cancel the FullPowerCycle on your system. |
| /opt/dell/srvadmin/iSM/bin/Invoke-FullPowerCycle get-status | To get FullPowerCycle status on your system. |
The following messages are displayed after each successful FullPowerCycle operation on operating system log files and LCL:
Request message: "The Full Power Cycle operation is triggered by the server operating system (OS) user <user name> from the OS on date <date>. However, the server components will be AC power cycled when the server is shut down".
Cancel Message: "The Full Power Cycle operation is successfully cancelled by the server operating system (OS) user <user name> from the OS on date <date>".
NOTE The FullPowerCycle feature is available for ESXi 7.x operating system, but not for ESXi 6.x operating systems.
NOTE The FullPowerCycle feature can be used only with local or domain administrator, or root or sudo users.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\