Server Administrator Version 7.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2013 Dell Inc. All Rights Reserved.
Contents 1 Introduction..................................................................................................................................9 What Is New In This Release................................................................................................................................... 9 Software Availability.......................................................................................................................................... 9 Systems Management Software.......
Upgrading Guidelines.......................................................................................................................................39 Upgrade............................................................................................................................................................40 Modify...............................................................................................................................................................40 Repair..............
Configuring The System To Send Traps To A Management Station Using The vSphere CLI.......................... 66 Troubleshooting......................................................................................................................................................66 7 Installing Systems Management Software On Citrix XenServer ..................................... 69 During The installation Of XenServer.............................................................................................
I have installed Server Administrator and Online Diagnostics in the same directory and Online Diagnostics fails to work, what do I do?.......................................................................................................... 87 I have installed Server Administrator using remote Server Administrator deploy on Windows Server 2008, I do not see Server Administrator icon on the desktop?.........................................................................
What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems after Server Administrator is started?..............................................................................................................97 What kernel modules are loaded when Server Administrator is started?.......................................................98 10 Linux Installer Packages........................................................................................................
Introduction 1 This topic provides information on: • Installing Server Administrator on managed systems. • Installing and using the Remote Enablement feature. • Managing remote systems using Server Administrator Web Server. • Configuring the system before and during a deployment or upgrade. NOTE: If you are installing management station and managed system software on the same system, install identical software versions to avoid system conflicts.
Systems management software comprises of two DVDs: • • Systems Management Tools and Documentation Server Update Utility NOTE: For more information on these DVDs, see Management Station Software Installation Guide. Server Administrator Components On A Managed System The setup program provides the following options: • Custom Setup • Typical Setup The custom setup option enables you to select the software components you want to install.
Component What is installed Deployment Scenario Systems to install on User’s Guide in the docs directory. Command Line Interface (Management Interface) Command Line Interface of Server Instrumentation Install to provide local and remote system management solutions to manage Server and Storage instrumentation data using command line interfaces. Supported systems. For a list of supported systems, see the Systems Software Support Matrix.
Component What is installed Deployment Scenario Systems to install on diagnose the probable cause of a system crash. Intel SNMP Agent (NIC Interfaces) Intel Simple Network Management Protocol (SNMP) Agent Install to enable Server Administrator to obtain information about Network Interface Cards (NICs). Only on systems on which Server Instrumentation is installed and which are running on Windows operating system.
• The Systems Build and Update Utility User’s Guide provides information on using the Systems Build and Update Utility. • The Systems Software Support Matrix provides information about the various systems, the operating systems supported by these systems, and the systems management components that can be installed on these systems. • The Server Administrator User's Guide describes the installation and use of Server Administrator.
2 Preinstallation Setup Ensure that you perform the following before installing Server Administrator: • Read the installation instructions for the operating system. • Read the Installation Requirements to ensure that the system meets or exceeds the minimum requirements. • Read the applicable readme files and the Systems Software Support Matrix. • Close all applications running on the system before installing the Server Administrator applications.
Return Code Description 2 A warning condition, or conditions, is associated with the software. It is recommended that you resolve the conditions causing the warning before proceeding with the installation of the software. To continue, select and install the software using the custom installation. 3 An error condition, or conditions, is associated with the software. Resolve the conditions causing the error before proceeding with the installation of the software.
• Do not install managed system and management station RAC components on the same system. Install only the managed system RAC components, as they offer the required functionality. Common causes for a return code of 3 (failure) from the prerequisite checker: • You are not logged in with built-in Administrator privileges. • The MSI package is corrupt or one of the required XML files is corrupt. • Error during copying from a DVD or network access problems while copying from a network share.
NOTE: To manage the server, select either Server Administrator Webserver or one of the Management Interfaces – CLI, WMI, SNMP or OSLOG along with Server Instrumentation (SI) or Server Administrator Storage Management Service (OMSS). Installation Requirements This section describes the general requirements of the Server Administrator and provides information on supported operating systems and web browsers. NOTE: Prerequisites specific to an operating system are listed as part of the installation procedures.
• Administrator rights. • TCP/IP connection on the managed system and the remote system to facilitate remote system management. • One of the Supported Systems Management Protocol Standards. • Monitor with a minimum screen resolution of 800 x 600. The recommended screen resolution is at least 1024 x 768. • The Server Administrator Remote Access Controller service requires remote access controller (RAC) installed on the managed system.
Digital Certificates All Server Administrator packages for Microsoft are digitally signed with a certificate that helps guarantee the integrity of the installation packages. If these packages are repackaged, edited, or manipulated in other ways, the digital signature is invalidated. This manipulation results in an unsupported installation package and the prerequisite checker does not allow you to install the software.
Remote Access Controller (iDRAC), Chassis Management Controller (CMC), and Remote Access Controllers (RAC), can interface with Active Directory. Using Active Directory, add and control users and privileges from a central database. Related Links: Using Microsoft Active Directory Configuring SNMP Agents The systems management software supports the SNMP systems management standard on all supported operating systems.
NOTE: Log in with administrator privileges to set or reset user or server preferences. 1. Click Preferences on the global navigation bar. 2. Click General Settings, and the Web Server tab. 3. Set options as necessary in the Server Preferences window: Session Timeout Sets the time limit for a session to remain active. Select Enable to set a time-out if there is no user interaction for a specified time in minutes. After a session time-out, the user must log in again to continue.
Key Signing Algorithm (For Self Signed Certificate) Displays the supported signing algorithms. Select an algorithm from the drop-down list. NOTE: If you select either SHA 512 or SHA 256, ensure that your operating system/ browser supports this algorithm. If you select one of these options without the requisite operating system/browser support, Server Administrator displays a cannot display the webpageerror. NOTE: This field is available only for Server Administrator auto-generated self-signed certificates.
• Authorization for WinRM and Windows Management Instrumentation (WMI) Servers Installing WinRM On Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows 7, Windows 8 and Windows Server 2012, WinRM 2.0 is installed by default. On Windows Server 2008, WinRM 1.1 is installed by default.
WinRM To configure user authorization for WinRM servers: 1. Click Start → Run. 2. Type winrm configsddl and click OK. If you are using WinRM 2.0, type winrm configsddl default. 3. Click Add and add the required users or groups (local/domain) to the list. 4. Provide the appropriate permission(s) to the respective users and click OK. WMI To configure user authorization for WMI servers: 1. Click Start → Run. 2. Type wmimgmt.msc, and then click OK.
Dependent RPMs For Remote Enablement If you choose to install the Remote Enablement feature, you have to install certain dependent RPMs and configure these RPMs before installing the feature. Install the following RPMs: • libcmpiCppImpl0 • libwsman1 • openwsman-server • sblim-sfcb • sblim-sfcc The dependent RPMs are available on the Systems Management Tools and Documentation DVD at srvadmin\linux \RPMS\supportRPMS\opensource-components\\.
– individually NOTE: If you are installing RPMs individually, follow this sequence. rpm -ivh sblim-sfcb-x.x.x.rpm rpm -ivh sblim-sfcc-x.x.x.rpm NOTE: Install the libwsman and openwsman client RPMs simultaneously as they have cyclic dependency. rpm -ivh libwsman1-x.x.x.rpm openwsman-client-x.x.x.rpm rpm -ivh openwsman-server-x.x.x.rpm Post-Installation Configuration For Remote Enablement This section details the steps to configure the dependent RPMs if you have installed the Remote Enablement feature.
Running sfcb And openwsman Run sfcb and openwsman: • /etc/init.d/sfcb start • /etc/init.d/openwsmand start NOTE: On Red Hat Enterprise Linux 6, replace sfcb with sblim-sfcb. On Red Hat Enterprise Linux 6, for the sblim-sfcb and openwsman to start automatically after a reboot you need to change the run-levels using the chkconfig utility.
session required /lib/security/$ISA/pam_unix.so session optional /lib/security/$ISA/pam_krb5.so Winbind Configuration For openwsman And sfcb For SUSE Linux Enterprise Server Operating System Follow the instructions mentioned below to configure openwsman and sfcb on 32-bit OMI installation. In case of a 64-bit installation, replace .lib with .lib64. 1. 2. Back up the following files: – /etc/pam.d/openwsman – /etc/pam.d/sfcb – /etc/pam.d/system-auth – /etc/pam.
Installing Managed System Software On Microsoft Windows Operating Systems 3 On Microsoft Windows, an autorun utility is displayed when you insert the Systems Management Tools and Documentation DVD. This utility allows you to choose the systems management software you want to install on the system. If the autorun program does not start automatically, use the autorun program from the DVD root or the setup program in the SYSMGMT\srvadmin\windows directory on the Systems Management Tools and Documentation DVD
You want to Select For systems running on Microsoft Windows, Remote Enablement is under the Server Instrumentation option. You must then install the Server Administrator Web Server on the remote system. View the status of local and remote storage attached to a managed system and obtain storage management information in an integrated graphical view. Storage Management. Remotely access an inoperable system, receive alert notifications when a system is down, and remotely restart a system.
The Systems Management installer features a Typical Setup option and a Custom Setup option for installing Server Administrator and other managed system software.
6. Click Next. The Software License Agreement is displayed. 7. Click I accept the terms in the license agreement and Next if you is displayed. The Setup Type dialog box is displayed. 8. Select Custom and click Next. If you are installing Server Administrator on a unsupported system, the installer displays only the Server Administrator Web Server option. A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X depicted next to it.
3. Reinstall Server Administrator. Option 2: After installing Citrix, type the command msiexec.exe /fa SysMgmt.msi Performing An Unattended Installation Of Managed System Software The Systems Management installer features a Typical Setup option and a Custom Setup option for the unattended installation procedure. Unattended installation enables you to simultaneously install Server Administrator on multiple systems.
Creating Custom Unattended Installation Packages To create a custom unattended installation package, perform the following steps: 1. Copy the SYSMGMT\srvadmin\windows directory from the DVD to the system hard drive. 2. Create a batch script that executes the installation using the Windows Installer Engine (msiexec.exe). NOTE: For Customized Unattended Installation, each required feature must be included as a command line interface (CLI) parameter for it to be installed. An example is msiexec.
Setting Result /i .msi – Installs the Server Administrator software. /i .msi /qn This command carries out a fresh installation. /x This command uninstalls a product. /x .msi – Uninstalls the Server Administrator software. /q[n|b|r|f] This command sets the user interface (UI) level. /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI.
selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package. For example, you can choose to install Server Administrator, but not Remote Access Controller service on a specific group of servers, and choose to install Server Administrator, but not Storage Management Service, on another group of servers. You can also choose to uninstall one or multiple features on a specific group of servers.
When the MSI engine is going through the installation sequence, it ignores all actions that are scheduled as rollback actions. If a Custom Action, MSI Standard Action, or a installation action fails, then a rollback starts. You cannot roll back an installation once it is completed; transacted installation is only intended as a safety net that protects the system during an installation session. If you want to remove an installed application, you should uninstall that application.
• If you have installed Server Administrator Web Server version 7.3, ensure that you install Server Instrumentation version 7.3 on the managed system. Accessing an earlier version of Server Administrator using Server Administrator Web Server version 7.3 may display an error. Upgrade For an unattended upgrade, the msiexec.exe /i SysMgmt.msi /qb command accesses the DVD to accept the software license agreement and upgrades all the required Server Administrator features on selected remote systems.
8. Click Install to install the selected software features. The Installing Server Administrator screen is displayed. Messages give the status and progress of the software features being installed. When the selected features are installed, the Install Wizard Completed dialog box is displayed. 9. Click Finish to exit the Server Administrator installation.
Uninstalling Managed System Software Using The Provided Media Perform the following tasks to uninstall managed system software using the provided media. 1. Insert the Systems Management Tools and Documentation DVD into the system's DVD drive. If the setup program does not start automatically, run the setup.exe in the SYSMGMT\srvadmin\windows directory on the DVD. The Server Administrator prerequisite status screen is displayed and runs the prerequisite checks for the managed system.
Unattended Uninstall Using The Product GUID If you do not have the installation DVD or the MSI package available during an uninstallation, use the package GUIDs in the command line to uninstall systems management software on managed systems or management stations running Windows operating system. For managed systems, use: • 32–bit msiexec.exe /x {BF2E05A3-9F39-48A0-B12E-B680949C84BD} • 64–bit msiexec.
Installing Managed System Software On Supported Linux And VMware ESX 4 The Systems Management installer supports both 32-bit and 64-bit architecture. The following table explains the operating system installation matrix for Systems Management. Table 9. Operating System Installation Matrix Operating System Architecture 32-bit Architecture 64-bit Architecture Red Hat Enterprise Linux 6.3 64-bit Not Supported Install Red Hat Enterprise Linux 5.
The install script srvadmin-install.sh allows silent or interactive installation. By including the srvadmin-install.sh script in the Linux scripts, install Server Administrator locally or across a network on single or multiple systems. The second install method uses the Server Administrator RPM packages provided in the custom directories and the Linux rpm command. Write Linux scripts that install Server Administrator locally or across a network on single or multiple systems.
Prerequisite RPM Service Names Command Line Options for srvadmininstall.
Prerequisite RPM OS Logging Option PE Server, OS srvadmin-xmlsup dsm_sa_datamgrd srvadmin-hapi dsm_sa_eventmgrd srvadmin-omilcore dsm_sa_shrsvcd srvadmin-deng srvadmin-isvc srvadmin-omcommon srvadmin-oslog srvadmin-cm (applicable for x32 bit only) srvadmin-omacs srvadmin-ominst srvadmin-raccomponents -l or --oslog Remote Enablement PE Server, OS, CIMOM, WSMAN CIMOM version >= SFCB 1.3.2 (applicable for systems running VMware ESX 4.0, Red Hat Enterprise Linux, and SUSE Linux) >= Open Pegasus 2.5.
Prerequisite RPM Service Names Command Line Options for srvadmininstall.
Prerequisite RPM Service Names Command Line Options for srvadmininstall.
whenever you run either the srvadmin-services.sh start or srvadmin‑services.sh restart commands, or when you restart the system (during which the Server Administrator Instrumentation Service is started.) Server Administrator installation blocks the installation of Server Administrator packages if an appropriate version of the OpenIPMI device driver is not currently installed on the system.
Installing The wsman And sblim Packages 1. In Package selection, select Basic Server. 2. Select Customize now and click Next. 3. Select System Management group. 4. From the sub-category, select Web-based Enterprise Management → Optional Packages option. The default selected packages are: openwsman-client, sblim-sfcb, sblim-wbemcli, and wsmancli Deselect the sblim-wbemcli package from the above list. 5. Select openwsman-server and click Next. 6.
– Storage Management – Remote Access Controller Remote enablement is not installed and Server Administrator services do not start automatically. NOTE: The 32-bit srvadmin-cm RPM is not installed when systems management software is installed on a 64bit operating system. If required, install the srvadmin-cm package from the appropriate subfolders under SYSMGMT/srvadmin/linux/RPMS/supportRPMS/srvadmin from the Systems Management Tools and Documentation DVD.
Table 12. Meta RPMs Meta RPMs Details srvadmin-all Installs all the components. srvadmin-base Installs the Server Instrumentation component. This component has to be installed before installing any of the other specific components. srvadmin-idrac Installs the iDRAC component. srvadmin-rac4 Installs the DRAC 4 component. srvadmin-rac5 Installs the DRAC 5 component. srvadmin-standardAgent Installs the Remote Enablement component.
NOTE: You can install Server Administrator on any system that meets operating system dependencies. However, after installation, certain Server Administrator services may not be started on unsupported systems. NOTE: When Server Administrator is installed on a system, dependency issues related to RPMs may occur. To resolve these issues, install the missing RPMs from SYSMGMT/srvadmin/linux/RPMS/supportRPMS/ opensourcecomponents.
The following options can be used along with options stated above: • [-a|--autostart] — Starts the installed services after components have been installed. • [-p|--preserve] — Preserves the screen without clearing the installation information. NOTE: If you do not use the [-p | --preserve] option during the installation, the history information on the screen gets erased. * — Options included for Linux granular installation.
The system displays a message identifying the architecture where, i386 refers to 32-bit and x86_64 refers to 64-bit. Managed System Software Installation Using Third Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, VMWare Update Manager (VUM), or Linux Respository for Yellowdog Updater Modified (YUM), Rug, and Zypper, to install managed systems software on supported systems.
The following command line will work for Red Hat Enterprise Linux 5 and 6, CentOS, and Scientific Linux: yum install srvadmin-all After the installation, type the following command to start the Server Administrator services: srvadmin-services start NOTE: You can install YUM as an add-on for SLES 9 or 10. Using RUG You can install Server Administrator using rug for SLES 10 or higher.
Installing Managed System Software On Microsoft Windows Server 2008 Core And Microsoft Hyper-V Server 5 The Server Core installation option of the Microsoft Windows Server 2008 and Hyper-V Server operating system provides a minimal environment for running specific server roles that reduce the maintenance and management requirements and the attack surface for those server roles.
• 1034.mst (Spanish) • 1036.mst (French) • 1041.mst (Japanese) • 2052.mst (Simplified Chinese) Related Links: Optional Command Line Settings Uninstalling Systems Management Software To uninstall managed system software, type msiexec /x .msi at the command prompt.
Installing Systems Management Software On VMware ESXi 6 VMware ESXi is factory-installed on some systems. For a list of these systems, see the latest Systems Software Support Matrix. Use Server Administrator Web Server version 7.0 to access VMware ESXi 4.0 U3, VMware ESXi 4.1 U2, VMware ESXi 5.0 U1 systems. Server Administrator is available as a .zip file for installing on systems running VMware ESXi. The zip file, OM-SrvAdminDell-Web--.VIB-ESXi_.
• Server Administrator Storage Management • Remote Access Controller Related Links: Troubleshooting Using The VMware vSphere Management Assistant (vMA) The vMA allows administrators and developers to run scripts and agents to manage ESX/ESXi systems. For more information on vMA, see vmware.com/support/developer/vima/. 1. Log on to vMA as an administrator and provide the password when prompted. 2. Copy and unzip the OM-SrvAdmin-Dell-Web--.VIB-ESXi_.
5. Right-click the ESXi host added in the previous step and click Maintenance Mode. 6. From Plug-ins select Manage Plug-ins → download VMware Update Manager (The status is enabled if the download is successful.) Follow the instructions to install the VUM client. 7. Select the ESXi host. Click Update Manager → Admin view → Patch Repository → Import Patches and follow the online instructions to upload the patch successfully. The offline bundle is displayed. 8. Click Baselines and Groups. 9.
Accessing Server Administrator on VMware ESXi To manage Server Administrator on VMware ESXi using the Server Administrator Web Server interface: 1. Install only the Server Administrator Web Server interface on another system. NOTE: Ensure that the version of the Server Administrator Web Server interface is greater or equal to the version of the Server Instrumentation installed. 2. Run the Server Administrator Web Server interface. The Managed System Login screen is displayed. 3.
Enabling CIM OEM Providers Using vSphere CLI (For VMware ESXi 4.0/ESXi 4.1) To enable CIM OEM providers on the VMware ESXi system using vSphere CLI: 1. If you are using vSphere CLI on Windows, navigate to the directory where you have installed the vSphere CLI utilities. On Linux, proceed to step 2. 2. Execute the command vicfg-advcfg.pl --server --username --password --set 1 UserVars.CIMOEMProvidersEnabled NOTE: For ESXi 4.
Configuring The SNMP Agent On Systems Running VMware ESXi Server Administrator generates Simple Network Management Protocol (SNMP) traps in response to changes in the status of sensors and other monitored parameters. You must configure one or more trap destinations on the system running Server Administrator to send SNMP traps to a management station.
This error is displayed if you are using an older version of the Remote CLI. To resolve this issue, download and install the latest vSphere version of the CLI. • When attempting to use the vihostupdate command, the following error may be displayed: Unable to create, write or read a file as expected.I/O Error (28) on file : [Errno 28] No space left on device. See the VMware KB article 1012640 at kb.vmware.com to fix this error.
Installing Systems Management Software On Citrix XenServer 7 The Server Administrator is installed on Citrix XenServer using the Supplemental Pack. The Supplemental Pack for Citrix XenServer can be installed in two ways: • During the installation of XenServer • On a running system During The installation Of XenServer To install the Supplemental Pack for Citrix XenServer during the installation of XenServer: 1. Start the installation of XenServer as usual and follow the instructions on the screen. 2.
OR $ xe-install-supplemental-pack .iso NOTE: If a previous version of Server Administrator is already installed on the system, then the command to upgrade it to version 7.0 is ./install.sh. After the installation or upgrade, execute the following post-installation configuration script of Remote Enablement feature $ cd /opt/dell/srvadmin/etc $ ./autoconf_cim_component.sh -p 5986 3. When the installation is complete, unmount the ISO file or CD: $ cd ..
Accessing Server Administrator on XenServer To manage Server Administrator on XenServer using the Server Administrator Web Server interface: 1. Install only the Server Administrator Web Server interface on another system. NOTE: Ensure that the version of the Server Administrator Web Server interface is greater or equal to the version of the Server Instrumentation installed. 2. Run the Server Administrator Web Server interface. The Managed System Login screen is displayed. 3.
Using Microsoft Active Directory 8 If you use Active Directory service software, configure it to control access to the network. The Active Directory database is modified to support remote management authentication and authorization. Server Administrator, as well as Integrated Remote Access Controllers (iDRAC), Remote Access Controllers (RAC), can now interface with Active Directory. With this tool, you can add and control users and privileges from one central database.
Figure 1. Typical Setup for Active Directory Objects In addition, you can set up Active Directory objects in a single domain or in multiple domains. Setting up objects in a single domain does not vary, whether you are setting up RAC, or Server Administrator objects. When multiple domains are involved, however, there are some differences. The following figure shows the set up of the Active Directory objects in a single domain.
Figure 2. Setting Up RAC Active Directory Objects in a Single Domain Setting Up Objects In A Single Domain To set up the objects in a single domain scenario, perform the following tasks: 1. Create two Association Objects. 2. Create two RAC Product Objects, RAC1 and RAC2, to represent the two DRAC 4 cards. 3. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privileges. 4. Group User1 and User2 into Group1. 5.
Figure 3. Setting Up RAC Active Directory Objects In Multiple Domains Setting Up RAC Active Directory Objects In Multiple Domain To set up the objects for this multiple domain scenario, perform the following tasks: 1. Ensure that the domain forest function is in Native mode. 2. Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain. 3. Create two RAC Device Objects, RAC1 and RAC2, to represent the two remote systems. 4.
Figure 4. Setting up Server Administrator Active Directory Objects In Multiple Domains Setting Up Server Administrator Active Directory Objects For Multiple Domain To set up the objects for this multiple domain scenario, perform the following tasks: 1. Ensure that the domain forest function is in Native mode. 2. Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1. 3. Create two Server Administrator Products, sys1 and sys2, to represent the two systems.
• Adding Users and Privileges to Active Directory • Configuring the Systems or Devices Configuring The Active Directory Product Name To configure the Active Directory product name: 1. Locate the omsaoem.ini file in the installation directory. 2. Edit the file to add the line adproductname=text, where text is the name of the product object that you created in Active Directory. For example, the omsaoem.ini file contains the following syntax if the Active Directory product name is configured to omsaApp.
To use the LDIF files, see the instructions in the readme that is in the LDIF files directory. To use the Schema Extender to extend the Active Directory Schema, perform the steps in Using the Dell Schema Extender. Copy and run the Schema Extender or LDIF files from any location. Using The Dell Schema Extender To use the Dell Schema Extender perform the following tasks: CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file.
Table 16. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description This class is used as a container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User Attributes dellRAC4Privileges dellRAC3Privileges dellOmsaAuxClass Table 17. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description This is the main class from which all Dell products are derived.
Table 20. General Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier dellPrivilegeMember 1.2.840.113556.1.8000.1280.1.1.2.1 FALSE Distinguished Name (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) List of dellPrivilege Objects that belong to this Attribute. dellProductMembers List of dellRacDevices Objects that belong to this role. This attribute is the forward link to the dellAssociationMembers backward link. Link ID: 12070 Single Valued 1.2.
NOTE: Install the Administrator Pack on each management station that is managing the new Active Directory objects. If you do not install the Administrator Pack, you cannot view the new object in the container. NOTE: For more information about the Active Directory Users and Computers snap-in, see the Microsoft documentation.
Creating A Privilege Object Privilege Objects must be created in the same domain as the Association Object to which they are associated. 1. In the Console Root (MMC) window, right-click a container. 2. Select New. 3. Select a RAC or Server Administrator object, depending on what you have installed. The New Object window is displayed. 4. Type in a name for the new object. 5. Select the appropriate Privilege Object. 6. Click OK. 7.
To Add A Privilege 1. Select the Privileges Object tab and click Add. 2. Type the Privilege Object name or browse and click OK. Click the Products tab to add one or more systems or devices to the association. The associated objects specify the products connected to the network that are available for the defined users or user groups. NOTE: Add multiple systems or RAC devices to an Association Object. To Add Products 1. Select the Products tab and click Add. 2.
Frequently Asked Questions 9 What ports do systems management applications use? The default port used by Server Administrator is 1311. These ports are configurable. For port information of a particular component, see the User Guide of that respective component.
What do I do when the creation of WinRM listener fails with the following error message? The CertificateThumbprint property must be empty when the SSL configuration will be shared with another service This error occurs when the Internet Information Server (IIS) is already installed and configured for HTTPS communication. Details about coexistence of IIS and WinRM is available at technet.microsoft.com/en-us/library/ cc782312.aspx.
Do I need to uninstall previous versions of Server Administrator before installing Citrix Metaframe? Yes. Uninstall previous versions of Server Administrator before installing Citrix Metaframe (all versions). As errors may exist in the registry after the Citrix Metaframe installation, you must reinstall Server Administrator. When I run systems management Install, I see unreadable characters on the Prerequisite check information screen.
must be located in the SYSMGMT \srvadmin\windows\SystemsManagement. For more detailed information, go to msdn.microsoft.com and search for MEDIAPACKAGEPATH Property Does systems management Install support Windows Advertised installation? No. Systems management Install does not support Windows Advertised installation - the process of automatically distributing a program to client computers for installation, through the Windows group policies.
b. Look for the VBS file extension and ensure that File Types is set to VBScript Script File. c. If not, click Change and choose Microsoft Windows Based Script Host as the application that gets invoked to run the script. • WSH is the wrong version, corrupted, or not installed. WSH is installed during operating system installation, by default. Download WSH from msdn.microsoft.com. Is the time shown during installation or uninstallation by Windows Installer Services accurate? No.
Feature Name in WIndows Remote Access Controller Console (DRAC 4) Remote Access Controller 4 (DRAC 4) Red Hat Enterprise Linux or SUSE Linux Enterprise Server After installing Server Administrator, I cannot log in. Log out and then log in again to access the Server Administrator Command Line Interface (CLI). I see the following message when I try to install Server Administrator on a guest Linux operating system. ./srvadmin-install.sh: line 2295 : [: ==: unary operator expected.
Where can I find the source packages for Open Source RPMs? Source packages for Open Source RPMs are available on an orderable DVD image. What do I do when management station RAC utility installation fails due to missing RPM file? During the installation of the management station RAC utility (mgmtst-racadm RPM under /SYSMGMT/ ManagementStation/linux/rac directory on the Systems Management Tools and Documentation DVD), the installation may fail due to missing RPM file dependencies on libstdc++.so libraries.
What are the names of all the Systems Management features under Red Hat Enterprise Linux or SUSE Linux Enterprise Server? The following table lists the names of all systems management features and their corresponding init script names under Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems. Table 24.
Name of RPM Description Other Server Administrator RPMs required provides the device drivers and libraries needed by systems management software to access information about the hardware on supported systems. srvadmin-isvc Server Administrator Instrumentation srvadmin-omilcore, srvadmin-deng, Service — Server Administrator and srvadmin-hapi provides a suite of systems management information for keeping supported systems on the network healthy.
Name of RPM Description Other Server Administrator RPMs required srvadmin-idracadm iDRAC Command Interface — The srvadmin-omilcore command line user interface to the Integrated Remote Access Controller. srvadmin-idracdrsc iDRAC Integration Layer — Integrated srvadmin-omilcore, srvadmin-deng, Remote Access CLI and Web Plug-in srvadmin-rac4 components, and to Server Administrator. srvadmin-omacore add-RAC4 — Software for remote management of fourth generation Remote Access Controllers.
Name of RPM Description Other Server Administrator RPMs required libraries needed by systems management software to access information about the hardware on supported systems. srvadmin-tomcat Secure Port Server — Systems Management Managed Node Web Server package. srvadmin-omilcore, srvadmin-deng, srvadmin-omacore, and srvadmin-jre srvadmin-jre Server Administrator Sun Java Runtime Environment — Systems management managed node Java runtime.
Name of RPM Description Other Server Administrator RPMs required healthy. Server Administrator Instrumentation Service provides fault management information, prefailure information, and asset and inventory information to management applications. The Instrumentation Service monitors the health of the system and provides rapid access to detailed fault and performance information about the hardware on supported systems. The Instrumentation Service requires installation of systems management device drivers.
In this case, if you try to install Server Administrator later by running the sh srvadmin-install.sh command, the following message is displayed: Server Administrator version X.Y.Z is currently installed. Installed components are: • srvadmin-omilcore-X.Y.Z-N • srvadmin-hapi-X.Y.Z-N Do you want to upgrade Server Administrator to X.Y.Z? Press (y for yes| to exit): On pressing , only those Server Administrator packages (in the above example), srvadmin-omilcore-X.Y.Z-N and srvadmin-hapi-X.Y.
Daemon Name Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server racsvc DRAC 4 Administrator daemon. What kernel modules are loaded when Server Administrator is started? This is dependent on the type of systems instrumentation. The following table displays the kernel modules loaded when Server Administrator is started. Table 27.
10 Linux Installer Packages This section lists the Linux installer packages. Table 28. Meta RPMs RPM Description Dependent packages srvadmin-base, srvadmin-idrac, srvadmin-rac4, srvadmin-rac5, srvadminstandardAgent, srvadminstorageservices, srvadminwebserver Required for Systems Management Software 6.5 7.0 7.1 7.
RPM Description Dependent packages Required for Systems Management Software 6.5 7.0 7.1 7.
RPM Description Dependent packages Required for Systems Management Software 6.5 7.0 7.1 7.
RPM Description OM Dependant packages Required for srvadmindeng, srvadminomilcore srvadminisvc Provides systems management interface to local and remote systems management libsmbios Provides None SMBIOS library to get standard BIOS tables smbios-utils- Provides bin SMBIOS Utility to get system information None Systems Management Software 6.5 7.0 7.1 7.2 Server Y Instrumentati on and SNMP monitoring Y Y Y Installation Y and software updates Y Y Y Installation Y Y Y Y Table 30.
RPM Description OM Dependant packages Required for Systems Management Software 6.5 7.0 7.1 7.2 on VMware ESX only srvadmin-cm Change srvadminManagement omacore NOTE: inventory On a collector. scripted Feeds install, software srvadmi inventory n-cm is data to installed management on 32bit station operatin applications g systems only. If required on a 64bit operatin g system, manuall y install the same.
Table 31. Server Administrator Web Server (GUI) for Local and Remote Management RPM Description Dependant packages Required for srvadmin-jre Provides JAVA Runtime for web server srvadminomilcore srvadminiws Server Administrato r Web server and GUI package srvadmintomcat Systems Management Software 6.5 7.0 7.1 7.
RPM Description OM Dependant packages Required for Systems Management Software 6.5 7.0 7.1 7.
RPM Description OM Dependant packages Required for Systems Management Software 6.5 7.0 7.1 7.2 y Programmin g Interface (CMPI) C++ plugins into SFCB *N/A on VmWare ESX * — Should be installed from the OS media for RHEL6 and SLES11. Table 33. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description OM Dependant packages srvadminrealssd* Required for Systems Management Software 6.5 7.0 7.1 7.2 Meta None package for * For Red Hat installing Enterprise management Linux 6.
RPM Description OM Dependant packages Required for Systems Management Software 6.5 7.0 7.1 7.2 storelib libraries *N/A for VMware ESX srvadminsysfsutils Provide None utilities for interfacing with sysfs file system. Used by the storage management libraries Storage Y instrumentati on Y Y Y srvadminmegalib LSI utility None libraries for storage management of PERC 4 controllers. *N/A for 64bit OMSA installation, and VMware ESX.
RPM Description OM Dependant packages Required for srvadminstorage queries and SNMP Traps Systems Management Software 6.5 7.0 7.1 7.2 srvadmindeng-snmp Server srvadminAdministrato deng r SNMP Framework Server N Administrato r SNMP Framework N N Y srvadminisvc-snmp Server SNMP module Server and N Operating System related SNMP Queries and SNMP Traps N N Y srvadminhapi, srvadminisvc * — Obsolete - merged with srvadmin-storage ** — Not applicable for OM 7.
RPM Description OM Dependant packages Required for Systems Management Software 6.5 7.0 7.1 7.
RPM Description OM Dependant packages Required for Systems Management Software 6.5 7.0 7.1 7.2 srvadminrac4populator- RAC Data srvadminpopulator for omilcore DRAC 4 DRAC 4 Y instrumentati on Y Y Y srvadminargtable2 Library for None parsing GNU style command line argument.
