Users Guide
Table Of Contents
- Introduction
- Setup And Administration
- Role-Based Access Control
- Authentication
- Encryption
- Assigning User Privileges
- Adding Users To A Domain On Windows Operating Systems
- Creating Server Administrator Users For Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems
- Disabling Guest And Anonymous Accounts In Supported Windows Operating Systems
- Configuring The SNMP Agent
- Configuring The SNMP Agent On Systems Running Supported Windows Operating Systems
- Enabling SNMP Access On Remote Hosts (Windows Server 2003 Only)
- Changing The SNMP Community Name
- Configuring Your System To Send SNMP Traps To A Management Station
- Configuring The SNMP Agent On Systems Running Supported Red Hat Enterprise Linux
- SNMP Agent Access Control Configuration
- Server Administrator SNMP Agent Install Actions
- Changing The SNMP Community Name
- Configuring Your System To Send Traps To A Management Station
- Configuring The SNMP Agent On Systems Running Supported SUSE Linux Enterprise Server
- Sever Administrator SNMP Install Actions
- Enabling SNMP Access From Remote Hosts
- Changing The SNMP Community Name
- Configuring The SNMP Agent On Systems Running Supported VMware ESX 4.X Operating Systems To Proxy VMware MIBs
- Configuring The SNMP Agent On Systems Running Supported VMware ESXi 4.X And ESXi 5.X Operating Systems
- Configuring Your System To Send Traps To A Management Station
- Firewall Configuration On Systems Running Supported Red Hat Enterprise Linux Operating Systems And SUSE Linux Enterprise Server
- Using Server Administrator
- Logging In And Out
- Server Administrator Local System Login
- Server Administrator Managed System Login — Using the Desktop Icon
- Server Administrator Managed System Login — Using The Web Browser
- Central Web Server Login
- Using The Active Directory Login
- Single Sign-On
- Configuring Security Settings On Systems Running A Supported Microsoft Windows Operating System
- The Server Administrator Home Page
- Using The Online Help
- Using The Preferences Home Page
- Using The Server Administrator Command Line Interface
- Logging In And Out
- Server Administrator Services
- Working With Remote Access Controller
- Viewing Basic Information
- Configuring The Remote Access Device To Use A LAN Connection
- Configuring The Remote Access Device To Use A Serial Port Connection
- Configuring The Remote Access Device To Use A Serial Over LAN Connection
- Additional Configuration For iDRAC
- Configuring Remote Access Device Users
- Setting Platform Event Filter Alerts
- Server Administrator Logs
- Setting Alert Actions
- Setting Alert Actions For Systems Running Supported Red Hat Enterprise Linux And SUSE Linux Enterprise Server Operating Systems
- Setting Alert Actions In Microsoft Windows Server 2003 And Windows Server 2008
- Setting Alert Action Execute Application In Windows Server 2008
- BMC/iDRAC Platform Events Filter Alert Messages
- Troubleshooting
- Frequently Asked Questions
Software updates are done through an SSH session and secure FTP and root level permissions/credentials are required for
this discrete action and asked for when the action is set up or requested. Credentials from the discovery range are not
assumed.
ITA communicating with Windows systems:
For servers (systems running Windows Server operating systems), the system may be configured with either or both of
SNMP and CIM for discovery by ITA. Inventory requires CIM.
Software updates, as in Linux, are not related to discovery and polling and the protocols used.
Using Administrator level credentials asked for at the time the update is scheduled or performed, an administrative (drive)
share is established to a drive on the target system, and files copying from somewhere (possibly another network share) is
done to the target system. WMI functions are then invoked to execute the software update.
As Server Administrator is not installed on Clients/Workstations, so CIM discovery is used when the target is running the
OpenManage Client Instrumentation.
For many other devices such as network printers, SNMP is the standard to communicate with (primarily discover) the
device.
Devices such as EMC storage have proprietary protocols. Some information about this environment can be gathered from
looking at the ports used.
11. Are there any plans for SNMP v3 support?
No, there are no plans for SNMP v3 support.
12. Does an Underscore character in the domain name cause Server Admin login issues?
Yes, an underscore character in the domain name is invalid. All other special characters (except the hyphen) are invalid too.
Use case-sensitive alphabets and numerals only.
13. How does selecting/deselecting 'Active Directory' on the login page of Server Administrator impact privilege
levels?
If you do not select the Active Directory check box, you will only have access that is configured in the Microsoft Active
Directory. You cannot log in using the Extended Schema Solution in Microsoft Active Directory.
This solution enables you to provide access to Server Administrator; allowing you to add/control Server Administrator
users and privileges to existing users in your Active Directory software. For more information, see "Using Microsoft Active
Directory" in the Server Administrator Installation Guide available at dell.com/openmanagemanuals.
14. What actions do I follow while performing Kerberos authentication and trying to login from Web server?
For authentication, the contents of the files /etc/pam.d/openwsman and /etc/pam.d/sfcb, on the managed node, must
be replaced with:
For 32-bit:
auth required pam_stack.so service=system-auth auth required /lib/security/pam_nologin.so
account required pam_stack.so service=system-auth
For 64-bit:
auth required pam_stack.so service=system-auth auth required /lib64/security/
pam_nologin.so account required pam_stack.so service=system-auth
15. Why is the Red Hat Enterprise Linux 5.9 (32-bit) operating system not able to detect the Emulex card after
installing the Emulex drivers?
On systems running Red Hat Enterprise Linux 5.9 (32-bit) operating system, the Emulex driver is dependent on the following
RPMs:
● kernel-headers-2.6.18-346.el5.i386.rpm
● glibc-headers-2.5-107.i386.rpm
● glibc-devel-2.5-107.i386.rpm
● gcc-4.1.2-54.el5.i386.rpm
If any of the RPMs are missing, the system has issues in detecting the Emulex network adapters.
Frequently Asked Questions
65