advertisement
20
Managing remote tasks
About remote tasks
With the remote tasks feature in OpenManage Essentials, you can:
• Run commands on local and remote systems, run batch files and executable files on the local systems, and schedule local and remote tasks.
NOTE: Ensure that you run the latest commands to successfully execute the remote tasks.
NOTE: The files must be located on the system with OpenManage Essentials installed and not on the remote system.
• Change power status for a system.
• Deploy OpenManage Server Administrator on systems.
• Deploy iDRAC Service Module on systems.
• Collect firmware and driver inventory information from a server that does not have OpenManage Server Administrator (OMSA) installed.
• View the remote tasks.
• Make changes to any task by right-clicking it.
NOTE: If you stop a running task, it may take 3-4 minutes for the task to stop gracefully and the updated task status to get reflected in the console.
NOTE: The Task Execution History reflects the remote tasks that you created or deleted only after a few seconds.
NOTE: When providing system credentials, if the username has spaces or periods, the username must be provided within quotation marks. For example, "localhost\johnny marr" or "us-domain\tim verlaine". Spaces and periods can be used in usernames for OpenMange System Administrator Tasks, Generic Command Line Tasks (local system), OpenManage
Systems Administrator Deployment Tasks. System Updates (In Band, through OpenManage System Administrator) also support spaces and periods. Out of Band patching (through RAC device) or commands such as RACADM do not support space or period in the username.
Managing Command Line Task
You can create custom command line tasks to run CLI commands on local and remote systems, and run batch files and executables on local systems.
For example, you can create a custom command line task to run a security audit and gather information on the systems’ security status.
NOTE: The Remote Server Administrator Command task requires that the Windows Management Instrumentation service is running on the selected targets.
To create command line tasks:
1.
From OpenManage Essentials, click Manage → Remote Tasks → Common Tasks → Create Command Line Task.
.
2.
On General , provide a task name.
3.
Select one of the following options:
• Remote Server Administrator Command — Select to run the server administrator command on remote servers.
• Generic Command — Select to run the command, executable file, or batch file.
• IPMI Command — Select to run the IPMI commands on the remote system.
294
• RACADM Command Line — Select to run the RACADM commands on the remote system.
4.
Based on your selection in the preceding step, provide the following:
• If you selected Remote Server Administrator Command , then provide command, SSH port number, and select Generate
Trusted Key for Linux if you want to generate a trusted key.
• If you selected Generic Command, RACADM Command Line, or IPMI Command then provide command and append output information. Providing the append output information is optional.
5.
On Task Target, do one of the following:
• Select a query from the drop-down list or create a new query by clicking the New button.
• Select server targets for running the commands. Only applicable targets are displayed by default. For more information, see the
6.
On Schedule and Credentials , provide user credentials, and set schedule for the tasks from available options, and then click
Finish .
For information about the fields in the Create a Command Line Task wizard, see
.
Related links
Managing RACADM Command Line Tasks
RACADM command line tasks are used to run commands on remote DRACs and iDRACs. For example, run a RACADM task to configure iDRAC through out of band (OOB) channel. To manage RACADM Command line tasks:
1.
From OpenManage Essentials, click Manage → Remote Tasks → Common Tasks → Create Command Line Task .
2.
On General , choose RACADM Command Line and enter a name for the task.
3.
Enter the RACADM sub-command (for example, getsysinfo.
) For a list of RACADM commands, go to dell.com/support .
4.
(Optional) Choose Output to file to capture task output from multiple targets. Enter path and file name.
• To log the information from all selected targets, select Append .
• To write all the detected errors to the log file, select Include errors .
5.
On Task Target, do one of the following:
• Select a query from the drop-down list or create a new query by clicking the New button.
• Choose target servers or DRACs/iDRACs. Only applicable targets are displayed by default. For more information, see the
6.
On Schedule and Credentials , set the schedule parameters, provide target credentials and then click Finish .
Related links
Managing Generic Command Line Task
Using Generic command line task, you can run different types of tasks such as, a batch file, a script file such as a Powershell or VBS script, an executable, or a command, on the local OpenManage Essentials system. While the task always runs on the local
OpenManage Essentials system, you can structure the local task to interact with or act upon a variety of remote devices or servers.
295
You can enter tokens (substitution parameters) in the command line task to be passed to the script file, executable, command, or batch file and execute local scripts on devices that are discovered in OpenManage Essentials.
To manage Generic command line tasks:
1.
From OpenManage Essentials, click Manage → Remote Tasks → Common Tasks → Create Command Line Task.
2.
In the General tab, choose Generic Command .
3.
If required, update the task name.
4.
Enter the path and command (batch, script, or executable) to run on the local system.
5.
(Optional) Enter any arguments for the command. If $USERNAME and $PASSWORD are used in Arguments , you can pass the credentials to the command by the entering the credentials under Script Credentials . If $IP or $RAC_IP are used in
Arguments , you can run the command against the selected target(s) by passing the IP address of each target to the command.
NOTE: The tokens provided in the Arguments field must entirely be in either uppercase or lowercase. For example,
$HOSTNAME or $hostname.
NOTE: If you are running a command that does not require any tokens or arguments, the Script Credentials section and the Task Target tab are not displayed.
6.
(Optional) Choose Ping Device if you want to ping the device first.
7.
(Optional) Choose Output to file to capture task output from multiple targets. Enter path and file name.
• To log the information from all selected targets, select Append .
• To write all the detected errors to the log file, select Include errors .
8.
On Task Target, do one of the following:
• Select a query from the drop-down list or create a new query by clicking the New button.
• Select targets for running the commands.
9.
On Schedule and Credentials , enter the local administrator credentials with rights to run commands on the OpenManage
Essentials system. Set schedule for the task(s) and then click Finish .
Related links
About Tokens
The following tokens can be used to pass values to the batch, script, or executable file:
• $IP and $RAC_IP — If these arguments are used, the Task Target tab appears in the Create a Command Link Task screen. The
Task Target tab allows you to select the targets to pass the arguments. $IP is used for a server IP and $RAC_IP is used for a
RAC (iDRAC) IP. From the Task Target tab, you can select either groups, a device or use dynamic queries.
• $USERNAME and $PASSWORD — In some instances, you must provide credentials for a remote system in your batch or script file. If $USERNAME or $PASSWORD are used in arguments, the Script Credentials section appears for these values. The credentials entered in the Script Credentials section is passed to the command line. You can pass either of these values or both.
NOTE: You must enter both values in the Script Credentials section. If you do not need to use one value, enter any text in the field and it is ignored if the token is not in use.
• $NAME — This token passes the name of the system found in the OpenManage Essentials Device Tree . The name is most often the host name of the system, but in some instances it might be either an IP address or a string such as Dell Rack
System – SVCTAG1 .
Passing Tokens to a Script
If you are using a batch file or a script, use %1, %2, %3 , and so on to receive the values passed from OpenManage Essentials. The values are passed in the order they are entered from left to right in the Arguments field.
For example, if you use $USERNAME $PASSWORD $IP $RAC_IP $NAME as arguments, a batch file with the following Echo
%1 %2 %3 %4 %5 displays the following result:
C:\Windows\system32>echo scriptuser scriptpw 10.36.1.180 10.35.155.111 M60505-W2K8x64 scriptuser scriptpw 10.36.1.180 10.35.155.111 M60505-W2K8x64
296
NOTE: The credentials are passed in plain text to the command line. If you schedule a task to run later, the credentials are encrypted and stored in the database. The credentials are decrypted when the task runs at the scheduled time.
However, if you use the RUN option on a previously created task, enter both administrator credentials for the system and the script credentials.
Managing Server Power Options
You can create tasks to manage power on servers.
NOTE: The power task requires that the Windows Management Instrumentation service is running on the selected targets.
To create a remote task:
1.
From OpenManage Essentials, click Manage → Remote Tasks → Common Tasks → Create Power Task.
2.
In Create a Power Task , on General , do the following:
• Provide task name.
• Select power options. If required, select Shutdown OS first to shut the operating system down before starting the power tasks.
3.
On Task Target, do one of the following:
• Select a query from the drop-down list or create a new query by clicking the New button.
• Select server targets for running the commands.
4.
On Schedule and Credentials , set the schedule parameters, provide target credentials, and then click Finish .
For information about the fields in the Create a Power Task wizard, see
.
Related links
Deploying Server Administrator
The deploy OpenManage Server Administrator task requires the following on the selected targets:
• Windows Management Instrumentation service must be running.
• The default Temp folder (C:\Users\<username>\AppData\Local\Temp) must be available. Ensure that the Temp folder is not deleted or moved.
You can create tasks to deploy OpenManage Server Administrator (OMSA) on servers running Windows or Linux operating systems.
You can also plan a date and time to schedule the OMSA deploy task.
To create an OpenManage Server Administrator deployment task:
1.
Click Manage → Remote Tasks → Common Tasks → Create Deployment Task.
2.
On General , select Server Administrator and provide a task name. If you want to deploy OpenManage Server Administrator on
Windows-based servers, then select Windows , provide installer path and, if required, provide arguments. If you want to deploy
OpenManage Server Administrator on Linux-based servers, select Linux and provide the installer path and, if required, provide arguments. For the list of supported packages and arguments (for servers running Window and Linux), see
Supported Windows and Linux Packages
and
. Select Generate Trusted Key and select Allow reboot .
NOTE: Install Server Administrator prerequisites before deploying Server Administrator on Linux.
3.
On Task Target , do one of the following:
• Select a query from the drop-down list or create a new query by clicking the New button.
297
• Select servers on which you want to run this task and click Next .
4.
On Schedule and Credentials , set the schedule parameters, provide user credentials to enable the task.
5.
If you want to deploy Server Administrator as a sudo user, select Enable Sudo and update the SSH port number.
NOTE: Before you deploy OMSA using sudo, create a new user account, edit the sudoers file using the visudo command, and add the following:
• For target systems running a 32-bit operating systems: Cmnd_Alias OMEUPDATE = /bin/tar,/bin/ cat,/opt/dell/srvadmin/bin/omexec,/tmp/LinuxPreInstallPackage/runbada,/tmp/
LinuxPreInstallPackage/omexec <sudo_username> ALL=OMEUPDATE, NOPASSWD:OMEUPDATE .
• For target systems running a 64-bit operating systems: Cmnd_Alias OMEUPDATE = /bin/tar,/bin/ cat,/opt/dell/srvadmin/bin/omexec,/tmp/LinuxPreInstallPackage64/runbada,/tmp/
LinuxPreInstallPackage64/omexec <sudo_username> ALL=OMEUPDATE, NOPASSWD:OMEUPDATE .
NOTE: If OMSA is uninstalled from a system by a root user, before deploying OMSA on that system using sudo, make sure that all OMSA pre-installation package files are removed from the tmp folder.
NOTE: Deploying OMSA using sudo is not supported for SUSE Linux Enterprise Server and ESX targets.
6.
Click Finish .
For information about the fields in the Create a Deployment Task wizard, see
Related links
Supported Windows and Linux Packages
Windows Packages
Table 230. Windows Packages
Package Type Clean installation
.msi
.msp
.exe
Supported
Not supported
Not supported
Major Version Upgrade (5.x to 6.x to 7.x to 8.x)
Supported
Not supported
Supported
Minor Version Upgrade (8.x to 8.y)
Supported
Supported
Supported
NOTE: OMSA deployment using the .exe package is supported only with Dell
Update Packages
(DUPs).
Linux Packages
Table 231. Linux Packages
Operating System
SUSE Linux Enterprise Server
10
SUSE Linux Enterprise Server
11
Package
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.x86_64_A01.6.tar.gz
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.x86_64_A01.6.tar.gz.sign
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.i386_A01.14.tar.gz
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.i386_A01.14.tar.gz.sign
298
Operating System
VMware ESX 4
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
Package
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.i386_A01.tar.gz
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.i386_A01.tar.gz.sign
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.x86_64_A01.4.tar.gz
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.x86_64_A01.4.tar.gz.sign
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL6.x86_64_A01.5.tar.gz
OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL6.x86_64_A01.5.tar.gz.sign
Arguments
Clean Installation
Table 232. Clean Installation
Component Installation
Server Administrator Web Server only
Linux Attribute
-w
Server Administrator Instrumentation only -d
Server Administrator Web Server and
Server Instrumentation
-w –d
Windows Attribute
ADDLOCAL=IWS
ADDLOCAL=SA
ADDLOCAL=ALL
.
Upgrade
• REINSTALL=ALL REINSTALLMODE=VOMUS — This is a required argument for Server Administrator minor version upgrade using .msi packages.
• /qn — This is an optional argument that is used for silent and unattended installation.
Deploying iDRAC Service Module
NOTE: The iDRAC Service Module can be deployed only on servers that meet the following criteria:
• PowerEdge 12th generation or later servers running a 64-bit Windows or Linux operating system
• iDRAC firmware version 1.51.51 or later
• The server and iDRAC must be discovered in OpenManage Essentials
The deploy iDRAC Service Module task requires the following on the target servers:
• Windows Management Instrumentation service must be running.
• The default Temp folder (C:\Users\<username>\AppData\Local\Temp) must be available. Ensure that the Temp folder is not deleted or moved.
You can create tasks to deploy the iDRAC Service Module on servers running Windows or Linux operating systems. You can also plan a date and time to schedule the iDRAC Service Module deployment task.
To create an iDRAC Service Module deployment task:
1.
Click Manage → Remote Tasks → Common Tasks → Create Deployment Task.
2.
On General , select iDRAC Service Module and provide a task name. If you want to deploy the iDRAC Service Module on
Windows-based servers, then select Windows , provide installer path and, if required, provide arguments. If you want to deploy the iDRAC Service Module on Linux-based servers, select Linux and provide the installer path, select Generate Trusted Key and Allow reboot . If you are using a .rpm package to deploy the iDRAC Service Module, select Upload and Install GPG key .
NOTE: Install the iDRAC Service Module prerequisites before deploying the iDRAC Service Module on Linux.
3.
On Task Target, do one of the following:
299
• Select a query from the drop-down list or create a new query by clicking the New button.
• Select servers on which you want to run this task and click Next .
NOTE: Devices that are not applicable for the iDRAC Service Module deployment are not available for selection in the Task Target. Moving the mouse pointer over such a device in the Task Target displays a tool tip that indicates why the iDRAC Service Module cannot be deployed. If you want to override the device capability and allow all the available devices for selection as task targets, select Enable all.
4.
On Schedule and Credentials , set the schedule parameters, provide user credentials to enable the task.
5.
If you want to deploy the iDRAC Service Module as a sudo user, select Enable Sudo and update the SSH port number.
NOTE: Before you deploy the iDRAC Service Module using sudo, create a new user account, edit the sudoers file using the visudo command, and add the following:
Cmnd_Alias OMEUPDATE = /bin/tar,/bin/cat,/bin/rpm,/opt/dell/srvadmin/bin/ omexec,/tmp/LinuxPreInstallPackage64/runbada,/tmp/LinuxPreInstallPackage64/omexec
<sudo_username> ALL=OMEUPDATE, NOPASSWD:OMEUPDATE
NOTE: If the iDRAC Service Module is uninstalled from a system by a root user, before deploying the iDRAC Service
Module on that system using sudo, make sure that all the iDRAC Service Module pre-installation package files are removed from the tmp folder.
NOTE: Deploying the iDRAC Service Module using sudo is not supported on SUSE Linux Enterprise Server and ESX targets.
6.
Click Finish .
For information about the fields in the Create a Deployment Task wizard, see
Related links
Supported Windows and Linux Packages
Windows Packages
Table 233. Windows Packages
Package Type
.msi
NOTE: The .msi package is applicable only for deploying iDRAC
Service Module version 2.0 or later.
Clean installation
Supported
Major Version Upgrade (1.x to 2.x)
Supported
.exe
NOTE: iDRAC Service Module deployment using the .exe package is supported only with Dell Update
Packages (DUPs).
Not supported Supported
Linux Packages
Table 234. Linux Packages
Operating System
• Red Hat Enterprise Linux 5
• Red Hat Enterprise Linux 6
• Red Hat Enterprise Linux 7
• SUSE Linux Enterprise Server 11
• Community Enterprise Operating
System (CentOS) 5.9
Package
OM-iSM-Dell-Web-LX-100-429.tar.gz
OM-iSM-Dell-Web-LX-100-429.tar.gz.sign
Systems-Management_Application_NH7WW_LN64_1.0.0_A01
Systems-Management_Application_NH7WW_LN64_1.0.0_A01.BIN
300
Operating System
• CentOS 6.5
SUSE Linux Enterprise Server 11
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
Package dcism-1.0.0-4.435.1.sles11.x86_64.rpm
dcism-1.0.0-4.435.1.el5.x86_64.rpm
dcism-1.0.0-4.435.1.el6.x86_64.rpm
Collecting Firmware and Driver Inventory
The Create F/W & Driver Inventory Task allows you to collect firmware and driver inventory information from a server. The collected inventory information serves as a baseline that is used by OpenManage Essentials to identify and apply updates on the server. This task allows you to collect firmware and driver inventory information that is otherwise not be available to OpenManage
Essentials in the following scenarios:
• Servers discovered using WMI or SSH protocol that do not have OpenManage Server Administrator (OMSA) installed.
• PowerEdge servers or OEM servers that do not have OMSA installed.
• Servers running Linux that have OMSA installed, but the inventory collector component is uninstalled.
After the inventory information is collected, you can update the firmware, BIOS, or drivers of the server through the System Update portal.
NOTE: The Create F/W & Driver Inventory Task utilizes the inventory collector component to collect firmware and driver inventory from target servers. The inventory collector component is deployed on each target server for collecting the inventory information. After the task is completed, the inventory collector component is automatically removed.
To collect firmware and driver inventory:
1.
Perform one of the following:
• Click Manage → Remote Tasks → Create F/W & Driver Inventory Task .
• If the server was discovered using WMI/SSH protocol and OMSA is not installed, click Manage → System Update → Non-
Inventoried Systems .
1.
Select the systems you want to inventory and click Inventory .
2.
In the Systems to Inventory window, click Run Inventory .
The Create a Firmware & Driver Inventory Task window is displayed.
2.
On General , provide a name for the task.
3.
If you want to filter the devices to be displayed in the Task Target based on the operating system, select Filter devices based on Operating System .
a. Select Windows or Linux .
b. If applicable, select 64-bit System .
NOTE: By default, target devices that have OMSA installed are not displayed on the Task Targets tab.
c. Select Show OMSA based targets to also view target devices that have OMSA installed in the Task Target tab.
d. If you selected Show OMSA based targets , perform one of the following in the Future Software Inventory Data Collected by section:
NOTE: The Future Software Inventory Data Collected by options only determine the method OpenManage
Essentials utilizes to gather firmware and driver inventory information from target devices after an in-band system update. If the F/W and Driver task based inventory option is selected, scheduled discovery and inventory cycles will still gather the OMSA-based inventory from target devices, except the information in the Software
Inventory table.
• OMSA based inventory — Select to revert to gathering firmware and driver inventory information through OMSA on target devices that have OMSA installed.
301
NOTE: To revert to gathering firmware and driver inventory information through OMSA, you must either run the firmware and driver inventory task or delete and rediscover the device.
• F/W and Driver task based inventory — Select to gather firmware and driver inventory information through the inventory collector component, even though OMSA may be installed on the device.
4.
On Task Target , do one of the following:
• Select a query from the drop-down list or click New to create a new query.
• Select servers on which you want to run this task and click Next .
5.
On Schedule and Credentials , set the schedule parameters, provide user credentials to enable the task.
6.
Click Finish .
The status of the inventory collection is displayed in the Task Execution History of the Remote Tasks portal.
Related links
Firmware and Driver Inventory Collection Task
Updating the inventory collector component
The Create F/W & Driver Inventory Task utilizes the inventory collector component to collect software inventory information from
Dell servers. Occasionally, a newer version of the inventory collector component may be available. You can verify if OpenManage
Essentials has the latest version of the inventory collector component through the Dell Solutions portal. If a newer version of the inventory collector component is available, the Update link is displayed on the Dell Solutions portal.
To update the inventory collector component:
1.
Click Dell Solutions .
The Dell Solutions portal is displayed.
2.
Click the Update link displayed in the Inventory collector component row.
3.
At the confirmation prompt, click Yes .
The inventory collector component is downloaded in the background. You can view the status of the update in the Task Status grid on the Home portal.
Working With Sample Remote Tasks Use Cases
Sample remote tasks are available for Server Power Options, Deploy Server Administrator, and Command Line. Sample remote tasks use cases are disabled by default. To enable a sample use case:
1.
Right-click the use case and select Clone .
2.
Enter the Cloned Task Name and click Ok .
3.
Right-click the cloned task and select Edit .
4.
Enter the required information and assign targets to the tasks. For information about the options, see
Related links
302
Use Cases in Remote Tasks
Server Power Options
Sample-Power On Device —Enable this use case to turn on the server. The system must have RAC/DRAC configured.
Deploy Server Administrator
Sample-OMSA Upgrade Windows —Enable this use case to upgrade OpenManage Server Administrator on a Windows-based system.
Command Line
• Sample - Windows OMSA Uninstall — Enable this use case to uninstall OMSA on a system running the Windows Server operating system.
• Sample - Linux OMSA Uninstall — Enable this use case to uninstall OMSA on a system running the Linux operating system.
• Sample - Server XML Configuration — Enable this use case to apply a specific server configuration to multiple managed nodes. For more information, see
Using the Sample - Server XML Configuration Command Line Task
.
• Sample-Generic Command Remote — Enable this use case to use tokens to receive the IP address or name of inventories systems.
NOTE: To use this command, you must enter the local system credentials.
• Sample - Generic Command Local — Enable this use case to run a command or script on system with OpenManage Essentials.
NOTE: To use this command, you must enter the local system credentials.
• Sample - IPMI Command — Enable this use case to receive information about the power status of a server.
• Sample - Remote Command — Enable this use case to view the system summary through Server Administrator.
• Sample - RACADM - Clear SEL Log — Enable this use case to clear the SEL log of RAC.
• Sample - RACADM-Reset — Enable this use case to reset the RAC.
• Sample - RACADM-Lockdown Disable — Enable this use case to disable lockdown mode of iDRAC9 servers.
• Sample - Disable Inventory Collector — Enable this use case to disable the inventory collector on target OMSA servers.
• Sample - Enable Inventory Collector — Enable this use case to enable the inventory collector on target OMSA servers.
Firmware and Driver Inventory Task
Scheduled S/W Inventory Task — Enable this use case to collect firmware and driver inventory from a server.
Using the Sample - Server XML Configuration Command Line Task
The following are the prerequisites for using the Sample - Server XML Configuration command line task:
• Lifecycle Controller 2 version 1.2 or later
• RACADM version 7.2 or later
• Firmware version 1.30.30 or later
• Express or Enterprise license
• iDRAC7
The Sample - Server XML Configuration command line task allows you to apply a specific server configuration to multiple managed nodes. Using Lifecycle Controller 2 version 1.2 or later, a server configuration summary can be exported from an iDRAC in XML format through the “Export Server Configuration” operation.
NOTE: For information on exporting the server configuration summary using Lifecycle Controller 2, see the
Configuration
XML Workflows
white paper at DellTechCenter.com/LC.
The server configuration summary XML file can be applied to another iDRAC using the Sample - Server XML Configuration command line task.
NOTE: To apply the server configuration summary from one iDRAC to another iDRAC, both the iDRACs must be of the same generation, same license state, and so on. For more information on the requirements, see the
Lifecycle Controller
(LC) XML Schema Guide
,
Server Configuration XML File
, and
Configuration XML Workflows
white papers at
DellTechCenter.com/LC.
303
To use the Sample - Server XML Configuration command line task:
1.
In the OpenManage Essentials Remote Tasks portal, right-click the Sample - Server XML Configuration , and click Clone .
The Input information for the newly cloned task dialog box is displayed.
2.
Provide the Cloned Task Name and click OK .
3.
Right-click the created cloned task and click Edit .
The Create a Command Line Task dialog box is displayed.
4.
Edit the Command field, and provide the location of the server configuration summary xml file in the OpenManage Essentials management station. For example, set –f c:\user1\server1.xml-t xml , where c:\user1\server1.xml
is the location of the server configuration summary xml file.
5.
In the Targets tab, select the appropriate targets for applying the server configuration.
6.
In the Schedule and Credentials tab, select to run or schedule the task, and provide the required credentials.
7.
Click Finish .
Device Capability Matrix
The following device capability matrix provides information about the type of remote tasks supported on devices that are displayed in the Task Target tab.
Table 235. Type Of Remote Tasks Supported On Devices That Are Displayed In The Task Target Tab
Remote Task Type
All Servers (except
ESXi) With Server
Administrator and
Discovered Using
SNMP/WMI
Windows-based
Servers without
Server
Administrator and discovered using
WMI
Linux-based
Servers without
Server
Administrator and discovered using
SSH
DRAC/iDRAC is not discovered
DRAC/iDRAC discovered using
IPMI
DRAC/iDRAC discovered using
SNMP/WS-Man
Reboot/power cycle operation
Supported Supported Not supported
Server operating system is not discovered
Not supported Not supported
Power off operation Supported
Power on operation Not supported
Remote Server
Administrator command task
Supported
IPMI command task Not supported
RACADM command line task
Not supported
Create F/W &
Driver Inventory task
Not supported
Supported
Not supported
Not supported
Not supported
Not supported
Supported
Not supported
Not supported
Not supported
Not supported
Not supported
Supported
Not supported
Supported
Not supported
Not supported
Not supported
Not supported
Not supported
Not supported
Not supported
Not supported
Supported
Not supported
The following table lists the device discovery requirements for the iDRAC Service Module deployment task. To deploy the iDRAC
Service Module, the server and the iDRAC must discovered using the appropriate protocols specified. For example, to deploy the iDRAC Service Module on a Windows-based server running Server Administrator that is discovered using SNMP/WMI, the iDRAC must be discovered using SNMP/WS-Man.
304
Table 236. Discovery Requirements for the iDRAC Service Module
Server/in-band discovery
Remote Task Type
All Windows-based
Servers With
Server
Administrator and
Discovered Using
SNMP/WMI
All Windows-based
Servers With
Server
Administrator and
Discovered Using
WMI
Linux-based
Servers With
Server
Administrator and discovered using
SNMP/SSH
N/A N/A iDRAC Service
Module deployment task
N/A N/A
Linux-based
Servers With
Server
Administrator and discovered using
SSH
N/A
N/A iDRAC/out-ofband discovery
DRAC/iDRAC discovered using
SNMP/WS-Man
N/A N/A
N/A
N/A
N/A N/A
Device capabilities for a server or DRAC/iDRAC device are populated during discovery and is leveraged by remote tasks to determine applicable targets for each task type. The capability is populated based on the following parameters:
• Protocol used to discover the server and DRAC/iDRAC. For example, IPMI, SNMP, and so on.
• If Server Administrator is installed on the server.
• Settings enabled on the DRAC/iDRAC.
Selecting the Enable All check box allows you to override device capability and allows all the available devices for selection as task targets.
The following device capability matrix provides information about the type of remote tasks supported on devices when the device capabilities are overridden.
Table 237. Type Of Remote Tasks Supported On Devices When The Device Capabilities Are Overridden
Remote Task Type
All Servers (except
ESXi) With Server
Administrator and
Discovered Using
SNMP/WMI
Windows-based
Servers without
Server
Administrator and discovered using
WMI
Linux-based
Servers without
Server
Administrator and discovered using
SSH
DRAC/iDRAC is not discovered
DRAC/iDRAC discovered using
IPMI
DRAC/iDRAC discovered using
SNMP/ WS-Man
Supported Not supported
Server operating system is not discovered
Not supported Not supported Reboot/power cycle operation
Supported
Power off operation Supported Supported Not supported Not supported
Power on operation Supported if:
Remote Server
Administrator command task
DRAC/iDRAC information is retrieved and displayed in the inventory page.
IPMI over LAN is enabled on the
DRAC/iDRAC device.
You select Enable
All in the Tasks
Target tab.
Not supported
Not supported
Not supported
Not supported
Supported
Not supported
Not supported
Supported if:
IPMI over LAN is enabled on the
DRAC/iDRAC device.
You select Enable
All in the Tasks
Target tab.
305
Remote Task Type
All Servers (except
ESXi) With Server
Administrator and
Discovered Using
SNMP/WMI
Windows-based
Servers without
Server
Administrator and discovered using
WMI
DRAC/iDRAC is not discovered
Linux-based
Servers without
Server
Administrator and discovered using
SSH
Not supported
Not supported
Not supported
Not supported
DRAC/iDRAC discovered using
IPMI
DRAC/iDRAC discovered using
SNMP/ WS-Man
Server operating system is not discovered
Not supported Not supported
Not supported Supported
IPMI command task Not supported
RACADM command line task
Supported if:
DRAC/iDRAC information is retrieved and displayed in the inventory page.
You select Enable
All in the Tasks
Target tab.
NOTE: In the Task Targets tab, if the Enable All option is selected, the iDRAC Service Module deployment is enabled for all discovered servers or unknown devices.
Related links
Managing RACADM Command Line Tasks
Deploying Server Administrator
Collecting Firmware and Driver Inventory
Working With Sample Remote Tasks Use Cases
Using the Sample - Server XML Configuration Command Line Task
Deploying iDRAC Service Module
306
advertisement