HP Integrity rx4610 User manual

Intel®Server Control
User’s Guide
Version 4.0
Printed in June 2001

ii
Notice
The information contained in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-
Packard shall not be liable for errors contained herein or for incidental or consequential damages in
connection with the furnishing, performance, or use of this material.
This guide has been reprinted with the permission of Intel Corporation. Hewlett-Packard assumes no
responsibility for the use or reliability of this software on equipment that is not furnished by Hewlett-Packard.
Information in this document is provided in connection with Intel®products. No license, express or implied,
by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided
in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel
disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or
warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent,
copyright or other intellectual property right. Intel products are not designed, intended or authorized for use
in any medical, life saving, or life sustaining applications or for any other application in which the failure of
the Intel product could create a situation where personal injury or death may occur. Intel may make changes
to specifications and product descriptions at any time, without notice. No part of this document may be
copied or reproduced in any form or by any means without prior consent of Intel.
This document contains proprietary information that is protected by copyright. All rights are reserved. No
part of this document may be photocopied, reproduced, or translated to another language without the prior
written consent of Hewlett-Packard Company.
Intel, Pentium, and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in
the United States and other countries.
†All other brand and product names are trademarks of, and are used to identify products of, their respective
owners.
Hewlett-Packard Company
Network Server Division
Technical Communications/ MS 45SLE
10955 Tantau Avenue
Cupertino, California 95014 USA
© Copyright 2001, Hewlett-Packard Company.
Audience Assumptions
This guide is for the person who installs, administers, and troubleshoots LAN servers. Hewlett-Packard
Company assumes you are qualified in the servicing of computer equipment and trained in recognizing
hazards in products with hazardous energy levels.

iii
Contents
1About Intel®Server Control..................................................................................................................1
Introducing Intel Server Control ................................................................................................................1
2Finding the Right Tool ...........................................................................................................................3
3Managing Remote Servers ....................................................................................................................5
Server Management Basics ......................................................................................................................5
Server Management Tools........................................................................................................................5
Platform Instrumentation Control ..........................................................................................................5
Direct Platform Control..........................................................................................................................8
Server Management Configuration (SM Config) Utility.........................................................................9
Service Partition on Itanium-Based Platforms ......................................................................................9
Remote Diagnostic Tests....................................................................................................................10
LAN-Alert Manager and Viewer ..........................................................................................................10
Management Consoles ...........................................................................................................................11
Server Management Consoles ...........................................................................................................11
Enterprise System Management Consoles ........................................................................................11
4Connecting to a Remote Server ..........................................................................................................13
Telephone ...............................................................................................................................................13
From the Console ...............................................................................................................................13
From the Remote Server ....................................................................................................................13
Setting Up a Telephone Connection...................................................................................................13
LAN .........................................................................................................................................................14
ICMB .......................................................................................................................................................14
Setting Up an ICMB Connection.........................................................................................................14
Direct (COM 2) ........................................................................................................................................14
Setting Up a Direct Connection ..........................................................................................................14
5Paging an Administrator......................................................................................................................15
Platform Event Paging (PEP)..................................................................................................................15
Server Event Notifications.......................................................................................................................15
6Using the Stand-alone ISC Console ...................................................................................................17
Launching ISC.........................................................................................................................................17
ESMC..................................................................................................................................................17
Programs Menu ..................................................................................................................................17
ActiveX Containers .............................................................................................................................17
Stand-alone ISC Console Controls .........................................................................................................18
Stand-alone ISC Console Main Screen ..............................................................................................19
Stand-alone ISC Console Button Bar .................................................................................................19
Server Menu Options ..........................................................................................................................20
View Menu Options.............................................................................................................................21
The Navigation Pane...............................................................................................................................21
The Tool Pane.........................................................................................................................................21
The Status Bar ........................................................................................................................................21

1
1 About Intel®Server Control
Introducing Intel Server Control
Intel®Server Control (ISC) is a software package that provides tools to manage remote servers. ISC is
installed and runs on a client-server architecture. The parts of ISC that run on the client workstation are
referred to as console software. The parts that run on the servers are referred to as instrumentation software
(platform instrumentation).
NOTE This section describes the Intel Server Control (ISC) server-management software
package. Refer to the section titled “Using the Intel Server Control Console” if you are
looking for information about using the ISC Console.
Intel Server Control consists of several components. Depending on the server platform on which you are
going to install and use ISC components, various features can be available. For information on what features
of ISC are available given specific server platforms, refer to Error! Reference source not found. on page
Error! Bookmark not defined..
The following list presents an overview of the ISC components:
Intel Server Control Console: The Intel Server Control Console is a management console that provides
basic server management functions. The console allows you to perform the following:
• In-band monitoring of servers (servers that are up and running) through a component called Platform
Instrumentation Control (PIC).
• Out-of-band monitoring of servers (those that are not up and running or in an unknown state) through a
component called Direct Platform Control (DPC).
• Run diagnostic tests that are specific to the server platform through a component called Remote
Diagnostic Tests.
The ISC Console can run by itself, within a web browser, or under Microsoft Management Console (MMC).
The ISC Console provides you with the ability to discover servers with ISC management tools.
Installing any single component of ISC causes the ISC Console to also be installed. For information on how
to install ISC, refer to the Installation Guide for the Intel Server Control.
The following list provides an overview of the ISC components. For more detailed information on each
component, refer to the appropriate sections later in this manual.
Platform Instrumentation Control (PIC): Platform Instrumentation Control (PIC) provides real-time
monitoring and alerting for server hardware sensors. This type of monitoring is known as in-band
monitoring; the managed server is up and running. PIC communicates via a LAN connection to the Platform
Instrumentation (PI) software on the managed server using standard DMI/RPC (non-Itanium™-based
servers) or CIM/DCOM protocols (Itanium-based servers).
See “Platform Instrumentation Control” for summary information. You can also click the Help button in the
PIC Console for detailed information.
Direct Platform Control: DPC is a server management tool that gives you access to a remote managed
server when it is online or offline, when the operating system is hung, or when it’s powered off. This kind of
monitoring is known as out-of-band monitoring. When you receive notice that a server has malfunctioned
(via a page, for example), you can use DPC to investigate the cause of the alert, to initiate corrective action,
and to restart the server into normal operation.
DPC communicates with the Emergency Management Port (EMP) on the server. The access path is through
a serial (modem or a direct connection using a null-modem cable) or LAN connection.

Chapter 1 About Intel® Server Control
2
Remote Diagnostic Tests: These tests consist of Modular Test Architecture (MTA) diagnostic tests that
when run allow you to quickly assess a server’s hardware status, view test logs, and determine the server’s
current configuration. You control the tests are controlled through a text-based console redirected to the
client workstation from DPC.
Refer to “Direct Platform Control” and “Remote Diagnostic Tests” for summary information. You can click
the Help button in the DPC Console for detailed information.
NOTE To remotely configure an Itanium™ - based server, use the Server Management
Configuration Utility (SM Config Utility). For an overview of this utility, refer to “Server
Management Configuration (SM Config) Utility” on page 9.
LAN-Alert Viewer and Manager: The LAN-Alert Manager sends and receives alerts over a LAN
connection as opposed to pages that are sent over a serial connection. The manager running on a server
executes as a service and sends out alerts packaged as SNMP traps using a UDP/IP protocol. The manager
running on a client decodes LAN alerts received from a managed server. The LAN-Alert Viewer is the user
interface running on a client that lets you monitor these types of alerts.
NOTE LAN-Alert Viewer and Manager is currently not supported. Please refer to the HP web
site at http://www.hp.com/ for the latest release.
LAN-Alert is a Java-based component that can run on Windows NT or Windows 2000 systems. LAN-Alert
cannot run locally on an Itanium-based platform. Refer to the help system that is part of LAN-Alert for more
information.

3
2 Finding the Right Tool
Table 1 provides a summary that can help you find the right tool to use for any server condition.
Table 1 Tool Summary
Managed Server Status Potential Remote Tasks Access Tools Available
The operating system is
running and the server is
online. Applications are also
running.
Update software
Shutdown
LAN/
POTS *
Platform Instrumentation
Control
Operating System is running
but the server is offline or
otherwise malfunctioning.
Inspect
Remedy
Restart
LAN/
Local
Platform Instrumentation
Control
The server runs its BIOS and
performs the Power On Self
Test successfully.
Redirect Console
Boot Service Partition
POTS * Direct Platform Control
Remote Diagnostic Tests
The server is off, hung, or
won't boot.
(Standby power enabled)
View history
Run hardware diagnostics
Update drivers
Examine state
Restart
POTS * Direct Platform Control
Remote Diagnostic Tests
* POTS stands for "Plain Old Telephone Service."

5
3 Managing Remote Servers
Server Management Basics
The Intel Server Control components provide a means to communicate with a managed server, and to
perform administrative and troubleshooting tasks from a remote client.
Table 2 shows the typical tasks that a system administrator might do. They include normal system
administration, setting up system alerts so that an administrator is notified when something on the server
needs attention, and acting in response to server alerts or errors.
Table 2 System Administrator Tasks
Administer • Monitor system status
• Track system history
• Manage system assets
Alert • Configure sensor thresholds
• Configure alert actions
• Respond to alerts received from the managed server
• Configure Predictive Failure Notification
Act • Restore the server
• Diagnose the server
• Update the server
• Configure the server
• Repair the server
The following sections under “Server Management Tools” describe the tools used for the various server
management tasks. Refer to “Management Consoles” later in this chapter for a description of the available
management consoles. The section titled “Connecting to a Remote Server” describes the different methods
for communicating with a managed server.
Server Management Tools
Several tools exist for server management, each for a different purpose or for use in a different condition.
Tools are sometimes used together, or in sequence, to perform server management tasks.
The available tools for remote server management, described in the following paragraphs, include:
• Platform Instrumentation Control
• Direct Platform Control
• Server Management Configuration Utility
• Service Partition
• Remote Diagnostic Tests
• LAN-Alert
Platform Instrumentation Control
Platform Instrumentation Control (PIC) runs on platforms whose operating systems include Microsoft
Windows 2000†with Service Pack 2. PIC provides real-time monitoring and alerting for server hardware
sensors. PIC communicates via a LAN connection to the Platform Instrumentation (PI) on the Server using
standard DMI/RPC (non-Itanium-based servers) and CIM/DCOM protocols (Itanium-based servers).

Chapter 3 Managing Remote Servers
6
ISC installs Platform Instrumentation on the managed server and console software on a client workstation. It
is also possible to install Platform Instrumentation on multiple servers and console software on multiple
clients. For information on console and managed server system requirements, refer to the Installation Guide
for the Intel Server Control.
PIC integrates into the enterprise and workgroup management consoles, as well as into the Intel Server
Control (ISC) Console. PIC relies on the management console to discover servers over the LAN. It also
forwards changes in the server state to the management consoles for appropriate alert handling.
NOTE Itanium-based platforms running Windows 64-bit Advanced Server not support the
integration of either the Hewlett Packard OpenView Network Node Manager Console or
the Computer Associates Unicenter The Next Generation.
What is Platform Instrumentation?
Platform Instrumentation consists of the server-resident software used to monitor and control the server when
the operating system is online. The instrumentation retrieves data from the operating system as well as from
the Platform Management Technology (hardware, firmware and BIOS), and communicates with management
tools with Desktop Management Interface 2.0 (DMI 2.0) commands (non-Itanium-based servers) or the
CIM/DCOM protocol (Itanium-based servers).
Platform Instrumentation also provides instrumentation data for the servers connected through the Intelligent
Chassis Management Bus (ICMB). This allows PIC to use the Platform Instrumentation on one server to
access the Platform Management Technology on another server/chassis. This is useful when the target server
is not fully operational (such as when the operating system is down) and cannot be reached directly by the
PIC, or when the target server is running an operating system that is not supported by the Platform
Instrumentation.
Any change in the server state generates an Event Indication. A Local Response Agent responds by taking
actions such as:
• Powering off the server
• Resetting the server
• Shutting down the server
• Generating an NMI/SDI
• Beeping the system speaker
• Logging to a disk
• Broadcasting a message on the network
• Displaying a message on the system console
• Paging the administrator.
You can use Platform Instrumentation Control from the client to:
• View consolidated server health information
• Manage non-Intel®-based systems via the Intelligent Chassis Management Bus (ICMB)
• Remotely monitor server hardware sensors
• Configure sensor thresholds
• Update the server’s LCD display (if available)
• Configure, receive, and act upon alert events in the system event log (SEL)
• Configure audio or visual notifications in response to an event
• Configure options to shut down, reboot, or power-off the system automatically in response to an event

