Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Trademarks used in this text: Dell, the DELL logo, PowerEdge, PowerVault, and Dell OpenManage are trademarks of Dell Inc.; Microsoft, Windows, MS-DOS, and Windows NT are registered trademarks and WindowsServer is a trademark of Microsoft Corporation; Intel and Pentium
are registered trademarks and Intel386 is a trademark of Intel Corporation; Novell and NetWare are registered trademarks of Novell Inc.; Red Hat is a registered trademark of Red Hat, Inc.; VESA is a registered trademark of Video Electronics Standards Association; UNIX is a registered
trademark of The Open Group in the United States and other countries; OS/2 is a registered trademark of International Business Machines
Corporation.
Server Administrator includes software developed by the Apache Software Foundation (www.apache.org). Server Administrator utilizes the
OverLIB JavaScript library. This library can be obtained from www.bosrup.com.
Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products.
Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
Upgrade Using the Service Pack Capability
Dell PowerEdge Installation and Server Management CD
Unattended and Silent Installation
Upgrading Server Administrator
. . . . . . . . . . . . . . . . . . . . . . 46
. . . . . . . . . . . . . . . . 45
. . . . . . . . . 45
. . . . . . . . . . . . . . . . . . . . . 46
Before You Begin
Installation Requirements
Supported Operating Systems
System Requirements
Installation Procedures
Installing Server Administrator with Citrix
Considerations Before Installing Storage Management Service
Server Administrator provides a comprehensive, one-to-one systems management solution in two
ways: from an integrated, Web browser-based GUI (the Server Administrator home page) and from a
command line interface (CLI) through the operating system. Server Administrator is designed for
system administrators to both locally and remotely manage systems on a network.
Server Administrator allows system administrators to focus on managing their entire network by
providing comprehensive one-to-one systems management.
NOTE: For the purposes of Server Administrator, a system can be a stand-alone system, a server with
attached network storage units in separate chassis, or a modular system consisting of one or more server
modules in a chassis.
Server Administrator provides information about:
•Systems that are operating properly and systems that have problems
•Systems that require updates
•Systems that require remote recovery operations
Integrated Features
Server Administrator provides easy-to-use management and administration of local and remote systems
through a comprehensive set of integrated management services. Server Administrator resides solely
on the system being managed and is accessible both locally and remotely from the Server Administrator
home page. Remotely monitored systems may be accessed by dial-in, LAN, or wireless connections.
Server Administrator ensures the security of its management connections through role-based access
control (RBAC), authentication, and industry-standard secure socket layer (SSL) encryption.
Installation
You can install Server Administrator by using several methods. The Dell™ PowerEdge™ Installation
and Server Management CD provides a setup program to install, upgrade, and uninstall Server
Administrator and other managed system software components on your managed system.
The Dell Systems Management Consoles CD provides a setup program to install, upgrade, and
uninstall management station software components on your management station. Additionally, you
can install Server Administrator on multiple systems through an unattended installation across a
network. Lastly, if you have a modular system, or if your Microsoft
was preinstalled, you already have the Server Administrator installed on your system.
®
Windows® operating system
Introduction9
NOTE: If you have a modular system, you must install Server Administrator on each server module that is installed
in the chassis.
To update individual Server Administrator components, use component specific Dell Update Packages.
Use the Dell Server Update Utility application CD to view the complete version report and to update an
entire system. The Server Update Utility is a CD-ROM based application for identifying and applying
updates to your server. The Server Update Utility can be downloaded from support.dell.com.
See the Server Update Utility User's Guide for more information about obtaining and using the Server
Update Utility (SUU) to update your Dell PowerEdge server or to view the updates available for any
server listed in the Repository.
Server Administrator Home Page
The Server Administrator home page provides easy to set up and easy-to-use Web browser-based system
management from the managed system or from a remote host through a LAN, dial-up service, or wireless
network. When the Server Administrator secure port server is installed and configured on the managed
system, you can perform remote management functions from any system that has a supported Web
browser and connection. Additionally, the Server Administrator home page provides extensive,
context-sensitive online help.
Instrumentation Service
The Instrumentation Service provides rapid access to detailed fault and performance information
gathered by industry-standard systems management agents and allows remote administration of
monitored systems, including shutdown, startup, and security.
Remote Access Service
NOTE: The Remote Access Service is not available on modular systems. You must directly connect to the Dell
Remote Access Controller (DRAC) on a modular system. See the Dell Embedded Remote Access/MC User's Guide
for more information.
The Remote Access Service provides a complete, remote system management solution for systems
equipped with a DRAC solution. The Remote Access Service provides remote access to an inoperable
system, allowing you to get the system up and running as quickly as possible. The Remote Access Service
also provides alert notification when a system is down and allows you to remotely restart a system.
Additionally, the Remote Access Service logs the probable cause of system crashes and saves the most
recent crash screen.
10Introduction
Storage Management Service
The Storage Management Service provides storage management information in an integrated graphical
view. The current release of Server Administrator provides two staggered versions of the Storage
Management Service:
1
Basic Storage Management Service
The basic Storage Management Service is similar to the Storage Management Service provided in
earlier releases of Server Administrator.
The basic Storage Management Service of Server Administrator:
•Enables you to view the status of local and remote storage attached to a monitored system.
•Supports SATA and ATA. Does not support Fibre Channel.
NOTE: Array Manager is not available if no previous Dell OpenManage™ systems management software (with
Array Manager installed) is detected. It is only available for upgrade. Support for Array Manager will be
discontinued in a future release. It is recommended that you switch to use Storage Management Service where
applicable.
2
Enhanced Storage Management Service
The enhanced Storage Management Service provides additional features for configuring storage.
On Windows and Linux, the enhanced Storage Management Service is installed using Express Setup
providing that the system does not have an existing Array Manager installation.
In addition to the tasks that you can perform using basic Storage Management Service, enhanced
Storage Management Service of Server Administrator:
•Allows you to perform controller and enclosure functions for all supported RAID and non-RAID
controllers and enclosures from a single graphical or command line interface without the use of
the controller BIOS utilities.
•Supports SCSI, SATA, ATA, and SAS; however; Fibre Channel is not supported.
•Protects your data by configuring data redundancy, assigning hot spares, or rebuilding failed drives.
Diagnostic Service
NOTE: The Diagnostic Service is not available on modular systems.
The Diagnostic Service provides a suite of diagnostic programs that run locally on your system or remotely
on a system connected to the network. The Diagnostic Service is engineered to diagnose problems on
individual systems and to run concurrently with all other applications running on the system under test.
Logs
Server Administrator displays logs of commands issued to or by the system, monitored hardware events,
POST events, and system alerts. You can view logs on the home page, print or save them as reports, and
send them by e-mail to a designated service contact.
Introduction11
Other Documents You Might Need
Besides this User's Guide, you can find the following guides either on the Dell Support website at
support.dell.com or on the documentation CD:
•The
•The
•The
•The
•The
•The
•The
•The
•The
•The
Dell OpenManage™ Installation and Security User's Guide
installation procedures and step-by-step instructions for installing, upgrading, and uninstalling Server
Administrator for each supported operating system.
Dell OpenManage Software Quick Installation Guide
can install on your management station (console) and on your managed systems and procedures for
installing your console and managed system applications on systems running supported operating
systems.
Dell OpenManage Server Administrator Compatibility Guide
about Server Administrator installation and operation on various hardware platforms (or systems)
running supported Microsoft Windows, and Red Hat
Dell OpenManage Server Administrator SNMP Reference Guide
Management Protocol (SNMP) management information base (MIB). The SNMP MIB defines
variables that extend the standard MIB to cover the capabilities of systems management agents.
Dell OpenManage Server Administrator CIM Reference Guide
Information Model (CIM) provider, an extension of the standard management object format (MOF) file.
The CIM provider MOF documents supported classes of management objects.
Dell OpenManage Server Administrator Messages Reference Guide
displayed in your Server Administrator home page Alert log or on your operating system’s event viewer.
This guide explains the text, severity, and cause of each Instrumentation Service Alert message that
Server Administrator issues.
Dell OpenManage Server Administrator Command Line Interface User's Guide
complete command line interface for Server Administrator, including an explanation of CLI
commands to view system status, access logs, create reports, configure various component parameters,
and set critical thresholds.
Dell OpenManage Array Manager User's Guide
and managing local and remote storage attached to a system. This document is also available in HTML
and PDF formats on the
Array Manager console as online help.
Dell OpenManage Server Administrator Storage Management User's Guide
reference guide for configuring and managing local and remote storage attached to a system. This
document is also available in HTML and PDF formats on the
as well as from the Storage Management console as online help.
Dell Remote Access Controller Installation and Setup Guide
installing and configuring a DRAC III, DRAC III/XT, and an ERA/O controller, configuring an ERA
controller, and using a RAC to remotely access an inoperable system.
Dell PowerEdge Installation and Server Management
®
Enterprise Linux operating systems.
is a comprehensive reference guide for configuring
provides complete information on
provides an overview of applications that you
provides compatibility information
documents the Simple Network
documents the Common
lists the messages that are
documents the
CD, as well as from the
is a comprehensive
Installation and Server Management
provides complete information about
CD,
12Introduction
•The
•The
•The
•The
•The
•The
•The
•The
•The
The Installation and Server Management CD contains a readme file for Server Administrator and
additional readme files for most applications found on the CD.
configuring and using an ERA/MC controller to remotely manage and monitor your modular system
and its shared resources through a network.
Dell PowerEdge 830 Systems — Configuration Guide
PowerEdge 830 system.
Dell PowerEdge 850 Systems — Configuration Guide
PowerEdge 850 system.
Dell PowerEdge 1655MC Systems — System Configuration Guide
setting up a PowerEdge 1655MC system.
Dell PowerEdge 1855 Systems — Configuration Guide
PowerEdge 1855 system.
Dell OpenManage Remote Install User's Guide
simultaneous provisioning and configuration solutions over the network by leveraging image based
technology.
Dell Update Packages User's Guide
Packages as part of your system update strategy.
Server Update Utility User's Guide
Update Utility (SUU) to update your Dell PowerEdge server or to view the updates available for any
server listed in the Repository.
provides information about obtaining and using Dell Update
provides information about obtaining and using the Server
provides information about using the racadm
provides complete information about
provides an overview of initially setting up a
provides an overview of initially setting up a
provides an overview of initially
provides an overview of initially setting up a
provides information about unattended,
Obtaining Technical Assistance
If at any time you do not understand a procedure described in this guide or if your product does not
perform as expected, help tools are available to assist you. For more information about these help tools,
see "Getting Help" in your system's Installation and Troubleshooting Guide.
Additionally, Dell Enterprise Training and Certification is available; see www.dell.com/training for more
information. This service may not be offered in all locations.
Introduction13
14Introduction
What’s New for Version 2.3
•Added Serial Attached SCSI (SAS) support for Dell™ PowerEdge™ 6800 and 6850
•Added support for PERC 5/e
•Added support for a new SAS hard-drive enclosure —PowerVault MD1000
®
•Removed support for Novell
NetWare® on Dell PowerEdge 6800 and 6850
What’s New for Version 2.315
16What’s New for Version 2.3
Setup and Administration
Security Management
Server Administrator provides security through role-based access control (RBAC), authentication,
and encryption for both the Web-based and command line interfaces.
Role-Based Access Control
RBAC manages security by determining the operations that can be executed by persons in particular
roles. Each user is assigned one or more roles, and each role is assigned one or more user privileges
that are permitted to users in that role. With RBAC, security administration corresponds closely to
an organization's structure.
User Privileges
Server Administrator grants different access rights based on the user's assigned group privileges.
The three user levels are: User, Power User, and Administrator.
Users can view most information.
Power Users can set warning threshold values, run diagnostic tests, and configure which alert actions
are to be taken when a warning or failure event occurs.
Administrators can configure and perform shutdown actions, configure Auto Recovery actions in
case a system has a hung operating system, and clear hardware, event, and command logs.
Administrators can also send e-mail.
Server Administrator grants read-only access to users logged in with User privileges, read and write
access to users logged in with Power User privileges, and read, write, and admin access to users
logged in with Admin privileges. See Table 3-1.
Table 3-1. User Privileges
User PrivilegesAccess Type
AdminWriteRead
User X
Pow er Us er XX
AdminXXX
Setup and Administration17
Read access allows viewing of data reported by Server Administrator. Read access does not allow changing
or setting values on the managed system.
Write access allows values to be changed or set on the managed system.
Admin access allows shutdown of the managed system.
Privilege Levels to Access Server Administrator Services
Table 3-2 summarizes which user levels have privileges to access and manage Server Administrator Services.
Table 3-2. Server Administrator User Privilege Levels
ServiceUser Privilege Level Required
ViewManage
InstrumentationU, P, AP, A
Remote AccessU, P, AA
DiagnosticsP, AP, A
Storage Management U, P, A A
Table 3-3 defines the user privilege level abbreviations used in Table 3-2.
Table 3-3. Legend for Server Administrator User Privilege Levels
UUser
PPower User
AAdministrator
NANot Applicable
Authentication
The Server Administrator authentication scheme ensures that the correct access types are assigned to the
correct user privileges. Additionally, when the command line interface (CLI) is invoked, the Server
Administrator authentication scheme validates the context within which the current process is running.
This authentication scheme ensures that all Server Administrator functions, whether accessed through
the Server Administrator home page or CLI, are properly authenticated.
Microsoft Windows Authentication
For supported Microsoft® Windows® operating systems, Server Administrator authentication is based
on the operating system's user authentication system using Windows NT
modules to authenticate. This underlying authentication system allows Server Administrator security to
be incorporated in an overall security scheme for your network.
18Setup and Administration
®
LAN Manager (NTLM)
Red Hat Enterprise Linux Authentication
For supported Red Hat® Enterprise Linux operating systems, Server Administrator authentication is
based on the Red Hat Enterprise Linux Pluggable Authentication Modules (PAM) library.
This documented library of functions allows an administrator to determine how individual applications
authenticate users.
Encryption
Server Administrator is accessed over a secure HTTPS connection using secure socket layer (SSL)
technology to ensure and protect the identity of the system being managed. Java Secure Socket
Extension (JSSE) is used by supported Microsoft Windows, and Red Hat Enterprise Linux to protect the
user credentials and other sensitive data that is transmitted over the socket connection when a user
accesses the Server Administrator home page.
Assigning User Privileges
You must properly assign user privileges to all Server Administrator users before installing Server
Administrator in order to ensure critical system component security.
The following procedures provide step-by-step instructions for creating Server Administrator users and
assigning user privileges for each supported operating system:
•Creating Server Administrator Users for Supported Windows Operating Systems
•Creating Server Administrator Users for Supported Red Hat Enterprise Linux Operating Systems
NOTICE: You must assign a password to every user account that can access Server Administrator to protect
access to your critical system components. Additionally, users who do not have an assigned password cannot log
into Server Administrator on a system running Windows Server™ 2003 due to operating system constraints.
NOTICE: You should disable guest accounts for supported Microsoft Windows operating systems in order to
protect access to your critical system components. See "Disabling Guest and Anonymous Accounts in Supported
Windows Operating Systems" for instructions.
Creating Server Administrator Users for Supported Windows Operating Systems
NOTE: You must be logged in with Admin privileges to perform these procedures.
Creating Users and Assigning User Privileges for Supported Windows Server 2003 Operating Systems
NOTE: For questions about creating users and assigning user group privileges or for more detailed instructions,
see your operating system documentation.
1
Click the
2
In the console tree, expand
3
Click
Start
Action
, and then click
button, right-click
Local Users and Groups
New User
My Computer,
.
and point to
, and then click
Manage
Users
.
.
Setup and Administration19
4
Type the appropriate information in the dialog box, select or clear the appropriate check boxes, and
Create
then click
NOTICE: You must assign a password to every user account that can access Server Administrator to protect
access to your critical system components. Additionally, users who do not have an assigned password
cannot log into Server Administrator on a system running Windows Server 2003 due to operating
system constraints.
5
In the console tree, under
6
Click the group to which you want to add the new user:
7
Click
Action
8
Click
Add
9
Type the user name that you are adding and click
10
Click OK.
.
, and then click
.
Local Users and Groups
Properties
.
, click
Groups
Users, Power Users
Check Names
.
to validate.
, or
Administrators
New users can log into Server Administrator with the user privileges for their assigned group.
Creating Users and Assigning User Privileges for Supported Windows 2000 Operating Systems
NOTE: For questions about creating users and assigning user group privileges or for more detailed instructions,
see your operating system documentation.
1
Right-click
2
In the console tree, expand
3
Click
4
Type the appropriate information in the dialog box, select or clear the appropriate check boxes, and
then click
My Computer
Action
, and then click
Create
and point to
Local Users and Groups
New User
Manage
.
.
, and then click
Users
.
.
.
NOTICE: You must assign a password to every user account that can access Server Administrator to protect
access to your critical system components. Additionally, users who do not have an assigned password
cannot log into Server Administrator on a system running Windows Server 2003 due to operating
system constraints.
5
In the console tree, under
6
Click the group to which you want to add the new user:
7
Click
Action
, and then click
8
Click
Add
.
9
Click the name of the user you want to add, and then click
10
Click
Check Names
11
Click OK.
Local Users and Groups
, click
Groups
.
Users, Power Users
Properties
.
Add
.
to validate the user name that you are adding.
, or
Administrators
New users can log into Server Administrator with the user privileges for their assigned group.
20Setup and Administration
.
Adding Users to a Domain
NOTE: For questions about creating users and assigning user group privileges or for more detailed instructions,
see your operating system documentation.
NOTE: You must have Active Directory installed on your system to perform the following procedures.
1
Click the
Users and Computers
2
In the console tree, right-click
and then point to
3
Type the appropriate user name information in the dialog box, and then click
NOTICE: You must assign a password to every user account that can access Server Administrator to protect
access to your critical system components. Additionally, users who do not have an assigned password
cannot log into Server Administrator on a system running Windows Server 2003 due to operating
system constraints.
4
Click
5
Double-click the icon representing the user you just created.
6
Click the
7
Click
8
Select the appropriate group and click
9
Click OK, and then click OK again.
Start
button, and then point to
Next
, and then click
Member of
Add
.
.
New→
tab.
User
Finish
Control Panel→
Users
or right-click the container in which you want to add the new user,
Administrative Tools→
Active Directory
.
Next
.
.
Add
.
New users can log into Server Administrator with the user privileges for their assigned group and domain.
Creating Server Administrator Users for Supported Red Hat Enterprise Linux Operating Systems
Admin access privileges are assigned to the user logged in as root. To create users with User and Power
User privileges, perform the following steps.
NOTE: You must be logged in as root to perform these procedures.
NOTE: You must have the useradd utility installed on your system to perform these procedures.
Setup and Administration21
Creating Users
NOTE: For questions about creating users and assigning user group privileges or for more detailed instructions,
see your operating system documentation.
Creating Users With User Privileges
1
Run the following command from the command line:
useradd -d <
where
<
group
NOTE: If <group> does not exist, you must create it by using the groupadd command.
2
Ty p e
passwd <
3
When prompted, enter a password for the new user.
NOTICE: You must assign a password to every user account that can access Server Administrator to protect
access to your critical system components.
The new user can now log in to Server Administrator with User group privileges.
Creating Users With Power User Privileges
1
Run the following command from the command line:
useradd -d <
NOTE: You must set root as the primary group.
2
Ty p e
passwd <
3
When prompted, enter a password for the new user.
home-directory
>
is
not root
username
.
>
and press <Enter>.
home-directory
username
>
and press <Enter>.
> -g <
> -g root <
group
> <
username
username
>
>
NOTICE: You must assign a password to every user account that can access Server Administrator to protect
access to your critical system components.
The new user can now log in to Server Administrator with Power User group privileges.
Disabling Guest and Anonymous Accounts in Supported
Windows Operating Systems
NOTE: You must be logged in with Admin privileges to perform this procedure.
1
If your system is running Windows Server 2003, click the
point to
2
In the console tree, expand
3
Click the
4
Click
5
Select
A red circle with an X appears over the user name. The account is disabled.
22Setup and Administration
Manage
Action
Account is disabled
. If your system is running Windows 2000, right-click
Guest
or
IUSR
and point to
Local Users and Groups
_sys tem name
Properties
and click OK.
user account.
.
Start
and click
button, right-click
My Computer
Users
.
My Computer,
and point to
and
Manage
.
Configuring the SNMP Agent
Server Administrator supports the Simple Network Management Protocol (SNMP) systems management
standard on all supported operating systems. In most cases, SNMP is installed as part of your operating
system installation. An installed supported systems management protocol standard, such as SNMP, is
required before installing Server Administrator. See "Installation Requirements" for more information.
You can configure the SNMP agent to change the community name, enable Set operations, and send
traps to a management station. To configure your SNMP agent for proper interaction with management
applications such as the Dell OpenManage™ IT Assistant and Array Manager, perform the procedures
described in the following sections.
NOTE: For IT Assistant to retrieve management information from a system running Server Administrator, the
community name used by IT Assistant must match a community name on the system running Server Administrator.
For IT Assistant to modify information or perform actions on a system running Server Administrator, the community
name used by IT Assistant must match a community name that allows Set operations on the system running
Server Administrator. For IT Assistant to receive traps (asynchronous event notifications) from a system running
Server Administrator, the system running Server Administrator must be configured to send traps to the system
running IT Assistant.
The following procedures provide step-by-step instructions for configuring the SNMP agent for each
supported operating system:
•Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems
•Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux Operating Systems
Configuring the SNMP Agent for Systems Running Supported Windows Operating Systems
Server Administrator uses the SNMP services provided by the Windows SNMP agent. You can configure
the SNMP agent to change the community name, enable Set operations, and send traps to a management
station. To configure your SNMP agent for proper interaction with management applications such as
IT Assistant and Array Manager, perform the procedures described in the following sections.
NOTE: See your operating system documentation for additional details on SNMP configuration.
Enabling SNMP Access By Remote Hosts
Windows Server 2003, by default, does not accept SNMP packets from remote hosts. For systems running
Windows Server 2003, you must configure the SNMP service to accept SNMP packets from remote hosts
if you plan to manage the system by using SNMP management applications from remote hosts.
To enable a system running the Windows Server 2003 operating system to receive SNMP packets from a
remote host, perform the following steps:
1
Click the
The
2
Expand the
3
Expand the
Start
button, right-click
Computer Management
Computer Management
Services and Applications
My Computer
window appears.
icon in the window, if necessary.
icon and click
, and point to
Services
Manage
.
.
Setup and Administration23
4
Scroll down the list of services until you find
Properties
click
The
SNMP Service Properties
5
Click the
6
Select
Accept SNMP packets from any host
from these hosts
Changing the SNMP Community Name
.
Security
window appears.
tab.
list.
SNMP Service
, right-click
SNMP Service
, or add the remote host to the
, and then
Accept SNMP packets
Configuring the SNMP community names determines which systems are able to manage your system
through SNMP. The SNMP community name used by management applications must match an SNMP
community name configured on the Server Administrator system so that the management applications
can retrieve management information from Server Administrator.
1
If your system is running Windows Server 2003, click the
point to
The
2
Expand the
3
Expand the
4
Scroll down the list of services until you find
click
The
5
Click the
a
Manage
Computer Management
Properties
SNMP Service Properties
To add a community name, click
The
. If your system is running Windows 2000, right-click
window appears.
Computer Management
Services and Applications
icon in the window, if necessary.
icon and click
SNMP Service
.
window appears.
Security
SNMP Service Configuration
tab to add or edit a community name.
Add
under the
window appears.
Start
Services
button, right-click
My Computer
.
, right-click
SNMP Service
My Computer,
and point to
Accepted Community Names
and
Manage
, and then
list.
.
b
Type the community name of a system that is able to manage your system (the default is public) in
the
Community Name
SNMP Service Properties
The
c
To change a community name, select a community name in the
and click
The
d
Make all necessary edits to the community name of the system that is able to manage your system
in the
The
6
Click OK to save the changes.
Edit
.
SNMP Service Configuration
Community Name
SNMP Service Properties window appears
24Setup and Administration
text box and click
Add
.
window appears.
window appears.
text box, and then click OK.
Accepted Community Names
list
.
Enabling SNMP Set Operations
SNMP Set operations must be enabled on the Server Administrator system to change Server
Administrator attributes using IT Assistant.
If your system is running Windows Server 2003, click the
1
point to
The
2
Expand the
3
Expand the
4
Scroll down the list of services until you find
Manage
. If your system is running Windows 2000, right-click
Computer Management
Computer Management
Services and Applications
window appears.
icon in the window, if necessary.
icon, and then click
SNMP Service
Start
button, right-click
My Computer
Services
.
, right-click
My Computer,
and point to
SNMP Service
and
Manage
, and click
Properties.
The
SNMP Service Properties
5
Click the
6
Select a community name in the
The
7
Set the
The
8
Click OK to save the changes.
Configuring Your System to Send SNMP Traps to a Management Station
Security
tab to change the access rights for a community.
SNMP Service Configuration
Community Rights
SNMP Service Properties
window appears.
Accepted Community Names
window appears.
to
READ WRITE
or
READ CREATE
window appears.
list, and then click
, and click OK.
Edit
.
Server Administrator generates 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 Server Administrator
system for SNMP traps to be sent to a management station.
If your system is running Windows Server 2003, click the
1
point to
The
Manage
. If your system is running Windows 2000, right-click
Computer Management
window appears.
Start
button, right-click
My Computer
My Computer,
and point to
and
Manage
.
.
2
Expand the
3
Expand the
4
Scroll down the list of services until you find
Properties
The
SNMP Service Properties
Computer Management
Services and Applications
.
window appears.
icon in the window, if necessary.
icon and click
SNMP Service
Services
.
, right-click
SNMP Service
Setup and Administration25
, and click
5
Click the
a
b
c
6
Click OK to save the changes.
Traps
tab to add a community for traps or to add a trap destination for a trap community.
To add a community for traps, type the community name in the
Add to list
, which is located next to the
Community Name
Community Name
box.
box and click
To add a trap destination for a trap community, select the community name from the
Name
drop-down box and click
The
SNMP Service Configuration
Type in the trap destination and click
The
SNMP Service Properties
Add
under the
window appears.
Add
.
window appears.
Trap Destinations
box.
Community
Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux
Operating Systems
Server Administrator uses the SNMP services provided by the ucd-snmp or net-snmp SNMP agent. You
can configure the SNMP agent to change the community name, enable Set operations, and send traps to
a management station. To configure your SNMP agent for proper interaction with management applications
such as IT Assistant and Array Manager, perform the procedures described in the following sections.
NOTE: See your operating system documentation for additional details on SNMP configuration.
SNMP Agent Access Control Configuration
The management information base (MIB) branch implemented by the Instrumentation Service is
identified by the OID, 1.3.6.1.4.1.674.10892.1. Management applications must have access to this
branch of the MIB tree to manage systems running the Instrumentation Service.
For Red Hat Enterprise Linux operating systems, the default SNMP agent configuration gives read-only
access for the "public" community only to the MIB-II "system" branch (identified by the OID,
1.3.6.1.2.1.1) of the MIB tree. This configuration does not allow management applications to retrieve or
change Instrumentation Service and other systems management information outside of the MIB-II
"system" branch.
If Server Administrator detects this configuration during installation, it attempts to modify the SNMP
agent configuration to give read-only access to the entire MIB tree for the "public" community. It does
this by changing the SNMP agent configuration file, /etc/snmp/snmpd.conf, in two ways.
The first change is to create a view to the entire MIB tree by adding the following line if it does not exist:
view all included .1
The second change is to modify the default "access" line to give read-only access to the entire MIB tree
for the "public" community. Server Administrator looks for the following line:
access notConfigGroup "" any noauth exact systemview none none
If Server Administrator finds the line above, it modifies the line so that it reads:
access notConfigGroup "" any noauth exact all none none
26Setup and Administration
These changes to the default SNMP agent configuration give read-only access to the entire MIB tree for
the "public" community.
NOTE: To ensure that Server Administrator is able to modify the SNMP agent configuration to provide proper
access to systems management data, it is recommended that any other SNMP agent configuration changes be
made after installation of Server Administrator.
Changing the SNMP Community Name
Configuring the SNMP community names determines which systems are able to manage your system
through SNMP. The SNMP community name used by management applications must match an SNMP
community name configured on the Server Administrator system so that the management applications
can retrieve management information from Server Administrator.
To change the SNMP community name used for retrieving management information from a system
running Server Administrator, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf, and
perform the following steps:
1
Find the line that reads:
com2sec publicsec default public
or
com2sec notConfigUser default public
Edit this line, replacing
2
public
with the new SNMP community name. When edited, the new line
should read:
com2sec publicsec default
community_name
or
com2sec notConfigUser default
3
To enable SNMP configuration changes, restart the SNMP agent by typing:
community_name
service snmpd restart
Setup and Administration27
Enabling SNMP Set Operations
SNMP Set operations must be enabled on the system running Server Administrator in order to change
Server Administrator attributes using IT Assistant.
To enable SNMP Set operations on the system running Server Administrator, edit the SNMP agent
configuration file, /etc/snmp/snmpd.conf, and perform the following steps:
1
Find the line that reads:
access publicgroup "" any noauth exact all none none
or
access notConfigGroup "" any noauth exact all none none
2
Edit this line, replacing the first
none
with
all
. When edited, the new line should read:
access publicgroup "" any noauth exact all all none
or
access notConfigGroup "" any noauth exact all all none
To enable SNMP configuration changes, restart the SNMP agent by typing:
3
service snmpd restart
Configuring Your System to Send Traps to a Management Station
Server Administrator generates SNMP traps in response to changes in the status of sensors and other
monitored parameters. One or more trap destinations must be configured on the system running Server
Administrator for SNMP traps to be sent to a management station.
To configure your system running Server Administrator to send traps to a management station, edit the
SNMP agent configuration file, /etc/snmp/snmpd.conf, and perform the following steps:
1
Add the following line to the file:
trapsink
IP_address community_name
where
IP_address
SNMP community name
2
To enable SNMP configuration changes, restart the SNMP agent by typing:
service snmpd restart
28Setup and Administration
is the IP address of the management station and
community_name
is the
X.509 Certificate Management Prerequisites
Web certificates are necessary to ensure the identity of a remote system and to ensure that information
exchanged with the remote system cannot be viewed or changed by others.
This section explains the administrative prerequisites for ensuring your ability to generate a new X.509
certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from
Certification Authority (CA) on each supported operating system.
The X.509 certificate management is provided through the Server Administrator home page for all
supported operating systems.
Firewall Configuration on Systems Running Supported Red Hat
Enterprise Linux Operating Systems
If you enable firewall security when installing Red Hat Enterprise Linux, the SNMP port on all external
network interfaces is closed by default. To enable SNMP management applications such as IT Assistant
to discover and retrieve information from Server Administrator, the SNMP port on at least one external
network interface must be open. If Server Administrator detects that the SNMP port is not open in the
firewall for any external network interface, Server Administrator displays a warning message and logs a
message to the system log.
You can open the SNMP port by disabling the firewall, opening an entire external network interface in
the firewall, or opening the SNMP port for at least one external network interface in the firewall. You can
perform this action before or after Server Administrator is started.
To open the SNMP port using one of the previously described methods, perform the following steps:
1
At the Red Hat Enterprise Linux command prompt, type
Mode Setup Utility.
setup
and press <Enter> to start the Text
NOTE: This command is available only if you have performed a default installation of the operating system.
The
Choose a Tool
2
Select
Firewall Configuration
Firewall Configuration
The
3
Select the Security Level by tabbing to it and pressing the spacebar. The selected Security Level is
indicated by an asterisk.
NOTE: Press <F1> for more information about the firewall security levels. The default SNMP port number is 161.
If you are using the X Window System GUI, pressing <F1> may not provide information about firewall security
levels on newer versions of Red Hat Enterprise Linux.
To disable the firewall, select
a
b
To open an entire network interface or the SNMP port, select
continue with step 4.
menu appears.
using the down arrow and press <Enter>.
screen appears.
No firewall
or
Disabled
and go to step 7.
High, Medium,
Setup and Administration29
or
Enabled
and
4
Tab t o
Customize
The
Firewall Configuration - Customize
5
Select whether to open an entire network interface or just the SNMP port on all network interfaces.
a
To open an entire network interface, tab to one of the Trusted Devices and press the spacebar.
and press <Enter>.
screen appears.
An asterisk in the box to the left of the device name indicates that the entire interface will be opened.
b
To open the SNMP port on all network interfaces, tab to
6
Tab t o OK and press <Enter>.
The
Firewall Configuration
7
Tab t o OK and press <Enter>.
The
8
Choose a Tool
Tab t o
Quit
menu appears.
and press <Enter>.
screen appears.
Other ports
and type
snmp:udp
.
30Setup and Administration
Loading...
+ 132 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.