PAN Manager Administrator's Guide

PAN Manager Administrator’s Guide
For BladeFrame® BF400 S2 and BladeFrame® BF200
Document Number 430-SB0084
August 2008
PM5.2_BF
Copyright
Copyright © 2008 Egenera, Inc. All rights reserved.
This document, and the product described in it, is furnished under license and may only be used in accordance
with the terms of such license. The content of this document is furnished for information purposes only and is
subject to change without notice.
Egenera, Egenera stylized logos, BladeFrame, BladeLatch, BladeMate, BladePlane, cBlade, Control Blade,
PAN Manager, pBlade, Processing Blade, sBlade, and Switch Blade are either registered trademarks or
trademarks of Egenera, Inc. in the United States and/or other countries.
PRIMERGY is a registered trademark of Fujitsu Siemens Computers.
AMD, AMD Opteron, and AMD Athlon are trademarks of Advanced Micro Devices, Inc..
EMC, CLARiiON, and Symmetrix are registered trademarks of EMC Corporation.
The IBM Developer Kit for Linux, Java 2 Technology Edition contains software which is copyright IBM
Corporation, Sun Microsystems Inc., Hewlett-Packard Co., and X Consortium.
Intel and Itanium are registered trademarks and Xeon is a trademark of the Intel Corporation in the United States
and other countries.
Sun, Sun Microsystems, the Sun Logo, Solaris, and the Java logo are trademarks or registered trademarks of
Sun Microsystems, Inc. in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries. The virtual VGA console uses Microsoft Terminal Services Advanced Client
(TSAC), which is a copyright of Microsoft Corporation.
MindTerm is copyright AppGate AB.
Nero is a trademark of Nero AG.
NetApp is a registered trademark and Network Appliance is a trademark of Network Appliance, Inc.
Oracle9i is a trademark of Oracle Corporation.
Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries.
SUSE is a registered trademark of SUSE LINUX Products GmbH, a Novell business.
VMware, Virtual SMP, and VMotion are registered trademarks or trademarks of VMware, Inc.
Xen, XenSource, XenServer, and XenEnterprise are either registered trademarks or trademarks of Citrix
Systems, Inc. in the United States and/or other countries.
All other company and product names are trademarks or registered trademarks of their respective holders.
Printed in the United States of America.
Egenera, Inc., 165 Forest Street, Marlboro, Massachusetts 01752.
Contents
Preface
Customer Support ..................................................................................................... xx
Document Conventions ............................................................................................ xx
Chapter 1: Getting Started with PAN Manager
About PAN Manager ............................................................................................... 1-2

PAN Manager Location.................................................................................... 1-2
Accessing PAN Manager ................................................................................. 1-2
Supported Browsers.......................................................................................... 1-2
The PAN Manager GUI .......................................................................................... 1-3

Documentation and Help .................................................................................. 1-3
Logging On to the GUI Initially ....................................................................... 1-3
Logging On to the GUI Subsequently .............................................................. 1-4
Part I: Creating a PAN
Chapter 2: Configuring the PAN Structure
Overview ................................................................................................................. 2-2
Naming the Platform ............................................................................................... 2-3

About the Platform Name................................................................................. 2-3
Naming Conventions ........................................................................................ 2-3
PM5.2_BF iii
Naming the Platform ........................................................................................ 2-3

About the Platform ID ...................................................................................... 2-4
Specifying the PAN Identification Attributes ......................................................... 2-5

About the PAN Identification Attributes.......................................................... 2-5
Editing the PAN General Information.............................................................. 2-5
Configuring the SMTP Server ................................................................................. 2-7
Specifying Default Boot and Root Disk Images ..................................................... 2-8

About Boot and Root Disk Images................................................................... 2-8
Setting the Default Boot Image ........................................................................ 2-9
Changing the System EVBS Image................................................................ 2-10
Setting the Default Root Disk Image.............................................................. 2-10
Activating Flow Control on the PAN .................................................................... 2-11

About Flow Control........................................................................................ 2-11
Activating Flow Control................................................................................. 2-12
Configuring Power Management .......................................................................... 2-13

Power Domains ............................................................................................. 2-13
Power Management ........................................................................................ 2-14
Configuring Power for Platforms Without PIM-Rs ....................................... 2-16
Configuring Power for Platforms with PIM-Rs ............................................. 2-16
Displaying Available Application Templates ....................................................... 2-18
Chapter 3: Configuring External Connectivity
Modifying Internal and External Management Settings ......................................... 3-3
Configuring Ethernet Interfaces .............................................................................. 3-5

About Ethernet Connections............................................................................. 3-5
Two Steps to Configure Ethernet Interfaces .................................................... 3-7
Checking or Naming Connectivity Setting....................................................... 3-7
Setting the Ping Mode Parameters ................................................................... 3-7
Configuring Redundant Ethernet Interfaces ............................................................ 3-8

About rEths....................................................................................................... 3-9
iv PM5.2_BF
Contents
About Ping Failover Detection Mode............................................................. 3-10

Two Steps to Configure a rEth ....................................................................... 3-11
Configuring a rEth.......................................................................................... 3-11
Activating Ping Failover Detection Mode on a rEth ...................................... 3-13
Creating vSwitches ................................................................................................ 3-13

About vSwitches............................................................................................. 3-13
vSwitch Uplinks ............................................................................................. 3-17
Creating a vSwitch ......................................................................................... 3-19
Chapter 4: Managing System Access
Establishing Access Control .................................................................................... 4-2
Creating Users and Accounts .................................................................................. 4-2

About Linux Accounts and PAN Manager Users ............................................ 4-2
About Authentication ....................................................................................... 4-4
Creating Users and Accounts ........................................................................... 4-4
Creating User Groups ....................................................................................... 4-5
Disabling Linux Account Management............................................................ 4-5
Enabling Linux Account Management............................................................. 4-6
Assigning Roles to PAN Manager Users ................................................................ 4-6

About Administrative Domains........................................................................ 4-6
About User Roles ............................................................................................. 4-7
About Permissions............................................................................................ 4-8
Guidelines for Assigning Roles........................................................................ 4-8
Assigning Roles to Users.................................................................................. 4-9
Managing Users and Accounts .............................................................................. 4-10

Modifying Users and Accounts ...................................................................... 4-10
Deleting Users and Accounts ......................................................................... 4-12
Deleting User Groups ..................................................................................... 4-13
Chapter 5: Creating LPANs
Creating and Allocating Resources to an LPAN ..................................................... 5-2
PM5.2_BF v
About LPANs ................................................................................................... 5-2

Allocating pBlades ........................................................................................... 5-3
Allocating Disks and Tapes.............................................................................. 5-3
Accessing DVD-ROM Drives.......................................................................... 5-5
Registering Virtual CD-ROMs......................................................................... 5-5
Allocating vSwitches........................................................................................ 5-6
Assigning Administrators................................................................................. 5-7
Steps to Allocate an LPAN............................................................................... 5-7
Discovering the Available Resources............................................................... 5-7
Creating an LPAN .......................................................................................... 5-13
Allocating pBlades ......................................................................................... 5-14
Allocating Disk Resources ............................................................................. 5-15
Enabling the Physical DVD-ROM Drive ....................................................... 5-16
Registering Images as Virtual CD-ROMs...................................................... 5-16
Modifying Virtual CD-ROM Images ............................................................. 5-17
Allocating Tape Devices ................................................................................ 5-18
Allocating vSwitches...................................................................................... 5-18
Configuring Disks for Persistent Reservations .................................................... 5-19

About SCSI-2 Reserve/Release Features ....................................................... 5-19
About SCSI-3 Persistent Reservations ........................................................... 5-20
Supported Configurations and Restrictions.................................................... 5-20
SCSI-3 Operations.......................................................................................... 5-21
Enabling Persistent Reservations ................................................................... 5-22
Disabling Persistent Reservations .................................................................. 5-23
Clearing Persistent Reservations .................................................................... 5-23
Creating Global and Local Pools ........................................................................... 5-24

About Pools .................................................................................................... 5-24
Roles Required for These Tasks..................................................................... 5-27
Creating a Local Pool ..................................................................................... 5-28
Allocating Blades to a Local Pool .................................................................. 5-28
Creating a Global Pool ................................................................................... 5-30
Enabling LPAN Access to a Global Pool....................................................... 5-30
Modifying a Global Pool ................................................................................ 5-31
Deleting a Global Pool ................................................................................... 5-32
Booting the LPAN’s pServers ............................................................................... 5-32

Booting, Rebooting, or Shutting Down an LPAN.......................................... 5-33
Booting, Rebooting, or Shutting Down a pServer.......................................... 5-34
vi PM5.2_BF
Contents
Modifying an LPAN’s Resources ......................................................................... 5-36

Adding a Resource to an LPAN ..................................................................... 5-36
Removing a Resource from an LPAN............................................................ 5-37
Modifying Resources Example ...................................................................... 5-37
Part II: Creating pServers
Chapter 6: Configuring pServers
Creating a pServer ................................................................................................... 6-2

About pServers ................................................................................................. 6-2
Obtaining a pServer’s Time.............................................................................. 6-3
Role Required for This Task ............................................................................ 6-3
Creating a pServer ............................................................................................ 6-3
Assigning Processing Blades ................................................................................... 6-4

About Processing Blades.................................................................................. 6-4
About Failover pBlades.................................................................................... 6-5
Two Major Steps to Assign Processing Blades................................................ 6-7
Assigning a Primary pBlade............................................................................. 6-7
Assigning a Failover pBlade ............................................................................ 6-8
Assigning SAN Disks .............................................................................................. 6-9

About SAN Disks ............................................................................................. 6-9
Using Network Attached Storage ................................................................... 6-10
Assigning a Disk to a pServer ........................................................................ 6-11
Assigning FC Tape Devices .................................................................................. 6-13

About Tape Devices ....................................................................................... 6-13
Assigning a Tape Device to a pServer ........................................................... 6-14
Enabling a DVD-ROM Drive ................................................................................ 6-16

About DVD-ROM Drives .............................................................................. 6-16
Enabling a DVD-ROM Drive for a pServer................................................... 6-16
Enabling a Virtual CD-ROM Drive ...................................................................... 6-17
PM5.2_BF vii
Establishing Network Connections ....................................................................... 6-17

About Networking pServers ........................................................................... 6-17
Creating Network Connections ...................................................................... 6-20
Completing a pServer’s Configuration .................................................................. 6-22

About Completing the Configuration ............................................................. 6-22
Completion Checklist ..................................................................................... 6-23
Chapter 7: Administering pServers
Displaying pServer Information .............................................................................. 7-2
Modifying a pServer Name or Description ............................................................. 7-3
Modifying a pServer Configuration ........................................................................ 7-4

About Modifying a Shutdown pServer............................................................. 7-4
About Modifying a Running pServer ............................................................... 7-5
Modifying a pServer Configuration Examples................................................. 7-9
Managing Virtual CD-ROMs ................................................................................ 7-11
Managing Boot and Root Disk Images ................................................................. 7-13

Modifying Registered Boot or Root Disk Images .......................................... 7-13
Creating Custom Images ................................................................................ 7-15
About Rescue Mode ....................................................................................... 7-15
Configuring pServer Boot Attributes .................................................................... 7-17

About pServer Boot Attributes....................................................................... 7-17
Configuring a pServer’s Boot Attributes........................................................ 7-18
Using the pServer Console .................................................................................... 7-21

About the pServer Console............................................................................. 7-21
Opening a Console ......................................................................................... 7-21
Using the Console on Linux and Windows pServers..................................... 7-21
viii PM5.2_BF
Contents
Chapter 8: Administering Windows-Based pServers
Connecting to a pServer Using the Remote Desktop Protocol ............................... 8-2

Opening an RDP Connection ........................................................................... 8-2
Reestablishing an RDP Session........................................................................ 8-3
Modifying the pServer IP Address (Optional) ................................................. 8-5
Connecting to a pServer Using the Virtual VGA Desktop ..................................... 8-6

Requirements and Limitations.......................................................................... 8-7
Accessing the vVGA Desktop.......................................................................... 8-7
Disabling the vVGA Desktop........................................................................... 8-8
Shutting Down Windows pServers ......................................................................... 8-9
Disabling the Hyperthreading Feature (Intel Only) ................................................ 8-9
Managing Device Drivers ..................................................................................... 8-10

About Device Drivers..................................................................................... 8-10
Device Driver Configuration Restrictions...................................................... 8-13
Displaying Driver Signatures and Versions ................................................... 8-14
Configuring Network Connections ....................................................................... 8-16

Network Configuration Requirements ........................................................... 8-16
Setting the MTU Size for vEths ..................................................................... 8-17
Choosing pBlades for a Multicast Environment ............................................ 8-18
Using IGMP with Microsoft NLB Clusters.................................................... 8-18
Configuring Multipath Storage Support ................................................................ 8-19
Tuning Virtual Memory for Applications ............................................................. 8-20

Setting Switches in the boot.ini File............................................................... 8-20
Enabling Memory Footprint Reduction.......................................................... 8-21
Recommendations for Running MSCS Clusters ................................................... 8-22

MSCS Requirements ...................................................................................... 8-22
Repurposing Example .................................................................................... 8-22
MSCS Clustering Considerations................................................................... 8-24
Adding Nodes to Running Clusters................................................................ 8-25
PM5.2_BF ix
Part III: Creating Application Services
Chapter 9: Configuring Resources
About Resources ...................................................................................................... 9-3
About Services ........................................................................................................ 9-8

Application Services......................................................................................... 9-9
Load-Balancing Services................................................................................ 9-10
Enabling and Disabling Use of Resources and Services on pServers ................... 9-12
Enabling and Disabling Application Services................................................ 9-12
Configuring Executable Resources ....................................................................... 9-13

About Executable Resources .......................................................................... 9-13
Create Executable Resources ......................................................................... 9-14
Modifying Executable Resources .......................................................................... 9-16

About Modifying Executable Resources........................................................ 9-16
Modifying Executable Resources................................................................... 9-16
Configuring Network Resources ........................................................................... 9-17

About Network Resources.............................................................................. 9-17
Create Network Resources ............................................................................. 9-18
Modifying Network Resources ............................................................................. 9-20

About Modifying Network Resources............................................................ 9-20
Modifying Network Resources....................................................................... 9-20
Modifying Network Settings for a Network Resource................................... 9-21
Configuring SCSI Disk File System Resources .................................................... 9-23

About SCSI Disk File System Resources....................................................... 9-23
Create SCSI Disk File System Resources ...................................................... 9-24
Modifying SCSI File System Resources ............................................................... 9-27

About Modifying SCSI File System Resources ............................................. 9-27
Modifying SCSI File System Resources ........................................................ 9-27
Modifying Mount Points for a SCSI File System Resource........................... 9-28
x PM5.2_BF
Contents
Configuring Network File System Resources ....................................................... 9-30

About Network File System Resources.......................................................... 9-30
Create Network File System Resources ......................................................... 9-30
Modifying Network File System Resources ......................................................... 9-33

About Modifying Network File System Resources........................................ 9-33
Modifying Network File System Resources................................................... 9-33
Configuring Failover Policy Resources ................................................................ 9-34

About Failover Policy Resources ................................................................... 9-34
Create Failover Policy Resources with the GUI............................................. 9-36
Modifying Failover Policy Resources ................................................................... 9-38

About Modifying Failover Policy Resources ................................................. 9-38
Modifying Failover Policy Resources ............................................................ 9-39
Modifying pServer Members of a Failover Policy Resource ......................... 9-39
Configuring User-Defined Monitor Resources ..................................................... 9-41

About User-Defined Monitor Resources........................................................ 9-41
Two Steps to Configure User Defined Monitor Resources............................ 9-42
Create User-Defined Monitor Resources with the GUI ................................. 9-42
Configure Event Trigger Rules for the User Defined Monitor ...................... 9-43
Configure Service Assignments for User Defined Monitors ......................... 9-44
Modifying User-Defined Monitor Resource Configurations ................................ 9-45

About Modifying User-Defined Monitor Resource Configurations .............. 9-45
Modifying User-Defined Monitor Resource Configurations ......................... 9-45
Configuring Health Monitor Resource Configurations ......................................... 9-46

About Health Monitor Resource Configurations ........................................... 9-46
Create Health Monitor Resource Configurations with the GUI ..................... 9-57
Modifying Health Monitor Resource Configurations ........................................... 9-60

About Modifying Health Monitor Resource Configurations ......................... 9-60
Modifying Health Monitor Resource Configurations .................................... 9-61
Adding a Monitor pServer to a Health Monitor Resource Configuration...... 9-62
Extracting Application Templates ......................................................................... 9-63

About Application Templates......................................................................... 9-63
Extract Application Templates with the GUI................................................. 9-63
PM5.2_BF xi
Chapter 10: Configuring Applications for PAN Manager Control
Understanding Application Control ...................................................................... 10-2

About Application Control ............................................................................. 10-2
About Resources............................................................................................. 10-2
Installing Application Software ............................................................................. 10-3

About Installing Application Software........................................................... 10-3
Three Steps to Install Application Software................................................... 10-5
Open a Connection to the pServer Console.................................................... 10-5
Complete the Installation................................................................................ 10-5
Managing Stand-alone Applications ..................................................................... 10-6

About Stand-alone Applications..................................................................... 10-6
Steps to Configure an Application for PAN Manager Control ...................... 10-7
Create an Application ..................................................................................... 10-8
Assign Executable Resources......................................................................... 10-9
Assign Network Resources............................................................................. 10-9
Assign SCSI Disk Resources........................................................................ 10-10
Assign Network File System Resources....................................................... 10-11
Assign Failover Policy Resources ................................................................ 10-11
Assign Health Monitor Resources................................................................ 10-12
Assign User Defined Monitor Resources for an Application....................... 10-13
Start, Stop, or Move an Application............................................................. 10-14
Modifying Application Control Configurations .................................................. 10-15

About Modifying Application Control Configurations................................ 10-15
Modifying Advanced Settings for an Application........................................ 10-16
Modifying Resource Assignments for an Application ................................. 10-17
Starting, Stopping, and Moving an Application........................................... 10-20
Chapter 11: Configuring Load Balancers
Understanding Load Balancer Control .................................................................. 11-2

About Load Balancer Control ........................................................................ 11-2
About Load Balancer Resources .................................................................... 11-3
About Load Balancer Attributes..................................................................... 11-4
Starting the Load-balancing Service ............................................................ 11-10
Router Requirements .................................................................................... 11-10
xii PM5.2_BF
Contents
Configuring a Load Balancing Service ............................................................... 11-12

Steps to Configure a Load Balancing Service .............................................. 11-12
Create or Delete a Load Balancer................................................................. 11-12
Assign Network Resources........................................................................... 11-13
Assign Failover Policy Resources ................................................................ 11-14
Assign Health Monitor Resources................................................................ 11-14
Assign a User Defined Monitor to a Load Balancer .................................... 11-15
Add Members to the Load Balancing Service.............................................. 11-16
Start, Stop, or Move a Load Balancing Service ........................................... 11-18
Modifying Load Balancer Control Configurations ............................................. 11-19

About Modifying Load Balancer Control Configurations ........................... 11-19
Modifying Load Balancer Control Configurations ...................................... 11-20
Modifying Advanced Settings for a Load Balancer Control Configuration 11-20
Modifying Resource Assignments for a Load Balancer Control Configuration ...
11-21
Starting, Stopping, and Moving a Load Balancer and its Members............. 11-23
Part II: Controlling and Monitoring the PAN
Chapter 12: Controlling PAN Components
Controlling the Platform ........................................................................................ 12-3

About Controlling the Platform...................................................................... 12-3
Shutting Down a Platform .............................................................................. 12-3
Rebooting a Platform...................................................................................... 12-4
Controlling a Blade ............................................................................................... 12-5

About Controlling a Blade.............................................................................. 12-5
Controlling a pBlade....................................................................................... 12-6
Controlling a cBlade....................................................................................... 12-8
Controlling a cBlade switch (BladeFrame BF200 only) ................................ 12-9
Controlling PAN Manager .................................................................................. 12-10

About Controlling PAN Manager ................................................................ 12-10
Starting PAN Manager ................................................................................. 12-11
Shutting Down PAN Manager...................................................................... 12-11
PM5.2_BF xiii
Controlling an LPAN .......................................................................................... 12-11

About Controlling an LPAN ........................................................................ 12-11
Booting an LPAN ......................................................................................... 12-12
Rebooting an LPAN ..................................................................................... 12-12
Shutting Down an LPAN.............................................................................. 12-12
Controlling a pServer .......................................................................................... 12-13

About Controlling a pServer ........................................................................ 12-13
Booting and Rebooting a pServer................................................................. 12-14
Shutting Down a pServer.............................................................................. 12-15
Controlling LPANs and pServers Together ........................................................ 12-16

About LPANs and pServers ......................................................................... 12-16
pServer Acquire/Release Resources Model ................................................. 12-17
pServer Boot Pending State.......................................................................... 12-17
LPAN Boot, Reboot, and Shutdown Model................................................. 12-19
LPAN Reboot Model.................................................................................... 12-19
Rebooting the Entire LPAN ......................................................................... 12-20
Chapter 13: Configuring Events, Triggers, and SNMP
Understanding Platform Monitoring ..................................................................... 13-2

Events ............................................................................................................. 13-2
Event Types .................................................................................................... 13-3
Monitors and Triggers .................................................................................... 13-3
Viewing Events .............................................................................................. 13-3
SNMP Support................................................................................................ 13-4
Configuring Event Types ...................................................................................... 13-6

About Event Types ......................................................................................... 13-6
Two Steps to Configure Event Action and Notification ................................ 13-6
Configure the Domain Defaults...................................................................... 13-7
Configure and Enable the Event Action(s) for an Event Type....................... 13-8
Configuring Triggers ............................................................................................. 13-9

About Triggers................................................................................................ 13-9
Two Steps to Configure Triggers ................................................................. 13-11
List the Available Monitors and Their Triggers........................................... 13-12
Configure the Trigger(s) for a Monitor ........................................................ 13-13
xiv PM5.2_BF
Contents
Modifying Default Trigger Values ...................................................................... 13-14

About Default Triggers................................................................................. 13-14
Two Steps to Configure Triggers ................................................................. 13-14
Viewing Events ................................................................................................... 13-15

About Events ................................................................................................ 13-15
Three Steps to View Events ......................................................................... 13-15
Apply a Filter and View a List ..................................................................... 13-15
View the Event Instance Details................................................................... 13-17
Update the Event Instance Status ................................................................. 13-17
Configuring SNMP Settings ................................................................................ 13-18

About SNMP ................................................................................................ 13-18
Two Steps to Configure SNMP.................................................................... 13-19
Configure the SNMP Agent(s) ..................................................................... 13-20
Configure the SNMP Manager(s)................................................................. 13-20
Exporting Virtual Network Topology Using SNMP ........................................... 13-22

cBlade Eths ................................................................................................... 13-23
rEths.............................................................................................................. 13-23
vSwitches...................................................................................................... 13-23
pServer Eths.................................................................................................. 13-24
Viewing the Network Topology with PAN Manager................................... 13-24
Chapter 14: Archiving for Disaster Recovery
PAN Archiving for Disaster Recovery .................................................................. 14-2

About Disaster Recovery................................................................................ 14-2
What an Archive Contains.............................................................................. 14-3
What an Archive Does Not Contain............................................................... 14-4
A Note on Boot and Root Disk Images .......................................................... 14-4
Preparing a Platform for Recovery................................................................. 14-5
Copying Configurations from One Platform to Another................................ 14-5
Moving Configurations Between a BladeFrame BF400 S2 and
BladeFrame BF200................................................................................. 14-6
Exporting a PAN Archive ..................................................................................... 14-6

About Exporting and Importing ..................................................................... 14-6
Steps to Create, Export, or Delete a PAN Archive......................................... 14-7
PM5.2_BF xv
Creating, Exporting, or Deleting a PAN Archive........................................... 14-7

Scheduling Regular Archiving ....................................................................... 14-9
Importing an Archive .......................................................................................... 14-12

About Importing an Archive ........................................................................ 14-12
Importing the PAN Archive ......................................................................... 14-12
Renaming the PAN Archive (Optional) ....................................................... 14-13
Merging PAN Configurations ............................................................................. 14-14

About Merging PAN Configurations ........................................................... 14-14
Merging the Archive..................................................................................... 14-15
Mapping Resources ............................................................................................. 14-16

About Mapping Resources ........................................................................... 14-16
Mapping PAN Resources ............................................................................. 14-17
Validating a PAN Archive .................................................................................. 14-19

About Validating a PAN Archive................................................................. 14-19
Validation Failures ....................................................................................... 14-19
Validation Warnings..................................................................................... 14-20
Validating the Archive ................................................................................. 14-20
Swapping the Current PAN for a PAN Archive .................................................. 14-21

About Swapping the Current PAN ............................................................... 14-21
Swapping the Configuration With the Archive ............................................ 14-22
Reserving a Disk for Exclusive Storage of PAN Archives ................................. 14-23

Reserving a Disk for Exclusive Storing of PAN Archives........................... 14-23
Managing an Image Archive ............................................................................... 14-24

Image Export Behavior................................................................................. 14-24
Image Restore Behavior ............................................................................... 14-25
Exporting and Restoring an Image Archive ................................................. 14-26
Chapter 15: Using the Resource Configuration Collector
Understanding PAN Manager Resource Configuration Collector ........................ 15-2

PAN Manager RCC Overview ....................................................................... 15-2
How PAN Manager RCC Works ................................................................... 15-2
xvi PM5.2_BF
Contents
pServer Configuration Data Collected by PAN Manager RCC ..................... 15-3

Type of Events the Trigger Data Collection................................................... 15-5
Processing PAN Manager Resource Configuration Collector Data ...................... 15-5

Location of the PAN Manager RCC DTD file ............................................... 15-5
Location and Format of RCC Reports............................................................ 15-5
Guidelines to Processing PAN Manager RCC ............................................... 15-6
Chapter 16: Maintenance and Troubleshooting
Log Files ................................................................................................................ 16-2
Maintenance Mode ................................................................................................ 16-3
Saving cBlade State Information .......................................................................... 16-4
Displaying a Configuration Report ...................................................................... 16-5

Command Options.......................................................................................... 16-5
Sample Output ................................................................................................ 16-6
Maintenance LPAN ............................................................................................... 16-8

Maintenance LPAN Features ......................................................................... 16-8
Accessing External Tools ............................................................................... 16-8
Using the Maintenance LPAN........................................................................ 16-8
Windows pServers ............................................................................................... 16-10

Handling Crash Dumps ................................................................................ 16-10
Handling Windows Blue Screen Errors ....................................................... 16-12
Troubleshooting an Unresponsive pServer .................................................. 16-15
Handling Other Types of Errors ................................................................... 16-21
Common Problems .............................................................................................. 16-22

Start-up Problems ......................................................................................... 16-22
Configuration Problems................................................................................ 16-23
Administration and Control Problems.......................................................... 16-24
PM5.2_BF xvii
Appendix A: SNMP Traps and Internal Events Tables
SNMP Traps Mapped to Internal Events ............................................................... A-1
Internal Event Types and Their Associated SNMP Traps ................................... A-23
Index
xviii PM5.2_BF
Preface
Welcome to PAN Manager PM5.2_BF. PAN Manager

Administrator’s Guide is part of the PAN Manager documentation
set. Its purpose is to describe the procedures for configuring and
administering a Processing Area Network, using the PAN Manager
Graphical User Interface.
Audience — PAN Manager Administrator’s Guide is for PAN

Administrators and LPAN Administrators.
Topics — Read this book to learn about the following:

• Configuring a PAN
• Creating and administering LPANs
• Creating and administering pServers
• Configuring and managing application resources
• Monitoring and troubleshooting the PAN
• Archiving for disaster recovery
PAN Manager Documentation Set — To learn about the other

documents available in the PAN Manager documentation set, see
Chapter 2, “Document List,” of PAN Manager Feature Summary.
PAN Manager Features — To learn about the PAN Manager

features available in the current release, see Chapter 3, “Feature
List,” of PAN Manager Feature Summary.
PM5.2_BF xix
Customer Support
If you require customer support regarding this product, use the

following contact information.
Fujitsu Siemens Computers customer support
Internet http://www.fujitsu-siemens.com/support
Telephone See the Help Desk information at http://
manuals.fujitsu-siemens.com/
primergyservers.html under General
Information, Warranty and Support.
Document Conventions
Convention Description
> Directory-level delimiter used to navigate the left pane of the

PAN Manager GUI.
Example: Resources > Ethernet Connections
Sans serif italics Variable text, such as a path, a filename, or an LPAN name.
Example: lpan -c lpanname
Sans serif Text that must be typed as shown.
Example: Type root at the login prompt.
xx PM5.2_BF
Preface
Convention Description
Bold The name of a field or window element appearing in a GUI. It also

highlights default values in PAN Manager man pages.
Example: In the Users page...
Italics Text that is emphasized.

Example: Do not connect the power.
[text] Text that is optional to a command.
{text} A set of choices, one of which is required.
| Separation of mutually exclusive choices in syntax lines.

Example: lpan [-aD | -rD]{switch | SCSI_ID} lpanname
Note Information of importance or that may not fit in main text.
Caution Failure to heed a caution could result in loss of data.
Warning — Failure to heed a warning could result in physical

! harm to the user or the hardware.
PM5.2_BF xxi
xxii PM5.2_BF
Chapter 1
Getting Started with
PAN Manager
PAN Manager provides a single control point for allocating,

configuring, and monitoring both physical and logical resources of
a Processing Area Network (PAN). A PAN consists of one or more
hardware platforms and their associated processing and I/O
resources.
This manual provides information on using the PAN Manager

graphical user interface (GUI) to:
• Configure a PAN
• Create and configure pServers in the PAN
• Configure applications and load balancers to run on the pServers
• Monitor the system and perform disaster recovery
PM5.2_BF 1-1
About PAN Manager
PAN Manager Whenever the Control Blades boot, PAN Manager starts.
Location
PAN Manager runs primarly on one Control Blade (the “master
cBlade”), but mirrors itself on the other cBlade. In the case of
failure, PAN Manager fails over to the other (“slave”) cBlade.
Any asynchronous LPAN and pServer operations, such as reboot or

shutdown, fail over with PAN Manager. If the operation was
incomplete at the time of failover, it restarts and completes
properly.
Accessing You can connect to PAN Manager in either of two ways:

PAN Manager
• Use a browser to access the graphical user interface (GUI)
• Use SSH or Telnet to access the command-line interface (CLI)
This manual describes only the PAN Manager GUI. For

information on the PAN Manager CLI, see PAN Manager Scripting
Guide and PAN Manager Command Reference.
Supported PAN Manager supports the following browser versions:

Browsers
• Internet Explorer 6.0 and higher
• Firefox 1.0 and higher
• Mozilla 1.7 and higher (Linux only)
To use the full functionality of the PAN Manager GUI, your web
browser must have Java plugin JRE1.5 or higher. This Java plugin
is available from http://java.sun.com.
1-2 PM5.2_BF
Getting Started with PAN Manager
The PAN Manager GUI
The PAN Manager graphical user interface (GUI) allows you to

configure, control, and/or monitor resources in the PAN, according
to your administrative role.
Note: To navigate within the PAN Manager GUI, use the Back
button on the PAN Manager GUI; do not use the browser’s Back
button.
Documentation From within the PAN Manager GUI, you can view the complete
and Help PAN Manager documentation set online. Clicking the
documentation link on the upper right corner of the GUI causes an
expandable tree of documentation titles to appear in the left panel.
We recommend that you consult the PAN Manager GUI Guide for
initial orientation.
In addition, PAN Manager online help (the help? button on the

upper right) describes the page you are visiting and how to use the
tools on that page.
Logging On to To log on to the PAN Manager GUI:

the GUI Initially • You must already be a PAN Manager user.
• Your browser must have cookies and JavaScript turned on.
PAN Manager user accounts parallel Linux user accounts on the

cBlades. When you log on to the cBlade, you are automatically
logged on to the PAN Manager with the appropriate permissions.
```To initially log on to PAN Manager as root:

1. From a GUI browser, enter the PAN Manager IP address (this IP
address is configured during installation).
For example, enter 192.168.200.1.
PM5.2_BF 1-3
Note: To avoid sending access credentials (username and

password) across the network in clear text, prefix the IP address
with https:// instead of http://. Be aware that
PAN Manager uses an unsigned certificate for HTTPS
connections. You need to accept this certificate when your
browser queries you.
The Welcome to PAN Manager login window appears.
2. In the User Name field, type root; in the Password field, type
the password configured at installation.
3. Click Login.
Logging On to After the other administrative roles have been established and users
the GUI have been assigned to them, all users of PAN Manager use the
Subsequently following procedure to log on. For more information on users and
roles, see Chapter 4, “Managing System Access”.
Note: Your browser must have cookies and JavaScript turned on.
```To log on to the PAN Manager as a user (administrator):

1. From a GUI browser, enter the PAN Manager IP address.
For example, enter 192.168.200.1.
Note: To avoid sending access credentials (username and

password) across the network in clear text, prefix the IP address
with https:// instead of http://. Be aware that
PAN Manager uses an unsigned certificate for HTTPS
connections. You need to accept this certificate when your
browser queries you.
The Welcome to PAN Manager login window appears.
2. In the User Name field, type your username; in the Password
field, type the your password.
3. Click Login.
1-4 PM5.2_BF
Part I
Creating a PAN
Part I of this guide outlines the tasks involved in creating a PAN

with PAN Manager, and consists of the following chapters:
• Chapter 2, “Configuring the PAN Structure”

• Chapter 3, “Configuring External Connectivity”
• Chapter 4, “Managing System Access”
• Chapter 5, “Creating LPANs”
Chapter 2
Configuring the PAN
Structure
This chapter describes configuring the PAN structure, which

consists of the platform(s) and PAN-wide attributes and defaults.
This chapter includes:
• Overview
• Naming the Platform
• Specifying the PAN Identification Attributes
• Configuring the SMTP Server
• Specifying Default Boot and Root Disk Images
• Activating Flow Control on the PAN
• Configuring Power Management
• Displaying Available Application Templates
PM5.2_BF 2-1
Overview
This chapter describes configuring the PAN’s identification

attributes, SNMP agent, and default settings.
The major steps for configuring the PAN are:

1. Name the platform(s).
2. Specify the PAN identification attributes.
3. Configure the SNMP agent for the PAN.
4. Specify the default boot image, root disk image, and file system
type.
5. (Optional) Activate flow control for the PAN.
Subsequent chapters in this book assume the following:

• You have planned the Logical PAN (LPAN) allocations and
configurations.
• You have planned the network topology.
• You have identified the PAN Manager users and their
responsibilities.
2-2 PM5.2_BF
Configuring the PAN Structure
Naming the Platform
About the Each platform must have a unique name within the PAN. The
Platform Name platform name is used as part of the pBlade and cBlade name and is
referenced in several commands. Each platform has the default
name of MyBladeFrame.
If you have only one platform, you can continue to use the name
MyBladeFrame. If you have multiple platforms, you might want to
assign different names to them.
Naming Platform names are limited to the following characters:

Conventions
• Uppercase or lowercase letters
• Numbers
• Dollar sign ($)
• Underscore (_)
Note: There is a limit of 32 legal characters in a name.
Role Required PAN Administrator

for This Task
Naming the ```To name the platform:

Platform
1. In the left pane, click Platforms > platform_name.
2. In the right pane, on the Platform platform_name page, click
the Edit button.
3. In the Edit Platform dialog box, enter a new name in the
Rename Platform field, and then click Submit.
The rest of the examples in this document use the default platform
name MyBladeFrame.
PM5.2_BF 2-3
About the The platform ID (also called BFID) is an internal identification

Platform ID number used to uniquely identify a platform on the external
management subnet. PAN Manager uses the BFID to tag distributed
resources and services.
All BFIDs on a given subnet must be unique. If you have a large

installation of platforms on multiple subnets, consider assigning
unique BFIDs across your whole network to minimize the chance
for duplicate BFIDs to accidentally occur within the same subnet.
Caution: If you are assigning or changing the BFID, you must

ensure that duplicate BFIDs do not get assigned to frames on the
same subnet. Duplicate BFIDs can result as a side effect of other
administrative tasks. When carrying out the following
admininstrative tasks, doublecheck the BFIDs in use on all subnets
that are affected by your action.
• When restoring a PAN archive from one platform to a different

platform, make sure the BFID in the archive does not conflict
with one already in use on the subnet.
• When moving a platform from one subnet to a different subnet
using the extnet command, doublecheck that the platform’s
BFID does not conflict with any of the existing platforms on the
different subnet.
Changing the Platform ID
```To change the BFID:

1. In the left pane, click the name of the Platform to modify.
2. In the right pane, on the Platform platform_name page, click
the platform ID button.
3. The Edit platform ID dialog box displays the current ID.
4. Enter a new number in the platform ID field.
5. Click the Submit button to save your work.
Note: If you change the BFID, you must restart PAN Manager.
2-4 PM5.2_BF
Specifying the PAN Identification Attributes
About the PAN The PAN can have identification attributes. This allows individual
Identification PANs to be distinguished in installations with multiple PANs. The
Attributes following are the PAN’s identification attributes:
• PAN name — The default PAN name is Egenera. If you have
only one PAN, you can retain or change the default. If you have
multiple PANs that are visible to one another, you must give
them unique names.
• PAN owner — Typically, this is the name of the PAN
Administrator. However, you can specify the name of an
organization. The owner is optional.
• PAN description — A descriptive phrase that identifies the
PAN. The description is optional.
• PAN location — The physical or geographical location of the
PAN. The location is optional.

for This Task
Editing the PAN ```To edit PAN General Information:

General
1. In the left pane, click the name of the PAN that you want to
Information
configure.
2. In the right pane, on the PAN pan_name page, in the Current
PAN area, click the Edit button.
3. In the Edit PAN Information dialog box, add or modify any of
the following information:
PAN name The unique name of this PAN.
Owner The owner designation of this PAN. This field is used
for informational purposes only.
PM5.2_BF 2-5
Location The physical location of the PAN. This field is used

Description A brief description of the PAN. This field is used
4. Click Submit.
2-6 PM5.2_BF
Configuring the SMTP Server
The mail gateway and SMTP server information allow

PAN Manager to communicate events to a person or a third-party
monitoring utility.
Role required for this task: PAN Administrator
```To configure the SMTP server (mail gateway) for the PAN
domain:
configure.
2. In the right pane, in the Current PAN area, click the SMTP
button.
3. In the PAN SMTP Settings dialog box, configure the following
fields:
• The SMTP server’s Host and Port number of the mail
service.
• The From Address to specify the full e-mail address from
which the PAN Administrator, or the PAN Manager
software acting on behalf of the PAN Administrator, can
send e-mail messages.
• The User account name of the administrator you specify in
the From Address field.
• A password (twice for verification) associated with that
Linux account.
4. Click Submit.
PM5.2_BF 2-7
Specifying Default Boot and Root Disk Images
About Boot and The pServer guide associated with each pServer operating system
Root Disk explains how to install boot and root disk images and how to make
Images them available to any pServer in the PAN.
With PAN Manager, you can designate a boot image and/or a root
disk image to be the PAN-wide default. If you specify a default boot
image, the effect is that any newly created pServer uses that boot
image unless you configure it otherwise. If you specify a default
root disk image, that image is used if you root a disk without
specifying an image.
PAN-wide defaults are useful primarily in cases where all or most

of the PAN’s pServers need to use the same operating system or file
system.
Boot Images
PAN Manager supports the following operating systems for

pServers:
• Red Hat Enterprise Linux Advanced Server (REL)
• SuSE Linux Enterprise Server (SLES)
• Microsoft Windows Server
• Sun Solaris operating environment
Boot images, once registered with PAN Manager, are available to

all LPANs, and thus to all pServers in the PAN. You can allow a
pServer to use the PAN-wide default, if any, or you can configure it
to always use another boot image. See “Managing Boot and Root
Disk Images” on page 7-13. You can also perform a one-time
override by specifying a different boot image at pServer boot time.
See “Booting, Rebooting, or Shutting Down a pServer” on
page 5-34.
2-8 PM5.2_BF
Egenera Virtualized Boot Services (EVBS) is a specialized boot

environment that you can use as a boot image. EVBS iterates over a
set of devices in a specified or default order until it finds a device
that it can boot from. If you specify EVBS as the PAN-wide default
boot image, you must accept its default device order: disk, VCD.
See Using Egenera Virtualized Boot Services for more information

on EVBS behavior.
Root Disk Images
A pServer may use any file system type that its operating system
supports.
Linux pServers use a root disk image, which is available to all

LPANs in the PAN. You can specify a root disk image to be the
default root disk image used in the PAN. You can also specify a
default file system for a root disk image. The supported file systems
are:
• ext2 (Red Hat)
• ext3 (Red Hat)
If you do not specify a default file system, PAN Manager uses the
first file system type listed.

for This Task
Setting the ```To set a default pServer boot image for the PAN:
Default Boot
1. In the left pane, click the PAN that you want to configure.
Image
2. In the right pane, in the Current PAN > Boot Image area, click
Default.
3. In the Set Default Boot Image dialog box, select the boot image
that you want to set as the Default for pServers within the PAN.
PM5.2_BF 2-9
The preferred boot image is EVBS. For more information on

EVBS, see Using Egenera Virtualized Boot Services.
4. Click Submit.
Changing the ```To change the EVBS version that serves as System EVBS:
System EVBS
Image System EVBS is used only by PAN Manager, and only to initiate
booting from a specified RAM disk image. You cannot supply boot
arguments to System EVBS.
1. In the left pane, click the PAN that you want to configure.
2. In the right pane, in the Current PAN > Boot Image area, click
System EVBS.
3. In the Set System EVBS Image dialog box, select the EVBS
image that you want to serve as the System EVBS.
4. Click Submit.
Setting the ```To set a default root disk image for the PAN:
Default Root
Disk Image
configure.
2. In the right pane, in the Current PAN > Root Images area, click
the Default button.
3. In the Set Default Root Image dialog box, select the root image
that you want to set as the Default.
4. Click Submit.
2-10 PM5.2_BF
Activating Flow Control on the PAN
About Flow Flow control prevents packet loss on the internal platform network.
Control The cBlades operate two gates that manage internal network traffic:
the internal broadcast traffic and all traffic to the external network.
Flow control affects both of these gates. Network traffic can be

limited by either or both gates, depending on which is receiving a
heavier load.
Flow control on external network traffic is activated on a rEth; flow

control on internal broadcast network traffic is activated at the PAN
level. Activating flow control on a rEth automatically activates it at
the PAN level. When flow control is activated, it allows the vEth
driver to communicate with the application in order to slow traffic
to the appropriate level.
Because flow control affects network traffic, keep in mind the

following when using this feature:
• Flow control is activated on the rEth or at the PAN level.
Therefore, all traffic is affected, across LPANs and across
VLANs.
• Load-balancing options are unaffected by flow control.
• Because vSwitches, and their pServer connections, define
broadcast domains, it is important to carefully define the internal
network topology. For example, if you have a pServer
generating broadcast traffic, configure it as the only pServer on
a vSwitch.
Note: Flow control is completely optional, and is off by default.

Activate flow control only if it is necessary for your specific
application requirements.
PM5.2_BF 2-11
It is also possible to control the rate of network traffic on a

pServer’s vEth. This level of control is useful if the servers on the
external network receive packets at a slower rate than the pServers
send them.
For more information on activating flow control on a rEth, see

“Configuring Redundant Ethernet Interfaces” on page 3-8.

for This Task
Activating Flow ```To activate flow control on the PAN domain:

Control
configure.
2. In the right pane, in the Current PAN area, click the Multicast
button.
3. In the PAN Multicast setting dialog box, click Allow
Multicast Flow Control on all PAN rEths, to modify the
current configuration.
4. Click Submit.
2-12 PM5.2_BF
Configuring Power Management
PAN Manager manages power consumption and denies power-up

to pBlades when doing so would exceed available power supply.
The tasks needed to configure PAN Manager for power
management differ by whether the platform does or does not have
Redundant Power Input Modules (PIM-Rs):
• If you have a platform with PIM-Rs, PAN Manager discovers

the platform amperage automatically, but it needs to be
configured with the voltage of the site power supply. The four
PIM-Rs provide power separately to each of four power
domains, and each PIM-R allows for power cord failover in the
event of a power supply failure. You need to set certain
parameters that have to do with power-line preference and
failover policy.
• If you have a platform without PIM-Rs, PAN Manager needs to
be configured with the voltage of the site power supply and the
amperage of the platform.
Power Domains The platform’s 28 blades are segregated into four domains, A, B, C,
D, each served by a separate power input module.
Note: The BladeFrame BF200 manages all power within a single

power domain.
Figure 2.1 illustrates the BladeFrame BF400 S2 power domains.
PM5.2_BF 2-13
Figure 2.1 BladeFrame BF400 S2 Power Domains
pBlade 24 pBlade 24 pBlade 24 pBlade 24

cBlade 2 cBlade 2 cBlade 2 cBlade 2
sBlade 2 sBlade 2 sBlade 2 sBlade 2
sBlade 1 sBlade 1 sBlade 1 sBlade 1
cBlade 1 cBlade 1 cBlade 1 cBlade 1

Power Domain A Power Domain B Power Domain C Power Domain D
Power The BladePlane is the spine that connects all of the blades, and
Management provides the fast transfer rate.
The BladePlane is either 20 or 30 amp. (For international

installations, the BladePlane may be labelled 16-amp or 24-amp.)
To safeguard against power overloading, PAN Manager monitors

power consumption and denies a blade power-up when it would
cause a power overload.
2-14 PM5.2_BF
In order for PAN Manager to properly manage power consumption,

it must be configured with the correct BladePlane amperage and
power supply voltage. (This information is typically given to
PAN Manager by the service provider when installing the system.)
Table 2.1 lists the power configurations supported for

BladeFrame BF400 S2.
Table 2.1 Power Configurations for BladeFrame BF400 S2
Voltage Amperage Maximum Wattage
200 16/20 3200
208 16/20 3328
210 16/20 3360
216 16/20 3456
220 16/20 3520
230 16/20 3680
240 16/20 3840
200 24/30 4800
208 24/30 4992
210 24/30 5040
216 24/30 5184
220 24/30 5280
230 24/30 5520
240 24/30 5760

for This Task
PM5.2_BF 2-15
Configuring The purpose of this procedure is to inform PAN Manager of the

Power for amperage and voltage that are available on the platform. On some
Platforms platforms, the amperage is discovered automatically; you need to
Without PIM-Rs set only the voltage.
Note: The settings of amperage and voltage must reflect the

physical properties of your platform. The settings are typically
applied by the service provider when installing the system, and it is
unlikely that you will need to change them. (You can change
amperage and voltage values while pServers are running.)
Configuring Power Settings
```To configure the power settings:

1. In the left pane, click Platform > platform_name.
2. In the right pane, on the Platform > platform_name page, click
the Power button.
3. In the Power Configuration dialog box, click the Power
Configuration button, then do the following to modify your
power configuration:
• Select an Amperage from the pull-down list. (Not available
on BladeFrame BF400 S2 with PIM-Rs.)
• Select a Voltage from the pull-down list.
4. Click Submit to save your changes.
Configuring There are three additional steps for configuring power for platforms
Power for with Redundant Power Input Modules (PIM-Rs):
Platforms with
1. Decide how you want to set the preferred power cord for each
PIM-Rs
PIM-R:
• Manually using the physical button on the PIM-R, which is
ideal if you have physical access to the platform. To use this
method, make sure the Enable manual power preference
button on physical device check box is checked in the
Configure PIM Settings dialog box.
2-16 PM5.2_BF
• Remotely using PAN Manager. For this method, use the

procedures for disabling the physical line preference button
and specifying the preferred power cord. Make sure the
Enable manual power preference button on physical
device check box is not checked in the Configure PIM
Settings dialog box.
2. Set the power line preference, either manually or remotely. The
preferred power line is the one used when both power lines meet
system specifications. You can choose Power Cord A, Power
Cord B, or None (no preference).
3. (Optional) Specify a soft limit for the power (Watts) and current
(Amps) for each PIM-R. When the power or current exceeds
these soft limits, PAN Manager writes events to the event log,
which can be useful for monitoring power consumption.
Disabling the Manual Power Preference Button
```To disable the Manual Power Preference button (also called

the Line Preference Selection button) on platforms with PIM-
Rs:
2. In the right pane, on the Platform > platform_name page, select
a PIM-R from the Power Domain table.
3. Click the Configure button.
4. In the Configure PIM Settings dialog box, clear the Enable
manual power preference button on physical device check
box.
5. Click the Submit button to save your settings and close the
dialog box.
Specifying the Preferred Power Cord
```To specify the Preferred Power Cord on platforms with PIM-Rs:

PM5.2_BF 2-17

4. In the Configure PIM Settings dialog box, select the preferred
power cord (Power Cord A, Power Cord B, or None).
dialog box.
Specifying the Event Trigger Limits
```To specify the power and current limits (“soft limits”) that trigger
an event on platforms with PIM-Rs:
4. In the Configure PIM Settings dialog box, enter the desired
power and current soft limits in the Power (Watts) and Current
(Amps) fields.
dialog box.
Displaying Available Application Templates
An application template is an object that encapsulates all of the

components and values associated with a specific template archive.
Application templates exist as files with .ptf extensions and reside
in the /opt/panmgr/templates directory on the cBlade.
```To display the available application templates:

configure.
2-18 PM5.2_BF
2. In the right pane, in the Current PAN area, click the Templates
button.
3. The PAN Templates dialog box lists the application templates
that are available to LPANs in this PAN. Templates are imported
into the LPANs.
4. Click Cancel to close the dialog box.
PM5.2_BF 2-19
2-20 PM5.2_BF
Chapter 3
Configuring External
Connectivity
This chapter describes the tasks necessary to configure the external

network connectivity for use by pServers.
Network connectivity is a chain of physical and virtual

components. Figure 3.1 illustrates this connectivity chain.
The location of the physical network connections varies by

platform. See READ THIS FIRST: PAN Manager Configuration
Guide for your platform for information on physical network
connections.
This chapter focuses on configuring virtual connectivity. It

describes:
• Modifying Internal and External Management Settings
• Configuring Ethernet Interfaces
• Configuring Redundant Ethernet Interfaces
• Creating vSwitches
PM5.2_BF 3-1
Instead of running cables between switch ports for each pServer, all
network connectivity goes through the platform’s network ports
and is configured from PAN Manager. The network ports handle all
the internal and external network traffic forthe platform, and their
redundancy provides for failover.
Figure 3.1 Network Connectivity
Virtual Ethernet
Interfaces (vEths)
Physical Ethernet
Redundant Ethernet
Interfaces (eths)
(rEth)
pServers
2
Physical Switch
Virtual Switch (vSwitch)

1 4
Physical Virtual
Note: PAN Manager does not store IP address configuration

information in the /etc/sysconfig/network-scripts file.
Therefore, you should use only PAN Manager controls, not any
external (shell) network commands, to configure network
connectivity.
3-2 PM5.2_BF
Configuring External Connectivity
Modifying Internal and External Management

Settings
You can modify the properties for the internal management network
of a platform, as well as the properties PAN Manager uses for
external network communication.
Caution: A system administrator initially sets the PAN Manager IP

address to a valid IP address for the external network to which the
platform is connected. The IP address for the PAN Manager on each
cBlade should come from a network administrator and must not
conflict with any other host address on the external network.
For additional information about modifying these management

addresses, see the EXTNET and INTNET commands in PAN Manager
Command Reference.
```To modify internal management IP addresses:

1. In the left pane, click the name of the platform that you want to
modify.
the Network button.
3. In the Platform Network Configuration dialog box, click
Internal Management Network Settings to display the
configurable fields.
4. Enter new values for any of the settings that you want to modify.
5. Click Submit.
Note: It takes a few minutes for these new settings to take

effect.
```To modify external management IP addresses:

modify.
PM5.2_BF 3-3

the Network button.
External Management Network Settings to display the
5. Click Submit.

effect.
```To modify external management multicast discovery settings:

modify.
the Network button.
External Management Discovery Settings to display the
5. Click Submit.

effect.
3-4 PM5.2_BF
Configuring Ethernet Interfaces
When configuring the external network connectivity for the PAN,

you begin by configuring the Ethernet interfaces, which directly
control the network ports.
About Ethernet The Ethernet connections enable the pServers to communicate with
Connections the premises network.
BladeFrame BF400 S2 supports NIC type e1000 for either a 10/

100/1000 Ethernet or a Fiber Gigabit interface.
You can observe and name the connectivity settings for each eth,
and configure the failover detection settings for each eth. You
establish the Ethernet connectivity settings, such as uplinks and
VLANs, when you uplink a vSwitch to a rEth. For information on
configuring vSwitches, see “Allocating vSwitches” on page 5-6.
Note: The Ethernet interface eth0 is reserved for PAN Manager and
is not listed. Do not use eth0 to configure an uplink for a vSwitch.
Connectivity Settings
The connectivity settings determine the behavior of the Media

Access Control (MAC) layer for an Ethernet interface, which
controls which Ethernet packets are processed by the Ethernet
interface.
• If all received packets are processed by the eth, its connectivity
setting is blank.
• On the Gigabit interface only, PAN Manager provides VLAN
support (following IEEE specification 802.1q) to allow more
flexibility in the use of the limited number of physical network
interfaces. If your network uses VLAN IDs, the Ethernet
packets’ VLAN ID tags determine which packets are processed
by which Ethernet interface. You can have up to 4096 VLAN
IDs per Gigabit interface.
PM5.2_BF 3-5
Connectivity settings are not mutually exclusive. An Ethernet

interface can support numerous VLAN IDs in addition to non-
VLAN-ID-tagged traffic.
To take advantage of VLAN IDs on your network, configure the

appropriate vSwitches and vEths on the pServer with the correct
VLAN IDs. VLAN IDs can be observed at the Ethernet interface
level only for informational purposes.
Network Failover Detection
Intelligent failover detection allows administrators to configure

rEths to report Ethernet device failures based on ping results (ping
failover detection mode or just ping mode).The alternative is to
detect such failures solely by the link status of the Ethernet device
(link status failover detection mode or just link status mode).
Ping mode uses ICMP (Internet Control Message Protocol)

ECHO_REQUEST and ECHO_REPLY packets to determine the
status of Ethernet devices. Link status mode checks for physical
connectivity with the external Ethernet switch.
You select link status mode or ping mode on the rEth(s), and set the
parameters required by the failover detection mode on the eths.
Note: If ping mode status parameters are set on the eth but ping
mode behavior is turned off at the rEth level, the eth-level
parameters are retained but ignored.
Be sure that the parameter values you choose match your network
configuration. PAN Manager validates your input format, but does
not attempt to detect logical errors. Some of the issues that you
must avoid include, but are not limited to the following:
• IP conflicts
• Duplicate MAC address entries
• Incorrect subnet mask
• Incorrect gateway
3-6 PM5.2_BF
• Invalid IP and MAC addresses (such as a broadcast or multicast

IP or MAC address)
Remember that each eth on a platform must have its own IP

address.

for This Task
Two Steps to There are two (optional) steps for configuring the Ethernet
Configure interfaces:
Ethernet
1. (Optional) Observe and/or name the connectivity setting.
Interfaces
2. (Optional) Set the parameters for ping failover detection mode.
Checking or ```To observe or name uplink setting on an eth:

Naming
1. In the left pane, click Resources > Networking.
Connectivity
Setting 2. In the right pane, on the Network Resources page, click the
name of the eth.
3. On the Ethernet page, you can name the eth settings by clicking
Modify. In the Modify Ethernet Device Settings dialog box,
specify a Switch Name and its corresponding Port for this
Ethernet Device.
4. Click Submit.
Setting the Ping ```To configure the failover detection mode on an eth:
Mode
Parameters Note: The eth must be part of a rEth that is configured for ping
failover detection mode before you can configure the failover
detection mode settings.
2. In the right pane, on the Network Resources page, click on the
name of the eth that you want to manage.
PM5.2_BF 3-7
3. On the Ethernet page, you can configure the ping mode

settings.
4. Click Failover Settings to display the Modify Failover
Detection Settings dialog box. Enter appropriate information in
the following fields:
• Enter the IP Address to be used for connectivity testing.
• Enter the Netmask of the Ethernet device.
• Enter the Gateway used by the ping mode detection.
• Enter the VLAN id if applicable.
• Select either Use existing hardware MAC address or
Specify custom MAC address
• Enter the Ping IP address external to the platform to be
pinged.
• In the Missed Ping Count Threshold field, enter the
number of consecutive missed ICMP echo replies that result
in a failure in the given time threshold. Default is 3.
• In the Missed Ping Time Threshold field, enter the amount
of time in milliseconds in which the given number of missed
ICMP echo replies need to occur before a failure is detected.
Default is 5000; the minimum is 1000 ms (1 second). A
threshold value below 1000 ms is not valid.
Note: The Missed Ping Time Threshold is rounded down.

5. Click Submit.
Configuring Redundant Ethernet Interfaces
Once you have configured the eths, you configure the redundant
Ethernet interfaces (rEths) for the PAN, which group the eths into
pairs for load-balancing and failover.
3-8 PM5.2_BF
About rEths A redundant Ethernet interface, or rEth, is a pair of external

Ethernet interfaces, one interface on each of the network controller
location. This pairing of interfaces provides load-balancing and
failover capability for network connectivity. Each rEth must have
the following properties:
• A unique name that conforms to the rules outlined in “Naming
Conventions” on page 2-3.
• A MAC address. PAN Manager automatically assigns a MAC
address, which is the typical method of assignment. However, if
your network administrator has strict control over MAC address
assignment, you might need to assign the MAC address
manually, using the PAN Manager command line interface. To
assign the MAC address manually, use the -M option with the
eth command.
Caution: If the assigned MAC address conflicts with another

MAC address on your network, you might experience network
outages.
• An Ethernet interface on each of the network controller

locations to pair together, forming the rEth. The two eths should
be of the same type and have identical VLAN ID settings.
• A load-balancing policy of either pair or static. If you do not
specify a load-balancing policy, PAN Manager uses single send/
receive (pair).
• Pair (the default) — Incoming and outgoing traffic is sent
and received on a single network controller blade. The
failover policy associated with this load-balancing policy is
to fail over both send and receive responsibility to the other
network controller blade. When the failed network
controller blade comes back online, it re-assumes both send
and receive responsibilities.
You can specify one of the two Ethernet interfaces as the
primary one that handles network traffic. If you do not
specify a primary interface, the first Ethernet interface
specified in the rEth handles network traffic.
Note: If you have more than one rEth configured in pair
PM5.2_BF 3-9
mode, you might improve the system’s load-balancing

capability and improve network performance by
designating their primary eths on different port locations.
• Static — Incoming and outgoing traffic is statically divided
between the two network port locations. Traffic is assigned
to one location or the other based on the pServer’s vEth
MAC address. Traffic from even-numbered MAC addresses
is assigned to one location; traffic from odd-numbered
MAC addresses is assigned to the other location. The
failover policy associated with this load-balancing strategy
is to fail over all traffic to the remaining location. Upon
recovery, the static assignments are re-established.
About Ping Intelligent failover detection allows administrators to configure

Failover rEths to report Ethernet device failures based on ping results (ping
Detection Mode failover detection mode or just ping mode). If ping mode is not
configured, such failures are determined solely by the link status of
the Ethernet device (link status failover detection mode, or just link
status mode).
Ping mode uses ICMP (Internet Control Message Protocol)

ECHO_REQUEST and ECHO_REPLY packets to determine the
status of Ethernet devices. Link status mode checks for physical
connectivity with the external Ethernet switch.
You set the parameters required by the failover detection mode on

the eths. Ping mode is activated on the rEth. The default setting is
link mode.
Note: In order for the ping mode failover detection to work

properly, you must have a vSwitch uplinked to the rEth before you
activate ping mode.

for This Task
3-10 PM5.2_BF
Two Steps to There are two major steps to configure rEths:

Configure a rEth
1. Create the rEth.
2. (Optional) Activate ping failover detection mode on the rEth.
Configuring a Creating a rEth

rEth
```To create a new rEth:
2. In the right pane, in the Network Resources page, in the
Redundant Ethernet area, click Create.
Note: If a dialog box that contains the warning Based on

current Ethernet device availability, no new Redundant
Ethernet device can be created appears, it means that there are
no Ethernet ports available. You can only create a rEth with
Ethernet ports that have not been utilized by an existing rEth.
3. In the Create Redundant Ethernet dialog box, you can
configure the new rEth’s settings. Enter appropriate information
in the following fields:
a. Enter a reference Name for the redundant rEth that is unique
to this platform. (See the name(s) of current rEths in the
Redundant Ethernet area.)
b. Specify a Load Balancing Policy for the redundant Eth by
selecting the radio button next to the policy that you want.
If you want this rEth configured to automatically fail over
and fail back to the original configuration if either Ethernet
interface cannot either transmit or receive packets for any
reason, select Pair.
c. If you select Pair, use the Primary Interface pull-down
menu to select Interface 1 or Interface 2 to enable
automatic rEth failback.
If this rEth’s primary (active) Ethernet interface cannot
either transmit or receive packets for any reason, rEth
failover occurs, allowing processing to continue on the
secondary (standby) Ethernet interface.
PM5.2_BF 3-11
With a Pair and Primary Interface configuration, the rEth

configuration automatically fails back to the original
configuration if the uplink is re-established on the primary
Ethernet interface that was down. However, if there is an
interval between the time that the external link is re-
established and the time that the external network is fully
configured, rEth failback can result in an interruption of
service.
To avoid this interruption, disable automatic rEth failback
by choosing none from the Primary Interface menu.
d. To activate implicit multicast flow control for this new rEth,
select the Flow Control check box; to deactivate implicit
multicast flow control, clear the check box.
e. Select the radio buttons of the Ethernet devices that you
want to pair as a rEth.
4. Click Submit.
Modifying a rEth
```To modify an existing rEth:

Redundant Ethernet area, click the name of the rEth to modify.
3. On the Redundant Ethernet page, click Modify.
4. Update the appropriate information in the configurable fields.
Note: You cannot modify an existing rEth’s Name or Ethernet

Devices. To modify these settings, delete the rEth, and then
create a new rEth that uses these settings.
5. Click Submit.
Deleting a rEth
```To delete a rEth:

3-12 PM5.2_BF

Redundant Ethernet area, click Delete.
3. In the Delete Redundant Ethernet dialog box, select the check
box next to the Name of the rEth configuration that you want to
delete.
4. Click Delete to continue.
In the Network Resources page, below the Network
Resources heading, a confirmation appears.
5. Click Cancel to close the dialog box.
Activating Ping ```To specify failover detection mode on a rEth:

Failover
Detection Mode
on a rEth 2. In the right pane, under Redundant Ethernet, click the name of
the rEth for which you want to set Failover Detection Mode.
3. On the Redundant Ethernet page, click Modify.
4. In the Modify rEth Settings dialog box, select either Link or
Ping.
Creating vSwitches
As the final step in configuring external network connectivity, you

create the virtual switches (vSwitches) that connect pServers
through rEths to the external network.
About vSwitches A virtual switch, called a vSwitch, is the software equivalent of a

hardware Ethernet switch. Within an LPAN, a vSwitch is used to
network two or more pServers together, or to provide the pServers
in an LPAN with connectivity to pServers in another LPAN or to
PM5.2_BF 3-13
the external, physical network. You must allocate at least one

vSwitch to each LPAN before any network communication can
occur within the LPAN.
The following conditions apply to vSwitches:

• You use PAN Manager to create vSwitches.
• You can allocate a vSwitch to more than one LPAN. This allows
communication between pServers across LPANs.
• You can create as many as 4096 vSwitches in each platform.
• You must name each vSwitch with a unique name within the
platform. (There is no support for renaming vSwitches after they
are created.)
• Upon creation, all vSwitches are configured to support
communication within and across LPANs. You must separately
configure an uplink on each vSwitch that you want to
communicate with the external network.
• If your network supports VLAN IDs, you must configure a valid
VLAN ID on a vSwitch. You can have only one VLAN ID per
vSwitch.
• Before you delete a rEth, you must first clear any vSwitches’
uplinks to that rEth.
• If you have multiple rEths in pair mode, and have designated
primary Ethernet interfaces on alternate network controller
blades, create and connect your vSwitches in a way to best
balance network traffic across the two blades.
Figure 3.2 illustrates the relationships among a vSwitch, three

pServers, and an LPAN
3-14 PM5.2_BF
Figure 3.2 Single vSwitch Connection
MyLPAN
pServer1 pServer2 pServer3
vSwitch_A
You can allocate multiple vSwitches to a single LPAN to create

multiple broadcast domains within the LPAN. In Figure 3.3, the
vSwitch_A broadcast domain includes pServer1, pServer2, and
pServer3. The vSwitch_B broadcast domain includes pServer3 and
pServer4.
PM5.2_BF 3-15
Figure 3.3 Multiple vSwitch Connections
MyOtherLPAN
pServer1 pServer2 pServer3 pServer4
vSwitch_A vSwitch_B
Figure 3.4 illustrates how you can use a single vSwitch to function
as a bridge between the pServers in two LPANs named QA and
Dev.
3-16 PM5.2_BF
Figure 3.4 vSwitch Connection Between LPANs
QA
QA_Beta QA_final QA_Rel
vSwitch_A
Dev
Dev1 Dev2 Dev3
vSwitch Uplinks Upon creation, all vSwitches are configured to support

communications within and across LPANs. If the pServers
connected to the vSwitch need to access the external network, the
vSwitch must have an uplink attachment. Figure 3.5 illustrates an
externally connected vSwitch.
PM5.2_BF 3-17
Figure 3.5 Externally Connected vSwitch
LPAN2
pServer1 pServer2 pServer3
ext_vSwitch
Uplink to
External Network
External
Network
A vSwitch is configured with the redundant Ethernet connection

(rEth) that it will use to connect to the external network. In order to
take advantage of the redundancy provided by the two network port
locations on a platform, the PAN Administrator must configure the
physical Ethernet connections in redundant pairs. Each pair consists
of an eth (the primary Ethernet interface) and a rEth (the redundant
Ethernet interface). If a vSwitch is connected to a rEth, the network
connectivity is maintained, even if one network port fails. (For
information on configuring rEths, see “Configuring Redundant
Ethernet Interfaces” on page 3-8.)
The vSwitch connections are configured with the uplink name and
VLAN IDs if your network uses a VLAN. Only incoming packets
tagged with the specified VLAN IDs are processed by the vSwitch,
and all outgoing packets are tagged with the specified VLAN ID.
3-18 PM5.2_BF
Note: Before creating any vSwitches for a specific LPAN, you

should consider the basic network topology that the LPAN
Administrator plans to create. Your network topology dictates how
many vSwitches you must create and allocate to the LPAN. Consult
the Network Administrator at your site for more information.

for This Task
Creating a When creating a vSwitch for external connections, you specify an

vSwitch uplink, which defines external connectivity outside of the platform.
If the vSwitch will only be used for internal connections between
pServers, you do not specify an uplink.
Creating a New vSwitch
```To create a new vSwitch:

vSwitches area, click Create.
3. In the Create vSwitches dialog box, enter appropriate
information in the following fields:
• Enter the Name of a new vSwitch.
In the Uplink section,
• Select the radio button next to a rEth if you want this
vSwitch to communicate with an external network.
• Select the radio button next to Not uplinked to make the
vSwitch only available for connectivity within a platform.
Selecting Not uplinked shades the other configuration
fields.
• Enter a valid VLAN ID for VLAN-tagged traffic to flow
over this vSwitch. Leave this field blank if you want only
non–VLAN-tagged network traffic to flow over this
vSwitch’s rEth.
PM5.2_BF 3-19
4. Click Submit.
The new vSwitch appears in the vSwitch area.
Deleting a vSwitch
```To delete a vSwitch:

vSwitches area, click Delete.
3. In the Delete vSwitches dialog box, select the check box next to
the vSwitch name that you want to delete.
4. Click Delete to continue, or click Cancel to close the dialog box.
Modifying a vSwitch
```To modify an existing vSwitch:

2. In the right pane, on the Network Resources page, in the
vSwitches area, in the Name column, select the vSwitch that
you want to modify.
3. On the vSwitch vSwitchname page, click the Edit button.
4. In the Edit vSwitch uplink dialog box, in the Uplink section,
enter appropriate information in the following fields:
• Select the radio button next to a rEth if you want this
vSwitch to communicate with an external network.
• Select the radio button next to Not uplinked to make the
vSwitch only available for connectivity within a platform.
Selecting Not uplinked shades the other configuration
fields.
• Enter a valid VLAN ID for VLAN-tagged traffic to flow
over this vSwitch. Leave this field blank if you want only
non–VLAN-tagged network traffic to flow over this
vSwitch’s rEth.
3-20 PM5.2_BF
Chapter 4
Managing System Access
This chapter describes creating PAN Manager users and assigning

them to roles.
In a typical Linux system, you might have the groups of admin and
worker. For a specific object, such as a file, users in the admin
group might have read and write privileges, and users in the worker
group might have only read privileges. PAN Manager uses a similar
system to establish access control for PAN administration. Instead
of groups, PAN Manager users are assigned roles to control their
access permissions.

• Establishing Access Control
• Creating Users and Accounts
• Assigning Roles to PAN Manager Users
• Managing Users and Accounts
PM5.2_BF 4-1
Establishing Access Control
The cBlade software installation creates one initial user account

with the user ID of root. This user is in the PAN Administrator role
and has full permissions for all tasks in the PAN. The PAN
Administrator takes the following three major steps to establish
access control for PAN and LPAN administration:
1. Create LPANS, as described in Chapter 5, “Creating LPANs”.
Note: If desired, you can create the PAN Manager users and
Linux accounts (Step 2) before creating LPANs. However, since
the roles are available only after the LPANs are created, you
must create LPANs before you assign users to roles (Step 3).
2. Create PAN Manager users and Linux user accounts.
3. Assign roles to users.
The PAN Administrator can modify or delete accounts, users, and

roles to suit changing conditions. See “Managing Users and
Accounts” on page 4-10.
Creating Users and Accounts
PAN Manager uses both Linux user accounts and its own defined
users to grant access to the PAN. This section provides guidelines
and procedures for creating accounts and users.
About Linux In a PAN, there are two distinct types of accounts:

Accounts and
• Linux user accounts for OS access on the cBlades.
PAN Manager
Users • PAN Manager “users” for PAN Manager access.
4-2 PM5.2_BF
You can manage Linux user accounts with either PAN Manager or
other account management tools, but not both. PAN Manager is a
convenient tool for simultaneously managing the user accounts on
both cBlades. PAN Manager automatically replicates the accounts
on the second cBlade, so you do not need to create them on both
cBlades. However, you might want to continue to use third-party
account management utilities if, for example, user accounts already
exist in a database. If you do not plan to use PAN Manager to
manage Linux accounts, see “Disabling Linux Account
Management” on page 4-5.
You must observe the following guidelines when creating accounts

and users:
• PAN Manager users must have Linux user accounts on both
cBlades. Issue these accounts with discretion, as they have
security implications.
Note: If you use PAN Manager to manage Linux accounts, you

create the Linux account as part of creating the PAN Manager
user. If you don’t use PAN Manager to manage Linux accounts,
you must create the Linux accounts separately before creating
the PAN Manager users.
• A Linux account must have the same name as its corresponding
PAN Manager user.
• Only PAN Administrators can create Linux accounts (using
PAN Manager) or PAN Manager users.
• You must assign a Linux account and PAN Manager user to the
personnel that administer the PAN and LPANs at your site. You
can assign just a Linux account to the personnel that need direct
access to the cBlades but not access to the PAN and LPANs.
• You must assign each PAN Manager user one or more roles
(PAN Administrator, LPAN Administrator, LPAN Operator,
and LPAN Monitor). For information on roles, refer to
“Assigning Roles to PAN Manager Users” on page 4-6.
PM5.2_BF 4-3
About PAN Manager uses the Linux PAM (Pluggable Authentication

Authentication Module) to authenticate users by password. For more information
on PAM, see the Linux PAM information at the Public Linux
Archive (http://www.kernel.org/pub/linux/libs/pam/
index.html).

for This Task
Creating Users ```To create a PAN Manager user account:

and Accounts
1. In the left pane, click Security.
2. In the right pane, on the PAN Security page, in the Users area,
click the Create button.
3. In the Create new User dialog box:
a. Enter the user name of the new PAN Manager user.
b. Enter this person’s actual name in the Full Name field.
c. In the Title and Department fields, enter information about
this person’s position and the organization in which they
work.
d. Enter the user’s e-mail address, in the form
bob@mycompany.com, in the Email field.
e. Enter the new password for the user’s PAN Manager
account in the Password and Confirm fields.
4. If there is currently no Linux user account for this person, and
you want to create one now, select the System Account check
box.
Note: Allowing PAN Manager to manage Linux user accounts

on the Control Blades prevents you from using other account
management utilities to manage those accounts.
5. To assign a PAN Manager administrative role to the new
PAN Manager user, in the Roles area, select a role from the
Select Role pull-down list, and then click the Add button.
4-4 PM5.2_BF
The role you select now appears under Assigned Roles. (To
deselect a role, select the check box to the left of the role, and
then click the Remove button.)
6. Click Submit.
Creating User ```To create an operating system group:

Groups
2. In the right pane, in the PAN Security page, in the System User
Groups area, click Create.
3. In the Create new User Group dialog box, enter the group
name in the space provided. (Linux automatically assigns a
group ID to the group name that you specify.)
4. Click Submit.
The new group and its group ID appear in the System User
Groups area.
Disabling Linux If you use standard Linux commands or a third-party utility to

Account manage Linux accounts, note the following restrictions:
Management
• You cannot use PAN Manager to add, modify, or remove Linux
user accounts.
• You need to disable PAN Manager account management, as
described in the following procedure.
Note: If you disable or enable account management during a

PAN Manager session, you must restart PAN Manager for the
change to take effect.
• You need to create separate accounts on each cBlade.
```To use a third-party account management tool to manage

Linux user accounts on the cBlades:
1. Configure both cBlades as clients of the account management
tool. (Refer to the product documentation for details.)
PM5.2_BF 4-5
2. In PAN Manager, click a PAN in the left pane, and then click the
Accounts button in the right pane.
3. Clear the check box in the PAN Account Control dialog box.
This disables the ability for PAN Manager to manage user
accounts.
4. Restart PAN Manager so the change takes effect.
Enabling Linux ```To configure PAN Manager to control user accounts on the
Account cBlade:
Management
configure.
2. In the right pane, in the Current PAN area, click the Accounts
button.
3. (Optionally) In the PAN Account Control dialog box, click
PAN Manager controls cBlade operating system user
accounts, to allow PAN Manager to control the user accounts
and groups at an operating system level.
4. Click Submit.
Assigning Roles to PAN Manager Users
Only PAN Manager users with appropriate privileges can

administer the PAN. Each user is associated with a role or set of
roles, and each role, in turn, is associated with an administrative
domain in the PAN. A role defines what actions are allowed on
what resources in the domain.
About PAN Manager supports the following administrative domains:

Administrative
Domains PAN — The entire Processing Area Network, including all LPANs.
4-6 PM5.2_BF
LPAN — The logical elements associated with a specific LPAN,

such as pServers.
About User The PAN administrative domain has only the Administrator role.
Roles The LPAN administrative domain has the following predefined
roles:
Administrator — Provides configuration, control, and monitor

permissions.
Operator — Provides control and monitor permissions.
Monitor — Provides monitor (view-only) permission.
Roles are collections of permissions. A user has the aggregate set of

permissions from all the roles to which he or she is assigned.
A minimum of four possible roles exist for each PAN. As you add
LPANs, the associated roles are available for user assignment.
Table 4.1 shows the roles and the tasks allowed.
Table 4.1 Roles and Tasks
Role Tasks
PAN Administrator Set up and configure all platforms.

Create PAN Manager users.
Create LPANs.
Start and stop PAN components.
Monitor PAN components.
Configure application control and high
availability.
Set up and configure elements for the
platform.
Start and stop the platform.
Monitor the platform.
PM5.2_BF 4-7
Role Tasks
LPAN Administrator Configure and modify the LPAN.

Configure application control and high
availability.
Start and stop pServers in the LPAN.
Monitor the LPAN.
LPAN Operator Start and stop pServers in the LPAN.

Monitor the LPAN.
LPAN Monitor Monitor the LPAN.
Administrator, Operator, and Monitor roles are available for each

LPAN in the PAN.
Note: PAN Manager automatically creates three roles for each

LPAN, but you are not required to assign a user to each role. Use
only the roles that you need to administer your system.
About Each predefined role provides a set of privileges that allows the
Permissions following actions:
Configuration — Create, configure, assign, and remove resources.
Control — Start and stop system components.
Monitor — View the status of system components.
Guidelines for Follow these guidelines when assigning roles to PAN Manager
Assigning Roles users:
• LPAN roles are created when an LPAN is created. You need to
create the LPAN before you can assign roles for administering
it.
• LPAN Administrators only have access to functions within their
LPAN.
4-8 PM5.2_BF
• The PAN Administrator should assign at least one user to the

LPAN Administrator role for each existing LPAN.
• You can assign users to multiple roles. Their set of permissions
is an aggregation of the permissions contained in their assigned
roles.

for This Task
Assigning Roles ```To assign the administrative roles to a PAN Manager user:
to Users
1. In the left pane, click the name of the PAN or LPAN that you
want to configure.
2. In the right pane, click Domain Settings.
3. On the Domain Settings page, in the Users area, click Assign.
4. In the Assign User to Domain dialog box, use the pull-down list
to select a user, then select the radio button next to a security
role.
5. Click Submit.
```To remove an administrative role assignment from a

PAN Manager user:
want to configure.
3. On the Domain Settings page, in the Users area, click
Unassign.
4. In the Unassign User from Domain dialog box, select the
check box next to the user that you want to unassign from all
security roles in this administrative domain.
5. Click Unassign.
PM5.2_BF 4-9
Managing Users and Accounts
You can carry out the following tasks to manage PAN Manager
users and Linux accounts:
• Modify PAN Manager users
• Modify Linux accounts (if you manage Linux accounts with
PAN Manager)
• Delete PAN Manager users
• Delete Linux accounts (if you manage Linux accounts with
PAN Manager)

for This Task
Modifying Users ```To modify a PAN Manager user’s information:

and Accounts
Note: If PAN Manager is not configured to manage user
accounts, contact your PAN Administrator to change your
PAN Manager user password, or any user information that is
read-only.
2. In the right pane, on the PAN Security page, in the Users area,
in the Name column, click the name of the PAN Manager user
that you want to modify.
3. On the User username page, do one or more of the following:
• To change the person’s name, title, department, or e-mail
address, click Modify. In the Modify PAN Manager User
dialog box, make any appropriate changes, and then click
Submit to save your changes.
4-10 PM5.2_BF
• To change the PAN Manager password for this user, click

Change Password. In the Change User Password dialog
box, enter the new password, and then confirm the new
password. Click Submit to save your changes.
• To modify the Linux user account information that is
associated with this user, under cBlade system account
information for this user, click Modify. In the Modify
cBlade System Account dialog box, modify one or more of
the following: User ID, Group Name, Default shell, and
Home Directory. Click Submit to save your changes.
• To delete the Linux user account associated with this user,
under cBlade system account information for this user,
click Delete.
Note: Because users must have a Linux account to login, this

user will no longer be able to use PAN Manager after this
operation.
To delete all traces of the user’s Linux user account from the
cBlades, select the Delete all traces... check box.
Click Submit to save your changes.
• To modify the security roles that are currently assigned to
the user, in the Security Roles area, click Assign/Unassign.
In the Assign/Unassign Security Roles dialog box, to
assign one or more security roles to the user, select the check
box next to each role; to unassign one or more security roles
from the user, clear the appropriate check box(es). Click
Submit to save your changes.
```To change your PAN Manager user information:
Note: If PAN Manager is not configured to manage user

accounts, contact your PAN Administrator to change your
PAN Manager user password, or any user information that is
read-only.
1. In PAN Manager, at the top of the left pane, next to Logged in
as:, click your user name.
2. On the username page, enter your name in the Full Name field.
PM5.2_BF 4-11
3. Enter your email address, in the form bob@mycompany.com.

4. In the Title field, enter information about your position at your
company.
5. In the Department field, enter the name of your organization
within your company.
6. If PAN Manager is configured to manage user accounts, you can
modify your PAN Manager user password. To change your
password:
a. Enter your password in the Current field.
b. Enter your new password in the field provided.
c. Enter your new password again in the Confirm New field.
7. To save your changes, click Submit.
Deleting Users ```To delete a PAN Manager user:

and Accounts
2. In the right pane, in the PAN Security page, in the Users area,
click Delete.
3. In the Delete Users dialog box, select the check box next to the
PAN Manager user(s) that you want to delete:
• To delete the operating system account associated with this
user, select the Delete system account for each selected
user check box.
• To leave the operating system user account intact on both
cBlades, clear the Delete system account for each selected
user check box. (Deleting the system account does not
remove the user’s Linux default directory or the /etc/group
and /etc/passwd entries on the cBlades.)
4. To remove all traces of this user’s Linux account on the cBlades,
select the Recursively check box.
5. Click Delete.
The user no longer appears in the Users area.
4-12 PM5.2_BF
Deleting User ```To delete an operating system group:

Groups
2. In the right pane, in the PAN Security page, in the System User
Groups area, click Delete.
3. In the Delete User Groups dialog box, select the group(s) that
you want to delete. (Reminder: You cannot delete an operating
system group if it contains members.)
4. Click Delete.
The group or groups no longer appear in the System User
Groups area.
PM5.2_BF 4-13
4-14 PM5.2_BF
Chapter 5
Creating LPANs
This chapter describes how to use PAN Manager to create and

configure a Logical Processing Area Network (LPAN). Many of the
tasks are similar to configuring conventional hardware, although
the hardware is distributed. Creating LPANs is very similar to
assembling parts, such as disks and processors, to build a computer.

• Creating and Allocating Resources to an LPAN
• Configuring Disks for Persistent Reservations
• Creating Global and Local Pools
• Booting the LPAN’s pServers
• Modifying an LPAN’s Resources
PM5.2_BF 5-1
Creating and Allocating Resources to an LPAN
About LPANs A Logical Processing Area Network (LPAN) is a collection of PAN

resources—pBlades, storage devices, and virtual network
resources—that are allocated as a group. You use PAN Manager
software to configure these resources into one or more pServers.
Typically, an LPAN represents the computing resources that are
devoted to a single purpose or organization.
The following general conditions apply to all LPANs:

• An LPAN is a named collection of resources. You must use
PAN Manager to configure the resources in an LPAN into one
or more pServers.
• You must add a disk to the PAN before it can be allocated to an
LPAN.
• You can only allocate a disk to one LPAN at a time.
• You can only allocate a pBlade to one LPAN at a time.
• You can only allocate a fibre channel tape device to one LPAN
at a time.
• On BladeFrame BF400 S2, the PAN may have up to 2000 SCSI
devices. On BladeFrame BF200, the PAN may have up to 756
SCSI devices.
• A user who wants to allocate resources to an LPAN must have
the PAN Administrator role.
• Each LPAN must have a unique name within the PAN. There is
a limit of 32 legal characters in a name.
• All the physical and virtual resources required to configure a
pServer must reside in the same LPAN as the pServer, with the
exception of blades in global pools.
• There can be up to 75 LPANs in a PAN.
5-2 PM5.2_BF
Creating LPANs
• You do not need to immediately configure the resources in an

LPAN into pServers. When you allocate the resources to an
LPAN, those resources become unavailable to other LPANs and
global pools.
• The pServers in separate LPANs can simultaneously mount a
cBlade’s DVD-ROM if it has been enabled for the LPANs. This
means that one pServer can eject the disc from the drive, leading
to other pServers getting I/O errors and/or partial directory
listings.
Allocating Each LPAN must contain enough primary and failover pBlades to
pBlades support all the running pServers in the LPAN. Each pServer must
have a primary pBlade. A failover pBlade automatically assumes
all processing if the primary pBlade fails. Allocating one or more
failover pBlades is optional.
On BladeFrame BF400 S2, the pBlades are named p1 through p24,

numbered from bottom to top.On BladeFrame BF200, the pBlades
are named p1 through p6, from left to right.
Allocating Disks You must first add Storage Area Network (SAN) devices to the
and Tapes PAN before they are allocated to LPANs. PAN devices (disks and
fibre channel tape devices) are those that are accessible by the
PAN. You can automatically or manually add disks and tapes,
which are discovered by a scan, to the PAN. PAN disks and tapes
are visible to the PAN Administrator until they are removed from
the PAN.
Removing a SAN device makes it unavailable to the PAN.

However, it is still visible as a “discovered” device unless that
Administrator purges it.
SAN devices are allocated to LPANs and configured with pBlades

to create pServers.You must allocate enough external disk storage
for each pServer that will be in the LPAN. The storage is used for
PM5.2_BF 5-3
each pServer’s root file system and swap space, as well as disk
space required for applications and data. A tape device is typically
used for backing up data from a pServer.
Note: By default, PAN Manager enables all disks with SCSI-2

reservations, which allow a single booted pServer to access a single
disk. To configure a disk for SCSI-3 reservations, which allow
access from multiple pServers, see “Configuring Disks for Persistent
Reservations” on page 5-19.
If Network Attached Storage (NAS) devices or a Network File

System (NFS) is available on the network, it is not allocated as an
LPAN resource. The NFS is exported to the individual pServers.
On the pServers, use the mount command to make the file systems
accessible. You must know the host name or IP address and the
name of the exported file system.
The following general attributes apply to all allocated storage

devices:
• Each pServer should have its own disk on the SAN.
• You can allocate up to 256 SCSI devices to each Linux/Unix
pServer (of these, 217 can be disks).
• You can allocate up to 128 devices to each Windows pServer
(including 2 media drives).
• A pServer can use both SAN and NFS.
• PAN Manager supports arbitrated loop and switched fabric SAN
protocols.
• All SAN devices must be attached using a multimode optical
cable.
• The PAN Administrator adds SAN disks to the PAN. SAN disks
have a SCSI ID, but might not be partitioned.
• The PAN Administrator adds tape devices to the PAN. Tape
devices have a SCSI ID.
5-4 PM5.2_BF
Creating LPANs
• Within a PAN, disks and tape devices can be allocated to a

single LPAN and assigned to one or more pServers in that
LPAN. Each pServer can have more than one disk and more
than one tape device assigned to it.
• A physical disk can be associated with multiple underlying
subpaths; each subpath has its own SCSI ID and is associated
with one of the cBlades. By default, PAN Manager displays a
single SCSI ID for each physical disk.
• Disks can be removed from the PAN as long as the PAN is not
set to automatically import discovered disks.
• Disks can be purged from the system (i.e., become not
discoverable). The PAN Administrator may wish to purge a disk
from the system if the physical disk has been removed from the
SAN or if the disk will be assigned a different ID number.
The naming conventions for SCSI IDs are as follows, for a SCSI ID
of (a.b.c.d):
a – Host bus adapter (HBA) number of the driver referencing the
physical HBAs.
b – Channel ID on the host.
c – Target ID of devices for the SAN.
d – Logical unit number (LUN).
Accessing DVD- All DVD-ROM drives are automatically allocated to the LPAN.
ROM Drives Because the DVD-ROM drives are shared across LPANs, the PAN
Administrator enables and disables them as they are needed. The
LPAN or PAN Administrator can enable and disable DVD-ROM
drives at the pServer level.
Registering A virtual CD-ROM drive (VCD) is automatically attached to each

Virtual CD-ROMs pServer at the time the pServer is created. The VCD enables the
pServer to access an ISO image that resides on the cBlades as if it
were an image on a physical CD-ROM.
PM5.2_BF 5-5
To prepare this capability, the PAN or LPAN Administrator

“registers” one or more ISO images with PAN Manager, which
automatically makes them available to all LPANs and all pservers.
The registration process entails copying the image(s) via NFS onto
one cBlade and naming the image, and optionally supplying image
type and description.
Caution: Once an image is registered with PAN Manager, it is

available to all pServers in the PAN. Do not register an image if you
wish to restrict its use.
After an image is registered, you can later modify it by changing its

display name and its user-supplied type and description. In
addition, you cause replace a registered image file with another.
Allocating A virtual switch, or vSwitch, is the software equivalent of a

vSwitches hardware Ethernet switch. Within an LPAN, a vSwitch is used to
network two or more pServers together, or to provide the pServers
in an LPAN with connectivity to pServers in another LPAN or to
the external, physical network. You must allocate at least one
vSwitch to each LPAN before any network communication can
occur within the LPAN.
The following conditions apply to vSwitches:

• Only users in the PAN Administrator role can create vSwitches.
• You can allocate a vSwitch to more than one LPAN. This allows
communication between pServers across LPANs.
• If you change the Ethernet connection configuration, you must
reflect those changes in the vSwitch(es) associated with the
Ethernet connection. For information on configuring Ethernet
Connections, see “Configuring Ethernet Interfaces” on
page 3-5.
• If you want to delete a rEth (redundant Ethernet interface), you
must first clear any vSwitches’ uplinks to that rEth. For
information on creating rEths, see “Configuring Redundant
Ethernet Interfaces” on page 3-8.
5-6 PM5.2_BF
Creating LPANs
The vSwitches can be internal, providing communication only

between pServers on a platform, or they can have an uplink to
connect pServers to the network outside of the platform.
Assigning The PAN Administrator should assign at least one LPAN

Administrators Administrator to the LPAN. The roles of Operator and Monitor are
also available for each created LPAN. The PAN Administrator can
assign these roles to users. (The PAN Administrator has full
privileges and can elect to administer the LPAN. In this case, he
does not have to assign himself to the LPAN Administrator role.)
Each user with administrative privileges must have a Linux user

account on the cBlades, a PAN Manager user account, and one or
more PAN Manager roles. For further information, see Chapter 4,
“Managing System Access”.

for This Task
Steps to Allocate These are the major steps for creating and allocating resources to an
an LPAN LPAN:
1. Discover the available resources.
2. Create an LPAN.
3. Allocate the pBlades.
4. Allocate disk resources.
5. Enable the DVD-ROM drive(s).
6. Allocate tape devices (optional).
7. Allocate the vSwitches.
Discovering the ```To list the currently available resources:

Available
1. In the left pane, select the triangle next to Resources to display
Resources
the types of resources and click one of the following:
PM5.2_BF 5-7
• Blades
• Pools
• Disks
• Tapes
• DVD-ROMs
• Networking
The corresponding page is displayed in the right pane.
Scanning for New PAN Disk Resources
```To scan for new PAN disk resources:

1. In the left pane, click Resources > Disks.
2. In the right pane, at the top of the SCSI Disks page, click the
Scan SAN button.
Any newly discovered PAN disk resource(s) appear in the
Discovered Disks area.
Automatically Importing PAN Disk Resources
```To enable or disable auto-importing a disk into the PAN:

1. In the Discovered Disks area, click the Auto-Import button.
2. In the Auto-Import to PAN dialog box, select or clear the
Auto-Import Discovered Disks to PAN check box. (Selecting
the check box ensures that any disk that PAN Manager discovers
is automatically imported into the PAN; clearing the check box
means that you must add manually any disks that you want to
add to the PAN.)
3. Click Submit to complete the modification, or Cancel to close
the dialog box.
Adding PAN Disk Resources
```To manually add a discovered disk resource to the PAN:

1. In the PAN Disks area, click the Add button.
5-8 PM5.2_BF
Creating LPANs
2. In the Add disk(s) to PAN dialog box, select the SCSI ID for
each disk that you want to add to the PAN.
3. Click Submit.
The added PAN disk resource(s) moves from the Discovered
Disks area to the PAN Disks area.
Editing a PAN Disk Resource Description
```To edit a PAN disk resource description:

1. From an appropriate configuration page, click the SCSI ID of
the disk whose description you want to modify.
2. On the SCSI ID page, click the Edit button.
3. In the Edit Disk dialog box, update the Description field.
4. Click Submit to save your work, or click Cancel to close the
dialog box.
Removing PAN Disk Resources
```To manually remove one or more discovered disk resources

from the PAN:
Note: You cannot manually remove a PAN disk resource when

the PAN’s Discovered Disks Auto-Import configuration is
selected.
1. In the PAN Disks area, click the Remove button.
2. In the Remove disk(s) from PAN dialog box, select the SCSI
ID for each disk that you want to remove from the PAN.
3. Click Submit.
The removed PAN disk resource(s) moves from the PAN Disks
area to the Discovered Disks area.
PM5.2_BF 5-9
Removing and Purging PAN Disk Resources
```To permanently remove one or more disk resources from the

PAN (so that it cannot be “rediscovered”):
Note: You cannot purge a PAN disk resource when the PAN’s
Discovered Disks Auto-Import configuration is selected.
2. In the right pane, at the top of the SCSI Disks page, click Scan
SAN.
This action ensures that PAN Manager recognizes all subpaths
to the disks to be purged.
3. In the PAN Disks area, click Remove.
4. In the Remove disk(s) from PAN dialog box, do the following.
a. Select the SCSI ID for each disk that you want to remove
from the PAN.
b. Select the Purge disk(s) after removal from PAN check
box.
5. Click Submit.
The PAN Disks area no longer displays the disk(s).
Purging Discovered Disk Resources
```To permanently remove one or more discovered disk

resources (so that it cannot be “rediscovered”):
Note: You cannot purge a Discovered Disk resource when the

PAN’s Discovered Disks Auto-Import configuration is
selected.
2. In the right pane, at the top of the SCSI Disks page, click Scan
SAN.
This action ensures that PAN Manager recognizes all subpaths
to the disks to be purged.
5-10 PM5.2_BF
Creating LPANs
3. In the Discovered Disk (Not in PAN) area, click the Purge

button.
4. In the Purge Discovered Disk(s) not in the PAN dialog box,
select the SCSI ID for each disk that you want to remove
completely.
5. Click Submit.
The Discovered Disk (Not in PAN) area no longer displays the
disk(s).
Scanning for New PAN Tape Resources
```To scan for new PAN tape devices:

1. In the left pane, click Resources > Tapes.
2. In the right pane, at the top of the SCSI Tapes page, click the
Scan SAN button.
Any newly discovered PAN tape device resource(s) appear in
the Discovered Tapes area.
Automatically Importing PAN Tape Devices
```To enable or disable auto-importing a tape device into the

PAN:
1. In the Discovered Tapes area, click the Auto-Import button.
2. In the Auto-Import to PAN dialog box, select or clear the
Auto-Import Discovered SAN devices to PAN check box.
(Selecting the check box ensures that any tape device
PAN Manager discovers is automatically imported into the
PAN.)
3. Click Submit to complete the modification, or Cancel to close
the dialog box.
PM5.2_BF 5-11
Viewing PAN Tape Devices
```To view the PAN’s tape device resources:

1. In the left pane, click Resources > Tapes. In the right pane, in
the SCSI Tapes page, in the PAN Tapes area, the current PAN
tape device resources are displayed.
Manually Adding Discovered Tape Devices
To manually add a discovered tape device to the PAN:

1. In the PAN Tapes area, click the Add button.
2. In the Add tape(s) to PAN dialog box, select the SCSI ID for
each tape device that you want to add to the PAN.
3. Click Submit.
The added PAN tape device(s) moves from the Discovered
Tapes area to the PAN Tapes area.
Editing a PAN Tape Device Description
To edit a PAN tape device’s description:

the tape device whose description you want to modify.
2. On the SCSI Tape tape_device_name page, click the Edit
button.
3. In the Edit Tape dialog box, update the Description field.
dialog box.
5-12 PM5.2_BF
Creating LPANs
Manually Removing Discovered Tape Devices
```To manually remove a discovered tape device from the PAN:
Note: You cannot manually remove a PAN tape resource when

the PAN’s Discovered Tapes Auto-Import configuration is
selected.
1. In the PAN Tapes area, click the Remove button.
2. In the Remove tape(s) from PAN dialog box, select the SCSI
ID for each tape device that you want to remove from the PAN.
3. Click Submit.
The removed PAN tape device(s) moves from the PAN Tapes
area to the Discovered Tapes area.
Creating an ```To create an LPAN:

LPAN
1. In the left pane, select LPANs.
2. In the LPANs page, click the Create button.
3. In the Create LPAN dialog box, enter the name of the LPAN,
optionally select the check box next to Proceed directly to
LPAN page after creation, and then click Submit to create the
LPAN.
Depending on your preference, the LPANs page displays all the
currently existing LPANs including the new one, or the LPANs
LPANname page displays the configuration page for your
newly created LPAN.
```To modify an existing LPAN:

1. Check to be sure that your changes will not negatively impact
any physical resources or applications currently in use.
2. Click the LPAN name.
This displays the LPAN’s configuration.
PM5.2_BF 5-13
```To delete an existing LPAN:

1. In the left pane, select LPANs.
2. In the LPANs page, click the Delete button.
3. In the Delete LPANs dialog box, select the check box next to the
LPAN that you want to delete.
4. Click Delete.
PAN Manager returns to the LPANs page. The deleted LPAN
no longer appears.
Allocating ```To allocate a pBlade to an LPAN:

pBlades
1. In the left pane, click LPANs > LPANname.
2. In the right pane, in the LPANs LPANname page, in the
pBlades area, click the Add button.
3. In the Add pBlades to LPAN dialog box, do one or both of the
following:
• Select the check box next to each pBlade that you want to
allocate to this LPAN, and click Add.
• You may manually enter a pBlade if you know a pBlade will
become available in that slot. To do this, in the Manual
Entry field, enter the pBlade name in the form
platform_name/px where x is the number of the pBlade
slot.
The pBlade appears in the Blades area.
```To remove a pBlade from an LPAN:

pBlades area, click the Remove button.
3. In the Remove pBlades from LPAN dialog box, select the
check box next to each pBlade that you want to remove from this
LPAN.
4. Click Remove.
5-14 PM5.2_BF
Creating LPANs
The pBlade no longer appears in the Blades area.
```(PAN Administrators only) To authorize an LPAN to acquire

pBlades from the global (PAN-wide) pool:
2. In the right pane, in the LPANs LPANname page, in the Local
pBlade Pool area, click the Global Pool Access button.
3. In the Configure Global Pool Access dialog box, do either of
the following:
• To enable global pool access for failover blades, select the
Access check box next to the pool name(s) that you want to
obtain blades from.
• To enable global pool access for primary blades, select the
Boot check box next to the pool name(s) that you want to
obtain blades from.
4. Click Submit.
Any pServer in the LPAN can appropriately access the global
pool.
Allocating Disk ```To allocate a disk to an LPAN:

Resources
2. In the right pane, in the LPANs LPANname page, in the SCSI
Disks area, click the Add button.
3. In the Add SCSI Disks to LPAN dialog box, select the check
box next to each SCSI disk that you want to allocate to this
LPAN, and click Add.
The SCSI disk appears in the SCSI Disks area.
```To remove a disk from an LPAN:

(You can remove a disk only if it is neither connected to a
pServer nor associated with any high-availability file system
resources.)
PM5.2_BF 5-15
2. In the right pane, in the LPANs LPANname page, in the SCSI

Disks area, click the Remove button.
3. In the Remove SCSI Disks dialog box, select the check box
next to each SCSI disk that you want to remove from this LPAN.
4. Click Remove.
The SCSI disk no longer appears in the SCSI Disks area.
Enabling the ```To enable DVD-ROM access for an LPAN:

Physical DVD-
(For pServers in an LPAN to access a DVD-ROM drive, a PAN
ROM Drive
Administrator must also enable DVD-ROM access for the
LPAN as a whole.)
2. In the right pane, in the LPAN LPANname page, in the DVD-
ROMs area, click the Enable/Disable button.
3. In the Enable/Disable DVD-ROM Access dialog box, select
the check box next to each DVD-ROM drive that you want to
make available to the pServers in the LPAN.
4. Click Submit.
Registering ```To register an image as a virtual CD-ROM:

Images as Virtual
Registering an image copies it via NSF to the cBlades and makes
CD-ROMs
it available to every pServers’ virtual CD-ROM drive.
1. On the PAN>PANname page, scroll to the Media Images area
and click Import.
2. In the Create Media Image dialog, fill in the following fields
for the image you wish to register as a virtual CD-ROM:
• Name: a display name
• Source: the full pathname of the image where it currently
resides
• (Optional) Type:
• (Optional) Description:
5-16 PM5.2_BF
Creating LPANs
3. Click Submit.
Modifying Virtual ```To modify an image registered as a virtual CD-ROM:

CD-ROM Images
An image file can be modified if it is not loaded onto any pServer
or if it is loaded onto a shutdown pServer. An image file cannot be
modified if it is loaded onto a running pServer.
1. In the left pane, click the name of the PAN that contains the
image you wish to modify.
2. In the right pane, in the Current PAN > Media Images area,
click the name of the image you wish to modify.
3. On the Media Image page, click Modify.
4. In the Modify Media Image dialog box, edit any of the
following fields:
• Name: Specify or change the display name.
• Source: Select one of the following:
– Use current source media image (no changes): If
selected, PAN Manager continues to use the media
image currently registered at that location.
– cBlade file: If selected, you must specify the full
directory path on the cBlades of an image file. The
specified file replaces the image at the registered
location.
– If the image is loaded onto a (shutdown) pServer, check
the force modify checkbox.
• (Optional) Type: Add or change descriptive text about the
type of the media image.
• (Optional) Description: Add or change descriptive text for
the media.
5. Click Submit.
PM5.2_BF 5-17
Allocating Tape ```To allocate a tape to an LPAN:

Devices
2. In the right pane, in the LPAN LPANname page, in the SCSI
Tapes area, click the Add button.
3. In the Add SCSI Tapes to LPAN dialog box, select the check
box next to each SCSI tape that you want to allocate to this
LPAN, and click Add.
The SCSI tape appears in the SCSI Tapes area.
```To remove a tape from an LPAN:

(You can remove a tape only if it is not connected to a pServer.)
2. In the right pane, in the LPAN LPANname page, in the SCSI
Tape area, click the Remove button.
3. In the Remove SCSI Tape dialog box, select the check box next
to each SCSI tape that you want to remove from this LPAN.
4. Click Remove.
The SCSI tape no longer appears in the SCSI Tapes area.
Allocating ```To allocate a vSwitch to an LPAN:

vSwitches
vSwitches area, click the Add button.
3. In the Add vSwitch to LPAN dialog box, select the check box
next to the vSwitch that you want to allocate to this LPAN, and
click Add.
The vSwitch now appears in the vSwitches area.
5-18 PM5.2_BF
Creating LPANs
```To remove a vSwitch from an LPAN:

(You can remove a vSwitch only if it is neither connected to a
pServer nor associated with any high-availability network
resources.)
vSwitches area, click the Remove button.
3. In the Remove vSwitches dialog box, select the check box next
to the vSwitch that you want to remove from this LPAN.
4. Click Remove.
The vSwitch no longer appears in the vSwitches area.
Configuring Disks for Persistent Reservations
By default, PAN Manager enables all disks with reserve/release

reservations as defined by the SCSI-2 standard, which allow only
one booted pServer at a time to access a given disk. You can enable
SCSI-3 persistent reservations for a disk, thus allowing more than
one pServer to access it.
Enabling SCSI-3 reservations disables the default SCSI-2

reservations for that disk.
About SCSI-2 Reserve/release SCSI-2 reservations prevent unwarranted access to

Reserve/Release a pServer’s SCSI devices by other pServers. Some applications that
Features you install on pServers may require SCSI reservations.
The platform’s cBlade enforces the reservation with respect to I/O

from other pServers. Because the cBlade does not forward reserve
(and release) commands to the device itself, the device reservation
is effective only within the platform. This allows the cBlade to
PM5.2_BF 5-19
continue to load-balance among all the paths to the device even

when the device is reserved. This results in better performance from
some storage arrays in the presence of a SCSI-2 reservation.
About SCSI-3 A persistent reservation is an association between a pServer

Persistent running on any pBlade and a SAN disk device. The SCSI-3
Reservations persistent reservation feature allows more than one booted pServer
to simultaneously access the same disk.
To use the persistent reservations feature on any disk, you must use
the array vendor’s command set to enable persistent reservations
for that disk. Refer to your array vendor’s documentation for details
about enabling persistent reservations.
For the persistent reservation feature, PAN Manager lists both the
pServer registrations and reservations associated with the disk. One
or more pServers may be configured to access the disk.
Supported Normally, you enable persistent reservations for the disk first, and
Configurations then add the disk to a pServer configuration. Therefore, make sure
and Restrictions that the pServer supports persistent reservations before adding the
disk to its configuration.
Specifically, PAN Manager supports SCSI-3 persistent reservations

only for the following pServers and applications:
• SLES pServers
• Veritas Cluster File System
See PAN Manager Release Notes for the latest supported

configurations for SCSI-3 persistent reservations.
Caution: PAN Manager does not prevent administrators from

enabling SCSI-3 persistent reservations on unsupported pServers. If
you enable SCSI-3 persistent reservations for a disk on an
unsupported pServer, PAN Manager writes messages to a log file
indicating the feature is not supported. However, by enabling SCSI-
3 persistent reservations, you disable SCSI-2 reservations, which
5-20 PM5.2_BF
Creating LPANs
could cause unexpected behavior in a pServer or application that

needs SCSI-2 reservations. Therefore, if you inadvertently enable
SCSI-3 persistent reservations for a disk on an unsupported pServer,
you need to explicitly go back and disable SCSI-3 persistent
reservations afterward.
PAN Manager does not support the following features for use with
SCSI-3 persistent reservations:
• Tape devices
• Map-all-subpaths feature, which provides disk subpaths for a
pServer
PAN Manager does support persistent reservations in disaster

recovery (DR) archives. For each disk in a DR archive,
PAN Manager preserves the persistent reservation enable/disable
flag. PAN Manager does not preserve the reservation data itself
(that is, the pServer registrations and reservations). When you swap
in a new DR archive, PAN Manager clears all the persistent
reservation data.
See the PAN Manager SAN Integration Guide for other restrictions
on the use of SCSI-3 persistent reservations.
SCSI-3 Administrators can perform the following operations on disks to

Operations control SCSI-3 persistent reservations: Enable—Enables SCSI-3
persistent reservations for the disk(s), and disables SCSI-2
reservations for the disk(s). You can enable persistent reservations
for a single disk from the individual disk page (such as the (9.0.0.1)
page), or enable for all disks from the SCSI Disks page.
• Disable—Disables SCSI-3 persistent reservations for the
disk(s), and enables SCSI-2 reservations for the disk(s). You can
disable persistent reservations for a single disk from the
individual disk page (such as the (9.0.0.1) page), or disable them
for all disks from the SCSI Disks page.
• Clear—Clears any stale SCSI-2 reservations and SCSI-3
persistent reservations (whichever is enabled on the disk). If you
move a disk from one pServer configuration to another pServer
PM5.2_BF 5-21
configuration, stale SCSI reservations can persist and cause

undesired application behavior. The Persistent Reservations
dialog lists the number of stale SCSI-3 registrations and
reservations for the disk. (Stale SCSI-2 reservations are not
listed.) The Clear operation removes all stale registrations and
reservations (SCSI-3 and SCSI-2), but does not disable or
enable persistent reservations.
Note: Note: When you delete a pServer, PAN Manager

automatically purges all the stale persistent reservations for the
disks that were associated with the pServer.
Normally, you enable, disable, or clear persistent reservations for a

disk before adding it to a pServer. Once you configure a disk for
use with a pServer and boot the pServer, you can force
PAN Manager to enable, disable, or clear persistent reservations as
long as Veritas Cluster Server is not running. To do this, use the
Force check box in the Persistent Reservations dialog. If Veritas
is running, you must shut down Veritas before modifying the
persistent reservations.
Enabling Before enabling SCSI-3 persistent reservations, review the

Persistent supported configuration and restrictions for this feature. By
Reservations enabling SCSI-3 persistent reservations, you disable SCSI-2
reservations.
```To enable SCSI-3 persistent reservations on one or all disks:

1. If Veritas Cluster Server is running on any of the pServers to
which any of the disks are mapped, shut down Veritas first.
2. Navigate to the SCSI Disks page (if enabling persistent
reservations on all disks) or the individual disk page (such as
(9.0.0.1)).
3. Click Persistent Reservations.
4. If the disk or disks are mapped to any running pServers, click the
Force check box.
5. Click Enable.
5-22 PM5.2_BF
Creating LPANs
Disabling By disabling SCSI-3 persistent reservations on one or all disks, you

Persistent enable SCSI-2 reservations.
Reservations
```To disable SCSI-3 persistent reservations on one or all disks:
which any of the disks are mapped, shut down Veritas first.
2. Navigate to the SCSI Disks page (if disabling persistent
reservations on all disks) or the individual disk page (such as
(9.0.0.1)).
Force check box.
5. Click Disable.
Clearing If you move a disk from one pServer configuration to another, stale
Persistent SCSI-3 persistent reservations or SCSI-2 reservations (depending
Reservations on configuration) can result. The Clear operation removes both
stale SCSI-2 reservations and stale SCSI-3 registrations and
reservations.
```To clear SCSI-2 and SCSI-3 reservations on one disk:

which the disk is mapped, shut down Veritas first.
2. Navigate to the individual disk page (such as (9.0.0.1)).
For SCSI-3 persistent reservations, the Persistent Reservations
dialog lists the number of stale registrations and reservations.
The dialog does not show stale SCSI-2 reservations.
Force check box.
5. Click Clear.
The Persistent Reservations dialog box now shows that no stale
registrations or reservations exist.
PM5.2_BF 5-23
Creating Global and Local Pools
About Pools A pool consists of one or more blades that are used as primary
pBlades and automatic backups if one of the pBlades associated
with your pServers should fail. Although you can assign specific
pBlades to specific pServers for primary and failover service, it
often makes sense to instead specify groups (pools) of eligible
pBlades for these purposes.
PAN Manager provides two kinds of pools:

• Local pools provide pBlade access only to pServers within a
single LPAN.
• Global pools provide pBlade access to pServers in any LPAN
that has been authorized to access that global pool.
You can have a maximum 20 global pools, 20 local pools per

LPAN, and 200 pools total.
It is important to organize pBlades of similar architectures into

pools from which pServers can safely boot. For example, if you
have a 64-bit pServer that cannot run on 32-bit pBlades, you want
to create one or more pools that contain only 64-bit pBlades
suitable for that pServer.
Likewise, if you have a pServer with special memory or processor

performance requirements or particular firmware options (such as
or node interleaving ), you want to create one or more pools
containing just pBlades that meet those special requirements.
Global and local pools can have user-defined names and

descriptions. Global pool names must be unique within the set of
global pools; local pool names must be unique within the set of
local pools in an LPAN (that is, you can have local pools with the
same name in two different LPANs). Pool naming conventions are
the same as for pServers: 32 characters maximum, limited to upper-
and lower-case alphanumerics, plus period, hyphen, dollar sign, and
5-24 PM5.2_BF
Creating LPANs
underscore ( [a-z][A-Z][0-9][.][-][$][_] ). By default, a global pool

named “global_pool” is automatically created, and a local pool
named “pool” is created whenever you create an LPAN.
Pool description fields are limited to 1024 characters; if longer,

they are truncated with a warning. The description field can be used
to indicate the kind of blades it contains, for example, “AMD two-
ways” or “Intel IA32E”.
If a pServer is configured to obtain its primary pBlade from a pool,

it obtains that pBlade when the pServer boots. If a pServer is
configured to obtain a failover pBlade from a pool, the affected
pServer automatically fails over to a pBlade from the pool.
The LPAN Administrator can create a local pool of pBlades. These

pBlades are not available to be specifically allocated to pServers.
The local pool is limited to the pServers within a single designated
LPAN.
PAN Administrators can specify that an LPAN has access to either

0 or 1 global pools. In a typical scenario, a pServer in a given
LPAN will first look to the local pool for a boot or failover blade; if
none is available, the pServer will next check for a blade from an
available global pool. A pServer can only fail over to a pBlade in an
available global pool. The PAN Administrator can enable boot
access for an LPAN such that a pServer can also boot from a global
pool blade.
The LPAN Administrator can configure pServers with pBlades in

one of three ways:
• Specific allocation of primary pBlades; specific allocation of
failover pBlades
• Specific allocation of primary pBlades; failover pBlade
obtained from a pool
• Primary pBlade obtained from a pool; failover pBlade obtained
from a pool
PM5.2_BF 5-25
You can use any combination of the methods within an LPAN;

however, a pServer’s primary or failover pBlade cannot be both
designated and obtained from the pool.
Note: Failover pBlades are not the same as application failover. For
information on application failover, see “Assign Failover Policy
Resources” on page 10-11.
Global pools can be viewed by PAN Administrators and by LPAN

Administrators who have access to specific global pools by clicking
Pools under Resources in the left PAN Manager pane.
Local pools for a given LPAN can be viewed by PAN

Administrators and LPAN Administrators in the Local pBlade
Pools section of the Configuration tab on the LPAN screen.
5-26 PM5.2_BF
Creating LPANs
Roles Required Table 5.1 specifies the roles required for specific pool-related tasks.
for These Tasks In general, the PAN Administrator role has complete control over
all local and global pool tasks. The LPAN Administrator role is
restricted to local pool tasks; the PAN Administrator role is
required for global pool tasks.
Table 5.1 Roles and Pool-Related Tasks
PAN LPAN
Task
Administrator Administrator
Create global pool YES NO
Create local pool YES YES
Delete global pool YES NO
Delete local pool YES YES
Rename global pool YES NO
Rename local pool YES YES
Set global pool description YES NO
Set local pool description YES YES
List global pool YES YES (only for those

global pools to which
the LPAN has access)
List local pool YES YES
Add blades to global pool YES NO
Add blades to local pool YES YES
Remove blades from global pool YES NO
Remove blades from local pool YES YES
Set global pool boot access per LPAN YES NO
Configure global pool for local pool failover YES YES (only for those
global pools to which
the LPAN has access)
PM5.2_BF 5-27
Creating a Local ```To create a local pool of pBlades:

Pool
1. In the left pane, select LPANs > LPAN_name.
2. In the right pane, in the Local LPAN pBlade Pools area, click
Create.
3. In the Create LPAN Local Pool dialog box, enter the pool
Name and Description. If you want to further define the
contents of the global pool now, select the check box labeled
Proceed directly to the Pools page after creation.
4. Click Submit.
Allocating ```To edit the name or description of a local blade pool:

Blades to a Local
1. In the left pane, select LPANs > lpan_name.
Pool
2. In the Local pBlade Pools area, select a local pool.
3. On the LPAN Local Pool pool_name page, click Edit.
4. In the Edit pool description dialog box, you can rename the
pool or modify its description.
```To create or remove a link from a local (LPAN-wide) blade pool

to a global blade pool:
1. In the left pane, select LPANs > lpan_name.
2. In the Local pBlade Pools area, select a local pool.
3. On the LPAN Local Pool pool_name page, click Global Pool
Link.
4. In the Link Global Pool dialog box, do one of the following:
• To allow pServers in the current LPAN to access blades in
a global pool if the local pool becomes depleted, click the
radio button next to the name of the global pool.
• To disallow pServers in the current LPAN from accessing
blades in a global pool if the local pool becomes depleted,
click None.
5-28 PM5.2_BF
Creating LPANs
5. Click Submit.
Any pServer in the LPAN can now appropriately access the
global pool.
```To allocate a pBlade or vBlade to a local (LPAN-wide) pool of

pBlades (PAN Administrators or LPAN Administrators only):
2. In the right pane, in the LPAN LPANname page, in the Local
pBlade Pools area, click the name of the pool that you want to
configure.
3. On the LPAN Local Pool pool_name page, in the Blades area,
click Add.
4. In the Add blades to Pool dialog box, click the check box next
to each pBlade or vBlade that you want to add to the local pool.
(If there are no pBlades or vBlades available, allocate additional
ones to your LPAN.)
PAN Manager enables you to select only those vBlades that are
not already in use and whose pBlades are in the same LPAN as
this pool.
5. Click Add.
In the Blades area, an entry for each allocated pBlade and
vBlade appears.
```To remove a pBlade or vBlade from a local pool in an LPAN

(PAN Administrators or LPAN Administrators only):
2. In the right pane, in the LPAN LPANname page, in the Local
pBlade Pools area, click the name of the pool that you want to
configure.
3. In the LPAN Local Pool pool_name page, in the Blades area,
click the Remove button.
4. In the Remove blades from Pool dialog box, select the check
box next to each pBlade or vBlade that you want to remove from
the local pool.
PM5.2_BF 5-29
PAN Manager enables you to select only those vBlades that are
not currently running a pServer.
5. Click Remove.
The selected pBlades and vBlades are removed from the pool and
no longer appear in the Blades area of the current LPAN Local
Pool pool_name page.
Creating a Global ```To create a global pool:

Pool
1. In the left pane, select Resources > Pools.
2. In the right pane, click Create.
3. In the Create Global Pool dialog box, enter a name and
description for the global pool. If you want to further define the
contents of the global pool now, select the check box labeled
Proceed directly to Pool page after creation.
4. On the Global Pool pool_name page, in the Blades area, click
Add.
5. The Add blades to Pool dialog box displays the list of pBlades
available for allocation. Do one or both of the following:
add to the pool.
slot.
6. Click Add to save your configuration.
Enabling LPAN ```To enable or disable LPAN access to a global pool:

Access to a
Global Pool
2. On the Global Pool pool_name page, click LPAN Access.
5-30 PM5.2_BF
Creating LPANs
3. In the Edit LPAN Access dialog box, do one or both of the

following:
• Select the Access check box for each LPAN that you want
to have failover access to the global pool; clear an LPAN’s
Access check box to disable its access to the global pool.
• Select the Boot check box if you want an LPAN’s pServers
to be able to boot using pBlades from this pool; clear the
Boot check box if you do not want an LPAN’s pServers to
boot using pBlades from this pool.
4. Click Submit to save your configuration.
Modifying a ```To modify a global pool:

Global Pool
1. Check to make sure your changes will not negatively impact any
physical resources or applications currently in use.
3. In the right pane, select the global pool that you want to modify.
4. On the Global Pool pool_name page, you may change the
name, description, LPAN access, or pBlades:
a. Clicking Edit displays the Edit Pool Description dialog
box. You may change the following information:
Rename Pool -- Enter the new name of the pool.
Description -- Enter or change the description of the pool.
b. Clicking LPAN Access displays the Edit LPAN Access
dialog box. You may change an LPAN’s access to the global
pool by selecting or clearing the Access or Boot check
boxes next to an LPANs name.
c. Clicking Add in the Blades section displays the Add
Blades to Pool dialog box. Add blades to the global pool by
selecting the check box next to the blade’s name.
d. Clicking Remove in the Blades section displays the
Remove Blades from Pool dialog box. Remove blades
from the global pool by selecting the check box next to the
blade’s name.
PM5.2_BF 5-31
Deleting a Global ```To delete a global pool:

Pool
1. Check to make sure your changes will not negatively impact any
physical resources or applications currently in use.
3. In the right pane on the Global Pools page, click Delete.
4. In the Delete Global Pool dialog box, select the check box next
to the global pool that you want to delete.
5. Click Delete to save your changes.
Booting the LPAN’s pServers
After you have configured the pServers, created the network

connections, and assigned the administrative roles, you can boot the
LPAN. Booting the LPAN simply means booting all the pServers
within the LPAN.
After the LPAN is booted, pServer use and administration proceeds

as though the pServers were conventional physical servers on the
network. That is, administrators log on to the pServers and use their
operating systems’ administrative commands and utilities to
administer them.
After the initial LPAN boot, you can shut down and reboot the
pServers individually, or you can do so collectively by shutting
down and rebooting the LPAN.
Role Required Pan Administrator or LPAN Administrator

for This Task
5-32 PM5.2_BF
Creating LPANs
Booting, Booting an LPAN

Rebooting, or
Shutting Down ```To boot an LPAN:
an LPAN
1. In the left pane, select LPAN > LPANname.
2. In the right pane, on the bottom border of the LPAN
LPANname page, in the Controls area, click .
3. In the Boot LPAN dialog box, click OK.
Rebooting an LPAN
```To reboot an LPAN:

3. In the Reboot LPAN dialog box, from the pull-down list, select
Time until reboot (minutes) to start the reboot operation.
4. (Optional) Select the check box next to Boot pServers that are
shutdown during reboot if you want PAN Manager to boot
pServers that are currently shutdown.
5. (Optional) In the Reboot LPAN dialog box, enter a text
message in the field, Message to send to console, to send to all
consoles currently open on pServers in this LPAN.
6. (Optional) If the pServer has no PAN agent running on it, select
the check box next to Force pServer reboot to reboot currently
booted pServers.
7. To reboot the LPAN, click OK; to quit the operation, click
Cancel.
Shutting Down an LPAN
```To shut down the LPAN:

PM5.2_BF 5-33
3. In the Shutdown LPAN dialog box, from the pull-down list,

select Time until Shutdown (minutes) to start the shutdown
operation.
4. (Optional) In the Shutdown LPAN dialog box, enter a text
5. (Optional) Select the Force pServer shutdown check box if
you want PAN Manager to force shutdown of currently booted
pServers.
6. To shut down the LPAN, click OK; to quit the operation, click
Cancel.
Booting, Booting a pServer

Rebooting, or
Shutting Down a ```To boot a pServer:
pServer
1. In the left pane, select LPANs > LPANname > pServername.
OR
On Dashboard page, click the name of a pServer.
2. On the bottom border of the pServer pServername page, in the
Controls area, click .
3. (Optional) In the Boot pServer dialog box, click Override to
change pServer boot attributes on a one-time basis:
a. In the Boot image field, select an image from the pull-down
list.
b. In the User Defined Boot Arguments field, specify any
custom boot arguments you want the pServer to boot with.
4. Click OK.
In the top border of the pServer pServername page, the Boot
Status indicates that the pServer is Booting. The word Booted
appears when the boot is complete.In the Boot pServer dialog
box, click OK.
5-34 PM5.2_BF
Creating LPANs
Rebooting a pServer
```To reboot a pServer:

OR
3. In the Boot pServer dialog box, do the following:
a. From the pull-down list, specify a time (in minutes from
now) for the pServer to reboot.
b. Enter a message to appear on the pServer console to warn of
the impending reboot.
c. If the PAN agent is not running on the pServer, select the
Force pServer reboot check box.
d. (Optional) In the Boot image field, either accept the
pServer’s currently configured boot image or select another
from the pull-down list.
e. (Optional) In the User Defined Boot Arguments field,
specify any customized boot arguments that you want the
pServer to boot with.
4. Click OK.
appears when the boot is complete.
Shutting Down a pServer
```To shut down a pServer:

1. In the left pane, select LPAN > LPANname > pServername.
OR
PM5.2_BF 5-35

3. In the Shutdown pServer dialog box, specify the time of the
shutdown, and then enter a message to send to the system
console about the shutdown.
4. If a node agent is not running on the pServer’s pBlade, select
Force pServer shutdown to force the shutdown.
5. Click OK.
Status indicates that the pServer is Shutting down. The word
Shutdown appears when the operation is complete.
Modifying an LPAN’s Resources
You can add or remove the following resources from an LPAN:

• pBlades
• Storage disks
• vSwitches
Adding a Only the PAN Administrator can add a resource to an LPAN, which
Resource to an can be done at any time. The LPAN Administrator can use the
LPAN newly added resource to build new pServers or add resources to
existing pServers.
Use the same procedure for adding a supplemental resource as you

did to add the original resources to the LPAN.
Note: If you want to add a large number of SAN devices after

completing the initial configuration of the PAN, shut down both
cBlades, make the required connections, and then reboot the
cBlades.
5-36 PM5.2_BF
Creating LPANs
Removing a Only the PAN Administrator can remove a resource from an

Resource from LPAN. The PAN Administrator can only remove a resource that is
an LPAN not in use. The LPAN Administrator or Operator must shut down
the pServer(s) using the resource prior to its removal.
Modifying ```To allocate a pBlade to an LPAN:

Resources
Example
pBlades area, click the Add button.
3. In the Add pBlades to LPAN dialog box, do one or both of the
following:
allocate to this LPAN, and click Add.
slot.
The pBlade appears in the Blades area.
```To remove a pBlade from an LPAN:

pBlades area, click the Remove button.
3. In the Remove pBlades from LPAN dialog box, select the
check box next to each pBlade that you want to remove from this
LPAN.
4. Click Remove.
The pBlade no longer appears in the Blades area.
```(PAN Administrators only) To authorize an LPAN to acquire

pBlades from the global (PAN-wide) pool:
PM5.2_BF 5-37
2. In the right pane, in the LPANs LPANname page, in the Local

pBlade Pool area, click the Global Pool Access button.
3. In the Configure Global Pool Access dialog box, do either of
the following:
• To enable global pool access for failover blades, select the
Access check box next to the pool name(s) that you want to
obtain blades from.
• To enable global pool access for primary blades, select the
Boot check box next to the pool name(s) that you want to
obtain blades from.
4. Click Submit.
Any pServer in the LPAN can appropriately access the global
pool.
5-38 PM5.2_BF
Part II
Creating pServers
Part II of this guide outlines the tasks involved in creating and

administering pServers. It consists of the following chapters:
• Chapter 6, “Configuring pServers”

• Chapter 7, “Administering pServers”
• Chapter 8, “Administering Windows-Based pServers”
Chapter 6
Configuring pServers
This chapter describes how to use PAN Manager to create and

configure pServers. Many of the tasks are similar to configuring
conventional hardware, but they are done through software. When
you have completed these tasks, you can administer the pServer
much as you would a traditional server.
Note on vBlades: This chapter pertains to pServers on physical

pBlades. If you are using vBlades, there are some differences in the
procedures. Please read the manual Using vBlades in conjunction
with this chapter.

• Creating a pServer
• Assigning Processing Blades
• Assigning SAN Disks
• Assigning FC Tape Devices
• Enabling a DVD-ROM Drive
• Enabling a Virtual CD-ROM Drive
• Establishing Network Connections
• Completing a pServer’s Configuration
PM5.2_BF 6-1
Note: Before proceeding, you should be familiar with the SAN and
network requirements of your data center.
Creating a pServer
About pServers You must create a pServer before you can configure its resources.
A pServer’s resources consist of Processing Blades (primary and
failover), storage disks and tape devices, and network connections.
Resources are assigned to a pServer to create its configuration, and
then locked in when the pServer boots. When the pServer shuts
down, those resources are then available to be assigned to other
pServers.
A correctly configured pServer is a fully functioning server

composed of both physical and virtual hardware resources. You
configure a pServer by combining a single Processing Blade with
one or more Storage Area Network (SAN) devices or Network
Attached Storage (NAS), and, optionally, with one or more virtual
switches (vSwitches).
The following general conditions apply to all pServers:

• Any user who wants to configure a pServer must possess the
LPAN Administrator role or the PAN Administrator role.
• Each pServer must exist within an LPAN.
• Each pServer must possess a unique name within the LPAN.
There is a limit of 32 legal characters in a name.
• Multiple pServers in different LPANs can have the same name.
• Each pServer must be connected to a vSwitch to allow network
connectivity. (Otherwise, the use of vSwitches is optional.)
• A pServer is connected to a vSwitch using a Virtual Ethernet
interface (vEth).
6-2 PM5.2_BF
• A pServer can be connected to up to 31 vSwitches, using 31

vEths.
• All the physical and virtual resources required to configure a
pServer must reside in the same LPAN as the pServer, with the
exception of blades in a global pool and NAS disks.
• You can have up to 144 pServers in an LPAN.
• You can have up to 600 pServers in a PAN.
Obtaining a The pServers obtain their time setting from the cBlades. You need
pServer’s Time to synchronize the time on the cBlades with each other and with an
external time source.
Role Required PAN Administrator or LPAN Administrator

for This Task
Creating a ```To create a pServer:

pServer
1. In the left pane, click LPAN > LPANname.
2. In the LPAN LPANname page, in the pServers area, click the
Create button.
3. In the Create pServer dialog box, enter the name of the
pServer, optionally select the check box next to Proceed
directly to pServer page after creation, and then click Submit
to create the pServer.
Depending on your preference, either the pServer
pServername (in LPAN LPANname) page displays the
configuration page for your newly-created pServer or the LPAN
LPANname page displays the LPAN LPANname page with all
existing pServers in the LPAN, including the new one you just
created.
PM5.2_BF 6-3
```To delete a pServer:
Note: You cannot delete a pServer that is not shut down.

1. In the left pane, click LPAN > LPANname.
2. In the LPAN LPANname page, in the pServers area, click the
Delete button.
3. In the Delete pServer dialog box, select the check box next to
the pServer(s) that you want to delete, and then click Delete.
4. PAN Manager returns to the LPAN LPANname page. The
deleted pServer no longer appears.
Assigning Processing Blades
About You assign a pBlade to a pServer. The pBlades must exist in the
Processing same LPAN as the pServer, unless the pServer obtains its pBlade
Blades from a global pool. The pServers have a primary Processing Blade
and might also have a failover Processing Blade.
The LPAN Administrator can configure pServers with pBlades in

one of three ways:
• Specific allocation of primary pBlades; specific allocation of
failover pBlades
• Specific allocation of primary pBlades; failover pBlade
obtained from a pool
• Primary pBlade obtained from a pool; failover pBlade obtained
from a pool
If the LPAN is authorized to access a global pool, the pServer can

obtain a primary pBlade from that global pool if the local pool is
depleted.
6-4 PM5.2_BF
For information on creating pools, see “Configuring Disks for

Persistent Reservations” on page 5-19.
You can use any combination of the above methods within an

LPAN; however, a pServer cannot have a designated blade AND
obtain the same type of blade (primary or failover) from the pool.
About Failover Assigning failover blades or obtaining failover blades from a local
pBlades or global pool is optional. If the LPAN Administrator specifies
neither, the pServer does not have a hardware failover
configuration; it will not fail over.
When selecting pBlades for failover, make sure that a failover

pblade has the same hardware capabilities as the pServer’s primary
pBlade. See “Configuring pServer Boot Attributes” on page 7-17.
When selecting pBlades for failover, make sure that a failover

pblade has same the hardware capabilities and firmware options as
the pServer’s primary pBlade. See “Configuring pServer Boot
Attributes” on page 7-17.
Also, it is good practice to select failover pBlades in a different

power domain from the primary pBlade. See “Configuring Power
Management” on page 2-13.
Single blade—You can assign a failover blade to multiple

pServers. However, if one pServer fails over to the pBlade, that
blade is no longer available for the other pServers.
Pools—If the pServer obtains its failover blade from a pool, it can
withstand multiple pBlade failures, as long as there are unused
blades in the pool. See “About Pools” on page 5-24 for information
on how a pBlade is selected from a pool.
Failover escalation—If a pServer fails after it achieves a fully

booted state, it attempts to reboot on the primary pBlade. If the
pServer does not boot on the primary pBlade, the pServer attempts
to boot on a failover pBlade (either the pBlade configured as the
failover pBlade or one from a pool). If the pServer cannot boot on a
PM5.2_BF 6-5
failover pBlade, it is considered failed. The pServer enters the boot

pending state until either a failover or primary pBlade becomes
available. When a pBlade is available, the pServer boots.
Fatal hardware errors—If fatal hardware errors are detected

twice on the same pBlade (inducing failover), PAN Manager
automatically marks that pBlade as out-of-service. When a pBlade
is out-of-service, it can no longer be used by any pServer or
allocated to an LPAN. To regain use of an out-of-service pBlade,
you must manually change it to in-service by clicking the Out-of-
Service button on the Blade page of the PAN Manager GUI.
The error count is maintained for the duration that the pBlade is
inserted in a specific slot. The counter is cleared whenever a blade
is ejected. If a pBlade is marked out-of-service, setting the blade
back to in-service also clears the counter. This allows you to boot
the blade after a series of fatal hardware errors, either for diagnostic
purposes or if you believe that the fatal hardware errors are
transient.
64-bit blades— If you are using a 64-bit pBlade, use one of the
following failover configurations to ensure that the 64-bit operating
system fails over to another 64-bit blade:
• Configure the pServer with both specific primary and failover
pBlades, both 64-bit.
• Configure all pServers running on 64-bit pBlades with the same
failover pBlade, also a 64-bit pBlade. Multiple pServers can
share a failover pBlade, as long as they are in the same LPAN.
With this configuration, each LPAN needs its own 64-bit
failover pBlade. When the pBlade is taken by a failover, it is
unavailable to the other pServers.
• Configure a pool of 64-bit pBlades for that LPAN.
Note: The above guidelines can also be used in any situation where
pBlade hardware is critical to pServer peformance. For example, if
you have a 32-bit pServer that requires a very fast processor or that
6-6 PM5.2_BF
has large memory requirements, you need to define failover

configurations that ensure that the pServer will fail over to a suitable
pBlade.

for This Task
Note: If you have the PAN Administrator role, you may assign a
pBlade to a pServer without first allocating the pBlade to an LPAN.
Two Major Steps There are two major steps for assigning Processing Blades to
to Assign pServers:
Processing
1. Assign a primary pBlade.
Blades
2. Assign a failover pBlade (optional).
Assigning a ```To assign the primary pBlade to a pServer:

Primary pBlade
1. In the left pane, select LPANs > LPAN_name > pserver_name.
2. On the pServer pserver_name page, in the Primary pBlade
area, click the Assign/Unassign button.
3. In the Assign/Unassign pBlade as Primary dialog box, select
the radio button next to a specific pBlade Name or Pool. If you
choose Pool, select a pool name from the dropdown menu.
4. Click OK.
In the Primary pBlade area, a pBlade icon appears.
```To unassign or modify the primary pBlade for a pServer:

2. On the pServer pserver_name page, in the Primary pBlade
3. In the Assign/Unassign pBlade as Primary dialog box:
• To remove the current setting, select the None radio button.
PM5.2_BF 6-7
• To reassign the pServer’s primary pBlade setting, select

another pBlade Name or Pool_name.
4. Click OK.
Assigning a ```To assign a failover pBlade to a pServer:

Failover pBlade
2. On the pServer pserver_name page, in the Failover pBlade
3. In the Assign/Unassign pBlade as Failover dialog box, select
the radio button next to a specific pBlade Name or Pool. If you
choose Pool, select a pool name from the dropdown menu.
4. Click OK to save your work, or Cancel to close the dialog box.
In the Failover pBlade area, a pBlade icon appears.
```To unassign or modify a failover pBlade for a pServer:

3. In the Assign/Unassign pBlade as Failover dialog box:
• To reassign the pServer’s failover pBlade setting, select
another pBlade Name or Pool_name.
4. Click OK.
6-8 PM5.2_BF
Assigning SAN Disks
About SAN Disks A PAN typically uses a Storage Area Network (SAN) for its
primary disk assignment. The following general attributes apply to
SAN disks:
• A PAN may be connected to up to 2048 SCSI devices.
Note: On BladeFrame BF200, a PAN may be connected to up

to 756 SCSI devices.
• SAN disks must exist in the same LPAN as the pServer.
• A pServer must have a disk with a root partition in order to boot,
unless the pServer boots from RAM, NFS, or an installation
image.
You can designate any or all of a pServer’s disks as “required.” A

pServer with required disks does not boot, reboot, or recover from
failure until all of its required disks are available.
If you initiate a boot or reboot command to a pServer with required

disks, and one or more of the required disks is unavailable, the
pServer enters or remains in an expected state as follows:
• On a boot command, the pServer remains shutdown.
• On a reboot command from PAN Manager, the pServer enters
the boot pending state until the required disk becomes available
or is removed from the pServer configuration.
• On a reboot command from the pServer, the pServer shuts
down.
If the entire system experiences a power outage and a reboot prior

to the SAN recovering, pServers that cannot locate their required
disks enter the boot pending state. When the disks become
available, the pServer automatically boots. The same is true if the
pServer fails over and cannot locate its required disk.
PM5.2_BF 6-9
Newly attached disks are marked as required by default. To mark a

disk as not required, modify the Disk Required attribute.
Disks assigned to pServers prior to Release 4.0 are considered

optional. You will need to modify the disk attribute to Required.
Some applications might require the pServer’s disk subpaths to be

visible to PAN Manager. By default, PAN Manager displays a
single SCSI ID for each physical disk. Each physical disk is
associated with two underlying subpaths; each subpath has its own
SCSI ID and is associated with one of the Control Blades.
Note on Persistent Disk Reservations: Normally, you enable,

disable, or clear persistent reservations for a disk before adding it
to a pServer. Once you configure a disk for use with a pServer and
boot the pServer, you can force PAN Manager to enable, disable, or
clear persistent reservations as long as Veritas Cluster Server is
not running. To do this, use the Force check box in the Persistent
Reservations dialog. If Veritas is running, you must shut down
Veritas before modifying the persistent reservations. See
“Configuring Disks for Persistent Reservations” on page 5-19 for
details.
Using Network You can use Network Attached Storage (NAS) and Network File
Attached Systems (NFS) in conjunction with or in lieu of SAN disks.
Storage
To use both SAN disks and a file system using NFS, configure the
pServer to use the SAN disk for its root file system. Then, access
the NFS just as a conventional server does. The file system must be
available from a properly configured NFS server.
To use NAS for a pServer’s root file system, do not associate a disk
with a root file system with the pServer. Apply the virtualization
extentions to the root file system to be NFS-mounted by the
pServer, and use the boot argument in the pServer boot command
to link to the NAS location. For more information on booting from
NAS, see “The pServer Virtualization Extensions contain the
6-10 PM5.2_BF
drivers that allow the pServer to communicate with the cBlade.” on

page 6-22. For information on setting up an NFS root environment,
see your Linux documentation.

for This Task
Assigning a Disk ```To add a SCSI disk to a pServer:

to a pServer
1. In the left pane, click LPAN > LPANname > pserver_name.
2. On the pServer pserver_name page, in the SCSI Disks area,
click the Add button to open the Map SCSI Disks to pServer
dialog box.
3. Use the pull-down menu to assign a pServer Disk Id.
4. Clear the check box next to Auto-enable disk at pServer boot
if your high-availability configuration requires the disk to be
disabled at boot time.
5. Use the pull-down menu to Choose physical SCSI disk to use
for this pServer disk from the disks currently available.
6. Click Submit, or click Cancel to close the dialog box.
A disk icon appears in the SCSI Disks area.
```To partition a disk:
Caution: Partitioning or repartitioning a SAN disk overwrites all

data on the disk.

the disk that you want to partition.
2. On the SCSI ID page, in the Partitions area, click the Add
button.
3. In the Add Partitions dialog box, enter a Partition Size and use
the pull-down menu to quantify the size at MB or GB. (To add
all remaining disk space to this partition, click the Fill button
instead of entering a number.)
PM5.2_BF 6-11
4. Specify a Partition Type using the pull-down menu.

dialog box.
6. Do any of the following:
• Add partitions to this disk, following Steps 2 through 4.
Note: If the disk will contain five or more partitions, be sure

that one of the first four partitions is of the Extended type.
• To edit partition sizes or types, click the Modify button.
• To cancel your edits and return to the last saved partition
table, click the Reset button.
• To erase all disk partition sizes and types, click the Clear
button.
• When you finish adding or modifying the partition(s), click
the Save button.
```To remove a SCSI disk from a pServer:

3. In the Remove SCSI Disk Mappings from pServer dialog box,
select the check box next to the SCSI ID(s) that you no longer
want assigned to the pServer.
4. Click Remove, or click Cancel to close the dialog box.
The disk icon no longer appears in the SCSI Disks area.
```To modify a SCSI disk mapping for a pServer:

click the Modify button.
3. In the Modify SCSI Disk Mappings dialog box, select the
SCSI disk mapping heading to display the configurable fields.
6-12 PM5.2_BF
4. (Optional) Use the pull-down menu to modify the Auto-

Enabled setting for this disk.
5. (Optional) Select the radio button next to a SCSI ID to specify
an alternative disk to Replace SCSI disk with.
6. Click Submit to complete the modification.
```To map all disk subpaths to a pServer:
Before mapping disk subpaths, be sure that the pServer’s operating

system supports subpath mappings.

2. In the pServer pServername page, click the Advanced
Configuration button.
3. In the Advanced pServer Configuration dialog box, click the
Disk Subpaths heading to expand it:
• To configure the pServer to use disk subpaths, select the
Map all disk subpaths check box.
• To configure the pServer not to use disk subpaths, clear the
Map all disk subpaths check box.
4. Click Submit.
Your changes will take effect after the pServer boots or reboots.
Assigning FC Tape Devices
About Tape A PAN may use a fibre channel (FC) tape device to store data from
Devices a pServer. Tape devices may be used in conjunction with third-
party backup applications to back up the data on a pServer.
Note: Tape devices are supported on Linux pServers only. They are
not supported on pServers running the Windows operating system.
PM5.2_BF 6-13
The following general attributes apply to FC tape devices:

• Tape devices must exist in the same LPAN as the pServer.
• Multiple tape devices may be assigned to a pServer, and a tape
device may be assigned to multiple pServers.
• A tape device is optional on pServer boot, but always enabled
after the pServer is booted.
• A tape device may be accessed by only one pServer at a time.
Although an FC tape device will be shown in the PAN Manager

GUI with multiple I/O paths, only one path will be mapped on a
single pServer. There is no multipathing, load balancing, or
automatic failover on the tape I/O paths. If a tape device becomes
unreachable, it is up to the data backup application (or the
Administrator’s manual intervention) to switch to another tape
device.

for This Task
Assigning a Tape ```To add a SCSI tape device to a pServer:

Device to a
1. In the left pane, select LPANs > LPAN_name> pserver_name.
pServer
2. On the pServer pserver_name page, in the SCSI Tapes area,
click the Add button to open the Map Tapes to pServer dialog
box.
3. Use the pull-down menu to assign a pServer Tape Id.
4. Clear the check box next to Auto-enable disk at pServer boot
if your high-availability configuration requires the tape device
to be disabled at boot time.
5. Use the pull-down menu to Choose physical SCSI disk to use
for this pServer disk from the tape devices currently available.
6. Click Submit.
The tape device now appears in the SCSI Tapes area.
6-14 PM5.2_BF
```To remove a SCSI tape device from a pServer:

3. In the Remove SCSI Tape Mappings from pServer dialog
box, select the check box next to the SCSI ID(s) that you no
longer want assigned to the pServer.
4. Click Remove.
The tape device no longer appears in the SCSI Tapes area.
```To modify a SCSI tape device mapping for a pServer:

3. In the Modify SCSI Tape Mapping dialog box, select the name
of the tape device to display the configurable fields.
4. (Optional) To auto-enable the tape device, do one of the
following:
5. Select the Auto-enable tape at pServer boot check box:
• To indicate that the tape device will be made available for
I/O automatically when the pServer boots, select the Auto-
enable tape at pServer boot check box.
• If you configure the pServer to run one or more high-
availability applications, clear the Auto-enable tape at
pServer boot check box.
6. (Optional) Select the radio button next to a SCSI ID to specify
an alternative tape device to Replace SCSI Tape with.
PM5.2_BF 6-15
Enabling a DVD-ROM Drive
About DVD-ROM On platforms that support physical DVD-ROM drives, the drives
Drives are allocated to the LPAN and then enabled at the LPAN level.
After a DVD-ROM drive is enabled at the LPAN level, it is by
default accessible by every pServer in the LPAN that resides on the
same platform as the DVD-ROM drive. The LPAN Administrator
can also enable and disable DVD-ROM drives for individual
pServers.
Note: You only need to enable a DVD-ROM drive for a pServer if

it has previously been disabled.

for This Task
Enabling a DVD- To enable DVD-ROM access for a pServer:

ROM Drive for a A pServer cannot have DVD-ROM access enabled if its LPAN
pServer does not have access enabled.
1. In the left pane, click LPANs > LPANname > pserver_name.
2. On the pServer pserver_name page, in the right pane, in the
pServer pserver_name page, in the Media Drives area, click
the Enable/Disable button.
3. In the Enable/Disable DVD-ROM Access dialog box, select
the check box(es) next to the specific DVD-ROM NAME to
which you want access enabled.
4. insert/eject
5. Click Submit.
Note: Selecting a DVD-ROM NAME that doesn’t have access

displays an Operational Error. Click OK to return to the
pServer pserver_name page or click Re-Open Form to submit
another configuration request.
6-16 PM5.2_BF
Enabling a Virtual CD-ROM Drive
A virtual CD-ROM drive (VCD) is a software facility that enables a

pServer to access a media (ISO) image that resides on the cblade
and is registered with PAN Manager.
PAN Manager automatically attaches a VCD to each pserver when

the pServer starts up. The Administrator need not take any action to
enable VCDs, other than to register images with PAN Manager (as
described in “Registering Virtual CD-ROMs” on page 5-5).
Establishing Network Connections
About The LPAN Administrator must create one element that is not
Networking contained in the allocated resource pool: the Virtual Ethernet
pServers interfaces (vEths) for the network connections. The vEths are the
equivalent of physical network ports. Create one vEth for each
connection to a vSwitch that the pServer needs to make. A pServer
can have up to 31 vEths, numbered from 0 to 30. Each pServer is
automatically configured with one additional vEth for
communication with PAN Manager. This additional vEth is
numbered vEth31.
Each vEth must have a MAC address. PAN Manager assigns the
MAC address automatically. However, if you are concerned that the
MAC address will conflict with another address on your network,
you might want to assign the MAC address manually. Obtain a
valid MAC address from your network administrator.
By connecting multiple pServers to a vSwitch, you create a

network. If the vSwitch has an uplink, the pServers are connected to
the network outside of the PAN. If the vSwitch does not have an
uplink, the pServers’ network is completely internal to the platform.
PM5.2_BF 6-17
For example, pServer1, pServer2, and pServer3 are connected to a

vSwitch with no uplink; pServer3 and pServer4 are connected to a
vSwitch with an uplink. In this configuration, pServer1, pServer2,
and pServer4 have one vEth each, and pServer3 has two vEths.
Figure 6.1 illustrates this configuration.
Figure 6.1 Multiple vSwitch Connections
MyOtherLPAN
pServer1 pServer2 pServer3 pServer4
vSwitch_A vSwitch_B
Note: If the pServer is to receive multicast network traffic, it must

support the Internet Group Management Protocol (IGMP).
Regulating Network Traffic Speeds
You can control the rate at which pServers can send packets over
the network. This is desirable if the receiving servers on the
external network receive packets at a slower rate than pServers send
them.
The available speed limits for pServer network traffic are:10 MB/
sec and 100 MB/sec.
6-18 PM5.2_BF
If you want to send packets at a specific speed for one application

only, and send all other network traffic at the best possible speed,
create a vEth and IP resource specific for the rate-controlled
application traffic. Create another vEth (or vEths) for other network
traffic. You can connect more than one vEth to the same vSwitch.
If you want an application that uses a specific network traffic speed

to fail over, you must configure all of the pServers in the failover
cluster to use the same vEth for the specified network speed (for
example, the same vEth on all of the pServers must be set to the
same network speed).
The rate control feature provides a rate limit for a vEth, which is the
upper bound of the network transfer rate. Administrators can set a
rate limit for all vEths associated with a pServer.
Note: Rate limiting is not supported by the Windows

operating system or any operating system running as a vBlade
guest.
You can also control network traffic in order to eliminate dropped

packets. Packets can be dropped if the pServer transmits packets
faster than the cBlades can move them to the external network. For
information on controlling network traffic at this level, see
“Activating Flow Control on the PAN” on page 2-11.
Configuring IP Addresses
You can configure IP addresses for pServers in one of two ways:

• If you use PAN Manager to manage application failover, use
PAN Manager to create IP resources. PAN Manager uses IP
resources to associate IP addresses with applications. With IP
resources, IP addresses move with an application when it fails
over. Configure IP resources with aliases.
• If you do not use PAN Manager failover capabilities, you can
configure the IP addresses on the pServers, just as you would
configure IP addresses on conventional servers.
PM5.2_BF 6-19
Note: Attempting to use external (shell) network modifications on

IP addresses controlled by PAN Manager can result in incorrect IP
communication.
If you choose to regulate the network traffic speeds on a vEth, you

can specify that vEth when you configure the IP resource for the
application.
Note: Configure all other external network configuration, including

IP addresses not under PAN Manager control, as you would on
conventional servers.

for This Task
Creating ```To connect a pServer to a network:

Network
1. On the pServer Dashboard, click the pServer_name. Or, in the
Connections
left pane, click LPAN > LPANname > pserver_name.
2. On the pServer pserver_name page, in the vEths area, click the
Add button to open the Assign vEth dialog box and display the
configurable fields:
• Select a vEth Name (veth0 to veth30) from the pull-down
list.
• To allow PAN Manager to assign a MAC address to the
vEth, select the Auto-Generate radio button; to specify
your own MAC address, click the Custom radio button and
enter a MAC address in the adjacent box. (Be sure to check
with your network administrator to avoid MAC address
naming collisions at your site.)
• To limit the rate of network traffic through this vEth
(between the pServer and the vSwitch), select a Rate Limit
from the pull-down list; to place no restriction on the flow
of network traffic through this vEth, select Unlimited.
6-20 PM5.2_BF
Note: Rate limiting is not supported by the Windows

operating system or any operating system running as a vBlade
guest.
• Select a vSwitch Name radio button in the Choose a
vSwitch to connect to this vEth area.
dialog box.
A vEth icon appears in the vEths area.
```To delete a pServer vEth:

Remove button.
3. In the Remove vEth dialog box, select the check box next to the
vEth Name(s) that you want to delete.
4. Click Remove, or click Cancel to close the dialog box.
The vEth icon no longer appears in the vEths area.
```To modify a pServer vEth:

Modify button.
3. In the Modify vEth dialog box, select the vEthname heading to
display the following configurable fields.
• (Optional) Modify the MAC address setting. (Be sure to
check with your network administrator to avoid MAC
address naming collisions at your site.)
• (Optional) Modify the setting for Rate Limit or Rate
Setting from the pull-down list. (Rate control is not
available to pServers running Microsoft Windows or any
operating system running as a vBlade guest.)
• (Optional) Select an appropriate vSwitch Name button in
the Choose a vSwitch to connect to this vEth area.
PM5.2_BF 6-21
4. Click Submit to proceed with the modification.
Completing a pServer’s Configuration
About A pServer with pBlade, disk, DVD-ROM drive (virtual or, on some
Completing the platforms, physical), and networking components is the virtual
Configuration equivalent of a traditional server’s hardware.To use your pServer,
you need to install the pServer’s operating system and
Virtualization Extentions
Operating Systems
In the PAN environment, pServers can use the following operating

systems:
• RedHat Linux
• SUSE Linux
• Microsoft Windows
• An extension of the Solaris operating environment
You should obtain the operating systems directly from Red Hat,
Inc., SUSE Linux, and/or Microsoft, Inc.
Obtain (extended) Solaris from Fujitsu Siemens Computers

customer support or http://www.fujitsu-siemens.com/support,
rather than from Sun Microsystems.
Virtualization Extentions
The pServer Virtualization Extensions contain the drivers that

allow the pServer to communicate with the cBlade.
6-22 PM5.2_BF
Using a NAS-rooted pServer
You can create a pServer and use a Network Attached Storage

(NAS) device for the root file system. It is the responsibility of the
administrator to make the appropriate configuration file changes
and to put the required files on the NAS server.
For Further Instructions
For detailed information on installing the pServer Virtualized

Extentions, installing the pServer operating system, and using a
NAS-rooted pServer, refer to the appropriate pServer Guide,
available from http://www.fujitsu-siemens.com/support
Completion Your pServer is completely configured when you have completed

Checklist the following tasks:
• Assigned pBlade(s).
• Assigned disk(s).
• (Optional) Assigned tape device(s).
• Created network connection(s).
• Installed the operating system and the Virtulazation Extensions.
• Created a root file system.
When you have completed these tasks, you can administer your
pServer much as you would a traditional server.
PM5.2_BF 6-23
6-24 PM5.2_BF
Chapter 7
Administering pServers
This chapter describes how to use PAN Manager to administer

pServers.
Note on vBlades: This chapter pertains to pServers on physical

pBlades. If you are using vBlades, there are some differences in the
procedures. Please read the manual Using vBlades in conjunction
with this chapter.
Note: Some additional information is specific to pServers running

the Windows operating system. See Chapter 8, “Administering
Windows-Based pServers”.

• Displaying pServer Information
• Modifying a pServer Name or Description
• Modifying a pServer Configuration
• Managing Virtual CD-ROMs
• Managing Boot and Root Disk Images
• Configuring pServer Boot Attributes
• Using the pServer Console
PM5.2_BF 7-1
Displaying pServer Information
```To learn more about a pServer:
Note: Depending on your PAN Manager administrative role,

some information described here might not be visible on this
page.
1. In the left pane, select Dashboard.
2. On the pServer Dashboard page, do one or more of the
following:
• To display details about any system monitors or recent
events associated with a pServer, in the Name column,
expand the triangular tab to the left of the pServer’s icon.
• To examine the contents and characteristics of a pServer, in
the Name column, hover over the pServer’s icon next to its
name.
• To display details about the events associated with a
pServer, click the number that appears in the Health
column.
• To perform a control operation on the pServer (boot, reboot,
shutdown, open a pServer console, or open a Virtual VGA
desktop session on a Windows pServer, if applicable), in the
Controls column, click the appropriate icon.
7-2 PM5.2_BF
Modifying a pServer Name or Description
```To edit the name or description a pServer:

2. On the pServer pserver_name page, click Edit.
3. In the Edit pServer dialog, modify the name or description.
4. Click Submit.
PM5.2_BF 7-3
Modifying a pServer Configuration
About Modifying The LPAN Administrator (or PAN Administrator) can modify a
a Shutdown shutdown pServer in the following ways:
pServer
• Add a disk.
• Remove a disk.
• Add a pBlade.
• Remove a pBlade.
• Add a failover pBlade.
• Remove a failover pBlade.
• Add a vEth.
• Remove a vEth.
• Modify a vEth’s connections.
• Modify the boot settings.
• Modifying a disk’s SCSI ID or auto-enable setting.
The only restrictions related to modifying a shutdown pServer

relate to the following:
• Removing a disk
If you remove a disk from a pServer configuration and that
pServer has multiple disks mapped to it, you may need to adjust
the device order of the remaining disks.
• Repartitioning a disk
If you repartition a disk currently used by a pServer, you must
reboot the pServer in order to reread the partition table and
update the kernel’s cache.
7-4 PM5.2_BF
About Modifying The LPAN Administrator can also modify a pServer configuration
a Running while the pServer is running.
pServer
To understand what it means to modify a pServer configuration on
a running pServer, consider the following topics:
• pServer Status and pServer Configuration
• Ethernet device modifications
• SCSI disk device modifications
• CD-ROM device modifications
• Real time properties modications
• Boot time properties modifications
The following sections describe each of these topics. Following a

discussion of the topics is a section that provides a summary table
of pServer properties.
The process of adding, removing, and/or modifying devices on

running pServers must be coordinated with the pServer operating
system admininistrator. While the exact actions that the pServer
operating system administrator must perform will vary among
different operating systems and device types, the following are
general points that apply in most cases:
• After a device is added, the pServer operating system
admininistrator needs to configure the operating system to use
the device.
• Before a device is removed, the pServer operating system
administrator needs to ensure that the operating system is
configured to not use the device.
• Before a device is modified, the pServer operating system
administrator must prepare the operating system for the change,
and needs to update the operating system configuration after the
modification.
PM5.2_BF 7-5
About pServer Status and pServer Configuration
The status of a pServer refers to the set of values for all properties
associated with a given pServer. An LPAN Administrator assigns
and sets these values for a given pServer prior to booting this
pServer. The configuration of a pServer refers to the set of values
for all properties associated with a running pServer at a particular
moment in time.
It is not possible to immediately change the status of a running

pServer when modifying the values of some properties. For
example, if an LPAN Administrator modifies the boot arguments of
a running pServer, PAN Manager displays the following:
• Boot argument status that existed when the pServer booted
• Configuration status that shows the boot argument modification
that will take effect at the next boot
Modifying Ethernet Devices on a Running pServer
An LPAN Administrator can add a vEth and modify a vEth’s

connections on a running pServer. The only restriction is that a
vEth cannot be removed while a pServer is running the Red Hat
Linux or SUSE operating system.
Modifying SCSI Disk Devices on a Running pServer
An LPAN Administrator can add, remove, and modify a SCSI disk

on a running pServer. PAN Manager makes no attempt to protect
disks that applications currently use. Thus, removing a disk from a
running pServer can result in I/O errors. It is the responsibility of
the LPAN administrator to ensure that a disk is not in use before
removing it from a running pServer.
7-6 PM5.2_BF
Modifying CD-ROM Devices on a Running pServer
An LPAN Administrator can enable or disable a CD-ROM device

on a running pServer. It is possible for an LPAN administrator to
enable or disable CD-ROM devices from the LPAN level and the
pServer level. The modification discussed here applies to the
pServer level.
Modifying Real-Time Properties on a Running pServer
An LPAN Administrator can modify the following real-time

properties on a running pServer:
• pServer name
• pServer label
These modifications take effect immediately.
Modifying Boot-Time Properties on a Running pServer
An LPAN Administrator can modify the following boot-time

properties on a running pServer:
• Primary pBlade
• Failover pBlade
• Boot image
• Boot arguments
• Default image
• Boot order
• Optional boot
These modifications take effect at the next boot of the specified

pServer.
Summary Table of pServer Properties
You can modify a pServer’s configuration. The following table lists

the pServer properties that you can modify:
PM5.2_BF 7-7
Table 7.1 pServer Properties
Property Action Change While Running?
disk add yes
disk remove yes*
disk modify yes
veth add yes
veth remove yes*
veth modify yes
pserver delete no
primary blade modify yes
failover blade modify yes
boot image modify yes (takes effect on next reboot)
boot arguments modify yes (takes effect on next reboot)
name modify yes
label modify yes
default image modify yes (takes effect on next reboot)
boot order modify yes
optional boot modify yes
* Removing disks and veths have limitations dependent on the

operating system.
When a disk is removed from a pServer running Linux, Linux

maintains a reference to the disk but the pServer is unable to access
the disk.
Ethernet devices cannot be removed from Linux while the server is

running. If a vEth is removed from a pserver through
PAN Manager, Linux maintains a reference to the veth, but the
pServer is unable to use it.
7-8 PM5.2_BF
Modifying a To modify a pServer’s configuration with the PAN Manager GUI,

pServer use the same pages that you used to configure the pServer
Configuration originally. The following examples illustrate how to modify some
Examples pServer configuration settings.
```To assign a failover pBlade to a pServer:

3. In the Assign/Unassign pBlade as Failover dialog box, select
the radio button next to a specific pBlade Name or Pool.
4. Click OK to save your work, or Cancel to close the dialog box.
In the Failover pBlade area, a pBlade icon appears.
```To unassign or modify a failover pBlade for a pServer:

3. In the Assign/Unassign pBlade as Failover dialog box:
• To reassign the pServer’s failover pBlade setting, select
another pBlade Name or Pool.
4. Click OK.
```To connect a pServer to a network:

• See “Creating Network Connections” on page 6-20.
```To delete a pServer vEth:

• See “Creating Network Connections” on page 6-20.
```To add a SCSI disk to a pServer:

• See “Assigning a Disk to a pServer” on page 6-11.
PM5.2_BF 7-9
```To remove a SCSI disk from a pServer:

```To modify a SCSI disk mapping for a pServer:

7-10 PM5.2_BF
Managing Virtual CD-ROMs
Each pServer has a single virtual CD-ROM drive (VCD), which

enables it to access ISO images registered with PAN Manager as if
they were images on media. The VCD status is displayed for each
pserver under the DVD-ROM column as VCD-ROM.
Note: PAN Manager attaches a VCD to each pServer as unit

number “(125.0)”, but only if that unit number is available. If a
pserver was created under a previous release, it is possible that that
unit number is already used for a SCSI device. As a result, no VCD
is attached. In this case, remove the SCSI device that is numbered
“(125.0)” from the pserver, reattach the SCSI device to the pserver
using a different unit number, and reboot the pServer. The VCD will
then be attached as number “(125.0)”.
You can “insert” one registered ISO image at a time into the VCD
on a pServer. You can also “eject” an image from the VCD. If the
pServer still has the image mounted, you must use the Force option
to eject it.
Note: When a VCD is inserted, some older pServers see its mount
point as /mnt/cdrom1, which is then not otherwise available to the
pServer. As a result, the mount point /mnt/cdrom2 accesses the
media in cBlade A, and the media in cBlade B is not accessible. See
the relevant pServer Integration Note for a workaround, as well as
for information on other VCD management issues that are specific
to the pServer operating system (Windows or Linux).
```To insert an image into a VCD:

1. On the pServer>pServerName page in the Media Drives area,
click Load/Eject.
2. In the Load/Eject Media in Virtual CD-ROM dialog, pull
down the Loaded Media menu.
3. Select the desired image.
4. Click Submit.
PM5.2_BF 7-11
```To eject an image from a VCD:

1. On the pServer>pServerName page in the Media Drives area,
click Load/Eject.
2. In the Load/Eject Media in Virtual CD-ROM dialog, pull
down the Loaded Media menu.
3. On the Loaded Media menu, select [EMPTY].
4. If the pServer still has the image mounted, check the Force
Media Ejection box.
5. Click Submit.
7-12 PM5.2_BF
Managing Boot and Root Disk Images
Each pServer in the PAN has a boot image and Linux pServers on
pBlades (though not on vBlades) also have a root disk image. These
images are created during the pServer installation process. The
respective pServer guides describe how to register the images with
PAN Manager so that they are available to all pServers in the PAN.
The PAN Manager GUI displays boot and root disk images. The
image(s) used by a particular pServer appear on the Dashboard >
pServername page; all available images are shown on the PAN >
PAN Name page. When a new boot image has been created, the
name of the image displays as Custom until the image is registered
with PAN Manager.
Modifying With PAN Manager, the PAN Administrator can modify registered
Registered Boot images in certain ways:
or Root Disk
Images • Change the display name
• Re-import the source image
• Add or change descriptive text about the image
Modifying a Boot Image
```To edit a pServer boot image:

1. In the left pane, click the name of the PAN containing the
pServer boot image that you want to configure.
2. In the right pane, in the Current PAN > Boot Images area, click
the name of the boot image that you want to modify.
3. On the pServer Boot Image page, click Modify.
4. In the Modify Boot Image dialog box, edit any of the following
fields:
• In the Name field, specify a new display name.
PM5.2_BF 7-13
• In the Re-import Source area, select one of the following:

– cBlade file and specify the full directory path on the
cBlades of a boot image file.
– Local file and enter the full directory path of the boot
image file, or use the Browse button to locate the file.
Note: For backward compatibility, PAN Manager also

recognizes boot image files by their base name, and locates boot
image files that have specific suffixes, such as -mu.tftp.
• (Optional) In the OS Type field, add or change descriptive
text about the operating system associated with tthe boot
image file.
• (Optional) In the Description field, change or add other
descriptive text about this pServer boot image.
5. Click Submit.
Modifying a Root Disk Image
```To modify a root disk image:

1. In the left pane, click the name of the PAN containing the root
disk image that you want to modify.
2. In the right pane, in the Current PAN > Root Images area,
click the name of the root disk image that you want to modify.
3. On the Root Image page, click Modify.
4. In the Modify Root Image dialog box, configure the following
fields:
• In the Name field, specify a display name that
administrators use to identify this root image for pServers.
In the Source area, select one of the following:
• Use current source root image (with no changes).
• cBlade file and specify the full directory path on the
cBlades where this image resides. This directory is set
during Linux-based pServer software installation.
7-14 PM5.2_BF
• (Optional) In the OS Type field, add descriptive text about

the operating system associated with this root image.
• (Optional) In the Description field, add other descriptive
text for this root image.
• In the Supported File Systems field, select one or more
check boxes next to the Linux-based filesystem types that
you want associated with this root image.
Select Use as default to set one of the filesystem types that
you selected in the previous step as the default filesystem
type for all Linux-based pServer root images.
Note: If you select only one file system type, you do not need
to select a default; if you select more than one, you must choose
a default. The default can be overridden when you root a new
disk.
5. Click Submit.
Creating Custom You can create boot or root disk images customized to your
Images environment. As with the standard images, these images can be
used exclusively by a single pServer or made available to all
pServers in the PAN. Any custom images you create should be
stored in the /tftpboot directory (for boot images) and the
/images directory (for root disk images) on both cBlades.
If you create custom images and want to register them with the
PAN, use the procedure described in the appropriate pServer guide.
About Rescue Recovery boot images are described in the respective pServer
Mode guides.
PAN Manager allows you to boot from a recovery boot image

without losing access to the configured boot image. At pServer boot
time, you can specify the particular boot image and boot options to
be used. These parameters do not persist for subsequent boots.
PM5.2_BF 7-15
See “Booting, Rebooting, or Shutting Down a pServer” on

page 5-34 for information on performing a one-time override of a
pServer’s configured boot image.
7-16 PM5.2_BF
Configuring pServer Boot Attributes
About pServer There are several attributes of a pServer related to booting. These
Boot Attributes attributes are part of a pServer’s configuration and take effect at the
next pServer boot. They persist until the configuration is changed.
Note: Some attributes can also be specified at boot time for a one-
time override, after which the pServer reverts to its configured
attributes. See in “Booting, Rebooting, or Shutting Down a
pServer” on page 5-34.
The following are the supported pServer boot attributes:

• Boot image—Can be any image that has been registered with
PAN Manager.
The configured boot image may be a PAN-wide default, as
described in “Specifying Default Boot and Root Disk
Images” on page 2-8, or it may be explicitly configured for the
pServer, as described in “Configuring a pServer’s Boot
Attributes” on page 7-18.
If you want to boot a pServer one time with a boot image other
than the pServer’s configured image, you select another boot
image at boot time. See “Booting, Rebooting, or Shutting Down
a pServer” on page 5-34.
• Options—Can specify how the pServer boots in relation to
other pServers in the LPAN.
• optional—The pServer does not have to boot in order for the
LPAN to boot. If a pServer is not optional, the LPAN does
not boot if the pServer boot fails.
• order—The pServer boots in a specified order relative to the
other pServers within the LPAN.
By default, all pServers are optional and without a specified
order.
• Boot arguments—Used to specify the following firmware
options:
PM5.2_BF 7-17
• Hyperthreading (default is On)—enables multithreaded

applications to execute threads in parallel on a single multi-
core processor instead of processing threads in a linear
fashion.
• Node interleaving (default is Off)—interleaves a single
page of memory from each processor at a time.
Administrators use node interleaving to improve the
performance of pServers running applications that do not
support non-uniform memory access (NUMA), which
concatenates all the memory from each processor in a single
block.
• Virtualization extensions (default is On)—used by Egenera
hypervisors to enable guest operating systems to use virtual
device drivers to access the vBlade processing resource on
a pBlade.
• Hardware prefetch (default is Off)—uses the hardware
features of certain pBlades to minimize latency by bringing
data and instructions into higher-speed memory before the
processor needs it. This argument can improve the
performance of pServers running Oracle applications.
Boot arguments persist until the pServer is configured with a
different boot image. If the pServer’s pBlade hardware does not
support a particular firmware option, enabling that option has no
effect.
Use caution when applying boot arguments; incorrect usage can
adversely affect a pServer’s performance.
Also take care when configuring failover pBlades and pools to
ensure that a failover pblade has same the hardware capabilities
and firmware options as the pServer’s primary pBlade.
Configuring a Boot Image and Options

pServer’s Boot
Attributes ```To specify the boot image and boot options for a pServer:
1. On the Dashboard, click a pserver_name.
OR
7-18 PM5.2_BF
In the left pane, click LPAN > LPANname > pserver_name.

2. On the pServer pserver_name page, in the Boot Image/
Options area, click the Modify button.
3. In the pServer Boot Image/Options dialog box:
• In the Boot Image area, select an image to be the configured
boot image.
• The User Defined Boot Arguments field is available for
specifying one or more custom boot arguments.
• Select pServer is optional to indicate that the LPAN should
not fail to boot if this pServer fails to boot.
4. Click Submit.
A boot image icon appears in the Boot Image/Options area of
the pserver_name page.
Boot Order
```To configure the order in which pServers boot within the LPAN:
2. On the LPAN LPANname page, in the pServers area, click the
Boot Order button.
3. In the Configure pServer Boot Order dialog box, specify a
boot order number for each pServer.
The pServer with the lowest number boots first; the highest
boots last. pServers that have the same boot order number boot
simultaneously.
Leaving Zero in an Order field means that the pServer is not
included in this relative order. Ordered pServers within the
LPAN boot before the unordered pServers.
4. Click Submit.
PM5.2_BF 7-19
Boot Arguments
```To enable or disable hyperthreading, node interleaving,

virtualization extensions, or hardware prefetch at the firmware
level for a pServer:
OR
In the left pane, click LPAN > LPANname > pserver_name.
2. On the pServer pserver_name page, click the Advanced
Configuration button.
3. In the Advanced pServer Configuration dialog box, click the
textbox next to the option of interest to expand it.
4. Select Disabled or Enabled from the expanded textbox.
5. Click Submit.
7-20 PM5.2_BF
Using the pServer Console
About the After a pServer is configured and booted, you can open a text
pServer Console console (terminal session) on that pServer from within the
PAN Manager GUI. You can enter console input to the pServer, and
the window displays console output from the pServer’s operating
system.
You can only open a console on pServers you are authorized to

access (in your LPAN administrative domain). Once opened, a
console on a pServer remains open, even after the pServer is shut
down, until it is exited.
Opening a ```To open a pServer console:

Console
1. In the left pane, click LPANs > LPANname > pServername.
2. In the right pane, in the pServer pserver_name page, in the
Controls area, click the Console icon ( ).
The pServer console appears in a separate window. At the top of
the console window, the message Authenticating with server...
appears.
3. When the “Authenticating with server...Authenticated” message
appears, press Enter once to log on to the console.
Using the The pServer console provides terminal access to the pServer’s
Console on operating system. The top border of the console provides various
Linux and information about the operating status of the pServer:
Windows
• LPAN/pServer — The name of the LPAN and the name of the
pServers
pServer.
• Health Light — The health lights are color-coded to indicate
the presence or absence of unresolved events on the pServer. A
health light can be one of the following three colors:
PM5.2_BF 7-21
• Red — The pServer is reporting one or more severity 1

(critical) or 2 (error) events.
• Yellow — The pServer is reporting one or more severity 3
(warning) or 4 (unusual) events.
• Green — All other states.
• pServer Status — The status indicates the state of the pServer:
booted, booting, or shutdown.
• Agent — The agent facilitates communication between the
PAN Manager and the pServer. A blue symbol indicates the
agent is operative. A shaded symbol indicates the agent is
unavailable.
• Controls — The following controls are available from the
console window: boot, reboot, or shutdown.
• Up time — The uptime is measured in days, hours, and minutes.
• pBlade Status — The photo-realistic images matches the color
of the physical indicator light that appears on the pServer’s
pBlade in the chassis. This LED appears on the pBlade's front
panel next to the handle.
Each pBlade can be in one of four states (Active, Recognized,
Standby, or Selected) as indicated by the lights.
• Active (steady blue) — The pBlade is executing software
instructions.
• Recognized (steady amber) — PAN Manager software is
running on the Control Blade. The Control Blade is able to
contact the other pBlades by means of the BladePlane.
• Standby (blinking amber) — The blade is receiving standby
power (the platform is plugged in)
• Selected (blinking blue) — An administrator has designated
the pServer’s pBlade for an administrative action.
• Platform/Blade — The platform name and identifying number
of the pServer’s pBlade.
7-22 PM5.2_BF
Chapter 8
Administering Windows-
Based pServers
This chapter provides information that is specific to configuring

and managing pServers running the Windows operating system,
including alternative ways to connect to a Windows pServer from
the PAN Manager GUI.
This chapter covers the following topics:
• Connecting to a pServer Using the Remote Desktop Protocol

• Connecting to a pServer Using the Virtual VGA Desktop
• Shutting Down Windows pServers
• Disabling the Hyperthreading Feature (Intel Only)
• Managing Device Drivers
• Configuring Network Connections
• Configuring Multipath Storage Support
• Tuning Virtual Memory for Applications
• Recommendations for Running MSCS Clusters
PM5.2_BF 8-1
Connecting to a pServer Using the Remote Desktop

Protocol
The Remote Desktop Protocol (RDP) utility lets administrators

locally display the desktop of a pServer that is running the
Windows operating system. The RDP utility is provided on the
Microsoft Windows CD-ROM. This section covers the following
topics about RDP:
• Opening an RDP Connection
• Reestablishing an RDP Session
• Modifying the pServer IP Address (Optional)
Opening an RDP To open an RDP connection:

Connection 1. Determine the IP address of the Windows pServer:
a. In PAN Manager, click the console control button for the
pServer to open the SAC console.
b. Press Enter until the SAC> prompt appears.
c. Enter the i command to determine which interface you want
to use:
SAC> i
Note: If the IP address is invalid, or you need to change it, see

“Modifying the pServer IP Address (Optional)” on page 8-5.
2. Edit your environment variables to place the path to the RDP
utility in your path. (The default path is C:\Program
Files\Remote Desktop.)
3. Open a Command Prompt window on your client system.

4. Start RDP with the following command:
C:\>mstsc /v:pServer_IP_Address /console
8-2 PM5.2_BF
Administering Windows-Based pServers
5. Log on to the Administrator account to access your pServer

Windows desktop.
Reestablishing If an administrative user is logged on to a pServer using the RDP

an RDP Session utility, it is possible to mistakenly disable the interface that the
pServer relies on for the connection. This terminates the RDP
session, and prevents reconnecting to the pServer and resuming the
RDP session.
To reestablish an RDP connection to a pServer:

1. In PAN Manager, click the console control button for the
2. Press Enter until the SAC> prompt appears.
3. At the SAC> prompt, to open a command session, enter the
following command:
cmd
The following message and a list of available channels appear:

The Command Prompt session was successfully launched
4. To change to the new command session, enter the following

command:
ch –si channel
where channel is a channel name, such as Cmd0001.

The following prompt appears:
Please enter login credentials
5. Enter the username, domain (leave blank if it is the local

computer), and password.
The following prompt appears:
C:\WINDOWS\system32>
6. Enter the following command:

NETSH INTERFACE SHOW INTERFACE
PM5.2_BF 8-3
The interfaces currently associated with the pServer appear

(Figure 8.1).
Figure 8.1 pServer Network Interfaces
Note the name of the interface for which the state is

Unreachable. Ignore the Internal and Loopback interfaces.
If it is still not clear which interface is the one you want to
reestablish, enter the IPCONFIG command. This second list of
interfaces omits the unreachable interface. Compare the two
lists to see which interface is missing.
7. When you have identified the unreachable interface, enter the
following command:
NETSH INTERFACE SET INTERFACE INTERFACE_NAME ENABLED
where INTERFACE_NAME is the name of the unreachable

interface. Enclose INTERFACE_NAME within double quotation
marks if it contains spaces.
8. When a message similar to the following appears, enter the Exit
command to close the command session:
The interface has been enabled, and is trying to get
an IP address.
Ok.
8-4 PM5.2_BF
The interface is reestablished. You can use an RDP client to

connect to the pServer. If you are not able to establish a connection,
enter the i command at the SAC> prompt to verify that an IP address
has been configured for the interface.
Modifying the To access a pServer using RDP, the pServer must have a valid IP
pServer IP address.
Address
(Optional) To modify the IP address of the pServer vEth interface:
1. In PAN Manager, click the console control button for the
2. Press Enter until the SAC> prompt appears.
3. Enter the i command to determine which interface you want to
use:
SAC> i
Output similar to the following appears:

Net: 2, Ip=nnnn Subnet=nnnn Gateway=nnnn
Net: 3, Ip=nnnn Subnet=nnnn Gateway=nnnn
4. Enter the i command to assign the IP address, in the following

format:
SAC> i network-number pServer-IP-address
netmask gateway-IP-address
For example, enter the following command:
SAC> i 2 172.28.5.133 255.255.255.0
172.28.5.254
The sample command assigns the following network addresses

to the pServer:
IP address: 172.28.5.133
Netmask: 255.255.255.0
Gateway: 172.28.5.254
5. When the following message appears, enter the i command

again to verify the new network addresses:
SAC successfully set the IP Address, subnet
mask, and gateway.
PM5.2_BF 8-5
6. To make these network parameter changes persist across

reboots, open the RDP utility from the client computer, and
enter the pServer IP address:
a. Open a Command Prompt window on your client
computer.
b. Start RDP with the following command:
C:\>mstsc /v:pServer_IP_Address /console
7. At the Login prompt, log on to the pServer as Administrator,

and then specify the password that you set in the Winnt.sif file.
8. Select Start > Control Panel > Network Connections > Local
Area Connection.
9. In the Local Area Connection Status dialog box, select the
General tab, and then click Properties.
10. In the Local Area Connection Properties dialog box, select
Internet Protocol (TCP/IP), and then click Properties.
11. In the Internet Protocol (TCP/IP) Properties dialog box, enter
the pServer IP address, netmask, and gateway address.
Connecting to a pServer Using the Virtual VGA

Desktop
The virtual VGA (vVGA) desktop enables remote keyboard, video,

and mouse (KVM) access to a Windows pServer. The vVGA
connection provides GUI access to the pServer desktop in the event
of a network failure. The vVGA desktop uses virtualization
software and the platform backplane to provide a secure, reliable
connection to a pServer Windows desktop, regardless of the state of
the network.
Although desktop access is also available using RDP, the vVGA

desktop provides some additional benefits and flexibility. RDP
relies on network availability to establish a connection to the
8-6 PM5.2_BF
pServer’s desktop. The vVGA desktop uses a different network

architecture than RDP, so it is still available even if you disable the
ability to connect remotely through the pServer System Properties
applet. Using vVGA is analogous to connecting to the desktop
through a console.
This section covers the following topics about the vVGA desktop:
• Requirements and Limitations
• Accessing the vVGA Desktop
• Disabling the vVGA Desktop
Requirements Because vVGA uses Microsoft ActiveX controls, you must access
and Limitations PAN Manager using Microsoft Internet Explorer, version 5.5 or
higher. Depending on your Internet Explorer security settings, you
may see a security warning message asking whether you want to
install and run the Remote Desktop ActiveX Control the first time
that you access the vVGA desktop. Click Yes to accept the
installation.
If you need to configure a firewall to use vVGA, allow inbound

requests to TCP port 3389 and outbound requests on ports 30000
through 30999. If you have a critical need to adjust these ports,
contact Fujitsu Siemens Computers customer support.
The following limitations apply to the vVGA desktop:

• One vVGA connection to the pServer.
• No redirection of devices, such as a disk or printer, to the vVGA
desktop.
• No concurrent vVGA and RDP console sessions.
• No cut and paste to or from the vVGA desktop.
Accessing the To access the vVGA desktop:

vVGA Desktop 1. Start PAN Manager.
The pServer dashboard appears.
PM5.2_BF 8-7
2. Select a pServer.
3. On the pServer_name page, click the vVGA icon.
4. Click in the console window to make it active for input.
5. When prompted to press Ctrl-Alt-Delete, press Ctrl-Alt-End
instead.
Note: On most keyboards, the End key is located next to the

Delete key.
6. Log on using the assigned Administrator username and
password.
The remote desktop ActiveX control substitutes Ctrl-Alt-End
for the Ctrl-Alt-Delete combination used in the normal logon
process.
Disabling the The vVGA desktop is a service that is started by default at boot
vVGA Desktop time, but you can manually disable the service. Because the vVGA
desktop relies on the platform backplane and cBlade for
communication with the pServer, the vVGA desktop may not
perform well during high traffic periods on the cBlade or PAN
Manager network. The enabled service itself, however, does not
impact performance in any way.
To stop the vVGA service and place it in the manual state:

1. Connect to the pServer desktop using RDP.
2. Open the Control Panel.
3. Select Administrative Tools, and then select Services.
4. With the EgenTsrv service selected, right-click to open the
Properties pop-up window.
5. Click the Startup Type drop-down box, and choose Manual.
6. Click the Stop button under Service Status to stop the service.
You can restart the service at any time using the Service Status
Start button.
8-8 PM5.2_BF
Shutting Down Windows pServers
You can shut down a pServer that is running Windows from any of
the following interfaces:
• The PAN Manager GUI or CLI
Note: If you do not have the PAN Agent installed, do not shut
down the pServer from PAN Manager because it results in an
ungraceful shutdown.
• An RDP connection
• A vVGA connection
• A serial text console (SAC console)l
Disabling the Hyperthreading Feature (Intel Only)
Hyperthreading is a feature supported by Intel pBlades but not by

AMD pBlades. By default, Hyperthreading on Windows pServers
is on. You use PAN Manager to enable or disable Hyperthreading at
the BIOS level for a pServer running a 64-bit operating system
(IA32e) or a 32-bit operating system (IA32).
For example, to disable Hyperthreading with the PAN Manager

CLI, use the following command:
# pserver -h no lpan_name/pserver_name
where lpan_name is the name of the LPAN and pserver_name is

the name of the pServer running in the LPAN.
PM5.2_BF 8-9
Note: The -h option of the pserver command is deprecated in PAN

Manager Release 5.1 and replaced with -fe "ht". See PAN
Manager Command Reference for the latest command syntax.
Managing Device Drivers
The Windows pServer includes a set of device drivers that

implement virtual hardware resources on the platform. This section
covers the following topics:
• About Device Drivers
• Device Driver Configuration Restrictions
• Displaying Driver Signatures and Versions
About Device The Windows pServer provides drivers that implement the
Drivers following features:
• vVGA console — EgenMouse, EgenDisplay, EgenKbd,
EgenVga, EgenExp, EgenKVM, and EgenXpt drivers
• SAC console — EgenCon driver
• Storage Area Network (SAN) connections — EgenDsm and
EgenScsi drivers
• Premises network connections — EgenNet driver
• Chassis connections — EgenBmc driver
All of the drivers access the platform fabric and Network Interface
Card (NIC) through the EgenBus and EgenLink drivers, as
Figure 8.2 shows. Figure 8.2 also highlights the drivers that write
events to the Windows Event Log, which can be useful for
diagnosing problems. For information about these events, see the
apropriate pServer guide..
8-10 PM5.2_BF
Figure 8.2 Drivers for Windows pServers

Key:
Virtual VGA Console
Drivers That Write
EgenMouse EgenDisplay Messages to the
Windows Event Log
SAN
EgenVideo
EgenKbd (EgenVga/ EgenDsm
EgenExp)
SAC
Network Console Chassis
EgenKVM EgenScsi EgenNet EgenCon EgenBmc
EgenXpt
EgenBus
EgenLink
NIC/Fabric
PM5.2_BF 8-11
The following table describes the filename and purpose of each

driver shown in Figure 8.2.
Driver Filename Purpose
EgenBmc.sys Provides access to the out-of-band management interface. Notifies

PAN Manager that the system is shutting down, rebooting, or
panicking with the following events in the PAN Manager event log:
• IPMI_SEL_CMD_HALT is displayed for shutdown.
• IPMI_SEL_CMD_REBOOT is displayed for reboot operations.
• IPMI_SEL_PANIC_DUMP and five non-sensor events are displayed
for crashes. The non-sensor events contain the Windows bug check
code associated with the crash.
EgenBus.sys Supports the Fujitsu Siemens Computers bus, and provides a
connection through the switched fabric network (BladePlane).
EgenCon.sys Supports a text-mode console for the pBlade, which consists of the
SAC running in the PAN Manager console window.
EgenDisp.sys Provides the display driver that draws the virtual screen.
EgenDsm.sys Provides the Fujitsu Siemens Computers Device-Specific Module
(DSM) for Microsoft Multipath I/O drivers.
EgenExp.sys Provides the helper library for the EgenVGA driver.
EgenKbd.sys Passes the client keyboard input to the system keyboard class driver.
EgenKVM.sys Ties the virtual Keyboard Video Mouse (KVM) devices to the system,
and provides the remote desktop protocol support that allows a remote
client to connect to a pServer over the Fujitsu Siemens Computers
fabric.
EgenLink.sys Supports the Fujitsu Siemens Computers interconnect interface, and
provides a connection through the switched fabric network
(BladePlane).
EgenMous.sys Provides remote mouse support by passing the client mouse input to
the system mouse class driver.
EgenNet.sys Provides access to the internal and external Ethernet network.
8-12 PM5.2_BF
Driver Filename Purpose
EgenScsi.sys Provides access to the storage devices (physical and virtual) associated
with a pServer.
EgenVga.sys Provides the virtual video device.
EgenXpt.sys Provides the transport layer that connects the EgenKVM driver to the
underlying fabric.
Device Driver While a pServer is running Windows, avoid making the following
Configuration configuration changes:
Restrictions
• Changing the driver signing options.
• Using the Windows Device Manager to disable any platform
devices.
• Changing or uninstalling any device drivers provided by Fujitsu
Siemens Computers.
• Changing settings on either of the communications ports
(COM1 or COM2).
Caution: Failure to adhere to these guidelines could cause the

pServer not to function properly.
You may change the pBlade configured for the pServer. If the new
pBlade has a different architecture than the pBlade in use when you
installed the pServer, the pServer may display a Found New
Hardware Wizard when booting a Windows system on a different
pBlade type. You must follow the wizard instructions to complete
the installation.
PM5.2_BF 8-13
Displaying Driver The device drivers are digitally signed by Microsoft or have Fujitsu
Signatures and Siemens Computers authenticode signatures. During the upgrade or
Versions installation, the installer puts these certificates in the Windows
collection certificate store on the pServer.
To verify which drivers are digitally signed:

1. Open the Control Panel on a pServer desktop.
2. Select System, and click the Hardware tab and the Device
Manager button.
3. Use the Device Manager to select and look at the properties of
individual devices to verify the driver status.
Note: Because of a Microsoft limitation, after the initial
installation of Release 2003.1.1.0, the boot drivers do not
display the digital signatures.
Fujitsu Siemens Computers provides a control panel
(EgenCfg.cpl) that displays the currently installed versions of the
drivers.
To open the Fujitsu Siemens Computers Server Configuration

control panel:
1. Select Control Panel > Fujitsu Siemens Computers Server
Configuration.
2. Click on the General tab.
The result is a list of Fujitsu Siemens Computers device drivers
currently installed on the pServer. The drivers are listed by
filename, version number, and the date/time of creation
(expressed in Coordinated Universal Time (UTC)).
Note: The Created time listed in the Fujitsu Siemens Computers

Server Configuration control panel does not match the times
shown in the Windows Device Manager. The Created column in
the control panel lists the time the driver was copied to the
system as recorded by the operating system. This behavior is
intentional because a user can overwrite the driver without
installing it with the Device Manager.
8-14 PM5.2_BF
To obtain a list of the driver versions that can be printed or

emailed:
1. Install the Microsoft Windows Support Tools by running
\Support\Tools\Suptools.msi from the Microsoft Windows
CD-ROM.
2. Enter the following command:
filever c:\windows\system32\drivers\egen* >> list
The filever command creates a file called list that contains

the driver versions of all the drivers beyond the Windows
drivers, as Figure 8.3. shows.
Figure 8.3 Listing the Virtualization Extensions Drivers
PM5.2_BF 8-15
Configuring Network Connections
You can configure network parameters for the pServer to suit your
application requirements and improve platform performance. This
section covers the following topics:
• Network Configuration Requirements
• Setting the MTU Size for vEths
• Choosing pBlades for a Multicast Environment
• Using IGMP with Microsoft NLB Clusters
Network When you configure the network for Windows pServers, adhere to
Configuration the following guidelines:
Requirements
• If you configure more than one vEth on a Windows pServer:
• The pServer might display a Found New Hardware
Wizard at boot time for each vEth. Follow the sequence of
dialog boxes, and accept the default values.
• You must configure the vEths as multihomed devices and
make all routes persistent.
• You cannot configure Windows pServers as multicast routers.
• The network speed (2 Gbps) that is displayed for the Ethernet
adapter reflects the maximum possible connection speed, not
the actual connection speed.
8-16 PM5.2_BF
Setting the MTU To control the network transmission rate for your pServer, you can
Size for vEths set the Maximum Transmission Unit (MTU) for both internal and
external traffic.
Use the following guidelines to set the MTU values of Windows

pServers:
• For vEths that connect to an external network (with an uplink),

set the MTU to 1500 for optimum network throughput.
• For vEths that connect to the internal network inside the
platform, set the MTU to 1500 for optimum network
throughput.
In the Fujitsu Siemens Computers Server Configuration tool, the

Veth Configuration tab enables you to add new MTU settings or
edit existing settings. This tab displays Registry MTU settings for
the pServer vEth interfaces. Settings for non-existent vEths are
ignored.
To add a new vEth MTU setting:

Configuration.
2. Click the Veth Configuration tab.
3. Click New.
4. In the New Veth Configuration dialog box, specify a valid vEth
number between 0 and 30, enter a valid MTU setting, and then
click OK.
5. Click Close to close the Fujitsu Siemens Computers Server
Configuration tool and save your changes.
6. Reboot the pServer so the MTU changes take effect.
To edit an existing MTU setting:

1. Select a vEth, and then click Edit.
2. In the Edit Veth Configuration dialog box, specify a new MTU
setting, and then click OK.
PM5.2_BF 8-17
3. Click Close to close the Fujitsu Siemens Computers Server

Configuration tool and save your changes.
4. Reboot the pServer so the MTU changes take effect.
The Veth Configuration tab also includes a Small Buffer Mode

check box, which enables memory footprint reduction. Do not set
this check box unless you are tuning the virtual memory used by
specific applications, as described in “Enabling Memory Footprint
Reduction” on page 8-21.
Choosing If you are configuring a multicast environment and have pServers

pBlades for a with different operating systems, use the following criteria to select
Multicast pBlades:
Environment
• If the pBlades have differing performance characteristics,
receiver pBlades should be faster than sending pBlades.
• If pBlades have equivalent CPU speeds, Linux pServers should
receive from Windows pServers rather than send to Windows
pServers.
Using IGMP with Release 2003.1.1.0 supports Layer 2 network switching, which
Microsoft NLB enables support for Microsoft Network Load Balance (NLB)
Clusters clusters. Running NLB Manager in unicast mode relies on switch
flooding, which is significantly rate limited by the cBlades and
causes unreliable behavior. To avoid this behavior, run NLB
Manager in multicast mode with Internet Group Management
Protocol (IGMP) enabled.
8-18 PM5.2_BF
Configuring Multipath Storage Support
You can alter the Multipath I/O (MPIO) configuration for the
pServer by activating or deactivating the Fujitsu Siemens
Computers DSM driver (EgenDsm.sys), which supports Microsoft
MPIO drivers.
To configure MPIO:
Configuration.
2. Click the Multi-Path Configuration tab.
The Multi-Path Configuration tab shows the MPIO
configuration for your storage devices and has the following
sections:
• The first pane controls whether multipath support is enabled
or disabled.
• The second pane lists device types for which MPIO is
configured by the Fujitsu Siemens Computers DSM driver.
• The third pane is for use by Fujitsu Siemens Computers
customer support only.
• The fourth pane lists device types for which MPIO is not
configured.
3. If you want all device types enabled for multipath support, click
Enable in the top pane. The devices configured through the
Fujitsu Siemens Computers DSM now appear in the second
pane.
4. If you plan to use multipath software provided by a vendor other
than Fujitsu Siemens Computers, click Disable in the top pane
to completely disable multipath support. Multipath support is
disabled for all device types listed in the bottom pane.
5. To close the Fujitsu Siemens Computers Server Configuration
tool and save your changes, click Close.
PM5.2_BF 8-19
6. To install another vendor’s multipath driver, or to configure the

MPIO characteristics of individual device types, contact Fujitsu
Siemens Computers customer support.
7. Reboot the pServer so the MPIO changes take effect.
Tuning Virtual Memory for Applications
For applications that use large amounts of virtual memory, you need
to make some configuration changes to improve performance.
Specifically, you need to make changes to both the Microsoft
Windows virtual memory configuration and reduce the memory
footprint of the device drivers, as outlined in the following sections:
• Setting Switches in the boot.ini File
• Enabling Memory Footprint Reduction
Setting Switches When under heavy load, Windows pServers can run out of non-
in the boot.ini paged pool or Page Table Entries (PTEs) if the /3GB switch has
File been set in the boot.ini file.
Some applications running on Windows pServers benefit from the

use of the /3GB switch in the boot.ini file, which provides 3GB of
user-space Virtual Memory (VM) to the application and only 1GB
of kernel-space VM for the operating system and drivers.
Unfortunately, the 1GB of kernel-space VM does not provide
enough space for both the Windows kernel services and the device
drivers. In a standard configuration (that is, without the
/3GB switch), the 4GB of VM is divided evenly, with 2GB for user-
space VM and 2GB for kernel-space VM.
To allow enough VM for the drivers, use the /userva switch

together with the /3GB switch in the boot.ini file. Specifically, if
you use /userva=3030, you allocate an additional 42MB of kernel-
space VM, which is the minimum recommended for running the
8-20 PM5.2_BF
drivers. If you want, you can use

/userva=2900, which allocates an additional 172MB of kernel-
space VM. For more information on the use of the /3GB and
/userva switches as recommended by Microsoft, see the following
Microsoft Knowledge Base article:
How to use the /userva switch with the /3GB switch to tune the
User-mode space to a value between 2 GB and 3 GB
http://support.microsoft.com/kb/316739/
Enabling The pServer virtualization extensions include two features that can
Memory improve memory utilization by applications:
Footprint
• Packet collapsing collapses multiple packets for send/receive
Reduction
and is turned on by default in Release 2003.1.1.0 pServers.
Packet collapsing does not impact network connectivity or
performance to other pServers or uplink destinations.
• To enable memory footprint reduction, you set the Small Buffer
Mode check box in the Veth Configuration tab of the Fujitsu
Siemens Computers Server Configuration control panel,
which also changes the MTU size for all vEths to 1500. You
must reboot the pServer for the buffer size change to take effect.
Memory footprint reduction does not impact network
connectivity, but might cause lower performance.
Note: When you enable memory footprint reduction, the

network driver automatically turns off the distributed multicast
algorithm. The distributed multicast algorithm distributes
Ethernet packets among cBlades and pBlades. The pBlades
share in the distribution work, which reduces the load on the
cBlade, and provides some parallelism and network
performance benefits.
PM5.2_BF 8-21
Recommendations for Running MSCS Clusters
One of the advantages of PAN Manager is the ability to easily

repurpose your computing resources: that is, to assign and reassign
pBlades to various tasks when they are most needed. This section
provides general recommendations (as opposed to detailed
procedures) about repurposing Windows pServers within a
Microsoft Cluster Server (MSCS) cluster and covers the following
topics:
• MSCS Requirements
• Repurposing Example
• MSCS Clustering Considerations
• Adding Nodes to Running Clusters
MSCS To use MSCS, you need PAN Manager Release 4.0 or higher, which
Requirements provides support for SCSI reservations.
Repurposing This section presents a general example of repurposing. Assume

Example that your business receives a heavy amount of web traffic on
weekdays from 6 AM to 8 PM and performs most of its accounting
processing after 8PM:
• In a traditional datacenter, you devote separate machines to
these applications, and have one set of resources remain
relatively idle while the other resources are busy.
• In the Fujitsu Siemens Computers PAN, you specify certain
pBlades as web servers starting at 6 AM, and then reboot as
accounting resources at 8 PM.
To implement this configuration in a platform with 12 pBlades, you

allocate resources as follows:
• Assign 10 pBlades to an LPAN pool for active pServers.
• Assign 2 pBlades in a global pool for failover.
8-22 PM5.2_BF
• Create 12 pServers, 10 of which are active at any one time:

• 8 pServers are devoted to web processing and always
booted.
• 2 pServers are devoted to web processing, but are only
active from 6 AM to 8 PM.
• 2 pServers are devoted to after-hours accounting
processing, and are only active from 8 PM to 6 AM.
You configure the pServers to get a pBlade from the pool when they
boot, which results in the following:
• From 6 AM to 8 PM, all 10 active pBlades are hosting all 10 web
pServers.
• At 8 PM, two web pServers shut down, which returns their
pBlades to the pool.
• After the two web pServers shut down, the two accounting
pServers boot with the appropriate disks for their applications
and acquire the recently freed pBlades from the pool.
To automate the shutting down and booting of these pServers, you

need to develop cron jobs that run on the cBlades. The basic script
to halt one pServer and restart another could be a variation of the
following:
ssh $USER@$PANIP "/opt/panmgr/bin/esh pserver -swqf $LPAN/app1"

ssh $USER@$PANIP "/opt/panmgr/bin/esh pserver -b $LPAN/app2"
where $USER specifies a valid login account on PAN Manager

specified by $PANIP, and $LPAN specifies the appropriate LPAN for
the app1 and app2 pServers.
Note: The first line simply forces the running pServer to halt. In a
production environment, you need to precede this line with
customized operating system (OS) and application procedures to
cleanly stop all activity before shutting down the pServer. These
procedures vary with the application, external load balancers, and
other configuration details.
PM5.2_BF 8-23
MSCS Clustering With MSCS, one of your processing resources is dedicated as a

Considerations passive failover node. For example, three of your servers may be
devoted to running Microsoft Exchange Server, while a fourth
server remains idle. This idle resource only becomes active in the
following situations:
• One of the active nodes in the cluster fails.
• You manually replace an active node with the passive node, so
that you can perform a patch or other maintenance procedure on
the original active node.
With PAN Manager, you can repurpose the passive node so it is

productive in another role while it is not needed by the cluster. The
only overhead introduced by this strategy is boot time: it takes a
little longer to reboot a pServer as an MSCS failover node than it
does for an idle passive node to become active. A “cluster-aware”
application, such as Microsoft Exchange, can gracefully fail over a
cluster node to a passive node with minimal server interruption. In
most situations, the ability to use a nonproductive server outweighs
the overhead of rebooting a pServer.
If you run MSCS in a PAN, set it up with the recommended number

of active nodes plus one passive node. Then, you shut down the
pServer that is the passive node, and reboot another pServer on that
newly freed pBlade, making an otherwise idle resource fully
productive.
When you need to do a patch update on the active nodes, you can
reboot the passive node pServer and use it to fail over an active
node. Then you perform the maintenance work on the formerly
active node, just as in any other MSCS environment.
Specific cluster failure behavior depends on the type of failure:

• A hardware or operating system failure is handled by PAN
Manager, which attempts to reboot, or by the OS, which
performs a crash dump followed by a reboot.
• An application failure is caught by the cluster server monitors,
and the cluster server attempts to restart the failed service some
number of times, depending on the configuration.
8-24 PM5.2_BF
Note: If the cluster server cannot restart a failed application, it

does not migrate to the passive node if the passive node is
repurposed.
Adding Nodes to If you add a node to a cluster and the added node hasn’t seen the
Running shared disks in a non-reserved state, the Add Node to Cluster
Clusters Wizard fails. Non-reserved state means the shared disks aren’t
added to the node until the Microsoft Windows installation is
complete and the cluster is running. To work around this, use the
Advanced button in the cluster wizard and select Advanced
Minimum Cluster Configuration.
PM5.2_BF 8-25
8-26 PM5.2_BF
Part III
Creating Application
Services
Part III of this guide outlines the tasks involved in creating

application services, and consists of the following chapters:
• Chapter 9, “Configuring Resources”

• Chapter 10, “Configuring Applications for PAN Manager
Control”
• Chapter 11, “Configuring Load Balancers”
PM5.2_BF
Chapter 9
Configuring Resources
This chapter describes using PAN Manager for configuring

resources that provide the following for applications and load
balancers:
• Failover policies (not supported on Windows pServers)
• Health monitor policies
• Storage
• Network connectivity
• Schedule the starting and stopping of an application or load
balancer
This chapter includes the following sections:

• About Resources
• About Services
• Enabling and Disabling Use of Resources and Services on
pServers
• Configuring Executable Resources
• Modifying Executable Resources
• Configuring Network Resources
• Modifying Network Resources
PM5.2_BF 9-1
• Configuring SCSI Disk File System Resources

• Modifying SCSI File System Resources
• Configuring Network File System Resources
• Modifying Network File System Resources
• Configuring Failover Policy Resources
• Modifying Failover Policy Resources
• Configuring User-Defined Monitor Resources
• Modifying User-Defined Monitor Resource Configurations
• Configuring Health Monitor Resource Configurations
• Modifying Health Monitor Resource Configurations
• Extracting Application Templates
After configuring the resources that the applications and load

balancers that run in your environment require, you assign them to
these applications or load balancers. In the case of application
templates, you simply extract the resources that reside in the
template to make them available to the pServers that reside in the
LPAN.
To learn how to assign resources for use with applications, see

Chapter 10, “Configuring Applications for PAN Manager Control”.
To learn how to assign resources for use with load balancers, see
Chapter 11, “Configuring Load Balancers”.
9-2 PM5.2_BF
About Resources
With PAN Manager, you configure as stand-alone entities the

resources that services use. (Examples of services are applications
and load balancers.) Resources are logical groupings of unique
types of configuration information. You select one or more resource
types and use them as building blocks to instruct PAN Manager on
how to control an application or load balancer. For example, you
can select resource types that do the following:
• Start and stop an application or load balancer
• Provide disk storage resources for an application
• Specify a network connection, failover policy, and health
monitor resources for an application or load balancer
All resources share the following characteristics:

• Resource names
LPAN administrators can rename resources at any time. LPAN
administrators can also assign resources of different types with
the same name. For example, a network resource and an
executable resource can both be named apache.
• Resource devices (for example, storage devices)
PAN Manager automatically adds a resource device to a pServer
when the application the device is configured with starts. You
do not need to configure the resource device on the pServer prior
to starting the application.
• Starting and stopping of resources
Resources cannot be started and stopped directly. Instead,
resources start and stop when the applications or load balancers
configured with them start and stop.
• Start order of resources
PM5.2_BF 9-3
PAN Manager starts resources in the following order based on

type:
• SCSI disk file system resources
• Network file system resources
• Network resources
• Executable resources
PAN Manager does not start a failover policy resource. Instead
PAN Manager uses the collection of resources associated with a
specific failover policy to determine which pServer the
application or load balancer attempts to run in case of a failover
or move operation.
In the case of health monitor resources, PAN Manager
automatically starts the health monitor after the application or
load balancer the health monitor is configured with successfully
starts.
LPAN administrators can configure the following resource types

independently:
• Network file system (NFS) resources
• Failover policy resources
• User defined monitor resources
• Health monitor resources
• Application templates
The following sections provide brief descriptions of each resource

type. Later sections in this chapter describe these resource types in
more detail.
9-4 PM5.2_BF
Executable Resources
Executable resources are a collection of attributes (for example,

command, description, start and stop arguments, and so forth) that
allow users to run a program or script (for example, Linux style init
scripts) on a pServer when an application starts or stops. LPAN
administrators can use any command or set of arguments in a
program or script, and run the program or script as any valid user on
the pServer.
Note: The stopping and starting of multiple executable resources

will be allowed for those resources shared among several
applications running on the same pServer. Executable resources will
be executed on the pServer for subsequent applications even if it was
already started for the first application. The resource will be
executed for the first application when stopping even if it is still
started on subsequent applications on the same pServer.
You can use an executable resource to start services with Linux

style init scripts or any other script or executable that runs on a
pServer. LPAN administrators can configure executable resources
only with applications, not with load balancers.
For more information and to learn how to configure executable

resources, see “Configuring Executable Resources” on page 9-13.
Network Resources
Network resources are a collection of attributes (for example, IP

address, netmask, broadcast address, and so forth) that allow users
to configure a network connection on a pServer. LPAN
administrators can then assign the configured network resources to
applications and load balancers. PAN Manager provides a default
netmask and broadcast address if an administrator configures only
the IP address. Administrators can configure network resources to
be used with applications and load balancers.
For more information and to learn how to configure network

resources, see “Configuring Network File System Resources” on
page 9-30.
PM5.2_BF 9-5
SCSI Disk Resources
PAN Manager provides two types of disk resources: disks in the

LPAN (SCSI disk resources) and disks shared over a network
(network file system resources). PAN Manager makes both types of
disk resources available on a pServer when the resource starts.
SCSI disk resources are a collection of attributes (for example,

device name, partition, mount point for the file system, and so
forth) that allows users to specify storage resources for a pServer.
LPAN administrators can then assign the configured SCSI disk
resources to applications. LPAN administrators cannot assign the
configured SCSI disk resources to load balancers.
For more information and to learn how to configure SCSI disk

resources, see “Modifying SCSI File System Resources” on
page 9-27.
Network File System Resources
In addition to SCSI disk resources, PAN Manager provides network

file system (NFS) resources. Network file system resources are a
collection of attributes (for example, host name, host file system
name, user name, and so forth) that allows users to define a disk
shared over a network for a pServer. LPAN administrators can then
assign the configured NFS resources to applications and load
balancers. NFS resources allow applications and load balancers to
access storage not made available within the LPAN.
For more information and to learn how to configure NFS resources,

see “Configuring Network File System Resources” on page 9-30.
Failover Policy Resources
Failover policy resources are a collection of attributes (for example,

pServer reboot options, pServer failback options, selection policy,
and so forth) that define a specific failover policy for a primary
pServer. A failover policy determines the pServers to which an
9-6 PM5.2_BF
application or load balancer can move or fail over. LPAN

administrators can then assign the configured failover policy
resources to applications and load balancers.
For more information on and to learn how to configure failover

policy resources, see “Configuring Failover Policy Resources” on
page 9-34.
User-Defined Monitor Resources
User-defined monitor resources are a collection of attributes (for

example, event name, schedule interval, and so forth) that allows
users to create a set of health, status, or statistical monitors whose
events could be used to enhance control over PAN Manager
behavior. For example, LPAN administrators can configure user-
defined monitor resources to create a monitor that triggers a service
restart, failover, or stop operation. LPAN administrators can assign
the configured user-defined monitor resources to applications and
load balancers.
For more information and to learn how to configure user-defined

monitor resources, see “Configuring User-Defined Monitor
Health Monitor Resources
Health monitor resources are a collection of attributes (for example,

name, pServers to be added, time delay to start, and so forth) that
define a specific health monitor to be used with services
(applications and load balancers). A health monitor periodically
tests the connection to the service using the service’s configured IP
address (a network resource). LPAN administrators can configure
health monitor resources that allow a health monitor to trigger a
service restart, failover, or stop operation.
For more information and to learn how to configure health monitor

resources, see “Configuring Health Monitor Resource
Configurations” on page 9-46.
PM5.2_BF 9-7
Application Templates
An application template is an object that encapsulates all of the

components and values associated with a specific template archive.
Application templates exist as files with .ptf extensions and reside
in the /opt/panmgr/templates directory on the cBlade.
For more information and to learn how to extract application

templates, see “Extracting Application Templates” on page 9-63.
About Services
Services are logical groupings of the different resource types (for

example, executable resources, network resources, NFS resources,
and so forth). An administrator independently selects the resources
required for an application or load balancer.
A service determines and enforces the order in which the selected

resources start and stop. Services can monitor themselves and take
appropriate actions when they detect failures. PAN Manager
supports the following services:
• Applications
• Load balancers
All services share the following characteristics:

• When a pServer is shutdown or rebooted
When PAN Manager shuts down or reboots a pServer that is
running a service, the shut down or reboot fails with an
appropriate message that alerts an administrator that services are
running on this pServer.
To shut down or reboot a pServer that is running one or more
services, an administrator must force the shutdown or the reboot
of the pServer.
9-8 PM5.2_BF
• When a service requires more than one network resource

To accommodate applications that require multiple IP
addresses, administrators can configure a service with multiple
network resources (specifically, multiple IP addresses).
Administrators can also configure multiple IP addresses on a
single netowrk resource.
• When a service needs to be moved
Administrators can configure a failover policy resource that
causes the service to be moved to a specified available pServer.
Another configuration scheme allows administrators to
configure a failover policy resource that causes the pServer to
automatically be selected to receive the moved service.
• When a service needs to be configured with multiple health
monitors
An administrator can configure a service with multiple health
monitors. For each health monitor added to the service, an
administrator must specify the IP address to be associated with
the health monitor. The health monitor uses this IP address when
checking the health of the service.
The following sections briefly describe applications and load

balancers.
Application An application service is a logical grouping of the different

Services resource types (for example, executable resources, network
resources, NFS resources, and so forth) that determines and
enforces the order in which the selected resources are started,
stopped, moved, and failed over together for a specific application.
An administrator independently selects the resources required for
an application service.
The following are some of the characteristics associated with

application services:
• Stand-alone or member of a load-balancing service
PM5.2_BF 9-9
An administrator can add an application service (even when the

application service is running) as a member of a load-balancing
service. The application service can also execute as a stand-
alone service.
• Associate a health monitor with an application service
Because an application service supports multiple network
resources (specifically, multiple IP addresses), an administrator
must associate a health monitor with one of the application
service’s IP addresses.
An administrator can configure any number of executable
resources for the application service. The stopping and starting
of multiple executable resources will be allowed for those
resources shared among several applications running on the
same pServer. Executable resources will be executed on the
pServer for subsequent applications even if it was already
started for the first application. The resource will be executed
for the first application when stopping even if it is still started on
subsequent applications on the same pServer.
• NFS resources
An administrator can configure NFS resources with an
application service.
• Modifying resources
An administrator can modify certain resources (for example,

autostart, description, failover policy, health monitor, and so forth)
while the application service is running.
For more information and to learn how to configure applications,

see Chapter 10, “Configuring Applications for PAN Manager
Control”.
Load-Balancing A load-balancing service is a logical grouping of the different

Services resource types (for example, network resources, NFS resources,
and so forth) that determines and enforces the order in which the
selected resources are started, stopped, moved, and failed over
9-10 PM5.2_BF
together for a specific load balancer. An administrator

independently selects the resources required for a load-balancing
service.
Load-balancing services use the Linux Virtual Server to disperse

requests across several instances of the same application running on
multiple pServers. A load-balancing service runs on a pServer
where administrators can monitor it and configure it with a failover
policy. Administrators can add application services as members to
the load-balancing service.
The following are some of the characteristics associated with load-

balancing services:
• Stand-alone or member of a load-balancing service
An administrator can add an application service (even when the
application service is running) as a member of a load-balancing
service. The application service can also execute as a stand-
alone service.
• Configured with multiple port/protocol combinations
An administrator can configure the load-balancing service with
multiple port/protocol combinations, including the ability to
configure persistence between the client and the load-balancing
member to which it first connected.
• Starting members of a load-balancing service
Administrators can configure load-balancing members to start
when the load-balancing service starts. PAN Manager generates
a warning if a load-balancing member starts and its associated
load-balancing service has not started.
• Modifying resources
An administrator can modify resources (for example, autostart,

description, failover policy, health monitor, and so forth) while the
load-balancing service is running.
For more information and to learn how to configure load balancing

services, see Chapter 11, “Configuring Load Balancers”.
PM5.2_BF 9-11
Enabling and Disabling Use of Resources and

Services on pServers
You can control whether resources (for example, executable

resources) and the services (for example, applications and load
balancers) that use these resources can run on individual pServers.
This feature is useful when a pServer runs applications that deal
with sensitive information.

Enabling and ```To allow or disallow application services (applications or load

Disabling balancers) to be run on a pServer:
Application
1. Log in to the pServer. (You must have root permission on the
Services
pServer.)
2. Navigate to the properties file that allows/disallows application
services to run on the pServer.
cd /opt/panmgr/bin
Note: If the egenera.panagent.properties file does not reside in

this directory, create the file, make its owner root, and give the
file read-write permissions.
3. Open the egenera.panagent.properties file in a text editor, and do
one of the following.
• By default, application services are enabled. To disable
application services from running on the pServer, change
the line
ha.enable=true
9-12 PM5.2_BF
to
ha.enable=false
• To enable application services to run on the pServer, change

the line
ha.enable=false
to
ha.enable=true
Save your changes to the egenera.panagent.properties file.

4. To allow the new setting to take effect, reboot the pServer.
Configuring Executable Resources
About Executable resources are a collection of attributes (for example,

Executable command, description, start and stop arguments, and so forth) that
Resources allow users to run a program or script (for example, Linux style init
scripts) on a pServer when an application starts or stops.
LPAN administrators configure instances of executable resources

by specifying a name and some or all of the following attributes:
• Command to be executed
• Description
• Start, stop, and run arguments
• User name
The result is an executable resource configuration that LPAN

administrators can assign to any number of applications when
configuring those applications. LPAN administrators can define
any number of executable resource configurations.
PM5.2_BF 9-13
The stopping and starting of multiple executable resources will be

allowed for those resources shared among several applications
running on the same pServer. Executable resources will be
executed on the pServer for subsequent applications even if it was
To learn how to assign executable resource configurations to an

application, see Chapter 10, “Configuring Applications for
PAN Manager Control”. You cannot assign executable resource
configurations to a load balancer.
Role Required LPAN Administrator

for This Task
Create ```To create an executable resource:

Executable
1. In the left pane, click LPANs > LPANname > High
Resources
Availability.
2. In the High Availability for LPAN LPANname page, in the
Executable Resources area, click the Create button.
3. In the Create Executable Resource dialog box, enter
appropriate information in the following fields:
• Enter a Name for the executable resource.
• Optionally enter a Description for the executable resource.
• Enter the Command associated with this executable
resource.
• Optionally enter appropriate Start Arguments, Stop
Arguments, or Execute Arguments.
• Optionally specify in Run as user the name of the pServer
operating system user account as which the executable
resource will run. (Leaving this field blank causes the
executable resource to run as the same user as the PAN
Agent, which on Linux is root.) For each executable
9-14 PM5.2_BF
resource that you configure on the pServer, be sure to

override, in its script, any of these variables, as appropriate,
to allow the application to run properly.
• To source the user environment of the user you specify in
the Run as user field, select the source user environment
check box. (This means that the existing environment, and
any variables specified in the application that is associated
with this executable resource, will be lost.)
• Optionally select the check box next to Proceed directly to
resource page after creation.
dialog box.
After you create an executable resource, an Executable
Resourcename icon appears in the Executable Resources area.
```To delete an executable resource:

Availability.
Executable Resources area, click the Delete button.
3. In the Delete Executable Resources dialog box, select the
check box next to the executable resource Name that you want
to delete.
4. Click Delete, or click Cancel to close the dialog box.
After you delete an executable resource, its Executable
Resourcename icon no longer appears in the Executable
Resources area.
PM5.2_BF 9-15
Modifying Executable Resources
This section discusses how to modify executable resources.
About Modifying The LPAN Administrator modifies executable resources.

Executable
Resources Use the same procedure to modify executable resources as you did
to create them. See “Create Executable Resources” on page 9-14.
You can modify executable resources in the following ways:

• Create a new executable resource.
• Delete an existing executable resource.
• Rename an existing executable resource.
• Modify the stop and execute arguments and the description
while the executable resource is running.
• Modify the start argument. In this case, the executable resource
must not be running.
• Modify the user associated with the executable resource. In this
case, the executable resource must not be running.
Modifying ```To modify an executable resource configuration:

Executable
Resources
Availability.
2. In the Executable Resources area, click the Executable
Resourcename that you want to modify.
3. In the Executable Resource Executable Resourcename page,
4. In the Modify Executable Resources dialog box, make
appropriate modifications for this executable resource.
9-16 PM5.2_BF

dialog box.
Configuring Network Resources
About Network Network resources provide LPAN administrators with the ability to
Resources create IP addresses, netmasks, and broadcast addresses,
independent of physical interfaces. Before configuring network
resources for applications or load balancers, review the following
topics:
• Items to consider when configuring IP addresses
• Attributes to specify when configuring network resources
Items to Consider When Configuring IP Addresses
In a PAN, IP addresses are created as resources independent of

physical interfaces. By creating an independent resource, IP
addresses can be easily moved to another pServer in a failover
scenario. The IP resource may contain all the information usually
associated with an IP address: the address itself, the netmask, and
the broadcast address. Only valid combinations of IP address,
netmask, and broadcast address are allowed. If you specify only the
IP address, a default netmask and broadcast are created. If you
specify an IP address and netmask, a default broadcast address is
created.
If your application or network environment requires that network

traffic be sent at a specific speed, instead of best effort, you may
configure the vEth on the pServer running that application to send
network packets at 10 MB, 100 MB, or unlimited. If a specific vEth
is used for an application, specify that vEth when creating the IP
resource.
PM5.2_BF 9-17
Note: If you want an application that uses a specific network traffic

speed to fail over, you must configure all of the pServers in the
failover cluster to use the same vEth for the specified network speed
(i.e. the same vEth on all of the pServers must be set to the same
network speed).
Attributes to Specify When Configuring Network

Resources
LPAN administrators configure network resources for a service by

specifying the following attributes:
• IP address and IP name
• Netmask
• Broadcast address
• Name of the vSwitch
• Name of the vEth
• LPAN name
After configuring a network resource, LPAN administrators can

assign the network resource to any number of applications or load
balancers.
To learn how to assign network resources to an application, see

To learn how to assign network resources to a load balancer, see

for This Task
Create Network ```To create a network (IP) resource:

Resources
Availability.
9-18 PM5.2_BF

Network Resources area, click the Create button.
3. In the Create Network Resource dialog box, enter appropriate
• Enter a Name for the network resource.
• Optionally enter a Description for the network resource.
• Configure this network resource Interface by selecting the
radio button next to Ethernet, vSwitch or None and select
the vSwitchname or vEthnumber from the appropriate
pull-down list. Be sure that the vSwitch or vEth you select
is also configured on the pServer on which the application
using the network resource is installed. Select None if you
want to configure this network resource Interface later.
• Configure this network resource’s Network Settings by
specifying an IP address, a Broadcast Address, and
Netmask Address associated with the network resource.
dialog box.
After you create a network resource, a Network Resourcename
icon appears in the Network Resources area.
```To delete a network (IP) resource:

Availability.
Network Resources area, click the Delete button.
3. In the Delete Network Resources dialog box, select the check
box next to the network resource Name that you want to delete.
After you delete a network resource, its Network
Resourcename icon no longer appears in the Network
Resources area.
PM5.2_BF 9-19
Modifying Network Resources
This section discusses how to modify network resources.
About Modifying The LPAN Administrator modifies network resources.

Network
Resources Use the same procedure to modify network resources as you did to
create them. See “Create Network Resources” on page 9-18.
The following list describes some of the modifications you can

make to network resources:
• Create a new network resource.
• Delete an existing network resource.
• Remove an IP address.
• Assign a vSwitch as an interface to an IP resource.
• Assign a MAC address if a vSwitch is configured for an IP
resource.
• Rename an existing network resource.
Modifying ```To modify a network (IP) resource configuration:

Network
Resources
Availability.
Network Resources area, click the Network Resourcename
3. In the Network Resource Network Resourcesname page,
click the Modify button at the top of the page.
4. In the Modify Network Resources dialog box, make
appropriate changes in any of the configurable fields.
9-20 PM5.2_BF
Modifying ```To add a network setting for this network (IP) resource:
Network Settings
for a Network
Availability.
Resource
3. In the Network Resource Network Resourcesname page, in
the Network Settings area, click the Create button.
4. In the Create Network Settings dialog box, specify an IP
address, a Broadcast Address (optional), and Netmask
Address (optional) that you want associated with this network
resource.
```To delete any network setting(s) for this network (IP) resource:
Availability.
the Network Settings area, click the Delete button.
4. In the Delete Network Settings dialog box, select the check box
next to the IP Address(es) that you no longer want associated
with this network resource.
```To modify network settings for this network (IP) resource:

Availability.
PM5.2_BF 9-21

the Network Settings area, click the Modify button.
4. In the Modify Network Settings dialog box, click the IP
address heading whose Broadcast Address or Netmask
Address settings you want to modify.
5. Enter a valid Broadcast or Netmask address associated with the
IP address for this network resource setting.
9-22 PM5.2_BF
Configuring SCSI Disk File System Resources
About SCSI Disk SCSI disk file system resources provide LPAN administrators with
File System the ability to create and add mount points, gain access to file
Resources systems, and specify partition information. Before configuring
SCSI disk file system resources for an application, review the
following topics:
• How PAN Manager handles file systems
• Items to consider when configuring file systems
• Attributes to specify when configuring SCSI disk file system
resources
How PAN Manager Handles File Systems
PAN Manager allows file systems to be shared among different

applications. Applications that share a read-write file system must
have the same failover policy (or no failover policy). The LPAN
Administrator is responsible for proper sharing of file systems.
PAN Manager software mounts and enables the dependent file

systems in the order specified, before starting the application. When
PAN Manager stops an application, it unmounts and disables
dependent file systems. If PAN Manager cannot clean a dependent
resource, it is the responsibility of the pServer administrator to
diagnose and correct the problem. The administrator should also
reissue the stop operation to clean the failed resource. If you force
stop an application, a load-balancer, or member of a load-balancer,
PAN Manager automatically unmounts the file system.
Items to Consider When Configuring File Systems
Just as with IP addresses, file systems are also created as resources.

By creating an independent resource, PAN Manager can easily
move file systems to another pServer in a failover scenario. The file
PM5.2_BF 9-23
system resource can contain all the information usually associated

with a file system: the mount point, the device associated with the
file system, and the mode (read-only or read/write).
Attributes to Specify When Configuring SCSI Disk File

System Resources
Administrators configure SCSI disk file system resources for an

application by specifying the following attributes:
• Mount points
• SCSI device IDs
• File systems
• Partitions
To learn how to assign SCSI disk resources to an application, see

You cannot assign SCSI disk resources to a load balancer.

for This Task
Create SCSI Disk Creating a SCSI disk file system is step is necessary only if the
File System application requires a file system.
Resources
Note: You can configure the same disk and partition in only one
SCSI disk file system resource. In other words, PAN Manager
considers configuring the same disk and partition in multiple SCSI
disk file system resources as invalid configurations. If such an
invalid configuration exists and you attempt to modify the
associated SCSI disk file system resource, PAN Manager displays
an appropriate error message. The error message identifies the SCSI
disk file system resource in which the conflict exists. You can only
remove (not modify) the SCSI disk file system resource in which the
conflict exists.
9-24 PM5.2_BF
Creating a SCSI File System Resource
```To create a SCSI file system resource:

Availability.
SCSI File System Resources area, click the Create button.
3. In the Create SCSI File System Resource dialog box, enter
• Enter a Name for the SCSI file system resource.
• Optionally enter a Description for the SCSI file system
resource.
• In the SCSI Disk area, select the radio button next to a SCSI
Id that has already been added to an LPAN. If no SCSI Id
disks are listed, you must add the disk(s) to the LPAN before
they appear. Select None to configure these settings later.
• In the Mount Point area, enter appropriate information in
the following fields:
– Enter the full Path from the pServer’s root file system
for this SCSI file system resource’s mount point.
– Use the pull-down menu to select the disk Partition on
the SCSI Id to which the file system resource’s mount
point points.
– Enter an integer in the Mount Order field to specify the
order that PAN Manager uses to mount this file system
mount point relative to the other mount points
configured for this file system.
– Enter any Mount Options to specify as arguments to
the Linux mount command, such as -t ufs. Do not
include "mount" here.
– Select the desired Mode for the SCSI file system
resource, either read/write or read only, using the pull-
down menu.
PM5.2_BF 9-25
– Optionally select the check box next to Create mount

point if it does not exist to allow PAN Manager to
automatically create the mount point, if it does not exist.
– Optionally select the check box next to Scan partition
before mounting to check, and optionally repair, the
partition before the partition is mounted.
If you selected Scan partition before mounting, you can
also specify any options in the Scan options (optional)
field, such as the partition’s file system type, to allow the
scan to run successfully.
dialog box.
After you create a SCSI file system resource, a SCSI File
System Resourcename icon appears in the SCSI File System
Resource area.
Deleting a SCSI File System Resource
```To delete a SCSI file system resource:

Availability.
SCSI File System Resources area, click the Delete button.
3. In the Delete SCSI File System Resources dialog box, select
the check box next to the SCSI file system resource Name that
you want to delete.
After you delete a SCSI file system resource, its SCSI File
System Resourcename icon no longer appears in the SCSI File
System Resources area.
9-26 PM5.2_BF
Modifying SCSI File System Resources
This section discusses how to modify SCSI file system resources.
About Modifying The LPAN Administrator modifies SCSI disk resource.

SCSI File System
Resources Use the same procedure to modify SCSI disk resources as you did
to create them. See “Create SCSI Disk File System Resources” on
page 9-24.

make to SCSI disk resources:
• Create a new SCSI disk resource.
• Delete an existing SCSI disk resource.
• Add a specified mount point to the SCSI disk.
• Removed a specified mount point from the SCSI disk.
• Rename an existing SCSI disk resource.
Modifying SCSI ```To modify a SCSI file system resource configuration:

File System
Resources
Availability.
SCSI File System Resources area, click the SCSI File System
3. In the SCSI File System Resource SCSI File System
Resourcename page, click the Modify button.
4. In the Modify SCSI File System Resource dialog box, make
appropriate changes in any of the configurable fields.
PM5.2_BF 9-27
Modifying Mount ```To create any mount point(s) for this SCSI file system
Points for a SCSI resource:
File System
Resource
Availability.
Resourcename for which you want to create a mount point.
Resourcesname page, in the Mount Points area, click the
Create button.
4. In the Create Mount Point dialog box, enter appropriate
• Enter the full Path from the pServer’s root file system for
this SCSI file system resource’s mount point.
• Use the pull-down menu to select the disk Partition on the
SCSI Id to which the file system resource’s mount point
points.
• Enter an integer in the Mount Order field to specify the
order that PAN Manager uses to mount this file system
mount point relative to the other mount points configured
for this file system resource.
• Enter any Mount Options to specify as arguments to the
Linux mount command, such as -t ufs or -t nfs. (Do not
include mount here.)
• Select the desired Mode for the SCSI file system resource,
either read/write or read only, using the pull-down menu.
• Optionally select the check box next to Create mount point
if it does not already exist to allow PAN Manager to
automatically create the mount point, if it does not exist.
• Optionally select the check box next to Scan partition
before mounting to check, and optionally repair, the
partition before the partition is mounted.
If you select Scan partition before mounting, you can also
specify any options in the Scan options (optional) field,
9-28 PM5.2_BF
such as the partition’s file system type, to allow the scan to

run successfully.
dialog box.
```To delete any mount point(s) for this SCSI file system resource:
Availability.
Resourcename which is configured with any mount point(s)
that you want to delete.
Delete button.
4. In the Delete Mount Points dialog box, select the check box
next to the Path of any mount point that you want to delete.
dialog box.
```To modify any mount point(s) for this SCSI file system
resource:
Availability.
Resourcename which is configured with any mount point(s)
Modify button.
4. In the Modify Mount Points dialog box, make appropriate
changes in any of the configurable fields.
dialog box.
PM5.2_BF 9-29
Configuring Network File System Resources
About Network Network file system (NFS) resources provide LPAN administrators
File System with the ability to mount a network shared directory to allow
Resources services access to storage not made available within the LPAN.
LPAN administrators configure NFS resources for a service by
specifying the following attributes:
• Host name and IP address
• Mount points
• Mount point options
• Host file system name
• Access mode

for This Task
Create Network ```To create a network file system resource:

File System
Resources
Availability.
Network File System Resources area, click the Create button.
3. In the Create Network File System Resource dialog box, enter
• Enter a Name for the network file system resource.
• Optionally enter a Description for the network file system
resource.
• Enter a Host to mount for this network file system resource.
(This must be a valid hostname or address on your network.)
9-30 PM5.2_BF
• Enter the Host Path of the host’s shared directory for this
network file system resource. (This must be a valid path on
the host’s system.)
• Select an appropriate Access Mode that PAN Manager will
have on the host’s shared directory, either read/write or
read only, using the pull-down menu.
• Enter a valid Mount point on a pServer where it will mount
the shared directory of the host using this network file
system resource.
• Enter valid Mount options to specify as arguments to the
Linux mount command when the pServer attempts to
mount the shared directory of the host using this network
file system resource.
• Optionally select the check box next to Create mount point
if it does not exist to allow PAN Manager to automatically
create the mount point, if it does not exist.
dialog box.
After you create a network file system resource, a Network File
System Resourcename icon appears in the Network File
System Resource area.
```To delete a network file system resource:

Availability.
Network File System Resources area, click the Delete button.
3. In the Delete Network File System Resources dialog box,
select the check box next to the network file system resource
Name that you want to delete.
4. Click Delete or click Cancel to close the dialog box.
PM5.2_BF 9-31
After you delete a network file system resource, its Network

File System Resourcename icon no longer appears in the
Network File System Resources area.
To learn how to assign network file system resources to an

PAN Manager Control”. You cannot assign network file system
resources to a load balancer.
9-32 PM5.2_BF
Modifying Network File System Resources
This section discusses how to modify network file system

resources, and includes the following topics:
• About Modifying Network File System Resources
• Modifying Network File System Resources with the CLI
• Modifying Network File System Resources with the GUI
About Modifying The LPAN Administrator modifies network file system resources.
Network File
System Use the same procedure to modify network file system resources as
Resources you did to create them. See “Create Network File System

make to network file system resources:
• Create a new network file system resource.
• Delete an existing network file system resource.
• Change the resource’s access mode (read/write or read-only) to
the specified mount point.
• Specify a valid host file system name for the shared disk or
directory.
• Rename an existing network file system resource.
Modifying ```To modify a network file system resource configuration:

Network File
System
Availability.
Resources
Network File System Resources area, click the Network File
System Resourcename that you want to modify.
PM5.2_BF 9-33
3. In the Network File System Resource Network File System

Resourcename page, click the Modify button.
4. In the Modify Network File System Resource dialog box,
make appropriate changes in any of the configurable fields.
dialog box.
Configuring Failover Policy Resources
About Failover Use a failover policy to ensure high availability of critical

Policy applications. Before configuring failover policy resources for an
Resources application or load balancer, review the following topics:
• General conditions that apply to all failover policies
• Attributes to specify when configuring failover policy resources
General Conditions That Apply to All Failover Policies
The following general conditions apply to all failover policies:

• You can define multiple failover policies in the same LPAN.
• Any application in the LPAN can use the failover policy, and
several different applications can use the same failover policy.
• If multiple applications share the same file system resource,
each of these applications must use the same failover policy.
Applications that have a common file system must always be
moved together, in the case of failover. This is true for read-
write file systems. It is not necessary to move read-only file
systems together. If multiple file system resources use the same
device, the applications must move together on a failover.
• Each dependent resource must be made available in exactly the
same manner as the primary pServer. For example, if the
application configures an IP address on vSwitch_1 connected to
the primary pServer, the failover pServer must also be
9-34 PM5.2_BF
connected to vSwitch_1. IP addresses may be mapped to

different vEths on the primary and failover pServers. The same
is true for disks. A disk mapped to the primary pServer must also
be mapped to the failover pServer (only if the disk is not
configured as part of the SCSI file system resource).
• The LPAN Administrator is responsible for assuring that any
other resource required by the application, but not under the
control of PAN Manager, is also available on each failover
pServer.
• Application failover and hardware failover happen
simultaneously. When a pServer fails, the application failover
policy initiates, moving the application to a failover pServer. In
the process of this move, the disk and IP resources used by the
application are disabled and unmapped from the failed pServer.
The failed pServer attempts to reboot, and if it cannot reboot on
the original pBlade, it reboots on the specified failover pBlade.
When PAN Manager detects that the failed pServer has rebooted
successfully, the application fails back to its original pServer (if
configured to fail back, which is the default). The failback
process remaps the disk and IP resources.
• If a failed pServer does not cleanly unmount file system
resources, the application cannot move back to that pServer until
it reboots. PAN Manager provides a CLI command option (fop
-X yes) and an equivalent GUI operation to reboot the pServer
if the application fails over.
• High availability (failover) is not the same as fault tolerance.
Clients that are connected to an application service that fails will
be required to reconnect to the restarted service. Time to
reconnect will be minimal.
• The following selection policies are available:
Round-robin — Cycles through the failover pServer list, each
time starting at the current point.
Ordered list — Cycles through the failover pServer list, each
time starting at the beginning of the list. You may order the
failover pServers; pServers with order numbers are selected
first, in order, starting at number 1. If two pServers have the
same order number, one is randomly selected.
PM5.2_BF 9-35
The default selection policy is ordered list.
Note: Although use of PAN Manager’s failover control is optional,

it is important to create a failover policy of some type for mission-
critical applications.
Attributes to Specify When Configuring Failover Policy

Resources
Administrators configure failover policy resources for a failover

policy by specifying the following attributes:
• Failover policy name
• Names of the pServers to be added to the list of available
pServers
• Option to return processing of the service over to the primary
pServer
• Description of the failover policy
• Order of pServer selection when the primary pServer fails
• pServer selection policy
• Option to reboot the pServer in the event that the service fails

for This Task
Create Failover ```To create a failover policy resource:

Policy
Resources with Note: A failover policy resource cannot be configured to
the GUI use a monitor pServer that runs the Microsoft Windows
operating system.
Availability.
Failover Policy Resources area, click the Create button.
9-36 PM5.2_BF
3. In the Create Failover Policy Resource dialog box, enter

• Enter a Name for the failover policy resource.
• Optionally enter a Description for the failover policy
resource.
• Select a Selection Policy for this failover policy resource
• Select the check box next to Reboot pServer to reboot a
monitored application’s current pServer before attempting
to move the application to another pServer as defined in the
failover policy resource.
• Select the check box next to Auto Failback to allow
processing to fail back to the primary pServer when it
becomes available.
• In the pServer Configuration area, you can add any
pServer in the LPAN to this failover policy resource. Select
the check box next to the pServer’s Name and optionally
enter an Ordering used in ordered failover policy resource.
Note: No pServer in this failover policy resource list of

pServers can be running a Microsoft Windows operating
system.
dialog box.
After you create a failover policy resource, a Failover Policy
Resourcename icon appears in the Failover Policy Resources
area.
```To delete a failover policy resource:

Availability.
Failover Policy Resources area, click the Delete button.
PM5.2_BF 9-37
3. In the Delete Failover Policy Resources dialog box, select the

check box next to the network resource Name that you want to
delete.
After you delete a failover policy resource, its Failover Policy
Resourcename icon no longer appears in the Failover Policy
Resources area.
To learn how to assign failover policy resources to an application,

Control”. To learn how to assign failover policy resources to a load
balancer, see Chapter 11, “Configuring Load Balancers”.
Modifying Failover Policy Resources
This section discusses how to modify failover policy resources.
About Modifying The LPAN Administrator modifies failover policy resource

Failover Policy configurations. If any application references a failover policy
Resources resource configuration that you want to modify or remove, you
must first remove the policy from every application that references
that policy. Only after removing the policy from every application
that references the policy can you remove or modify the policy.
Use the same procedure to modify failover policy resource

configurations as you did to create them. See “Create Failover
Policy Resources with the GUI” on page 9-36.

make:
• Modify the selection policy (round robin or ordered) for the
failover policy resource configuration.
9-38 PM5.2_BF
• Add a pServer to the list of pServers associated with the failover

policy resource configuration.
• Remove a pServer from the list of pServers associated with the
failover policy resource configuration.
• Change the text description for the failover policy resource
configuration.
• Rename the failover policy resource configuration.
Modifying ```To modify a failover policy resource configuration:

Failover Policy
Resources
Availability.
Failover Policy Resources area, click the Failover Policy
3. In the Failover Policy Failover Policy Resourcename page,
4. In the Modify Failover Policy dialog box, make appropriate
Modifying ```To modify the pServer(s) members of this failover policy

pServer resource:
Members of a
Failover Policy Note: For each pServer that you select, be sure its
Resource operating system supports the application service, and that the
PAN agent is present on the pServer.
Availability.
2. In the Failover Policy Resources area, click the Failover
Policy Resourcename with pServer member(s) you want to
modify.
3. In the Failover Policy Failover Policy Resourcename page, in
the pServer Members area, click the Modify button.
PM5.2_BF 9-39
4. In the Modify pServer Members dialog box, make appropriate

changes in any of the Name and Ordering fields.
5. Click Submit or click Cancel to close the dialog box.
9-40 PM5.2_BF
Configuring User-Defined Monitor Resources
About User- User-defined monitor resources are a collection of attributes (for

Defined Monitor example, event name, schedule interval, and so forth) that allows
Resources users to create a set of health, status, or statistical monitors whose
events could be used to enhance control over PAN Manager
behavior. Administrators configure user defined monitor resources
for a specific user defined monitor by specifying the following
attributes:
• User defined monitor name
• Names of the health, status, or statistical events to be added to
the list of events associated with this user defined monitor
• Compare type value
• Time to delay the start of the user defined monitor
• Path to the executable script
• Frequency with which the user defined monitor runs
• Description of the user defined monitor
• Event severity
To learn how to assign user-defined monitor resources to an

PAN Manager Control”. To learn how to assign user-defined
monitor resources to a load balancer, see Chapter 11, “Configuring
Load Balancers”.

for This Task
PM5.2_BF 9-41
Two Steps to There are two steps for configuring user-defined monitor resources:
Configure User
1. Create the user-defined monitor resource and specify the
Defined Monitor
monitor-related attributes that the application or load balancer
Resources
needs.
2. Configure the event trigger rules for this user-defined monitor.
Create User- ```To create a user-defined monitor:

Defined Monitor
1. In the left pane, click the LPANname in which you want to
Resources with
create a user-defined monitor.
the GUI
2. In the right pane, in the LPAN LPANname page, click the
Monitor tab at the top of the page.
3. At the top of the Monitor page, click the Create button.
4. In the Create Monitor dialog box, enter appropriate
• Enter a Name for the user-defined monitor.
• Optionally enter a Description for the user-defined
monitor.
• In the Executable area, enter the command that this user-
defined monitor runs (for example, an executable script that
runs the application that monitors your service(s)).
• In the Data Unit area, enter a descriptive label for the data
that this user-defined monitor generates. This label appears
on this monitor’s charts and graphs.
• In the Frequency (sec.) area, enter an integer with a
minimum value of ten to set the frequency that this monitor
checks the status of you service(s).
• To avoid false failures when the application starts up,
specify a delay (in seconds) for activating its health monitor.
To do this, specify an integer in the Start Up Delay (sec.)
field.
5. Click Submit to save your work.
The monitor appears at the top of the Monitors page.
9-42 PM5.2_BF
```To delete a user-defined monitor:

1. In the left pane, click the LPANname in which you want to
delete one or more user-defined monitors.
3. At the top of the Monitor page, click the Delete button.
4. In the Delete monitor dialog box, select the check box next to
the user-defined monitor Name that you want to delete.
The monitor no longer appears on the Monitors page.
Configure Event ```To configure the event trigger rules for this user-defined
Trigger Rules for monitor:
the User Defined
After a user-defined monitor is created, you can modify it or set
Monitor
its event trigger rules.
1. In the left pane, click the LPANname for which you want to
configure event trigger rules for a user-defined monitor.
3. At the top of the Monitor page, click the monitor you want to
create rules for.
4. On the User Monitor monitor page, in the Rules area, click
Create. To create the event trigger rules for this monitor, do the
following:
• Enter a Name for the event that this monitor will generate.
• From the Operator pull-down list, select a compare
statement type rule that PAN Manager uses to compare data
against the rule trigger Value.
• Enter a Value for the rule trigger that PAN Manager uses for
the Event this monitor will generate.
• From the Severity pull-down list, define the seriousness of
the event that this monitor will generate.
PM5.2_BF 9-43

dialog box.
Configure ```To assign or unassign a services for a user-defined application:

Service
After a user-defined monitor is created, you can modify it or set
Assignments for
its event trigger rules.
User Defined
Monitors 1. In the left pane, click the LPANname for which you want to
configure event trigger rules for a user-defined monitor.
create assignments for.
4. On the User Monitor monitor page, in the Service
Assignments area, click Assign/Unassign. Select (or clear) the
check box next to the Service name of the application to which
you want to assign (or from which you want to unassign) this
user-defined monitor.
dialog box.
9-44 PM5.2_BF
Modifying User-Defined Monitor Resource

Configurations
This section discusses how to modify user-defined monitor

resource configurations.
About Modifying The LPAN Administrator modifies user defined monitor resource
User-Defined configurations.
Monitor
Resource Use the same procedure to modify user defined monitor resource
Configurations configurations as you did to create them. See “Create User-Defined
Monitor Resources with the GUI” on page 9-42.

make to existing user defined monitor resource configurations:
• Delete a user defined monitor resource configuration.
• Rename a user defined monitor resource configuration.
• Specify the health, status, or statistical event to be added to a
user defined monitor resource configuration.
• Modify the description of the user defined monitor resource
configuration.
Modifying User- ```To modify a user-defined monitor configuration:

Defined Monitor
1. In the left pane, click the LPANname in which you have a user-
Resource
defined monitor you want to modify.
Configurations
edit.
4. On the User Monitor monitor page, click Modify.
PM5.2_BF 9-45
5. In the Edit monitor dialog, make appropriate changes in any of

the configurable fields.
dialog box.
Configuring Health Monitor Resource

Configurations
About Health Health monitors monitor applications to determine whether the

Monitor application is operational. Detected application failures initiate a
Resource response, such as an attempted restart or failover. Health monitors
Configurations are application-specific; each application type requires its own
health monitor. Thus, you can use the same health monitor for
several applications of the same type.
Before creating a health monitor resource configuration for an

application or load balancer, review the following topics:
• Understanding the Service Monitoring Daemon
• Understanding the Scripts Supplied with MON
• Understanding Custom Monitor Scripts
• Integrating Custom Monitor Scripts
• Understanding Database Monitors
• Understanding Alerts
• Escalating Failure Policy
Understanding the Service Monitoring Daemon
PAN Manager uses the functionality of the service monitoring

daemon, MON, to provide health monitoring for applications
running on pServers.
9-46 PM5.2_BF
Note: Do not confuse MON with the PAN Manager mon command.
MON is an open-source service monitoring daemon, whereas the
mon command configures statistical monitors within a PAN. For
more information on monitoring a PAN, see “Understanding
Platform Monitoring” on page 13-2.
MON is a general-purpose resource-monitoring system used in the

PAN to monitor application availability. MON can be run on a
pServer within an LPAN and can be configured to monitor the
operational status of specified applications running on any pServer
within that LPAN. The monitoring task can be specified to take
place at chosen time intervals, and, when an application is
determined to be nonoperational, predefined actions can be taken to
recover the application. If an application fails and is restarted or
failed over, users may see a brief interruption of service, or may
have to log back into the application, but the time of interruption of
service should be minimized.
The following figure illustrates a simple MON server configured in

a PAN environment.
PM5.2_BF 9-47
Figure 9.1 Simple MON configuration
ana emen
User
C ns l
LPAN
Application
pServer
Application
pServer
MON
pServer
External
Network
Application
pServer
MON is only used in the PAN to provide application monitoring

and failover. PAN Manager directly handlers server hardware
availability and failover.
When MON first starts, it randomly delays execution of all monitor

scripts between 0 and 60 seconds, in addition to the delay specified
when you configure the monitor. This delayed start evenly
distributes the MON workload. If an application starts and dies
before its monitor script starts, MON assumes that the application
failed to start. PAN Manager fails over the application according to
its failover policy.
9-48 PM5.2_BF
The PAN supports a default monitor script, which is supplied with

PAN Manager. This is a sample implementation; you may modify
the script to fit your environment. The script is located in the /opt/
panmgr/examples/mon directory on the cBlade.
PAN Manager supports health monitors for the following

applications:
• Apache HTTP Server
• BEA WebLogic Server
• IBM WebSphere Application Server
• Any JDBC compliant database (however, the monitor has been
specifically tested with Oracle and Sybase)
• Zeus Web server
Understanding the Scripts Supplied with MON
MON is distributed with the following default health monitor

scripts. These scripts reside in /usr/lib/mon/mon.d or /opt/
egenera/mon on the pServer.
asyncreboot.monitor
cpqhealth.monitor
dialin.monitor
dns.monitor
foundry-chassis.monitor
fping.monitor
freespace.monitor
ftp.monitor
hpnp.monitor
http.monitor
http_t.monitor
http_tp.monitor
imap.monitor
ldap.monitor
msql-mysql.monitor
na_quota.monitor
netappfree.monitor
nntp.monitor
phttp.monitor
ping.monitor
pop3.monitor
PM5.2_BF 9-49
process.monitor
rd.monitor
reboot.monitor
rpc.monitor
seq.monitor
silkworm.monitor
smtp.monitor
tcp.monitor
telnet.monitor
up_rtt.monitor
For more information on these, see www.kernel.org/software/

mon.
The following table lists the monitor scripts used to build the
application health monitors supported by this release of
PAN Manager.
Table 9.1 Monitor Scripts.
Application Monitor Script
Apache http.monitor
WebLogic http.monitor
WebSphere http.monitor
Zeus http.monitor
Database dbmon
Understanding Custom Monitor Scripts
You can write custom monitor scripts to monitor your application,

but you must use them with the supplied alert script. You can write
custom monitor scripts in any language, as long as the script
follows these criteria
• Scripts must execute through the command line.
• Scripts must appropriately parse command-line options passed
to the monitor script by MON.
9-50 PM5.2_BF
• Scripts must return an integer value indicating the instantaneous

health of the application being monitored.
• Monitor scripts must produce a list of IP addresses at which an
application exists. When MON invokes the application monitor,
this list is passed as a command-line argument. The application
monitor then uses the list to ping each application instance.
Specifically, the monitor script must do the following:
a. The monitor script must parse a list of IP addresses passed
on the command line. (Other command line arguments must
precede the IP list and use flags to distinguish the
arguments.) For example:
http.monitor -p 8080 192.168.0.1 192.168.0.2
The hmon command section later in this chapter provides a
more detailed example.
b. The script must test each IP address.
c. The script must return 0 if testing all hosts is successful and
return 1 if any host fails.
d. The script must produce textual output containing all
addresses that failed. These addresses must be on the first
line of the output.
For more details on writing monitor scripts, including examples,

see www.kernel.org/software/mon.
Integrating Custom Monitor Scripts
You can integrate a custom monitor script into the PAN as follows:
1. Create the monitor script.
2. Copy the monitor script to the appropriate location on the MON
server. This is normally in /usr/lib/mon/mon.d or /opt/
egenera/mon on the pServer.
3. Define an application health monitor that uses the new monitor

script. Use the PAN Manager hmon command to specify the
monitor script used by the application health monitor.
PM5.2_BF 9-51
4. Indicate the application health monitor used to monitor the

application. Use the PAN Manager app command to specify the
health monitor name and application being monitored.
Understanding Database Monitors
The PAN software includes the dbmon database monitor, which you
can use to monitor database applications with the hmon -M
command.
Note: The database monitor, dbmon, tests the health of a database

application by attempting to make a connection to the database. If it
fails to make a connection for any reason, it assumes a database
failure occurred. However, the failure to make a connection can be
for a number of reasons, including lack of available licenses. If you
choose to use dbmon, you must make sure that it can connect to the
monitored database for it to operate correctly.
For each monitored database, you must provide the following

arguments:
• All required jar/class files for the database driver and its
dependencies.
These files must be accessible from the hmon server.
• The value of a class path that includes all jar/class files for the
database driver and its dependencies.
This class path must be absolute and cannot contain relative
class paths containing a dot "." or dots "..".
• The full name of the database driver class to be used to monitor
the database.
The following examples of driver names have been tested:
oracle.jdbc.driver.OracleDriver
and
com.sybase.jdbc2.jdbc.SybDriver
• The database-specific URL at which you want to monitor the

database.
9-52 PM5.2_BF
• The IP address of the host where the database is located.

The following examples of URLs have been tested:
jdbc:oracle:thin:@192.168.10.2:1521:egen0
and
jdbc:sybase:Tds:172.29.22.5:4100
• The user name and password required to connect to the

database.
These are optional and may not be required, depending on the
specific database being monitored.
• An optional login timeout.
Use the following syntax to configure a database monitor:
hmon -M "dbmon -dbclasspath classpath

-d driver_name -l url -u user_name -p password
-t time_out" lpan_name/monitor_name
dbmon
Specifies the database monitor.
-dbclasspath classpath
Specifies the class path of any database-specific jar/class files. This

is appended to a class path containing jar files specific to the
platform. The resulting class path allows the monitor to connect to
the database and communicate any failures back to PAN Manager.
driver_name
Specifies the full package and class name of the database driver
used to connect to the database. Additionally, the implementation
of the class must reside in the class path specified with
-dbclasspath classpath.
PM5.2_BF 9-53
url
Specifies the vendor-specific URL used to connect to the database.
user_name
Specifies the user name required to connect to the database, if

required.
password
Specifies the password required to connect to the database, if

required.
timeout
Specifies the time out value is in seconds. If a connection is not

obtained within this timeout, the monitor reports a failure. The
default value is 15 seconds.
lpan_name
Specifies the name of the LPAN that contains this health monitor.
The name must conform to the PAN Manager naming conventions.
Names are limited to the following characters: upper or lower case
letters, numbers, dollar sign ($), period (.), dash (-), and underscore
(_). The name is required and must be unique.The maximum name
length is 32 characters. To ensure that CLI output displays line up,
specify names with a maximum length of 12 characters.
monitor_name
Specifies the name given to this configuration of a health monitor.

The name must conform to the PAN Manager naming conventions.
Names are limited to the following characters: upper or lower case
letters, numbers, dollar sign ($), period (.), dash (-), and underscore
(_). The name is required and must be unique.The maximum name
9-54 PM5.2_BF
The following is an example of the hmon -M command:
hmon -M "dbmon -dbclasspath /home/dbadmin/classes12.zip -d

oracle.jdbc.driver.OracleDriver
-l jdbc:oracle:Tds:172.29.22.5:4100 -u scott -p tiger
-t 5" foo/myOracleMon
Note: The entire argument of the -M option is enclosed in quotation

marks.
Understanding Alerts
This release of the PAN software does not support custom alert
scripts, even though MON is distributed with a number of default
alerts. If you develop your own monitor script, you must associate
any event actions with the alert script that is supplied with your
system.
The alert script supports the actions defined by the escalating

failure policy, and you must configure your health monitors to
associate events with the actions defined in this policy.
Escalating Failure Policy
The escalating failure policy defines the response of the system

following an application failure. In an LPAN, this failure policy is
configured using the hmon command.
PAN Manager configures MON to use the same alert script for all
application failures. This alert script collects details about the
application failure, and passes a message from MON to
PAN Manager. The system software reacts to the failure
notification by taking action according to the escalating failure
policy that has been defined for that application.
A failure policy takes the following form:

1. Restart after x failures.
2. Fail over after y failures.
3. Give up after z failures.
PM5.2_BF 9-55
If a monitored application is determined to be nonoperational, the

system software responds as follows:
1. After x consecutive failure notifications, the system attempts to
restart the application in its present location (that is, on the
current pServe)r. If this is successful, the failure counter is reset.
2. After x+y consecutive failure notifications, the system attempts
to fail the application over to another pServer. If this is
successful, the failure counter is reset.
3. After x+y+z consecutive failure notifications, the system gives
up.
Consequently, if a program crashes frequently, but is successfully

restarted within x failure notifications, it never fails over to another
pServer.
However, if after x failure notifications, the system was unable to

restart the application, it waits for y more failure notifications
before failing over the program to a standby pServer. If this failover
is successful, the failure counter is reset. The next time there are x
failure notifications, the system attempts to restart the application
before failing over a second time.
Note: It is important that you configure a value to the Giveup

option. If you do not, the escalation policy halts; PAN Manager no
longer responds to MON events. The state of the application is
assumed to be "started," but is not verified by PAN Manager. The
application may require human intervention to verify its state.
The following guidelines apply when using health monitors:

• You specify the pServer on which to run a health monitor. This
pServer becomes the MON server.
• You must define the health monitors to be used. Each health
monitor can monitor multiple instances of an application on
multiple pServers. A health monitor is associated with one or
more pServers.
9-56 PM5.2_BF
• Each application instance being monitored must have a health

monitor designated to it. Otherwise, the application is not
monitored.
• Any pServer can be assigned to a health monitor.
• Within an LPAN, any monitor host pServer must have network
connectivity to all pServers that it monitors.
• PAN Manager starts and stops MON. Therefore, you should
never start MON manually on a designated MON server.
To learn how to assign health monitor resources to an application,

Control”. To learn how to assign health monitor resources to a load
balancer, see Chapter 11, “Configuring Load Balancers”.

for This Task
Create Health ```To create a health monitor resource:

Monitor
Resource Note: You cannot configure a health monitor resource to
Configurations use a monitor pServer that runs the Microsoft Windows
with the GUI operating system.
Availability.
Health Monitor Resources area, click the Create button.
3. In the Create Health Monitor Resource dialog box, enter
• Enter a Name for the health monitor resource.
• Optionally enter a Description for the health monitor
resource.
• Enter the full path to the Script that initiates this health
monitor resource’s monitoring application running on its
pServer.
PM5.2_BF 9-57
• Use the Application Monitoring Escalation Policies area

to configure the PAN Manager health monitor resource
escalation policy, based on multiple health monitors. Use
the appropriate pull-down menus to specify the following:
– Restart if... Select all started to prompt PAN Manager
to a restart monitored applications only when all started
monitors reach their Restart policy trigger; select any
started to prompt PAN Manager to restart a monitored
application only when any started monitor reaches its
their Restart policy trigger.
– Failover if... Select all started to prompt PAN Manager
to move monitored applications to failover-configured
pServers only when all started monitors reach their
Failover policy trigger; select any started to prompt
PAN Manager to move monitored applications to
failover-configured pServers when any started monitor
reaches its Failover policy trigger.
– Give up if... Select all started to prompt PAN Manager
to shut down monitored applications only when all
started monitors reach their Give up policy trigger;
select any started to prompt PAN Manager to shut
down monitored applications when any started monitor
reaches its Give up policy trigger.
• Use the Monitor pServer area to configure the pServer, any
optional delay configurations, and this application
monitor’s escalation policy. Enter appropriate information
in the following fields:
Note: This monitor pServer cannot be running a

Microsoft Windows operating system.
– Use the pull-down menu to select a pServer on which
you have installed the health monitor resource’s
monitoring application. Select None to configure these
settings later.
9-58 PM5.2_BF
– To avoid false failures when the application starts up,

specify a delay for activating its health monitor. To do
this, specify an integer in the Start Up Delay field and
use the pull-down menu to select whether the interval is
expressed in seconds, minutes, or hours.
– To set the frequency for checking the application’s
status, specify an integer in the Poll Interval field and
use the pull-down menu to select whether the interval is
expressed in seconds, minutes, or hours.
– In the Thresholds (in order of occurrence) area,
configure this application monitor’s escalation policy
by entering an integer in each field appropriately:
Indicate restart after The number of consecutive
failures that PAN Manager receives before it
attempts to restart the application.
Indicate failover after The number of consecutive
attempts to move the monitored application to its
failover-configured pServers. If no failover pServer
is configured, the monitor skips directly to the
giveup after policy.
Indicate giveup after The number of consecutive
attempts to shut down the monitored application.
Note: It is important to specify a value for its giveup after

policy; without it, PAN Manager attempts to restart or fail over
the application indefinitely.
dialog box.
After you create a health monitor resource, its Health Monitor
Resourcename icon appears in the Health Monitor Resources
area.
PM5.2_BF 9-59
```To delete a health monitor resource:

Availability.
Health Monitor Resources area, click the Delete button.
3. In the Delete Health Monitor Resources dialog box, select the
check box next to the health monitor resource Name that you
want to delete.
After you delete a health monitor resource, its Health Monitor
Resourcename icon no longer appears in the Health Monitor
Resources area.
Modifying Health Monitor Resource Configurations
This section discusses how to modify health monitor resource

configurations, and includes the following topics:
• About Modifying Health Monitor Resource Configurations
• Modifying Health Monitor Resource Configurations
• Adding a Monitor pServer to a Health Monitor Resource
Configuration
About Modifying The LPAN Administrator modifies health monitor resource

Health Monitor configurations. You can modify a health monitor resource
Resource configuration at any time.
Configurations
Use the same procedure to modify health monitor resource
configurations as you did to create them. See “Create Health
Monitor Resource Configurations with the GUI” on page 9-57.
9-60 PM5.2_BF
You can modify health monitor resource configurations in the

following ways:
• Modify the selection policy (round-robin or ordered) for the
health monitor resource configuration.
• Add a pServer to the list of pServers associated with the health
monitor resource configuration.
• Remove a pServer from the list of pServers associated with the
health monitor resource configuration.
• Change the text description for the health monitor resource
configuration.
• Change the time period (in seconds, minutes, or hours) to delay
the start of the health monitor resource configuration.
• Rename the health monitor resource configuration.
Modifying Health ```To modify a health monitor resource configuration:

Monitor
Resource
Availability.
Configurations
Health Monitor Resources area, click the Health Monitor
3. In the Health Monitor Health Monitor Resourcename page,
4. In the Modify Health Monitor dialog box, make appropriate
PM5.2_BF 9-61
Adding a Monitor ```To add a monitor pServer to a configured health monitor

pServer to a resource configuration:
Health Monitor
Resource Note: Be sure that the operating system of each monitor
Configuration pServer supports the health monitor.
Availability.
Monitor pServers area, click the Create button.
3. Enter appropriate information in the following fields:
• Use the pull-down menu to select a pServer to which you
have assigned the health monitor resource’s monitoring
application. Select None to configure these settings later.
• To avoid false failures when the application starts, specify a
delay for activating its health monitor. To do this, specify an
integer in the Start Up Delay field and use the pull-down
menu to select whether the interval is expressed in seconds,
minutes, or hours.
• To set the frequency for checking the application’s status,
specify an integer in the Poll Interval field and use the pull-
down menu to select whether the interval is expressed in
seconds, minutes, or hours.
• In the Thresholds (in order of occurrence) area, configure
this application monitor’s Escalation Policy by entering an
integer in each field, as appropriate:
– Indicate restart after the number of consecutive
failures that PAN Manager receives before it attempts to
restart the application.
– Indicate failover after the number of consecutive
move the monitored application to its failover-
configured pServers. If no failover pServer is
configured, the monitor skips directly to the giveup
after policy.
9-62 PM5.2_BF
– Indicate giveup after the number of consecutive

shut down the monitored application.
Note: You must specify a value for its giveup after policy;
without it, PAN Manager attempts to restart or fail over the
application indefinitely.
dialog box.
Extracting Application Templates
About An application template is an object that encapsulates all of the

Application components and values associated with a specific template archive.
Templates Application templates exist as jar files (with .jar file extensions)
and reside in the /opt/panmgr/templates directory on the cBlade.
LPAN administrators do not need to configure application

templates. Instead, LPAN administrators extract an application
template by specifying its name. After extracting an application
template, it becomes available to the pServers that reside in the
specified LPAN.

for This Task
Extract ```To extract an application template:

Application
Templates with
Availability.
the GUI
upper most area, click the Templates button.
PM5.2_BF 9-63
3. In the Extract Template dialog box, select the radio button next
to the Name of an available template that you want to extract.
4. Click Submit to extract the template, or click Cancel to close
the dialog box.
When an application template is extracted, new resources
configured with the template are created and displayed in the
appropriate resource area.
```To display available application templates you can allocate for

use in one or more LPANs:
1. In the left pane, select the PAN_name.
2. On the PAN pan_name page, click the Templates button.
3. The PAN Templates dialog box lists the application templates
available for this PAN.
9-64 PM5.2_BF
Chapter 10
Configuring Applications
for PAN Manager Control
Note: Application failover is not supported on pServers running the

Windows operating system.
This chapter describes using PAN Manager to control application

start, stop, and failover operations. This use of PAN Manager is
optional. After the pServers exist on the network just as
conventional servers do, you can manage applications manually by
logging directly onto a pServer, or you can install application
software and use third-party tools to manage the applications.
However, since the PAN architecture makes failover much easier to
configure than for conventional servers, it is advantageous to use
PAN Manager for application control. This chapter includes the
following sections:
• Understanding Application Control
• Installing Application Software
• Managing Stand-alone Applications
• Modifying Application Control Configurations
PM5.2_BF 10-1
Understanding Application Control
About PAN Manager can control applications in the following ways:

Application
• Start, stop, and move an application.
Control
• Fail over an application.
• Provide storage and network connectivity.
• Load balance an application.
You can configure applications under PAN Manager control to

automatically start when a pServer boots, or to be started manually.
All applications that are specified to automatically start after the
pServer boots are started serially in the order specified.
A failover group consists of a pServer running the application

(referred to as a primary pServer) and a set of pServers that can take
over running the application in the event of a pServer failure.
A load balancer consists of a set of pServers running the same or

cooperating instances of an application. The application is listening
on a single IP address, and a separately defined pServer has the
responsibility to distribute the incoming requests for the application
to the individual instances.
To learn how to add an application to a load balancer, see

About With PAN Manager, you configure as stand-alone entities the

Resources resources that applications use. Resources are logical groupings of
unique types of configuration information. You select one or more
resource types and use them as building blocks to instruct
PAN Manager on how to control an application.
10-2 PM5.2_BF
Configuring Applications for PAN Manager Control
Before configuring an application for PAN Manager control, LPAN

Administrators must configure the following resource types:
• Failover policy resources
• User-defined monitor resources
• Health monitor resources
To learn how to configure these resources, see Chapter 9,

“Configuring Resources”.
Installing Application Software
About Installing After you configure and boot the pServers, you can install
Application application software just as you would on conventional servers.
Software Although this document does not describe in detail the steps for
installing specific application software, the steps in this section
outline how to install software on a pServer.
If you want to know the number of CPUs, speed, and RAM for each
pBlade, use the blade -l platformname/pblade_number
command to list this information. Install your application software
on the pServer best equipped to handle the application’s processing
requirements.
If you want to install software from a DVD-ROM, you must first

gain access to one of the DVD-ROM drives allocated to the LPAN.
Since the DVD-ROM drives are shared among pServers and across
LPANs, access can only be granted by the PAN Administrator.
PM5.2_BF 10-3
If you want to install software from a virtual CD-ROM, you must

first make the image available to the pServer’s VCD. See
“Managing Virtual CD-ROMs” on page 7-11.
Before installing an application on a disk, make sure to add the disk

to the specified pServer or specify the disk when configuring a
SCSI file system resource (using the fs command or the equivalent
GUI page). If you add the disk to the specified pServer, you can
mount the disk and then install an application (and the application’s
init script) on it.
If you specify the disk when configuring a SCSI file system

resource, you can configure the application for PAN Manager
control (but not assign executable resources to the application at
this point). When the application boots, PAN Manager mounts the
file system (and by extension the associated disk). You can then
install an application (and the application’s init script) on the disk.
You can then assign executable resources to the application by
shutting down the application.

for this Task
There are three ways to connect to a pServer over the network:
• AppGate MindTerm
• SSH
• PAN Manager console command
If you are using the PAN Manager console command to install

software onto a pServer, you must be a PAN Manager user with the
LPAN Administrator role.
If you are using MindTerm or SSH to access the pServer,

permissions are determined by standard policies and are outside the
scope of PAN Manager. You do not need to be a PAN Manager user
to access a pServer through MindTerm or SSH.
10-4 PM5.2_BF
This document illustrates the use of the PAN Manager console.

Refer to your AppGate MindTerm or SSH documentation if you use
those methods to connect to a pServer.
Three Steps to There are three major steps for installing application software on a
Install pServer:
Application
1. If installing from a DVD-ROM or virtual CD-ROM, enable
Software
pServer access to the media or image.
See “Registering Virtual CD-ROMs” on page 5-5 or “Accessing
DVD-ROM Drives” on page 5-5.
2. Open a connection to the pServer console.
3. Complete the installation as required by the application.
Open a ```To open a pServer console:

Connection to
1. In the left pane, click LPANs > LPANname > pServername.
the pServer
Console 2. In the right pane, in the pServer pserver_name page, in the
Controls area, click the Console button ( ).
The pServer consoleappears in a separate window. At the top of
the console window, the message Authenticating with server...
appears.
3. When the “Authenticating with server...Authenticated” message
appears, press Enter once to log on to the console.
Complete the ```To complete a software installation from the pServer console:
Installation
1. Mount the appropriate CD-ROM device (cdrom1 or cdrom2 or
VCD).
2. Follow the required software installation instructions.
3. Unmount the CD-ROM device.
You can close the pServer console by clicking the window
closed.
PM5.2_BF 10-5
4. (optional) Disable the pServer’s access to the DVD-ROM

device with the steps:
a. In the left pane, click LPANS > LPANname >
pServername.
b. In the right pane, in the pServer pServername page, in the
DVD-ROMs area, click the Enable/Disable button.
c. In the Enable/Disable DVD-ROM Access dialog box,
select the check box(es) next to the specific DVD-ROM
NAME which you want access disabled.
d. Click Submit.
Managing Stand-alone Applications
About Stand- Stand-alone applications are those applications that are under
alone PAN Manager control, but are not part of a load balancer. You
Applications might want to put an application under the control of PAN Manager
if you want to automatically start the application or automate
failover for the application.
To learn how to add an application to a load balancer, see

LPAN administrators configure applications for PAN Manager

control by specifying the following attributes:
• The name of the application
• The name of the LPAN in which the application runs
• The name of the primary pServer that runs the application
• A description for the application
• Add previously configured resources:
• Executable
10-6 PM5.2_BF
• Network
• Network file system
• SCSI disk
• Failover policy
• Health monitor
• The resource start order
• Add variable
• Whether the application should start when the pServer boots
To learn how to configure resources (executable, network, network

file system, SCSI disk, failover policy, and health monitor), see
Chapter 9, “Configuring Resources”.

for This Task
Steps to To configure an application for PAN Manager control, perform

Configure an these steps:
Application for
1. Create an application.
PAN Manager
Control 2. Assign the following resources to an application:
• Executable
• Network
• SCSI file system
• Network file system
• Failover policy
• Health monitor
• User defined monitor
3. Start, stop, or move an application.
PM5.2_BF 10-7

Create an ```To create an LPAN’s high-availability application:

Application
2. In the LPAN LPANname page, click the High Availability
button.
Applications area, click the Create button.
4. In the Create Application dialog box, enter the name of the
application, optionally select the check box next to Proceed
directly to Application page after creation, and then click
Submit to create the application.
```To modify an LPAN’s high-availability application name or

description:
Availability.
Applications area, click the Applicationname that you want to
modify.
3. In the Application Applicationname page, click the Edit
button.
4. In the Edit Application dialog box, you can Rename
Application and update the Description.
5. Click Submit to save your work, or Cancel to close the dialog
box.
10-8 PM5.2_BF
```To delete an LPAN’s high-availability application:

Availability.
Applications area, click the Delete button.
3. In the Delete Applications dialog box, select the check box next
to the Name of the application that you want to delete.
4. Click Delete to proceed with the operation or click Cancel to
close the dialog box.
Assign Note: To learn how to create executable resource configurations,

Executable see “Create Executable Resources” on page 9-14.
Resources
```To assign or unassign an executable resource to an
application:
Availability.
2. In the Executable Resources area, click the Executable
Resourcename you want to assign to (or unassign from) an
application.
3. In the Executable Resource Executable Resourcename page,
in the Service Assignments area, click the Assign/Unassign
button.
4. In the Assign/Unassign Resource dialog box, select (or clear)
the check box next to the Service name of the application to
which you want to assign (or from which you want to unassign)
this executable resource.
dialog box.
Assign Network Note: To learn how to configure network resources, see “Create
Resources Network Resources” on page 9-18.
PM5.2_BF 10-9
```To assign or unassign a network (IP) resource to a service:

Availability.
that you want to assign to (or unassign from) an application or
load balancer.
3. In the Network Resource Network Resourcename page, in the
Service Assignment area, click the Assign/Unassign button.
the check box next to the Service name of any application or
load balancer to which you want to assign (or from which you
want to unassign) this network resource.
dialog box.
Assign SCSI Note: To learn how to configure SCSI file system resources, see
Disk Resources “Create SCSI Disk File System Resources” on page 9-24.
```To assign or unassign a SCSI file system resource to a service:

Availability.
Resourcename that you want to assign to (or unassign from) an
application or load balancer.
Resourcename page, in the Service Assignment area, click the
Assign/Unassign button.
the check box next to the Service name of any application to
which you want to assign (or from which you want to unassign)
this SCSI file system resource.
10-10 PM5.2_BF

dialog box.
Assign Network Note: To learn how to configure network file system resources, see
File System “Create Network File System Resources” on page 9-30.
Resources
```To assign or unassign a network file system resource to a
service:
Availability.
Network File System Resource area, click the Network File
System Resourcename that you want to assign to (or unassign
from) an application or load balancer.
3. In the Network File System Resource Network File System
Resourcename page, in the Service Assignment area, click the
Assign/Unassign button.
the check box next to the Service Name of any application or
want to unassign) this network file system resource.
dialog box.
Assign Failover Note: To learn how to create failover policy resource

Policy configurations, see “Create Failover Policy Resources with the
Resources GUI” on page 9-36.
```To assign or unassign this failover policy resource to a service:

A high-availability service can only be configured to use one
failover policy at a time.
Availability.
PM5.2_BF 10-11

the Service Assignments area, click the Assign/Unassign
button.
want to unassign) this failover policy resource.
dialog box.
Assign Health Note: To learn how to create health monitor resource

Monitor configurations, see “Create Health Monitor Resource
Resources Configurations with the GUI” on page 9-57.
```To assign or unassign this health monitor resource to a service:

Availability.
button.
want to unassign) this health monitor resource.
5. If you are assigning this health monitor resource, use the pull-
down menu to select an available Network Resource for this
health monitor resource to monitor.
10-12 PM5.2_BF

dialog box.
Assign User Note: To learn how to create user-defined monitor resource

Defined Monitor configurations, see “Create User-Defined Monitor Resources with
Resources for an the GUI” on page 9-42.
Application
```To assign a user-defined monitor to an application:
Availability.
Applications area, click the Applicationname to which you
want to assign a user-defined monitor.
3. In the Application Applicationname page, click the Monitor
tab at the top of the page.
4. In the Monitor page, in the User Defined Monitors area, click
the Assign button.
5. In the Assign Monitor for H/A dialog box, select the radio
button next to the Name of the user-defined monitor that you
want to assign to this application.
dialog box.
The monitor appears in the User Defined Monitors area.
```To unassign a user-defined monitor from application:

Availability.
Applications area, click the Applicationname for which you
no longer want this user-defined monitor assigned.
3. In the Application Applicationname page, click the Monitor
tab at the top of the page.
the Unassign button.
PM5.2_BF 10-13
5. In the Unassign Monitor dialog box, select the check box next
to the Name of the user-defined monitor you no longer want
assigned to this application.
dialog box.
The monitor no longer appears in the User Defined Monitors
area.
```To define an action PAN Manager takes on an application

associated with the monitor in response to a rule:
Availability.
Applications area, click the Applicationname for which you
want to configure an action for its user-defined monitor.
3. Click the Monitor tab at the top of the page.
the Edit button.
5. In the Edit monitor dialog box, the Edit Rule Action table lists
the rules currently associated with this monitor. In the Action
column, select an action from the pull-down list, and then click
Update.
Start, Stop, or ```To control an LPAN’s high-availability application:

Move an
Application
Availability.
control.
3. On the bottom border of this Application Applicationname
page, in the Controls area, you can use the following control
buttons:
• Click to start this application.
10-14 PM5.2_BF
• Click to stop this application.

• Click to move this application to a booted pServer
specified in its failover policy configuration or back to its
primary pServer, if available.
• Click to run the application’s executable resource(s).
Note: If an action is currently prohibited on the application, the

button is shaded.
Modifying Application Control Configurations
This section discusses how to modify application control

configurations and includes the following topics:
• About Modifying Application Control Configurations
• Modifying Application Control Configurations with the CLI
• Modifying Advanced Settings for an Application with the CLI
• Modifying Resource Assignments for an Application with the
CLI
• Starting, Stopping, and Moving an Application with the CLI
• Modifying Advanced Settings for an Application with the GUI
• Modifying Resource Assignments for an Application with the
GUI
• Starting, Stopping, and Moving an Application with the GUI
About Modifying The LPAN Administrator modifies application control

Application configurations. Use the same procedure to modify application
Control control configurations as you did to create them.
Configurations
PM5.2_BF 10-15

make to existing application control configurations:
• Add a file system to an application control configuration.
• Rename an application control configuration.
• Change the autostart setting for an application control
configuration.
• Move an application control configuration.
• Force the application control configuration to stop.
Modifying ```To modify advanced settings for an LPAN’s high-availability

Advanced application:
Settings for an
Application
Availability.
2. In the High Availability for LPAN LPANname page click the
Advanced Configuration button.
3. In the Advanced Application Configuration dialog box, you
can select any of the following headings:
• Auto-start—The heading expands allowing you to select,
as appropriate, the check box next to application if
available pServer boots and click Submit.
• Environment Variables—The heading expands, allowing
you to modify any of the following fields:
– In the Add new variable area, enter the Name and
Value for an environmental variable that you want to
assign to this application, and click the Add button.
– In the Current environment variables area, for any
environment variable Name that you want to modify,
enter a new Value, and click the Modify button.
– In the Current environment variables area, select the
check box next to the Name of any variables that you
want to delete, and click the Delete button.
10-16 PM5.2_BF
• Load Balancer Membership—The heading expands,

allowing you to modify any of the following fields:
– Use the Assign to load balancer pull-down menu to
select a load balancer to which you want to add this
application. Select None to remove it from a load
balancer if it is already a member.
– Use the Use network resource pull-down menu to
select an existing network resource to which the load
balancer forwards connections.
– In the Membership weight field, enter a numeric
weight value for this member; highest number indicates
strongest weight.
– Select the check box, as appropriate, next to Start
member as load balancer starts.
4. To close the Advanced Application Configuration dialog box
without modifying any field, click the X in the upper corner of
the dialog box.
Modifying To learn how to create resource configurations (executable,

Resource network, network file system, and so forth), see Chapter 9,
Assignments for “Configuring Resources”.
an Application
```To manage resource assignments for an LPAN’s high-
availability application:
Availability.
Applications area, click the Applicationname whose resource
assignments you want to manage.
From the Application Applicationname page, you can manage
any resource assignment for this application from any of the
following areas in the page:
PM5.2_BF 10-17
• Primary pServer—Click the Assign/Unassign button. In

the Assign/Unassign pServer as Primary dialog box,
select the radio button next to the Name of the new primary
pServer.
Important: For the pServer you select, be sure that the
operating system supports the application service, and that the
PAN agent is present.
Click Assign to save your work, or click Cancel to close the
dialog box.
• Failover Policy—Click the Assign/Unassign button. In the
Assign/Unassign Failover Policy dialog box, select the
radio button next to the Name of the failover policy
assignment. Click Assign to save your work, or click
Cancel to close the dialog box.
• Executable Resources—Do any of the following:
– Click the Assign button. In the Add Executable
Resources dialog box, select the check box next to the
Name of an executable resource, select a check box
next to at least one command (Stop, Start or User-
defined) to Execute on, and optionally specify an
Order of the command execution. Click Assign to save
your work, or click Cancel to close the dialog box.
– Click the Modify button. In the Modify Executable
Resources dialog box, select the check box to choose a
new command (Stop, Start or User-defined) to
Execute on, and optionally enter an Order of the
command execution. Click Submit to save your work,
or click Cancel to close the dialog box.
– Click the Remove button. In the Remove Executable
Name of an executable resource to remove from this
application. Click Remove to continue, or click Cancel
to close the dialog box.
• SCSI File System Resources—Do any of the following:
10-18 PM5.2_BF
– Click the Assign button. In the Add SCSI File System

Name of the SCSI file system resource and optionally
specify an Order of the SCSI file system. Click Assign
to save your work, or click Cancel to close the dialog
box.
– Click the Set Order button and in the Order SCSI File
System Resources dialog box, enter a new Order for a
SCSI file system resource. Click Submit to save your
work, or click Cancel to close the dialog box.
– Click the Remove button and in the Remove SCSI File
System Resources dialog box, select the check box
next to the Name of the SCSI file system resource to
remove from this application. Click Remove to
continue, or click Cancel to close the dialog box.
• Network (IP) Resources—Do any of the following:
– Click the Assign button. In the Add Network
Name of the network resource to assign to this
application and optionally specify an Order for the
network resources. Click Assign to save your work, or
click Cancel to close the dialog box.
– Click the Set Order button. In the Order Network
Resources dialog box, enter a new Order for a network
resource. Click Submit to save your work, or click
– Click the Remove button. In the Remove Network
Name of the network resource to remove from this
application. Click Remove to continue, or click Cancel
• Health Monitors—Do any of the following:
– Click the Assign button. In the Add Health Monitor
Resource dialog box, select the check box next to the
Name of a health monitor resource, and use the pull-
down menu to select an available Network Resource
PM5.2_BF 10-19
for this health monitor resource to monitor. Click

Assign to save your work, or click Cancel to close the
dialog box.
– Click the Modify button. In the Modify Health
Monitor Assignments dialog box, use the pull-down
menu to select a different, existing Network resource.
Click Submit to save your work, or click Cancel to
– Click the Remove button. In the Remove Health
Monitor Resources dialog box, select the check box
next to the Name of the health monitor resource to
remove from the application. Click Remove to
• Network File System Resources—Do any of the
following:
– Click the Assign button. In the Add Network File
System Resources dialog box, select the check box
next to the Name of a network file system resource and
optionally specify an Order of the network file system.
Click Assign to save your work, or click Cancel to
– Click the Set Order button. In the Order Network File
System Resources dialog box, enter a new Order for
the network file system resources. Click Submit, or
3. Click the Remove button. In the Remove Network File System
Resources dialog box, select the check box next to the Name of
the network file system resource to remove from this
application. Click Remove to continue, or click Cancel to close
the dialog box.
Starting, ```To control an LPAN’s high-availability application:

Stopping, and
Moving an
Availability.
Application
10-20 PM5.2_BF

control.
3. On the bottom border of this Application Applicationname
page, in the Controls area, you can use the following control
buttons:
• Click to start this application.
• Click to stop this application.
• Click to move this application to a booted pServer
specified in its failover policy configuration or back to its
primary pServer, if available.
• Click to run the application’s executable resource(s).
Note: If an action is currently prohibited on the application, the

button is shaded.
PM5.2_BF 10-21
10-22 PM5.2_BF
Chapter 11
Configuring Load
Balancers
Note: Load-balancing is not supported on pServers running the

Windows operating system.
This chapter describes using PAN Manager to control load balancer

start, stop, and failover operations. This use of PAN Manager is
optional. A load-balancer consists of a set of pServers running the
same or cooperating instances of an application. The application is
listening on a single IP address and a separately defined pServer has
the responsibility to distribute the incoming requests for the
application to the individual instances.
This chapter includes the following sections:

• Understanding Load Balancer Control
• Configuring a Load Balancing Service
• Modifying Load Balancer Control Configurations
PM5.2_BF 11-1
Understanding Load Balancer Control
About Load You use a load balancer to distribute the network traffic load among
Balancer Control multiple instances of an application by means of a load-balancing
server and IP address. The load-balancing pServer accepts requests
for the service and distributes them to the members of the load
balancer. The Linux Virtual Server (LVS) provides load-balancing
support on the platform. LVS is incorporated into the Linux
operating system installed on the pServers. For more information
on LVS, see www.linuxvirtualserver.org.
The load-balancing pServer accepts the request and forwards it to

the member pServers, and must be a pServer within the same
LPAN, but cannot run the service being load balanced. The
following figure illustrates a load-balancing service.
Figure 11.1 Load-Balancing Service
MyLPAN
pServer
#2
Apache
#1
(Port 80)
pServer
Incoming #1
Requests Load
Balancer
pServer
#3
Apache
#2
(Port 80)
11-2 PM5.2_BF
Configuring Load Balancers
Note: If the load-balancing service or member servers use a failover

policy or a health monitor, create the policy and monitor before
starting the load balancer.
To learn how to create failover policy resource configurations, see

“Create Failover Policy Resources with the GUI” on page 9-36.
To learn how to create health monitor resource configurations, see

“Create Health Monitor Resource Configurations with the GUI” on
page 9-57.
About Load With PAN Manager, you configure as stand-alone entities the
Balancer resources that load balancers use. Resources are logical groupings
Resources of unique types of configuration information. You select one or
more resource types and use them as building blocks to instruct
PAN Manager on how to control a load balancer.
Before configuring a load balancer for PAN Manager control,

LPAN administrators must configure the following resource types:
• Failover policy resources (optional)
• User defined monitor resources (optional)
• Health monitor resources (optional)
You can specify a failover policy for the load-balancing service.

The default is no failover policy. It is good practice to have a
failover policy for any and all mission-critical applications and
services.
You can specify a health monitor for the load-balancing service.

The default is no health monitor. It is good practice to have a
monitor for the load-balancing service, especially if you are using a
failover policy.
To learn how to configure these resources, see Chapter 9,

“Configuring Resources”.
PM5.2_BF 11-3
About Load Before configuring a load balancer for PAN Manager control, it is
Balancer useful for LPAN administrators to become familar with the
Attributes following categories of load balancer-related attributes:
• Load balancer attributes
• Optional load balancer attributes
• Load balancer member attributes
• Optional load balancer member attributes
The following sections provide brief descriptions of the attributes

that make up these categories.
Load Balancer Attributes
Service protocol — PAN Manager supports two service protocols:

Transmission Control Protocol (TCP) and User Datagram Protocol
(UDP). The default is TCP.
Port number — The service uses this port number to receive

requests.
Scheduling policy — The application load is distributed using one

of the following scheduling policies:
round-robin — The load-balancing server cycles through the

list of member pServers and selects the next pServer in the list.
weighted round-robin — Weights are assigned to each pServer
in the list of member pServers. A scheduling sequence is
generated from this weighted list, and requests are directed to a
pServer based on the scheduling sequence. The value for
weighted is a number that slows the frequency with which the
load balancer directs incoming requests. A pServer with a
weight of 3 receives three times as many requests as a pServer
with a weight of 1.
least connected — The load-balancing server directs service
requests to the member pServer with the least established
service connections.
11-4 PM5.2_BF
weighted least connected — Different weights are associated

with the member pServers. A higher weight allows a pServer to
have more connections. Requests are routed to the pServer with
the least established service connections and the highest weight.
The value for weighted is a number that slows the frequency
with which the load balancer directs incoming requests. A
pServer with a weight of 3 receives three times as many requests
as a pServer with a weight of 1.
The default is round-robin.
Load-balancing service IP — The load-balancing service IP is the

IP resource configured with the IP address of the load-balancing
service.
pServer name — Specifies the pServer that runs the load-balancing

service. The name must conform to PAN Manager naming
conventions. Names are limited to the following characters: upper-
case or lower-case letters, numbers, dollar sign ($), period (.), dash
(-), and underscore (_). The name is required and must be
unique.The maximum name length is 32 characters. To ensure that
CLI output displays line up, specify names with a maximum length
of 12 characters.
LPAN name — Specifies the name of the LPAN that contains this
load-balancing service. The name must conform to PAN Manager
naming conventions. Names are limited to the following characters:
upper-case or lower-case letters, numbers, dollar sign ($), period
(.), dash (-), and underscore (_). The name is required and must be
of 12 characters.
Load-balancing service name — The load-balancing service is

given a name so that it can be referenced by other PAN Manager
commands. The load-balanced service name must conform to the
PAN Manager naming conventions – names are limited to the
following characters: upper or lower case letters, numbers, dollar
sign ($), and underscore (_). The name is required and must be
unique.
PM5.2_BF 11-5
Optional Load Balancer Attributes
PAN Manager allows you to define certain optional attributes of the

load-balancing service. If you choose not to define them,
PAN Manager uses the default values. You can set these attributes
during the service creation; they are shown in a separate command
for illustration purposes only. You can specify any or all of the
following attributes:
Description — The description is used for information purposes

only. The default is no description.
Failover policy — You can specify a failover policy for the load-
balancing service. The default is no failover policy. It is good
practice to have a failover policy for any and all mission-critical
applications and services.
Health monitor — You can specify a health monitor for the load-
balancing service. The default is no health monitor. It is good
practice to have a monitor for the load-balancing service, especially
if you are using a failover policy.
Automatically start — You can choose to have the load-balancing

service start automatically when the pServer boots. The default
requires a manual start of the load-balancing service.
If you choose to automatically start the load-balancing service, all

of the member applications should also be set to automatically start.
If the pServers boot in a specified order, the pServer running the
load-balancing service should boot before the members of the load-
balancing cluster. (Remember that applications configured to
automatically start also start when PAN Manager starts, restarts, or
fails over.)
Owner — The owner is the user who has permission to start the
load-balancing service. The owner must be set as "root."
11-6 PM5.2_BF
Load Balancer Member Attributes
The members require the following attributes:
Load-balancing service name — The service name is the name of

the load-balancing service as defined when the service was created
(in Step 2). By specifying the service name, the member pServers
know the IP address used by the load-balancing service, port, and
protocol of the load-balancing service.
The name must conform to PAN Manager naming conventions.

Names are limited to the following characters: upper-case or lower-
case letters, numbers, dollar sign ($), period (.), dash (-), and
underscore (_). The name is required and must be unique.The
maximum name length is 32 characters. To ensure that CLI output
displays line up, specify names with a maximum length of 12
characters.
IP name — Specifies the name of the IP resource configured with

the primary IP address of the member pServer. The name must
conform to PAN Manager naming conventions. Names are limited
to the following characters: upper-case or lower-case letters,
numbers, dollar sign ($), period (.), dash (-), and underscore (_).
The name is required and must be unique. The maximum name
File System — Specifies the name of the file system resource

required by the application. The name must conform to
PAN Manager naming conventions. Names are limited to the
following characters: upper-case or lower-case letters, numbers,
dollar sign ($), period (.), dash (-), and underscore (_). The name is
required and must be unique.The maximum name length is 32
characters. To ensure that CLI output displays line up, specify
names with a maximum length of 12 characters.
pServer name — Specifies the name of the pServer to add as a

member of the load-balancing service. The name must conform to
PM5.2_BF 11-7
Weight — If a weighted scheduling policy is used, such as

weighted round-robin or weighted least connected, assign a weight
to each of the member servers. Weight is a static whole number
greater than one used to increase the connections to a member
pServer. Weight is required if the load-balancing service policy is
weighted (either weighted round-robin or weighted least
connected). The default weight is 1.
Alias — The alias is used for the IP address of the load-balancing

service. Configure the IP address of the load-balancing service on
the members to enable them to receive requests. The alias number
is an ordinal number between 0 (zero) and 9. (The IP address of the
load-balancing service is configured by specifying the service
name.) The IP address of the load-balancing service is configured
on an alias on a local interface on the pServer. It does not consume
a vEth. The default alias is 0 (zero).
LPAN name — Specifies the name of the LPAN that contains this
member pServer. The name must conform to PAN Manager naming
conventions. Names are limited to the following characters: upper-
case or lower-case letters, numbers, dollar sign ($), period (.), dash
(-), and underscore (_). The name is required and must be
of 12 characters.
Member name — Specifies the name given to this member of the

load-balancing cluster. The member name should be different from
the name of the member pServer. The name must conform to
11-8 PM5.2_BF
Optional Load Balancer Member Attributes
PAN Manager allows you to define certain optional attributes of the

members of the load-balancing service. If you choose not to define
them, PAN Manager uses the default values. You can specify any or
all of the following attributes:
Description — Specifies a description is used for information

purposes only. The default is no description.
Failover policy — You can specify a failover policy for the load-
balanced application. The default is no failover policy. It is good
practice to have a failover policy for any and all mission-critical
applications and services.
Health monitor — You can specify a health monitor for the load-
balanced application. The default is no health monitor. It is good
practice to have a monitor for the application, especially if you are
using a failover policy.
Automatically start — You can choose to have the load-balanced

application start automatically when the pServer boots. The default
is to require a manual start of the application.
If you choose to automatically start the load-balancing service, all

of the member applications should also be set to automatically start.
If the pServers boot in a specified order, the pServer running the
load-balancing service should boot before the members of the load-
balancing cluster. (Remember that applications configured to
automatically start also start when PAN Manager starts, restarts, or
fails over.)
Owner — The owner is the user who has permission to start the
load-balanced application. The default is root.
PM5.2_BF 11-9
Starting the If the pServer is already booted and running, you must manually
Load-balancing start the load-balancing service.
Service
When you start the load-balancing service first, the members start
automatically.
If you start a member of the load-balancing service first, the service

also starts automatically (if the service is not already started).
However, other members of the cluster are not started.
Router A load-balancing scenario with the following conditions requires an

Requirements additional pServer configured as a router:
• The pServer running the load-balancing service has vEths
configured with both internal and external IP addresses.
• The members of the load-balancing service have vEths
configured with only internal IP addresses.
In this scenario, you must configure a pServer to act as a router for

the outgoing responses from the load-balancing service members.
The pServer configured as a router cannot be used as a failover
pServer for the load-balancing service. Configure the router as the
default gateway on the load-balancing member pServers, using
conventional procedures. The following figure illustrates this
scenario.
11-10 PM5.2_BF
Figure 11.2 Load-Balancing Cluster with Router
Load-balancer Member
MyLPAN
pServer3 pServer1
vSwitch_A vSwitch_B
External
Network
pServer4 pServer2
Router Member
PM5.2_BF 11-11
Configuring a Load Balancing Service

for This Task
Steps to Note: Load Balancing Services are not supported for

Configure a Load pServers that are running the Windows® operating system.
Balancing
Service ```To configure an LPAN’s load balancer for the CLI:
1. Create or delete a load balancer.
2. Assign the following resources to a load balancer:
• Network
• Failover policy
• Health monitor
• User-defined monitor
3. Add members to the load balancer.
4. Start a load balancer and its members.
```To configure an LPAN’s load balancer for the GUI:

1. Create or delete a load balancer.
2. Modify non-resource settings for a load balancer.
3. Manage resources for the member servers.
4. Add members to the load balancer.
5. Start, stop, or move a load balancer and its members.
Create or Delete ```To create an LPAN’s high-availability load balancer:

a Load Balancer
Availability.
11-12 PM5.2_BF

Load Balancers area, click the Create button.
3. In the Create Load Balancer dialog box, enter the name of the
load balancer, optionally select the check box next to Proceed
directly to Load Balancer page after creation, and then click
Submit to create the application.
```To delete an LPAN’s high-availability load balancer:

Availability.
Load Balancers area, click the Delete button.
3. In the Delete Load Balancers dialog box, select the check box
next to the Name of the load balancer that you want to delete.
4. Click Delete to proceed with the operation, or click Cancel to
Assign Network ```To assign or unassign a network (IP) resource to a service:

Resources
Availability.
that you want to assign to (or unassign from) an application or
load balancer.
3. In the Network Resource Network Resourcename page, in the
Service Assignment area, click the Assign/Unassign button.
want to unassign) this network resource.
dialog box.
PM5.2_BF 11-13
Assign Failover ```To assign or unassign this failover policy resource to a service:
Policy
A high-availability service can only be configured to use one
Resources
failover policy at a time.
Availability.
the Service Assignments area, click the Assign/Unassign
button.
want to unassign) this failover policy resource.
dialog box.
Assign Health ```To assign or unassign this health monitor resource to a service:
Monitor
Resources
Availability.
button.
want to unassign) this health monitor resource.
11-14 PM5.2_BF
5. If you are assigning this health monitor resource, use the pull-
down menu to select an available Network Resource for this
health monitor resource to monitor.
dialog box.
Assign a User ```To assign a user-defined monitor to a load balancer:

Defined Monitor
to a Load
Availability.
Balancer
Load Balancers area, click the Load Balancername to which
you want to assign a user-defined monitor.
3. In the Load Balancer Load Balancername page, click the
4. In the Monitors page, in the User Defined Monitors area, click
the Assign button.
5. In the Assign Monitor for H/A dialog box, select the radio
button next to the Name of the user-defined monitor you want
to assign to this load balancer.
dialog box.
The monitor appears in the User Defined Monitors area.
```To unassign a user-defined monitor from a load balancer:

Availability.
Load Balancer area, click the Load Balancername to which
you no longer want this user-defined monitor assigned.
the Unassign button.
PM5.2_BF 11-15
5. In the Unassign Monitor dialog box, select the check box next
to the Name of the user-defined monitor that you no longer want
assigned to this load balancer.
dialog box.
The monitor no longer appears in the User Defined Monitors
area.
```To define an action PAN Manager takes on a load balancer

associated with the monitor in response to a rule:
Availability.
Load Balancers area, click the Load Balancername for which
you want to configure an action for its user-defined monitor.
3. Click the Monitor tab at the top of the page.
the Edit button.
5. In the Edit monitor dialog box, the Edit Rule Action table lists
the rules currently associated with this monitor. In the Action
column, select an action from the pull-down list, and then click
Update.
Add Members to ```To add a member to a high-availability load balancer:

the Load
Balancing Note: For each member application service that you
Service select, be sure its pServer’s operating system supports the
application service, and that the PAN agent is present on the
pServer.
Availability.
Load Balancers area, click the Load Balancername to which
you want to add a member.
11-16 PM5.2_BF
3. In the Load Balancer Load Balancername page, in the

Application Members area, click the Add button.
4. In the Add Member dialog box, you can configure the
following fields:
• Use the Choose Application to add pull-down menu to
select an available application to add to this load balancer.
• Enter an integer in the Weight field to specify the
proportion of network traffic that this application receives,
relative to the entire load of network traffic managed by the
load balancer. A pServer with a higher weight receives new
jobs first and gets more jobs than a pServer with a lower
weight. For more information on the schedulers, see the
Linux ipvsadm man page.
• Use the Application Network pull-down menu to select an
existing network resource that this specified load balancer
can use as this application’s primary network interface.
• Optionally select the check box next to Start w/ Load
Balancer to enable PAN Manager to automatically start this
application when the load balancer starts.
dialog box.
```To modify the settings for a member of a load balancer:

Availability.
Load Balancers area, click the Load Balancername whose
member settings you want modify.
Application Members area, click the Modify button.
4. In the Modify Member dialog box, select the Application
Membersname heading whose settings you want to modify, and
make appropriate changes.
PM5.2_BF 11-17
5. Click Submit to save your work, or click the X in the upper

corner of the dialog box to close the Modify Member dialog
box without modifying any field.
```To remove a member from a load balancer:

Availability.
Load Balancers area, click the Load Balancername from
which you want to remove a member.
Application Members area, click the Remove button.
4. In the Remove Member dialog box, select the check box next
to the Member name of the application that you want to remove
from this load balancer.
5. Click Remove to proceed with the operation, or click Cancel to
Start, Stop, or ```To control a load balancer and its members:

Move a Load
Balancing
Availability.
Service
Load Balancers area, click the Load Balancername you want
to control.
3. On the bottom border of this Load Balancer Load
Balancername page, in the Controls area, you can use the
following control buttons:
• Click to start this load balancer.
• Click to stop this load balancer.
• Click to move this load balancer and its members to
booted pServers specified in its failover policy
configuration or back to its primary pServer, if available.
11-18 PM5.2_BF
If an action is currently prohibited on this load balancer, the

button is shaded.
Modifying Load Balancer Control Configurations
This section discusses how to modify load balancer control

configurations and includes the following topics:
• About Modifying Load Balancer Control Configurations
• Modifying Load Balancer Control Configurations
• Modifying Advanced Settings for a Load Balancer Control
Configuration
• Modifying Resource Assignments for a Load Balancer Control
Configuration
• Starting, Stopping, and Moving a Load Balancer and its
Members
About Modifying The LPAN Administrator modifies load balancer control

Load Balancer configurations. Use the same procedure to modify load balancer
Control control configurations as you did to create them.
Configurations
make to existing load balancer control configurations:
• Add a health monitor resource configuration to a load balancer
control configuration.
• Rename a load balancer control configuration.
• Change the autostart setting for a load balancer control
configuration.
• Move a load balancer control configuration.
• Force the load balancer control configuration to stop.
PM5.2_BF 11-19
Modifying Load ```To modify an LPAN’s high-availability load balancer name or

Balancer Control description:
Configurations
Availability.
Load Balancers area, click the Load Balancername that you
want to modify.
3. In the Load Balancer Load Balancername page, click the Edit
button.
4. In the Edit Load Balancer dialog box, you can Rename the
load balancer and update its Description.
dialog box.
Modifying ```To modify advanced settings for a load balancer:

Advanced
Settings for a
Availability.
Load Balancer
Control 2. In the High Availability for LPAN LPANname page, in the
Configuration Load Balancers area, click the Load Balancername that you
want to modify.
4. In the Advanced Load Balancer Configuration dialog box,
click the Auto-Start heading and select, as appropriate, the
check box next to Auto-start load balancer if available
pServer boots.
5. Click Submit.
To close the Advanced Load Balancer Configuration dialog
box without modifying any field, click the X in the upper corner
of the dialog box.
11-20 PM5.2_BF
Modifying Note: To learn how to create resource configurations (executable,

Resource network, network file system, and so forth), see Chapter 9,
Assignments for “Configuring Resources”.
a Load Balancer
Control ```To manage resource assignments for an LPAN’s high-
Configuration availability load balancer:
Availability.
Load Balancers area, click the Load Balancername whose
resource assignments you want to manage.
3. From the Load Balancer Load Balancername page, you can
manage any resource assignment for this load balancer from any
of the following areas in the page:
• Primary pServer—Click the Assign/Unassign button. In
the Assign/Unassign pServer as Primary dialog box,
select the radio button next to the Name of the new primary
pServer assignment.
Important: For the pServer that you select, be sure
that the operating system supports the application service,
and that the PAN agent is present.
Click Assign to save your work, or click Cancel to close the
dialog box.
• Load Balancing Connections—Do any of the following:
– Click the Create button. In the Create Connection
dialog box, use the Protocol pull-down menu to select
tcp, tcp (persist) or udp, enter an integer to specify the
Port to which this load balancer listens, use the Policy
pull-down menu to select the algorithm that this load
balancer uses to distribute requests to its members.
Click Submit to save your work, or click Cancel to
– Click the Modify button. In the Modify Connection
dialog box, click the Load Balancer Connectionname
heading that you want to modify, and make appropriate
PM5.2_BF 11-21
modifications in the configurable fields. Click Submit

to save your work, or click Cancel to close the dialog
box.
– Click the Delete button. In the Delete Connection
dialog box, select the check box next to the Name of the
load balancer connection that you want to remove from
the load balancer. Click Delete to continue, or click
• Failover Policy—Click the Assign/Unassign button. In the
Assign/Unassign Failover Policy dialog box, select (or
clear) the radio button next to the Name of the failover
policy that you want to assign to, or unassign from, this load
balancer. Click Assign to save your work, or click Cancel
• Health Monitors—Do any of the following:
– Click the Assign button. In the Add Health Monitor
Resource dialog box, select the check box next to the
Name of a health monitor resource that you want to
assign to this load balancer, and use the pull-down menu
to select an available Network Resource for this health
monitor resource to monitor. Click Assign to save your
work, or click Cancel to close the dialog box.
– Click the Modify button. In the Modify Health
Monitor Assignments dialog box, use the pull-down
menu to select a different, existing Network resource
for any configured health monitor resource assigned to
this load balancer. Click Submit to save your work, or
– Click the Remove button. In the Remove Health
Monitor Resources dialog box, select the check box
next to the Name of the health monitor resource to
remove from this load balancer. Click Remove to
• Network (IP) Resources—Do any of the following:
11-22 PM5.2_BF
– Click the Assign button. In the Add Network

Name of the network resource to assign to this load
balancer, and optionally specify an Order for the
network resources. Click Assign to save your work, or
– Click the Set Order button. In the Order Network
Resources dialog box, enter a new Order for any
network resource assigned to this load balancer. Click
Submit to save your work, or click Cancel to close the
dialog box.
– Click the Remove button. In the Remove Network
Name of the network resource to remove from the load
balancer. Click Remove to continue, or click Cancel to
Starting, ```To control a load balancer and its members:

Stopping, and
Moving a Load
Availability.
Balancer and its
Members 2. In the High Availability for LPAN LPANname page, in the
Load Balancers area, click the Load Balancername you want
to control.
3. On the bottom border of this Load Balancer Load
Balancername page, in the Controls area, you can use the
following control buttons:
• Click to start this load balancer.
• Click to stop this load balancer.
• Click to move this load balancer and its members to
booted pServers specified in its failover policy
configuration or back to its primary pServer, if available.
If an action is currently prohibited on this load balancer, the
button is shaded.
PM5.2_BF 11-23
11-24 PM5.2_BF
Part II
Controlling and
Monitoring the PAN
This part outlines the tasks involved in controlling and monitoring

the PAN, and consists of the following chapters:
• Chapter 12, “Controlling PAN Components”

• Chapter 13, “Configuring Events, Triggers, and SNMP”
• Chapter 14, “Archiving for Disaster Recovery”
• Chapter 15, “Using the Resource Configuration Collector”
• Chapter 16, “Maintenance and Troubleshooting”
Chapter 12
Controlling PAN
Components
This chapter describes controlling PAN components. Sections in

this chapter include:
• Controlling the Platform
• Controlling a Blade
• Controlling PAN Manager
• Controlling an LPAN
• Controlling a pServer
• Controlling LPANs and pServers Together
PM5.2_BF 12-1
You can control the PAN components in the following ways:
Table 12.1 Control Capabilities of PAN Components
Component Control Capabilities
Platform Boot, shut down, reboot
Control Blade Power on, power off, reset, send non-maskable

interrupt (NMI), select/unselect, mark as out/in
service
PAN Manager Start, stop
Processing Power on, power on but suppress booting (“warm

Blade standby”), power off, send non-maskable interrupt,
select/unselect, mark as out/in service *
LPAN Boot, shut down, reboot
pServer Boot, shut down, reboot
* Failover time to a pBlade is significantly reduced if the target

pBlade is in “warm standby” state, i.e., powered on but not
booted. The PAN Manager gives preference to such pBlades
for failover if any are available. When a “warm” pBlade is
chosen for failover, the PAN Manager causes the pBlade to
boot.
12-2 PM5.2_BF
Controlling PAN Components
Controlling the Platform
About You can boot, reboot or shut down a platform. Shutting down a
Controlling the platform shuts down all the pServers running on the Processing
Platform Blades of the specified platform. Shutting down a platform also
shuts down and powers off both Control Blades.
Rebooting a platform brings back the last configuration before

shutdown. The LPANs that were booted and their previously
booted pServers will reboot, while unbooted LPANs remain
unbooted. If a pServer was running on a failover pBlade, the
pServer reboots using the failover pBlade. LPANs boot in the order
specified in their configuration.
Warning: Rebooting or shutting down a platform will cause an

! interruption in processing of all pServers configured for the
specified platform. Both Control Blades shut down or reboot,
causing an interruption in the entire system.
Roles Required PAN Administrator

for This Task
Shutting Down a ```To shut down a platform:

Platform
1. In the left pane, click Platforms > platformname.
2. In the right pane, on the bottom border of the Platform
platformname page, in the Controls area, click .
3. In the Shutdown Platform dialog box, from the pull-down list,
select Time until Shutdown (minutes), to start the shutdown
operation.
4. (Optional) In the Shutdown Platform dialog box, enter a text
consoles currently open on this platform.
PM5.2_BF 12-3
5. To shut down the platform, click OK; to quit the operation, click
Cancel.
6. Clicking OK displays a Warning Prompt dialog box. To
continue, click Continue; to quit the operation, click Cancel.
Rebooting a ```To reboot a platform:

Platform
2. In the right pane, on the bottom border of the Platforms
platformname page, in the Controls area, click .
3. In the Reboot Platform dialog box, from the pull-down list,
select Time until Reboot (minutes), to start the reboot
operation.
4. (Optional) In the Reboot Platform dialog box, enter a text
consoles currently open on this platform.
5. To reboot the platform, click OK; to quit the operation, click
Cancel.
6. Clicking OK displays a Warning Prompt dialog box. To
continue, click Continue; to quit the operation, click Cancel.
12-4 PM5.2_BF
Controlling a Blade
About You can perform the following control operations on any blade on
Controlling a the platform:
Blade
• Power off
• Power on
• Reset
• Send a non-maskable (NMI) interrrupt
• Select/unselect
• Mark as out of service or in service
These functions are typically reserved for diagnostic and recovery

purposes only
Warning: Powering off a Processing Blade makes that blade

! unavailable to the associated LPAN and pServer. If a pServer has
failover policies defined for this blade, those policies are triggered,
affecting applications.
Powering off a cBlade causes the remaining cBlade to assume all

processing.
Do not power off both Control Blades or both sBlades at the same
time. This causes a system failure.
Note: Do not reinsert any blade (into an existing or new slot) until
the chassis LED has extinguished.
Roles Required PAN Administrator

for This Task
PM5.2_BF 12-5
Controlling a ```To control a pBlade:

pBlade
You use the buttons in the Controls area at the bottom of a blade
page to control all of the functions of a pBlade. The control
action you perform depends upon the current status of this
pBlade. To control this pBlade:
2. In the right pane, on the Platform platformname page, in the
table listing the status of blades in the platform, select the
pBlade number in the Slot column.
In the right pane, the pBlade platformname/pN page appears,
where N is the slot number of the selected pBlade.
3. In the Controls area, on the bottom border of this pBlade page,
use one of the following buttons to control the selected pBlade:
• Click to power this pBlade on or off.
• Click or to set the pBlade as a warm or cool
pBlade, respectively. (A "warm pBlade" is powered up, and
when used for pServer failover, can minimize failover time;
a cool pBlade is in a powered off state.)
• Click to power cycle this pBlade.
• Click to send an NMI (Non-Maskable Interrupt) to this
pBlade.
• Click to select or unselect this pBlade.
• Click to mark this pBlade as Out of Service or In
Service.
Note: If an action is currently prohibited on the blade, the

button is shaded.
4. Clicking any of these buttons displays an appropriate dialog
box. To continue the operation, click OK; to quit the operation,
click Cancel.
12-6 PM5.2_BF
```To select or unselect one or more pBlades for an administrative

task:
You can select or unselect a group of pBlades for an
administrative task without using the buttons in the Controls
area on the pBlade page.
1. In the left pane, click Resources > pBlades.
2. In the right pane, on the pBlades page, click the Set Selection
button.
3. In the Set pBlade Selection dialog box, do either of the
following in the Select column:
• Select the check box next to each pBlade you want to select
for an administrative task.
• Clear the check box next to each pBlade you want to
deselect for an administrative task.
4. Click Submit to save your work or Cancel to close the dialog
box.
```To mark one or more pBlades as Out of Service or In Service:

You can mark a group of pBlades as Out of Service or In
Service without using the buttons in the Controls area on the
pBlade page.
1. In the left pane, click Resources > pBlades.
2. In the right pane, on the pBlades page, click the Set Service
Status button.
3. In the Set pBlade Service Status dialog box, do either of the
following in the In Service column:
• Select the check box next to each pBlade you want to place
In Service.
• Clear the check box next to each pBlade you want to place
Out of Service. (If the pBlade is currently configured on a
booted pServer, PAN Manager places the pBlade Out of
Service the next time the pServer is shutdown or rebooted.)
PM5.2_BF 12-7
4. Click Submit to save your work or Cancel to close the dialog

box.
Controlling a ```To control a cBlade:

cBlade
You use the buttons in the Controls area at the bottom of the
blade page to control all of the functions of a cBlade. The control
action you perform depends upon the current status of this
cBlade. To control this cBlade:
table listing the status of blades in the platform, click C1 or C2
in the Slot column.
In the right pane, the cBlade platformname/C1 or cBlade
platformname/C2 page appears.
3. If you plan to power a cBlade off or powercycle a cBlade, and
you do not want to send an alert to Fujitsu Siemens Computers
customer support or your authorized support vendor, use the
PAN Manager command line interface to turn maintenance
mode ON.
a. Log on to a cBlade.
b. Change to the /opt/panmgr/bin directory, then turn
maintenance mode on.
# cd /opt/panmgr/bin
# maintenance on
4. The Controls area, on the bottom border of this cBlade page,

has the following buttons for controling the selected cBlade:
• Click to power this cBlade on or off.
• Click to powercycle this cBlade.
• Click to send an NMI (Non-Maskable Interrupt) to this
cBlade.
• Click to select or unselect this cBlade.
• Click to mark this cBlade as Out of Service or In
Service.
12-8 PM5.2_BF
Note: If an action is currently prohibited on the blade, the

button is shaded.
click Cancel.
6. If applicable, use the PAN Manager command line interface to
turn maintenance mode back OFF.
a. Log on to the cBlade.
b. Change to the /opt/panmgr/bin directory, then turn
maintenance mode off.
# cd /opt/panmgr/bin
# maintenance off
Caution: Since PAN Manager dynamically configures certain IP

addresses, you must control cBlades using PAN Manager instead of
network stop or restart commands. If you perform the network stop
or network restart commands on a cBlade, PAN Manager loses its IP
addresses and networking failures occur. Avoid executing network
stop or network restart on a cBlade. If executing these commands is
unavoidable, you must restart PAN Manager on the cBlade.
Controlling a ``` To control a cBlade switch (BladeFrame BF200 only):

cBlade switch
You use the buttons in the Controls area at the bottom of the
(BladeFrame BF
blade page to control all of the functions of a cBlade ES or a
200 only)
cBlade switch. The control action you perform depends upon the
current status of this cBlade ES or cBlade switch. To control this
cBlade switch:
table listing the status of blades, select C1 or C2 in the Slot
column.
In the right pane, the cBlade platformname/C1 or cBlade
platformname/C2 page appears.
PM5.2_BF 12-9
3. On the bottom border of this cBlade page, in the Controls area,

there are two buttons you can use to control the selected cBlade
switch:
• Click to power the cBlade switch on or off.
• Click to power cycle the cBlade switch.
click Cancel.
Controlling PAN Manager
About PAN Manager starts automatically when the Control Blades boot. It
Controlling is designed to run in a master/slave relationship. The PAN Manager
PAN Manager instance that starts first (cBlade 1 is always given preference)
becomes the master and assumes control of all
PAN Manager-related operations.
Note: Stopping and starting PAN Manager are typically reserved

for diagnostic and recovery purposes only.
The PAN Manager instance on one Control Blade automatically

reboots the other Control Blade if that Control Blade does not have
its instance of PAN Manager running. This protects the boot, I/O,
and network mapping that PAN Manager maintains in the kernel
from getting stale. To shut down PAN Manager completely without
a Control Blade getting rebooted, shut down both master and slave
at the same time, that is within 45 seconds of each other. Shut down
the master Control Blade first, followed by the slave Control Blade.
Reboot both Control Blades in order (master first) to restart
PAN Manager. To determine which Control Blade is master, use
the bframe command. The Use column for the c1 and c2 blades
indicates which is master and which is slave.
12-10 PM5.2_BF

for This Task
Starting Start PAN Manager with an initialization script, which takes a

PAN Manager start argument. Use the /etc/rc.d/init.d/panmanager start
script to start PAN Manager.
Shutting Down Shut down PAN Manager with an initialization script, which takes
PAN Manager a stop argument. Use the /etc/rc.d/init.d/panmanager stop
script to shut down PAN Manager.
Controlling an LPAN
About You can boot, shut down, and reboot an LPAN. Booting an LPAN
Controlling an boots all of the pServers in the LPAN configured to boot
LPAN automatically. The pServers boot in the order specified in their
configuration. If a pServer was running on a failover pBlade, the
pServer reboots using the failover pBlade if the primary pBlade is
not available.
Shutting down an LPAN causes all pServers in the LPAN to be shut

down, and the pBlades to be powered off.
Rebooting an LPAN causes all pServers in the LPAN to shut down,

to boot their operating systems, and run their initialization scripts.
This is equivalent to rebooting each of the pServers individually.
Note: If a pServer was shut down individually before the LPAN was
rebooted, that pServer does not reboot. Rebooting an LPAN reboots
pServers that are running at the time of shutdown.
Roles Required • PAN Administrator

for This Task
PM5.2_BF 12-11
• LPAN Administrator for the specified LPAN

• LPAN Operator for the specified LPAN
Booting an LPAN ```To boot an LPAN:

2. In the right pane, on the bottom border of the LPAN LPANname
page, in the Controls area, click .
3. In the Boot LPAN dialog box, click OK.
Rebooting an ```To reboot an LPAN:

LPAN
3. In the Reboot LPAN dialog box, from the pull-down list, select
Time until reboot (minutes) to start the reboot operation.
4. (Optional) Select the check box next to Boot pServers that are
shutdown during reboot if you want PAN Manager to boot
pServers that are currently shutdown.
5. (Optional) In the Reboot LPAN dialog box, enter a text message
in the field, Message to send to console, to send to all consoles
currently open on pServers in this LPAN.
6. (Optional) If the pServer has no PAN agent running on it, select
the check box next to Force pServer reboot to reboot currently
booted pServers.
7. To reboot the LPAN, click OK; to quit the operation, click
Cancel.
Shutting Down ```To shut down the LPAN:

an LPAN
12-12 PM5.2_BF
3. In the Shutdown LPAN dialog box, from the pull-down list,

select Time until Shutdown (minutes) to start the shutdown
operation.
4. (Optional) In the Shutdown LPAN dialog box, enter a text
5. (Optional) Select the Force pServer shutdown check box if
you want PAN Manager to force shutdown of currently booted
pServers.
6. To shut down the LPAN, click OK; to quit the operation, click
Cancel.
Controlling a pServer
About You can boot, shut down, and reboot a pServer using the
Controlling a PAN Manager. Booting causes the specified pServer to be powered
pServer up, to boot its operating systems, and to run its initialization script.
pServers boot in the mode specified in their boot option.
Shutting down a pServer causes the specified pServer to shut down,

and its pBlades to be powered off.
Rebooting a pServer causes the specified pServer to shut down, to

boot its operating system, and to run its initialization script.
Caution: Since PAN Manager dynamically configures certain IP

addresses, keep in mind the following:
• You must control pServers and high availability applications

using PAN Manager instead of network stop or restart
commands. If you perform the network stop/ restart commands
on a pServer running an application configured for high
availability, a networking failure occurs for any of the
application’s IP resources running on that pServer.
PM5.2_BF 12-13
For pServers, you must stop any applications, restart the PAN
Agent on the pBlade, and then restart the application.
• If an application health monitor loses its IP connectivity to a
monitored application, PAN Manager assumes that the
monitored application has failed and initiates the specified
failover policy for the application. In some instances, the
pServer hosting the health monitor can lose IP connectivity.
PAN Manager cannot detect whether the loss of IP connectivity
occurred with the pServer hosting the monitor or with the
pServer running the monitored application. If the loss of IP
connectivity occurred on the pServer hosting the monitor,
PAN Manager initiates a failover on an otherwise healthy
application.

for This Task
• LPAN Administrator for the LPAN containing the specified
pServer
• LPAN Operator for the LPAN containing the specified pServer
Booting and ```To boot a pServer:

Rebooting a
pServer
2. In the right pane, on the bottom border of the pServer
pServername page, in the Controls area, click .
3. (Optional) In the Boot pServer dialog box, in the Boot image
field, either accept the pServer’s currently configured boot
image or select another from the pull-down list.
4. (Optional) In the User Defined Boot Arguments field, specify
any customized boot arguments that you want the pServer to
boot with.
5. Click OK.
appears when the boot is complete.In the Boot pServer dialog
box, click OK.
12-14 PM5.2_BF
```To reboot a pServer:

3. In the Boot pServer dialog box, do the following:
a. From the pull-down list, specify a time (in minutes from
now) for the pServer to reboot.
b. Enter a message to appear on the pServer console to warn of
the impending reboot.
c. If the PAN agent is not running on the pServer, select the
Force pServer reboot check box.
d. (Optional) In the Boot image field, either accept the
pServer’s currently configured boot image or select another
e. (Optional) In the User Defined Boot Arguments field,
specify any customized boot arguments that you want the
pServer to boot with.
4. Click OK.
appears when the boot is complete.
Shutting Down a ```To shut down a pServer:

pServer
3. In the Shutdown pServer dialog box, specify the time of the
shutdown, and then enter a message to send to the system
console about the shutdown.
4. If a node agent is not running on the pServer’s pBlade, select
Force pServer shutdown to force the shutdown.
5. Click OK.
PM5.2_BF 12-15

Status indicates that the pServer is Shutting down. The word
Shutdown appears when the operation is complete.
When using pServers on vBlades, you must use the force option to:
• Shut down suspended a pServer
• Shut down or reboot an LPAN that includes a suspended
pServer
When you shut down a suspended pServer, PAN Manager discards

the file containing the suspended state. You can’t resume it after
that.
Controlling LPANs and pServers Together
About LPANs You can boot individual pServers just as you would conventional
and pServers servers. However, by grouping several pServers in an LPAN, you
can also boot and shut down pServers collectively. PAN
administrators, LPAN administrators, and LPAN operators should
be familiar with the following topics associated with LPAN and
pServer behavior:
• pServer Acquire/Release Resources Model
• pServer Boot Pending State
• LPAN Boot, Reboot, and Shutdown Model
• LPAN Reboot Model
The following sections discuss each of these topics.
12-16 PM5.2_BF
pServer Acquire/ A pServer acquires resources (for example, pBlade and disk) when
Release it successfully boots and releases these same resources when
Resources shutdown. When a pServer shuts down, it frees its pBlade and disk
Model resources, making them available for use by other pServers. In
addition, a pServer boots according to its failover policy upon its
next reboot causing it to revert back to its primary pBlade (if
available) on the next boot.
The following list summarizes the effects of the pServer acquire/

release resources model:
• A user can acquire resources (that is, reserve resources) for a
pServer that has booted.
• Resources from a shutdown (but previously booted) pServer
become available for assignment to another pServer.
• Rebooting a pServer assigned to boot from a pool can result in
the pServer rebooting on a different pBlade.
• The bframe command displays a pServer’s primary pBlade only
if the pServer has successfully booted. Likewise, the same
display semantics apply to the PAN Manager GUI.
• The PAN Manager CLI has no need to provide options to the
pserver command that acquires/releases pServer resources.
Likewise, the PAN Manager GUI has no need to provide the
equivalent functionality.
pServer Boot There are times when the arrival of a resource should cause a failed
Pending State pServer to attempt to reboot. For example, after a power outage, if
the platform comes up before the SAN, PAN Manager
automatically reboots the pServers when the SAN becomes
available.
Another example is the loss and recovery of a platform power

domain: when the power is restored, PAN Manager attempts to
recover the failed pServers.
PAN Manager provides a Boot Pending state that has a long (one
hour, by default) timeout. If a resource is lost by a pServer and the
resource returns within the timeout period, the pServer attempts to
PM5.2_BF 12-17
boot. If the timeout expires, the pServer sends an event and

transitions to the shutdown state. A successful pServer boot or
shutdown operation removes the Boot Pending state. A user-
initiated boot that fails due to an unsatisfied resource allocation
does not cause the pServer to enter the Boot Pending state. Boot
Pending only occurs when a booted pServer fails and cannot
recover due to inadequate resources.
The following list summarizes the circumstances in which a

pServer exits the Boot Pending state:
• If the required resource returns for a pServer in the Boot Pending
state, the pServer exits the Boot Pending state and moves into
the Booting state.
• If a user issues a shutdown command to a pServer in the Boot
Pending state, the pServer exits the Boot Pending state and
moves into the Shutdown state.
• If a user issues a boot or reboot command to a pServer in the
Boot Pending state, PAN Manager returns an error message
stating that the pServer is in the Boot Pending state due to the
lack of a required resource, and therefore it cannot be booted.
Note: If a pServer is in the Boot Pending state and a PAN

Administrator modifies the pServer’s configuration (for example,
specifying that the pServer’s required disk is now an optional disk),
PAN Manager exits the pServer from the Boot Pending state and
boots the pServer.
As a result of the Boot Pending state, the PAN Manager CLI has no
need to provide an option to the pserver command that specifies
that a pServer automatically boot. Likewise, the PAN Manager
GUI has no need to provide the equivalent functionality.
PAN Manager displays Boot Pending as a valid state (shutdown/

boot pending). PAN Manager attempts to identify the missing
resource causing the pServer to be in the Boot Pending state.
12-18 PM5.2_BF
LPAN Boot, LPAN boot, reboot, and shutdown operations are passed directly to
Reboot, and the pServers within an LPAN. The lpan command determines the
Shutdown Model order of operations by traversing the pServer list in the LPAN in the
specified boot order. If the LPAN administrator did not specify a
boot order, the lpan command performs the operations in display
order. In addition, the lpan command traverses the pServer list
once. Therefore, if a pServer is in a transition state while the LPAN
operation is in progress, the pServer may be effectively skipped for
the operation.
The following list summarizes the effects of the LPAN boot, reboot,
and shutdown model on the PAN Manager CLI and GUI:
• If all the pServers in an LPAN are booted, and a user attempts to
boot the LPAN the resulting operation is a no boot operation, not
an error. PAN Manager displays an appropriate message
indicating that the user issued the command, but no boot
operations were initiated.
• Because the boot, shutdown, and reboot operations are
independent, all of these buttons will be available on the LPAN
page in the GUI at all times, regardless of the number of
pServers in an LPAN that are booted or shutdown.
LPAN Reboot An LPAN reboot operation is accomplished in two phases:

Model
• Phase one
In reverse boot order, all pServers in the LPAN that are in the
Booted state are shutdown. After the reboot operation
completes, these pServers are in the Shutdown state.
• Phase two
In boot order, boot the pServers that were in a Booted state at the
time that the LPAN reboot operation was invoked.
Note: If a required pServer (for the LPAN boot order) was shut
down prior to the LPAN reboot operation, it will be skipped over
during the LPAN reboot operation, even though it was marked
PM5.2_BF 12-19
as required. That is, during an LPAN reboot operation, only

those pServers that were already booted will be considered
required.

for this Task
• LPAN Administrator for the LPAN containing the specified
pServer
• LPAN Operator for the LPAN containing the specified pServer
Rebooting the See “Booting an LPAN” on page 12-12 and “Rebooting an

Entire LPAN LPAN” on page 12-12.
12-20 PM5.2_BF
Chapter 13
Configuring Events,
Triggers, and SNMP
As with any server, it is important to monitor the events and usage

of the platform. PAN Manager provides monitoring capabilities at
three levels:
• Platform system health
• pServer system health
• Application health
This chapter describes platform and pServer monitoring

capabilities. PAN Manager uses event notification to inform
administrators of important events in the system. This chapter
includes the following sections:
• Understanding Platform Monitoring
• Configuring Event Types
• Configuring Triggers
• Modifying Default Trigger Values
• Viewing Events
• Configuring SNMP Settings
• Exporting Virtual Network Topology Using SNMP
PM5.2_BF 13-1
For information on application health monitors, see Chapter 10,

“Configuring Applications for PAN Manager Control”.
The cBlades are equipped with a utility called CIO (Customer

Information Operation). CIO automatically alerts Fujitsu Siemens
Computers customer support or your authorized support vendor in
the case of a severe cBlade event, such as an unresponsive cBlade.
You can turn off this utility when such an event is expected,
typically during routine maintenance. See the discussion of
Maintenance Mode in Chapter 16, “Maintenance and
Troubleshooting”.
Understanding Platform Monitoring
Events An event is an occurrence that is generated either by an action or by

a condition meeting defined criteria. Events can happen on both the
physical (hardware) and logical (software) components of the
platform.
When an event occurs, PAN Manager may complete one or more of

the following actions:
• Send an e-mail notification.
• Send an SNMP trap (All user visible event types have an
associated SNMP trap. These SNMP traps are defined in the
PAN Manager MIB (Management Information Block). See
Appendix A, “SNMP Traps and Internal Events Tables”.)
Event actions are defined by the event type. Event types may be
configured to specify the action that PAN Manager should take
when an event of a specific event type occurs.
By default, SNMP traps are sent only for high-severity events

(i.e., with a severity level of 1 or 2). However, you can configure
PAN Manager to send an SNMP trap for a low-severity event.
13-2 PM5.2_BF
Configuring Events, Triggers, and SNMP
Event Types Each physical and logical component in the platform has a set of
event types. To view all possible event types associated with a
component, use the PAN Manager GUI.
```To view event types:

1. In the left pane, click the component for which you want to view
the event type.
2. Click the Events tab in the right pane.
3. Click the Event Types button. The list of all possible event
types for the selected component displays.
Monitors and Monitors track system resources and generate an event when a
Triggers certain condition is met. Logical monitors have one or more
configurable triggers that allow you to set the conditions that fire an
event. Triggers may have system-wide default values as well as
individual values for a specific pServer’s monitor. For information
on setting the default and individual trigger values, see
“Configuring Triggers” on page 13-9 and “Modifying Default
Trigger Values” on page 13-14.
Viewing Events Each event has the following attributes:
Event ID — A unique number generated for the specific event.

Events are numbered sequentially within security domains as they
occur. (You can only see the events in your security domain.) There
may be gaps in the event ID numbers due to the numbering system.
Event Message — A text message indicating the physical or

logical component that generated the event.
Event Status — A one-letter indication of an investigation into the

event. An event can have one of the following letters to indicate its
status:
• O = Open
• I = Investigating
PM5.2_BF 13-3
• R = Resolved
• U = Unknown
Events are generated with a status of Open ("O"). Modifying the

status of an event is optional.
Event Severity — A number from 1 (highest) to 6 (lowest) to

indicate the severity of the event. An event can have one of the
following numbers to indicate its severity:
• 1 = Critical
• 2 = Error
• 3 = Warning
• 4 = Unusual
• 5 = Information
• 6 = Debug
Time stamp — The date and time of the event, in the format "mm/
dd/yy hh:mm:ss".
Event user — The user that caused the event. If the event is
hardware-related, or caused by an unexpected event, the user is
"system." If the event is caused by human intervention, such as a
configuration event, the user is the user ID of the person who
caused the event.
System Component — The platform component that generated the

event.
SNMP Support PAN Manager provides two types of Simple Network Management
Protocol (SNMP) Version 1 and Version 2 agents:
PAN Agent — Provides monitor and control access for the PAN
resources. PAN resources include both logical attributes of the
PAN, such as LPANs and pServers, and physical attributes of the
platforms in the PAN, such as blades and disks.
13-4 PM5.2_BF
LPAN Agent — Provides monitor and control access for a given

LPAN’s resources. LPAN resources include the logical attributes of
the LPAN, such as pServers and pools, and the physical attributes
of the LPAN, such as blades and disks.
Each SNMP agent provides information restricted to the scope of

its control. For example, an LPAN agent can only see resources of
the LPAN for which it is configured. It cannot see resources
allocated to another LPAN.
PM5.2_BF 13-5
Configuring Event Types
About Event PAN Manager software provides a set of default actions for each
Types event type. The administrator for each administrative domain (PAN
or LPAN) can set new defaults for their domain. In addition, an
administrator can customize the actions for a specific event type.
Administrators can modify default actions, but can only add custom
actions; custom actions do not override domain defaults.
The out-of-the-box default actions for each event type are:

• Send an SNMP trap
• Do not send an e-mail message

Members of an administrative domain inherit the settings for that

domain. For example, pBlade event types inherit the settings for the
platform.
Note: For the list of event types that can send SNMP traps, see
Appendix A, “SNMP Traps and Internal Events Tables”.
Role Required PAN Administrator (for PAN level defaults)

for This Task
LPAN Administrator (for LPAN level defaults)
Two Steps to The following are the major steps for configuring event action and
Configure Event notification:
Action and
1. Configure the domain defaults.
Notification
2. Configure and enable the event action(s) for an event type.
13-6 PM5.2_BF
Configure the Configuring the Domain

Domain Defaults
```To configure event action and notification for the domain:
want to configure.
3. On the Domain Settings page, click Event Settings.
4. In the Configure Event Settings dialog box, do any of the
following:
• In the Send email notification to area, specify the email
address(es) of the person or group to whom PAN Manager
is to send system messages about events in this domain.
• In the SNMP area, select the check box to direct the entity
reporting an event to send an SNMP trap.
• In the Minimum Severity field, use the pull-down list to
select the minimum event severity to generate your
configured notifications.
5. To save the configuration, click Submit.
Configuring the LPAN Domain
```To configure event action and notification for the LPAN

domain:
2. In the right pane, on the LPAN LPANname page, click the
3. In the Advanced LPAN Configuration dialog box, click the
Event Action and Notification heading to display the
4. To configure Event Action and Notification for the LPAN
domain, do any of the following:
• In the Email area, specify the email address(es) of the
person or group to whom PAN Manager is to send system
messages about events.
PM5.2_BF 13-7
• In the SNMP area, select the check box to direct the LPAN
entity reporting an event to send an SNMP trap.
• In the Minimum Severity area, use the pull-down list to
select the minimum event severity (1 to 6, where 1 is the
most severe) to generate your configured notifications.
5. Click Submit.
Configure and ```To customize event action and notification for an event type:
Enable the Event
1. In the left pane, click the monitored object associated with the
Action(s) for an
event type that you want to modify.
Event Type
In the right pane, an appropriate object page appears.
2. Click the Monitor tab at the very top of the page.
3. To display the individual monitors in a Monitor group, click the
Monitor group heading of the individual monitor that you want
to display.
To collapse this list, click the heading again.
4. Click the Event Trigger for the individual monitor event type
On the Event Type page, in the Actions area, the default email
and SNMP actions of this event type are listed for each
appropriate security domain.
5. In the Actions area, select the Custom Actions radio button,
and then do one or both of the following:
• Enter the email address of the person or group to receive
notification of an event of this type.
• Select the Send SNMP Trap check box to have
notifications of events of this type sent to any configured
SNMP manager(s).
Note: You can also restore the event type to a default event
action and notification configuration by selecting the Default
Actions radio button in the appropriate security domain area.
13-8 PM5.2_BF
6. Click Submit to save your changes, or click the Monitor tab to

return to the Monitor page without saving your changes.
Configuring Triggers
About Triggers PAN system monitors have triggers that define the conditional
criteria to fire an event. Out-of-the-box PAN Manager provides the
trigger defaults shown in the following table. Monitors shown with
an asterisk (*) have configurable triggers.
Table 13.1 Default Trigger Values
Monitor Trigger Value
+12 ATX Voltage High Value = 14.6 volts

Low Value = 9.77 volts
+2.5 Voltage High Value = 2.77 volts

+3.3 ATX Voltage High Value = 3.64 volts

+5 ATX Voltage High Value = 5.54 volts

CPU0 Core Voltage High Value = 1.76 volts

CPU0 Temperature exceeds 72 degrees Celsius
CPU1 Core Voltage High Value = 1.76 volts

CPU1 Temperature exceeds 72 degrees Celsius
PM5.2_BF 13-9
Monitor Trigger Value
pServer 1 Minute Load exceeds 20.0 for 300 seconds

Average *

Average *

Average *
pServer CPU Utilization * exceeds 90% for 300 seconds
pServer Disk Block Read Rate exceeds 100,000 reads per second
* for 600 seconds
pServer Disk Block Write Rate exceeds 100,000 writes per second
* for 600 seconds
pServer Disk Used Percentage exceeds 90% for 300 seconds

Rate *
pServer Memory Utilization * exceeds 90% for 180 seconds
pServer Network Packet exceeds 100,000 packets per second

Receive Rate * for 600 seconds
pServer Network Packet Send exceeds 100,000 packets per second

Rate * for 600 seconds
pServer Network Receive Error exceeds 100,000 packets per second

pServer Network Send Error exceeds 100,000 packets per second

pServer Swap Utilization * exceeds 90% for 300 seconds
The default trigger settings apply to all monitors of that type. For
example, each pServer in the PAN has its own Swap Utilization
monitor. Each of those monitors inherits its trigger values from the
default. The PAN Administrator and LPAN Administrator can
reconfigure trigger values for specific monitors within their
administrative domain. For example, the Swap Utilization monitor
for pServer1 can have triggers with a different value than the
13-10 PM5.2_BF
default. The Swap Utilization monitor for pServer1 uses the

reconfigured values; the Swap Utilization monitors for all of the
other pServers use the default trigger values.
Triggers on hardware monitors cannot be reconfigured. Only

triggers on monitors indicated with an asterisk in the previous table
can be reconfigured.
Note: Changes to monitor and trigger settings are lost if the

platform is rebooted. When a platform reboots, the default values are
restored and the PAN Administrator must re-enter the modified
settings.
Note: PAN Manager generates an internal event with a severity 3

(3=SEVERITY_WARNING) when a pServer software monitor
exceeds the specified limit. For example, PAN Manager generates a
3=SEVERITY_WARNING when a pServer’s 1 minute load
average monitor exceeds 20.0 seconds on average for 300 seconds.
PAN Manager generates an internal event with a severity 5

(5=SEVERITY_INFO) when a pServer software monitor returns to
a normal operating range. For example, PAN Manager generates a
5=SEVERITY_INFO when a pServer’s 1 minute load average
monitor returns to a normal operating range.
Note: The PAN Manager command to configure system monitors

(mon) should not be confused with the MON service monitoring
daemon. MON is used to monitor application health. For more
information on using MON with the platform, see “Configuring
Health Monitor Resource Configurations” on page 9-46.

for This Task
Two Steps to There are two major steps for configuring default trigger values:
Configure
1. List the monitor and its associated triggers.
Triggers
2. Modify individual trigger values.
PM5.2_BF 13-11
List the Available You can display selected monitors in two formats by selecting the
Monitors and individual monitors that you want to display and then selecting the
Their Triggers appropriate format button at the top of the Monitor Groups area:
• Charts—data is grouped by Monitor groups and the chart is
formatted according to your selection in the Monitor group
heading.
• Tables—data for each monitor is a row in a table with headings
Name, Value, Unit.
```To list the available monitors in charts or tables:

1. In the left pane, click the monitored object you want to view.
The Monitors page appears in the right pane. The Monitor
groups area below it lists all the Monitor Groups associated
with the object you selected.
3. To display the individual monitors in a Monitor group, click a
monitor group heading. (Click the heading again to collapse
this list.)
4. Select the individual monitors displayed under the heading that
you want to display:
• Click the Select All button to select all the monitors under
one heading.
• Click the Unselect All button to clear all the check boxes
under this Monitor group heading.
• Select or clear individual check boxes.
5. (Optional) Use the pull-down menu to select a Chart Type.
You can display data for other individual monitors by selecting
those monitors before proceeding.
6. Scroll to the top of the page and select the Charts or Table
button to format the display of data.
13-12 PM5.2_BF
7. To reformat the display of data, click the Charts or Table

button at the top of the Monitor Chart View page or Monitor
Table View page.
To return to the Monitors area, click the Select Monitors
button. The Monitor groups heading(s) under which you have
selected individual monitors are collapsed and have checks next
to them.
Configure the ```To modify the monitor threshold for an event type:
Trigger(s) for a
Monitor Note: Only certain monitors have event types that have
configurable monitor thresholds.
1. In the left pane, click the monitored object associated with the
event type that you want to modify.
The Monitor page appears in the right pane. The Monitors area
lists the monitor groups associated with the object that you
selected.
3. To display the individual monitors in a Monitor group, click the
Monitor group heading of the individual monitor that you want
to display.
To collapse this list, click the heading again.
4. Click the Event Trigger for the individual monitor event type
The Event Type page is displayed. If this Event Type is
configurable, the Hardware/Software Monitor Threshold
description of this event type has configurable fields.
5. Enter the new value(s) for this Hardware/Software Monitor
Threshold.
6. Click Submit to save your changes, or click the Monitor tab to
return to the Monitor page without saving your changes.
PM5.2_BF 13-13
Modifying Default Trigger Values
About Default The PAN Administrator can set new defaults for the triggers
Triggers indicated with an asterisk in Table 4.2, “Default Trigger Values”.
The trigger default settings (either out-of-the-box or set by the PAN
Administrator) apply to all monitors within the PAN. Setting new
trigger default values is only available through the PAN Manager
CLI.
Caution: If you reset the default trigger values, you must restart
PAN Manager.

for This Task
Two Steps to There are two major steps for configuring default trigger values:
Configure
1. List the monitor and its associated triggers.
Triggers
2. Modify individual trigger values.
13-14 PM5.2_BF
Viewing Events
About Events You can view events that have occurred in the system. You can also
filter the list of events or view the details of a single event. Users
can only view events generated in their administrative domain
(LPAN). The PAN Administrator can see all events. A
PAN Manager user can update an event instance, provided that user
has privileges for the component that generated the event.
Note: Due to the stateless nature of the hardware, events generated

before the software sets the blade’s clock have a timestamp of 12/31/
1969. The events that are generated with this timestamp are benign
and may be ignored.

for This Task
• LPAN Administrator
• LPAN Operator
• LPAN Monitor
Three Steps to There are three major steps for viewing events:
View Events
1. Apply a filter and view a list.
2. View the event instance details.
3. Update the event instance status.
Apply a Filter and ```To apply a filter to a list of events:

View a List
Events are always filtered based on your security role. This filter
configuration is applied to the list of events that PAN Manager
lets you view. You can configure or modify the event filter from
any object that your security role can view.
1. In the left pane, click any object for which there is a list of
events.
PM5.2_BF 13-15

2. Click the Events tab.
3. On the Events page, click the Set Filter button.
4. In the Set Events Filter dialog box, select the radio button(s)
next to any of the following fields:
• Use the Severity field to specify a severity range (1 is most
severe; 6 is least severe) to filter events.
• Use the ID field to use a limited range of event ID numbers
to filter events.
• Use the Time Stamp field to filter events based on when
they occurred—specify the delimiting date(s), in the format
yy/mm/dd hh:mm:ss, where yy=year, mm=month, dd=day,
hh=hour, mm=minute, and ss=second.
• Use the Status field to filter a list of events by their status.
• Use the Event Message contains field to filter events based
on a specific string in the event description. Enter the string
without quotes. For example: to display each event whose
description mentions the LPAN called lpan5, enter lpan5; to
display each event whose description mentions the pBlade
called p1 on a platform named f2, enter f2/p1.
5. When you finish specifying the filter settings, do any of the
following:
• To apply this filter and return to the Events page, click
Submit.
The Events page is displayed. At the top of the Events
Blocks area, a row displays the current filter settings and a
Remove button.
• To clear the settings you just entered, click Clear Filter.
• To return to the Events page without saving your changes,
click Cancel.
13-16 PM5.2_BF
```To remove a filter from a list of events:

An event filter persists until you log off. You can remove a filter
at any time.
events.
3. On the Events page, at the top of the Events Pages area, click
the Remove button next to the event filter configuration.
View the Event ```To view the details of an event instance:

Instance Details
events.
The Events page is displayed listing one or more Events
Blocks. Each Events Block lists events for the chosen object as
they are logged, not necessarily by their event ID.
3. To view another Events Block list of events for this object, click
a Page Number at the top of the table, if available.
4. Clicking the Type ID column displays the Event Type page for
this event.
Update the Event ```To update the status of an event instance:

Instance Status
events.
3. On the Events page, in the Status column, click the icon of the
event instance whose status you want to update:
PM5.2_BF 13-17
• means the event is open

• means the invent is under investigation
• means the event is closed
4. In the Update Status dialog box, select the radio button next to
the appropriate status.
5. Click Submit to update the status, or Cancel to close the dialog
box.
```To update the status of all events in the current event pages, to
“resolved:”
events. In the right pane, an appropriate object page appears.
3. On the Events page, click Set Filter to filter the list of events
for the object that you want to set to Resolved.
4. With the final list of events displayed, click the Resolve Events
button.
The displayed events now have the icon displayed in the
Status column.
Configuring SNMP Settings
About SNMP If you use SNMP (Simple Network Management Protocol) to

manage your network, you can configure the platform to use
SNMP. The platform provides two types of SNMP Version 1 and
Version 2 agents:
PAN — Provides monitor and control access for PAN resources.
LPAN — Provides monitor and control access for a given LPAN’s

resources.
13-18 PM5.2_BF
Each SNMP agent provides its own view of the available resources,
based on its security domain. The LPAN SNMP agent can only
view resources in its LPAN; it cannot view resources in other
LPANs.
SNMP agent addresses are restricted to the network determined by

the PAN IP address and network mask. Further, SNMP agent
addresses might NOT coincide with addresses assigned to cBlades.
Finally, each security domain that utilizes its SNMP agent must
choose a unique address/port combination for the agent.
PAN Manager rejects invalid SNMP agent IP addresses/port
configurations.
Each SNMP agent can be enabled to monitor or control the

resources in its domain.
Monitor — Allows all authorized management stations to read

SNMP objects from the agent, provided they specify a valid read-
only or read-write community string.
Control — Allows authorized management stations to set SNMP

objects on the agent, thereby invoking management operations,
provided they specify the valid read-write community string.
To enable an SNMP agent, monitor must be enabled. To allow the

agent to invoke management operations, both monitor and control
must be enabled.
Note: If you do not want to use SNMP, you can omit configuring
the SNMP settings. SNMP is disabled by default.

for This Task
Two Steps to There are two major steps for configuring SNMP settings:
Configure SNMP
1. Configure the SNMP agent(s).
2. Configure the SNMP manager(s) for the SNMP agent.
PM5.2_BF 13-19
Configure the ```To configure or modify the SNMP agent for this administrative
SNMP Agent(s) domain:
1. In the left pane, click the name of the PAN or LPAN you want
to configure.
3. On the Domain Settings page, click the SNMP Agent button.
4. In the Configure SNMP Agent Settings dialog box, configure
or modify the following fields:
• In the IP Address and Port fields, specify an IP address and
UDP port number on which an SNMP agent listens for
requests.
• In the Contact and Location fields, specify the email
address of the domain’s SNMP administrator and the
physical location of the platform.
• In the Community Strings fields, specify the Read (Read-
Only) and Read/Write strings accepted by the SNMP agent
for this domain.
• In the Scope field, select Disable, Monitor, or Monitor
and Control from the drop-down list to specify the SNMP
agent’s scope of control for this domain.
5. Click Submit.
Configure the ```To configure the SNMP Manager(s) for this domain:
SNMP
Manager(s)
want to configure.
3. In the right pane, on the Domain Settings page, in the SNMP
External Managers area, click the Add button.
4. In the Add new SNMP External Manager dialog box,
configure the following fields:
13-20 PM5.2_BF
• In the IP Address field, specify an IP address of the external

SNMP manager that controls and (or) monitors the PAN
domain, and optionally, to which the agent for this domain
sends trap messages.
• In the Netmask field, specify an IP address mask to
authenticate either a specific SNMP manager or a group of
managers.
• In the Trap Port field, specify the UDP port number on
which the external SNMP manager is to receive trap
messages from the agent for this domain.
Note: For the domain agent to send traps to this manager, the
port number must be greater than zero. A value of zero prevents
an agent from sending traps to this manager.
• In the Community String field, specify a valid community
string that the SNMP manager will accept from the agent.
The default is “public.”
• Select the radio button next to the Version field, either
SNMP v1 (default) or SNMP v2c, to specify the trap format
of the SNMP software used by the SNMP manager.
5. Click Submit.
```To modify the SNMP Manager(s) for this domain:

want to configure.
External Managers area, click the Modify button.
4. Click the IP Address heading of the existing SNMP Manager to
display the configurable fields.
5. Enter the new values for the settings that you want to modify.
6. Click Submit.
PM5.2_BF 13-21
```To delete the SNMP Manager(s) for this domain:

1. In the left pane, click the name of the PAN, platform, or LPAN
that you want to configure.
External Managers area, click the Delete button.
4. Select the check box next to the IP Address of the existing
SNMP Manager that you want to delete.
5. Click Delete.
Exporting Virtual Network Topology Using SNMP
The PAN Manager SNMP agents export proprietary Management

Information Bases (MIBs) that allow SNMP Managers to discover
network topology using SNMP management tools. This section
describes the MIB tables for the following network components:
• Platform Eths
• rEths
• vSwitches
• pServer Eths
These tables describe the component attributes and the relationships

between components, which allow the mapping of a PAN virtual
network topology.
Note: This does not include exporting routing tables of cBlades or

pServers.
13-22 PM5.2_BF
cBlade Eths Eths serve as uplinks for vSwitches and as building blocks for
rEths. Each entry in the Eth table exports attributes already exposed
through the CLI and GUI, as follows:
• Name of the interface
• Reference to the host sBlade or cBlade
• Hardware MAC address
• Software MAC address
• Port type/speed
• List of VLAN IDs and uplink descriptions
rEths PAN networking uses the concept of a Redundant Eth (rEth) to take
advantage of the redundancy of the network controller blades (i.e.,
the blades that contain the Ethernet ports). The PAN Manager
SNMP agents export the existence of rEths in addition to Eths. A
rEth table exports the same set of rEth attributes already exposed
through the CLI and GUI, as follows:
• Name of the rEth
• Primary Eth interface
• Secondary Eth interface
• rEth MAC address
• rEth failover policy
• rEth flow control policy
vSwitches The vSwitches serve to connect pServers to other pServers and to

other networks. SNMP uses a vSwitch table to export vSwitch
attributes, as follows:
• vSwitch name
• rEth uplink name
• VLAN ID
• Uplink description
PM5.2_BF 13-23
• vSwitch LPAN allocations

• vSwitch pServer Eth allocations
pServer Eths SNMP uses the following tables to export the pServer Eth
attributes.
The pServer Eth table exports the following:

• Byte, packet, and error counters
• Eth MAC address
• Eth state (up or down)
• Eth addresses
In addition, a pServer Eth IP table exports the following:

• Interface or alias name
• IP address
• Broadcast address
• Network mask
Viewing the ```To display the Virtual Network Topology:

Network
Topology with
PAN Manager 2. In the right pane, at the top of the page, click the icon next
to Network Resources.
13-24 PM5.2_BF
Chapter 14
Archiving for Disaster
Recovery
This chapter describes the features in PAN Manager that allow the
PAN Administrator to archive PAN configurations. This
functionality is designed to help with the implementation of disaster
recovery procedures for the platform.
This chapter includes the following topics:

• PAN Archiving for Disaster Recovery
• Exporting a PAN Archive
• Importing an Archive
• Merging PAN Configurations
• Mapping Resources
• Validating a PAN Archive
• Swapping the Current PAN for a PAN Archive
• Reserving a Disk for Exclusive Storage of PAN Archives
• Managing an Image Archive
PM5.2_BF 14-1
PAN Archiving for Disaster Recovery
About Disaster PAN Manager offers disaster recovery features that allow the PAN
Recovery Administrator to replace a current PAN configuration with an
archived PAN configuration. The major steps of the procedure are
the following:
1. Export a PAN configuration archive periodically.
2. Import a PAN archive onto a target PAN (platform).
3. Merge the PAN configuration on the target platform(s) with the
PAN archive to preserve certain settings that exist on the target
platform(s).
4. Map the resources in the PAN archive to those available in the
target system.
5. Swap (replace) the target’s PAN configuration with the PAN
archive.
You can use PAN archives for the following purposes:

• To repair damaged PAN configuration files.
• To restore a destroyed or incapacitated platform onto a disaster-
recovery platform.
• To retarget a platform.
Although PAN archiving is designed primarily for disaster
recovery operations, you can use it to retarget a platform even
when no recovery is necessary. For example, a PAN
Administrator can configure a platform to run one PAN
configuration during the day and another at night.
PAN archives can be exported to a local disk (on a cBlade) or saved

to a location outside the platform, for example, to a SAN disk. You
can schedule PAN archiving to occur regularly to ensure that
backups are current.
14-2 PM5.2_BF
Archiving for Disaster Recovery
What an Archive A PAN archive contains saved PAN configuration information,

Contains including the following items.
• General PAN domain information (name, owner, description,
location, and accounts)
• IP addresses for internal and external networks, multicast
address, and port number
• SNMP settings
• Mail gateway information (from address, SMTP server
information)
• Default event actions for the PAN domain (e-mail, send SNMP
traps, and minimum severity)
• Platform identity and power settings
• PAN Manager users (removal of invalid roles)
• Eths for the sBlade or cBlade NICs
• rEth settings and vSwitch configurations
• SAN disk resource mapping
• SAN disk persistent reservation flags (enable/disable)
• LPAN and pServer configurations and settings, including boot
and root disk image registration information
• All non-registered (custom) pServer boot images
• Registration information for ISO images used in virtual
CD-ROMs (not the images themselves)
• Failover configurations
• High-availability application configurations
• The following cBlade log files (optional):
• console.log
• tomcat.log
• egenera_cli.log
• tftp.log
PM5.2_BF 14-3
Note: Depending on the size of these log files, including them

can add a significant amount of time to the archiving process.
What an Archive The following are not included in the PAN archive:
Does Not
• Linux user accounts and any associated files. (PAN Manager
Contain
accounts are included.)
• cron files.
• Registered (i.e., custom) pServer boot images.
• Root disk images.
• Media images (VCDs.
• Disks’ persistent reservation data (that is, the pServer
registrations and reservations), other than the enable/disable
flag.
Note: To reduce the size of an archive, you may consider registering

your custom boot images. You can archive registered boot images
(and other images) using another PAN Manager procedure. See
“Managing an Image Archive” on page 14-24.
A Note on Boot There are two components to configuring boot and root disk images
and Root Disk on pServers:
Images
• The image files
• The configuration data in PAN Manager that defines the
location of the image files and their names
The physical boot and root disk image files are very large and are
not saved to the PAN archive. The configuration data is archived to
allow you to switch back to the archive without repeating the
process of registering the boot and root images.
14-4 PM5.2_BF
Preparing a The following items are beyond the scope of the PAN Manager’s
Platform for disaster recovery functionality. These items are not archived, and
Recovery they must be installed and/or configured on the target platform
before an archived PAN configuration is swapped in.
• The appropriate version of cBlade software must be installed on
both cBlades.
• Disks must be installed with the appropriate pServer operating
system(s) corresponding to the pServer boot image(s)
configured in the archive.
• VLANs that the archived PAN is expecting must be configured
on the target platform.
Copying If you want to copy a PAN configuration from one platform to

Configurations another, do not use the merge feature. Merging overwrites certain
from One settings in the archive with values from the target platform.
Platform to
Another Instead of merging, modify the PAN configuration archive by
performing the following procedure between the import and swap
steps. The purpose of this procedure is to configure unique
resources, such as IP addresses and SNMP IP addresses, in the
archive.
```To modify the PAN configuration archive:

1. Extract the contents of the archive from its JAR file:
# jar -xvf archive-name
The content is extracted to ../runtime.

2. Edit the extracted configuration files to specify your desired
configuration. The files are:
../runtime/misc/platform-conf.xml
../runtime/misc/domain-conf.xml
3. Repackage the archive, adding the name of any configuration

file you have modified:
# jar -uvf archive-name modified-file-name
PM5.2_BF 14-5
Moving If you want to move a PAN archive from a BladeFrame BF400 S2

Configurations (maximum of 24 blades) to a BladeFrame BF200 (maximum of six
Between a blades), there are special considerations due to the smaller number
BladeFrame BF4 of possible blades on a BladeFrame BF200. You must create a
00 S2 and resource map that maps blades greater than six to None. This
BladeFrame BF2 prevents an error when you swap the BladeFrame BF400 S2
00 archive onto a BladeFrame BF200.
If the cBlade configuration on the BladeFrame BF400 S2 contains

more rEths than the target BladeFrame BF200, you must remove
the extraneous rEths from the configuration. (To remove a rEth, use
the pan -m [-h] command. See the PAN Manager pan man page
or PAN Manager Command Reference for more details.)
You may save this resource map file and use it whenever you want
to swap a PAN archive from a BladeFrame BF400 S2 to a
BladeFrame BF200.
Exporting a PAN Archive
About Exporting You can export and import PAN configurations, and retarget your
and Importing platform to run any imported PAN configuration. You can also
view and validate imported configurations to ensure their
correctness before you swap to the new configuration.
For additional security, PAN archives can be exported to a SAN

disk, thus allowing you to transfer a PAN configuration outside the
local platform. The SAN disk must be allocated for disaster
recovery, as described in “Reserving a Disk for Exclusive Storage
of PAN Archives” on page 14-23.
Caution: You can only choose a SAN disk that is not currently
assigned to an LPAN. After you export this file, you will erase it if
you use PAN Manager to subsequently assign the disk to an LPAN
and root the disk.
14-6 PM5.2_BF

for This Task
Steps to Create, There are two steps to export a PAN archive:

Export, or Delete
1. Create a PAN archive.
a PAN Archive
2. Export the PAN archive to the desired location.
There is one step to delete a PAN archive:

1. Delete the PAN archive.
Creating, Creating a PAN Archive

Exporting, or
Deleting a PAN ```To create a PAN archive:
Archive
1. In the left pane, select the name of the PAN.
2. In the right pane, on the PAN pan_name page, click the
Disaster Recovery button.
3. On the Disaster Recovery page, click the Save Current PAN
button.
4. In the Archive Current PAN dialog box, enter an Archive
name for the current PAN configuration. (The default name is
identical to the name of the PAN.)
Note: The name panmaster is reserved for internal

PAN Manager use. You cannot use it as an archive name.
5. To include an internal log file in the archive (for possible future
diagnostic use by Fujitsu Siemens Computers customer
support), select the Include internal log files check box.
6. Click Submit to create an archive file (archive_name.par) that
resides on both cBlades.
The archive now appears in the Archives area.
PM5.2_BF 14-7
Exporting a PAN Archive
```To export a PAN archive to a disk that is external to the

platform (useful for disaster recovery purposes):
3. On the Disaster Recovery page, in the Archives area, click the
Export button.
4. In the Export Archive dialog box, select a location to which to
save the PAN archive file. Do one of the following:
• Select the Local file radio button, and then click Browse to
save the PAN archive file on a local computer.
• Select the cBlade file system radio button to save the PAN
archive file on the cBlade.
Caution: You can only choose a SAN disk that is not currently
assigned to an LPAN. When you export this file, you erase it if you
use PAN Manager to subsequently assign the disk to an LPAN and
root the disk.
• Select the SAN Disk radio button; from the pull-down list,
select a SAN disk that has been reserved for the purpose of
storing PAN archive files.
5. If an identically named archive already exists in the export area
you have selected, select the Rename PAN check box, enter a
new name for the archive, and click Submit.
Deleting a PAN Archive
```To delete a PAN archive:

14-8 PM5.2_BF

Delete button.
4. In the Delete Archives dialog box, select the check box next to
each archive that you want to delete.
5. Click Delete.
Scheduling Optionally, you can direct PAN Manager to create and export
Regular archives on a regular schedule.
Archiving
Creating a Schedule
```To create a schedule for creating PAN archives on a regular

basis:
3. On the Disaster Recovery page, in the Archiving Schedules
area, click the Create button.
4. In the Create Archive Schedule dialog box, do the following:
• In the Schedule name field, specify the name of the
schedule that PAN Manager will use to back up the PAN
configuration. (For clarity, specify a name that describes the
backup frequency, such as "weeklysched1".)
• In the Initiate archiving at area, specify the following time
parameters of the archive schedule:
– Time: The hour and minute of the day that the archive
will be created, and whether the time is early (AM) or
late (PM) in the day.
– Frequency: Specifies whether the archive is created
Daily or Once a week on a specific day of the week. If
weekly, select from the pull-down list the day of the
week on which the archive will be created.
PM5.2_BF 14-9
• In the Destination area, specify the location to which

PAN Manager will export the PAN archive. You can do
either of the following:
– To have PAN Manager save the archive on the Control
Blade(s), select the Default location on cBlade radio
button.
– (Advisable for disaster recovery) To store the newly
created PAN archive on a SAN disk (which is not
already assigned to an LPAN), select the SAN Disk
radio button, then select a disk from the pull-down list.
5. Click Submit.
Editing a Schedule
```To edit an existing schedule for creating PAN archives on a

regular basis:
area, click the name of the schedule you want to edit.
4. On the Archive Schedule page, click the Modify button.
5. In the Modify Schedule schedule_name dialog box, do any of
the following:
• In the Schedule name field, change the name of the
schedule that PAN Manager uses to back up the PAN
configuration.
• In the Initiate archiving at area, edit the following time
parameters of the archive schedule:
– Time: The hour and minute of the day that the archive
will be created, and whether the time is early (AM) or
late (PM) in the day.
14-10 PM5.2_BF
– Frequency: Whether the archive is created Daily or

Once a week on a specific day of the week. If weekly,
select from the pull-down list the day of the week on
which the archive will be created.
• In the Destination area, change the location to which
PAN Manager will export the PAN archive. You can do
either of the following:
– To have PAN Manager save the archive on the Control
Blade(s), select the Default location on cBlade radio
button.
– (Advisable for disaster recovery) To store the PAN
archive on a SAN disk (which is not already assigned to
an LPAN), select the SAN Disk radio button, then
select a disk from the pull-down list.
Deleting Schedules
```To delete one or more schedules for creating PAN archives:

area, click the Delete button.
4. In the Delete Schedules dialog box, select the check box next to
each schedule that you want to delete.
5. Click Delete.
PM5.2_BF 14-11
Importing an Archive
About Importing Importing an archive copies it from the storage location to the
an Archive cBlade in preparation for application to a PAN.

for This Task
Importing the ```To import a PAN archive:

PAN Archive
1. In the left pane, select the name of the PAN to which you are
importing an archive.
Import button.
4. In the Import Archive dialog box, in the Source Archive area,
do one of the following to locate the archive you want to import:
• Select the Local file radio button, then click Browse to
locate the PAN archive file on a local computer.
• Select the cBlade file radio button, and then click Browse
to locate the PAN archive file.
• Select the On SAN Disk radio button; from the pull-down
list, select a PAN archive file.
5. You cannot import a PAN archive if an identically named
archive already exists on the cBlades. To rename the PAN
archive as you import it, select the Rename PAN check box,
enter the new name, and click Submit.
The PAN archive file now resides on the cBlade(s).
14-12 PM5.2_BF
Renaming the ```To rename a PAN archive:

PAN Archive
(Optional) Note: You cannot use PAN Manager to rename an archive that
resides on a SAN disk. In this case, you must import the archive
before you rename it.
Rename button.
2. In the Rename Archive dialog box, select the archive you want
to rename from the Archive to rename scroll list, and then enter
a new name for the archive in the New name field.
3. Click Submit.
PM5.2_BF 14-13
Merging PAN Configurations
About Merging Merging a PAN archive with a current PAN configuration is

PAN required to ensure that configuration information specific to the
Configurations current (target) platform, such as IP addresses, is maintained after
the configurations are swapped.
Note: If you are replacing a PAN configuration with a PAN archive

created on the same platform, you do not need to merge the PAN
configuration files.
Merging replaces some PAN settings, modifies others (including

any resources you have mapped), and leaves others untouched.
Merging a PAN archive with the resources in the current PAN
replaces the following settings:
• General PAN domain information (owner, description, location,
using PAN Manager to manage accounts).
• IP addresses for internal and external networks, multicast
address, and port number.
• Platform name and power settings.
• PAN domain default event actions (e-mail, send SNMP traps,
minimum severity).
• Multicast flow control settings for each rEth interface.
• Boot image registration information. (pServer boot images are
reset if an image of the same name is not merged into the
archive. A warning is generated if a pServer’s configured boot
image is cleared.)
• Root disk image registration information.
• Mail gateway (from address and SMTP server info).
• PAN Manager users (removal of invalid roles).
14-14 PM5.2_BF
Merging replaces all of the settings in the PAN configuration

archive that are listed above, and this list cannot be modified. If you
only want to replace a subset of these settings, you must modify the
target platform appropriately before merging. For example:
• If you want the PAN configuration archive to maintain the same
Mail Gateway, modify the target platform Mail Gateway before
merging.
• If you want the same users and roles set in the PAN
configuration archive to be used on the target platform after the
merge, create the /home/username directories on the target
platform before merging.
• If you want the target platform to use new IP addresses for the
cBlades instead of the ones in the archive, configure the cBlade
with the new IP addresses before merging. (Be sure that third-
party software, such as SNMP Managers, are reconfigured to
point to the correct IP addresses.)

for This Task
Merging the ```To merge the configuration settings in the PAN archive with
Archive those in the current PAN:
name of the PAN archive.
4. On the PAN Archive archive_name page, click the Merge
button:
5. In the Merge PAN into Archive dialog box, click list of data
changed.
PAN Manager displays a list of the resources in the current PAN
that differ from those in the PAN archive.
PM5.2_BF 14-15
If there are any anomalies in the list, click Cancel; to proceed

with the merge, click Submit, then click Continue to confirm.
When the merge is complete, the PAN Archive archive_name
page reappears.
Mapping Resources
About Mapping Typically, you export, or save, a PAN archive on one platform and
Resources import the archive to another platform. After importing the saved
archive, you need to map resources (such as pBlades, disks, and
Eths configured in rEths) referenced in the PAN archive to the
resources that are available in the target PAN.
You can specify the following mappings:

• Map each pBlades to another valid pBlade or to None.
Note: pBlade mappings may cause changes to a global pool, an

LPAN, an LPAN pool, a primary blade, or a failover blade.
Note: PAN Manager does not allow you to map pBlades into
illegal configurations. For example, pBlades from two different
LPAN local pools and a global pool cannot all be mapped to a
single, fourth pBlade.
• Map each disk to another valid disk name or to None.
Note: Disk mappings may cause changes to LPANs, pServers,

and high-availability file-system resources.
• Map each eth to another valid eth name or to None.
Note: Eth mappings may cause changes to rEths.
During resource mapping, validation is also done, but the warnings

are suppressed. The resource mapping fails if the validation fails.
14-16 PM5.2_BF
There is an option to remove invalid rEths during resource

mapping. If this option is selected, rEths that are configured with an
eth that is not valid in the target PAN are removed. Also, if an eth is
configured in multiple rEths, all but one of those rEths is removed.
The rEth that remains is randomly chosen. It is not valid for an eth
to be configured in multiple rEths. If this option is not selected, the
resource mapping fails if any of these conditions are encountered.
Note: You can either build a resource map or specify a resource

map file built previously. If you upload a previously built resource
map, you can modify it before applying it. You can also save the
mapping you decide upon.

for This Task
Mapping PAN ```To map the resources for a PAN archive:

Resources
3. On the Disaster Recovery page, in the Archives area, click
Import and specify or select the name of a PAN archive.
4. On the PAN Archive archive_name page, click Map
Resources.
5. (Optional) On the Resource Mapping for Archive
archive_name page, click Upload Map File.
PAN Manager clears the existing mappings and populates the
page with the mappings in this file. You can modify the
mappings before applying them (go to Step 6).
6. Associate the resources in the PAN (pBlades, disks, tapes, and
eths) to matching resources in the PAN archive:
PM5.2_BF 14-17
• In the pBlades, Disks, Tapes, or Eths area, click Add.

From the Archive list box, select a resource, and then from
the Current PAN list box, select a matching resource from
the current PAN and click Add. Within each resource area,
you can add more than one mapping resource at a time.
• In the Options area, select the Map SAN devices (disks
and tapes) unique ID check box to map disks (or tapes) in
the PAN archive to disks (or tapes) in the current PAN,
based on unique SCSI IDs.
• In the Options area, to prevent PAN Manager from
attempting to map redundant Ethernet (rEth) interfaces in
the PAN archive with those in the current PAN, select the
Delete Invalid rEths check box.
7. (Optional) To save your mappings to a file, click Save Map
File.
8. Click Apply at the top of the page.
14-18 PM5.2_BF
Validating a PAN Archive
About Validating The validation process determines whether the configuration

a PAN Archive settings in the PAN archive map correctly to those in the current
PAN. Validation occurs during resource mapping (validation
warnings are suppressed during resource mapping), during PAN
swapping, or when specified by running the pan -v command.
This section describes the failures and warnings that can occur
during validation.
Validation A configuration fails during validation for the following reasons:

Failures
• A blade, disk, or Eth specified is not in a valid format.
• Blades that could never be in the platform (for example, slot 25
or slot 0) are specified.
• The same blade is configured in multiple LPANs or in an LPAN
and the global pool.
• The same disk is configured in multiple LPANs.
• Eths that could never be in the platform (for example, Eth33) are
configured in a rEth.
• Eths in the same blade are configured in a rEth.
• Eths that are not in the current platform are configured in a rEth.
(The invalid rEth can be removed during resource mapping by
selecting the Remove Invalid rEths option.)
• An eth is configured in multiple rEths. (The invalid rEth can be
removed during resource mapping by selecting the Remove
Invalid rEths option.)
• The type of a device in an LPAN or pServer cannot be
determined. (This means that the XML in the PAN archive is
invalid.)
PM5.2_BF 14-19
Validation The following can generate warnings during validation:

Warnings
• Blades with slot numbers that are valid, but are not physically in
the platform
• Disks that are in valid formats, but not detected by the platform

for This Task
Validating the ```To test (validate) the configuration settings in the PAN archive
Archive with those in the current PAN:
4. On the PAN Archive archive_name page, click the Validate
button.
5. In the Validate Archive dialog box, click Submit to continue.
6. When the confirmation Archive successfully checked for
validation appears at the top of the PAN Archive
archive_name page, the validation is complete.
14-20 PM5.2_BF
Swapping the Current PAN for a PAN Archive
About Swapping When resource mapping and PAN configuration merging have been
the Current PAN successfully completed, the current PAN configuration can be
replaced with the PAN archive. Validation is automatically
performed during the swap, and if validation fails, the swap does
not take place.
Swapping a PAN archive is the same as performing a full

PAN Manager restart on both cBlades. PAN Manager GUI users
are automatically logged out. The PAN Manager is inaccessible to
CLI and GUI users during the swap operation. After the swap
operation completes, PAN Manager automatically restarts. You
must log back on to the PAN Manager GUI.
Note: The PAN archive contains the SCSI-3 the persistent

reservation enable/disable flags, but it does not contain the
reservation data itself (that is, the pServer registrations and
reservations). When you swap in a DR archive, PAN Manager clears
all the persistent reservation data.
Note: The swap operation can result in the appearance of numerous

messages in console.log, which you can safely ignore. The swap
can also result in negative events in event.log, which might reflect,
for instance, virtual-resource configurations that are invalid in the
target PAN. It is advisable to disable the CIO facility during a swap
operation, to avoid sending needless alerts to your service provider.
See “Maintenance Mode” on page 16-3.
Note: A swap operation could result in bringing up a PAN Manager

that has the same Platform ID as another platform on the same
subnet. To avoid duplicate Platform IDs, you must change the ID
either during a merge operation or after the swap. If afterward, edit
the Platform ID in the Platform>Platform ID dialog, and restart
PAN Manager.
PM5.2_BF 14-21

for This Task
Swapping the ```To swap the current PAN configuration with a PAN archive:
Configuration
With the Archive
4. On the PAN Archive archive_name page, click the Swap
button.
Caution: Please note that:
• A swap operation replaces the current PAN (and all of its

current configuration) with the PAN that is stored in the
archive.
• A swap operation is not easily reversed.
• You will be logged out of PAN Manager and service might
be unavailable for several minutes.
5. In the Swap Archive dialog box, click OK to proceed (or
Cancel to return to the PAN Archive archive_name page).
If there are no errors, PAN Manager restarts automatically.
After PAN Manager restarts, the current PAN uses the new
resources.
If there are errors, you must correct the displayed resource
inconsistencies in the resource map of the PAN archive and then
attempt the swap operation again.
14-22 PM5.2_BF
Reserving a Disk for Exclusive Storage of PAN

Archives
This section discusses how to reserve disks for exclusive storage of

PAN archives.

for this Task
Reserving a Disk ```To allocate a PAN disk resource for PAN archive storage:
for Exclusive
Storing of PAN
Archives 2. In the right pane, on the SCSI Disks page, click the Allocate
Disks button.
3. In the Allocate disks dialog box, select the SCSI ID heading for
the disk that you want to reserve for PAN archive storage.
4. Select the Disaster Recovery radio button.
5. Click Submit to complete the allocation.
On the SCSI Disks page, in the PAN Disks area, the disk’s
Allocation now appears as Disaster Recovery.
```To modify a PAN disk resource allocation:

1. In the left pane, click Resources > Disks
2. Click the SCSI ID of the disk, and in the SCSI ID page, click
the Allocate button.
3. In the Change Disk Allocation dialog box, select the
appropriate radio button for your modification.
PM5.2_BF 14-23
Managing an Image Archive
A PAN configuration archive does not contain images (except for

non-registered boot images), because their large size would strain
storage resources and slow down the normal disaster recovery
procedures. The PAN Administrator can, however, use another
facility to archive and later restore any of the images not included in
a PAN archive: registered pServer boot images, root disk images,
and media images (VCDs).
Images may be used for their normal purposes, such as pServer

booting, while an export or restore operation is in progress. If an
export or restore operation is interrupted, or if PAN Manager fails
over while an archive operation is in progress, the administrator
should re-execute the process to make sure it runs to completion.
The procedures and PAN Manager behavior when archiving images

are slightly different from the behavior when archiving the PAN
configuration.
Image Export The image archiving facility exports a set of images either to a SAN
Behavior disk or to a designated location on the master cBlade (or network
location accessible from the master cBlade). The PAN
Administrator specifies a name for the set of exported images and
indicates which type(s) of images the set contains: non-custom boot
images, root disk images, or media images (VCDs).
• If the export destination is a SAN disk, the disk must have been
reserved for disaster recovery use. See “Reserving a Disk for
Exclusive Storage of PAN Archives” on page 14-23.
The exported image archive is appended to any files currently
residing on the disk. The PAN Administrator can use the pan
command to clear the disk of earlier content (both PAN archives
and image archives) before performing the export operation.
14-24 PM5.2_BF
The facility prepares for export by creating a temporary archive

on the master cBlade (in /crash_dumps/panmgr/
largetmpdir). The export process aborts if there is not
sufficient space on the cBlade to hold the temporary archive.
• If the export destination is on the cBlade, be aware that PAN
Manager does not register, mirror, or otherwise safeguard the
image archive, and the archive does not show up in any
command listings. Managing and safeguarding the archive is the
administrator’s responsibility.
Only one export operation is permitted at a given time, and images

may not be removed or modified while the export is in progress.
Images may be added during the export operation, but newly added
images will not appear in the archive.
Image Restore The behavior of the image-restore facility is slightly different from
Behavior the “import” behavior of the disaster recovery facility. Instead of
merging and then swapping in the archive, the administrator simply
restores the archive (or selected part of it), all in one step. The
images immediately become usable on the cBlade, and they are
mirrored to the other cBlade.
Besides choosing which image types to restore, the administrator

can also specify whether to overwrite matching files in the current
PAN. An image is considered “matching” if its original pathname
(before export) was the same as an image in the current PAN.
• No-overwrite behavior (default): The facility checks the

current PAN configuration, and restores images selectively:
Boot, root, and media images: The facility restores
resgistered images that do not match an existing image.
• Overwrite behavior: The facility restores all registered images
to the current PAN, overwriting existing images if necessary.
The overwrite option should be used only when the system is not
in heavy use. Not only is it demanding in time and computing
resources, but there is a risk of overwriting image files that are
in use.
PM5.2_BF 14-25
Exporting and This section describes how to export and restore an archive of
Restoring an image files in the current PAN.
Image Archive
Role Required for This Task
PAN Administrator
```To export an image archive:

1. In the left panel under the current PAN name, choose Disaster
Recovery.
2. On the Disaster Recovery page, under Image Archives, click
Export.
3. In the Export PAN Images dialog, indicate the desired
destination:
• If cBlade file system, specify the absolute pathname of the
image collection.
• If SAN disk, specify a name for the image collection.
This option is available only if you have previously reserved
a SAN disk for archiving. See “Reserving a Disk for
Exclusive Storage of PAN Archives” on page 14-23.
4. Still in the Export PAN Images dialog, choose which images
types to include: boot, root, and/or media. (Recall that
unregistered boot images are archived as part of the PAN
disaster recovery procedure.)
5. Click Submit.
```To restore an image archive:

Recovery.
Restore.
3. In the Restore PAN Images dialog:
a. Specify the location of the image archive to be restored.
b. Choose which images types to restore.
14-26 PM5.2_BF
c. Indicate whether to overwrite matching image files in the

current PAN.
4. Click Submit.
```To remove an exported image archive (archives on SAN disk

only):
Recovery.
Delete.
3. In the Delete Image Archives page, indicate which archive to
remove.
Note: The GUI displays only the archives stored on a SAN disk,
not those stored on the cBlade.
4. Click Submit.
PM5.2_BF 14-27
14-28 PM5.2_BF
Chapter 15
Using the Resource
Configuration Collector
This chapter describes the data collected by the PAN Manager

Resource Configuration Collector (RCC) and an administrator’s
requirements necessary to use this data. By processing the data in
the daily report files generated by PAN Manager RCC, you can
track physical (pBlade, storage disks, switches, etc.) resource usage
by each pServer over time. This use of PAN Manager is optional.
Sections in this chapter include:

• Understanding PAN Manager Resource Configuration
Collector
• Processing PAN Manager Resource Configuration Collector
Data
PM5.2_BF 15-1
Understanding PAN Manager Resource

Configuration Collector
PAN Manager PAN Manager RCC provides customers with an accurate and
RCC Overview configurable source of pServer configuration data at each pServer
state change. By taking a snapshot of the hardware and software
assignments of a pServer at state changes (i.e. when it boots,
reboots, fails over or shuts down), customers can track what
resources were running and when on each pServer. PAN Manager
RCC thus provides raw data customers can use to track what and
when hardware and software resources were used by pServer name.
With such information, Fujitsu Siemens Computers customers can
accurately charge their customers for pServer resource usage
accordingly.
PAN Manager RCC data reports are XML-formatted data arrays.

Using the DTD provided by Fujitsu Siemens Computers, you can
customize a parsing algorithm to grab only the data your
organization is interested in for calculating hardware and software
resource usage related to pServers over time.
How PAN Manager RCC is designed to run over a reporting period,

PAN Manager continuously listening for specific types of pServer-related events.
RCC Works Whenever a specific pServer-related event is generated,
PAN Manager RCC collects and stores the pServer’s configuration
data. At the completion of a reporting period, PAN Manager RCC
generates an XML-formatted report that includes each instance of
pServer configuration data collected during the reporting period.
A PAN Manager RCC report is generated once every 24-hour

period, from midnight to midnight. Until a daily report is generated
at midnight, the day’s PAN Manager RCC data is not available for
data processing. (Real-time data information on pServer events is
always available using PAN Manager’s event-generation system.)
15-2 PM5.2_BF
Using the Resource Configuration Collector
pServer The following table illustrates the type of configuration data

Configuration available in each PAN Manager RCC report:
Data Collected
by PAN Manager Table 15.1 pServer Configuration Data Collected by PAN Manager
RCC RCC
PAN Manager RCC collects the

Extract with tag
following data for:
A pServer immediately following an event for pserver-data

that pServer or for each pServer when a
reporting cycle begins or ends:
• Name
• Internal Ref-name
• Description
Each of the pServer’s current, primary, and blade-data

failover pBlades:
• Name
• Part Number
• Serial Number
• Number of CPUs
• RAM Capacity
• Clock Speed
• Cache
• Watts
This same data is collected if this pServer’s
current, primary, and failover pBlade
configuration comes from a local or global
pool.
PM5.2_BF 15-3
PAN Manager RCC collects the

following data for: Extract with tag
Each of the pServer’s “current” or “configured” image-data

OS image:
• Name
• OS Type
• cBlade Location
• Description
• Whether this image is the default image for
the PAN domain (yes | no)
• What PAN Manager image arguments are
associated with this image
• What PAN Manager boot arguments are
associated with this image
Each of this pServer’s storage disk assignment disk-data

by pServer ID (i.e, (1.0), (2.0), etc.):
• SCSI ID
• Capacity (in GB)
• Vendor
• Revision
• Serial Number
• UUID
Each of this pServer’s vEth configurations: veth-data

• The MAC Address associated with this vEth
• The pServer’s vSwitch name associated with
this vEth
• The Upper rate limit as which network traffic
is configured to flow through this interface
• Any IP Address assigned to this vEth at the
time of the event.
15-4 PM5.2_BF
Using the Resource Configuration Collector
Type of Events PAN Manager RCC listens for specific types of events for which it
the Trigger Data collects information. In general there are two different families of
Collection events which tells PAN Manager RCC to collect data for a pServer:
• A pServer event occurs (i.e., a pServer boot, reboots, fails over
or shuts down)
• The reporting cycle begins or ends
The latter events are important to keep in mind in the case where a
pServer does not change state when a report cycle begins or ends.
In the case where a pServer is already booted when the report cycle
begins or ends, the pServer’s configuration data is collected.If
several pServers are booted, then each pServer’s configuration data
is collected. The same is true when the report cycle ends.
Processing PAN Manager Resource Configuration

Collector Data
To process PAN Manager RCC reports, you must use a data-

processing application and ultimately calculate the resource usage
associated with this data. In developing and using this application,
the following information is important.
Location of the Fujitsu Siemens Computers provides a DTD file to process

PAN Manager PAN Manager RCC reports in the location /opt/panmgr/etc/
RCC DTD file rcc.dtd.
Location and PAN Manager RCC generates a report file from a reporting period
Format of RCC in the location /var/log/panmgr/rcc. Each report file is named
Reports using the following convention: rc-yyyy-mm-dd-hhmmss.xml.
PM5.2_BF 15-5
Here, yyyy represents the four-digit year, mm represents month, dd

represents day of month, hh represents hour of the day in military
format, mm represents minutes, and ss represents seconds.
Guidelines to Use the following guidelines to process PAN Manager RCC data:
Processing
• PAN Manager must be running for the PAN Manager RCC to
PAN Manager
function. In periods where PAN Manager goes down, no
RCC
PAN Manager RCC is collected.
• PAN Manager RCC data is not available until the end of a
reporting cycle.
• After you process a PAN Manager RCC report according to
your algorithm, you should transfer the data into a data
collection system designed to calculate the resource usage
associated with each pServer.
15-6 PM5.2_BF
Chapter 16
Maintenance and
Troubleshooting
This chapter describes some useful system maintenance procedures

and provides troubleshooting hints for resolving some problems
you might encounter when working with PAN Manager.

• Log Files
• Maintenance Mode
• Saving cBlade State Information
• Displaying a Configuration Report
• Maintenance LPAN
• Windows pServers
• Common Problems
PM5.2_BF 16-1
Log Files
Table 16.1 lists the locations of the log files for various
installations, with summaries of their contents.
Table 16.1 Locations of Installation Log Files
Log File Contents
/opt/egenera/install/ Contains a log of a cBlade scratch

egenera.install.log installation.
/opt/egenera/install/ Contains a log of a cBlade and
egenera.upgrade.log- pServer update.
2.1.xxx
/opt/egenera/install/ Contains a log of Egenera RPMs

egenera.software.log and base images installed.
/opt/egenera/install/ Contains a log of a Red Hat style
egenera.install.log-$RV scratch installation or upgrade, to a
named release number ($RV).
A Power Self Test (POST) is performed by the BIOS every time a

pBlade boots. Table 16.2 lists the location of the POST log file.
Table 16.2 Power Self Test Log
Log File Contents
/proc/egenera/ipmi/ Contains the value of the POST. (In

node/ap-XX/postcode the case of POST test failure, the
last value of POST code represents
the reason for the failure.)
16-2 PM5.2_BF
Maintenance and Troubleshooting
Maintenance Mode
The cBlades are equipped with a utility called CIO (Customer

Information Operation). CIO automatically alerts Fujitsu Siemens
Computers customer support or your authorized support vendor in
the case of a severe cBlade event, such as an unresponsive cBlade.
However, there may be times when such an event is expected,
typically during routine maintenance. In such cases, use the
maintenance mode feature to avoid sending an unneeded alert to
service personnel.
```To turn on maintenance mode:

1. Log on to a cBlade.
2. cd to the /opt/panmgr/bin directory.
3. At the prompt enter:
# maintenance on
```To turn off maintenance mode:

# maintenance off
```To check the status of maintenance mode:

# maintenance status
A message stating if maintenance mode is on or off appears.
PM5.2_BF 16-3
Saving cBlade State Information
As part of diagnosing a problem, Fujitsu Siemens Computers

customer support may ask you for a copy of the cBlade state
information. The save_state command collects detailed state
information from the /proc and
/proc/egenera directories, and creates a tar file that has been
compressed with gzip.
To save cBlade state information, use the following command on

each cBlade:
# /opt/egenera/bin/save_state pathname.tar.gz
where pathname is the full pathname of the resulting tar file.
In some situations, you may need to save state information several

times in a given day. For this reason, you should specify a unique
tar filename that includes your customer name, hostname, the date,
and the time; for example:
# /opt/egenera/bin/save_state /tmp/smartco_bf5_103105_23:59.tar.gz
Note: Do not tamper with files in the /proc and /proc/egenera

directories unless you are instructed to do so by Fujitsu Siemens
Computers customer support.
16-4 PM5.2_BF
Displaying a Configuration Report
When diagnosing a problem, you can verify the hardware and

software configuration with the showme command. This command
displays a detailed configuration report on standard output that
includes information about the blades, power input modules
(PIMs), Small Computer System Interface (SCSI) adapters,
Ethernet devices, and software.
Command The showme command has the following command-line syntax:

Options
# /opt/egenera/bin/showme [-b][-p][-d][-e][-s][-l][-h]
where:
• -b (blades only) — displays the configuration data for each
installed pBlade, cBlade, and sBlade. On the
BladeFrame BF200, this option displays data for each pBlade
and cBlade only. This data includes the serial number, part
number, firmware version, the quantity and clock speed of the
CPUs, amount of memory, CPU architecture, Baseboard
Management Controller (BMC) version, and Basic Input Output
System (BIOS) version.
• -p (PIMs only) — displays the configuration data for each PIM
on the BladeFrame BF400 S2. This option does not apply to the
BladeFrame BF200. This data includes the serial number, part
number, firmware version, number of Amps, connection type,
and BMC version.
• -d (disks only) — displays the configuration data for each Small
Computer System Interface (SCSI) adapter (HBA). This data
includes the adapter type, firmware and driver versions, loop
state, flags, and World Wide Name (WWN).
PM5.2_BF 16-5
• -e (Eths only) — displays the configuration data for each

Ethernet interface. This data includes the driver version, link
state, speed, and media type.
• -s (software only) — displays the cBlade software version,
including any upgrade versions and patch numbers.
• -l (long display) — displays complete configuration details for
use by Fujitsu Siemens Computers customer support. You can
use the -l option in combination with the -b, -p, -d, -e, or -s
option to display more details about blades, PIMs, disks,
Ethernet interfaces, or software. You can use the -l option by
itself to display details about all components, including the
internal Giganet adapters on the cBlade.
• -h (help) — displays the command syntax and supported
options.
When you specify the showme command without options, it displays

the configuration of all blades, PIMs, disks, Ethernet interfaces, and
software.
Sample Output The following example shows the configuration report for the PIMs
on a typical BladeFrame BF400 S2:
# /opt/egenera/bin/showme -p
Fujitsu Siemens Computers Configuration Report

----------------------------
frame5-c2 (10.10.10.1)
BladeFrame BF400 S2
10-31-05 9:19
-------------------------------------------------------------------------
PIMS:
PIM S/N P/N FW STS AMP CONN BMC
pim1 PR2SA300B013 950-000093 47000021R06 20C 30 L6-30 9.0
pim2 PR2SA300B011 950-000093 47000021R06 20C 30 L6-30 9.0
pim3 PR2SA300B014 950-000093 47000021R06 20C 30 L6-30 9.0
pim4 PR2SA300B012 950-000093 47000021R06 20C 30 L6-30 9.0
16-6 PM5.2_BF
The following example shows a complete configuration report for a

typical BladeFrame BF200:
# /opt/egenera/bin/showme
Fujitsu Siemens Computers Configuration Report
----------------------------
frame1-c2 (10.10.10.2)
BladeFrame BF200
11-17-05 14:31
-------------------------------------------------------------------------
BLD S/N P/N FW CPU MEM ARCH BMC BIOS
p1 AP2SM1000347 950-000009 47000007R24 2x1.26 2GB IA-32 8.1 1.1
p2 AP2SM1000899 950-000009 47000007R24 2x1.26 2GB IA-32 8.1 1.1
p3 AP6SA3001446 950-000062 47000014R13 2x3.20 2GB IA-32E 8.4 1.7
p4 AP6SA3001418 950-000062 47000014R11 2x3.20 2GB IA-32E 8.4 1.6
p5 AP2SM1000380 950-000009 47000007R24 2x1.26 2GB IA-32 8.1 1.1
p6 AP2SM1000686 950-000009 47000007R24 2x1.26 2GB IA-32 8.1 1.1
c1 CS1CL2000382 950-000032 47000013R05 2x3.06 2GB IA-32 8.1 1.5
c2 CS1CL2000367 950-000032 47000013R05 2x3.06 2GB IA-32 8.1 1.5
ETH DEVICES:
eth0 Intel(R) PRO/100 Network Driver V2.1.29
eth0 Link: Up Speed: 100
eth0 State: Up Media: Copper
eth1 Intel(R) PRO/1000 Network Driver V5.2.30.1

eth2 Intel(R) PRO/1000 Network Driver V5.2.30.1

SCSI ADAPTERS:
scsi3 QLogic PCI to Fibre Channel Host Adapter
scsi3 Firmware: 3.02.24 LoopState: <READY>
scsi3 Driver: 6.07.02e Flags: 0x8e0813
scsi3 WWN: 20000007b101624c
scsi4 QLogic PCI to Fibre Channel Host Adapter

scsi4 Firmware: 3.02.24 LoopState: <READY>
scsi4 Driver: 6.07.02e Flags: 0x8e0813
scsi4 WWN: 21000007b101624c
INSTALLED SOFTWARE:
CD Version: 4.0.0.1-35
Update: 5.0.0.0-10
PM5.2_BF 16-7
Maintenance LPAN
The PAN contains a pre-defined, special-purpose LPAN named

.maint. Administrators use this LPAN to perform certain diagnostic
and maintenance tasks on pBlades, such as updating their firmware.
Maintenance The maintenance LPAN (.maint) has the following features:

LPAN Features
• It appears on PAN Manager’s LPANs page (but not in the list of
LPANs in the left panel).
• It cannot be deleted or renamed.
• Like other LPANs, it can be managed only by its own
administrator or the PAN Administrator.
• You cannot add or remove pBlades from .maint in the usual
way, but only by marking or unmarking them for maintenance
(as described in “Using the Maintenance LPAN” on page 16-8).
• pBlades can “coexist” in .maint and in their original LPANs.
That is, you need not deconfigure a pBlade to place it in the
maintenance LPAN.
• You can configure a local pool in .maint, but this LPAN cannot
access a global pool.
Accessing To connect with the premises network (to access tools on other
External Tools servers), you can create a vSwitch and uplink it to an rEth that has
the appropriate connectivity. Add this vSwitch to the .maint LPAN.
See “Creating vSwitches” on page 3-13.
Using the To use the .maint LPAN, an administrator adds pBlades to it,
Maintenance operates on them as needed, and then restores them to their original
LPAN LPANs. Note the roles required for these steps.
16-8 PM5.2_BF
```To add a pBlade to the maintenance LPAN:
Note: Any LPAN administrator can place pBlades from that LPAN
into the maintenance LPAN.
1. On the LPANs>LPAN_name page or the Resources>Blades
page, click the name of the desired pBlade.
2. On the pBlade_name page, click the Out of Service icon.
• If the pBlade is shut down, it enters the Out of Service state.
• If the pBlade is booted, it enters the Out of Service Pending
state, and becomes Out of Service the next time it is shut
down. Shut it down when convenient.
3. Once the pBlade is Out of Service, click the Maintenance icon.
The pBlade is placed in the maintenance LPAN, and appears as Not

available in its original LPAN. The pBlade remains configured its
original LPAN.
```To remove a pBlade from the maintenance LPAN:
Note: Only the .maint LPAN Administrator or the PAN

Administrator can remove a pBlade from .maint.
1. On the LPANs>LPAN .maint page, select the pBlade to be
removed. Deconfigure it if necessary.
2. On the pBlade_name page, click the Power Off icon.
3. On the pBlade_name page, click the Maintenance icon to
unmark the pBlade for maintenance.
The pBlade becomes available in its previous LPAN with its

previous configuration. It appears in the Shut Down, Out of Service
state.
PM5.2_BF 16-9
Windows pServers
This section describes some troubleshooting procedures that are

specific to pServers running the Windows operating system.
If you encounter a problem with a Windows pServer, diagnose the

problem using the the information provided here on crash dumps,
bug checks, and unresponsive pServers. You can also use consult
the Windows pServer guide for a list of events that may be logged
by the drivers in the virtualization extensions.
If you cannot solve the problem, your support vendor may ask for
the following information:
• The most recent crash dump file. (See “Handling Crash
Dumps” on page 16-10.)
• A save_state file. (See “Saving cBlade State Information” on
page 16-4.)
• A list of the drivers and their version numbers. (See “Displaying
Driver Signatures and Versions” on page 8-14.)
Handling Crash This section explains how to handle crash dumps.

Dumps
Automatic Crash Dumps
If a pServer stops functioning, it generates a crash dump that

preserves valuable information about the pServer operating
conditions just before it stopped. This crash dump information is
copied to a SAN disk and takes the form of a kernel memory dump.
During a crash dump, PAN Manager displays a red ambulance icon

for the pServer Boot Status and a mouse-over tool tip that says
“pServer is taking a crash dump.” See Figure 16.1. As the crash
dump progresses, the pServer console shows the size of the crash
dump file (expressed in MB). See Figure 16.2.
16-10 PM5.2_BF
Figure 16.1 Crash Dump Status Indicator
Figure 16.2 Crash Dump Output
During the crash, PAN Manager records an

IPMI_SEL_PANIC_DUMP event, five subsequent OEM nonsensor
events, and an IPMI_SEL_PANIC_REBOOT event in the PAN
Manager event log. See “Handling Windows Blue Screen
Errors” on page 16-12 for more information.
When the crash dump is complete, the pServer reboots

automatically (default). After the reboot, a pop-up dialog box asks
if you want to send the crash dump to Microsoft for analysis. Click
No, and contact Fujitsu Siemens Computers customer support
instead.
Manual Crash Dumps
If the pServer did not automatically generate a crash dump, you can
manually generate one by issuing the crashdump command in the
SAC console window.
Caution: Generate a crash dump only when it is appropriate.

Although a crash dump can preserve valuable state information
about a pServer, generating a crash dump at an inappropriate time
can damage data on mounted file systems.
PM5.2_BF 16-11
Locating and Naming Crash Dumps
Because each crash dump is saved under the same name

(\%SystemRoot%\Memory.dmp, by default), each new crash dump
overwrites the previous one. To preserve a crash dump, rename it to
a different filename.
If a page file is too small, or you move it off of the system drive,
you cannot recover a dump file.
To change the default name of the crash dump, go to the Advanced

tab of the System control panel, and click Startup and Recovery.
You can edit the Dump File field in the System Failure pane.
Handling This section describes the format of Windows blue screen errors to
Windows Blue help you track down issues with Windows pServers.
Screen Errors
About Blue Screen Errors
When Microsoft Windows encounters a condition that

compromises safe system operation, the system halts. This
condition is called a blue screen or bug check, but it can also be
referred to as a system crash, a kernel error, or a Stop error.
If no debugger is attached, a blue text screen appears with

information about the error. This screen is called a blue screen, a
bug check screen, or a Stop screen.
In the PAN, Windows bug check data is displayed on both the

pServer console (if one is attached) and in the PAN Manager event
log.
16-12 PM5.2_BF
Format of Blue Screen Data
In the pServer console, the Windows blue screen data consists of

the following items:
• Stop code — The hexadecimal number that follows the word
“STOP” is called the Stop code or bug check code. The Stop
code is the most important item on the blue screen.
• Four parameters — Each Stop code has four associated
parameters. The four parameters follow the bug check code on
the first line or are embedded in the explanation below it. In
either case, the parameters always appear sequentially. If fewer
than four parameters appear, the missing parameters have values
of zero.
Note: In some cases, Windows displays only the first line of the
blue screen. This can occur if the error involves vital services
needed for the display.
• Explanation — Each blue screen provides an explanation of
what happened and suggestions for recovery. The blue screen
also indicates whether a crash dump file was written. For more
information on crash dumps, see “Handling Crash Dumps” on
page 16-10.
The exact appearance of a Windows blue screen depends on the

cause of the error. The following example shows a blue screen
where the parameters follow the Stop code, and a crash dump
occurred:
STOP: 0x00000079 (0x00000002, 0x00000001, 0x00000002, 0x00000000)

Mismatched kernel and hal image.
Beginning dump of physical memory
Physical memory dump complete. Contact your system administrator or
technical support group.
The next example shows a blue screen with three parameters

embedded in the explanation and one parameter omitted (with a
value of zero).
STOP: c000021a {Fatal System Error}
PM5.2_BF 16-13
The Windows Logon Process system process terminated unexpectedly with a

status of 0x00000001 (0x00000000 0x00000000).
The system has been shut down.
Format of PAN Manager Events
In PAN Manager, if you click the Events tab on the pServer page,
you can review the event log. Figure 16.3 shows a sample event log
in which a blue screen error with a crash dump occurred.
Figure 16.3 PAN Manager Event Log
In the PAN Manager event log, a blue screen error is recorded as an

IPMI_SEL_PANIC_DUMP event followed by five nonsensor
events. The first nonsensor event contains the Stop code, and the
other four nonsensor events contain the four parameters associated
with the Stop code.
Each nonsensor event has the following format, reading from left to
right:
• Byte 0 (using a 0 base) identifies the parameter number in the
nonsensor event. Parameter 0 is the stop code, parameters 1
through 4 are the parameters associated with the Stop code.
• Byte 1 is a Boolean flag that defines the parameter size in bytes:
• If set to 1, there are 4 bytes (32-bit).
• If set to 0, there are 8 bytes (64-bit).
• Bytes 2 through 5 (32-bit) or Bytes 2 through 9 (64-bit) specify
the value of the parameter, which is read from right to left.
16-14 PM5.2_BF
In Figure 16.3, the first nonsensor event describes parameter 0,

which is the Stop code, as follows:
• Byte 0 is set to 0x00, which specifies parameter 0.
• Byte 1 is set to 0x01, which specifies a 4-byte parameter value
(32-bit).
• Bytes 2 through 5 are set to 0xad:0xde:0xad:0xde, which
reading right to left specify a stop code of 0xdeaddead.
Troubleshooting This section provides a procedure for determining the cause of an

an Unresponsive unresponsive pServer and taking the appropriate corrective action.
pServer
Check the pServer Boot Status
To check the pServer Boot Status (Figure 16.4):

1. Look at the /var/log/messages file on the cBlade to determine
whether SAN or network events have occurred or whether
configurations have changed recently.
2. Use PAN Manager to verify that the pServer is still booted.
3. If the pServer crashed, wait for the crash to complete. (This may
take several minutes.)
4. Set up the Microsoft Windows Debugger to determine the cause
of the crash. To install the Windows Debugger, go to the
following web site and download the debugger and web-based
tutorials: http://www.microsoft.com/whdc/devtools/debugging/
default.mspx.
5. If the pServer is booted, continue with the next procedure, as
Figure 16.5 shows.
PM5.2_BF 16-15
Figure 16.4 Check the pServer Boot Status
pServer is
unresponsive
Have SAN or Network

Correct SAN or events occurred?
Yes
network issue (tail /var/log/messages on
the cBlade)
No
Is the pServer Go to Figure 6.5

pServer OK? No Yes
booted?
Yes No
Wait for crash to

Done
complete
Set up the
Windows Contact the
Debugger to driver
determine which manufacturer
driver crashed
16-16 PM5.2_BF
Check the Up Time
To check the Up Time for a pServer that is booted

(Figure 16.5):
1. Look at the Up Time field at the top of the page.
• If the Up Time field is less than a few minutes, wait for the
pServer reboot to complete.
• If the Up Time field is reasonable, go to Step 1 on
page 16-19.
2. Look at the PAN Manager Events tab for evidence of the
process or event that caused the crash.
3. If the event log indicates that the pServer is in a reboot loop, do
the following:
a. Mount the disk on another pServer.
b. Examine the boot.ini file, and make sure the /bootlog
switch option is present to turn on boot logging to the file
named %SystemRoot%Ntbtlog.txt.
c. Reboot the disk to generate a log file.
d. Collect a recent crash dump, save_state file, boot log, and
list of driver versions.
e. Contact Fujitsu Siemens Computers customer support.
4. If the pServer is not in a reboot loop, do the following:
a. Use the Microsoft Windows Debugger to look for the cause
of the crash.
b. Look for a Stop code in the PAN Manager event log. (For
more information, see “Handling Windows Blue Screen
Errors” on page 16-12.)
c. Look for a crash dump in %SystemRoot%. Collect the crash
dump, a recent save_state file, and a list of driver versions.
d. Contact Fujitsu Siemens Computers customer support.
PM5.2_BF 16-17
Figure 16.5 Check the Up Time
Is the Up Time Go to Figure 6.6

Yes
reasonable?
No
Wait for the reboot

to complete.
Check PAN Set up the Microsoft

Manager and Is the pServer in a Windows Debugger.
No
Windows Event reboot loop? Look for bug check
Logs code and a crash dump.
Yes
Contact Support
Mount the disk on
_______________
another pServer, make
sure that boot logging is
Provide a recent crash
on, and reboot to
dump, save_ state file,
generate a log.
boot log, and list of
driver versions.
16-18 PM5.2_BF
Check the SAC Console
To determine the cause of SAC problems (Figure 16.6):

1. Open a console, and press Enter several times to reach the SAC
prompt.
2. If the SAC responds, do the following:
a. Enter the i command, and verify that the IP addresses of the
pServer, subnet mask, and gateway are correct.
b. Open a command prompt session, and perform basic
network troubleshooting. (For example, ping the gateway
and DNS servers.)
c. If the command prompt does not respond, use PAN Manager
to issue a Non-Maskable Interrupt (NMI), generate a crash
dump, and reboot.
d. Look for a crash dump in %SystemRoot%.
e. Collect the crash dump, a recent save_state file, and a list
of driver versions.
f. Contact Fujitsu Siemens Computers customer support.
3. If there is no response from the SAC console, do the following:
a. Use PAN Manager to issue an NMI, generate a crash dump,
and reboot.
b. Look for a crash dump in %SystemRoot%. If there is no crash
dump and the pServer is hung, power cycle the pBlade.
Power cycling the pBlade does not generate a crash dump.
c. Collect the crash dump (if present after the NMI), a recent
save_state file, and a list of driver versions.
d. Contact Fujitsu Siemens Computers customer support.
PM5.2_BF 16-19
Figure 16.6 Check the SAC Console
Open SAC. Press

Enter several
times.
Send an NMI from Use the i

PAN Manager to Does the SAC command to verify
No Yes
generate a crash respond? that IP addresses
dump and reboot. are valid.
Is there a crash Is there a cmd

dump? prompt?
No Yes
Yes
No
Send an NMI from Perform basic
PAN Manager to network
generate a crash troubleshooting.
Power cycle the (For example, ping
dump and reboot.
pBlade. the gateway and
DNS server.)
Contact Support
_______________
Provide a recent crash

dump (if present),
save_state file, and list
of driver versions.
16-20 PM5.2_BF
Handling Other Sone harmless errors you may encounter include the following:
Types of Errors
• On AMD pBlades, a correctable error on a cBlade causes
Windows to log silent machine check (ECC) errors in the
Windows Event Manager instead of PAN Manager to log events
to the PAN Manager Event Log. These ECC errors are harmless.
• On AMD pBlades, the Windows Device Manager displays a
yellow warning (!) status for System Interrupt Controllers. You
can ignore the yellow warning status; it is harmless.
PM5.2_BF 16-21
Common Problems
This section lists some common probelms you might encounter and
hints for solving them.
Start-up Table 16.3 lists some common start-up problems.

Problems
Table 16.3 Start-up Issues and Hints
Issue Troubleshooting Hints
Cannot connect to the You need to connect to the

PAN Manager IP address PAN Manager IP address through
an SSH or a Telnet session. Check
that your connection is
operational and configured
correctly.
Check that the network is
running.
Check that Tomcat is running.
Cannot log on to PAN Manager Check that you are using the
correct User ID and Password.
16-22 PM5.2_BF
Configuration Table 16.4 lists some common configuration problems.

Problems
Table 16.4 Configuration Issues and Hints
Trouble configuring boot and root The boot and root disk images
disk images provided with the platform are
configured automatically by
PAN Manager.
If you have custom boot or root
disk images, you must configure
the PAN with the list of available
images.
Trouble creating an LPAN You need PAN Administrator

privileges to allocate resources to
an LPAN.
You need LPAN Administrator
privileges to configure the
resources in an LPAN.
You can only configure disks and
pBlades to one LPAN at a time,
unless the pBlade is a member of
a pool.
Trouble creating a pServer You can only create a pServer

after you have created the LPAN
that will contain the pServer.
If you want to use a boot image
that is different from the PAN
default, you must specify it when
creating the pServer.
All the physical and virtual
resources required to configure a
pServer must reside in the same
LPAN as the pServer.
Trouble creating pools You cannot allocate the same

pBlade to a pool and to a pServer.
PM5.2_BF 16-23
Table 16.4 Configuration Issues and Hints (Continued)
Trouble creating a load-balanced The load-balancing pServer must

service be within the same LPAN as the
pServers running the service.
The load-balancing pServer
cannot be running the service
being load balanced.
Administration Table 16.5 lists some common administration and control problems.
and Control
Problems Table 16.5 Administration Issues and Hints
Cannot boot an LPAN When you boot an LPAN for the

first time, you must manually
boot all of the pServers within the
LPAN unless they have been
configured to boot automatically.
Check that the boot order for
pServers within the LPAN is
defined correctly.
Trouble when shutting down an If you get a message similar to the

LPAN following:
Shutting down 5 of 6
pservers
this usually means there is no
agent running on the other two
pServers.
Use the lpan command option -f
to force a shutdown.
16-24 PM5.2_BF
Table 16.5 Administration Issues and Hints (Continued)
Cannot boot a pServer Check that the pServer is

configured with all the correct
boot options.
A pServer must be configured
with a disk with a root partition
before it will boot.
Blade failover is not working Check that there are pBlades still
available in the failover pool.
When a pServer has failed over to
a pBlade in a failover pool, that
pBlade is no longer available to
other pServers in the event of
further failure.
Cannot open a console Check that your Telnet

connection is operational and
configured correctly.
Check that your network is
running.
When opening a console it does If an administrator has opened a

not open at the command line console and changed to a mode
other than the command line (for
example vi) and then another
administrator opens the same
console, the second administrator
will be in the same mode as the
first.
Cannot shut down the platform Usually this is because there is no

agent running. Use the
bframe -s -f option to force a
shutdown.
PM5.2_BF 16-25
16-26 PM5.2_BF
Appendix A
SNMP Traps and Internal
Events Tables
This appendix provides tables with the following information:

• SNMP Traps Mapped to Internal Events
• Internal Event Types and Their Associated SNMP Traps
SNMP Traps Mapped to Internal Events
Table A.1 provides the following information:

• SNMP traps version 1 and SNMP traps version 2 (first column)
• The associated internal event type (second column)
The internal event types appear in the type= field in the /opt/
panmgr/bin/event.log file.
For convenience, the items appear in alphabetical order according

to the items listed in the first column (SNMP Traps Version 1).
PM5.2_BF A-1

Table A.1 SNMP Traps and Associated Internal Event Types
SNMP Traps Version 1

Internal Event Type
applicationConfigWarningTrap config.ha.warning
applicationConfigWarningEvent
applicationCreatedTrap config.lpan.ha.service.created
applicationCreatedEvent
applicationDeletedTrap config.lpan.ha.service.deleted
applicationDeletedEvent
applicationFailedOverTrap status.ha.service.failover.completed
applicationFailedOverEvent
applicationFailingOverTrap status.ha.service.failover.started
applicationFailingOverEvent
applicationFailoverFailedTrap status.ha.service.failover.failed
applicationFailoverFailedEvent
applicationFailoverTrap status.ha.service.hmon.failover
applicationFailoverEvent
applicationFailureDetectedTrap status.ha.service.hmon.failure
applicationFailureDetectedEvent
applicationGiveupTrap status.ha.service.hmon.giveup
applicationGiveupEvent
applicationModifyTrap config.ha.service.config.changed
applicationModifyEvent
applicationMonitorFailedTrap status.ha.monitor.failed
applicationMonitorFailedEvent
applicationMonitorInvalidTrap status.ha.monitor.invalid
applicationMonitorInvalidEvent
A-2 PM5.2_BF
SNMP Traps and Internal Events Tables

Internal Event Type
applicationMonitorRecoveredTrap status.ha.monitor.recovered
applicationMonitorRecoveredEvent
applicationMovedTrap status.ha.service.move.completed
applicationMovedEvent
applicationMoveFailedTrap status.ha.service.move.failed
applicationMoveFailedEvent
applicationMovingTrap status.ha.service.move.started
applicationMovingEvent
applicationRestartedTrap status.ha.service.hmon.restart
applicationRestartedEvent
applicationStartedTrap status.ha.service.start.completed
applicationStartedEvent
applicationStartFailedTrap status.ha.service.start.failed
applicationStartFailedEvent
applicationStartingTrap status.ha.service.start.started
applicationStartingEvent
applicationStatusWarningTrap status.ha.warning
applicationStatusWarningEvent
applicationStopFailedTrap status.ha.service.stop.failed
applicationStopFailedEvent
applicationStoppedTrap status.ha.service.stop.completed
applicationStoppedEvent
applicationStoppingTrap status.ha.service.stop.started
applicationStoppingEvent
bfArchiveCreateTrap config.archive.created
bfArchiveCreateEvent
bfArchiveDeleteTrap config.archive.deleted
bfArchiveDeleteEvent
PM5.2_BF A-3

Internal Event Type
bfArchiveSchedCreateTrap config.archive.schedule.created
bfArchiveSchedCreateEvent
bfArchiveSchedDeleteTrap config.archive.schedule.deleted
bfArchiveSchedDeleteEvent
bfArchiveSchedFailedTrap status.archive.schedule.failure
bfArchiveSchedFailedEvent
bfArchiveSchedModifiedTrap config.archive.schedule.modified
bfArchiveSchedModifiedEvent
bfArchiveSchedRunningTrap status.archive.schedule.run
bfArchiveSchedRunningEvent
bfPANManagerDowntimeTrap status.pan.manager.downtime.report
bfPANManagerDowntimeEvent
bfRccExpiredFilesDeletedTrap status.rcc.expired.files.deleted
bfRccExpiredFilesDeletedEvent
bfRccReportPeriodEndTrap status.rcc.period.end
bfRccReportPeriodEndEvent
bfRccReportPeriodStartTrap status.rcc.period.begin
bfRccReportPeriodStartEvent
platformDeviceIdMismatchTrap status.devicemanager.device.mismatch
platformDeviceIdMismatchEvent
platformMasterRecoveredTrap config.frame.master.recovered
platformMasterRecoveredEvent
platformPowerDeniedTrap status.frame.power.consumption.powerdeni
ed
platformPowerDeniedEvent
platformPowerOverCommitTrap status.frame.power.consumption.overattac
hed
platformPowerOverCommitEvent
platformPowerOverDrawTrap status.frame.power.consumption.overpower
ed
platformPowerOverDrawEvent
A-4 PM5.2_BF

Internal Event Type
platformREthMisconfigTrap status.devicemanager.eth.mismatch
platformREthMisconfigEvent
cBladeCDROMIOAvailableTrap config.devicemanager.device.io.available
cBladeCDROMIOAvailableEvent
cBladeCDROMIOUnavailableTrap config.devicemanager.device.io.unavailab
le
cBladeCDROMIOUnavailableEvent
cBladeCmdHaltTrap ipmi.event (with IPMI_SEL_CMD_HALT in

eud= field)
cBladeCmdHaltEvent
cBladeCmdRebootTrap status.blade.rebooting
cBladeCmdRebootEvent
cBladeDeselectedTrap status.blade.selected
cBladeDeselectedEvent
cBladeDisabledTrap status.blade.out.of.service
cBladeDisabledEvent
cBladeDiskIOAvailableTrap config.devicemanager.device.io.available
cBladeDiskIOAvailableEvent
cBladeDiskIOUnavailableTrap config.devicemanager.device.io.unavailab
le
cBladeDiskIOUnavailableEvent
cBladeEnabledTrap status.blade.in.service
cBladeEnabledEvent
cBladeEthIOAvailableTrap config.devicemanager.device.io.available
cBladeEthIOAvailableEvent
cBladeEthIOUnavailableTrap config.devicemanager.device.io.unavailab
le
cBladeEthIOUnavailableEvent
cBladeEthLinkDownTrap status.eth.link.down
cBladeEthLinkDownEvent
cBladeEthLinkUpTrap status.eth.link.up
cBladeEthLinkUpEvent
PM5.2_BF A-5

Internal Event Type
cBladeEthStatusActiveTrap status.eth.reth.active
cBladeEthStatusActiveEvent
cBladeEthStatusStandbyTrap status.eth.reth.standby
cBladeEthStatusStandbyEvent
cBladeEthStatusFailedTrap status.eth.reth.failed
cBladeEthStatusFailedEvent
cBladeEthStatusUnconfiguredTrap status.eth.reth.unconfigured
cBladeEthStatusUnconfiguredEvent
cBladeFailureTrap status.pan.manager.failed
cBladeFailureEvent
cBladeFanSpeedLowerTrap status.ipmi.fan.low.critical
cBladeFanSpeedLowerEvent
cBladeFanSpeedUpperTrap status.ipmi.fan.high.critical
cBladeFanSpeedUpperEvent
cBladeFatalHwErrorTrap status.ipmi.fatal.hardware.event
cBladeFatalHwErrorEvent
cBladeHbaDisabledTrap status.hba.disable
cBladeHbaDisabledEvent
cBladeHbaEnabledTrap status.hba.enable.info
cBladeHbaEnabledEvent
cBladeHbaStatusChangedTrap status.hba.change.info
cBladeHbaStatusChangedEvent
cBladeHbaStatusDownTrap status.hba.down
cBladeHbaStatusDownEvent
cBladeHwEventTrap status.ipmi.event
cBladeHwEvent
cBladeInitTrap status.blade.runlevel
cBladeInitEvent
A-6 PM5.2_BF

Internal Event Type
cBladeInsertedTrap config.frame.blade.inserted
cBladeInsertedEvent
cBladeMasterFailoverTrap status.pan.manager.failed.over
cBladeMasterFailoverEvent
cBladeMasterTrap status.pan.manager.started
cBladeMasterEvent
cBladeNMIOpTrap status.blade.operation
cBladeNMIOpEvent
cBladeNonFatalHwErrorTrap status.ipmi.nonfatal.hardware.event
cBladeNonFatalHwErrorEvent
cBladeNonUniqueDiskIdTrap config.devicemanager.device.duplicateID
cBladeNonUniqueDiskIdEvent
cBladeOutOfServicePendingTrap status.blade.out.of.service.pending
cBladeOutOfServicePendingEvent
cBladePanicTrap status.blade.panic
cBladePanicEvent
cBladePanManagerStartedTrap status.pan.manager.started
cBladePanManagerStartedEvent
cBladePedDeadlockTrap cblade.system.message.ped.deadlock
cBladePedDeadlockEvent
cBladePedErrorTrap cblade.system.message.ped.error
cBladePedErrorEvent
cBladePedFabricTrap cblade.system.message.ped.fabric
cBladePedFabricEvent
cBladePedLegacyTrap cblade.system.message.ped.legacy
cBladePedLegacyEvent
cBladePedNodeTrap cblade.system.message.ped.node
cBladePedNodeEvent
PM5.2_BF A-7

Internal Event Type
cBladePedOtherTrap cblade.system.message.ped.other
cBladePedOtherEvent
cBladePedPathErrorTrap cblade.system.message.ped.patherror
cBladePedPathErrorEvent
cBladePedSerialBitTrap cblade.system.message.ped.serialbit
cBladePedSerialBitEvent
cBladePedSwitchTrap cblade.system.message.ped.switch
cBladePedSwitchEvent
cBladePowerCycleOpTrap status.blade.operation
cBladePowerCycleOpEvent
cBladePowerOffOpTrap status.blade.operation
cBladePowerOffOpEvent
cBladePowerOffTrap status.power.event
cBladePowerOffEvent
cBladePowerOnOpTrap status.blade.operation
cBladePowerOnOpEvent
cBladePowerOnTrap status.power.event
cBladePowerOnEvent
cBladeRemovedTrap config.frame.blade.ejected
cBladeRemovedEvent
cBladeResetOpTrap status.blade.operation
cBladeResetOpEvent
cBladeSelectedTrap status.blade.selected
cBladeSelectedEvent
cBladeSlaveTrap status.pan.manager.started
cBladeSlaveEvent
cBladeStonithTrap status.pan.manager.stonithed
cBladeStonithEvent
A-8 PM5.2_BF

Internal Event Type
cBladeSyslogDroppedTrap status.cblade.sys.msg.dropped
cBladeSyslogDroppedEvent
cBladeSyslogEventTrap status.cblade.sys.msg.1
cBladeSyslogEvent to
status.cblade.sys.msg.10
cBladeSyslogPollingStoppedTrap status.cblade.sys.msg.stopped
cBladeSyslogPollingStoppedEvent
cBladeSystemThresholdHighTrap status.system.threshold.high
cBladeSystemThresholdHighEvent
cBladeTempLowerTrap status.ipmi.temp.low.critical
cBladeTempLowerEvent
cBladeTempUpperTrap status.ipmi.temp.high.critical
cBladeTempUpperEvent
cBladeVoltageLowerTrap status.ipmi.voltage.low.critical
cBladeVoltageLowerEvent
cBladeVoltageUpperTrap status.ipmi.voltage.high.critical
cBladeVoltageUpperEvent
diskPartitionedTrap status.disk.partitioned
diskPartitionedEvent
diskRootedTrap status.disk.rooted
diskRootedEvent
diskWinPeTrap status.disk.winpe
diskWinPeEvent
executableResourceConfigWarningTrap config.ha.warning
executableResourceConfigWarningEvent
executableResourceCreateTrap config.lpan.ha.resource.created
executableResourceCreateEvent
executableResourceDeleteTrap config.lpan.ha.resource.deleted
executableResourceDeleteEvent
PM5.2_BF A-9

Internal Event Type
executableResourceModifyTrap config.ha.resource.config.changed
executableResourceModifyEvent
failoverPolicyConfigWarningTrap config.ha.warning
failoverPolicyConfigWarningEvent
failoverPolicyCreateTrap config.lpan.ha.resource.created
failoverPolicyCreateEvent
failoverPolicyDeleteTrap config.lpan.ha.resource.deleted
failoverPolicyDeleteEvent
failoverPolicyModifyTrap config.ha.resource.config.changed
failoverPolicyModifyEvent
globalPoolCreatedTrap config.lpanmanager.pool.created
globalPoolCreatedEvent
globalPoolDeletedTrap config.lpanmanager.deleted
globalPoolDeletedEvent
healthMonitorConfigWarningTrap config.ha.warning
healthMonitorConfigWarningEvent
healthMonitorCreateTrap config.lpan.ha.resource.created
healthMonitorCreateEvent
healthMonitorDeleteTrap config.lpan.ha.resource.deleted
healthMonitorDeleteEvent
healthMonitorModifyTrap config.ha.resource.config.changed
healthMonitorModifyEvent
loadBalancerConfigWarningTrap config.ha.warning
loadBalancerConfigWarningEvent
loadBalancerCreatedTrap config.lpan.ha.service.created
loadBalancerCreatedEvent
loadBalancerDeletedTrap config.lpan.ha.service.deleted
loadBalancerDeletedEvent
A-10 PM5.2_BF

Internal Event Type
loadBalancerFailedOverTrap status.ha.service.failover.completed
loadBalancerFailedOverEvent
loadBalancerFailingOverTrap status.ha.service.failover.started
loadBalancerFailingOverEvent
loadBalancerFailoverFailedTrap status.ha.service.failover.failed
loadBalancerFailoverFailedEvent
loadBalancerFailoverTrap status.ha.service.hmon.failover
loadBalancerFailoverEvent
loadBalancerFailureDetectedTrap status.ha.service.hmon.failure
loadBalancerFailureDetectedEvent
loadBalancerGiveupTrap status.ha.service.hmon.giveup
loadBalancerGiveupEvent
loadBalancerModifyTrap config.ha.service.config.changed
loadBalancerModifyEvent
loadBalancerMonitorFailedTrap status.ha.monitor.failed
loadBalancerMonitorFailedEvent
loadBalancerMonitorInvalidTrap status.ha.monitor.invalid
loadBalancerMonitorInvalidEvent
loadBalancerMonitorRecoveredTrap status.ha.monitor.recovered
lbMonitorRecoveredEvent
loadBalancerMovedTrap status.ha.service.move.completed
loadBalancerMovedEvent
loadBalancerMoveFailedTrap status.ha.service.move.failed
loadBalancerMoveFailedEvent
loadBalancerMovingTrap status.ha.service.move.started
loadBalancerMovingEvent
loadBalancerRestartedTrap status.ha.service.hmon.restart
loadBalancerRestartedEvent
PM5.2_BF A-11

Internal Event Type
loadBalancerStartedTrap status.ha.service.start.completed
loadBalancerStartedEvent
loadBalancerStartFailedTrap status.ha.service.start.failed
loadBalancerStartFailedEvent
loadBalancerStartingTrap status.ha.service.start.started
loadBalancerStartingEvent
loadBalancerStatusWarningTrap status.ha.warning
loadBalancerStatusWarningEvent
loadBalancerStopFailedTrap status.ha.service.stop.failed
loadBalancerStopFailedEvent
loadBalancerStoppedTrap status.ha.service.stop.completed
loadBalancerStoppedEvent
loadBalancerStoppingTrap status.ha.service.stop.started
loadBalancerStoppingEvent
localPoolCreatedTrap config.lpan.pool.created
localPoolCreatedEvent
localPoolDeletedTrap config.lpan.pool.deleted
localPoolDeletedEvent
lPanActivatedTrap status.lpan.activated
lPanActivatedEvent
lPanCreatedTrap config.lpanmanager.lpan.created
lPanCreatedEvent
lPanDeactivatedTrap status.lpan.deactivated
lPanDeactivatedEvent
lPanDeletedTrap config.lpanmanager.lpan.deleted
lPanDeletedEvent
lPanDeviceAvailableTrap config.lpan.device.arrived
lPanDeviceAvailableEvent
A-12 PM5.2_BF

Internal Event Type
lPanDeviceUnavailableTrap config.lpan.device.departed
lPanDeviceUnavailableEvent
lPanModifyTrap config.lpan.config.changed
lPanModifyEvent
lPanOperationAbortedTrap status.lpan.operation.aborted
lPanOperationAbortedEvent
lPanOperationCompletedTrap status.lpan.operation.completed
lPanOperationCompletedEvent
lPanOperationStartedTrap status.lpan.operation.started
lPanOperationStartedEvent
lPanPBladeAllocatedTrap config.blade.allocated
lPanPBladeAllocatedEvent
lPanPBladeAvailableTrap config.lpan.blade.arrived
lPanPBladeAvailableEvent
lPanPBladeDeallocatedTrap config.blade.deallocated
lPanPBladeDeallocatedEvent
lPanPBladeUnavailableTrap config.lpan.blade.departed
lPanPBladeUnavailableEvent
lPanUserMonitorCreatedTrap config.lpan.monitor.created
lPanUserMonitorCreatedEvent
lPanUserMonitorDeletedTrap config.lpan.monitor.deleted
lPanUserMonitorDeletedEvent
lPanUserMonitorModifiedTrap config.lpan.monitor.modified
lPanUserMonitorModifiedEvent
networkResourceConfigWarningTrap config.ha.warning
networkResourceConfigWarningEvent
networkResourceCreateTrap config.lpan.ha.resource.created
networkResourceCreateEvent
PM5.2_BF A-13

Internal Event Type
networkResourceDeleteTrap config.lpan.ha.resource.deleted
networkResourceDeleteEvent
networkResourceModifyTrap config.ha.resource.config.changed
networkResourceModifyEvent
nfsResourceConfigWarningTrap config.ha.warning
nfsResourceConfigWarningEvent
nfsResourceCreateTrap config.lpan.ha.resource.created
nfsResourceCreateEvent
nfsResourceDeleteTrap config.lpan.ha.resource.deleted
nfsResourceDeleteEvent
nfsResourceModifyTrap config.ha.resource.config.changed
nfsResourceModifyEvent
pBladeBootImageChangedTrap status.blade.boot.image.changed
pBladeBootImageChangedEvent
pBladeCmdHaltTrap status.blade.shuttingdown
pBladeCmdHaltEvent
pBladeCmdRebootTrap status.blade.rebooting
pBladeCmdRebootEvent
pBladeDeselectedTrap status.blade.selected
pBladeDeselectedEvent
pBladeDisabledTrap status.blade.out.of.service
pBladeDisabledEvent
pBladeEnabledTrap status.blade.in.service
pBladeEnabledEvent
pBladeFanSpeedLowerTrap status.ipmi.fan.low.critical
pBladeFanSpeedLowerEvent
pBladeFanSpeedUpperTrap status.ipmi.fan.high.critical
pBladeFanSpeedUpperEvent
A-14 PM5.2_BF

Internal Event Type
pBladeFatalHwErrorTrap status.ipmi.fatal.hardware.event
pBladeFatalHwErrorEvent
pBladeHwErrorThresholdTrap status.ipmi.hw.error.threshold.event
pBladeHwErrorThresholdEvent
pBladeHwEventTrap status.ipmi.event
pBladeHwEvent
pBladeInitTrap status.blade.runlevel
pBladeInitEvent
pBladeInsertedTrap config.frame.blade.inserted
pBladeInsertedEvent
pBladeIpmiCeccThresholdTrap status.ipmi.cecc.threshold.event
pBladeIpmiCeccThresholdEvent
pBladeNMIOpTrap status.blade.operation
pBladeNMIOpEvent
pBladeNonFatalHwErrorTrap status.ipmi.nonfatal.hardware.event
pBladeNonFatalHwErrorEvent
pBladeOutOfServicePendingTrap status.blade.out.of.service.pending
pBladeOutOfServicePendingEvent
pBladePanicTrap status.blade.panic
pBladePanicEvent
pBladePowerCycleOpTrap status.blade.operation
pBladePowerCycleOpEvent
pBladePowerOffOpTrap status.blade.operation
pBladePowerOffOpEvent
pBladePowerOffTrap status.power.event
pBladePowerOffEvent
pBladePowerOnOpTrap status.blade.operation
pBladePowerOnOpEvent
PM5.2_BF A-15

Internal Event Type
pBladePowerOnTrap status.power.event
pBladePowerOnEvent
pBladeRemovedTrap config.frame.blade.ejected
pBladeRemovedEvent
pBladeResetOpTrap status.blade.operation
pBladeResetOpEvent
pBladeSelectedTrap status.blade.selected
pBladeSelectedEvent
pBladeTempLowerTrap status.ipmi.temp.low.critical
pBladeTempLowerEvent
pBladeTempUpperTrap status.ipmi.temp.high.critical
pBladeTempUpperEvent
pBladeVbladeRamOvercommitTrap status.blade.vblade.ram.overcommit.event
pBladeVbladeRamOvercommitEvent
pBladeVoltageLowerTrap status.ipmi.voltage.low.critical
pBladeVoltageLowerEvent
pBladeVoltageUpperTrap status.ipmi.voltage.high.critical
pBladeVoltageUpperEvent
pBladeWinkoutTrap status.blade.winkout
pBladeWinkoutEvent
poolConfigChangedTrap config.pool.config.changed
poolConfigChangedEvent
pimConfigErrorTrap config.pim.error
pimConfigErrorEven
poolPBladeArrivedTrap status.pool.blade.arrive
poolPBladeArrivedEvent
poolPBladeDepartedTrap status.pool.blade.departed
poolPBladeDepartedEvent
A-16 PM5.2_BF

Internal Event Type
pServerAgentArrivedTrap status.pserver.agent.available
pServerAgentArrivedEvent
pServerAgentDepartedTrap status.pserver.agent.unavailable
pServerAgentDepartedEvent
pServerBootedTrap status.pserver.boot.succeeded
pServerBootedEvent
pServerBootFailedTrap status.pserver.boot.failed
pServerBootFailedEvent
pServerBootingTrap status.pserver.boot.started
pServerBootingEvent
pServerCreatedTrap config.lpan.pserver.created
pServerCreatedEvent
pServerDeletedTrap config.lpan.pserver.deleted
pServerDeletedEvent
pServerDiskAvailableTrap status.pserver.disk.available
pServerDiskAvailableEvent
pServerDiskUnavailableTrap status.pserver.disk.unavailable
pServerDiskUnavailableEvent
pServerFailedTrap status.pserver.failed
pServerFailedEvent
pServerFailoverTrap status.pserver.failover.started
pServerFailoverEvent
pServerHardwareOfflineTrap status.pserver.hardware.offline
pServerHardwareOfflineEvent
pServerHardwareOnlineTrap status.pserver.hardware.online
pServerHardwareOnlineEvent
pServerMigratedTrap status.pserver.migrate.succeeded
pServerMigratedEvent
PM5.2_BF A-17

Internal Event Type
pServerMigrateFailedTrap status.pserver.migrate.failed
pServerMigrateFailedEvent
pServerMigratingTrap status.pserver.migrate.started
pServerMigratingEvent
pServerModifiedTrap config.pserver.config.changed
pServerModifiedEvent
pServerOperationStartedTrap status.pserver.operation.started
pServerOperationStartedEvent
pServerPanicCycleTrap status.pserver.panic.cycle
pServerPanicCycleEvent
pServerPBladeAllocatedTrap config.blade.allocated
pServerPBladeAllocatedEvent
pServerPBladeAvailableTrap status.pserver.pblade.available
pServerPBladeAvailableEvent
pServerPBladeDeallocatedTrap config.blade.deallocated
pServerPBladeDeallocatedEvent
pServerRebootingTrap status.pserver.reboot.started
pServerRebootingEvent
pServerRecoveredTrap status.pserver.recovered
pServerRecoveredEvent
pServerRecoverTrap status.pserver.recovered
pServerRecoverEvent
pServerResourceUnavailableTrap pserver.resource.unavailable.event
pServerResourceUnavailableEvent
pServerResumedTrap status.pserver.resume.completed
pServerResumedEvent
pServerResumeFailedTrap status.pserver.resume.failed
pServerResumeFailedEvent
A-18 PM5.2_BF

Internal Event Type
pServerResumingTrap status.pserver.resume.started
pServerResumingEvent
pServerShutdownFailedTrap status.pserver.shutdown.failed
pServerShutdownFailedEvent
pServerShutdownTrap status.pserver.shutdown.completed
pServerShutdownEvent
pServerShuttingDownTrap status.pserver.shutdown.started
pServerShuttingDownEvent
pServerSuspendedTrap status.pserver.suspend.completed
pServerSuspendedEvent
pServerSuspendFailedTrap status.pserver.suspend.failed
pServerSuspendFailedEvent
pServerSuspendingTrap status.pserver.suspend.started
pServerSuspendingEvent
pServerSyslogDroppedTrap status.pserver.sys.msg.dropped
pServerSyslogDroppedEvent
pServerSyslogEventTrap status.pserver.sys.msg.1 to
status.pserver.sys.msg.10
pServerSyslogEvent
pServerSyslogPollingStoppedTrap status.pserver.sys.msg.stopped
pServerSyslogPollingStoppedEvent
pServerSystemThresholdHighTrap status.system.threshold.high
pServerSystemThresholdHighEvent
pServerSystemThresholdlowTrap status.system.threshold.low
pServerSystemThresholdlowEvent
pServerUserMonitorTrap status.user.monitor.event
pServerUserMonitorEvent
rethStatusRedundantTrap status.reth.state.redundant
rethStatusRedundantEvent
PM5.2_BF A-19

Internal Event Type
rethStatusNotRedundantTrap status.reth.state.notredundant
rethStatusNotRedundantEvent
rethStatusDegradedTrap status.reth.state.degraded
rethStatusDegradedEvent
rethStatusFailedTrap status.reth.state.failed
rethStatusFailedEvent
sBladeDeselectedTrap status.blade.selected
sBladeDeselectedEvent
sBladeDisabledTrap status.blade.out.of.service
sBladeDisabledEvent
sBladeEnabledTrap status.blade.in.service
sBladeEnabledEvent
sBladeFanSpeedLowerTrap status.ipmi.fan.low.critical
sBladeFanSpeedLowerEvent
sBladeFanSpeedUpperTrap status.ipmi.fan.high.critical
sBladeFanSpeedUpperEvent
sBladeFatalHwErrorTrap status.ipmi.fatal.hardware.event
sBladeFatalHwErrorEvent
sBladeHwEventTrap status.ipmi.event
sBladeHwEvent
sBladeInsertedTrap config.frame.blade.inserted
sBladeInsertedEvent
sBladeNonFatalHwErrorTrap status.ipmi.nonfatal.hardware.event
sBladeNonFatalHwErrorEvent
sBladeOutOfServicePendingTrap status.blade.out.of.service.pending
sBladeOutOfServicePendingEvent
sBladePowerCycleOpTrap status.blade.operation
sBladePowerCycleOpEvent
A-20 PM5.2_BF

Internal Event Type
sBladePowerOffOpTrap status.blade.operation
sBladePowerOffOpEvent
sBladePowerOffTrap status.power.event
sBladePowerOffEvent
sBladePowerOnOpTrap status.power.event
sBladePowerOnOpEvent
sBladePowerOnTrap status.power.event
sBladePowerOnEvent
sBladeRemovedTrap config.frame.blade.ejected
sBladeRemovedEvent
sBladeResetOpTrap status.blade.operation
sBladeResetOpEvent
sBladeSelectedTrap status.blade.selected
sBladeSelectedEvent
sBladeTempLowerTrap status.ipmi.temp.low.critical
sBladeTempLowerEvent
sBladeTempUpperTrap status.ipmi.temp.high.critical
sBladeTempUpperEvent
sBladeVoltageLowerTrap status.ipmi.voltage.low.critical
sBladeVoltageLowerEvent
sBladeVoltageUpperTrap status.ipmi.voltage.high.critical
sBladeVoltageUpperEvent
scsiDiskResourceConfigWarningTrap config.ha.warning
scsiDiskResourceConfigWarningEvent
scsiDiskResourceCreateTrap config.lpan.ha.resource.created
scsiDiskResourceCreateEvent
scsiDiskResourceDeleteTrap config.lpan.ha.resource.deleted
scsiDiskResourceDeleteEvent
PM5.2_BF A-21

Internal Event Type
scsiDiskResourceModifyTrap config.ha.resource.config.changed
scsiDiskResourceModifyEvent
userCreatedTrap config.user.added
userCreatedEvent
userDeletedTrap config.user.deleted
userDeletedEvent
userModifiedTrap config.user.modified
userModifiedEvent
A-22 PM5.2_BF
Internal Event Types and Their Associated SNMP

Traps
Table A.2 provides the following information:

• Internal event type (first column)
• Associated SNMP trap version 1 and SNMP trap version 2
(second column)
The internal event type (when generated) appears in the type= field
in the /opt/panmgr/bin/event.log file.
For convenience, the items appear in alphabetical order according

to the items listed in the first column (Internal Event Type).

Table A.2 Internal Event Types and Associated SNMP Traps
Internal Event Type SNMP Traps Version 1

cblade.system.message.ped.deadlock cBladePedDeadlockTrap
cBladePedDeadlockEvent
cblade.system.message.ped.error cBladePedErrorTrap
cBladePedErrorEvent
cblade.system.message.ped.fabric cBladePedFabricTrap
cBladePedFabricEvent
cblade.system.message.ped.legacy cBladePedLegacyTrap
cBladePedLegacyEvent
cblade.system.message.ped.node cBladePedNodeTrap
cBladePedNodeEvent
PM5.2_BF A-23

Internal Event Type
cblade.system.message.ped.other cBladePedOtherTrap
cBladePedOtherEvent
cblade.system.message.ped.patherror cBladePedPathErrorTrap
cBladePedPathErrorEvent
cblade.system.message.ped.serialbit cBladePedSerialBitTrap
cBladePedSerialBitEvent
cblade.system.message.ped.switch cBladePedSwitchTrap
cBladePedSwitchEvent
config.archive.created bfArchiveCreateTrap
bfArchiveCreateEvent
config.archive.deleted bfArchiveDeleteTrap
config.archive.schedule.created bfArchiveSchedCreateTrap
bfArchiveSchedCreateEvent
config.archive.schedule.deleted bfArchiveSchedDeleteTrap
bfArchiveSchedDeleteEvent
config.archive.schedule.modified bfArchiveSchedModifiedTrap
bfArchiveSchedModifiedEvent
config.blade.allocated lPanPBladeAllocatedTrap
pServerPBladeAllocatedTrap
lPanPBladeAllocatedEvent
pServerPBladeAllocatedEvent
config.blade.deallocated lPanPBladeDeallocatedTrap
lPanPBladeDeallocatedEvent
pServerPBladeDeallocatedTrap
pServerPBladeDeallocatedEvent
config.devicemanager.device.duplicateID cBladeNonUniqueDiskIdTrap
cBladeNonUniqueDiskIdEvent
A-24 PM5.2_BF

Internal Event Type
config.devicemanager.device.io.available cBladeCDROMIOAvailableTrap
cBladeCDROMIOAvailableEvent
cBladeDiskIOAvailableTrap
cBladeDiskIOAvailableEvent
cBladeEthIOAvailableTrap
cBladeEthIOAvailableEvent
config.devicemanager.device.io.unavailab cBladeCDROMIOUnavailableTrap
le
cBladeCDROMIOUnavailableEvent
cBladeDiskIOUnavailableTrap
cBladeDiskIOUnavailableEvent
cBladeEthIOUnavailableTrap
cBladeEthIOUnavailableEvent
config.frame.blade.ejected cBladeRemovedTrap
cBladeRemovedEvent
pBladeRemovedTrap
pBladeRemovedEvent
sBladeRemovedTrap
sBladeRemovedEvent
config.frame.blade.inserted cBladeInsertedTrap
cBladeInsertedEvent
pBladeInsertedTrap
pBladeInsertedEvent
sBladeInsertedTrap
sBladeInsertedEvent
config.frame.master.recovered platformMasterRecoveredTrap
platformMasterRecoveredEvent
PM5.2_BF A-25

Internal Event Type
config.ha.resource.config.changed executableResourceModifyTrap
executableResourceModifyEvent
failoverPolicyModifyTrap
failoverPolicyModifyEvent
healthMonitorModifyTrap
healthMonitorModifyEvent
networkResourceModifyTrap
networkResourceModifyEvent
nfsResourceModifyTrap
nfsResourceModifyEvent
scsiDiskResourceModifyTrap
scsiDiskResourceModifyEvent
config.ha.service.config.changed applicationModifyTrap
applicationModifyEvent
loadBalancerModifyTrap
loadBalancerModifyEvent
applicationMonitorRecoveredTrap
applicationMonitorRecoveredEvent
loadBalancerMonitorRecoveredTrap
lbMonitorRecoveredEvent
applicationStartFailedTrap
applicationStartFailedEvent
loadBalancerStartFailedTrap
loadBalancerStartFailedEvent
applicationStartingTrap
applicationStartingEvent
loadBalancerStartingTrap
loadBalancerStartingEvent
A-26 PM5.2_BF

Internal Event Type
config.ha.warning applicationConfigWarningTrap
applicationConfigWarningEvent
executableResourceConfigWarningTrap
executableResourceConfigWarningEvent
failoverPolicyConfigWarningTrap
failoverPolicyConfigWarningEvent
healthMonitorConfigWarningTrap
healthMonitorConfigWarningEvent
loadBalancerConfigWarningTrap
loadBalancerConfigWarningEvent
networkResourceConfigWarningTrap
networkResourceConfigWarningEvent
nfsResourceConfigWarningTrap
nfsResourceConfigWarningEvent
scsiDiskResourceConfigWarningTrap
scsiDiskResourceConfigWarningEvent
config.lpan.blade.arrived lPanPBladeAvailableTrap
lPanPBladeAvailableEvent
config.lpan.blade.departed lPanPBladeUnavailableTrap
lPanPBladeUnavailableEvent
config.lpan.config.changed lPanModifyTrap
lPanModifyEvent
config.lpan.device.arrived lPanDeviceAvailableTrap
lPanDeviceAvailableEvent
config.lpan.device.departed lPanDeviceUnavailableTrap
lPanDeviceUnavailableEvent
PM5.2_BF A-27

Internal Event Type
config.lpan.ha.resource.created executableResourceCreateTrap
executableResourceCreateEvent
failoverPolicyCreateTrap
failoverPolicyCreateEvent
healthMonitorCreateTrap
healthMonitorCreateEvent
networkResourceCreateTrap
networkResourceCreateTrap
nfsResourceCreateTrap
nfsResourceCreateEvent
scsiDiskResourceCreateTrap
scsiDiskResourceCreateEvent
config.lpan.ha.resource.deleted executableResourceDeleteTrap
executableResourceDeleteEvent
failoverPolicyDeleteTrap
failoverPolicyDeleteEvent
healthMonitorDeleteTrap
healthMonitorDeleteEvent
networkResourceDeleteTrap
networkResourceDeleteEvent
nfsResourceDeleteTrap
nfsResourceDeleteEvent
config.lpan.ha.resource.deleted scsiDiskResourceDeleteTrap
scsiDiskResourceDeleteEvent
config.lpan.ha.service.created applicationCreatedTrap
applicationCreatedEvent
loadBalancerCreatedTrap
loadBalancerCreatedEvent
A-28 PM5.2_BF

Internal Event Type
config.lpan.ha.service.deleted applicationDeletedTrap
applicationDeletedEvent
loadBalancerDeletedTrap
loadBalancerDeletedEvent
config.lpan.monitor.created lPanUserMonitorCreatedTrap
lPanUserMonitorCreatedEvent
config.lpan.monitor.deleted lPanUserMonitorDeletedTrap
lPanUserMonitorDeletedEvent
config.lpan.monitor.modified lPanUserMonitorModifiedTrap
lPanUserMonitorModifiedEvent
config.lpan.pool.created localPoolCreatedTrap
localPoolCreatedEvent
config.lpan.pool.deleted localPoolDeletedTrap
localPoolDeletedEvent
config.lpan.pserver.created pServerCreatedTrap
pServerCreatedEvent
config.lpan.pserver.deleted pServerDeletedTrap
pServerDeletedEvent
config.lpanmanager.lpan.created lPanCreatedTrap
lPanCreatedEvent
config.lpanmanager.lpan.deleted lPanDeletedTrap
lPanDeletedEvent
config.lpanmanager.pool.created globalPoolCreatedTrap
globalPoolCreatedEvent
config.lpanmanager.pool.deleted globalPoolDeletedTrap
globalPoolDeletedEvent
config.pim.error pimConfigErrorTrap
pimConfigErrorEvent
PM5.2_BF A-29

Internal Event Type
config.pool.config.changed poolConfigChangedTrap
poolConfigChangedEvent
config.pserver.config.changed pServerModifiedTrap
pServerModifiedEvent
config.user.added userCreatedTrap
userCreatedEvent
config.user.deleted userDeletedTrap
userDeletedEvent
config.user.modified userModifiedTrap
userModifiedEvent
ipmi.event (with IPMI_SEL_CMD_HALT in cBladeCmdHaltTrap

eud= field)
cBladeCmdHaltEvent
pserver.resource.unavailable.event pServerResourceUnavailableTrap
pServerResourceUnavailableEvent
status.archive.schedule.failure bfArchiveSchedFailedTrap
bfArchiveSchedFailedEvent
status.archive.schedule.run bfArchiveSchedRunningTrap
bfArchiveSchedRunningEvent
status.blade.boot.image.changed pBladeBootImageChangedTrap
pBladeBootImageChangedEvent
status.blade.in.service cBladeEnabledTrap
cBladeEnabledEvent
pBladeEnabledTrap
pBladeEnabledEvent
sBladeEnabledTrap
sBladeEnabledEvent
A-30 PM5.2_BF

Internal Event Type
status.blade.operation cBladeNMIOpTrap
cBladeNMIOpEvent
cBladePowerCycleOpTrap
cBladePowerCycleOpEvent
pBladePowerCycleOpTrap
pBladePowerCycleOpEvent
sBladePowerCycleOpTrap
sBladePowerCycleOpEvent
cBladePowerOffOpTrap
cBladePowerOffOpEvent
pBladePowerOffOpTrap
pBladePowerOffOpEvent
sBladePowerOffOpTrap
sBladePowerOffOpEvent
cBladePowerOnOpTrap
cBladePowerOnOpEvent
pBladePowerOnOpTrap
pBladePowerOnOpEvent
sBladePowerOnOpTrap
sBladePowerOnOpEvent
cBladeResetOpTrap
cBladeResetOpEvent
pBladeResetOpTrap
pBladeResetOpEvent
sBladeResetOpTrap
sBladeResetOpEvent
pBladeNMIOpTrap
pBladeNMIOpEvent
PM5.2_BF A-31

Internal Event Type
status.blade.out.of.service cBladeDisabledTrap
cBladeDisabledEvent
pBladeDisabledTrap
pBladeDisabledEvent
sBladeDisabledTrap
sBladeDisabledEvent
status.blade.out.of.service.pending cBladeOutOfServicePendingTrap
cBladeOutOfServicePendingEvent
pBladeOutOfServicePendingTrap
pBladeOutOfServicePendingEvent
sBladeOutOfServicePendingTrap
sBladeOutOfServicePendingEvent
status.blade.panic cBladePanicTrap
cBladePanicEvent
pBladePanicTrap
pBladePanicEvent
status.blade.rebooting cBladeCmdRebootTrap
cBladeCmdRebootEvent
pBladeCmdRebootTrap
pBladeCmdRebootEvent
status.blade.runlevel cBladeInitTrap
cBladeInitEvent
pBladeInitTrap
pBladeInitEvent
A-32 PM5.2_BF

Internal Event Type
status.blade.selected cBladeSelectedTrap
cBladeSelectedEvent
pBladeSelectedTrap
pBladeSelectedEvent
sBladeSelectedTrap
sBladeSelectedEvent
cBladeDeselectedTrap
cBladeDeselectedEvent
pBladeDeselectedTrap
pBladeDeselectedEvent
sBladeDeselectedTrap
sBladeDeselectedEvent
status.blade.shuttingdown pBladeCmdHaltTrap
pBladeCmdHaltEvent
status.blade.vblade.ram. pBladeVbladeRamOvercommitTrap
overcommit.event pBladeVbladeRamOvercommitEvent
status.blade.winkout pBladeWinkoutTrap
pBladeWinkoutEvent
status.cblade.sys.msg.1 — cBladeSyslogEventTrap
status.cblade.sys.msg.10 cBladeSyslogEvent
status.cblade.sys.msg.dropped cBladeSyslogDroppedTrap
cBladeSyslogDroppedEvent
status.cblade.sys.msg.stopped cBladeSyslogPollingStoppedTrap
cBladeSyslogPollingStoppedEvent
status.devicemanager.device.mismatch platformDeviceIdMismatchTrap
platformDeviceIdMismatchEvent
status.devicemanager.eth.mismatch platformREthMisconfigTrap
platformREthMisconfigEvent
status.disk.partitioned diskPartitionedTrap
diskPartitionedEvent
PM5.2_BF A-33

Internal Event Type
status.disk.rooted diskRootedTrap
diskRootedEvent
status.disk.winpe diskWinPeTrap
diskWinPeEvent
status.eth.link.down cBladeEthLinkDownTrap
cBladeEthLinkDownEvent
status.eth.link.up cBladeEthLinkUpTrap
cBladeEthLinkUpEvent
status.eth.reth.active cBladeEthStatusActiveTrap
cBladeEthStatusActiveEvent
status.eth.reth.standby cBladeEthStatusStandbyTrap
cBladeEthStatusStandbyEvent
status.eth.reth.failed cBladeEthStatusFailedTrap
cBladeEthStatusFailedEvent
status.eth.reth.unconfigured cBladeEthStatusUnconfiguredTrap
cBladeEthStatusUnconfiguredEvent
status.frame.power.consumption.overattac platformPowerOverCommitTrap
hed
platformPowerOverCommitEvent
status.frame.power.consumption.overpower platformPowerOverDrawTrap
ed
platformPowerOverDrawEvent
status.frame.power.consumption.powerdeni platformPowerDeniedTrap
ed
status.frame.power.consumption.powerdeni platformPowerDeniedTrap
ed
status.ha.monitor.failed applicationMonitorFailedTrap
applicationMonitorFailedEvent
loadBalancerMonitorFailedTrap
loadBalancerMonitorFailedEvent
A-34 PM5.2_BF

Internal Event Type
status.ha.monitor.invalid applicationMonitorInvalidTrap
applicationMonitorInvalidEvent
loadBalancerMonitorInvalidTrap
loadBalancerMonitorInvalidEvent
status.ha.service.failover.completed applicationFailedOverTrap
applicationFailedOverEvent
loadBalancerFailedOverTrap
loadBalancerFailedOverEvent
status.ha.service.failover.failed applicationFailoverFailedTrap
applicationFailoverFailedEvent
loadBalancerFailoverFailedTrap
status.ha.service.failover.started applicationFailingOverTrap
applicationFailingOverEvent
loadBalancerFailingOverTrap
loadBalancerFailingOverEvent
status.ha.service.hmon.failover applicationFailoverTrap
applicationFailoverEvent
loadBalancerFailoverTrap
loadBalancerFailoverEvent
status.ha.service.hmon.failure applicationFailureDetectedTrap
applicationFailureDetectedEvent
loadBalancerFailureDetectedTrap
loadBalancerFailureDetectedEvent
status.ha.service.hmon.giveup applicationGiveupTrap
applicationGiveupEvent
loadBalancerGiveupTrap
loadBalancerGiveupEvent
PM5.2_BF A-35

Internal Event Type
status.ha.service.hmon.restart applicationRestartedTrap
applicationRestartedEvent
loadBalancerRestartedTrap
loadBalancerRestartedEvent
status.ha.service.move.completed applicationMovedTrap
applicationMovedEvent
loadBalancerMovedTrap
loadBalancerMovedEvent
status.ha.service.move.failed applicationMoveFailedTrap
applicationMoveFailedEvent
loadBalancerMoveFailedTrap
loadBalancerMoveFailedEvent
status.ha.service.move.started applicationMovingTrap
applicationMovingEvent
loadBalancerMovingTrap
loadBalancerMovingEvent
status.ha.service.start.completed applicationStartedTrap
applicationStartedEvent
loadBalancerStartedTrap
loadBalancerStartedEvent
status.ha.service.stop.completed applicationStoppedTrap
applicationStoppedEvent
loadBalancerStoppedTrap
loadBalancerStoppedEvent
status.ha.service.stop.failed applicationStopFailedTrap
applicationStopFailedEvent
loadBalancerStopFailedTrap
loadBalancerStopFailedEvent
A-36 PM5.2_BF

Internal Event Type
status.ha.service.stop.started applicationStoppingTrap
applicationStoppingEvent
loadBalancerStoppingTrap
loadBalancerStoppingEvent
status.ha.warning applicationStatusWarningTrap
applicationStatusWarningEvent
loadBalancerStatusWarningTrap
loadBalancerStatusWarningEvent
status.hba.change.info cBladeHbaStatusChangedTrap
cBladeHbaStatusChangedEvent
status.hba.disable cBladeHbaDisabledTrap
cBladeHbaDisabledEvent
status.hba.down cBladeHbaStatusDownTrap
cBladeHbaStatusDownEvent
status.hba.enable.info cBladeHbaEnabledTrap
cBladeHbaEnabledEvent
status.ipmi.cecc.threshold.event pBladeIpmiCeccThresholdTrap
pBladeIpmiCeccThresholdEvent
status.ipmi.event cBladeHwEventTrap
cBladeHwEvent
pBladeHwEventTrap
pBladeHwEvent
sBladeHwEventTrap
sBladeHwEvent
status.ipmi.fan.high.critical cBladeFanSpeedUpperTrap
cBladeFanSpeedUpperEvent
pBladeFanSpeedUpperTrap
pBladeFanSpeedUpperEvent
sBladeFanSpeedUpperTrap
sBladeFanSpeedUpperEvent
PM5.2_BF A-37

Internal Event Type
status.ipmi.fan.low.critical cBladeFanSpeedLowerTrap
cBladeFanSpeedLowerEvent
pBladeFanSpeedLowerTrap
pBladeFanSpeedLowerEvent
sBladeFanSpeedLowerTrap
sBladeFanSpeedLowerEvent
status.ipmi.fatal.hardware.event cBladeFatalHwErrorTrap
cBladeFatalHwErrorEvent
pBladeFatalHwErrorTrap
pBladeFatalHwErrorEvent
sBladeFatalHwErrorTrap
sBladeFatalHwErrorEvent
status.ipmi.hw.error.threshold.event pBladeHwErrorThresholdTrap
pBladeHwErrorThresholdEvent
status.ipmi.nonfatal.hardware.event cBladeNonFatalHwErrorTrap
cBladeNonFatalHwErrorEvent
pBladeNonFatalHwErrorTrap
pBladeNonFatalHwErrorEvent
sBladeNonFatalHwErrorTrap
sBladeNonFatalHwErrorEvent
status.ipmi.temp.high.critical cBladeTempUpperTrap
cBladeTempUpperEvent
pBladeTempUpperTrap
pBladeTempUpperEvent
sBladeTempUpperTrap
sBladeTempUpperEvent
A-38 PM5.2_BF

Internal Event Type
status.ipmi.temp.low.critical cBladeTempLowerTrap
cBladeTempLowerEvent
pBladeTempLowerTrap
pBladeTempLowerEvent
sBladeTempLowerTrap
sBladeTempLowerEvent
status.ipmi.voltage.high.critical cBladeVoltageUpperTrap
cBladeVoltageUpperEvent
pBladeVoltageUpperTrap
pBladeVoltageUpperEvent
sBladeVoltageUpperTrap
sBladeVoltageUpperEvent
status.ipmi.voltage.low.critical cBladeVoltageLowerTrap
cBladeVoltageLowerEvent
pBladeVoltageLowerTrap
pBladeVoltageLowerEvent
sBladeVoltageLowerTrap
sBladeVoltageLowerEvent
status.lpan.activated lPanActivatedTrap
lPanActivatedEvent
status.lpan.deactivated lPanDeactivatedTrap
lPanDeactivatedEvent
status.lpan.operation.aborted lPanOperationAbortedTrap
lPanOperationAbortedTrap
status.lpan.operation.completed lPanOperationCompletedTrap
lPanOperationCompletedEvent
status.lpan.operation.started lPanOperationStartedTrap
lPanOperationStartedEvent
status.pan.manager.downtime.report bfPANManagerDowntimeTrap
bfPANManagerDowntimeEvent
PM5.2_BF A-39

Internal Event Type
status.pan.manager.failed cBladeFailureTrap
cBladeFailureEvent
status.pan.manager.failed.over cBladeMasterFailoverTrap
cBladeMasterFailoverEvent
status.pan.manager.started cBladeMasterTrap
cBladeMasterEvent
cBladePanManagerStartedTrap
cBladePanManagerStartedEvent
cBladeSlaveTrap
cBladeSlaveEvent
status.pan.manager.stonithed cBladeStonithTrap
cBladeStonithEvent
status.pool.blade.arrive poolPBladeArrivedTrap
poolPBladeArrivedEvent
status.pool.blade.departed poolPBladeDepartedTrap
poolPBladeDepartedEvent
status.power.event cBladePowerOffTrap
cBladePowerOffEvent
cBladePowerOnTrap
cBladePowerOnEvent
pBladePowerOffTrap
pBladePowerOffEvent
pBladePowerOnTrap
pBladePowerOnEvent
sBladePowerOffTrap
sBladePowerOffEvent
sBladePowerOnTrap
sBladePowerOnEvent
status.pserver.agent.available pServerAgentArrivedTrap
pServerAgentArrivedEvent
A-40 PM5.2_BF

Internal Event Type
status.pserver.agent.unavailable pServerAgentDepartedTrap
pServerAgentDepartedEvent
status.pserver.boot.failed pServerBootFailedTrap
pServerBootFailedEvent
status.pserver.boot.started pServerBootingTrap
pServerBootingEvent
status.pserver.boot.succeeded pServerBootedTrap
pServerBootedEvent
status.pserver.disk.available pServerDiskAvailableTrap
pServerDiskAvailableEvent
status.pserver.disk.unavailable pServerDiskUnavailableTrap
pServerDiskUnavailableEvent
status.pserver.failed pServerFailedTrap
pServerFailedEvent
status.pserver.failover.started pServerFailoverTrap
pServerFailoverEvent
status.pserver.hardware.offline pServerHardwareOfflineTrap
pServerHardwareOfflineEvent
status.pserver.hardware.online pServerHardwareOnlineTrap
pServerHardwareOnlineEvent
status.pserver.migrate.failed pServerMigrateFailedTrap
pServerMigrateFailedEvent
status.pserver.migrate.started pServerMigratingTrap
pServerMigratingEvent
status.pserver.migrate.succeeded pServerMigratedTrap
pServerMigratedEvent
status.pserver.operation.started pServerOperationStartedTrap
pServerOperationStartedEvent
PM5.2_BF A-41

Internal Event Type
status.pserver.panic.cycle pServerPanicCycleTrap
pServerPanicCycleEvent
status.pserver.pblade.available pServerPBladeAvailableTrap
pServerPBladeAvailableEvent
status.pserver.reboot.started pServerRebootingTrap
pServerRebootingEvent
status.pserver.recovered pServerRecoverTrap
pServerRecoverEvent
pServerRecoveredTrap
pServerRecoveredEvent
status.pserver.resume.completed pServerResumedTrap
pServerResumedEvent
status.pserver.resume.failed pServerResumeFailedTrap
pServerResumeFailedEvent
status.pserver.resume.started pServerResumingTrap
pServerResumingEvent
status.pserver.shutdown.completed pServerShutdownTrap
pServerShutdownEvent
status.pserver.shutdown.failed pServerShutdownFailedTrap
pServerShutdownFailedEvent
status.pserver.shutdown.started pServerShuttingDownTrap
pServerShuttingDownEvent
status.pserver.suspend.completed pServerSuspendedTrap
pServerSuspendedEvent
status.pserver.suspend.failed pServerSuspendFailedTrap
pServerSuspendFailedEvent
status.pserver.suspend.started pServerSuspendingTrap
pServerSuspendingEvent
A-42 PM5.2_BF

Internal Event Type
status.pserver.sys.msg.1 to pServerSyslogEventTrap
status.pserver.sys.msg.10
pServerSyslogEvent
status.pserver.sys.msg.dropped pServerSyslogDroppedTrap
pServerSyslogDroppedEvent
status.pserver.sys.msg.stopped pServerSyslogPollingStoppedTrap
pServerSyslogPollingStoppedEvent
status.rcc.expired.files.deleted bfRccExpiredFilesDeletedTrap
bfRccExpiredFilesDeletedEvent
status.rcc.period.begin bfRccReportPeriodStartTrap
bfRccReportPeriodStartEvent
status.rcc.period.end bfRccReportPeriodEndTrap
bfRccReportPeriodEndEvent
status.reth.state.redundant rethStatusRedundantTrap
status.reth.state.notredundant rethStatusRedundantTrap
status.reth.state.degraded rethStatusDegradedTrap
rethStatusDegradedEvent
status.reth.state.failed rethStatusFailedTrap
rethStatusFailedEvent
status.system.threshold.high pServerSystemThresholdHighTrap
pServerSystemThresholdHighEvent
cBladeSystemThresholdHighTrap
cBladeSystemThresholdHighEvent
status.system.threshold.low pServerSystemThresholdlowTrap
pServerSystemThresholdlowEvent
status.user.monitor.event pServerUserMonitorTrap
pServerUserMonitorEvent
PM5.2_BF A-43
A-44 PM5.2_BF
Index
A vSwitch to an LPAN 3-14, 5-6

application
access control 4-3
installation 10-4
accessing pServer
application control
through MindTerm or SSH 10-4,
automatic start of 10-2, 11-6, 11-9
10-5
definition 10-2
through PAN Manager console
application failover 9-55, 10-2
command 10-4
application health
accounts
failure policy 9-55
creating 4-4
monitoring 9-46
removing 4-4
application health monitors
ActiveX controls 8-7
default 9-49
adding
guidelines 9-56
executable resources 9-16, 9-45
application resource
failover policies 9-38
configuring for failover 9-34
resources to an LPAN 5-36
definition 9-3, 10-2
administrative domains 13-6
executable 9-5
LPAN 4-7
failover policy 9-6, 9-7
PAN 4-6
health monitor 9-7
types 4-6
network 9-5
alert script 9-55
network file system 9-6
alias 11-8
user defined monitor 9-7
allocating
application resources
disk to an LPAN 5-2, 5-3, 5-4
definition 11-3
pBlade
application template
to an LPAN 5-2, 5-3
definition 9-8
SAN disk to an LPAN 5-3, 5-4
PM5.2_BF Index-1
archive bug check errors 16-12

exporting 14-6 bus driver 8-12
importing 14-6
mapping resources 14-16
merging 14-14 C
PAN archive 14-1
cBlade
validating 14-19
failover 12-10
assigning
master 12-10
failover pBlade to pServer 6-4, 6-5
slave 12-10
pBlade to pServer 6-4
cBlades
primary pBlade to pServer 6-4
configuration report 16-5
users to roles 4-8
state information 16-4
automatic crash dumps 16-10
CD-ROM
automatic start
enabling 10-3, 10-4
of application 10-2, 11-6, 11-9
clusters
MSCS 8-22
NLB 8-18
B
command session 1-2
-b option configuration reports 16-5
showme command 16-5 configuring
blue screen errors 16-12 application failover 9-34
boot arguments (pServer) 7-17 domain defaults for event types
boot image 14-4 13-7
default 2-8, 7-17 Ethernet interfaces 3-5
specifying for pServer 7-17 file system
boot images 2-8 for failover 9-34
boot.ini file 8-20, 16-17 IP address
booting for pServer 6-19
LPAN 5-32, 12-11 PAN attributes 2-5
on different pBlade type 8-13 rEth (redundant Ethernet interface)
pServer 5-32, 12-13 3-9, 3-11
pServers collectively 12-16 system monitor 13-11, 13-14
broadcast address trigger 13-9
network resource 9-5 connection
PAN Manager control of 9-5 external vSwitch 3-18
browser multiple vSwitch 3-16
supported versions 1-2 single vSwitch 3-15
Index-2 PM5.2_BF
Index
vSwitch between LPANs 3-17 E

console
-e option, showme command 16-6
driver 8-12
ECC errors 16-21
RDP connection 8-2, 8-9
EgenCfg.cpl applet 8-14, 8-17
vVGA 8-6
Egenera drivers 8-12
crash dumps
description 8-10
automatic 16-10
displaying versions 8-14
manual 16-11
restrictions 8-13
naming 16-12
signatures 8-14
crashes, handling 16-12
enabling CD-ROM 10-3, 10-4
creating
Ethernet configuration report 16-6
failover policies 9-34
Ethernet interface
pServer 6-2
configuring 3-5
vEth 6-17
connecting pServers to network 3-5
vSwitch 3-13, 5-6
failover 3-9
cron jobs, and repurposing servers 8-23
load-balancing 3-9
redundant (rEth) 3-8, 3-9, 3-11,
3-18
D
event
-d option, showme command 16-5 definition 13-2
diagnostic flowcharts 16-15 trigger 13-9
disabling viewing 13-3, 13-15
MPIO 8-19 event type
vVGA 8-8 configuring domain defaults 13-7
disaster recovery 14-1 default action 13-6
disks events
configuration report 16-5 nonsensor 16-11, 16-14
display driver 8-12 PAN Manager event log 8-12,
displaying 16-14
platform configuration report 16-5 executable resource
drivers adding 9-16, 9-45
description 8-10 definition 9-5
displaying versions 8-14 modifying 9-16, 9-45
restrictions 8-13 removing 9-16, 9-45
signatures 8-14 external network connection 3-17
DSM driver 8-12
dumps, handling 16-10
PM5.2_BF Index-3
F hardware prefetch 7-18

HBAs, configuration reports 16-5
failover 6-19
health monitor resource
application 9-55
definition 9-7
configuring file systems for 9-23
hyperthreading 7-18, 8-9
creating failover policies 9-34
Ethernet interface 3-9
guidelines 9-34
I
failover pBlade
assigning to pServer 6-4 IGMP and NLB clusters 8-18
obtaining from pool 6-4 IP address 12-9, 12-13
failover policies alias 11-8
adding 9-38 configured for a pServer 6-19
creating 9-34 network resource 9-5
modifying 9-38 PAN Manager control of 9-5
removing 9-38 IP addresses 8-5
failover policy resource IPMI driver 8-12
definition 9-6, 9-7
failure policies
application health 9-55 K
file system
keyboard driver 8-12
configuring for failover 9-34
KVM driver 8-12
pServer’s root 5-4
filever command 8-15
firewall configuration 8-7
L
flowcharts for troubleshooting 16-15
Found New Hardware wizard 8-13, -l option, showme command 16-6
8-16 least connected scheduling policy 11-4
link driver 8-12
Linux Virtual Server (LVS) 11-2
G load balancing resource
executable 9-5
global pool 5-24
failover policy 9-6, 9-7
health monitor 9-7
network 9-5
H
network file system 9-6
handling crash dumps 16-10 user defined monitor 9-7
hardware configuration reports 16-5 load-balancing
Index-4 PM5.2_BF
Index
definition 10-2, 11-1, 11-2 failover policies 9-38

Ethernet interface 3-9 network resources 9-20
selection policy 11-4 pServer configuration 7-4, 7-5
local pool 5-24 MON (service monitoring daemon)
logging 9-46, 9-47, 13-11
PAN Manager event log 8-12, monitor script
16-11, 16-14 custom 9-50
LPAN integrating 9-51
adding resources 5-36 monitoring
administrative domain 4-7 application health 9-46, 13-1
allocating platform system health 13-1, 13-2
disk 5-2, 5-3, 5-4 pServer boot process 6-2
pBlade 5-2, 5-3 pServer system health 13-1
vSwitch 3-13, 3-14, 5-6 mouse driver 8-12
assigning administrator 5-7 MPIO
booting 5-32, 12-11 enabling and disabling 8-19
definition 5-2 MSCS
naming 5-2 recommendations 8-22
rebooting 12-11 mstsc command 8-6
removing resources 5-36, 5-37 MTU size 8-17
shutting down 12-11 multicast requirements 8-16, 8-18
LPAN Administrator
assigning 5-7
N
name, platform default 2-3
M
naming
MAC address 3-9, 6-17 LPANs 5-2
maintenance LPAN 16-8 pServers 6-2
Maintenance Mode 16-3 naming convention
manual crash dumps 16-11 load-balancing service 11-5
memory footprint reduction 8-21 rEth 3-9
memory, tuning virtual memory 8-20 SCSI ID 5-5
Memory.dmp file 16-12 naming crash dumps 16-12
Microsoft NAS device
Windows debugger 16-15 allocating to an LPAN 5-4
modifying 9-27, 9-33 booting from 6-10
executable resources 9-16, 9-45 netmask
PM5.2_BF Index-5
network resource 9-5 P

PAN Manager control of 9-5
-p option, showme command 16-5
network
packet collapsing 8-21
configuration guidelines 8-16
PAN
connectivity 3-9
administrative domain 4-6
driver 8-12
configuring attributes 2-5
network connectivity 3-1
PAN archiving 14-1, 14-2
network file system (NFS) 6-10
PAN Manager
network file system resource
command line interface (CLI) 1-2
definition 9-6
event log 8-12, 16-14
modifying 9-33
graphical user interface (GUI) 1-2
network file system resources 9-33
roles 4-1
network resource
user accounts 4-4
broadcast address 9-5
parameters with Stop code 16-13
definition 9-5
pBlade
IP address 9-5
allocating to an LPAN 5-3
netmask 9-5
assigning
network resources
to pServer 6-4
modifying 9-20
assigning to pServer
network stop/restart 12-9, 12-13
failover 6-4
network topology 3-19
primary 6-4
NLB clusters 8-18
displaying characteristics 10-3
node interleaving 7-18
failover 5-26
nonsensor events 16-11, 16-14
obtaining from global pool 5-25
Ntbtlog.txt file 16-17
obtaining from local pool 5-25
pool 6-4
powering off 12-5
O
powering on 12-5
operating system resetting 12-5
supported versions 2-8 sending non-maskable interrupt
/opt/egenera/bin/save_state command 12-5
16-4 pBlade requirements 8-18
/opt/egenera/bin/showme command pBlades
16-5 configuration report 16-5
ordered list selection policy 9-35 persistent disk reservation 5-20
PIM configuration report 16-5
platform
Index-6 PM5.2_BF
Index
monitoring 13-2 reserving resources 6-2

rebooting 12-3 shutting down 5-32, 12-13
shutting down 12-3 understanding configuration of 7-6
trigger 13-3 understanding status of 7-6
platform configuration reports 16-5 validating configuration 6-2
Platform ID 2-4 vEth 6-3
pool pServer access
definition 5-24 through MindTerm or SSH 10-4,
descriptions 5-25 10-5
global 5-24 through PAN Manager console
local 5-24 command 10-4
maximum numbers 5-24 pServer blade assignment
naming conventions 5-24 failover pBlade 6-5
organizing similar blades 5-24 primary pBlade 6-4
powering off pServer booting 5-32, 12-13
pBlade 12-5 boot image 7-17
powering on rebooting 12-13
pBlade 12-5 pServers
primary pBlade 6-4 booting collectively 12-16
primary redundant Ethernet interface disabling hyperthreading 8-9
(rEth) 3-9 shutting down 8-9
pServer unresponsive 16-15
assigning SAN disks to 6-9 PTEs, and virtual memory 8-20
assigning tape devices to 6-13, 6-16
communicating across LPANs 5-6
configuring IP address 6-19 R
creating 6-2
RCC 15-1
definition 6-2
requirements using 15-2
enabling DVD-ROM drive 6-16
RDP
modifying configuration 7-4, 7-5
opening a connection 8-2
monitoring boot process 6-2
reestablishing a session 8-3
naming 6-2
rebooting
network connection 6-3, 6-17
LPAN 12-11
obtaining pBlade 6-4
platform 12-3
obtaining primary pBlade from pool
pServer 12-13
6-4
reboots
rebooting 12-13
reboot loop 16-17
repartitioning SAN disk 7-4
PM5.2_BF Index-7
removing configuration report 16-5

executable resources 9-16, 9-45 scheduling policies
failover policies 9-38 least connected 11-4
repurposing servers 8-22 round-robin 11-4
resetting weight 11-8
pBlade 12-5 weighted least connected 11-5
Resource Configuration Collector 15-1 weighted round-robin 11-4
rEth (redundant Ethernet interface) SCSI disk resources 9-27
configuring 3-9, 3-11 modifying 9-27
specifying primary 3-9 SCSI driver 8-13
uplink 3-18 SCSI-2 disk reservations 5-4
roles SCSI-3 disk reservations 5-19
administrator 4-7 selection policies for failover
assigning to a user 4-8, 4-12 ordered list 9-35
definition 4-7 round-robin 9-35
monitor 4-7 service resource
operator 4-7 executable 9-5
permissions 4-8 failover policy 9-6, 9-7
removing a user 4-12 health monitor 9-7
root image 14-4 network 9-5
round-robin network file system 9-6
scheduling policies 11-4 user defined monitor 9-7
selection policy 9-35 setting MTU size 8-17
showme command 16-5
shutting down
S LPAN 12-11
platform 12-3
-s option, showme command 16-6
pServer 5-32, 12-13
SAC console 8-10, 16-19
shutting down pServers 8-9
SAN connections, drivers 8-10
signatures, of drivers 8-14
SAN disk
small buffer mode 8-21
allocating to an LPAN 5-3, 5-4
SNMP
allocation limit 5-4
configuring 13-18
guidelines 6-9, 6-13
support 13-4
repartitioning 7-4
types of agents 13-18
save_state command 16-4
software configuration reports 16-5
save_state file 16-10
state information 16-4
sBlades
Stop codes 16-13
Index-8 PM5.2_BF
Index
system crashes 16-12 users

System Interrupt Controllers 16-21 creating accounts 4-4
system monitor 13-3 PAN Manager 4-4
configuring 13-11, 13-14 /userva switch, boot.ini file 8-20
T V
tasks 3-1 /var/log/messages file 16-15
TCP 11-4 versions
TCP ports 8-7 drivers 8-14
trigger 13-3 vEth
configuring 13-9 creating 6-17
default values 13-9 network connection 6-17
modifying default values 13-14 total number allowed 6-3
troubleshooting vEths, and MTU size 8-17
process flowcharts 16-15 VGA driver 8-13
viewing events 13-15
Virtual Ethernet Interface. See vEth
U virtual memory, tuning 8-20
virtualization extensions 7-18
UDP 11-4
VLAN 3-5, 3-18
understanding
ID 3-5
pServer configuration 7-6
VLAN ID 3-14
pServer status 7-6
vSwitch
ungraceful shutdown 8-9
allocating to an LPAN 3-14, 5-6
unreachable interfaces 8-4
bridging LPANs 3-16
Up Time field 16-17
clearing uplink 3-14, 5-6
uplink 3-14, 3-17
creating 3-13, 3-19, 5-6
user
definition 3-13, 5-6
assigning to a role 4-8
external 5-7
user account
external communication 3-14, 3-17
creating 4-4
internal 5-7
removing 4-4
total number allowed 3-14
user accounts
uplink 3-17, 6-17
creating 4-4
vVGA
removing 4-4
disabling 8-8
user defined monitor resource
drivers 8-10
definition 9-7
PM5.2_BF Index-9
features 8-6 weighted least connected scheduling

firewall configuration 8-7 policy 11-5
limitations 8-7 weighted round-robin scheduling
opening a connection 8-7 policy 11-4
requirements 8-7 Windows event log
Egenera drivers 8-10
W
Y
weight 11-8
yellow warning 16-21
Index-10 PM5.2_BF

PAN Manager Administrator's Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PAN Manager Administrator's Guide

Uploaded by

Copyright:

Available Formats

PAN Manager Administrator’s Guide

For BladeFrame® BF400 S2 and BladeFrame® BF200

Document Number 430-SB0084

Customer Support ..................................................................................................... xx

Document Conventions ............................................................................................ xx

Chapter 1: Getting Started with PAN Manager

About PAN Manager ............................................................................................... 1-2

The PAN Manager GUI .......................................................................................... 1-3

Part I: Creating a PAN

Chapter 2: Configuring the PAN Structure

Overview ................................................................................................................. 2-2

Naming the Platform ............................................................................................... 2-3

Naming the Platform ........................................................................................ 2-3

Specifying the PAN Identification Attributes ......................................................... 2-5

Configuring the SMTP Server ................................................................................. 2-7

Specifying Default Boot and Root Disk Images ..................................................... 2-8

Activating Flow Control on the PAN .................................................................... 2-11

Configuring Power Management .......................................................................... 2-13

Displaying Available Application Templates ....................................................... 2-18

Chapter 3: Configuring External Connectivity

Modifying Internal and External Management Settings ......................................... 3-3

Configuring Ethernet Interfaces .............................................................................. 3-5

Configuring Redundant Ethernet Interfaces ............................................................ 3-8

About Ping Failover Detection Mode............................................................. 3-10

Creating vSwitches ................................................................................................ 3-13

Chapter 4: Managing System Access

Establishing Access Control .................................................................................... 4-2

Creating Users and Accounts .................................................................................. 4-2

Assigning Roles to PAN Manager Users ................................................................ 4-6

Managing Users and Accounts .............................................................................. 4-10

Chapter 5: Creating LPANs

Creating and Allocating Resources to an LPAN ..................................................... 5-2

About LPANs ................................................................................................... 5-2

Configuring Disks for Persistent Reservations .................................................... 5-19

Creating Global and Local Pools ........................................................................... 5-24

Booting the LPAN’s pServers ............................................................................... 5-32

Modifying an LPAN’s Resources ......................................................................... 5-36

Part II: Creating pServers

Chapter 6: Configuring pServers

Creating a pServer ................................................................................................... 6-2

Assigning Processing Blades ................................................................................... 6-4

Assigning SAN Disks .............................................................................................. 6-9

Assigning FC Tape Devices .................................................................................. 6-13

Enabling a DVD-ROM Drive ................................................................................ 6-16

Enabling a Virtual CD-ROM Drive ...................................................................... 6-17

Establishing Network Connections ....................................................................... 6-17

Completing a pServer’s Configuration .................................................................. 6-22

Chapter 7: Administering pServers

Displaying pServer Information .............................................................................. 7-2

Modifying a pServer Name or Description ............................................................. 7-3

Modifying a pServer Configuration ........................................................................ 7-4

Managing Virtual CD-ROMs ................................................................................ 7-11

Managing Boot and Root Disk Images ................................................................. 7-13

Configuring pServer Boot Attributes .................................................................... 7-17

Using the pServer Console .................................................................................... 7-21

Chapter 8: Administering Windows-Based pServers

Connecting to a pServer Using the Remote Desktop Protocol ............................... 8-2

Connecting to a pServer Using the Virtual VGA Desktop ..................................... 8-6

Shutting Down Windows pServers ......................................................................... 8-9

Disabling the Hyperthreading Feature (Intel Only) ................................................ 8-9

Managing Device Drivers ..................................................................................... 8-10

Configuring Network Connections ....................................................................... 8-16