Chapter 3 Managing Remote Servers
7
• View system event log, system hardware inventory, BIOS and system slot information. If they are
implemented on the server, you can also view SCSI controller status and LAN adapter status.
You can also use PIC to track system status and manage hardware conditions, such as:
• Temperature
• Voltage
• Cooling fan status
• Chassis intrusion
• ECC memory
• Processor status
• Power supply status
Launching Platform Instrumentation Control as a Stand-alone Application
To launch Platform Instrumentation Control as a stand-alone application from a Windows-based client,
follow these steps:
1. Click on the Start menu.
2. Select Programs.
3. Select Intel Server Control.
4. Select ISC Console. This action causes the ISC Console to launch. You can launch ISC tools, such as
PIC, from the ISC Console.
5. From the ISC Console either discover the server you want to manage or add the server. For information
on how to discover or add servers using the ISC Console, refer to the section titled “Server Menu
Option” that appears later in this manual. Discovering or adding a server causes icons for applicable
ISC tools to appear in the right pane of the ISC Control. If the managed server has Platform
Instrumentation software installed, the icon for PIC appears.
6. Double-click the PIC icon. This action causes the PIC login screen for the managed server to appear.
7. Enter your username and password and click OK.
For information on how to use the DMI-based PIC, refer to the Intel®Platform Instrumentation Control
Console User’s Guide. For information on how to use the Java-based PIC, refer to the online help system.
Launching Platform Instrumentation Control from
Within a Supported Enterprise System Management Console (ESMC)
To launch Platform Instrumentation Control from within an ESMC, follow these steps:
1. Be sure that a supported ESMC is running on the client. For information on supported ESMCs, refer to
the section titled “Enterprise System Management Consoles.”
2. Locate the icon in the ESMC that represents the managed server to which you want to connect.
3. Click on the icon. This action reveals a menu of available ISC tools.
4. Click Intel, Platform Instrumentation Control to launch PIC.
5. Enter your username and password and click OK.
For information on how to use the DMI-based PIC, refer to the Intel Platform Instrumentation Control
Console User’s Guide. For information on how to use the Java-based PIC, refer to the online help system.
Launching the Java-based Platform
Instrumentation Control as an Applet from Within a Web Browser
To launch the Java-based Platform Instrumentation Control (PIC that uses the CIM/DCOM protocol) as an
applet from within a Web browser, you must already have a Web server running on an IA-32 platform. The
server can be either a Microsoft IIS or Apache Web server. The following steps show you how to setup PIC

Chapter 3 Managing Remote Servers
8
on an existing Microsoft IIS Web server. Information on how to setup a Web server itself is beyond the
scope of this document.
1. Create a folder named “pic40” under the folder “Inetpub\wwwroot.”
2. Copy the following files from the Resource CD to the folder you created in the previous step.
oSWebconsole.jar – a signed JAR file containing all the code to run PIC
oJh.jar – the JAR file containing the JAVA help classes
oWpic.htm – the main file that launches PIC as an applet
oApplet.htm – a sample HTML file showing how to launch PIC
oWpiccert.cer – The certificate required to run the signed applet
3. Keep or modify the applet.htm file. This file contains a hyperlink that opens Wpic.htm in a new
window. To see how the hyperlink is created, examine the HTML in the file.
After configuring the Web server, you must perform these next steps on all client machines that will be
launching PIC.
1. Copy the file WMIwrap.dll from the Resource CD to the “c:\windows\system32” or
“c:\windows\WinNT” folder on the client system. If the client has had ISC installed on it, this folder
should already have the WMIwrap.dll file.
2. Download the certificate file Wpiccert.cer from the Web server to any folder on the client hard
drive. You can do this by opening the the applet.htm file located on the Web server and right-
clicking on the “certificate” link. Once you right-click on the link, perform a Save As operation to
copy the file anywhere on the client’s local hard drive. Be sure that you save the file with the .cer
extension.
3. Double-click on the certificate file you just saved and follow the installation instructions.
4. Launch a Web browser.
5. Launch PIC by going to the URL “http://<web_server_name>/pic40/applet.htm”, where
<web_server_name> is the name of the Web server you configured earlier.
For information on how to use the Java-based PIC, refer to the online help system.
Direct Platform Control
Direct Platform Control is a server management tool that gives you access to a managed server when it is
online or offline, when the operating system is hung, or when it’s powered off. When you receive notice
(through a page, for example) that a server has malfunctioned you can use DPC to investigate the cause of the
alert, to initiate corrective action, and to restart the server into normal operation.
DPC communicates with the Emergency Management Port (EMP) on the server. The access path is serial
(modem or by way of a direct serial connection). DPC also works through a redirected text-based console.
Since DPC does not communicate with the server-resident operating system, it can be used to manage the
server even if the server's operating system and primary processors are not working. Because the server's
emergency management hardware works on 5V standby power, DPC can be used to communicate with and
control a powered down server; the server just needs to be plugged into the proper power receptacles.
DPC integrates into a variety of management consoles, as well as the ISC Console. DPC relies on the
management console or the ISC Console to discover managed servers over the LAN.
Using DPC, you can do the following to a managed server:
• Establish or end a connection
• Power on
• Power off
• Perform a reset operation

Chapter 3 Managing Remote Servers
9
• Reboot the server to its service partition
• View the System Event Log (SEL) for information about recent server activity
• View Sensor Data Records (SDRs) for information about sensor characteristics
• Review Field Replaceable Unit (FRU) inventories
• View Remote Sensor Access (RSA) information
• Maintain a Phonebook for managed servers
• Run Remote Diagnostic Tests on a managed server
• Transfer files to and from the server
• Run the server’s shell program
• Run service partition-based programs on the server
For more information on how to launch and run the DPC, refer to the Intel Direct Platform Control Console
User’s Guide.
Server Management Configuration (SM Config) Utility
The SM Config Utility resides as an Extensible Firmware Interface (EFI) executable on the service partition
of an Itanium™ - based server. You can run this utility locally or remotely through the Direct Platform
Control (DPC) Console. Running the utility allows you to locally configure an Itanium-based server. Using
this utility you can set up the connection parameters needed between the server and the client workstation
running console software.
With the SM Config Utility you can do the following:
• Configure the Emergency Management Port (EMP) for remote server management over a modem or
direct serial connection.
• Configure the Direct Platform Control over LAN feature (DPC\LAN) for remote server management
over the network.
• Configure power restoration policies when the system loses AC power.
• Set the accelerated cool-down timeout.
• Set the Fault Resilient Boot (FRB) timeout.
• Configure the Advanced Configuration and Power Interface (ACPI) features.
• Enable or disable Platform Event Filtering (PEF) and Platform Event Paging (PEP).
For procedures on how to configure both serial and LAN connections between an Itanium-based server and
client workstations, refer to the Intel Direct Platform Control Console User’s Guide. For information on how
to launch the SM Config Utility locally on the server and for information on how to use the utility, refer to the
server’s product guide.
Refer to the managed servers product guide for more information on the SM Config Utility. You can also
refer to the Intel®Direct Platform Control Console User’s Guide for information on how to configure an
Itanium-based server for communication with DPC.
Service Partition on Itanium-Based Platforms
The service partition on an Itanium-based platform is also referred to as the Extensible Firmware Interface
(EFI) System Partition. This partition is not a separate, dedicated partition as is its functional counterpart on
an IA-32 platform. The presence of “service partition” files within the existing system partition defines the
EFI System Partition (service partition).
The service partition is established when the installation program copies service partition files into the
existing system partition. These files include utilities, diagnostics, and other software required for remote
management. You can run the utilities and diagnostics located on the service partition either locally or
remotely. In order to run the utilities and diagnostics you must boot the server from the service partition.

Chapter 3 Managing Remote Servers
10
Remote execution is available from the Direct Platform Control (DPC) Console Manager. Applications that
execute in the service partition run only on the managed server.
For information on how to install the service partition files, refer to the Installation Guide for the Intel Server
Control.
Remote Diagnostic Tests
Remote Diagnostics Tests allow you to quickly assess the server’s hardware status, view test logs, and
determine the server’s current configuration. These tests reside on the server’s service partition. On Itanium-
based platforms, Remote Diagnostics Tests are available as an Extensible Firmware Interface (EFI)
application.
You can run Remote Diagnostics Tests remotely by connecting to the server with DPC and then rebooting to
the service partition. After the server reboots, the remote diagnostics become available and you can use them
for testing server hardware.
For more information on how to run Remote Diagnostics Tests from DPC, refer to the Intel Direct Platform
Control Console User’s Guide.
LAN-Alert Manager and Viewer
The LAN-Alert feature enables a server to proactively alert administrators of critical system failures and state
changes regardless of the state of the server’s operating system or the server’s management software.
NOTE Itanium-based platforms running Windows 64-bit Advanced Server not support execution
of the LAN-Alert component. LAN-Alert executes only on systems running the Windows
NT or Windows 2000 operating system.
LAN-Alert Manager
The LAN-Alert Manager, when executing on a server, interfaces with the Baseboard Management Controller
(BMC) to create SNMP traps and send them out over the LAN using a UDP/IP protocol. When the manager
executes on a client that is monitoring servers, the manager senses and decodes these traps for viewing by the
LAN-Alert Viewer.
With the LAN-Alert feature you can detect and sense the following:
• Temperature Sensor out of range
• Voltage Sensor out of range
• Chassis Intrusion (Security Violation)
• Power Supply Fault
• BIOS: Uncorrectable ECC error
• BIOS: POST Error Code
• Boot Failures
• Fatal MCA
• Watchdog Timer reset, power down, or power cycle
• System restart (reboot)
• Fan failures
The server’s BIOS setup lets you configure the following:
• The trap destination as a specific IP address or an address of a specific IP subnet.
• The Host IP Configuration data such as the IP address, default gateway, and subnet mask
• The Platform GUID

