ServerConductor/Blade Server Manager Description and Reference

[Contents][Glossary][Index][Back][Next]

Preface

This manual describes the functions of the following program products and explains how to use them:

Unless otherwise required, these products are referred to collectively as ServerConductor.

Intended readers

This manual is intended for system administrators who use ServerConductor to operate and manage host systems. The manual assumes that the user has a basic knowledge of Windows XP, Windows Server 2003, or Linux, and of the Web.

Organization of this manual

This manual consists of the following chapters and appendixes:

1. Overview
Chapter 1 provides an overview of ServerConductor and describes its system configuration.

2. System Configuration
Chapter 2 uses several example configurations to describe the information that is needed to build a ServerConductor system.

3. Setup
Chapter 3 describes how to install and set up ServerConductor.

4. Operation of the Console Service
Chapter 4 explains the basics of how to start, stop, and operate the console service, which is ServerConductor's operation program.

5. Asset Management
Chapter 5 describes how to use ServerConductor to manage assets and describes the inventory information that can be managed.

6. Failure Management
Chapter 6 describes the functions for viewing and reporting alerts, which are used to manage failures that may occur in a ServerConductor system.

7. Power Control
Chapter 7 describes the methods and types of power control supported by ServerConductor.

8. Remote Control
Chapter 8 describes how to set up and use remote control in ServerConductor.

9. Group Management
Chapter 9 describes how to use ServerConductor to set up and manage hosts in groups.

10. Connection Management
Chapter 10 describes how to use ServerConductor to manage system connections.

11. Changing environment settings
Chapter 11 describes how to change settings from ServerConductor's console service.

12. Program Linkage
Chapter 12 describes how to start external programs to which ServerConductor may be linked.

13. SNMP Translator
Chapter 13 describes the features that enable you to use an SNMP manager to view information managed by ServerConductor.

14. Usage Notes
Chapter 14 provides notes about using ServerConductor.

15. Operating the WEB Management Console
Chapter 15 describes how to operate the WEB management console, which is ServerConductor's operating program.

A. Messages
Appendix A describes the messages that are issued by ServerConductor.

B. List of Alerts
Appendix B describes the alerts that are issued by ServerConductor.

C. Inventory Information
Appendix C describes the inventory information that can be managed by ServerConductor.

D. Glossary
Appendix D defines terms used in this manual.

Conventions: Abbreviations

This manual uses the following abbreviations for product names:

Abbreviation Full name or meaning
Agent ServerConductor/Agent
BSM ServerConductor/Blade Server Manager
Linux A generic term for:
  • Red Hat Linux
  • Red Hat Enterprise Linux AS 4
Microsoft Access Microsoft Access(R)
Microsoft Internet Explorer Microsoft(R) Internet Explorer
Windows A generic term for:
  • Windows XP
  • Windows Server 2003
Windows XP Windows XP Professional
Windows XP Professional Microsoft(R) Windows(R) XP Professional
Operating System
Windows Server 2003 A generic term for the following:
  • 32-bit Windows Server 2003
  • Windows Server 2003 (IPF)
Windows Server 2003 Standard Edition Microsoft(R) Windows Server(TM) 2003, Standard Edition Operating System
Windows Server 2003 Enterprise Edition Microsoft(R) Windows Server(TM) 2003, Enterprise Edition Operating System
Windows Server 2003 Datacenter Edition Microsoft(R) Windows Server(TM) 2003, Datacenter Edition Operating System
Windows Server 2003 (IPF) Microsoft(R) Windows Server(TM) 2003 Enterprise Edition for Itanium-Based Systems

This manual also uses the following abbreviations:

Abbreviation Full name or meaning
API Application Program Interface
BIOS Basic Input Output System
BMC Baseboard Management Controller
CSV Comma Separated Value
DHCP Dynamic Host Configuration Protocol
DLL Dynamic Link Library
DMA Direct Memory Access
DSN Data Source Name
ECC Error Correcting Code
FAT File Allocation Tables
IPF Itanium Processor Family
IRQ Interrupt Request
JDK Java Development Kit
LAN Local Area Network
MIB Management Information Base
NTFS NT File System
ODBC Open DataBase Connectivity
OS Operating System
PC Personal Computer
PCI Peripheral Component Interconnect
RAS Reliability, Availability and Serviceability
RAS Remote Access Service
RPM Red Hat Package Manager
SCSI Small Computer System Interface
SNMP Simple Network Management Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
UPS Uninterruptible Power Supply
URL Uniform Resource Locator

Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

Conventions: Fonts and symbols

Font and symbol conventions are classified as:

These conventions are described below.

General font conventions

The following table lists the general font conventions:

Font Convention
Bold Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example, bold is used in sentences such as the following:
  • From the File menu, choose Open.
  • Click the Cancel button.
  • In the Enter name entry box, type your name.
Italics Italics are used to indicate a placeholder for some actual text provided by the user or system. Italics are also used for emphasis. For example:
  • Write the command as follows:
    copy source-file target-file
  • Do not delete the configuration file.
Code font A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
  • At the prompt, enter dir.
  • Use the send command to send mail.
  • The following message is displayed:
    The password is incorrect.

Examples of coding and messages appear as follows (although there may be some exceptions, such as when coding is included in a diagram):

MakeDatabase
...
StoreDatabase temp DB32

In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes of brevity.

Conventions in syntax explanations

Syntax definitions appear as follows:

StoreDatabase [temp|perm] (database-name ...)

The following table lists the conventions used in syntax explanations:

Example font or symbol Convention
StoreDatabase Code-font characters must be entered exactly as shown.
database-name This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
SD Bold code-font characters indicate the abbreviation for a command.
perm Underlined characters indicate the default value.
[ ] Square brackets enclose an item or set of items whose specification is optional.

Ex: [-snmp]
This means you may specify or omit -snmp.
| Only one of the options separated by a vertical bar can be specified at the same time.

Ex.: -adagent|-load|-snmp
This means you may select any one of the options -adagent, -load, or -snmp.
... An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ] immediately preceding the ellipsis may be specified as many times as necessary.
() Parentheses indicate the range of items to which the vertical bar (|) or ellipsis (...) is applicable.

Conventions: KB, MB, GB and TB

This manual uses the following conventions: