To start a Server Administrator session on a local system, click the Server Administrator icon
on your desktop. Clicking the Server Administrator icon causes the Log in
window to be displayed.
To start a Server Administrator session on a remote system, open your Web
browser and type:
https://hostname:1311
(where
hostname is the assigned name for the managed node system and 1311 is the
default port)
or
https://IP address:1311
(where
IP address is the IP address for the managed node system and 1311 is the
default port)
in the address field and press <Enter>.
The Server Administrator home page opens and displays the Log in
window.
NOTE: You must type https://
(not http://) in the address
field to receive a valid response in your browser.
NOTE: The default port for Server
Administrator is 1311. You can change the port, if necessary. See "Web Server and
Security Setup" for instructions on setting up your server
preferences.
To log into the Server Administrator home page, type in your preassigned Username and Password in the appropriate fields on
the Log in window. If you are accessing Server Administrator from a
defined domain, you will also need to specify the correct Domain name.
NOTE: You must have preassigned user rights
to log into Server Administrator. See "Setup and Administration" for
instructions on setting up new users.
To end your Server Administrator session, click Log Out on the global
navigation bar. The Log Out button is located in the upper- right
corner of each Server Administrator home page.
The system tree displays all
visible system objects based on the user's access privileges.
The action window displays the available
management actions for the
selected system tree object based on
the user's access privileges. The action window contains three
functional areas:
The action tabs display the primary actions or
categories of actions that are available for the selected object based on the user's access
privileges.
The action tabs are divided into subcategories
of all available secondary options for the action tabs based on the user's access
privileges.
The data area displays information for the
selected system tree object, action tab, and subcategory based on
the user's access privileges.
Additionally, when logged into the Server Administrator home page, the system
model, the assigned
name of the system, and the current user's user name and user
privilege are displayed in the top-right corner of the window.
The following figure shows a Server Administrator home page layout for a user
logged in with administrator privileges:
Clicking an object in the system tree opens a corresponding
action window for that object. You can navigate in the action window by clicking
action tabs to select major categories and clicking the action tab subcategories to
access more detailed information or more focused actions. The information
displayed in the data area of the action window can range from system logs to
status indicators to system probe gauges. Underlined items in the data area of
the action window indicate a further level of functionality. Clicking an
underlined item creates a new data area in the action window that contains a
greater level of detail. For example, clicking Main System Chassis
under the Health subcategory of the Properties action tab lists
the health status of all the
components contained in the Main System Chassis object that are monitored for
health status.
NOTE: Many of the system tree objects, system
components, action tabs, or data area features are not available to users logged in with only User privileges. Admin or Power User
privileges are required to view many of the system tree objects, system
components, action tabs, and data area features that are configurable.
Additionally, only users logged in with Admin privileges have access to
the shutdown functionality included under the Shutdown tab.
The system tree appears on the left side of the Server Administrator home
page
and lists the components of your system that are viewable. The system components are categorized by component
type. When you expand the main object
known as System,
the major categories of system components that
may appear are Main System Chassis, Software, and Storage.
To expand a branch of the tree, click the plus sign (
) to the left of an object, or double-click the object. A minus sign (
)indicates an expanded entry
that cannot be expanded further.
When you click an item on the system tree, details about the component or object appear in the
data area of
the action window. Clicking an action tab displays all
available user options as a list of subcategories.
Clicking an object on the system tree opens that component's action window,
displaying the available action tabs. The data area defaults to a preselected
subcategory of the first
action tab for the selected object. The preselected subcategory is usually the
first option. For example, clicking the Main System
Chassis object opens an action window in which the Properties action
tab and Health subcategory is displayed in the window's data area.
Data Area
The data area is located below the action tabs on the right side of the home
page. The data area is where you perform tasks or view details about system components. The content of the window depends on the
system tree object and action tab that are currently selected. For example,
when you select BIOS from the system tree, the Properties tab is selected
by default and the version information for the system
BIOS appears in the data area. The data area of the action window contains many common features, including status indicators, task buttons, underlined items, and
gauge indicators.
The icons that appear next to component names show the
status of that component (as of the latest page refresh).
A green check mark indicates that a component is healthy
(normal).
A yellow triangle containing an exclamation point indicates
that a component has a warning (noncritical) condition. A warning condition
occurs when a probe or other monitoring tool detects a reading for a
component that falls within certain minimum and maximum values. A warning
condition requires prompt attention.
A red X indicates that a component has a critical (failure) condition.
A critical condition occurs when a probe or other monitoring tool detects
a reading for a component that falls within certain minimum and maximum
values. A critical condition requires immediate attention.
A blank space indicates that a component's health status is
unknown.
Most windows opened from the Server Administrator home page contain at
least three task buttons: Print, Email, and Refresh. There
are numerous other task buttons included on specific Server Administrator
windows. Log windows, for example, also contain Save As and Clear
Log task buttons. For specific information about individual task buttons,
click Help on any Server Administrator home page window to view detailed information about the specific
window you are viewing.
Clicking Print
prints a copy of the open window to your default printer.
Clicking Email creates an
e-mail message addressed to your designated e-mail recipient. See "Setting User
and Server Preferences" for instructions on setting up your e-mail server and
default e-mail recipient.
Clicking Refresh reloads the system component status
information in the action window data area.
Clicking Save As saves an HTML file of the action window in a .zip
file.
Clicking Clear Log erases all events from the log displayed in the action window data area.
Underlined Items
Clicking an underlined item in the action window data area displays additional details about that
item.
Gauge Indicators
Temperature probes, fan probes, and voltage probes are each represented by a
gauge indicator. For example, readings from a system's CPU fan probe are
displayed in the following gauge indicator:
Context-sensitive online help is available for every window of the Server
Administrator home page. Clicking Help on the global navigation bar opens
an independent help window that contains detailed information about the specific
window you are viewing. The online help is designed to help guide you through the
specific actions required to perform all aspects of the Server Administrator
services. Online help is available for all windows you can view, based on the
software and hardware groups that Server Administrator discovers on your system
and your user privilege level.
The Server Administrator command line interface (CLI) allows users to perform essential systems management
tasks
from the operating system command prompt of a monitored system.
In many cases, the CLI allows a user with a very
well-defined task in mind to rapidly retrieve information about the system. Using CLI commands,
for example, administrators can write batch
programs or scripts to execute at specific times. When these programs execute,
they can capture reports on components of interest, such as fan RPMs. With
additional scripting, the CLI can be used to capture data during
periods of high system usage to compare with the same measurements at times of
low system usage. Command results can be routed to a file for later analysis.
The reports can help administrators to gain information that can be used to
adjust usage patterns, to justify purchasing new system resources, or to focus
on the health of a problem component.
For complete instructions on the functionality and
use of the CLI, see the Server Administrator Command Line
Interface User's Guide.
Perform the following steps to set up your Server Administrator Web server
preferences.
NOTE: You must be logged in with Admin privileges to set or reset
server preferences.
Click System�> Software�> Server Administrator,
and click Server under the Preferences tab.
In the Server Preferences window, set options as necessary.
The Session Timeout feature can set a limit on the amount of
time that a Server Administrator session can remain active. Select the Enable
radio button to allow Server Administrator to time out if there is no user
interaction for a specified number of minutes. Users whose session times out
must log in again to continue. Select the Disable radio button to
disable the Server Administrator session timeout feature.
The HTTPS Port field specifies the secure port for Server
Administrator. The default secure port for Server Administrator is 1311.
NOTE: Changing the port number to an
invalid or in-use port number might prevent other applications or browsers
from accessing Server Administrator on the managed node system.
The IP Address to Bind to field
specifies the IP Address(es) for the managed node system that Server
Administrator binds to when starting a session. Select the All radio button to
bind to all IP addresses applicable for your system. Select the Specific
radio button to bind to a specific IP address.
NOTE: Changing the IP Address to
Bind to value to a value other than All may prevent other
applications or browsers from accessing Server Administrator on the
managed node system.
The SMTP Server name and DNS Suffix for SMTP Server
fields specify
your company or organization's Simple Mail Transfer Protocol (SMTP) and
domain name server (DNS) suffix. To enable Server Administrator to send e-mails, you must type
the IP address and DNS suffix for the SMTP Server for your
company or organization in the
appropriate fields.
NOTE: For security reasons, your company
or organization might not allow e-mails to be sent through the SMTP server
to outside accounts.
The Command Log Size field specifies the largest file size in MB
for the command log file.
The Support Link field specifies the URL for the business
entity that provides support for your managed node system.
When you finish setting options in the Server Preferences window, click Apply Changes.
Perform the following steps to set up your Server Administrator user
preferences:
Click System�> Software�> Server Administrator.
To add a preselected e-mail recipient, type the e-mail address of your designated service contact in the Mail
To: field, and click Apply Changes.
Clicking Email in any window sends an e-mail message
with an attached HTML file of the window to the designated e-mail address.
To change the Server Administrator home page appearance, select an
alternative value in the skin or scheme fields and click Apply Changes.
Web certificates are necessary to ensure the identity of a remote system and
ensure that information exchanged with the remote system cannot be viewed or
changed by others. To ensure system security for Server
Administrator, it is strongly recommended that you either generate a new X.509
certificate, reuse an existing X.509 certificate, or import a root certificate
or certificate chain from a Certification Authority (CA).
NOTE: You must be logged in with Admin privileges to
perform certificate management.
To manage X.509 certificates through the Server Administrator home page, click
System�> Software�> Server Administrator, and
click the
Web Server tab. Use
the Server Administrator X.509 certificate tool to either generate a new X.509
certificate, reuse an existing X.509 certificate, or import a root certificate
or certificate chain from a CA. Authorized CAs include Verisign, Entrust, and
Thawte.
NOTE: Systems running supported Novell� NetWare�
operating systems must have Novell Java virtual machine (JVM) for NetWare version 1.2 or later to
perform certificate management through the Server Administrator home page. Novell JVM
for NetWare version 1.2 or later
is installed as part of the NetWare 6.0 or later operating system
installation. See the Novell website at www.novell.com
for information about upgrading to Novell JVM for NetWare version 1.2 or
later.
Exceptions for Systems Running Supported Novell NetWare Operating Systems
The X.509 Certificates cannot be managed through the Server Administrator home page
for systems running NetWare 5.1 with a version of Novell JVM for NetWare that
is earlier than 1.2. You must
perform certificate management with the Novell Certificate Server using
ConsoleOne running on a NetWare client system if your managed node system uses a version of Novell JVM
for NetWare that is earlier than 1.2. By default, ConsoleOne is
located in the mapped public directory of a NetWare client system.
NOTE: Novell Certificate Server cannot be managed
using ConsoleOne running on a NetWare server console.
Using ConsoleOne, you can create or recreate an server
certificate if yours becomes corrupted.
NOTE: Back up your critical
server certificate information before beginning the following procedures.
Creating a New Server Certificate Signed by the NDS Organizational CA
Log in with Admin privileges to a NetWare client system and map a drive to the sys:\public
directory on the managed node system.
Double-click ConsoleOne.
Right-click the container object that contains the system to be managed with
Server Administrator, select New, and click
Object.
The New Object window appears.
Select NDSPKI: Key Material and click OK.
The Create Server Certificate (KeyMaterial) window appears. The Standard
creation method is selected by default.
Type the Certificate name and click Next.
Click Finish.
Edit the sys:\system\dell\omanage\IWS\config\server_properties.ini
and sys:\system\dell\omanage\IWS\config\client_properties.ini files by editing the
following line:
nssl.keystore = certificate name - hostname
where certificate name is the name of the certificate you just
created and hostname is the name of the managed node system running
NetWare.
The Certificate window appears. A white cross in a red circle
appears over the certificate icon at the top of the window. This icon
indicates that the certificate cannot be verified to a trusted certificate
authority.
Click the Certification Path tab.
Select Organizational CA and click View Certificate.
Information about the organizational CA is displayed.
Click Install Certificate.
The Certificate Manager Import Wizard appears.
Click Next.
Automatically select the certificate store based on
the type of certificate is selected by default.
Click Next.
Click Finish to complete the Certificate Manager Import Wizard.
The Root Certificate Store window appears.
Click Yes.
A window informs you that the import was successful.
Click OK.
The Java plug-in will now recognize the certificate as valid.
The Server Administrator Log in window appears with a yellow
lock (in the locked position) at the bottom corner of the window.
Creating a New Server Certificate Signed by an External Organizational
Authority
Log in with administrator privileges to a client system and map a
drive to the sys:\public directory on the managed node system.
Double-click ConsoleOne.
Right-click the container object that contains the system to be managed with
Server Administrator, select New, and click
Object.
The New Object window appears.
Select NDSPKI: Key Material and click OK.
The Create Server Certificate window appears. The Standard
creation method is selected by default.
Select the Custom creation method, type the Certificate name, and click Next.
Click External Certificate Authority and click Next.
Select the RSA key size and click Next.
Type the Subject Name, choose the signature algorithm, and click Next
(by
default, the signature algorithm is set to RSA Encryption with SHA-1 hash).
ConsoleOne generates a Certificate Signing Request (CSR).
Click Finish.
The Save Certificate Signing Request window appears.
Save the CSR.
Send the CSR to a trusted CA such as Verisign,
Thawte, or Entrust.
The CA returns two files: one is the root certificate and the other is a response
in a Public Key Cryptography Standard #7 (PKCS#7) format.
Right-click the certificate you named in step 5 and click Properties.
Click Import.
Paste the trusted root certificate
in the edit box and click Next.
Paste the response in the edit box and click Next.
Edit the sys:\system\dell\omanage\IWS\config\server_properties.ini
and the sys:\system\dell\omanage\IWS\config\client_properties.ini files
by editing the following line:
nssl.keystore = certificate name - hostname
where certificate name is the name of the certificate you just
created and hostname is the name of the managed node system running Novell
NetWare.
The next time you log into Server Administrator, the Java plug-in recognizes the certificate as signed by an external
trusted certificate authority.
Server Administrator automatically starts each time you reboot the managed
node system. To manually start, stop, or restart Server Administrator, use the
following instructions.
NOTE: To control Server Administrator, you
must be logged in with administrator
privileges (logged in as root for supported Red Hat Linux operating systems).
Starting Server Administrator
Supported Microsoft� Windows� Operating Systems
To start Server Administrator on systems running a supported Windows 2000 operating
system, perform the following steps:
Click the Start button and point to Settings�> Control
Panel�> Administrative Tools�> Services.
The Services window appears.
Right-click the Server Administrator icon.
Click Start.
To start Server Administrator on systems running a supported Windows NT� operating
system, perform the following steps:
Click the Start button and point to Settings�> Control
Panel�> Services.
The Services window appears.
Right-click the Server Administrator icon.
Click Start.
Supported Red Hat Linux Operating Systems
To start Server Administrator on systems running a supported Red Hat Linux operating
system,
run the following command from the command line:
omawsd start
Supported Novell NetWare Operating Systems
To start Server Administrator on systems running a supported Novell NetWare operating
system,
run the following command from the command line:
Dell/omanage/IWS/bin/netware/omastart
Stopping Server Administrator
Supported Microsoft Windows Operating Systems
To stop Server Administrator on systems running a supported Windows 2000 operating
system, perform the following steps:
Click the Start button and point to Settings�> Control
Panel�> Administrative Tools�> Services.
The Services window appears.
Right-click the Server Administrator icon.
Click Stop.
To stop Server Administrator on systems running a supported Windows NT operating
system, perform the following steps:
Click the Start button and point to Settings�> Control
Panel�> Services.
The Services window appears.
Right-click the Server Administrator icon.
Click Stop.
Supported Red Hat Linux Operating Systems
To stop Server Administrator on systems running a supported Red Hat Linux operating
system,
run the following command from the command line:
omawsd stop
Supported Novell NetWare Operating Systems
To stop Server Administrator on systems running a supported Novell NetWare operating
system,
run the following command from the command line:
Dell/omanage/IWS/bin/netware/omastop
Restarting Server Administrator
Supported Microsoft Windows Operating Systems
To restart Server Administrator on systems running a supported Windows 2000 operating
system, perform the following steps:
Click the Start button and point to Settings�> Control
Panel�> Administrative Tools�> Services.
The Services window appears.
Right-click the Server Administrator icon.
Click Restart.
To restart Server Administrator on systems running a supported Windows NT operating
system, perform the following steps:
Click the Start button and point to Settings�> Control
Panel�> Services.
The Services window appears.
Right-click the Server Administrator icon.
Click Restart.
Supported Red Hat Linux Operating Systems
To restart Server Administrator on systems running a supported Red Hat Linux operating
system,
run the following command from the command line:
omawsd restart
Supported Novell NetWare Operating Systems
To restart Server Administrator on systems running a supported Novell NetWare operating
system,
run the following command from the command line:
) to the left of an object, or double-click the object. A minus sign ( 
)indicates an expanded entry
that cannot be expanded further.