Chapter 3 Managing Remote Servers
11
• Alert event filters.
LAN-Alert Viewer
The LAN-Alert Viewer is a Java-based console that provides the capability to manage LAN Alerts. The
viewer presents information regarding:
• Server IP
• Sensor Info
• Event Info
• Sensor Device
• Sensor Number
• Event Severity
The Alert Viewer supports the following actions:
• Configure—Allows you to configure different notification and viewer options.
• Acknowledge—Sets the selected alerts’ “status” to Acknowledge. This means you have seen and are
aware of the alert.
• Delete—Removes the selected alert from the list of alerts.
• Close—Closes the viewer.
• Select All—Selects all alerts, for performing actions on all alerts.
• View Details—Launches the detailed view of the selected alert(s).
For information on how to use the LAN-Alert feature, refer to the online help system installed as part of the
component.
Management Consoles
Server management tools such as Platform Instrumentation Control, Direct Platform Control, and the Client
System Setup Utility run as components within a server management console. Server management consoles
provide the basic functions of establishing connections with remote systems, displaying server or network
status, and launching the tool applications.
Server management consoles range from basic versions that are used with single servers to complex versions
that are used with complex enterprise-wide network systems.
Server Management Consoles
Server Managers are used in small-office environments to manage a single server or a small number of
servers. Server Managers provide the tools to find servers on a network (“discovery”), view multiple servers,
receive LAN-based alerts from the remote servers, and control the security of the server.
The Intel Server Control Console provides a straightforward and inexpensive Server Management Console
when used by itself, within an ActiveX-enabled web browser, or within Microsoft Management Console
(MMC).
Enterprise System Management Consoles
Enterprise System Management Consoles (ESMC) are used in an enterprise-wide environment to manage a
complex organization of networks. They can include performance monitoring, load balancing, optimization,
and traffic analysis.
Hewlett Packard OpenView Network Node Manager†and Computer Associates Unicenter The Next
Generation†are ESMCs that support ISC components. To use the ISC tool modules with an ESMC, select
the appropriate Integration Agent when you are installing the ISC software.

Chapter 3 Managing Remote Servers
12
NOTE Itanium-based platforms running Windows 64-bit Advanced Server not support the
integration of either the Hewlett Packard OpenView Network Node Manager Console or
the Computer Associates Unicenter The Next Generation.
Hewlett Packard OpenView Network Node Manager
The Hewlett Packard OpenView Network Node Manager Console automatically detects servers running the
ISC Platform Instrumentation software. ISC-enabled servers display on the network map, and an “Intel
Server Control” applet is added as an option in the Tools menu.
Computer Associates Unicenter The Next Generation
Computer Associates Unicenter The Next Generation automatically detects servers running the ISC Platform
Instrumentation software if the ISC to discovery service is enabled. The service can be started either from the
Auto Discovery dialog or from the Windows NT Services applet. The discovery service creates a new “Intel
Server Control” object for each ISC-enabled server. The ISC objects display under “ISC World View.”

13
4 Connecting to a Remote Server
You can connect to a managed server several ways. A key to effective management is to configure your
system with methods that allow you to communicate with the server during conditions that can range from
fully functional to powered-off states. The available connections are:
• Telephone (modem)
• Local Area Network (LAN)
• Intelligent Chassis Management Bus (ICMB)
• Local Direct (COM 2)
The connection methods are described in the following paragraphs.
Telephone
You can use a telephone/modem connection to communicate with a managed server.
A telephone connection is particularly useful when the managed server is not communicating with the local
area network, such as when the server is hung or powered-off.
Using a telephone line to connect to an unpowered server requires that a battery-backed-up management card
be installed in the server.
From the Console
With a modem installed in both the client console system and the remote server, you can connect to the server
using DPC or Client SSU. You can use Client SSU only if the managed server is not an Itanium-based
platform.
Using the modem connection through the Direct Platform Control (DPC), you can
• Reset the remote server's power
• Reboot the remote server using the service partition
NOTE Direct Platform Control is an optional application that might not be installed on this
system. Look for the DPC icon in the right-hand pane of the ISC Console. To install
DPC, rerun the installation program on the Resource CD-ROM and choose that
component during the installation process.
From the Remote Server
You can set up the managed server to send messages to your console through the telephone connection.
Setting Up a Telephone Connection
Using a telephone connection requires:
• A modem on both the managed server and the client workstation.
• A server with on-board emergency management features.
In order to use a telephone/modem link to a server, you must configure a serial connection on both the
managed server and the client workstation. For information on how to configure the serial link, refer to the
Intel Direct Platform Control Console User’s Guide.

Chapter 4 Connecting to a Remote Server
14
LAN
A more common method of communicating with a managed server is through a network connection. All of
the server-management tools work when connected through this type of connection.
In order to use a network connection, you must configure a LAN connection on both the managed server and
the client workstation. For information on how to configure the LAN connection, refer to the Intel Direct
Platform Control Console User’s Guide.
ICMB
You can use ICMB to communicate with platforms having operating systems or architectures that are not
otherwise supported by the server management tool applications.
Using the ICMB connection requires that you have a functioning LAN connection to a server that is
connected via ICMB to the managed server.
Setting Up an ICMB Connection
An ICMB connection requires:
• A managed server with an ICMB interface.
• A server with an ICMB interface, connected to the server management console.
See the Product Guide for the managed server for information about setting up an ICMB connection.
Direct (COM 2)
With a direct connection to the managed server via a serial link, you may monitor hardware components,
view the System Event Log (SEL), Sensor Data Records (SDR), and perform Remote Diagnostics Tests. On
servers running Windows NT, you can also use the DMI-based Platform Instrumentation Control to monitor
server health, configure alerts, set thresholds, and monitor the system logs.
Setting Up a Direct Connection
Setting up a direct connection between the client and the managed server is identical to setting up the
telephone/modem method described previously. Connect the managed server and the workstation client
using a null-modem serial cable.
Refer to the server’s product guide for the managed server for information about configuring the serial port.

15
5 Paging an Administrator
Platform Event Paging (PEP)
Platform Event Paging allows the managed server to alert a system administrator of critical system failures
and state changes, independent of the state of the operating system or server management software. Platform
Event Paging uses a numeric paging service through an external modem.
Platform Event Paging can generate pages during pre-boot and post-boot states—all that is required is that the
Baseboard Management Controller is functional and there is power to the system.
The managed server's BIOS setup provides a configuration for the paging string and event filters. The paging
string contains all the information to connect to the pager and the message to send. The Platform
Instrumentation Control tool also has a dialog for configuring the same paging string.
NOTE You must use the Server Management Configuration (SM Config) Utility to configure
PEP information on Itanium-based servers. For information on how to use SM Config,
refer to the server’s product guide.
When notified by a page, an administrator can use the server management tools to remotely view server
health/status, system logs, and current configuration; reconfigure, reset or power off /on the server; or execute
off-line diagnostics to further analyze the condition of the server. Pages can be configured for the following
events:
• Temperature Sensor out of range
• Voltage Sensor out of range
• Chassis Intrusion [Security Violation]
• Power Supply Fault
• BIOS: Uncorrectable ECC error
• BIOS: POST Error Code
• FRB Failures
• Fatal NMI/SDI (NMI/SDI from source other than Front Panel NMI/SDI or Uncorrectable ECC Error)
• Watchdog Timer reset, power down, or power cycle
• System restart (reboot)
• Fan failures
Server Event Notifications
The server's Local Response Agent can be configured to shut down a server, broadcast messages, make a
local alarm beep, send a page to an administrator, and other actions. Use the Platform Instrumentation
Control tool to configure an LRA page. See “What is Platform Instrumentation?” for more information.