PAN Manager Command Reference - Fujitsu …manuals.ts.fujitsu.com/file/3640/commands.pdfPM5.2_BF vi...

PAN Manager Command Reference

For BladeFrame® BF400 S2 and BladeFrame® BF200

Document Number 430-SB0085

August 2010

PM5.2_BF

CopyrightCopyright © 2010 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 Technology Solutions.

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.[100901:110913]

Egenera, Inc., 165 Forest Street, Marlboro, Massachusetts 01752.

iii

Contents

Preface

Customer Support ..................................................................................................1-vii

Chapter 1: PAN Manager Commands Overview

Using PAN Manager Commands ............................................................................ 1-2

Functional Groupings of PAN Manager Commands .............................................. 1-4

The Man Page Format ........................................................................................... 1-10

Chapter 2: PAN Manager CommandsACCOUNT ............................................................................................................. 2-2APP ...................................................................................................................... 2-7BFRAME ............................................................................................................ 2-15BLADE ................................................................................................................. 2-21CONSOLE ......................................................................................................... 2-36DISK ................................................................................................................... 2-38ETH ................................................................................................................. 2-46 EVENT ................................................................................................................ 2-52EVENTTYPE ....................................................................................................... 2-61EXERES ............................................................................................................ 2-67EXTNET .............................................................................................................. 2-71FOP ................................................................................................................... 2-75FS ....................................................................................................................... 2-80HMON ................................................................................................................ 2-84INTNET .............................................................................................................. 2-90IP .................................................................................................................... 2-93


iv

LB ........................................................................................................................ 2-98LPAN ................................................................................................................. 2-108MON .................................................................................................................. 2-119MONDEF ........................................................................................................... 2-125NFS ................................................................................................................... 2-129PAN .................................................................................................................... 2-132PANMGR ........................................................................................................... 2-153PIM .................................................................................................................... 2-155POOL .................................................................................................................. 2-160PSERVER .......................................................................................................... 2-166RETH .................................................................................................................. 2-189ROLE .................................................................................................................. 2-198SAN .................................................................................................................. 2-200SMTPSVR ......................................................................................................... 2-208SNMP ............................................................................................................... 2-210SNMPMGR ....................................................................................................... 2-214SW ..................................................................................................................... 2-218TAPE ................................................................................................................ 2-222UMON ............................................................................................................... 2-225USER ................................................................................................................. 2-229VERSION .......................................................................................................... 2-233

Contents

v

PM5.2_BF vi

Preface

Welcome to PAN Manager PM5.2_BF. The PAN Manager Command Reference is part of the PAN Manager documentation set. Its purpose is to describe how PAN Manager commands are grouped, and provides the command man pages in a print format.

Audience — PAN Manager Command Reference is for PAN Administrators and LPAN Administrators.

Topics — Read this book to learn about the following:

• Using PAN Manager Commands

• Functional Groupings of PAN Manager Commands

• The Man Page Format

• Detailed descriptions of each command

Preface

PM5.2_BF vii

Customer Support

For the latest support, downloads, release notes, and other information resources regarding PAN Manager software, please use the following contact information:

Fujitsu Technology Solutions customer support

For customer support regarding this product, please use the following contact information:

Fujitsu Technology Solutions customer support

Internet http://support.ts.fujitsu.com

Telephone See the Help Desk information at http://manuals.ts.fujitsu.com/primergyservers.html, under Contact.

Internet http://support.ts.fujitsu.com

Telephone See the Help Desk information at http://manuals.ts.fujitsu.com/primergyservers.html, under Contact.


viii PM5.2_BF

Document Conventions

Convention Description

> Directory-level delimiter used to navigate the left pane of the PAN Manager GUI.

Example: Resources > Networking

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.

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 1-1

Chapter 1PAN Manager Commands

Overview

This overview of the PAN Manager Command Reference includes the following topics:

• Using PAN Manager Commands

• Functional Groupings of PAN Manager Commands

• The Man Page Format


1-2 PM5.2_BF

Using PAN Manager Commands

PAN Manager provides a set of commands that you can use from the Linux command line or from scripts like any other Linux command. These commands are described in detail in the next chapter, and their documentation can also be accessed on-line as described below.

Using the PAN Manager Commands in Scripts

When you create scripts using PAN Manager, keep in mind the follow guidelines:

Script Syntax

Each PAN Manager command is actually a subcommand of the PAN Manager shell (/opt/panmgr/bin/esh). If you use PAN Manager commands in a shell script, you must do one of the following:

• Use the entire esh pathname with each command. For example:# /opt/panmgr/bin/esh lpan -l

• Add /opt/panmgr/bin to your user PATH, then include the 'esh' prefix with each command. For example:# esh lpan -l

Before you use the scripts in your own environment, you need to gather all the information required for configuration. We also recommend that you create a logical diagram of your planned configuration. Before you create scripts specific to your site, you need the following information:

• Your platform name

• IP addresses of the cBlades, PAN Manager, and any external resources to which you plan to connect

• Storage Area Network (SAN) disk IDs or SCSI IDs

PAN Manager Commands Overview

PM5.2_BF 1-3

• External switch information for external connections

Scripting: Guidelines and Best Practices

Each PAN Manager command is a subcommand of the PAN Manager shell (/opt/panmgr/bin/esh). In the operating system on the Control Blade, each PAN Manager command is aliased in each user account’s login profile, by default:

alias account='esh account'alias app='esh app'alias bframe='esh bframe'...

You can use any of a number of scripting languages, including bash, perl, or csh in which to embed specific PAN Manager command lines or the sample scripts provided in Appendix A, “Sample Scripts”.

Argument Placement

For PAN Manager commands that have add, create, edit, or modify options, the argument of those options must be placed at the end of the command string. For example, to add a user and specify the user’s email address, enter the following:

# user -a -E [email protected] username

Even though the option flag (-a) is at the beginning of the command, the argument (username) must be at the end of the command string. If the argument of one of these options is not the last string, a parsing error may occur, losing the user’s original intent.

Accessing PAN Manager man Pages

PAN Manager man pages are reference pages available for each PAN Manager command. PAN Manager man pages conform to the standard Red Hat Linux man page format.


1-4 PM5.2_BF

You access PAN Manager man pages from the Linux prompt like any other man page, except that you must preface the command with an “egenera_” prefix. For example, to view the lpan man page, enter the following command at the Linux prompt:

# man egenera_lpan

Accessing PAN Manager Help

To display the options and appropriate syntax for each command, enter the following command, substituting the actual command name:

# help commandname

Functional Groupings of PAN Manager Commands

The following tables group PAN Manager commands according to commonly performed functions. See the PAN Manager Administrator’s Guide for a detailed understanding of how and when these functions are used while managing a PAN.

Getting Started PAN Administrators use the following commands to configure the basic settings for a PAN:

Table 1.1 Configuration Commands

Task Commands used

Rename the platform. BFRAME

Configure the PAN administrative domain, including an SNMP agent, a mail server, and boot and root images.

SNMP

SNMPMGR

PAN

../admin/title.html


PM5.2_BF 1-5

Configuring Connectivity

PAN Administrators use the following commands to set up their PAN’s network communication:

Configure power management. BFRAME

PIM

Table 1.1 Configuration Commands

Task Commands used

Table 1.2 Set-up Commands

Task Commands used

Configure the cBlade Ethernet interfaces. ETH

Configure the cBlade Redundant Ethernet (rEth) connections.

RETH

Configure external management network properties.

EXTNET

Configure internal management network properties.

INTNET

Create a new resource that mounts a shared disk or a directory on the network so that services can access storage outside the LPAN.

NFS

Configure the cBlade Virtual Switches (vSwitches).

SW

Configure external disk or tape devices. DISK

SAN

TAPE

Create one or more global pools of [=Vendor pBlade model (plats: DRS, DBS, DMC)=]s.

POOL


1-6 PM5.2_BF

Establishing Access Control

PAN Administrators use the following commands to set up user accounts for everyone who will work directly in their PAN:

Creating LPANS PAN or LPAN Administrators use the following commands to create LPANs and add resources to them in their PAN:

Table 1.3 Access Control Commands

Task Commands used

Create Linux accounts. ACCOUNT -a

Create Linux account passwords. ACCOUNT -m-P

Assign administrative roles to PAN Manager users.

USER -aR

Table 1.4 LPAN Commands

Task Commands used

Create a new LPAN. LPAN -c

Allocate [=Vendor pBlade model (plats: DRS, DBS, DMC)=]s to an LPAN.

LPAN -aB

Allocate disks to an LPAN. LPAN -aD

Allocate vSwitches to an LPAN. LPAN -aD

Assign administrative roles to users of the LPAN.

USER -aR

(Optional) Create a local pool of [=Vendor pBlade model (plats: DRS, DBS, DMC)=]s for use only in the LPAN.

POOL


PM5.2_BF 1-7

Creating pServers

Once LPAN Administrators have created LPANs, they use the following commands to create pServers within LPANs in their PAN:

Configuring Application Control

LPAN Administrators use the following commands to create the configurations necessary to run applications under the control of PAN Manager:

Table 1.5 pServer Commands

Task Commands used

Create a new pServer. PSERVER -c

Assign a primary [=Vendor pBlade model (plats: DRS, DBS, DMC)=] or a vBlade to the pServer.

PSERVER -P

Assign a primary [=Vendor pBlade model (plats: DRS, DBS, DMC)=] to the pServer.

PSERVER -B

Assign a pBlade pool—local or global —as the primary blade for a pServer.

PSERVER -B

Assign a specific pBlade or pBlade pool as the failover blade for a pServer.

PSERVER -F

Assign a disk to a pServer. (To partition a disk and add a root file system, use the DISK command.)

PSERVER -a

Assign the vSwitch(es) to a pServer. PSERVER -a

Boot a pServer. PSERVER -b

Table 1.6 Application Control Commands

Task Commands used

Create an IP resource for an application. IP

Define a file system resource. FS

Create a health monitor for application(s). HMON


1-8 PM5.2_BF

For specific information on using the hmon command, see PAN Manager Administrator’s Guide.

Monitoring the PAN

PAN or LPAN Administrators use the following commands to display the status of or alter the various hardware and software monitors in their PAN or LPAN:

Create a failover policy for application(s). FOP

Configure an application to run under PAN Manager control.

APP

Configure a load-balancing service. LB

Create or modify an executable resource that let users start, stop, or run a program or script (Linux init scripts, for example) on a pServer.

EXERES

Create a new resource that mounts a shared disk or a directory on the network so that services can access storage outside the LPAN

NFS

Table 1.6 Application Control Commands

Task Commands used

Table 1.7 Monitoring Commands

Task Commands used

List events that have been registered by the PAN Manager software.

EVENT

List the event types that the PAN Manager software monitors or modify a specific event type’s actions.

EVENTTYPE

List and modify the default trigger values for each monitor the PAN Manager software monitors.

MONDEF

List and modify the default trigger values for each system monitor of the PAN.

MON

../admin/title.html


PM5.2_BF 1-9

List, modify, or create user-defined monitor resources for an LPAN. User-defined monitor resources let a user create a set of health, status, or statistical monitors, and use the monitor’s events to control PAN Manager behavior.

UMON

Table 1.7 Monitoring Commands

Task Commands used


1-10 PM5.2_BF

The Man Page Format

PAN Manager man pages follow a format commonly seen in Linux man pages. The format for PAN Manager man pages can include the following items:

Table 1.8 Man Page Fields

Format Content

NAME The command name followed by a brief functional description.

SYNOPSIS A listing of syntax showing how to use each command option.

DESCRIPTION The details of command functionality and important technical details.

OPTIONS The descriptions of each command parameter.

EXAMPLES Specific uses of some or all of a command's arguments.

RETURN VALUES A description of the command's return value, a useful feature for scripting purposes.

SEE ALSO An alphabetical listing of other commands related to the task.

PM5.2_BF 2-1

Chapter 2PAN Manager Commands

This chapter provides an alphabetical list of all PAN Manager commands, and is formatted to provide users with printed and HTML versions of the command manpages.

PAN Manager Command Syntax

For PAN Manager commands that have add, create, edit, or modify options, the argument of the option must be placed at the end of the command string. For example, to add a user and specify the user’s email address, enter:

user -a -E [email protected] username

Note: Even though the option flag (-a) is at the beginning of the command, the argument (username) comes at the end of the command string. If the argument of one of these options is not the last string, a parsing error may occur, losing the user’s original intent.


2-2 PM5.2_BF

ACCOUNT

NAME account - creates, lists, or modifies a user’s Linux account on a cBlade.

SYNOPSIS account [-l] [username]

account -a [-L "descriptive_label" -N groupname] username

account -r [-R] username

account -m [-U UID] [-P password] [-N groupname] [-L "descriptive_label"] [-H homedirectory] [-I groupID] [-S defaultshell] username

account [-lG]

account [-aG |-rG] groupname

DESCRIPTION The account command provides a Linux account tool for the PAN Manager software. Only PAN Administrators use the account command to add, remove, modify, or list user accounts on both Control Blades (cBlades). The software facilitates a PAN Administrator’s tasks of creating Linux user accounts by duplicating the Linux account information on both cBlades.

By default, PAN Manager software is enabled to allow PAN Administrators to create and remove users. PAN Administrators can choose to enable a third-party Linux user account management tool using the pan -u command; however, by enabling a third party management of Linux accounts, they cannot use the account command to set up Linux user accounts. For additional information, see the PAN Manager Administrator’s Guide.

You must create a Linux account for any administrator who will need to access the Control Blade directly, such as for installation or debugging purposes. Be sure to issue these accounts with discretion, as they have security implications.

ACCOUNT

PM5.2_BF 2-3

PAN Manager Command Naming Conventions

Names must begin with either an alphanumeric character or a period (.) and are limited to a maximum of 32 characters with this limited character set: [a-z][A-Z][0-9][.][-][_][$]. Duplicate names in the same name space are not allowed.

Additional naming conventions for this command include:

username

Indicates the username PAN Manager uses to identify a PAN Manager user.

groupname

Indicates a Linux-recognized group that exists on the cBlades.

OPTIONS -aG, --addgroup groupname

Creates a Linux-recognized group. To create a Linux user account and add that user to a group at the same time (using the -N (groupname) option), you must first use the -aG (addgroup) option to create the group.

-a, --add username

Creates a Linux user account. Use this option with the -L (description) or the -N (groupname) option. The username must be unique. We recommend that you add a user to group at the same time you create a Linux user account so you do not create a new GID in the /etc/group file with the same number as the UID created. See the Linux usermod man page for more information.

-H, --homedir homedirectory

Associates a login directory associated with the specified Linux user account. When an account is initially created, a default /home/username directory is created and assigned as the login directory for the user. If you use this option to change the login directory, the


2-4 PM5.2_BF

directory must exist before the user can log in. This option is only valid with the -e (edit) option.

-I, --groupid groupID

Specifies a group ID number for a Linux user account.

-l, --long

Lists the Linux user accounts and displays the description, UID, groupname, GID, home directory, and default shell for each username. This option is only valid with the -l option. Using the command without an argument lists all the Linux user accounts by username only.

-L, --description "descriptive_label"

Adds a description to the information associated with the specified Linux user account. This option is valid with the -a (add) or -m (modify) options. Enter the text within quotes. For example:

account -aN development -L "Development manager" cgable

-lG, --listgroup

Lists the current groupnames with their group ID.

-m, --modify username

Allows you to edit the information associated with the user account. With this option, you must specify any or all of the -U (UID), -N (group/GID), -L (description), or -H (home directory) options.

-N, --groupname groupname

Specifies a group that is recognized by Linux to which to add a user. Groups are created with the -aG (addgroup) option. This option is used with the -a (add) and -m (modify) options and requires a groupname as an argument. When you create a new Linux account, the default group is that user. For this reason, we recommend that you specify an existing group.

ACCOUNT

PM5.2_BF 2-5

-P, --password "paqssword"

Sets a Linux user password for a user account. You can create or modify a user password using this option with the -m (modify) option.

-r, --remove username

Removes a Linux user account. For complete removal of a user, add the -R (recursive) option to remove the home directory of the user as well.

-R, --recursive

Removes all traces of the Linux account, including the user’s default directory and the /etc/group and /etc/passwd listings for the specified user. This option is only valid with the -r (remove) option.

-rG, --removegroup groupname

Deletes a Linux-recognized group.

-S, --shell defaultshell

Specifies the Linux shell associated with the specified Linux user account. When an account is initially created, the default assignment is the bash shell. If you use this option to change a user’s shell, make sure that the shell file already exists before the user logs in. This option is only valid with the -m (modify) option.

-U, --uid UID

Specifies a user ID to use with the specified Linux user account. By default, when you add a user account, a UID is automatically generated. Use this option to change the default UID of the Linux user account. This option is only valid with the -m (modify) option.

EXAMPLES List user accounts by name, description, UID, groupname, GID, home directory, and default shell:

account -l


2-6 PM5.2_BF

Create Linux user cgable and add him to the development group; also pick up GID, if it exists:

account -N development cgable

Edit a user’s home directory for login:

account -m -H /home/panmgr cgable

Delete user account cgable and remove the /home/cgable directory:

account -r -R cgable

Add the group called production:

account -aG production

Add user cgable to the production group:

account -m -N production cgable

RETURN VALUE On success, returns 0. On error, returns 1.

AUTHOR Egenera, Inc.

SEE ALSO UMON

ROLE

PAN

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_pan).

APP

PM5.2_BF 2-7

APP

NAME app - creates, lists, or modifies an application configured to run under PAN Manager control.

SYNOPSIS app [-c] [-L description] [-A {yes|no}] [[-a filesystem] [-G nfs_resource] [-I IPresource] [-N executable {-B {yes|no} |-S {yes|no}|-E {yes|no}}] [-o order]] [-V "name=value"] [-F failoverpolicy] [-H healthmon -j IPresource] [-P primary_pservername] lpanname/application

app [-k newname] [-F failoverpolicy |-e] [[-I |-i] IPresource] [-H monitorname -j IPresource |-h monitorname] [[-G |-g] nfs] [[-a |-r] filesystem] [[-N |-n] executable] [-o order] [-V "name=value" |-v name] [-p] lpanname/application

app [-b | -d | -m [pservername] |-s [-f]] lpanname/application

app [-l] lpanname[/application]

app -R executable lpanname/application

app --add-monitor monitorname lpanname/application

app --remove-monitor monitorname lpanname/application

app -M monitorname -U eventname -Q {failover|restart|none} lpanname/application

DESCRIPTION The app command configures a stand-alone application to run under PAN Manager control, for high availability. After you create a SCSI filesystem, a network resource, a health monitor, a failover policy, an executable resource, an NFS mount point, a failover policy, or a load-balancing service in an LPAN, use the app command to choose the dependencies and policies for an application with the appropriate option.


2-8 PM5.2_BF




lpanname/app_name

This is a reference to a high–availability application running on the primary pServer you create using the app command. (To maintain high availability within an LPAN, you must specify the LPAN in which you would like the application to run.) PAN Manager naming conventions require that you use a '/' between the LPAN name and the application name. For example, specify the application Webserver1 in the production LPAN as production/Webserver1. PAN Administrators use the lpan command to name LPANs.

monitorname

Specifies a PAN Manager user-defined monitor.

OPTIONS --add-monitor monitorname

Associates a user-defined monitor with the specified application. LPAN Administrators use the PAN Manager umon command to create user-defined monitors.

-a, --add-filesystem lpanname/application

Designates a SCSI filesystem resource disk to mount for a high–availability application’s physical resources to access using PAN Manager software.

-A, --autostart {yes|no}

Specifies whether an application starts when the pServer boots and the PAN agent is available. By default, this is set to “no.”

APP

PM5.2_BF 2-9

-b, --start lpanname/application

Manually starts all stand-alone application resources. This option is required to start an application after the stand-alone configuration has been created and the LPAN is booted.

-B, --exeres-start {yes|no}

Determines whether to start the specified executable resource on the pServer when the application starts. The LPAN Administrator can start all resources (for example network resources or SCSI file system resources) without starting the executable resources to help install or debug an application.

-c, --create lpanname/application

Creates the application specified.

-d, --delete lpanname/application

Deletes the specified stand-alone application from an LPAN.

-e, --reset-failover

Removes the current failover policy from an application.

-E, --exeres-execute {yes|no}

Determines whether or not users can run the specified executable resource on the pServer after the application starts and before the application stops.

-f, --force

Forces an application to stop. This option can only be used with the -s (stop) option.

-F, --set-failover failoverpolicy

Assigns a failover policy to an application. When specifying a failover policy, use only a failover policy set to use a pServer configured to run this application.

-g -- remove-nfs nfs_resource

Removes a network file system resource.


2-10 PM5.2_BF

-G --add-nfs nfs_resource

Adds a network file system resource and configures it to run under PAN Manager control for high availability.

-h, --remove-healthmonitor monitorname

Removes the specified health monitor from an application.

-H, --add-healthmonitor monitorname

Assigns a health monitor to an application.

-i, --remove-ipresource IPresource

Removes the specified network resource from an application.

-I, --add-ipresource IPresource

Assigns a network resource to an application.

-j, --assign-hmon-ipresource hmon-associated IPresource

Assigns a network resource to a health monitor. You must specify the network resource that the health monitor uses before assigning a health monitor to an application. The network resource must already be assigned to the application.

-k,--rename newname

Renames the specified application.

-l, --long

Lists detailed information about each stand-alone application within an LPAN, such as status, configuration, and its resources.

-L, --description "text"

Adds descriptive information about the specified application.

-m, --move pservername

Moves an application to the specified pServer. Using this option without the pservername argument moves the application to the pServer set in the current failover policy. To use this option without

APP

PM5.2_BF 2-11

an argument, create a failover policy with the fop command, using a pServer configured to run this application.

-M, --monitor monitor_name

Specifies an existing user-defined monitor that has already been added to the application. LPAN Administrators use the --add-monitor option to add user-defined monitors to the application.

Use this option with the -U (event) and -Q (set-event-action) options to configure a user-defined monitor event and specify actions for a specific user-defined monitor for this application.

-n --remove-exeres executable_resource

Removes the specified executable resource.

-N --add-exeres executable_resource

Assigns a specified executable resource to the application.

-o, --order resource_order

Specifies an order in which you want this application to use specified resources, if you need to specify the order in which resources start.

-p, --remove-primaryserver primarypservername

Dissociates the specified pServer from an application.

-P, --primaryserver primarypservername

Assigns a pServer within a specified LPAN to run the specified application.

-Q, --set-event-action {failover|restart|none}

Specifies an action to take if a user-defined monitor triggers an event.


2-12 PM5.2_BF

-r, --remove-filesystem filesystem

Removes a SCSI filesystem resource for a specified stand-alone application.

--rremove-monitor monitorname

Dissociate a user-defined monitor from the specified application.

-R, --run-exeres executable_resource

Runs an executable resource that can be invoked by an administrator at any time after an application has started and before it has stopped.

--remove-monitor monitor_name

Removes the specified user-defined monitor from an application.

-s, --stop lpanname/application

Manually stops the specified stand-alone application. Use this option to shut down a stand-alone application or to stop resources, instead of halting the application from within its pServer.

-S, --exeres-stop {yes|no}

Determines whether or not to stop the specified executable resource on the pServer when the application stops.

-U, --event event_name

Configures a user-defined monitor event. LPAN Administrators use this option in conjunction with the -M (monitor) and -Q (set-event-action) options to configure an action for the specified event.

-v, --remove-variable variablename

Removes the environment variable.

-V, --add-variable {"name=value"}

Creates an environment variable name and value (such as VMWARE_CONFIG and /vmware_mnt/linux/linux.cfg). This makes the application associated with this environment variable

APP

PM5.2_BF 2-13

available for all executable resources and user-defined monitors executed on the pServer.

EXAMPLES The following example configures an instance of Apache to run under PAN Manager control with the following settings:

LPAN name: development

Application name: Apache1

Primary pServer: Web1

Use the following resources already configured:

Filesystem: Apache_fs

Failover policy: Apache_failover

IP resource: Apache_IP

Health monitor: Apache_health

Executable resource: Apache_exe

app -c -a Apache_fs -P Web1 -F Apache_failover -j -H Apache_health -I Apache_IP -N Apache_exe development/Apache1

Start the Apache1 application:

app -b development/Apache1

Move this application from its current pServer to one listed in the Apache_failover policy:

app -m development/Apache1

Stop this application:

app -s development/Apache1


2-14 PM5.2_BF



SEE ALSO EXERES

FOP

FS

HMON

INTNET

IP

LPAN

NFS

PSERVER

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_lpan).

BFRAME

PM5.2_BF 2-15

BFRAME

NAME bframe - lists hardware and configuration information about a specified platform and modifies its power settings.

SYNOPSIS bframe [-l] [platformname]

bframe [-n newname {oldname}]

bframe [-s |-x][-f][-T "min" -M "textmessage"] [platformname]

[??Is the following line true for BX900? (It *was* Dell only.)]

bframe [-c control_password] control_password

bframe [-W {16|20|24|30}] [platformname]

bframe [-U {200|208|210|216|220|230|240}][-P {"separate"|"AC-BD"}] [platformname]

DESCRIPTION The bframe command lists the status of a specified platform within the PAN administrative domain. Administrators use the bframe command to do the following:

• Configure PAN Manager support for power management.

• Shut down or reboot a specified platform.

Note: Shutting down a platform shuts down all the servers running on it, and then the two cBlades. Rebooting a platform brings back the last configuration before it was shut down.

• Display the status, power configuration, processor configurations, blades, and current usage details of a platform.All users can display this information.


2-16 PM5.2_BF




platformname

Specifies a platform.

We recommend that you rename a platform to something specific to your application. This name is used in arguments when you issue the eth, pserver, pool, reth, role, and blade commands.

OPTIONS [??Is the following true for BX900? If not, is there a BX900 equivalent?]

-c, --control-password control_password

Configures the Dell PAN System for Blades hardware CMC password for SSH communication.

-f, --force

Forces a bframe operation without a prompt. You can use -f with the -s (shutdown) or -x (reboot) options

-g, --suggest-frame-id

Requests PAN Manager to suggest a unique platform ID (BFID) for the current platform by discovering all platforms on the local network and then picking an ID that is not in use.

-I, --set-frame-id BFID

Sets a new platform ID (BFID).

BFRAME

PM5.2_BF 2-17

-l, --long

PAN Administrators use this option to list the status, serial numbers, processor configuration, and current usage in LPANs for each of the platform’s physical blades and vBlades. Also displays FRU data such as BMC, BIOS, and CMOS revs. The output displays only populated chassis slots to which the user has access.

PAN Administrators use this option to list the status, serial numbers, processor configuration, and current usage in LPANs for each of the platform’s physical blades. Also displays FRU data such as BMC, BIOS, and CMOS revs. The output displays only populated chassis slots to which the user has access.

-M, --message "text"

Specifies an optional warning message to be displayed before a platform is shut down. PAN Administrators can use this option to provide details to PAN Operators and PAN Monitors of how long before a shutdown will occur. PAN Administrators use this option after the -s (shutdown) option.

-n, --rename newname oldname

Allows a PAN Administrator to rename the specified platform.

-P, --power-domain {"separate"|"AC-BD"}

Specifies whether a platform is configured with four power domains or combined into two power domains (requires Y-cables). Use separate to configure four separate power domains; use AC-BD to combine power domains. (This option does not apply to BladeFrame BF200 systems.)

-s, --shutdown platformname

Gracefully shuts down all pServers, LPANs, and hardware in this order (Slave, then Master cBlade). PAN Administrators use this option with the -T (time) and -M (message) options to create a conditional shutdown.


2-18 PM5.2_BF

Note: When you use the bframe -s option to power down a platform, the entire platform, including switches, is gracefully powered off. To power back on, you must flip the breaker switches on domains A and B. If you insert a cBlade and attempt to boot it without first cycling these switches, it will fail to boot with a “switches broken or missing” kernel panic message.

[??Does the following note apply to BX900?]

Note: When you use the bframe -s option to power down a platform, the blades are gracefully powered off. To power back on, press the power toggle (I/O) on each cBlade.

-T, --time number_of_minutes

Specifies an interval of time (in minutes) before the blades of a platform begin to shut down. PAN Administrators use this option after the -s (shutdown) option.

-U, --power-input {200|208|210|216|220|230|240}

Specifies the power input voltage to the platform. By default the power input is configured for 200 Volts. PIM-R power line failover is automatically calculated to be 85% of the configured voltage. For systems with PIM-Rs, the default value is 200 volts; for this configuration, PAN Manager initiates a failover to the second power line if the primary line voltage drops to 170 volts or lower (85% of 200).

-W, --bladeplane {16| 20 24|30}

Specifies whether the BladePlane is configured as 16, 20, 24, or 30 Amperes. By default the BladeFrame BF400 S2 BladePlane is configured for 20 Amperes.

-x, --reboot platformname

Reboots a platform.

BFRAME

PM5.2_BF 2-19

Note: The last configuration of a pServer is rebooted. This means that previously booted LPANs reboot, and if a pServer was running on a failover pBlade, the pServer reboots using either the specified failover pBlade or the first available pBlade in the failover pool when the reboot occurs.

EXAMPLES View the current state of the pBlades and cBlades on the platform:

bframe

View the current state of both cBlades:

bframe | grep ^c

Change the platform name from the default, MyBladeFrame, to PlatformOne:

bframe -n PlatformOne MyBladeFrame

For the PlatformOne platform, set the power input voltage to 220 and the BladePlane amperage to 30 from the default settings of 200 and 24, respectively (this also sets the failover voltage target to 187 volts if the system utilizes PIM-Rs):

bframe -W 30 -U 220 PlatformOne



SEE ALSO BLADE

EVENTTYPE

LPAN

PAN

PIM

POOL


2-20 PM5.2_BF

PSERVER

ROLE

SNMP


BLADE

PM5.2_BF 2-21

BLADE

NAME blade - Lists or controls one or more specified cBlades, pBlades, or sBlades (the BladeFrame BF200 does not have an sBlade).

blade - Lists or controls one or more specified blades.

SYNOPSIS blade [-l] platformname/[cn|sn|pn]

blade --boot-hypervisor [-I image_name] {platformname/pn}

blade --list-vblades [-l] [platformname/pn[-n]]

blade --config-hypervisor [-I image_name] {platformname/pn}

blade --unconfig-hypervisor {platformname/pn}

blade [--notify-slave-hypervisor| --promote-to-master-hypervisor]{platformname/pn}

[??Is the following true for BX900?]

blade -d platformname/pn-n

blade -h hostname platformname/cn

blade [--select|--unselect |-i |-o] [-l] {platformname/[cn|sn|pn]}

blade -n {platformname/[pn |cn |sn]}

blade -n platformname/{cn |pn}

blade [--cpu-cap cap_percentage][ -p {"lowest" | "low" | "normal" | "high" | "highest"}] platformname/pn[-n]

blade [-c][-M RAMvalue {"Gb"|"Mb"}] [-P cpu_number] [-p {"lowest" | "low" | "normal" | "high" | "highest"}] platformname/pn-n

blade [-c][-M RAMvalue {"Gb"|"Mb"}] [-P cpu_number] [-p {"lowest" | "low" | "normal" | "high" | "highest"}]


2-22 PM5.2_BF

platformname/pn

blade

blade [-D] platformname/pn

blade [-R] platformname/pn

blade {-b |-s |-x} [-w] [-l] [-f] {platformname/pn[-n] | platformname/cn}

blade {-b |-s |-x} [-w] [-l] [-f] {platformname/pn | platformname/cn}

blade {-b |-s |-x} -S [-w] [-f] platformnameES/cn

blade [-W | -C] platformname/pn

DESCRIPTION The blade command lists information about a specified blade and allows you to perform diagnostic operations. Administrators use the blade command to do the following:

• Power on or off any blade in a platform.

• Diagnose problems associated with hardware or a system hang traced to a specific blade.

• Create or delete a vBlade configuration on a pBlade.

• Recover a hypervisor group from recovery mode.

• Configure, unconfigure, boot, and shutdown a hypervisor instance running on a pBlade.

• Modify the cBlade hostname.

• Place a pBlade into or remove it from the maintenance LPAN (.maint).

Caution: Use of the blade command can make a blade unavailable to its LPAN. If the LPAN has failover actions defined for this blade, those actions could be triggered, affecting applications and other blades running in that LPAN. We recommend notifying LPAN Administrators that a blade in their LPAN is being diagnosed, so they are prepared in the event that a specified blade is shut down, rebooted, or marked unused by PAN Manager software.

BLADE

PM5.2_BF 2-23




platformname/{cn | sn | pn | pimn}

Specifies a platform and a specific blade or redundant Power Input Module (PIM-R).

platformname/{cn|sn|pn}

PAN Manager naming conventions require you to use a forward slash (/) between the platform name and the blade name. For example, pBlade 2 on the platform named production would be referred to as production/p2. pBlades are numbered as follows:

• From their slot locations 1 through 24 from the bottom up for BladeFrame BF400 S2.

• From their slot locations 1 through 6 from the left for BladeFrame BF200.

[??The following is TBD for BX900.]

• From their slot locations, 1 through ??.

platformname/pn-n

Specifies a vBlade (of a particular pBlade), preceded by the platform on which it is located. PAN Manager naming conventions require you to use the format pn-n to specify the vBlade name, where:

• pn is the name of the pBlade (such as p5) that hosts this vBlade

• - (hyphen) is a required separator


2-24 PM5.2_BF

• n is a number (from 1 to 32) that uniquely identifies this vBlade on its pBlade.

OPTIONS -b, --boot platformname/{pn[-n] | cn}

-b, --boot platformname/{pn | cn}

Powers on the specified blade. You do not need to use this option initially. Use this command option to power on and boot a specified blade that you manually shut down or powered off. PAN Administrators can use this option with the -w (wait) option to cause the PAN Manager command line prompt not to return until this operation is complete.

--boot-hypervisor [-I image_name] platformname/pn

Specifies that you want to power on the target pBlade and boot a hypervisor (in preparation for running vBlades on that pBlade). PAN Manager follows these rules to determine which hypervisor to boot on the pBlade:

• If you specify a hypervisor ISO image name in this command, PAN Manager boots the hypervisor from that image.

• If you omit the image name in this command, PAN Manager tries to obtain the hypervisor ISO image to use from the following:

a. current hypervisor configuration of the pBlade (if any)

b. default hypervisor ISO image of the PAN (if any)

If PAN Manager can’t obtain a hypervisor ISO image, it displays an error message.

-c, --create-vblade {platformname/pn-n}

Specifies that you want to create a vBlade on a specified pBlade. The target pBlade slot must be filled in order for this command to be valid. LPAN Administrators can use this option with the -M (memory) and -P (CPUs) options to set configurations on this vBlade.

BLADE

PM5.2_BF 2-25

-C, --cool platformname/pn

Turns off the power for a failover pBlade that you have designated as warm using the -W (warm) option.

--config-hypervisor {platformname/pn}

Specifies that you want the target pBlade to be configured with a hypervisor (in preparation for running vBlades on that pBlade). Including this option without a hypervisor ISO image name tells PAN Manager to use the default hypervisor ISO image PAN Administrators set with the PAN Manager command pan --set-default-hypervisor-image image_name. If no default hypervisor ISO image is currently set, PAN Manager displays an error message.

To specify a hypervisor ISO image name instead of using the default, LPAN Administrators must combine this blade command option with the -I (image_name) option.

--cpu-cap cap_percentage {platformname/pn[-n]}

Specifies the maximum percentage of CPU time you want the hypervisor to give to the specified blade. If you specify a pBlade (using pn), you set the limit for the hypervisor management domain; if you specify a vBlade (using pn-n), you set the limit for a pServer booted on that vBlade. The default is 0 (no limit).

You set the cap_percentage in terms of percentages of CPU time expressed as an integer. For example, 50 indicates that the vBlade can consume up to half a physical CPU; 200 indicates 2 CPUs, and so on.

Setting a CPU cap only takes effect when a hypervisor is booted on the pBlade; it has no effect on a pBlade pServer.

-d, --delete-vblade {platformname/pn-n}

Deletes the vBlade on a specified pBlade. Specifies that you want to remove the target vBlade from its pBlade. LPAN Administrators can delete a vBlade only when the specified pBlade slot is filled,


2-26 PM5.2_BF

the vBlade is not currently assigned to a pServer configuration or used by a running pServer, and the vBlade is not currently assigned to a blade pool.

-D, --set-maintenance platformname/pn

Marks the pBlade for a maintenance task. This places the pBlade in the maintenance LPAN (.maint), but does not remove the pBlade from the LPAN and pServer, if any, in which it is already configured. This option assumes the pBlade is currently in an Out of Service state (blade -o).

-f, --force

Forces a cBlade operation without a prompt. This option requires a -b (boot), -s (shutdown) or -x (reboot) option. Used with the -s or -x option, forces a cBlade shutdown with no attempt to do it gracefully. You cannot combine this option with sBlade, pBlade, or vBlade operations.

Forces a cBlade operation without a prompt. This option requires a -b (boot), -s (shutdown) or -x (reboot) option. Used with the -s or -x option, forces a cBlade shutdown with no attempt to do it gracefully.

-h, --hostname platformname/cn

Allows a PAN Administrator to change the default cBlade hostname (control-blade-A and control-blade-B) to something more meaningful.

-i, --in-service platformname/{pn | cn | sn}

Indicates that you want to assign In Service status to a specified specified blade. In normal start-up mode, PAN Manager automatically marks a blade as In Service, so there is no need to use this option initially. Use this command when you need to toggle a specified blade status from Out of Service to In Service.

Placing a blade In Service powers it on. In many cases this results in the blade automatically booting.

BLADE

PM5.2_BF 2-27

-I, --media-image image_name

Specifies the display name of a particular hypervisor ISO image (as registered in the PAN under media images) to override the default hypervisor ISO image. To view a list of the registered hypervisor ISO images and their display names, use the PAN Manager command pan -i.

-l, --long [platformname/{pn[-n] | cn | sn}]

-l, --long [platformname/{pn | cn | sn}]

Lists information about a specified blade or all the blades in a platform. Information includes FRU data such as architecture, and BMC, BIOS, and CMOS revs.


Note: A display of N/A or None means that the INFORMATION about the property is not available. The FUNCTIONALITY is available.

Note: A display of N/A or None means that the FUNCTIONALITY about the property is not available.

--list-vblades platformname/pn[-n]

Specifies that you want to display information about vBlades only (not pBlades). LPAN Administrators can combine this option with the -l (long) option to request a long version of the listing, with details about the specified vBlade(s).

-M, --mem RAMvalue {"Gb"|"Mb"} platformname/pn-n

Specifies how many GB or MB of RAM of the pBlade to allocate to this vBlade. LPAN Administrators can combine this option with the -c (create-vblade), -p (priority), -P (cpus) options when you create a vBlade. You can also use this option to modify the memory allocation of this vBlade. If you omit this option, the default value of 512MB is used. For details on valid values for this option, see the list of restrictions in the “About vBlades” chapter in the PAN


2-28 PM5.2_BF

Manager Administrator’s Guide. If PAN Manager encounters a problem with your vBlade memory allocation, it displays an error message.

--notify-slave-hypervisor platformname/pn

Specifies that you want to notify the target pBlade hypervisor about a new master hypervisor for the group (set using the lpan --group-hypervisors lpanname command) following the recovery of a hypervisor group. LPAN Administrators must perform this command individually for each remaining slave in the hypervisor group. For more details on using this option, see the PAN Manager Administrator’s Guide.

-n, --nmi {platformname/pn | platformname/cn | platformname/sn}

-n, --nmi platformname/{cn | pn}

Sends a non–maskable interrupt (NMI) to a specified blade for diagnostic purposes. This NMI causes the blade to behave as if it had a panic. By default, a panic causes a pBlade to dump core memory and reboot. Use the following entry from a terminal on the specified pBlade to change the behavior to reboot-only:

#echo "reboot" > /proc/egenera/panic

To return the behavior to dump and reboot, use the following entry:

#echo "dump" > /proc/egenera/panic

You can also include this command in a start-up script.

-o, --out-service platformname/{pn | cn | sn}

Indicates that you want to assign Out of Service status to a specified blade. This option marks the specified blade not to be used, even though it remains listed in its configuration definitions. Use this option when you want a specified blade to be left idle, but you do not want to edit configuration definitions.

BLADE

PM5.2_BF 2-29

For example, if you have assigned a pBlade to an LPAN, but the LPAN Administrator does not want to use the pBlade, you can shut down the LPAN, mark the pBlade Out of Service, and then reboot the LPAN. To return the specified blade to service, use the -i (in-service) option to mark the blade In Service.

-p, --priority {"lowest" | "low" | "normal" | "high" | "highest"} platformname/pn-n

Specifies a CPU priority for a vBlade relative to the other vBlades (using the vBlade argument pn-n) or the management domain on that pBlade (using the pBlade argument pn). LPAN Administrators can combine this option with the -c (create-vblade), -M (memory), -P (cpus) options when you create a vBlade. You can also use this option to modify the CPU priority for a vBlade relative to the other vBlades or the management domain on that pBlade. For details on changing the priority setting, see the PAN Manager Administrator’s Guide.

-P, --cpus cpu_number platformname/pn-n

Specifies how many CPUs to allocate to this vBlade. These are virtual CPUs (which the underlying hypervisor maps to the pBlade physical CPUs). LPAN Administrators can combine this option with the -c (create-vblade), -p (priority), -P (cpus) options when you create a vBlade. You can also use this option to modify the number of CPUs allocated to this vBlade. For details on valid values for this option, see the PAN Manager Administrator’s Guide.

--promote-to-master-hypervisor platformname/pn

Specifies that you want to promote the target pBlade hypervisor from slave to master status in its hypervisor group (set using the lpan --group-hypervisors lpanname command). LPAN Administrators must perform this command to recover a hypervisor group from recovery mode.For more details on using this option, see the PAN Manager Administrator’s Guide.


2-30 PM5.2_BF

-R, --unset-maintenance platformname/pn

Unmarks the pBlade for a maintenance task. The pBlade must not be configured on any pServers in the maintenance LPAN. This removes the pBlade from the maintenance LPAN.

--rediscover platformname/pn

Instructs PAN Manager to reboot the specified blade and set the blade to boot from its disk. You use this command on new pBlades you are installing into an existing system only after you initially allow PAN Manager to discover the pBlade with its hard drive uninserted. Rediscovery is required after PAN Manager initially discovers the blade and has powered off the pBlade.

To rediscover the pBlade, you must reinsert the drive into the unbooted blade (note the slot number into which the pBlade is inserted) and use this command option with the platformname/pn argument.

-s, --shutdown platformname/{pn[-n] | sn | cn}

-s, --shutdown platformname/{pn | cn}

Indicates that you want to power off the specified blade. This option immediately shuts down any pServer(s) or hypervisor currently running on the pBlade or vBlade.

Indicates that you want to power off the specified blade. This option immediately shuts down any pServer(s) currently running on the pBlade.

However, on a cBlade, it initiates a graceful shutdown of a cBlade and all its processing (the equivalent of the Linux shutdown -h command), due to the severe consequences of powering off a cBlade. A graceful shutdown requires that PAN Manager is running on the other cBlade and is communicating with the master cBlade.

If you want to force a cBlade shutdown without attempting to do it gracefully, add the -f (force) option. PAN Administrators can use this option with the -w (wait) option to cause the PAN Manager command line prompt not to return until this operation is complete.

BLADE

PM5.2_BF 2-31

-S, --switch-comp

Specifies the switch component on the BladeFrame BF200 cBlade. PAN Administrators can use this option with the -w (wait) option to cause the command line prompt to not return until this operation is complete.

--select platformname/{pn | cn | sn}

Causes the indicator lights on a specified blade to blink blue. We recommend using this feature to help locate a specific blade in the chassis. The blinking blue indication persists until reset with the --unselect option.

Causes the indicator lights on a specified blade to blink either green or amber, depending on the blade. This option helps you to physically locate a specified blade. The blinking LED indicator persists until reset with the --unselect option.

--unconfig-hypervisor {platformname/pn}

Specifies that you no longer want the target pBlade to be configured with a hypervisor. As a result, this pBlade will not boot up into the hypervisor (unless PAN Manager does that automatically in response to pServer boot or failover demands for vBlades defined on the pBlade). A pBlade without a hypervisor can be used to boot a regular pServer, but it doesn’t support vBlades. You can unconfigure a hypervisor on a pBlade only when that pBlade is shut down.

--unselect platformname/{pn | cn | sn}

Terminates the blinking blue indication on a “selected” blade. The indicator lights on the blade revert to their normal meaning: steady amber for recognized, steady blue for active.

Terminates the blinking green indication on a “selected” blade. The indicator lights on the blade revert to their normal meaning: steady amber for recognized, steady green for active.


2-32 PM5.2_BF

-w, --wait

Causes the blade command to pause while a boot or shutdown process is underway, and displays a progress indicator. Use this option with the -b (boot), -s (shutdown), or -x (reboot) options when you would like to suspend command-line operations until the boot or shutdown is completed.

-W, --warm platformname/pn

Allows a failover pBlade to boot more rapidly when a failover occurs by designating it in advance as a warm pBlade. A warm pBlade is powered ON, and is bootable only when it becomes the current pBlade of a pServer.

-x, --reboot platformname/{pn[-n] | sn | cn}

-x, --reboot platformname/{pn | cn}

Resets and reboots the specified blade. PAN Administrators can use this option with the -w (wait) option to cause the command line prompt not to return until this operation is complete.

EXAMPLES List the details for pBlade p7 (on platform zeus):

blade -l zeus/p7

Power off pBlade p7 (on platform zeus), which shuts down the pServer currently running:

Power off pBlade p7 (on platform zeus), which shuts down the pServer or hypervisor currently running:

blade -s zeus/p7

Power off vBlade p7-3 (on platform zeus):

blade -s zeus/p7-3

Reset and reboot pBlade 3 (on platform PlatformOne):

blade -x PlatformOne/p3

BLADE

PM5.2_BF 2-33

Mark pBlade 14 In Service (on platform PlatformOne):

blade -i PlatformOne/p14

Set the indicator light to blink blue on cBlade 1 (on platform production):

blade --select production/c1

Set the indicator light on cBlade 1 to its normal meaning (on platform production):

blade --unselect production/c1

Configure pBlade p7 (on platform zeus) to use the default hypervisor ISO image:

blade --config-hypervisor zeus/p7

Configure pBlade p7 (on platform zeus) to use the hypervisor ISO image named HV30002005_IA32:

blade --config-hypervisor -I HV30002005_IA32 zeus/p7

Unconfigure the hypervisor from pBlade p7 (on platform zeus):

blade --unconfig-hypervisor zeus/p7

Power on pBlade p7 (on platform zeus) and boot the hypervisor from the hypervisor ISO image named HV30002005_IA32:

blade --boot-hypervisor -I HV30002005_IA32 zeus/p7

Create vBlade 1 on pBlade p7 (on platform zeus), allocating the default amount of memory to 512MB and number of CPUs to 1:

blade -c zeus/p7-1


2-34 PM5.2_BF

Create vBlade 2 on pBlade p7 (on platform zeus), and allocate 256 MB of memory and 2 CPUs for it:

blade -c -M 256"Mb" -P 2 zeus/p7-2

Modify vBlade 1 on pBlade p7 (on platform zeus) to allocate 1 GB of memory:

blade -M 1"Gb" zeus/p7-1

Modify vBlade 2 on pBlade p7 (on platform zeus) to allocate 128 MB of memory and 1 CPU for it:

blade -M 128"Mb" -P 1 zeus/p7-2

Delete vBlade 2 on pBlade p7 (on platform zeus):

blade -d zeus/p7-2

List all of the vBlades in the PAN:

blade --list-vblades

For the LPAN’s hypervisor group, promote the slave hypervisor on pBlade p7 (on platform zeus) to be group master, enter:

# blade --promote-to-master-hypervisor zeus/p7

For the LPAN’s hypervisor group, notify the slave hypervisor on pBlade p3 (on platform zeus) about the new group master, enter:

blade --notify-slave-hypervisor zeus/p3



SEE ALSO BFRAME

BLADE

PM5.2_BF 2-35

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_bframe).


2-36 PM5.2_BF

CONSOLE

NAME console - opens a terminal session on a pServer.

SYNOPSIS console [lpanname/pservername]


console -s [lpanname/pservername]

DESCRIPTION The console command opens a Linux console device on a pServer. Entering the console command without an argument displays a list of initialized or booted pServers to choose from; if you enter the console command with a valid pServer argument, the console opens immediately.

The PAN Manager console initiates a terminal session and sends standard input to the pServer console. The pServer console output is displayed as the standard output. A PAN Manager console normally translates the inputs for sigint (Control-C), sigquit (Control-/), and sigtstp (Control-z).

To abort a pServer console, press Enter once and type a tilde character (~) followed by a period (.). There is a one–second pause after typing the tilde character in which to type the period; if the "." is not typed within one second, the abort sequence is terminated. If both characters in the sequence (~.) are not typed within one second, the sequence is not sent to the pServer (thus not echoed) and the pServer connection is aborted.

Issues to be aware of when using the console command include:

• Once opened, a pServer console remains opened until it is aborted, even after the pServer is shut down.

CONSOLE

PM5.2_BF 2-37

• In the case of certain network communication errors, you may need to re-establish a pServer console. An administrator can open a console on a pServer to watch the pServer's output as it boots if it has been previously booted.

• Opening a console on an uninitialized or unbooted pServer opens the console late which means you may miss the first few seconds of booting.

OPTIONS [??Is the following option supported in BX900?]

-s,--serial console

Initiates a serial console on a pBlade pServer.

Without an argument this option displays a list of initialized or booted pServers to which you have permission to connect. If you enter the console -s command followed by a valid pServer argument, a serial console opens immediately.

None.



SEE ALSO PSERVER

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_pServer).


2-38 PM5.2_BF

DISK

NAME disk - controls or lists operations on a disk physically connected to a PAN and recognized by PAN Manager software by means of the sfdisk utility.

SYNOPSIS disk [-l] [-A |-C |-U |"(SCSI_ID)"]

disk -z {yes|no} "(SCSI_ID)"

disk -v {yes|no} [-n][-f] "(SCSI_ID)"

disk -c [-n] "(SCSI_ID)"

disk -b "(SCSI_ID)"

disk -L "text" "(SCSI_ID)"

disk -p [part_table_filename] "(SCSI_ID)"

disk -R [-P partition] [-r root_image_name [-F fs_type]][-g] "(SCSI_ID)"

disk -W [-S partition-size] [-I ip-address -G gateway -M subnet-mask] "(SCSI_ID)"

disk --clear-suspend-disk "(SCSI_ID)"

Synopsis Deprecations for Release 5.2

The WinPE 2.1 method automatically partitions the disk, therefore the following PAN Manager disk command for partitioning a disk is deprecated in Release 5.2. For information on using WinPE, see the pServer Guide for Microsoft Windows Server 2003. The following disk command options should be removed from any scripts.

disk -W [-S partition-size] [-I ip-address -G gateway -M subnet-mask] "(SCSI_ID)"

DESCRIPTION The disk command allows you to list, modify and control certain operations on a specified disk that is physically connected to the PAN. Administrators use the disk command to do the following:

• Configure disk resources.

DISK

PM5.2_BF 2-39

• Partition disks on remote storage devices.

• Choose root images and filesystem types for disks, and create a root filesystem on disks allocated to an LPAN.

• Specify a default filesystem type for each pServer disk in an LPAN.

• Control persistent reservations.

• Configure Linux GRand Unified Bootloader (GRUB) functionality when assigning a Linux-based root filesystem.

PAN Administrators should use the san and tape commands to scan a Storage Area Network (SAN) for recently added disks and tape devices after the cBlades of a platform are initially booted.

PAN Administrators use the disk command to list information about any disk available to a PAN, while LPAN Administrators can only list information about disks allocated to their LPAN. Administrators use the disk command without arguments to see all the disks available to their administrative domain, or the disk -l command to see details about these disks. See the -l (long) option for details.

After PAN Administrators allocate disk(s) to an LPAN using the lpan command, LPAN Administrators configure their disk resources using the disk command.

LPAN Administrators use the disk command to partition disks. The disk command uses the Linux sfdisk command to create partitions on remote storage devices. PAN Manager software requires a specific format for the information it uses to create disk partitions. The default partition in /opt/panmgr/etc illustrates the information required. Other examples of partition files are located in the directory /opt/panmgr/examples.

For more information about disk partitioning see the OPTIONS or PAN Manager Administrator’s Guide.


2-40 PM5.2_BF




"(SCSI_ID)"

Specifies a PAN Manager SCSI ID of a device for a SAN storage array disk device rather than a subpath SCSI ID of the device. When specifying a SCSI device name, use the convention "(w.x.y.z)" where:

• The SCSI_ID is enclosed in parentheses and quotation marks.

• w is a cBlade-kernel-generated pseudo-device reference to a unique multipath ID.

• x is the PATH_GROUP ID.

• y is the target ID of the storage array device attached to the cBlade (variable when there are multiple storage arrays).

• z is the LUN residing on target 1.

OPTIONS -A, --all-disks

Displays all PAN and non-PAN discovered disks.

-b, --list-persistent-reservations "(SCSI_ID)"

Lists pServer registrations and persistent reservation information for a specified disk.

--clear-suspend-disk "(SCSI_ID)"

Clears the specified SAN disk from suspending command-line operations.

DISK

PM5.2_BF 2-41

-c, --clear-disk-reservations "(SCSI_ID)"

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 configuration, stale SCSI reservations can persist and cause undesired application behavior. The clear operation removes all stale registrations and reservations (SCSI-3 and SCSI-2), but does not disable or enable persistent reservations.

This command fails if the disk is attached to a booted pServer. Use the -n option to force the command to complete even if the disk is mapped to a pServer and the pServer is booted.

-C, --configured-disks

Lists all disks configured in the PAN and provides the ID, disk capacity, type (of SAN), serial number, configured I/O paths, and the LPAN in which each is configured.

-f, --force

Causes the specified option to complete without a prompt from PAN Manager for the user to confirm the action.

-F, --file-system-type fs_type

Specifies which filesystem type is associated with a Linux-based root image. You can only use this option in combination with the -R (root-partition) and -r (root-image) options. To see the default filesystem for a root image, use the pan -il command.

-g, --install-grub

Specifies that you want PAN Manager to configure Linux GRUB (GRand Unified Bootloader) functionality as it assigns a Linux-based root filesystem to a specified disk device or partition on that disk device. You must use this option in combination with the -R (root-partition) option.

-l, --long

Adds partition and assignment information to the default information listing: SCSI ID, disk capacity (GB), Type (of SAN),


2-42 PM5.2_BF

serial number, and LPAN of allocation. This option adds disk partition table in a data format you can use as the basis for a new partition table file. You can edit and copy this data in any text editor.

-l, --long [“(SCSI_ID)”]

Lists information about a specified disk or all disks in the PAN.

-L, --description {"text"}

Sets the description for the specified disk as it is displayed in the long listing.

-n, --override-pr-restrictions

Forces the command to complete even if the disk is mapped to a pServer and the pServer is booted. Without adding this option to the -c (clear-disk-reservations) or -v (persistent-reservations) options, PAN Manager returns an error indicating that the disk is currently in use.

-p, --partition-disk "(SCSI_ID)"

Specifies a file that PAN Manager uses to create partitions on the specified disk. Use the default partition table information in /opt/panmgr/etc and /opt/panmgr/examples to format a partition table file that meets your exact needs. You can store these files anywhere on a cBlade.

Note: Use this option without an argument if you want PAN Manager software to create the default pBlade partition on the specified disk. Currently, there is no method to partition multiple disks using the disk command.

-P, --partition-number partition_number

Specifies an optional partition number on a disk device for a root filesystem assignment. By default, partition number one is rooted. You specify a partition number when rooting a disk using this option with the -R (root-partition) option.

DISK

PM5.2_BF 2-43

Caution: A root filesystem of a pServer must be autoenabled on the partition number you specify when rooting a disk. Thus the disk containing the partition with a root filesystem of the pServer must be autoenabled and the partition must be attached using the pserver -a "(SCSI_ID)" -A yes lpanname/pservername "(X.0)" command for the pServer to boot.

-r, --root-image root_image_display_name

Specifies the root image that an LPAN or PAN Administrator used to root a specified disk device. You can see the available list of root images and their default filesystems using the disk -l command. In the list of filesystems displayed, the first filesystem is the default. You must use this option with the -R (root-partition) option.

-R, --root-partition "(SCSI_ID)"

Assigns the specified disk with a Linux-based root filesystem. Invoking this option without arguments roots the disk with a default root image and filesystem for a given Linux operating system. To see the default root image and filesystem, use the disk -l command.

-U, --unconfigured-disks

Returns a list of disks that are not configured to an LPAN or to disaster recovery.

-v, --persistent-reservations {“yes” | “no”} ["(SCSI_ID)"]

Specifying “yes” with this option means PAN Manager enables SCSI-3 persistent reservations on a specified disk. If no “(SCSI_ID)” argument is used, PAN Manager enables SCSI-3 persistent reservations on all disks that are not attached to booted pServers in the PAN. PAN and LPAN Administrators should only enable SCSI-3 persistent reservations on disks used by applications that support SCSI-3 reservations, and disks used by pServers that have disk subpaths disabled. See PAN Manager Administrator’s Guide for specific requirements.


2-44 PM5.2_BF

When PAN Manager enables SCSI-3 persistent reservations on disks, PAN Manager also disables SCSI-2 reservations on those disks.

Specifying “no” means PAN Manager disables SCSI-3 persistent reservations on a specified disk. If no “(SCSI_ID)” argument is used, PAN Manager disables SCSI-3 persistent reservations on all disks that are not currently attached to booted pServers in the PAN. This enables SCSI-2 reservations on the disk(s).

SCSI_ID-z, --dr-disk {yes|no}

Allocates the specified disk for Disaster Recovery.

EXAMPLES Clear the SAN disk “(9.0.1.54)” from suspending command–line operations.

disk --clear-suspend-disk “(9.0.1.54)”

Partition disk “(9.0.0.32)” according to the file example1.part in the directory /opt/panmgr/examples:

disk -p /opt/panmgr/examples/example1.part “(9.0.0.32)”

Display the details of partition and assignment information for disk “(9.0.0.32)”:

disk -l "(9.0.0.32)"

Create a root filesystem with the default root image for the PAN administrative domain on disk “(9.0.0.32)”:

disk -R "(9.0.0.32)"

Create a root filesystem with the RHEL42_32bit_rootimage root image associated with the PAN administrative domain default filesystem on disk “(9.0.0.32)”:

disk -R -r RHEL42_32bit_rootimage "(9.0.0.32)"

DISK

PM5.2_BF 2-45



SEE ALSO BFRAME

LPAN

PAN

PSERVER



2-46 PM5.2_BF

ETH

NAME eth - creates, lists, or modifies the configuration for a physical Ethernet card on a cBlade.

SYNOPSIS eth [-l][ethn@platformname/{cn}]

eth -I ip_address -S subnet_mask {-H|-M mac_address}[-G gateway][-V vlan_id] ethn@platformname/{cn}

eth -R ping_ip_address [-C count_threshold -T milliseconds] ethn@platformname/{cn}

eth -c ethn@platformname/{cn}

DESCRIPTION The eth command allows administrators to do the following:

• Modify configurations of any physical Network Interface Cards (NICs) on a cBlade or sBlade of a platform.

After the configuration is created or modified using the eth command, PAN Administrators create virtual switches (vSwitches) using the sw command.

• Configure the PAN Manager Intelligent Network Failover feature.

This functionality allows administrators to configure rEths to report Ethernet device failures based on ping results (ping failover detection mode, or just “ping mode”). Default behavior is to detect such failures solely by the link status of the Ethernet device, called “link status mode”).

After configuring ping failover detection mode with the eth command, you use the reth command to turn the feature on and off (that is, to select “link status mode” or “ping mode”).

ETH

PM5.2_BF 2-47




ethn@platformname/cn

Specifies a device on a cBlade Network Interface Card (NIC). PAN Manager naming conventions require you to use a forward slash (/) between the platform name and cBlade number. For example ethn on cBlade 2 on the platform named production, would be referred to as ethn@production/c2.

The PAN Manager NIC naming conventions vary depending upon your platform. Use the eth -l command to list the details for your particular platform configuration.

Important: On a BladeFrame BF400 S2, a valid rEth consists of paired devices Eth1, Eth2, Eth3, Eth4, Eth15, Eth16, Eth17, and Eth18 on different cBlades; on a BladeFrame BF200, a valid rEth consists of paired devices Eth1 and Eth2 on different cBlades.


Important: A valid rEth consists of paired devices Eth6 or Eth7 on each cBlade.

OPTIONS -c, --clear-ping-configuration

Clears all ping failure detection mode settings. Allowed only when the rEth of the Ethernet device is set to link failover detection mode.


2-48 PM5.2_BF

-C, --count-threshold count_threshold

For ping failover detection mode, an integer that specifies the number of missed pings that determine a failure.

-G, --gateway ip-address

For ping failover detection mode, specifies the IP address of the network gateway.

-H, --hardware-mac-address

For ping failover detection mode, specifies that the Ethernet device will use its hardware MAC address, as opposed to a user-specified MAC address specified with the -M option.

-I, --ip-address ip-address

For ping failover detection mode, specifies the source (platform) IP address.

-l, --long

Lists information for each NIC on your cBlade, including each NIC type and MAC address. Also returns the ping detection mode settings of the Ethernet device when ping detection mode has been configured.

-M, --mac-addr mac-address

For ping failover detection mode, specifies that the Ethernet device will use a user-specified MAC address, rather than its hardware MAC address as specified with the -H option.

-R, --remote-ip-address ip-address

For ping failover detection mode, specifies the IP address of the remote device (the target of the ping).

-S, --subnet-mask subnet_mask

For ping failover detection mode, specifies the value with which to perform a bitwise AND operation on the IP address, to determine the subnetwork address.

ETH

PM5.2_BF 2-49

-T, --time-threshold milliseconds

For ping failover detection mode, determines the number of milliseconds (ms) to wait for a ping echo before determining that the target device has failed. The default ping threshold value is 5000 ms; the minimum ping threshold value is 1000 ms (1 second). A threshold value below 1000 ms is not valid. Note that the cBlade kernel rounds down the time-threshold value. For example, if you specify a value of 1098 ms, PAN Manager rounds the value down to 1090 ms.

EXAMPLES View details about all Ethernet device configurations on the platform:

eth -l

View the status of Ethernet device eth2 on c2 of the platform, production:

eth -l eth2@production/c2


View the status of Ethernet device eth7 on c2 of the platform, production:

eth -l eth7@production/c2

Clear all the uplink assignments on the NIC named eth3 on cBlade 1 of the production platform:

eth -d eth3@production/c1

Clear all the uplink assignments on the NIC named eth6 on cBlade 1 of the production platform:

eth -d eth6@production/c1


2-50 PM5.2_BF

Set the network stack for eth2 for ping failure detection mode. The source IP address is 192.68.5.32, the subnet mask is 255.255.240.0, the gateway is 192.68.5.100, and the hardware MAC address is used:

eth -I 192.68.5.32 -S 255.255.240.0 -G 192.68.5.100 -H eth2@PlatformOne/c2

Set the network stack for eth6 for ping failure detection mode. The source IP address is 192.68.5.32, the subnet mask is 255.255.240.0, the gateway is 192.68.5.100, and the hardware MAC address is used:

eth -I 192.68.5.32 -S 255.255.240.0 -G 192.68.5.100 -H eth6@PlatformOne/c2

Set a “ping mode” failure detection configuration for eth2. The ping target is 192.68.5.204, failure is determined by 5 unanswered pings, a ping is determined to have failed if no response is received after 1500 milliseconds:

eth -R 192.68.5.204 -C 5 -T 1500 eth2@PlatformOne/c2

Set a “ping mode” failure detection configuration for eth7. The ping target is 192.68.5.204, failure is determined by 5 unanswered pings, a ping is determined to have failed if no response is received after 1500 milliseconds:

eth -R 192.68.5.204 -C 5 -T 1500 eth7@PlatformOne/c2

Clear the “ping mode” failure detection configuration for eth2. For this command to return successfully, you must first disable “ping mode” for any rEth that uses eth2:

eth -c eth2@PlatformOne/c2

Clear the “ping mode” failure detection configuration for eth7. For this command to return successfully, you must first disable “ping mode” for any rEth using eth7:

eth -c eth7@PlatformOne/c2

ETH

PM5.2_BF 2-51

List the “ping mode” failure detection configuration for eth2, along with other information; “ping mode” settings are included in the output only if they have been configured for this device:

eth -l eth2@PlatformOne/c2

List the “ping mode” failure detection configuration for eth7, along with other information; “ping mode” settings are included in the output only if they have been configured for this device:

eth -l eth7@PlatformOne/c2



SEE ALSO BFRAME

IP

PSERVER

RETH

SW

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_sw).


2-52 PM5.2_BF

EVENT

NAME event - lists the details of an instance of a triggered event in a PAN.

SYNOPSIS event [-N [print_number]] [V |-v severity] [-E |-I |-i event_ID_number] [-T |-t timestamp] [-M messagekeyword] [-L number] [-S {"O"|"I"|"R"}] [-p lpanname[/pservername]|-b platformname/[cn|sn|pn] |-D "(SCSI_ID)"|-n ethn@platformname/cn]

event [-N [print_number]][[V |-v] severity] [[-E |-I | -i] event_ID_number] [-T |-t timestamp] [-M messagekeyword][-L number][-S {"O"|"I"|"R"}][-p lpanname[/pservername]|-b platformname[/pn |sn |cn |pimn] |-D "(SCSI_ID)"|-n ethn@platformname/cn]

event -u event_ID_number -S {"O"|"I"|"R"}[-a] | [[-V |-v severity] [-I |-i event_ID_number] [-T |-t timestamp] [-M messagekeyword] [-L number]] [-p lpanname[/pservername] |-b platformname/[cn|sn|pn] | -D "(SCSI_ID)" | -n ethn@platformname/cn | -R type [targetname]]

event -u event_ID_number -S {"O"|"I"|"R"}[-a] | [[-V |-v severity] [-I |-i event_ID_number] [-T |-t timestamp] [-M messagekeyword] [-L number]] [-p lpanname[/pservername] |-b platformname/[cn|sn|pn|pimn] | -D "(SCSI_ID)" | -n ethn@platformname/cn]

event -U event_ID_number -S {"O"|"I"|"R"}

event -E event_ID_number

DESCRIPTION The event command offers a filter for viewing an event or event listings in a PAN. The event command allows administrators to do the following:

• Display all events for a PAN sequentially by event ID by using the event command without an option or argument. Use the options and arguments to display more specific event information.

EVENT

PM5.2_BF 2-53

• Filter PAN, blade, LPAN or pServer events listings within their administrative domain (PAN or LPAN).

• Modify the status of events based on the event filter.

See the OPTIONS section or PAN Manager Administrator’s Guide for more information.







Specifies a platform and a specific blade.




[??The following is TBD for BX900?]



2-54 PM5.2_BF

lpanname[/pservername]

Specifies a pServer. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the pServer name. For example, the pServer, Web1, in the production LPAN would be referred to as production/Web1.

"(SCSI_ID)"







ethn@platformname[/cn]

Specifies a cBlade NIC. PAN Manager naming conventions require that you use a forward slash (/) between the platform name and cBlade number. For example, eth1 on cBlade 2 on the platform named production would be referred to as eth1@production/c2. PAN Administrators use the bframe command to rename a platform from the default MyBladeFrame name.

OPTIONS -a, --all

Updates all events, used with the -u option.

EVENT

PM5.2_BF 2-55

-b, --blade platformname/{cn |sn |pn |pimn}

Lists events within a administrative domain for one or all blades or Power Input Modules (PIMs). (The BladeFrame BF200 does not have an sBlade.)

-b, --blade platformname/{cn|sn|pn}

Lists events within an administrative domain for all blades within the administrative domain or a specific blade.

-D, --disk "(SCSI_ID)"

Lists the events for the specified SAN disk or Fibre Channel tape device.

-E, --eventid event_ID_number

Specifies a single event listing by its event ID. Use this option if you are interested in the details of a single event and you know the event ID of the event.

-i, --id-before event_ID_number

Filters events that occurred before the specified number. You can view all events before the specified number or combine this option with other option(s) to create a more specific filter.

-I, --id-after event_ID_number

Filters events that occurred after the specified number. You can view all events after the specified number or combine this option with other option(s) to create a more specific filter.

-L, --last-events number

Filters events displaying only the last specified number of events, such as the last ten events. You can combine this option with other option(s) to create a more specific filter.

-M, --message-contain keyword(s)

Filters events using only a keyword or keywords that you know are part of the message printed for that type of event. For example, using "PlatformOne/p2" will return all events for this specific


2-56 PM5.2_BF

pBlade that contain this text in the message, while using "core voltage" will return all events of this specific event type. Combining these strings, as in the example, "PlatformOne/p2 core voltage" returns only events on this specific pBlade with this specific event type.

-n, --eth {ethn@platformname/cn}

Lists the events for the specified Eth device.

-N, --num-events number_of_events_displayed

Pauses the display of events after a set number are printed. This option requires you to press the “Return” or “y” key to display the next set of events. To stop a set number of listings before it is complete, you can press the “q” key. This option displays ten events at a time, by default. This option can take a number argument to set a number of events to display at once; for example the command event –N 7 displays seven events and pauses until you press the “return” or “y” key.

Note: Without this option, every event that matches your criteria is displayed at once. In the case of many events, you may not see the entire list of events you have asked for.

-p, --pserver {lpanname | lpanname/pservername}

Lists events within a LPAN administrative domain for either all pServers within the administrative domain or a specific pServer.

-R, --type type [targetname]

Displays events that pertain only to a specific type of object, or optionally, to a specific targetname within that type. Supported type and targetname values are:

EVENT

PM5.2_BF 2-57

app [lpanname/app_name]

disk ["(SCSI_ID)"]

eth ethn@platformname/cn

exeres [lpanname/executable_resource]

fop [lpanname/failoverpolicy]

frame [plaformname]

fs [lpanname/filesystemname]

hmon [lpanname/monitorname]

ip [lpanname/IPresource]

lb [lpanname/servicename]

lpan [lpanname]

nfs [lpanname/nfsname]

pool [globalpoolname | lpanname/localpoolname]

pserver [lpanname/pservername]

reth [rethname]

san ["(SCSI_ID)"]

sw [vswitchname]

tape ["(SCSI_ID)"]

-S, --status {O|I|R}

Specifies the status of an event, or list of events. Use this option to filter a list of events or modify a specific event status by combining this option with the -U (--update-status) or -u (--bulk-update-status) option.

-t, --time-before mm/dd/yy_hh:mm:ss

Lists events that occurred before a specified date and time. You can view all events before this time or combine this option with other options to create a more specific filter. You must follow the format: "mm/dd/yy hh:mm:ss".

-T, --time-after mm/dd/yy_hh:mm:ss

Lists events that occurred after a specified date and time. You can view all events after this time or combine this option with other options to create a more specific filter. For example, you must follow the format: "mm/dd/yy hh:mm:ss".


2-58 PM5.2_BF

-u, --bulk-update-status

Sets status of a number of events. Usually used to resolve a large number of events. Use the -S option to specify the event status to set. Use the -a option to set the specified status of all events or use a combination of filter options (-i -I -v -V -t -T -L) to specify a specific range of events.

-U, --update-status event_ID_number

Modifies the status of an event. You must use this option with the -S (status) option to specify a range of events or eventids.

-v, --severity-less-or-equal-to severity_number

Lists events with a severity less than or equal to the specified number. You can view all events of less severity than the specified number or combine this option with other option(s) to create a more specific filter.

-V, --severity-more-or-equal-to severity_number

Lists events with a severity greater than or equal to the specified number. You can view all events of less severity than the specified number or combine this option with other option(s) to create a more specific filter.

EXAMPLES View all events after event 2200, ten at a time (on platform PlatformOne):

event -I 2200 -N PlatformOne

View events 2200 to 2500, 5 at a time (on platform PlatformOne):

event -I 2199 -i 2501 -N 5 PlatformOne

View the last 8 events of severity 3 or less (3 to 6), 5 at a time:

event -L 8 -v 3 -N 5

EVENT

PM5.2_BF 2-59

View the last 8 events of severity 2 or greater (1 and 2), for a pServer named rivers/nile:

event -L 8 -V 2 rivers/nile

List all events that pertain to all disks in your administrative domain:

event -R disk

Display all events that pertain to a specific disk (such as 9.0.34.23):

event -R disk "(9.0.34.23)"

List all events that pertain to all pServers in your administrative domain:

event -R pserver

List all events that pertain to a single pServer (such as pserver1 in the LPAN my_lpan):

event -R pserver my_lpan/pserver1

View all events of status “I” with severity 3 or greater (1 to 3), 12 at a time:

event -S I -V 3 -N 12

Modify the status of a triggered event, 2545, to resolved ("R"):

event -U 2545 -S R

List the events for disk 9.0.2.28:

event -D "(9.0.2.28)"

Display a long listing of the events for eth1 on cBlade 1 (on platform PlatformOne).

event -l -n eth1@PlatformOne/c1


2-60 PM5.2_BF

Resolve all events with severities 4 and higher:

event -u -S R -V 4



SEE ALSO BFRAME

EVENTTYPE

LPAN

MON

PAN


EVENTTYPE

PM5.2_BF 2-61

EVENTTYPE

NAME eventtype - lists or modifies event types monitored in a PAN.

SYNOPSIS eventtype [-l] [eventtypeID] [-p lpanname [/pservername]| -b platformname/{cn|sn|pn} | -S "(SCSI_ID)" | -n ethn@platformname/{sn}]

eventtype [-l] [eventtypeID] [-p lpanname [/pservername]| -b platformname|{cn| sn| pn| pimn} | -S "(SCSI_ID)" | -n ethn@platformname/{cn}]

eventtype [-a |-r emailaddress] [-e {default|custom}] [-q {yes|no}] {-P |-L} eventtypeID

DESCRIPTION The eventtype command lists or modifies actions for a specified event type monitored in a PAN. The eventtype command allows administrators to do the following:

• List or modify event actions only within your administrative domain by name and event type ID. The -l (list) option lists detailed information about each event type monitored within your administrative domain.

• Customize event type actions for sending SNMP traps and sending email notification within an administrative domain.

You can only use the eventtype command for an event type that is not within your administrative domain. Administrators use the appropriate command to set the default event actions for their administrative domain (using the pan or lpan commands).




2-62 PM5.2_BF





Specifies a platform and a specific blade.






lpanname[/pservername]

Specifies a pServer. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the pServer name. For example, the pServer Web1 in the production LPAN would be referred to as production/Web1.

"(SCSI_ID)"



EVENTTYPE

PM5.2_BF 2-63





ethn@platformname/{cn}

Specifies a cBlade NIC. PAN Manager naming conventions require that you use a forward slash (/) between the platform name and cBlade number. For example, eth1 on cBlade 2 on the platform named production would be referred to as eth1@production/c2. PAN Administrators use the bframe command to rename a platform from the default MyBladeFrame name.

OPTIONS -a, --add-email email_address

Adds the address of a person to which PAN Manager sends email notification when a specified event monitor is triggered. Use this option to modify the list of email addresses to include an email address not included in the administrative domain default list and only for a specific event type.

-b, --blade platformname/{cn |sn |pn |pimn}

Lists events within an administrative domain for one or all blades or Power Input Modules (PIMs). (The BladeFrame BF200 does not have an sBlade.)

-b, --blade platformname/{cn|sn|pn}

Lists events within an administrative domain for all blades within the administrative domain or a specific blade.

-e, --enable-action {default|custom}

Specifies whether a default administrative domain event action is activated for the specified event action or whether it has the customized setting activated. Customized settings are only


2-64 PM5.2_BF

permitted within an administrative domain and do not override event actions for other administrative domains.

After making the customized setting, the administrative domain administrator must use the eventtype -e custom command to activate the customized setting.

To restore the event actions to the administrative domain’s default values, use the eventtype -e default command. This switch allows customized settings to be activated and inactivated repeatedly without having to reset the event actions for the event type.

Using the eventtype command for an event type that is not within your administrative domain is not permitted and returns an error. Administrative domain administrators use the appropriate command to set the default event actions for their administrative domain (using the pan or lpan commands).

See the EXAMPLES section or PAN Manager Administrator’s Guide for more information.

-l, --long

Displays a list of specified event types, either for an entire domain or for one or a group of pServers or blades. Use -l option with the -p (pserver) or -b (blade) option to narrow the list of event types specific to pServers or blades within the administrative domain.

-L, --lpan-domain

Specifies the administrative domain (an LPAN) in which the event type ID's command action takes effect. Use this option with the -a (add-email), -r (remove-email), -e (enable-action) or -Q (send-snmptrap) options to specify the administrative domain of the event type ID in which the command action takes effect.

-n, --eth ethn@platformname/{sn}

Lists the event types for the specified Eth.

EVENTTYPE

PM5.2_BF 2-65

-p, --pserver {lpanname |lpanname/pservername}

Lists the event type settings within an LPAN administrative domain for either all pServers within the administrative domain or a specific pServer.

-P, --pan-domain

Specifies the administrative domain (the entire PAN) in which the event type ID's command action takes effect. Use this option with the -a (add-email), -r (remove-email), -e (enable-action) or -Q (send-snmptrap) options to specify the administrative domain of the event type ID in which the command action takes effect.

-q, --send-snmptrap {yes|no}

Specifies whether to send an SNMP trap if a specific event type is triggered.

-r, --remove-email email_address

Removes the address of a person the administrative domain administrator no longer wants to receive email notification.

-S, --disk "(SCSI_ID)"

Lists the event types for the specified SAN disk or Fibre Channel tape device.

EXAMPLES List all the event types by ID# and name for the pServer owl (in LPAN forest:

eventtype -p forest/owl

List the actions for a specific event type on pBlade 12 (on platform PlatformOne) Blade PlatformOne/p2 Status Change Event (ID#101763):

eventtype -l -b PlatformOne/p2 101763


2-66 PM5.2_BF

Add [email protected] to the current list of LPAN email recipients only for status changes for event type ID # 101763:

eventtype -a [email protected] -e custom -L 101763

List the event types for disk 9.0.2.28:

eventtype -S "(9.0.2.28)"

Display a long listing of the event types for eth1 on cBlade 1 (on platform PlatformOne):

eventtype -l -n eth1@PlatformOne/c1



SEE ALSO BFRAME

EVENT

LPAN

MON

PAN

SNMP

SNMPMGR


EXERES

PM5.2_BF 2-67

EXERES

NAME exeres - creates, modifies, or lists a high–availability executable resource for an LPAN.

SYNOPSIS exeres [-c] [-C command] [-B argument] [-S argument] [-E argument] [-L description] [-U username [-u {yes|no}]] lpanname/executable_resource

exeres -N newname lpanname/executable_resource

exeres [-l] lpanname [/executable_resource]

exeres -d lpanname/executable_resource

DESCRIPTION An executable resource is a set of attributes and arguments that let users start, stop, or run a program or script (such as Linux init scripts) on a pServer.

The exeres command creates or modifies an executable resource and assigns it a name, a description, and a command (with or without start, stop, or execute arguments), and specifies a user that runs the command on the pServer.




command

Specifies the command to be run by the executable resource.


2-68 PM5.2_BF

username

Specifies a user name associated with an executable resource. You cannot change the username while the executable resource is running.

If you do not use -U to specify a user name, the executable resource will run as the user root and use the pServer software’s default user environment settings, as provided in the PAN Agent. (For each executable 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.)

argument

Specifies an argument to be used by command while the executable resource is running.

executable_resource

Specifies the name of the executable resource PAN Manager can associate with an application.

OPTIONS -B, --start-arg argument

Specifies an argument to be used when PAN Manager starts an executable resource.

-c, --create

Creates a new executable resource.

-C, --command command

Specifies a command to be run by the executable resource.

-d, --delete

Deletes an existing executable resource.

EXERES

PM5.2_BF 2-69

-E, --exe-arg argument

Specifies an argument to be used while the executable resource is running.

-l, --long

Lists information about the current assigned executable resources within an LPAN, including information on the name, description, user, command, arguments, start, stop, execute, and assignments, if available.


Adds descriptive information about the executable resource.

-N, --rename newname

Renames the specified executable resource within an LPAN.

-S, --stop-arg argument

Specifies an argument to be used when PAN Manager stops an executable resource.

-u, --source-user-env {yes|no}

Sources the user environment when used with the -U (user) option.

-U, --user username

Associates a specific username with an executable resource.

If you do not use -U to specify a username, the executable resource will run as the user root and use the pServer software’s default user environment settings, as provided in the PAN agent. (For each executable 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.)


2-70 PM5.2_BF

EXAMPLES The following command lists all available information about executable resources configured for the LPAN lpaname.

exeres -l lpanname



SEE ALSO APP

LB

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_app).

EXTNET

PM5.2_BF 2-71

EXTNET

NAME extnet - lists or modifies the external management network properties.

SYNOPSIS extnet [-P platformmasteripaddr -1 cblade1ipaddr -2 cblade2ipaddr -M networkmaskipaddr -B broadcastipaddr -G gatewayipaddr [-f]] [platformname]

extnet [-g multicastipaddr -p multicastport] [platformname]

extnet [-r [-f]] [platformname]

DESCRIPTION The extnet command lists or modifies the properties a platform uses for external network communication. Using the extnet command without an argument lists the current IP address settings.

PAN Administrators use the extnet command to modify the IP address for each of the following:

• PAN Manager

• cBlade 1

• cBlade 2

• External gateway

• Network mask

• Broadcast settings

PAN Administrators also use the extnet command for the following PAN discovery settings:

• External multicast group and port

• Floating global IP


2-72 PM5.2_BF

Because PAN Manager multicast discovery occurs over the external management network, the extnet command allows the setting of the external multicast group and port.

The PAN Manager IP address allows clients (such as Windows VGA desktop consoles) to connect to PAN Manager (GUI or CLI) directly.

Any modification of the network portion of the IP address requires the simultaneous modification of the -1 (cblade1), -2 (cblade2), -B (broadcast) and, if applicable, the -G (gateway) options. See the EXAMPLES section for details.

Because of the sensitive nature of these IP address settings, PAN Manager displays the proposed new settings with your prompt to continue. If a new setting is invalid, an error appears describing why.

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.

OPTIONS -1, --cBlade1-ipaddress cblade1ipaddress

Sets the IP address for cBlade 1. The default cBlade 1 IP address is 192.168.200.2.

-2, --cBlade2-ipaddress cblade2ipaddress

Sets the IP address for cBlade 2. The default cBlade 2 IP address is 192.168.200.3.

-B, --broadcast broadcastipaddress

Sets the network broadcast address for communication with an external network. By default,the network broadcast address is 192.168.200.255.

EXTNET

PM5.2_BF 2-73

-f, --force

Forces any extnet command execution without prompting.

-g, --multicast-ip-address multicastipaddress

Specifies the multicast group IP address to support PAN discovery over the external management network. By default, the multicast group IP address is 224.224.224.223.

-G, --gateway gatewayipaddress

Sets the IP address for the gateway, if it exists, of the external network to which a platform is connected. By default, there is no gateway setting.

-M, --network-mask networkmaskipaddress

Sets the network mask for communication with an external network. By default, the network mask is set to 255.255.255.0.

-p, --multicastport multicastport

Specifies the multicast port to support PAN discovery over the external management network. By default, the multicast port is 9001.

-P, --frame-master platformmasteripaddress

Sets the primary IP address for PAN Manager, which resides on the master cBlade and transfers to the remaining cBlade in the event of failover.

Note: This setting requires a valid IP address argument for the network to which the platform is connected.

-r, --remove-gateway

Removes the current gateway setting. Removing the external network gateway IP address setting prevents IP traffic from leaving the platform’s external network.

EXAMPLES List the default extnet settings:

extnet


2-74 PM5.2_BF

Modify the external network to a simple Class A setting and add a gateway setting:

extnet -P 10.0.0.1 -1 10.0.0.2 -2 10.0.0.3 -B 10.0.0.255 -G 10.0.0.128

Remove the current gateway setting:

extnet -r



SEE ALSO INTNET

ROLE

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_role).

FOP

PM5.2_BF 2-75

FOP

NAME fop - creates, modifies, or lists a high–availability failover policy resource within an LPAN.

SYNOPSIS fop [-c] [-a pservername] [-O order] [-F {yes|no}] [-L description] [-S {"rr"|"ordered"}[-X {yes|no}] lpanname/failoverpolicy

fop -r pservername lpanname/failoverpolicy

fop -N newname lpanname/failoverpolicy

fop [-l] lpanname[/failoverpolicy]

fop -d lpanname/failoverpolicy

DESCRIPTION The fop command creates or modifies a failover policy within an LPAN to specify where a service moves to in the event of a failure.

LPAN Administrators use the fop command to set up failover policies for applications to include settings for:

• pServer — The pServer(s) to which an application fails over

• Selection policy — Specifies whether a failover policy selects an available pServer based on a specified order (ordered) option or selects the first available pServer as the failover pServer (round robin)

• Failback — Returns an application to its original pServer if it becomes available again.




2-76 PM5.2_BF


lpanname/failoverpolicy

Specifies a failover policy you create using the fop command for high–availability applications.

In order to maintain high availability within an LPAN, specify the LPAN in which you run the application and the pServer(s) to which you want the application to fail over. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the failover policy name. For example, the failover policy for the Apache application on the pServer, Web1, in the production LPAN could be referred to as production/Apachefailover or production/ApacheWeb1_failover. PAN Administrators use the lpan command to name LPANs.

OPTIONS -a, --add-pserver lpanname/pservername

Assigns a specified pServer to the list of pServers for a given failover policy.

-c, --create lpanname/failoverpolicy

Creates a new failover policy within an LPAN.

-d, --delete lpanname/failoverpolicy

Removes a specified failover policy from an LPAN.

-F, --failback {yes|no}

Specifies whether the failover policy should automatically return application processing back to the primary pServer if it becomes available again. This is set as “yes” by default.

-l, --long lpanname

Lists information about the current failover policy within an LPAN, including the selection policy for pServers, the automatic failback setting, and the service assignments.

FOP

PM5.2_BF 2-77


Adds descriptive information about the specified failover policy.

-N, --rename newname

Renames the specified failover policy.

-O, --order order

Specifies the order in which pServers are selected in the event that the service needs to move. This is an optional setting used with the -a (add-pserver) option that is specified according to the selection policy set using the -S (selection-policy) option. You can modify the order of a specified pServer by adding the pServer again with the new order number.

-r, --remove-pserver pservername

Takes the specified pServer off the list of pServers for a given failover policy.

-S, --selection-policy {"rr"| "ordered"}

Specifies whether a failover policy is carried out by an "ordered" list (default) or round robin ("rr"). The ordered approach selects an available pServer based on the order specified with the -O (order) option, using the first available pServer it finds on the list. A round-robin approach uses the next available pServer as the failover pServer. Ordered selection can have multiple pServers running on a single preferred pServer, while round-robin selection spreads failed pServers over as wide a range of failover blades as possible.

-X, --reboot-pserver {yes|no}

Specifies whether to reboot the pServer whose application has failed. Configure this option when you create or modify a failover policy.

EXAMPLES Create a failover policy named Apache_failover for the LPAN named development. Configure it to contain the Web2 pServer:

fop -c -a Web2 development/Apache_failover


2-78 PM5.2_BF

Add a second pServer (Web3) to the failover policy named Apache_failover:

fop -a Web3 development/Apache_failover

Modify the selection policy from the default (ordered) to Round Robin (rr):

fop -S rr development/Apache_failover

Specify the pServer named Web3 as the first failover pServer:

fop -a Web3 -O 1 development/Apache_failover

Note: This makes the original Web2 pServer the second failover pServer.

You can also condense the last three commands to one command:

fop -a Web3 -S ordered -O 1 development/Apache_failover

Add a third pServer (Web4) to this failover policy and modify the selection policy to round-robin:

fop -a Web4 -S rr development/Apache_failover



SEE ALSO APP

DISK

FS

HMON

LB

LPAN

PSERVER

FOP

PM5.2_BF 2-79



2-80 PM5.2_BF

FS

NAME fs - creates or modifies a SCSI disk resource within an LPAN.

SYNOPSIS fs [-c] [-D "(SCSI_ID)"] [-L description] [-M mount_point -P partition_number [-m {yes|no} -O "mount option" -A {rw|ro} -S {yes|no} [-s "scan_option"] -o order]] lpanname/filesystemname

fs -N newname lpanname/filesystemname

fs [-a] -M mount_point -P partition_number [-m {yes|no} -O "mount option" -A {rw|ro} -S {yes|no}[-s "scan_option"] -o order] lpanname/filesystemname

fs -r -M mount_point lpanname/filesystemname

fs [-l] lpanname[/filesystemname]

fs -d lpanname/filesystemname

DESCRIPTION The fs command creates or modifies a SCSI disk resource within an LPAN that can be assigned to an application. Use the fs command to assign the filesystem resource to an application to implement high availability and then move the application to failover pServers.




lpanname/filesystemname

Specifies the filesystem on a specified storage device that an application running under PAN Manager control uses for its file storage and manipulation. In order to maintain high availability

FS

PM5.2_BF 2-81

within an LPAN, you must specify the LPAN in which the application runs. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the filesystem name. For example, the filesystem name for an Apache application running in the production LPAN could be referred to as production/apach_fs. PAN Administrators use the lpan command to name LPANs.

"(SCSI_ID)"







OPTIONS -a, --add-mountpoint

Adds the specified mount point to the disk.

-A, --access-mode {rw|ro}

Designates whether an LPAN’s access to the specified mount point is read-write or read-only.

-c, --create lpanname/filesystemname

Creates the resource.

-d, --delete lpanname/filesystemname

Deletes the resource.


2-82 PM5.2_BF

-D, --device "(SCSI_ID)"

Specifies a SCSI ID within double-quotes and parentheses (for example, -D “(3.0.2.0)”) to be attached to the pServer.

-l, --long

Lists current filesystem resources, partitions, access modes, and mount points within an LPAN.


Adds descriptive information about the disk resource.

-m, --create-mountpoint {yes|no}

Specifies whether to create a new mount point on the pServer if it does not exist.

-M, --mountpoint directory_name

Specifies a directory on a pServer’s filesystem to use as an application’s filesystem mount point.

-N, --rename {new_name}

Renames the specified filesystem resource.

-o, --order {integer}

Specifies the order in which you want the partitions mounted.

-O, --mount-option "option"

Specifies a mount command argument for the filesystem.

-P, --partition partition_number

Specifies the partition number to mount. This option requires an integer greater than zero and less than sixteen as an argument.

-r, --remove-mountpoint mount-point

Specifies the mount point to remove.

FS

PM5.2_BF 2-83

-s, --scan-option "scan_option"

Specifies a scan command argument for the filesystem.

-S, --scan-partition {yes|no}

Specifies whether or not to scan the partition before mounting.

EXAMPLES Create a filesystem logical resource named ftpfs from the mount point called /usr/local/ncftp in the LPAN named lpan_01:

fs -c -D "(9.0.1.32)" -M /usr/local/ncftp -P 2 -m yes -O -o async -A rw lpan_01/ftpfs

RETURN VALUE Success returns a zero. An error returns a 1.


SEE ALSO APP

FOP

LB



2-84 PM5.2_BF

HMON

NAME hmon - creates, modifies, or lists a high–availability health monitor resource within an LPAN.

SYNOPSIS hmon [-c] [-L description] [-M monitor_script] [[-S pservername |-s] [-I |-D time {S|M|H}] [-F |-G |-R number_of_times]] lpanname/monitorname

hmon [-d| -N newname] lpanname/monitorname

hmon [-l] lpanname [/monitorname]

hmon [-a] -S pservername | -s [-I |-D time {S|M|H}] [-F | -G | -R number_of_times] lpanname/monitorname

hmon -r {-S pservername | -s} lpanname/monitorname

hmon -E {"all"|"any"} {-f |-g |-x} lpanname/monitorname

DESCRIPTION The hmon command creates, lists, or modifies an application health monitor within an LPAN. A health monitor detects a high–availability software failure by running a specific MON monitor script configured with the hmon command and assigned to any application using the app command. For more information about MON configuration, go to http://www.kernel.org/software/mon.

LPAN Administrators must set up MON servers and failover policy resources before they can run load-balanced services or stand-alone applications configured for failover. Use the hmon command to configure the following settings for an application health monitor:

• MON monitor script — The script that the MON server runs to test the health of an application.

• Interval — The time period (in seconds, minutes, or hours) the MON server script is invoked. Use only integers.

• pServer — The pServer on which the MON server runs.

HMON

PM5.2_BF 2-85

• Escalation policy — The escalation of PAN Manager's response when an application's health monitor detects failure.

• Thresholds — Specifies an action to take when a user-defined set of circumstances is reached.

• Startup delay — Specifies the amount of time to wait before starting an application or service.

Configuring a Health Monitor's Policy

LPAN Administrators can vary PAN Manager’s response to an application failure by setting the following thresholds:

• Restart — Specifies how many failures PAN Manager receives before it attempts to restart the application.

• Failover — Specifies how many failures PAN Manager receives before it attempts to restart the application on a failover pBlade (if configured), as determined by its failover policy.

• Give up — Specifies how many failures PAN Manager receives before it attempts to shut down the application.

Each time the health monitor escalates to the next level and the failure counter is reset:

• After three consecutive failure notifications, the system attempts to restart the application on its present pServer. If the application is successfully restarted, the failure counter is reset.

• If the application restarts but is still unresponsive, the system allows four consecutive failure notifications before attempting to failover the application to a designated failover pServer. If the failover is successful, the failure counter is reset.

• If the application fails over but is still unresponsive, the system allows five consecutive failure notifications before giving up.


2-86 PM5.2_BF




lpanname/monitorname

Specifies the health monitor configuration for an application running under PAN Manager control. In order to maintain high availability within an LPAN, you must specify the LPAN in which the application runs. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the health monitor name. For example, the health monitor for an Apache application running in the production LPAN could be referred to as production/apache_hmon. PAN Administrators use the lpan command to name LPANs.

OPTIONS -a, --add-server

Used with the -S option, adds the specified pServer to the LPAN health monitor.

-c, --create lpanname/health_monitor

Creates a new health monitor service within an LPAN.

-d, --delete lpanname/health_monitor

Removes a health monitor service from an LPAN.

-D, --startup-delay integer {S|M|H}

Sets the time period (in seconds, minutes or hours) to delay the start of the health monitor. Use this option for applications that take a relatively long time to boot, in order to avoid false failure notifications from the health monitor. You must specify the time period as an integer.

HMON

PM5.2_BF 2-87

-E, --escalate {all|any}

Specifies the escalation policy to be used if the health monitor detects an application failure. Use the -x, -f, or -g option after specifying the escalation option.

-f, --failover-policy

Specifies the failover policy to use with any or all events if the health monitor detects an application failure.

-F, --failover-after number_of_times

Defines the number of consecutive failures PAN Manager allows before the application’s failover policy, if configured, is applied. If no failover policy is defined, no action is taken. Set this option to zero if no failover policy is configured. The default value is 5.

-g, --giveup-policy

Specifies the action to take (in conjunction with the -E option) with any or all events if the local or remote monitor fails.

-G, --giveup-after number_of_times

Defines the number of consecutive failures PAN Manager allows before the application gives up and no longer responds to the health monitor. The value must be a whole number. Specifying zero configures the monitor to ignore the giveup escalation. The default value is 5.

-I, --interval integer {S|M|H}

Sets the frequency (in seconds, minutes or hours) in which the specified health monitor script runs. You must specify time periods in integers.

-l, --long

Lists the current settings for each health monitor within an LPAN, including the service assignments.

-L, --description {"text"}

Adds descriptive information about the specified health monitor.


2-88 PM5.2_BF

-M, --mon-script monitor_script_filename

Specifies the name of the monitor script for a specified health monitor. See PAN Manager Administrator’s Guide for details in configuring each script.

-N, --rename {name}

Renames the specified health monitor.

-r, --remove-server

Stops running the health monitor on the specified pServer. This option is only valid with the -S (server) option.

-R, --restart-after number_of_times

Defines the number of consecutive failures PAN Manager allows before it attempts to restart the application.

-s, --local-server

Specifies that the monitor script be run locally on the pServer on which the application is running.

-S, --server pservername

Specifies the pServer that runs the MON monitor script.

-x, --restart-policy

Determines any or all actions to take to restart the application based on the specified escalation policy.

EXAMPLES Create a health monitor named Apache_health with the following settings:

• LPAN name: development

• Monitor name: Apache_health

• Monitor script: http.monitor

• interval: 5 (seconds)

HMON

PM5.2_BF 2-89

• pServer: apache_1 hmon -c -S apache_1 -M http.monitor -I 5 S development/Apache_health

Allow the health monitor named Apache_health 2 failure notifications before PAN Manager attempts to restart Apache on its pServer, 3 failure notifications before PAN Manager attempts to restart Apache according to its failover policy, and 4 failure notifications before PAN Manager shuts down Apache:

hmon -R 2 -F 3 -G 4 development/Apache_health

Reset the interval trigger for the health monitor named Apache_health to 45 minutes:

hmon -I 45 M development/Apache_health



SEE ALSO APP

FOP

INTNET

IP

LB

MON

MONDEF

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_mon).


2-90 PM5.2_BF

INTNET

NAME intnet - lists or modifies the internal management network properties.

SYNOPSIS intnet [-N networkipaddr -M networkmaskipaddr -B broadcastipaddr [-f]] [platformname]

intnet [-N networkipaddr -M networkmaskipaddr -B broadcastipaddr [-f]][-t {intnet | boot1 | boot2 | ipmi}][platformname]

intnet [platformname]

DESCRIPTION The intnet command lists or modifies the properties for the internal management network of a platform. Use the intnet command to modify the following IP addresses for your platform’s internal management network configuration:

• Network mask IP address

• Broadcast IP address

By changing the IP address of the internal management network, the host address for each cBlade and pBlade is calculated according to slot number.

Any modification of the internal management network causes a PAN Manager restart which can create temporary outages of the targeted platform.

Caution: Before running the intnet command, you must shut down all pServers on a platform to ensure that PAN Agents restart properly.

Caution: Before running the intnet command, you must shut down all pServers and hypervisors on a platform to ensure that PAN Agents restart properly.

INTNET

PM5.2_BF 2-91

The intnet command does not update the Network Time Protocol (NTP) service daemon (ntpd). If you change the internal IP address of a cBlade you must edit the ntp.conf file to replace the old IP address with the new one.

Note: If you modify the network mask to limit the number of host addresses on the internal management network, you must leave enough capacity for each cBlade and pBlade to have its own IP address.

Using the intnet command without an argument lists the current network, network mask, and broadcast address settings.

OPTIONS -B, --broadcast broadcastipaddr

Sets the network broadcast address for the internal management network of a platform. By default, the network broadcast address is 192.168.255.255.

-f, --force

Forces any modification without a prompt.

-M, --network-mask networkmaskipaddr

Sets the network mask for the internal management network of a platform. By default, the network mask is set to 255.255.255.0.

-N, --network networkipaddr

Sets the network IP address for the internal management network of a platform. By default, the network IP address is set to 192.168.255.0.

-t, --type {intnet | boot1 | boot2 |ipmi}

Specifies the network type for listings or modifications to the PAN Manager internal management network, the IPMI network, or a boot network. By default, the boot type is “intnet.”


2-92 PM5.2_BF

-t, --type {intnet | boot1 | boot2 |ipmi}

Specifies the network type for listings or modifications to the PAN Manager internal management network, a boot network, or the IPMI network. By default, the boot type is “intnet.”

Note: Users can use the PAN Manager “intnet -t ipmi” command to list the IPMI internal management network settings, however, you cannot make implied modifications to the IPMI network. It is only the “-t ipmi” command that does not allow modifications.



SEE ALSO EXERES

EXTNET

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_exeres).

IP

PM5.2_BF 2-93

IP

NAME ip - Creates, lists, or modifies the network resources for an application or load-balancing service.

SYNOPSIS ip [-c] [-I ipaddr [-B broadcastipaddr] [-N netmaskipaddr]] [-E switchname [-M address |-m][R{10Mb|100Mb|no}]|-V vethname] [-L description] lpanname/IPresource

ip [-K newname] [-r ipaddr] [-i] lpanname/IPresource

ip [-l] lpanname [/IPresource]

ip -d lpanname/IPresource

DESCRIPTION The ip command creates, lists, or modifies the network resource(s) running under PAN Manager control within an LPAN. LPAN Administrators use the ip command to specify related configuration variables for a network resource, including:

• IP address — The IP address for an application configured to use the IP resource.

• Interface — The pServer’s interface, a vEth or virtual switch (vSwitch), the pServer uses to handle the IP traffic directed to the application.

• Network mask — The network mask address of the IP resource.

• Broadcast address — The broadcast address of the IP resource. Multiple broadcast IP addresses are supported.

By default if only an IP address is given when creating the IP resource, the network mask and broadcast address are created. If an IP address and network mask are given, the broadcast address is created. If all three are provided, PAN Manager verifies that the


2-94 PM5.2_BF

combination is valid. If the IP address is modified for the IP resource, PAN Manager notifies you if the network mask or broadcast address need to be modified in order to be valid.




lpanname/IPresource

Specifies the block of information an application running under PAN Manager control uses for its IP address resources. In order to maintain high availability within an LPAN, you must specify the LPAN in which the application runs. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the IP Resource name. For example, the IP resource for an Apache application running on pServer (Web1) in the production LPAN could be referred to as production/Web1IP. PAN Administrators use the lpan command to name LPANs.

OPTIONS -B, --broadcast broadcastipaddr

Assigns a broadcast address to the specified IP resource. If the address is not specified, the server will assign a default broadcast and netmask address.

-c, --create lpanname/IPresource

Creates an IP resource within a specified LPAN.

-d, --delete lpanname/IPresource

Removes the specified IP resource from a specified LPAN.

-E, --switch switchname

Assigns a vSwitch as an interface to an IP resource.

IP

PM5.2_BF 2-95

-i, --clear-interface ipaddress

Clears the interface configured for the network resource. Acts on either a vSwitch configured with the -E option, or a vEth configured with the -V option.

-I, --ip-address ipaddress

Assigns IP addresses to an IP resource within a specified LPAN.

-K, --rename new_name

Renames the specified network resource.

-l, --long

List information about the settings for each IP resource of a specified LPAN, such as IP address, netmask, broadcast, and interface.


Adds descriptive information about the specified network resource.

-m, --auto-assign

If no MAC address is specified when configuring a vSwitch for an IP resource, the server will automatically assign one.

-M, --mac-address mac_address

Assigns the specified MAC address if a vSwitch is configured for an IP resource.

-N, --netmask netmaskipaddr

Assigns a netmask address to the specified IP resource.

Note: If you configure more than one IP resource with the same netmask and any applications using these IP resources go down, other applications with the same netmask may see a short temporary loss of network connection.

-r, --remove-ip ipaddress

Deletes the specified network resource.


2-96 PM5.2_BF

-R, --rate-limiting {10Mb|100Mb|no}

Sets an upper limit rate, if any, in megabits per second, to the specified network resource. Use the specific text in quotes to specify a rate limit of 10Mb or 100Mb, or use “no” to leave it unregulated.

NOTE: Rate limiting is not supported by the Windows(TM) operating system or any operating system running as a vBlade guest on a platform.

NOTE: Rate limiting is not supported by the Windows(TM) operating system.

-V, --veth vethname

Assigns a vEth as an interface to an IP resource. Use this option to assign an IP resource to a specific pServer vEth. If you use the -E (switchname) option to specify a switch, PAN Manager assigns the lowest numbered vEth available.

EXAMPLES Create an IP resource named Apache_IP with the following settings:

LPAN name: development

vSwitch used: apache_switch

IP address: 192.168.0.45

ip -c -I 192.168.0.45 -E apache_switch development/Apache_IP



SEE ALSO APP

IP

PM5.2_BF 2-97

ETH

HMON

LB

RETH

SW

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_sw).


2-98 PM5.2_BF

LB

NAME lb - creates, lists, or modifies a high–availability load-balancer within an LPAN.

SYNOPSIS lb [-d [x]|-b |-s [-z] [-f] |-m [pservername]] lpanname/servicename

lb [-l] [lpanname/servicename]

lb [-c] [-A {yes|no}] [-L description] [-p primary_pservername] [-F failoverpolicy] [[-I IPresource [-o order]] [-H healthmonitor -j IPresource]] [-T -S {tcp|tcp-persist|udp} -P port [-X {rr|wrr|lc|wlc}]] [-a membername -u IPresource [-W weight] [-w {yes|no}]] lpanname/servicename

lb [-K newname] [[-I |-i IPResource [-o order]] [-H healthmon -j IPresource |-h healthmon]] [-F failoverpolicy |-e] [-q] lpanname/servicename

lb [-T -S {tcp|tcp-persist|udp} -P port [-X {rr|wrr|lc|wlc}]] [-t -S {tcp|tcp-persist|udp} -P port] lpanname/servicename

lb [-a membername -u IPresource [-W weight] [-w {yes|no}] [-r membername] lpanname/servicename

lb --add-monitor monitorname lpanname/servicename

lb --remove-monitor monitorname lpanname/servicename

lb -M monitorname -U eventname -Q {failover|restart|none} lpanname/servicename

DESCRIPTION The lb command creates, lists, or modifies the member(s) of a load-balancing service within an LPAN. You create load-balancing services to ensure that multiple application instances can maintain a dynamic response to requests. By running more than one application instance as members, load-balancing services spread client requests across its members to avoid flooding an application with requests. In addition, LPAN Administrators can add

LB

PM5.2_BF 2-99

application instances (previously configured but not running) to a service in times of heavy utilization before the application reaches an overloaded state.

After creating a load-balancing service with the lb command, LPAN Administrators add one or more members to it. A load-balancing service and its members are required to run within a single LPAN. Load-balancing services and their members are configured using LPAN resources, such as failover policies, filesystem resources, network resources, executable resources, and health monitors. Use the fop, fs, ip, and hmon commands to create these resources. See the appropriate man page or PAN Manager Administrator’s Guide for more information.

See the OPTIONS and PAN Manager Administrator’s Guide for more information about configuring autostart for load-balancing services.




lpanname/servicename

Specifies a load-balancing service by name. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the service name. For example, the load-balancing service for an Apache application running in the production LPAN could be referred to as production/lbsapache, while a member of the service could be referred to as production/apache_one.


2-100 PM5.2_BF

membername

Specifies the name given to this member of the load-balancing service. The member name should be different from the name of the member pServer.

monitorname

Specifies a PAN Manager user-defined monitor. LPAN Administrators use the PAN Manager umon command to create user-defined monitors.

OPTIONS --add-monitor monitorname

Associate a user-defined monitor with the specified application. LPAN Administrators use the PAN Manager umon command to create user-defined monitors.

-A, --autostart {yes|no}

Specifies whether a load-balancing service starts when its pServer boots. Configure load-balancing services and their members to autostart using the lb –A yes command for the service and the lb –A yes command for the service members. By default, this is set to "no".

-a, --add-member membername

Adds a new member to a load-balancing service and assigns the member a name.

-b, --start lpanname/servicename

Starts a specified load-balancing service, if configured. PAN Administrators use the lb –b (start) and lb –s (stop) commands to start or stop a load-balancing service. Manually starting a load-balancing service starts all the members currently in the service that are configured to be started. To add a member to a service that is running, you must manually start the member with the lb –b command. Manually stopping a service stops all its members; any member can be manually stopped while a service is running.

LB

PM5.2_BF 2-101

-c, --create lpanname/servicename

Creates a load-balancing service.

-d, --delete lpanname/servicename

Deletes the specified load-balancing service from the specified LPAN.

-e, --resetfailover

Removes the failover policy setting from the specified load-balancing service.

-f, --force

Forces a load-balancing service to stop. Use this option with the -s (stop) option.

-F, --setfailover failoverpolicy

Sets or modifies a failover policy for the specified service.

-h, --remove-healthmonitor health_monitor

Removes a health monitor from the specified service.

-H, --add-healthmonitor health_monitor

Sets or modifies a health monitor for the specified service.

-i, --removeipresource IPresource

Removes a service IP resource for the specified service.

-I, --add-ipresource IPresource

Sets or modifies an IP resource running under PAN Manager control for a load-balancing service. PAN Manager software relays the service IP resource network traffic to application instances running on members of the load-balancing service according to the scheduling policy set using the -X (scheduling-policy) option.

-j, --assign-hmon-ipresource hmon-associated_IPresource

Starts the specified load-balancing member and associates it with an IP resource.


2-102 PM5.2_BF

-K,--rename new_name

Renames the specified load-balancing service.

-l,--long

Lists configuration settings for the specified load-balancing service(s).


Adds descriptive information about the specified load-balancing service.

-m, --move pservername

Forces a load-balancing service to move its computing resources to the specified pServer. If the option is used without the pservername argument, the load-balancing service moves to the pServer defined in its failover policy.

-M, --monitor monitorname

Specifies an existing user-defined monitor that has already been added to the load-balancing service. LPAN Administrators add user-defined monitors to the load-balancing service with the --add-monitor option.

Use this option with the -U (event), and -Q (set-event-action) options to configure a user-defined monitor event and to specify actions for a specific user-defined monitor.

-o, --order resource_start_order

Specifies an order in which you want the load-balancing service to start IP resources.

-p, --primaryserver primarypservername

Specifies the primary pServer for a load-balancing service.

-P, --port port_number

Specifies a port number on which a load-balancing service listens.

LB

PM5.2_BF 2-103

-q, --remove-primaryserver

Removes the specified primary pServer from the load-balancing service.

-Q, --set-event-action {failover|restart|none}

Specifies the action to take in the event that the load balancing event threshold is triggered.

--remove-monitor monitorname

Removes a specified user-defined monitor from the load-balancing service.

-r, --remove-member membername

Removes the specified member from a load-balancing service.

-s, --stop lpanname/servicename

Stops a specified load-balancing service. PAN Administrators use the lb –b (start) and lb –s (stop) commands to start or stop a load-balancing service. Manually starting a load-balancing service starts all the members currently in the service that are configured to be started. To add a member to a service that is running, you must manually start the member with the lb –b command. Manually stopping a service stops all its members; any member can be manually stopped while a service is running.

-S, --service-type {tcp|tcp-persist|udp}

Specifies the type of service protocol, either tcp (default), tcp in persist mode (tcp-persist), or udp.

-t, --remove-connection

Removes a connection configured for a load-balancing service.

-T, --add-connection

Specifies the connection to be configured for the load balancer. You can specify 0 or more connections.


2-104 PM5.2_BF

-u, --assign-mem-ipresource member-associated_ IPresource

Specifies a load balancing member’s network resource to run under PAN Manager control. The network resource specified with the -j option should only have one IP address configured.

-U, --event {event_name}

Configures a user-defined monitor event. LPAN Administrators use this option in conjunction with the -M (monitor) and -Q (set-event-action) options to configure an action for the specified event.

-w, --start-with-service {yes|no}

Specifies whether or not a member is started when the load balancing service stops or starts.

-W, --weight number

Specifies the processing capacity of this application relative to the entire load managed by the load balancer. See the Linux ipvsadm man page for more information on the schedulers.

-x, --delete-member

Used with the -d option, removes all members of the load balancing service.

-X, --scheduling-policy {rr|wrr|lc|wlc}

Specifies an algorithm for distributing requests to the load-balancing service member pServers as specified by the Linux ipvsadm command. You must specify one of the following algorithms:

• rr — round-robin (default) — Distribute jobs equally among available members.

• wrr — weighted-round robin — Assign relatively more jobs to members that have higher weight.

• lc — least-connection — Assign relatively more jobs to pServers that have fewer scheduled jobs.

LB

PM5.2_BF 2-105

• wlc — weighted-least-connected — Assign relatively more jobs to pServers that have less scheduled jobs relative to their capacity.

See the Linux ipvsadm man page or the LVS website for more information on the schedulers.

-z, --stop-member

Used with the -s option to stop all members when the load-balancer stops.

EXAMPLES The following example outlines the steps to configure a load-balancing service for several Apache servers running in the LPAN called market1. The pServers running the service and the members and the failover policy named Apache_failover must already exist.

Configure IP resources using two vSwitches, already configured:

• first member: apache1ip

• second member: apache2ip

• load-balancing service load: extload1

ip -c -E int_sw1 -I 172.29.15.3 market1/apache1ip

ip -c -E int_sw1 -I 172.29.15.4 market1/apache2ip

ip -c -E ext_sw -I 172.29.15.5 market1/extload1

Note: Create each IP resource with an alias. Each resource IP address must be valid for the network to which the platform connects.

Create a load-balancing service with the following settings:

• Load-balancing service name: lbsapache

• pServer: load1

• port: 80


2-106 PM5.2_BF

• service type: tcp

• scheduling policy: wrr

• failover policy: Apache_failover

• IP resource: extload1

lb -c -p load1 -P 80 -F Apache_failover -S tcp -X wrr -I extload1 market1/lbsapache

Use the following settings to add two members to this load-balancing service:

• application name: app_apache

• LPAN name: mylpan

• health monitor: apache_hmon

• first member name: apache_one

• second member name: apache_two

• first member pServer: apache_1

• second member pServer: apache_2

• first member IP resource: apache1ip

• second member IP resource: apache2ip

• each member's failover policy: Apache_failover

• weighting criteria: apache_one handles twice the load of apache_two

lb -a app_apache -p apache_1 -F Apache_failover -I apache1ip -W 2 -H apache_hmon lbsapache/mylpan

lb -a app_apache -p apache_2 -F Apache_failover -I apache2ip -H apache_hmon lbsapache/mylpan

Note: The filesystem must be configured on unit “(0.0)” of the disk resource of each pServer running each instance of Apache in the LPAN named market1. An initialization script for Apache (applications/Apache/etc/rc.d/init.d/httpd) must also exist on this disk, on each application's pServer.

LB

PM5.2_BF 2-107

Boot the load-balancing service, lbsapache, and start the service members apache1 and apache2:

lb -b market1/lbsapache

Move this load-balancing service from its current pServer to one listed in the Apache_failover policy:

lb -m market1/lbsapache



SEE ALSO APP

FOP

FS

HMON

IP

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_ip).


2-108 PM5.2_BF

LPAN

NAME lpan - creates, lists, or modifies an LPAN configuration.

SYNOPSIS lpan -b [-w [-q]] lpanname

lpan -E [-aA |-rA emailaddress] [-V {1-6}] [-Q {yes|no}] lpanname

lpan -H [-l] lpanname

lpan -I "template_name" lpanname

lpan -s [-f] [-T "min" -M "textmessage"] [-w [-q]] lpanname

lpan [-x|-X] [-f] [-T "min" -M "textmessage"] [-w [-q]] lpanname

lpan [-aB |-rB] {platformname/pN} lpanname

lpan [-aD |-rD] {switchname|"(SCSI_)"} lpanname

lpan [-c |-d [-f]] lpanname

lpan -G globalpoolname {[-F {yes|no}][-P {yes|no}]} lpanname

lpan [-l] [lpanname]

lpan [-n new_name] [-L "text"] lpanname

lpan [--group-hypervisors|--ungroup-hypervisors] lpanname

lpan [-e | -u] DVDROMname lpanname

DESCRIPTION The lpan command creates, lists, or modifies an LPAN configuration. LPAN Administrators use the lpan command to:

• Create, modify, or remove an LPAN configuration.

• List all the resources currently allocated to the LPAN(s) under their control.

• Boot, reboot, or shut down a specific LPAN and its currently active pServers.

LPAN

PM5.2_BF 2-109

• Configure default actions for LPAN administrative domain events.

• Boot, shut down, reboot, or release resources for all the pServers in an LPAN.

• Authorize LPAN access for global pools.

An LPAN is a set of logically isolated computing resources that includes processors, network connections, and storage allocated to an organization. PAN Manager software provides each organization the ability to exclusively manage its set of resources after the resources are allocated by a PAN Administrator. These resources include the following:

• pBlade resources — Specify pBlades available to pServers within the LPAN, or authorize pServers to access a global pool of pBlades. Note that each global pool must explicitly be given access to LPANs (for example, lpan -F yes -G globalPool2 foo), pServers must be configured with a specific local pool (for example, pServer -B localPool2 foo/ps1), and local pools must be linked with accessible global pools (for example, pool -G globalPool2 foo/localPool2).

• SCSI disks from a SAN — Assign disk storage from a SAN available to pServers within the LPAN.

• SCSI tape devices — Assign Fibre Channel tape devices to pServers within the LPAN.

• vSwitches — Assign vSwitches that pServers can use to connect to internal and external networks.

• DVD-ROM — Provide an LPAN with shared access to the DVD-ROM drive located on each cBlade. Use these to install DVD-ROM-based applications on pServers.

After an LPAN has its resources and these assignments, LPAN Administrators use the pserver and disk commands to configure the resources in LPANs by creating the pServer(s), attaching each device to a specific name, and assigning a root filesystem to each pServer as necessary. LPAN Administrators then use the lpan


2-110 PM5.2_BF

command to define an activation order for the pServers within their LPAN, boot their LPAN, and specify shutdown options for their LPAN.

For more information about creating and modifying LPANs, see the OPTIONS and PAN Manager Administrator’s Guide.




platformname/pn






"(SCSI_ID)"

Specifies a PAN Manager SCSI ID of a device for a SAN storage array disk or a tape device rather than a subpath SCSI ID of the device. When specifying a SCSI device name, use the convention "(w.x.y.z)" where:


LPAN

PM5.2_BF 2-111





switchname

Specifies a virtual switch (vSwitch). Use the sw command to create a vSwitch.

OPTIONS -aA, --add-email emailaddress

Adds a recipient to the list of addresses to which PAN Manager sends email notification of LPAN administrative domain events. You must use this option with the -E (default-event-action) option to activate the setting. You set the severity criteria for email notification for administrative domain events with the -V (severity) option.

-aB, --addblade platformname/pn[-n]

-aB, --addblade platformname/pn

Specifies a pBlade to be used as a processing resource for the pServer(s) of an LPAN.

-aD, --adddevice {switchname| "(SCSI_ID)"| DVDROMname}

-aD, --adddevice {switchname| "(SCSI_ID)"}

Specifies an optional device assignment to a specified LPAN for disks, tape devices, or switches. PAN Administrators use this command in consultation with each LPAN Administrator.

-b, --boot lpanname

Boots an LPAN after it has been configured. By default, an LPAN boots into a multi-user configuration and applies the configuration to all pServers within the LPAN. To change the option for an


2-112 PM5.2_BF

individual pServer, reset that pServer’s boot option using the pserver -b command.

Because booting and rebooting an LPAN boots only the LPAN’s pServers that were booted when it was shut down, pServers already shut down when an LPAN is shut down and rebooted will remain shut down. The LPAN reboots normally and all LPAN resources function normally. The pServers that do not boot must be started manually using the pserver -b command.

Note: If an LPAN fails to boot, it is possible that one of the pServers was not able to boot with a configuration that prevented the LPAN boot process. See the pserver man page and the -o (optional) option or PAN Manager Administrator’s Guide for more information.

-c, --create lpanname

Creates a new LPAN, within a PAN, named as the LPAN Administrator wishes. PAN Administrators use this command in consultation with each LPAN Administrator.

-d, --delete lpanname

Removes a specified LPAN. Use the -f (force) option to delete without prompting. All pServers in the LPAN must be shut down before this command succeeds.

-e, --enabledevice DVDROMname

Allows a physical DVD-ROM on the cBlades to be accessed by each pServer within the specified LPAN. In order to allow an LPAN’s pServers access, PAN Administrators must initially use this option to grant specific LPANs access to a physical DVD-ROM. LPAN Administrators can then use this option to either enable all pServers within the LPAN DVD-ROM access or they can use the pserver -e DVDROMname pservername command to grant DVD-ROM access to specific pServers. The access status of physical DVD-ROMs(s) on a pServer are displayed under the Enabled column in the output of the pserver -l command.

LPAN

PM5.2_BF 2-113

This command option is not necessary to enable a pServer to access its virtual CD-ROM (VCD). LPAN Administrators use the PAN Manager pserver --insert-vcd image_name command option to insert and can immediately access the media image in the VCD via a console on the pServer.

-E, --default-event-action

Activates event type actions for all events in the LPAN administrative domain. Use this option to set criteria and email recipients for sending email notification of events with the -aA (add-email) and -V (severity) options.

Use this option to activate or inactivate the sending of SNMP traps with the -Q (send-snmptrap) option. For more information on configuring events, triggers, and SNMP, see PAN Manager Administrator’s Guide.

-f, --force

Forces an LPAN operation without prompting. This option requires the -d (delete), -s (shutdown), or -x (reboot) option.

-F, --pool {yes|no}

Authorizes an LPAN to access a global pool of pBlades for failover (see the -G option). PAN Administrators must use this option to allow the pServers in an LPAN to access a global pool of failover pBlades created using the pool command. Authorize access with a yes argument, and deauthorize access with a no argument. Use the -P option to give the pServers boot access to the blades in the global pool.

-G, --global_pool {globalpoolname}

Specifies the global pool to which the LPAN should have failover or unlimited (boot) access. See the -F option for failover access, or the -P option for unlimited access.

--group-hypervisors lpanname

Groups the hypervisors in a specified LPAN. This is required if you plan to perform migration operations on any vBlade pServers in


2-114 PM5.2_BF

that LPAN. If you do not plan to perform these operations, grouping hypervisors is not recommended. PAN Manager does not support VBXS Hypervisor v2.0 or earlier in a group. Make sure that your LPAN does not contain any of these older hypervisors. (Support for migration on VBXS Hypervisor v1.1 does not require hypervisor grouping. VBXS Hypervisor v2.0 does not provide support for migration.) Before you can group or ungroup the hypervisors in an LPAN, all of the hypervisors in that LPAN must be shut down.

-H, --high-availability

Lists all of the high–availability resources in the LPAN and can be combined with the -l (long) option.

-I, --extract-template “template_name”

Extracts a set of scripts and binaries that makes VMware GSX Server 3 resources available to the LPAN. You must enclose template_name within quotation marks.

-l, --long

This option lists current LPANs within an administrator’s domain and includes a display of each LPAN’s description, pServers booted, and properties, as well as details about the pServers, pBlades, and devices within each LPAN. If you specify an LPAN argument following this option, it lists these details only for that LPAN.

Note: Without the -l option, the lpan command lists the following status information for the LPANs within their administrative domain: pServer, status, agent, pBlade, hostname, up time.


Adds a descriptive label to an LPAN, for human reference.


Specifies an optional warning message to be printed before an LPAN is shut down. LPAN Administrators can use this option to provide details to LPAN operators and monitors of how long before

LPAN

PM5.2_BF 2-115

a shutdown will occur. LPAN Administrators use this option after the -s (shutdown) or -X (reboot) option.

-n, --rename new_name

Allows a PAN Administrator to rename the specified LPAN.

-P, --unlimited {yes|no}

Specifies whether an LPAN has unlimited (boot) or restricted (failover only) access to the pBlades in a global pool (see the -G option). Specify unlimited with a yes argument and restricted with a no argument.

-q, --quiet

Combined with the -w (wait) option, this option suppresses informational messages and the progress indicator during a boot or shutdown process. Use the -q and -w options only in combination with the -b (boot), -s (shutdown), or -X (reboot) options.

-Q, --send-snmptrap {yes|no}

Specifies whether an SNMP trap is sent for any event within the LPAN administrative domain. You must use this option with the -E (default-event-action) option. For more information on configuring events, triggers, and SNMP, see PAN Manager Administrator’s Guide.

-rA, --remove-email emailaddress

Removes a recipient from the list of addresses to which email notification of LPAN administrative domain events are sent. You must use this option with the -E (default-event-action) option.

-rB, --removeblade platformname/pn

Specifies a pBlade to be removed from the processing resources of an LPAN. PAN Administrators use this command in consultation with each LPAN Administrator.


2-116 PM5.2_BF

-rD, --removedevice {switchname|"(SCSI_ID)"| DVDROMname}

-rD, --removedevice {switchname|"(SCSI_ID)"}

Specifies a device to be removed from a specified LPAN. PAN Administrators use this command in consultation with each LPAN Administrator.

-s, --shutdown lpanname

Halts the processing of an LPAN, including all of its pServers. The current LPAN configuration is saved for the next LPAN reboot. LPAN Administrators combine this option with the -T (time), -M (message), or -w (wait) options to create a conditional shutdown.


Specifies an interval of time (in minutes) before an LPAN shuts down. LPAN Administrators use this option after the -s (shutdown) or -X (reboot) option.

-u, --disabledevice DVDROMname

Removes DVD-ROM access from all the pServers within the specified LPAN.

--ungroup-hypervisors lpanname

Ungroups the hypervisors in a specified LPAN. This is appropriate if you no longer plan to perform migration operations on any vBlade pServers in that LPAN.

-V, --severity severity_number

Sets the severity criteria for email notification for LPAN administrative domain events. You must use this option with the -E (default-event-action) option. By default, this value is 2.

-w, --wait

Causes the lpan command to pause while a boot or shutdown process is underway and displays a progress indicator. Use this option with either the -b (boot) or -s (shutdown) options in cases in which you would like to suspend command-line operations until the boot or shutdown is completed.

LPAN

PM5.2_BF 2-117

-x, --reboot lpanname

Reboots the specified LPAN. Use the -f (force) option to reboot without prompting. LPAN Administrators combine this option with the -T (time), -M (message), or -w (wait) options if you want to create a conditional reboot.

-X, --reboot-all

Reboots all pServers in an LPAN, including pServers that are shut down. Use the -f (force) option to reboot without prompting. LPAN Administrators combine this option with the -T (time), -M (message), or -w (wait) options if you want to create a conditional reboot.

EXAMPLES Remove a disk device from the development LPAN:

lpan -rD "(9.0.1.10)" development

Add a descriptive label to the development LPAN:

lpan -L "Processing area for project" development

Add a blade to the development LPAN:

lpan -aB PlatformOne/p3 development

Disable access to the DVD-ROM on cBlade 2 for all the pServers within the development LPAN:

lpan -u "(2.0.2.0)"@PlatformOne/c2 development

Force the removal of the development LPAN without a verification prompt:

lpan -d -f development

List the pServers configured for the pBlades in an LPAN named doc:


2-118 PM5.2_BF

List the pServers and hypervisors configured for the pBlades in an LPAN named doc:

lpan doc

Enable the LPAN lpan1 to have failover access to the blades in global pool IA32:

lpan -F yes -G IA32 lpan1

Enable the LPAN lpan1 to have boot access to the blades in global pool IA32:

lpan -P yes -G IA32 lpan1



SEE ALSO APP

BFRAME

BLADE

DISK

EVENTTYPE

FOP

MON

MONDEF

PAN

POOL

PSERVER

RETH

SNMP


MON

PM5.2_BF 2-119

MON

NAME mon - lists or modifies the statistical monitors for system processes on pBlades, LPANs, or a platform.

SYNOPSIS mon [-l] [-B {platformname | platformname/pn} | -P {lpanname |lpanname/pservername}] |-M {monitor-name | monitor_ID} |-S "(SCSI_ID)" |-n ethn@platformname/{sn | cn}]

mon -M {monitor-name | monitor_ID} -T trigger-number {[-H high-value] [-L low-value] [-D duration]}

DESCRIPTION The PAN Manager mon command lists or modifies the statistical monitors and their trigger values for processes on each pServer or across an LPAN. There are two sets of processes that you can monitor using PAN Manager software — system resources and hardware resources. Only the following system resource triggers can be modified:

• CPU (utilization, load average)

• Memory (current: physical and virtual)

• Disk I/O (bytes read/written, errors)

• Network (packets, errors)

• Swap (available space)

• Paging (available space)

• Filesystem (available space)

The LPAN Administrator role is required to use the mon command to optionally configure any monitor trigger for a specified LPAN or pServer.


2-120 PM5.2_BF




platformname/pn or lpanname/pservername

Specifies a pBlade or a pServer. PAN Manager naming conventions require you to use a forward slash (/) between the name of the platform or LPAN and the pBlade or pServer name. For example, the pServer Web1 in the production LPAN would be referred to as production/Web1. PAN Administrators use the bframe command to rename a platform and the lpan command to name LPANs, while LPAN Administrators use the pserver command to name pServers.

Monitor Names and IDs

Each monitor has a unique name and ID and has settings that include its configurability as well as trigger number(s) and trigger values. To see the exact name and ID for the event monitors for a platform, LPAN, or pServer, use the mon -l command with the appropriate argument.

Trigger Numbers and Values

Each monitor has one or more trigger numbers that contain trigger value settings. Trigger numbers specify a set of trigger values specific to each event monitor and can number one or greater. Trigger values are the statistical values that create an event and are specific to the trigger number for an event monitor. Before modifying trigger values from the default values, determine the trigger number and the trigger values for the specific monitor using the mon -l command with the appropriate argument. High and low trigger values depend upon the resources monitored, while the duration value is used to calculate a timed average and must be greater than 120 seconds.

MON

PM5.2_BF 2-121

"(SCSI_ID)"







OPTIONS -B, --blade {platformname|platformname/pn}

Specifies the name of a platform or pBlade. Use this option with the -l (long) option to display all the monitors and their settings for a platform or pBlade.

-D, --duration number_of_seconds

Specifies a duration, in seconds, used to calculate a timed average for monitoring over which a trigger value is monitored. For example, some triggers work by monitoring a system value and triggering an event the moment the system value exceeds a threshold value; others trigger an event when the system value is averaged over a timed duration and the averaged value exceeds a threshold value. The duration is used in the latter case. This input value must be greater than 120.

-H, --high-value high-value_integer

Specifies an upper-limit threshold trigger over which the event monitor triggers an event.


2-122 PM5.2_BF

-l, --long

Lists setting information about all or specified event monitors. The display includes a monitor ID, its trigger types and trigger values, and the event actions for a specified pServer or LPAN. Not specifying an argument lists this information for all the monitors within the current LPAN for LPAN Administrators, or within a platform for PAN Administrators.

-L, --low-value low-value_integer

Specifies a lower-limit threshold trigger under which the event monitor triggers an event.

-M, --monitor {monitorname|monitor_ID}

Specifies an event monitor by its name or monitor ID. Use this option with the -l (long) option to display the settings for an event monitor by its name or monitor ID.

-n, --eth {ethn@platformname/sn | cn}

Lists the monitors for the specified Eth.

-P, --pserver {lpanname | lpanname/pservername}

Specifies the name of an LPAN or pServer. Use this option with the -l (long) option to display all the monitors and their settings for a particular LPAN or pServer.

-S, --san-device "(SCSI_ID)"

Lists the monitors for the specified SAN device (a disk or tape device).

-T, --trigger triggernumber

Specifies an exact monitor trigger to be modified. Trigger numbers and their values are displayed for each monitor with the mon -l [-B | -M | -P] command. In general, triggers are numbered 1 or greater and some monitors have more than one trigger number. Use this option in combination with the -M (monitor-name) option to modify a specific monitor trigger value, followed by the -H (high-value), -L (low-value), or -D (duration) values.

MON

PM5.2_BF 2-123

EXAMPLES List the triggers for the monitors of the entire LPAN named Staging:

mon -l -P Staging

List the triggers for the monitors of the pServer named Web1 in the Staging LPAN:

mon -l -P Staging/Web1

Modify the monitor named “pServer rivers/nile Swap Utilization” so that it triggers events if Swap Utilization exceeds 90% or returns below 60% for a period of 5 minutes:

mon -M "pServer rivers/nile Swap Utilization” -T 1 -H 90 -L 60 -D 300

You can reset this monitor’s triggers by specifying its monitor ID number — 1930 — instead of its name:

mon -M 1930 -T 1 -H 90 -L 60 -D 300

With either command you get the following confirmation display with the new trigger values in parentheses:

Trigger 1 Criteria: Sent when pServer rivers/nile Swap Utilization exceeds (90)% or then returns below (60)% for (300) seconds

List the monitors for disk 9.0.2.28:

mon -S "(9.0.2.28)"

Display a long listing of the monitors for eth1 on cBlade 1 (on platform PlatformOne).

mon -l -n eth1@PlatformOne/c1



2-124 PM5.2_BF


SEE ALSO EVENT

EVENTTYPE

HMON

INTNET

LPAN

MONDEF

PSERVER


MONDEF

PM5.2_BF 2-125

MONDEF

NAME mondef - lists or modifies the default trigger values for statistic monitors for the PAN administrative domain.

SYNOPSIS mondef [-l] [monitor-name]

mondef [-H high-threshold] [-L low-threshold] [- D duration] -T trigger-type monitor-name

DESCRIPTION The PAN Manager mondef command lists or modifies the default trigger values for statistic monitors for the PAN domain. Default trigger values are inherited from the most current configuration; therefore the default values for LPANs come from the default values of the PAN domain.

PAN Administrators can list or modify the PAN domain default values using the mondef command. LPAN Administrators can list or modify the set of statistical monitor trigger values within their LPAN using the mon command. PAN Administrators use the mondef -l command to see a list of the default trigger values for the PAN domain.





2-126 PM5.2_BF

Monitor Names and Trigger Types

Each monitor and its trigger type refers to either a threshold event trigger or a return event trigger that is used as an argument to the mon command. To see the exact name of each trigger type name for each monitor, use the mon -l lpanname/pserver or mon -l lpanname commands.

Trigger Values

The default values list thresholds as percentages of resources used and a duration used to calculate a timed average in seconds.

OPTIONS -D, --duration number_of_seconds

Sets the default time limit, in seconds, for a monitor trigger. A trigger duration must be at least 120 seconds.

-H, --high-threshold high-value_integer

Sets the default upper limit for a monitor trigger.

-l, --list

Lists information about all the monitors for the PAN domain. This option provides information such as the type and trigger values of each monitor.

-L, low-threshold low-value_integer

Sets the default lower limit for a monitor trigger.

-T, --trigger-type triggernumber

Identifies which trigger of the monitor you are modifying.

EXAMPLES List the trigger default values for the disk space monitors within the PAN domain:

mondef -l system threshold.remainingdiskspace

MONDEF

PM5.2_BF 2-127

Modify default trigger values for CPU utilization and disk space monitors within the PAN domain. The high threshold event trigger for CPU utilization is set to 33, while the low threshold event trigger for disk space monitors is set to 10 and the duration for the low event trigger is extended to 300 seconds:

mondef -H 33 -T system.threshold.high system.threshold.memoryutiliz

mondef -L 10 -D 300 -T system.threshold.low system.threshold.remainingdiskspace

You do not need to reference the former trigger values since the new values overwrite the previous values.



SEE ALSO EVENT

HMON

INTNET

LPAN

MON

PSERVER



2-128

NFS

PM5.2_BF 2-129

NFS

NAME nfs - creates a network filesystem resource that PAN Manager mounts from a shared NFS server directory to a mount point on a pServer that the pServer’s services can access.

SYNOPSIS nfs [-c] [-L description] [-A {"rw"|"ro"}] [-H {hostname |ipaddress}] [-F filesystemname] [-M mount_point] [-m yes|no] [-O "mount_command_options"] lpanname/nfsname

nfs -N newname lpanname/nfsname

nfs [-l] lpanname [/nfsname]

nfs -d lpanname/nfsname

DESCRIPTION The PAN Manager nfs command creates a network filesystem (NFS) resource. LPAN Administrators use the nfs command to specify an NFS server hostname or host IP address, a pServer mount point, and a filesystem name of the shared disk or directory. Administrators can specify the access permission (read-write or read-only) and Linux mount command options as well as rename, delete, or create a description for a specified NFS resource.




lpanname/nfsname

Specifies the name of an NFS resource in an LPAN. NFS resources are unique to an LPAN. Use the nfs -l command to list the NFS resources within the LPAN.


2-130 PM5.2_BF

OPTIONS -A, --access-mode {"rw"|"ro"}

Specifies whether an NFS resource accesses the specified hostname’s filesystem with read-write (rw) or read-only (ro) privileges.

-c, --create

Creates an NFS resource available to all pServers within an LPAN.

-d, --delete

Removes an NFS resource from an LPAN.

-F, --host-filesystem filesystemname

Specifies a valid hostname filesystem name for the shared disk or directory.

-H, --host {hostname|ipaddress}

Specifies the hostname or IP address of an NFS server available on an LPAN Administrator’s network.


Specifies a description for the NFS resource.

-l, --long

Lists current NFS resources within an LPAN.

-m, --create-mountpoint {yes|no}

Specifies whether to create a new mountpoint on the pServer if it does not exist.

-M, --set-mountpoint mount_point

Specifies a directory path on a pServer’s filesystem that PAN Manager will use as the directory mount point for the specified NFS resource.

-N, --rename new_name lpanname/nfsname

Renames the specified NFS resource.

NFS

PM5.2_BF 2-131

-O, --mount-option mount_command_options

Specifies additional Linux mount command arguments PAN Manager can use when an LPAN Administrator is creating or modifying an NFS resource.

EXAMPLES The following example creates a mount point with read and write access for the /home/mylogin directory on the LPAN LP_mylogin:

nfs -c -A "rw" -H 192.23.20.2 -F /home/mylogin -M /mnt/temp -m yes LP_mylogin/nfs

List the parameters of the NFS resource of the LPAN LP_mylogin to verify that the mount point has been created successfully:

nfs -l LP_mylogin



SEE ALSO APP

FS



2-132 PM5.2_BF

PAN

NAME pan - lists and modifies the PAN configuration.

SYNOPSIS pan [-l [-i [-R |-I |-J image_name]]][domainname]

pan [-b |-s [--force] |-x] [domainname]

pan [-L description] [-o owner] [-w owner_location] [-W {yes|no}] [domainname]

pan -a {-R -C image_location -F fs_type| -I [-C image_location]} [-T OS_type] [-P description] image_name

pan {-R [-F fs_type] |-I}[-N new_image_name -T OS_type -P description] [--update-image image_location [--force]] image_name

pan -a -J -C image_location [-T OS_type][-P description] image_name

pan -J [-N new_image_name][-T OS_type][-P description] [--update-image image_location [--force]] image_name

pan -f fs_type root_image_name

pan -r |-y {-R |-I | -J} image_name

pan -z {-R |-I}

pan [--set-default-hypervisor-image image_name | --clear-default-hypervisor-image]

pan --set-hypervisor-password password

pan -E [-aA |-rA emailaddress] [-V {1-6}] [-Q {yes|no}]

pan -X {file |"(SCSI_ID)"}[-j] [-M newarchivename] [archivename]

pan -Y {file |"(SCSI_ID)"}[-M newarchivename] [archivename]

pan {-K [-l] |-S [-j]} [archivename]

pan -K -H "(SCSI_ID)"

pan -v panname

pan [-m resourcemapfile [-h] [-t] | -c [--force] |-D [-H "(SCSI_ID)"] |-g [-G name_map] |-M newarchivename] archivename

pan -k [schedulename]

PAN

PM5.2_BF 2-133

pan -q schedulename

pan -p schedulename -n "frequency:hour:min" [-H "(SCSI_ID)"]

pan -e |-d | {-l -u}

pan --set-name newpanname

pan --set-system-evbs-image evbs_image_name

pan [--collect-save-state [--force][--exclude-log-history][--exclude-pan-trace]]|[--list-last-save-state]

pan -M newarchivename archivename

pan -S archivename

pan --modify-schedule schedulename [--rename-schedule newschedulename] [-n "frequency:hour:min"] [-H "(SCSI_ID)" | --set-default-location]

pan --rename-schedule newschedulename schedulename

pan {--export-images | --restore-images} {file | "(SCSI_ID)"}] [--use-san sanEntryName] [--overwrite-images] [--no-boot-images] [--no-root-images] [--no-media-images] [--no-firmware-images]

pan --erase-dr-disk "(SCSI_ID)"

pan --image-archive-status

DESCRIPTION The pan command lists the status of the platforms within a PAN administrative domain and lets a PAN Administrator use the pan command to do the following:

• List configuration information for all platforms and Storage Area Network (SAN) resources within the PAN administrative domain.

• Boot, reboot, or shut down all LPANs within the PAN administrative domain.

• Configure default actions for PAN administrative domain events.

• Add (register), remove, or modify the root image(s) for disks and boot image(s) for pServers within the PAN administrative domain.


2-134 PM5.2_BF

• Add (register) or modify media images for use by ALL pServers within the PAN administrative domain.

• Import. export, and merge a PAN configuration archive.

• Implement disaster recovery (PAN archiving) plans or facilitate a periodic switching from one configuration to another.

• Enable or disable the PAN Manager Linux user account tool.

• Enable or disable flow control for the PAN domain.

Without any arguments, the pan command lists configuration information for all resources within the PAN administrative domain.

For additional details about archiving for disaster recovery, refer to the OPTIONS and PAN Manager Administrator’s Guide .




archivename

Specifies the name of a PAN archive.

panname

Specifies the name of a PAN domain.

"(SCSI_ID)"


PAN

PM5.2_BF 2-135






OPTIONS -a, --add image_name

Adds a display name for a disk root image, a boot image for pServers, or a media image within the PAN administrative domain. Creating a new display name does not overwrite other images or display names. This option allows any number of display names for a given image. Boot and root images are copied to both cBlades in the /tftpboot directory, while PAN Manager manages usage of all media images on both cBlades. (Copying large media files to a particular area which could use up all available cBlade hard disk space.) PAN Administrators should check these directories for available area to ensure no size restrictions exist before registering the image.

PAN Administrators must register a media image for use by all pServers before a pServer can access the image by means of a virtual CD-ROM (VCD).

PAN Administrators must register a media image for use by all pServers before a pServer or hypervisor can access the image by means of a virtual CD-ROM (VCD).

To do so, PAN Administrators must mount the media (from one of the cBlades) or copy the media image (to one of the cBlades) then use the PAN Manager pan -a -J -C image_location imagename command, which allows you to manage media images that are stored on the cBlades, and helps you avoid using excess cBlade disk space.


2-136 PM5.2_BF

PAN Administrators must register any custom pServer image before multiple pServers can boot from it. PAN Administrators should note that registering a media image with PAN Manager makes the image available to all pServers in the PAN, that is, all pServers in all LPANs.

For more information on registering custom boot images, see the appropriate pServer Guide for the software release you want to install on the pServer.

-aA, --add-email emailaddress

Adds a recipient to the list of addresses to which email notification of PAN administrative domain events is sent. You must use this option with the -E (default-event-action) option to activate the setting. You set the severity criteria for email notification for administrative domain events with the -V (severity) option.

-b, --boot

Boots the PAN domain and all LPANs within it.

-C, --image-location image_location

Specifies the directory path on the cBlades containing the root, boot, and media images within the PAN administrative domain. Boot and root images are copied to both cBlades in the /tftpboot directory, while PAN Manager manages usage of all media images on both cBlades (copying large media files to a particular area which could use up all available cBlade hard disk space).

-c, --swap archivename

Replaces the current PAN domain configuration with the PAN configuration archive. Swapping an imported PAN configuration archive automatically validates the archive file with the target platform physical resources before attempting the swap, even if you separately perform a validation with the -v (validate) option. A swap cannot occur until it is free of validation errors.

PAN

PM5.2_BF 2-137

--clear-default-hypervisor-image

Specifies that you do not want any hypervisor ISO image set as the default.

--collect-save-state [--force][--exclude-log-history][--exclude-pan-trace]

Instructs PAN Manager to collect save state information from both cBlades. This option recognizes additional options including --force (allows you to overwrite the existing save state file without being prompted), --exclude-log-history (omits information from expired event logs from the save state file), and --exclude-pan-trace (omits stack trace information from the save state file).

If for some reason PAN Manager is not running, PAN Administrators can log on to either accessible cBlade and run the save state script manually:

# /opt/egenera/bin/save_state pathname.tar.gz

where pathname is the full pathname of the resulting compressed tar file. This action gathers save state information only for the cBlade to which you logged on.

-D, --delete-panarchive

Deletes a specific PAN archive file.

-d, --disable-user-account

Disables PAN Manager control of Linux user accounts. This configuration enables third-party tools to manage Linux user accounts, and disables the account command.

-E, --default-event-action

Activates event type actions for all events in the PAN administrative domain. Use this option to set the criteria and email recipients for sending email notification of events with the -aA (add-email) and -V (severity) options.


2-138 PM5.2_BF

Use this option to activate or de-activate the sending of SNMP traps with the -Q (send-snmptrap) option. For more information on configuring events, triggers, and SNMP, see PAN Manager Administrator’s Guide.

-e, --enable-user-account

Enables PAN Manager to create and remove Linux user accounts. This is the default configuration and enables the account command.

--erase-dr-disk “(SCSI_ID)"

Removes all the disaster recovery image archives that are on the disaster recovery disk.

--export-images {file | "(SCSI_ID)"}

Exports a set of images to a SAN disk, a designated location on the master cBlade, or a network location accessible from the master cBlade. The PAN Administrator can specify 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, media images (VCDs), and/or pBlade firmware images.

You can export PAN configuration archives to a local disk on a cBlade or to a SAN volume as a way to back up the configuration outside the platform (in conjunction with SAN volume HW mirroring software such as EMC SRDF or EMC MirrorView). PAN archiving can be configured to occur on a periodic schedule, which can ensure that recent backups are available. Archived PAN configurations can be used for different purposes, including the following:

• To repair damaged PAN configuration files.

• To restore a destroyed or incapacitated platform onto a disaster recovery platform.

• To retarget a platform.

PAN

PM5.2_BF 2-139

-F, --file-system-type fs_type(s)

Specifies one or more filesystem type(s) associated with a root image. PAN Administrators use this option with the -a (add), -R (root-image), and -C (image_location) options to associate the filesystem type(s) with a newly added root image. They use this option with the -R (root-image) options to modify the association between a root image and a filesystem type. PAN Administrators use the -f (set-default-file-system) option to set a default filesystem for a specific root image. PAN Manager supports ext2 and ext3 (Red Hat) filesystem types.

-f, --set-default-file-system fstype root_imagename

Specifies the default filesystem type for a root image. PAN Administrators can set the default filesystem type for all the root images LPAN Administrators use to create their pServers in the PAN administrative domain. Only PAN Administrators have the ability to create, modify, or remove this setting. You can see the default installation setting using the pan -i command. See the disk man page or PAN Manager Administrator’s Guide for more information. PAN Manager supports ext2 and ext3 (Red Hat) filesystem types.

--force

Forces a PAN operation without a prompt. PAN Administrators use this option with the -s (shutdown) option to gracefully shut down all operations in the PAN domain without a prompt.

-g, --merge archivename

Replaces data in the specified PAN configuration archive with data from the basic configuration of the target platform for the settings listed in the DESCRIPTION section of the pan command. You cannot merge the PAN configuration archive until it is imported to the target platform using the -Y (import) option.

-H, --sandisk "(SCSI_ID)"

Specifies a SAN disk target that has a PAN configuration archive file. Use this option in combination with the -D (delete), -K (list-PAN-archive), or -p (add-schedule) options.


2-140 PM5.2_BF

-h, --mergereths

Deletes all rEths and vSwitches using those rEths from a PAN configuration archive. Use this option only in combination with the -m (map) option.

-I, --boot-image image_name

Specifies a boot image that PAN Administrators register with PAN Manager for all pServers within the PAN.

Important: This file cannot be updated while the image is currently in use by any pServer. If it is configured by pServers, the --force option is required.

-i, --list-images

Displays the registered root disk, boot, and media images for the PAN. By itself, this option lists only the display names for the root disk and boot images; with the -l (long) option, the display name, image location, OS type, and description also appear. This command can be used by PAN Administrators, LPAN Administrators, LPAN Monitors, and LPAN Operators.

--image-archive-status

Displays the status of any image archive operation in progress. This will show whether there is an export or restore running, or, if none are running, the time that the last one finished. It will also give information about how it finished (successful, failed, and so on). If it is still running, information about what part of the process it is in (such as creating the archive, writing the archive to SAN, or restoring the media images) will be displayed. This information is only held in memory, so if PAN Manager restarts, or fails over, the last run job information would be lost.

-J, --media-image image_name

Specifies a media image that PAN Administrators register with PAN Manager for all pServers within the PAN to use. After you mount (from one of the cBlades) or copy the media image (to one of the cBlades), PAN Administrators use this option with the -a

PAN

PM5.2_BF 2-141

(add), -C (image_location), and -P (description) options to register the image with PAN Manager.

This command option allows you to manage media images that are stored on the cBlades, and helps you avoid using excess cBlade disk space. For more information about disk space on cBlades, contact Fujitsu Technology Solutions customer support or your authorized support vendor. PAN Administrators should note that registering a media image with PAN Manager makes the image available to all pServers in the PAN, that is, all pServers in all LPANs.

Important: A file cannot be updated if the image is currently inserted into the virtual CD (VCD) of a pServer that is not shutdown (booting, booted, suspended, or shutting down). If the media file is inserted into the VCD of a pServer that is shutdown, you can modify the image by using the --force option.

-j, --include-logs

Specifies that the following log files under /opt/panmgr/logs are included when you save a PAN archive:

• console.log

• tomcat.log

• egenera_cli.log

• tftp.log

Depending on the size of these log files, this action can add a significant amount of time to any subsequent archiving process for this particular PAN archive file.

-K, --list-PANarchives

Displays the names or the names and settings (using the -l (long) option) of the PAN archives that have been saved to the cBlade of the current platform. Use this option in combination with the -H "(SCSI_ID)" option to specify a SAN disk containing one or more PAN archives.


2-142 PM5.2_BF

A PAN archive does NOT include the following settings or files, which you may need to recreate on the target platform for a disaster recovery plan:

• Linux user accounts and any files there

• cron files

-k, --list-schedule schedulename

Displays the settings for the specified archive schedule.

-L, --label "text"

Adds descriptive text to a PAN administrative domain configuration for administrator reference. Descriptive text containing spaces must use quotation marks to avoid parsing errors.

-l, --long

Displays more detailed information about PAN resources than using the pan command without an argument.

--list-last-save-state

Lists useful information about the last (if any) save state that was created. You can use the PAN Manager CLI or GUI interchangeably to create a save state file. Only one save state file can exist at any given time (on the master cBlade: /opt/panmgr/large_tmp/panname_save_states.tar).

-M, --rename-PANarchive “newarchivename” archivename

Allows a PAN Administrator to rename the specified PAN configuration archive.

-m, --map resource-map-file archivename

Replaces settings in a PAN archive with settings in a resource map file, specified using the full file pathname. This map must exist on a local, master cBlade, and must conform to the format specified in the Resource Mapping section in the DESCRIPTION section of the pan command.

PAN

PM5.2_BF 2-143

--modify-schedule schedulename

Modifies a specific schedule configured in the PAN. Use this option with the --rename-schedule newschedulename or -n "frequency:hour:min" or --sandisk "(SCSI_ID)" options. Remember, descriptive text that contains spaces must use quotation marks to avoid parsing errors.

-N, --image-name new_image_display_name

Renames the specified root, boot, or media image for the PAN administrative domain.

-n, --schedule-time "frequency:hour:min"

Specifies an archiving schedule frequency and 24 hour time of day. Use this option combined with the -p (add-schedule) option to add the necessary details for the archive schedule. Specify a daily or weekly frequency using either the string "daily" or the day of the week the weekly archiving should be done. For example, the string "daily:14:30" specifies creating a PAN archive each day at 14:30, while the string "Tuesday:14:30" specifies creating a PAN archive each week on Tuesday at 14:30. You must spell the day of week correctly, in either uppercase or lowercase.

--no-boot-images

Specifies not to include the boot-image in the PAN archive. Used only with the --export-images or --restore-images options.

--no-firmware-images

Specifies not to include the firmware-image in the PAN archive. Used only with the --export-images or --restore-images options.

--no-media-images

Specifies not to include the media-image in the PAN archive. Used only with the --export-images or --restore-images options.

--no-root-images

Specifies not to include the root-image in the PAN archive. Used only with the --export-images or --restore-images options.


2-144 PM5.2_BF

-o, --owner "text"

Indicates the person who determines the operating configuration of the PAN administrative domain. Descriptive text that contains spaces must use quotation marks to avoid parsing errors.

--overwrite-images

Overwrites any duplicate image already in archive. Perform the overwrite operation only at a time when there is very little frame activity, so you do not end up writing over and removing files that are in use. Used with the --export-images or the --restore-images options.

-P, --image-description "text"

Adds descriptive text to a root or boot image used in the PAN administrative domain configuration. Use this option with the -a (add) or the -R (root-image) or -B (boot-image) options. Descriptive text that contains spaces must use quotation marks to avoid parsing errors.

-p, --add-schedule schedulename -n "frequency:hour:min"

Schedules the current PAN configuration to be saved as a PAN archive file on the master cBlade (Default) or to a specified disk -H (sandisk). The name of the scheduled archive is automatically derived from the current PAN configuration. You can modify a current schedule by specifying the schedule and resetting the -n (schedule-time) option. You can rename the archive file later using the -M (rename-PANarchive) option.

-Q, --send-snmptrap {yes|no}

Specifies whether an SNMP trap is sent for any event within the PAN domain. You must use this option with the -E (default-event-action) option. See PAN Manager Administrator’s Guide for more information on configuring events, triggers, and SNMP.

-q, --remove-schedule schedulename

Removes a specific schedule configured in the PAN.

PAN

PM5.2_BF 2-145

-R, --root-image root_image_display_name

Specifies a root image that PAN Administrators register with PAN Manager for all pServers within the PAN.

Important: A file cannot be updated if it is currently being used to root a disk. Concurrent attempts to root a disk while you attempt to modify the image file will fail until the current rooting or modification is complete. PAN Manager returns an error message until the first operation is complete.

-r, --remove image_display_name

Removes a root or boot image from pServers within the PAN administrative domain. Removing an image currently listed as a default root disk or boot image leaves the PAN administrative domain without a default root disk or boot image.

-rA, --remove-email emailaddress

Removes a recipient from the list of addresses to which email notification of PAN domain events are sent. You must use this option with the -E (default-event-action) option.

--rename-schedule "newschedulename" schedulename

Renames a specific schedule configured in the PAN.

--restore-images {file | "(SCSI_ID)"}

Restores a set of archived images from a SAN disk, a designated location on the master cBlade, or network location accessible from the master cBlade. This command can only be executed by the PAN Administrator.

-S, --save archivename

Saves the current PAN configuration as an archive file with the same name. You can later rename the archive file, using the -M (rename-PANarchive) option. Saving a PAN archive places the file on the current cBlade you are logged into or on the master cBlade if you are logged into PAN Manager.


2-146 PM5.2_BF

-s, --shutdown

Shuts down the PAN domain and all LPANs within it. This command halts the processing for all the pBlades within the PAN domain.

Caution: PAN Administrators use this command to shut down all current LPANs within the PAN domain and should warn LPAN Administrators well in advance when using this command option.

--set-default-hypervisor-image image_name

Specifies the display name of a particular hypervisor ISO image (as registered in the PAN) to set as the default. To view a list of the registered hypervisor ISO images and their display names, use the PAN Manager command pan -i.

--set-default-location

Set the default location of a specific archive schedule configured in the PAN.

--set-hypervisor-password password

Specifies that you want to change the current hypervisor root password. PAN Manager applies your password change to all hypervisors in the PAN, whether or not they are currently running.

You need the hypervisor root password when logging on to a hypervisor console. The default password is egenera, but it is recommended that you change this to ensure security.

--set-name newpanname

Specifies a new name for the PAN. If the chosen name is in use by other PANs on the same LAN subnet, PAN Manager generates a warning.

--set-system-evbs-image evbs_image_name

Specifies the display name of a particular boot image (as registered in the PAN) to set as the system EVBS image. To view a list of the registered boot images and their display names, use the PAN Manager command pan -i. Use system EVBS for ramdisk

PAN

PM5.2_BF 2-147

installs. See PAN Manager Administrator’s Guide for an overview of booting pServer images.

-T, --os-type "text"

Adds descriptive text about the operating system with which a root or boot image is associated in the PAN administrative domain. Use this option with the -a (add) or the -R (root-image) or -B (boot-image) option. Descriptive text that contains spaces must use quotation marks to avoid parsing errors. This option must be used to register WinPE images.

-t, --map-disk-by-UID

Used with the -m option, maps disks according to their unique IDs.

-u, --user-account

Toggles whether PAN Manager software is enabled to create Linux accounts (true) or if it is disabled so PAN Administrators must rely on third party Linux account management tools (false). A false setting means that the PAN Manager account command is disabled. This option requires the -l (long) option.

--use-san sanEntryname

Specifies that you want the image archive to go to a SAN disk. The sanEntryname is the name of the image archive entry on the SAN disk. Used with the --export-images or the --restore-images options.

--update-image image_location image_name

Specifies that you want to modify a root, boot, or media image registered with PAN Manager. PAN Administrators can modify these images as long as the image is not in use by a pServer. Combine this option with the following options:

• -I (boot-image) — to modify a boot image. If the boot image is configured by pServers, you must use the --force option.

• -R (root-image) — to modify a root image. The file cannot be updated if it is currently being used to root a disk.


2-148 PM5.2_BF

• -J (media-image) — to modify a media image. The file cannot be updated if the image is currently inserted into the virtual CD (VCD) of a pServer that is not shutdown (booting, booted, suspended, or shutting down). If the media file is inserted into the VCD of a pServer that is shutdown, you can modify the image by using the --force option.

-V, --email-severity severity_number

Sets the severity criteria for email notification for PAN administrative domain events. You must use this option with the -E (default-event-action) option. By default this value is 2.

-v, --validate

Checks the current physical resources with those listed in the current (target) PAN. This ensures that after you have modified a PAN configuration archive to work with the current (target) platform configuration, a swap (using the -c (swap) option) will work with the current physical resources.

-W, --flow-control {yes|no}

Activates or deactivates global flow control for broadcast network traffic between pServers. By default, global flow control for the PAN domain is not enabled.

NOTE: Global flow control is not supported for vBlades or any pServers running the Microsoft Windows(TM) operating system.

NOTE: Global flow control is not supported for any pServers running the Microsoft Windows(TM) operating system.

PAN Administrators activate global flow control for a PAN domain to ensure that no broadcast packet loss occurs between any pServers in the PAN domain. Such global traffic flow control between pServers is different from flow control for all external network traffic flowing through a specific rEth. To activate external flow control for a rEth, use the reth -F yes command.

PAN

PM5.2_BF 2-149

-w, --owner-location "text"

Adds descriptive text to a PAN administrative domain configuration specifying where the PAN Administrator is physically located. Descriptive text that contains spaces must use quotation marks to avoid parsing errors.

-X, --export {dir | "(SCSI_ID)"}

Specifies a directory or SCSI path device on which to save a PAN archive. By default, exporting a PAN configuration creates an archive file named after the PAN domain from which it was created. To specify a non-default name for the archive file, use the -M (rename-PANarchive).

For more information, see the “Archiving for Disaster Recovery (PAN archiving)” section of PAN Manager Administrator’s Guide.

Caution: PAN Administrators temporarily shut down all current LPANs within the PAN domain with this command and should warn LPAN Administrators well in advance when using this command option.

-x, --reboot

Reboots the PAN domain. PAN Administrators use this command to reboot all the LPANs (and the current pServer configurations in each LPAN) within the PAN domain.

-Y, --import {dir | "(SCSI_ID)"}

Specifies a directory or SCSI path device from which to import a PAN archive. By default, importing a PAN configuration creates a local archive file in the /opt/panmgr/pars directory on both cBlades named after the PAN. To specify a different name for the archive file locally, use the -M (rename-PANarchive).

For more information, see the “Archiving for Disaster Recovery (PAN archiving)” section of PAN Manager Administrator’s Guide.


2-150 PM5.2_BF

-y, --set-default-image image_display_name

Specifies the default root and boot images for a PAN administrative domain. PAN Administrators can set the default root and boot images from a list of available images LPAN Administrators use to root disks or create their pServers in the PAN administrative domain. Only PAN Administrators have the ability to create, modify, or remove this setting. You can see the default installation setting using the pan -l command. LPAN Administrators use the pserver -l command to see the default setting. For more information, see the disk or pserver man page or PAN Manager Administrator’s Guide.

-z, --clear-default-image {-R |-I}

Clears any default boot or root disk image assignment for a PAN domain.

EXAMPLES List the current platforms and their current state within the PAN domain:

pan

Display whether the PAN Manager user account tool is enabled for the PAN domain:

pan -u -l

Reboot all the LPANs in the PAN domain Development_Lab

pan -x Development_Lab

List display names of PAN registered images (this includes boot, root, and media images such as ISO images):

pan -i

Display detailed information about these images:

pan -i -l

PAN

PM5.2_BF 2-151

Register a boot or root WinPE image:

pan -a -I -C /tftpboot/winpe_x86_gs.tgz -T WINPE winpe_x86_gs

Rename the 32-bit RHEL 4.2 boot image (named RHEL420xxxxI_IA32 by default) to RHEL42_32bit_bootimage:

pan -I -N "RHEL42_32bit_bootimage" RHEL420xxxxI_IA32

Set the newly renamed, 32-bit RHEL 4.2 boot image RHEL42_32bit_bootimage as the default boot image for all pServers in the PAN domain:

pan -y -I RHEL42_32bit_bootimage

Set the name of the PAN to "PAN_002A":

pan --set-name "PAN_002A"

Set the PAN’s default hypervisor ISO image to HVXS21_210nnnn_X86_64:

pan --set-default-hypervisor-image HVXS21_210nnnn_X86_64

Clear the PAN default hypervisor ISO image setting:

pan --clear-default-hypervisor-image

Change the hypervisor root password in the PAN to t0pSecret:

pan --set-hypervisor-password t0pSecret




2-152 PM5.2_BF

SEE ALSO ACCOUNT

BFRAME

DISK

EVENTTYPE

LPAN

PSERVER

SNMP


PANMGR

PM5.2_BF 2-153

PANMGR

NAME panmgr - lists information about the current PAN Manager software.

SYNOPSIS panmgr [-v]

DESCRIPTION The panmgr command lists information about the Control Blades (cBlades) and the current version, compatibility number, and build number of PAN Manager running on each cBlade.

Using the panmgr command without an argument displays the current role (master or slave) and up since (date and time) information for each cBlade.

OPTIONS -v, --version

Limits the display to the current PAN Manager version and build number.

EXAMPLES List the current version of PAN Manager software:

panmgr -v

Output similar to the following appears:

my_platform1/c1 5.2.7 (build 1667)my_platform1/c2 5.2.7 (build 1667)

Important: The three segment number indicates that the PAN Manager version number is 5.2, and that the cBlade compatibility number is 7. (The compatibility number is for internal use only, and does not represent part of the PAN Manager release number.)


2-154 PM5.2_BF

List the cBlades’ master/slave status:

panmgr



PIM

PM5.2_BF 2-155

PIM

NAME pim - lists or modifies hardware and configuration settings for a specified Redundant Power Input Module (PIM-R).

SYNOPSIS pim [-p "A"|"B"|"none"] [-A amperage_event_trigger] [-a][-W wattage_event_trigger] [-w] platformname/pimn

pim [-e "yes"|"no"] platformname/pimn

pim [--select |--unselect] platformname/pimn

pim [-l] platformname/pimn

DESCRIPTION The pim command lists the status of specified PIM-R devices (includes current PIM-R data displays) and allows administrators to configure and modify PIM-R settings. Administrators use the pim command to:

• Display status and settings for one or all PIM-R devices

• Select and unselect a PIM-R device (similar to select and unselect for a blade)

• Enable and disable the PIM-R power line preference

• Set a preferred power line (A, B, or none)

• Set or clear a PAN Manager event trigger limit for current (in Amperage) and power (in Wattage)

PAN administrator and Operator roles have read/write permissions to configure PIM-R devices; PAN Monitor roles have read-only permissions to display current PIM-R settings.

PAN Manager must be running on the cBlades to take advantage of the PAN Manager pim command. The pim command is disabled on systems that do not support the PIM-R option.


2-156 PM5.2_BF

Choosing a Line Preference For Each PIM-R

A PIM-R device connects a single power domain to two redundant power sources. BladeFrame BF400 S2 requires four PIM-R devices, which are connected through the BladePlane. If the primary power source fails, the PIM-R automatically switches to the secondary power source, thereby maintaining constant power to the PIM-R device’s power domain.

You set a primary power line preference for one of the two power line inputs. You make this selection either physically using the PIM-R device’s Line Preference Select button or using the pim -p (preferred) command option. The default settings on a new PIM-R are that the Line Preference Select button is enabled and PAN Manager’s line preference setting is set to “none.” PAN Manager persists setting modifications in the event that you replace a PIM-R device.

Setting a power line preference (A or B, which is labeled on each PIM-R device) through PAN Manager automatically disables the Line Preference Select button on the PIM-R device. To re-enable the Line Preference Select button through PAN Manager, you must use the pim -e "yes" command). This command sets the PAN Manager line preference setting to “none” and prevents conflicting preference settings between PAN Manager and the Line Preference Select button.



Additional naming convention considerations for this command include:

PIM

PM5.2_BF 2-157

platformname/pimN

Specifies a PIM-R, where 1 >= N <= 4. PAN Manager naming conventions require you to use a forward slash (/) between the platform name and PIM-R number. For example, pim2 on the platform named Production would be referred to as Production/pim2. PIM-R devices are numbered one to four from the bottom up, according to their slot location on the BladePlane. PAN administrators use the bframe command to name or rename a platform.

OPTIONS -a, --clear-current-limit

Removes any current limit that was set using the -A (current-limit) option.

-A, --current-limit {amperage_event_trigger}

(BladeFrame EX only) Specifies an amperage at which the PIM-R device triggers a PAN Manager event. Valid values (in Amps) are integers in the range of 0 to 51.

Only use the pim -A or -W options to set PAN Manager event triggers. Do not use these options to configure PIM-R voltages. See the bframe command for details on configuring the voltage input to a PIM-R device. For more information about configuring voltage, see the PAN Manager Administrator’s Guide.

-e, --enable-pref-button {"yes"|"no"}

Specifies whether the power line preference button (labeled Line Preference Select) on a specified PIM-R is enabled. The default setting for a new PIM-R is that the Line Preference Select button is enabled. If the Line Preference Select button on a PIM-R is disabled, the button on the PIM-R does nothing when you press it. Configuring the PIM-R device’s power line preference using the -p (preferred) option automatically disables the Line Preference Select button. PAN Manager persists any setting modifications in the event that you replace a PIM-R device.


2-158 PM5.2_BF

-l, --long

Displays the current PIM-R device settings.

-p, --preferred-power {"A"|"B"|"none"}

Specifies a preferred (if any) power line for the primary power source for a specified PIM-R and automatically disables the Line Preference Select button on that PIM-R device. If at any time the Line Preference Select button is re-enabled through PAN Manager (using the pim -e "yes" command), PAN Manager’s preferred power line setting is reset to “none.” The default setting on a new PIM-R is that the line preference is set to “none.” PAN Manager persists any setting modifications in the event that you replace a PIM-R device.

--select platformname/pimN

Causes the indicator lights on a specified PIM-R device LED to blink blue. Fujitsu Technology Solutions recommends using this feature to help locate a specific PIM-R on the BladePlane. The blinking blue indication persists until reset with the --unselect option.

--unselect platformname/pimN

Terminates the blinking blue indication on a specified PIM-R device. The indicator light on the PIM-R reverts to its normal meaning: steady amber for recognized, steady blue for active.

-w, --clear-power-limit

Removes any power limit previously set with the -W (power-limit) option.

-W, --power-limit {wattage_event_trigger}

Specifies a wattage at which the PIM-R device triggers a PAN Manager event. Valid values (in Watts) are integers in the range of 0 to 6375.

Only use the pim -A or -W options to set PAN Manager event triggers. Do not use these options to configure PIM-R voltages. See the bframe command for details on configuring the voltage input to

PIM

PM5.2_BF 2-159

a PIM-R device. For more information about configuring voltage, see the PAN Manager Administrator’s Guide.

EXAMPLES List the current settings of PIM-R device pim1 on platform PlatformOne:

pim -l PlatformOne/pim1

For PIM-R device pim1 on platform PlatformOne, set the preferred power line to A (this setting disables the Line Preference Select button on the PIM-R device); and set PAN Manager to trigger an event if the PIM-R amperage reaches 30 amps or the wattage reaches 1500 watts:

pim -p "A" -A 30 -W 1500 PlatformOne/pim1

Re-enable the Line Preference Select button on this device (this resets the PAN Manager’s line preference setting to “none”):

pim -e "yes" PlatformOne/pim1



SEE ALSO BFRAME

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_bframe).


2-160 PM5.2_BF

POOL

NAME pool - creates, lists, or modifies a set of Processing Blades (pBlades) for a local or global pool.

SYNOPSIS pool [-l] [globalpoolname | lpanname/localpoolname]

pool [-c | -d] {globalpoolname | lpanname/localpoolname}

pool [-L "descriptiontext"] [-n newname] {globalpoolname | lpanname/localpoolname}

pool [-G globalpoolname | -g] lpanname/localpoolname

pool [-a | -r] platformname/pn globalpoolname

pool [-a | -r] platformname/pn[-n] lpanname/localpoolname

pool [-a | -r] platformname/pn lpanname/localpoolname

DESCRIPTION The pool command allows PAN Administrators to create, list, or modify a global pool of pBlades, or LPAN Administrators to create or remove a local pool of pBlades or vBlades to be used by pServers. PAN Manager prohibits you from allocating vBlades to a global pool.

The pool command allows PAN Administrators to create, list, or modify a global pool of pBlades, or LPAN Administrators to create or remove a local pool of pBlades to be used by pServers.

PAN Manager enforces a limit on the total number of global pools and local LPAN pools that can be created: 20 global pools, 20 pools per LPAN, and 200 pools total.

Using the pool command, administrators perform the following pBlade pool tasks:

• (PAN Administrators only) Create, list, or modify a global pool.

• Create or remove a local pool.

POOL

PM5.2_BF 2-161

• Add pBlades to pools

• Link a global pool to a local pool.

PAN Administrators can create multiple global pools by7 giving them unique names. Administrators can create and authorize access to a global pool for each type of pBlade architecture you have in a PAN. The LPAN Administrator can then link an existing local pool to this global pool.

• Configure a designated failover pool.

A pServer cannot have a pBlade assignment (primary or failover) designated by pBlade architecture type; however we recommend that PAN or LPAN Administrators create global or local pools made of similar types of pBlades by processor-type to ensure that a pServer obtains a pBlade from a pool that is appropriate for its requirements. Assigning pBlades with large memory configurations and fast processor speeds to the same pool ensures that pServers requiring these pBlade resources always obtain a primary or failover pBlade of a suitable type.




platformname/pn




2-162 PM5.2_BF




platformname/pn-n





globalpoolname

Specifies a global pool name.

lpanname/localpoolname

Specifies a local pool name within an LPAN. More than one local pool can have the same name in the PAN domain as long as the locals pools are not in the same LPAN.

OPTIONS -a, --addblade {platformname/pn globalpoolname} | platformname/pn[-n] lpanname/localpoolname}

Allocates a specified pBlade to a specified global or local pool or allocates a specified vBlade to a specified local pool.

-a, --addblade {platformname/pn globalpoolname} | platformname/pn lpanname/localpoolname}

Allocates a specified pBlade to a specified global or local pool.

POOL

PM5.2_BF 2-163

-c, --create

Creates a specified global (PAN Administrator only) or local pool (LPAN Administrator only). PAN Manager enforces a limit on the total number of global pools and pools per LPAN that can be created: 20 global pools, 20 pools per LPAN, and 200 pools total.

-d, --delete

Deletes a local or global pool.

-g, --clear-global lpanname/localpoolname

Clears the link between the local pool lpanname/localpoolname and any global pool. It is not necessary to specify the name of the global pool, because a local pool can only link to one global pool.

-G, --set-global globalpoolname lpanname/localpoolname

Sets a link between local pool lpanname/localpoolname and global pool globalpoolname. PAN Manager allows the local pool to access only one global pool at a time. To allow a pServer to access more than one global pools of pBlades, LPAN Administrators must create a local pool for each global pool that they want pServers to access.

-l, --list

Lists the current pBlades assigned to the specified global or local pool. With no argument, this option lists settings and status of all local and global pools.

-L, --description "text" {globalpoolname | lpanname/localpoolname}

Adds text to the description field for a global or local pool. Descriptions are limited to 1024 characters in length.

-n, --rename newpoolname {globalpoolname | lpanname/localpoolname}

Renames the specified local or global pool.


2-164 PM5.2_BF

-r, --removeblade {platformname/pn globalpoolname} | platformname/pn[-n] lpanname/localpoolname}

-r, --removeblade {platformname/pn globalpoolname} | platformname/pn lpanname/localpoolname}

Removes the specified pBlade from the specified global or local pool. You cannot remove a blade from a local pBlade pool if it is a pServer’s current pBlade, and you cannot remove a pBlade from a global blade pool if it is a pServer’s current pBlade, unless you are removing the pBlade from the global pool and adding it to the LPAN in which that same pServer resides.

EXAMPLES Create a global pool named global_x86s:

pool -c global_x86s

Create a local pool named local_x86s in the LPAN DEPT7 and link it to global pool global_x86s:

pool -c -G global_x86s DEPT7/local_x86s

Add pBlade 1 in platform DIV_PLATFORM to the global pool global_x86s

pool -a DIV_PLATFORM/p1 global_x86s

Add pBlade 2 in platform DIV_PLATFORM to local pool local_x86s in the LPAN DEPT7 (the pBlade must already be present in the LPAN in which the local pool resides):

pool -a DIV_PLATFORM/p2 DEPT7/local_x86s

Add text to the description field of global pool global_x86s:

pool -L "This pool contains x86 blades for use by all division LPANs" global_x86s

List only the names of blade pools (local and global) and their contents, to which you have access:

pool

POOL

PM5.2_BF 2-165

List all blade pools (local and global) and their contents, to which you have access:

pool –l

Add vBlade p7-1 (on platform zeus) to the local pool named pool in the doc LPAN:

pool -a zeus/p7-1 doc/pool

Remove vBlade p7-3 (on platform zeus) from the local pool named pool in the doc LPAN:

pool -r zeus/p7-3 doc/pool



SEE ALSO LPAN

PAN

PSERVER



2-166 PM5.2_BF

PSERVER

NAME pserver - creates, lists, or modifies a pServer configuration within an LPAN.

SYNOPSIS pserver -a "(SCSI_ID)" [-f] [-A {yes|no}] [-o {yes|no}] lpanname/pservername "(X.0)"

pserver -a switchname [-f][-P {10Mb|100Mb|no}] [-G "macaddress"] lpanname/pservername vethn

pserver -d [-f] lpanname/pservername

pserver -b [-I boot_image] [-K "boot_args"] [-w [-q]] lpanname/pservername

pserver -s [-f] [-T "min" -M "textmessage"] [-w [-q]] lpanname/pservername

pserver -x [-I boot_image] [-K "boot_args"] [-f] [-T "min" -M "textmessage"] [-w [-q]] lpanname/pservername

pserver --pan-boot-image image_name lpanname/pservername

pserver [-B|-F] {platformname/pn[-n] | localpoolname | "none"} lpanname/pservername

pserver [-B|-F] {platformname/pn | localpoolname | none} lpanname/pservername

pserver [-l] [lpanname | lpanname/pservername]

pserver [-L "labeltext"] [-n new_pservername][-O activateorder] lpanname/pservername

pserver -m {"(X.0)"}[-D "(SCSI_ID)"] [-A {yes|no}][-o {yes|no}] lpanname/pservername

pserver -m vethn [-D switchname][-P {10Mb|100Mb|no}][-G "macaddress"] lpanname/pservername

pserver -M platformname/pn[-n] lpanname/pservername

pserver -M platformname/pn lpanname/pservername

pserver -o {yes|no} lpanname/pservername

pserver -p {yes|no} lpanname/pservername

pserver -r [-f] lpanname/pservername {vethn|"(X.0)"}

pserver [--fe|--fd|--fc] {ht|ni|ve|hp} lpanname/pservername

PSERVER

PM5.2_BF 2-167

pserver [--insert-vcd {media_image}|--eject-vcd] lpanname/pservername

pserver [-e|-u] DVD-ROMname lpanname/pservername

pserver [-c [-I boot_image [-K "boot_args"]]lpanname/pservername

pserver [-I boot_image |-i] [-K "boot_args"]lpanname/pservername

pserver [-S "(SCSI_ID)"|-R [platformname/pn[-n]]] lpanname/pservername

pserver [-S "(SCSI_ID)"|-R [platformname/pn]] lpanname/pservername

pserver --set-keyboard-map keyboardmap_name lpanname/pservername

DESCRIPTION The pserver command creates, lists, or modifies a pServer within an LPAN configuration. LPAN Administrators configure pServers by combining a Processing Blade (pBlade) with Storage Area Network (SAN)-accessible disk devices, Fibre Channel tape devices, and virtual switch (vSwitch) resources assigned to their LPAN. LPAN Administrators use the pserver command to do the following:

• Create, modify, or remove a pServer

• Specify a boot image and a boot order for a pServer

• Boot, shut down, suspend, resume, or reboot a pServer

Using the pserver command, LPAN Administrators configure the following pServer settings:

• pBlade resources — Specify whether the pServer uses a particular pBlade or obtains one from a pool of pBlades.

• SCSI disks from a SAN — Assign disk storage to a pServer.

• SCSI tape devices — Assign Fibre Channel tape devices to a pServer.

• vSwitches — Connect a pServer to internal communications and external networks.


2-168 PM5.2_BF

• DVD-ROMs — Access a physical DVD-ROM in an LPAN with shared access to the DVD-ROM drive located on either cBlade.

• Virtual CD-ROMs — Access a single virtual CD-ROM (VCD) attached to a pServer. In general, PAN Manager attaches one VCD device to a pServer and recognizes the device as unit number "(125.0)".

For vBlades running a hypervisor, PAN Manager allocates up to 32 VCDs, one for each Guest OS running on the hypervisor.




lpanname/pservername

PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the pServer name. For example, the pServer named Web1, in the LPAN named production is referred to as production/Web1. PAN Administrators use the lpan command to name LPANs, and LPAN Administrators use the pserver command to name pServers.

platformname/pn

Specifies a platform and a specific pBlade.



PSERVER

PM5.2_BF 2-169




platformname/pn-n





switchname

Specifies a virtual switch (vSwitch). (To create a vSwitch, use ther sw command.)

"(SCSI_ID)"








2-170 PM5.2_BF

"(X.0)"

Specifies the unit name of a media assignment of the pServer. When specifying unit name, enclose the Unit name in parentheses and quotation marks.

Caution: The unit name to which you assign a root filesystem for a pServer must be autoenabled for the pServer to boot.

vethn

Specifies the map name of vSwitch assignments of a pServer. You are allowed to map 31 vEths to a pServer and must use the naming convention: veth0, veth1, veth2...veth30. Each pServer is automatically configured with one additional vEth for communication with PAN Manager. This additional vEth is numbered vEth31.

lpanname/localpoolname

Specifies a local pool within an LPAN. More than one local pool can have the same name in one system as long as the locals pools are not in the same LPAN.

OPTIONS -a, --attachdevice {switchname | "(SCSI_ID)"} lpanname/pservername {vethn |"(X.0)"}

Creates a pServer device assignment. Depending on the arguments that you specify, use this option to attach vEths (-a switchname lpanname/pservername vethn) and disk or Fibre Channel tape devices (-a "(SCSI_ID)" lpanname/pservername "(X.0)").

When you first configure pServers in an LPAN, combine this option with the -A (autoenable) option to attach disks and the -G (mac–address) option to attach vSwitches for a pServer. By default, disk attachments are autoenabled.

After you create a device assignment using this option, you can modify it with the -m (modifydevice) -D (devicename) option combination.

PSERVER

PM5.2_BF 2-171

-A, --autoenable-device {yes|no}

Specifies whether a disk or Fibre Channel tape device is accessible to a pServer when it boots. By default, attaching any SCSI path device name configures the disk to be autoenabled. Use this option to specify disk access as not autoenabled or to reset access to a specific disk as autoenabled. Only one pServer can be autoenabled to a SCSI disk or Fibre Channel tape device ID at one time.

In the case of high–availability failover, SCSI path devices used for a high–availability application must be allocated to each of the failover pServers that you would like to use for the application. In addition, the SCSI path device(s) must be allocated to each pServer as not autoenabled, because the enabling occurs upon pServer boot and failover. Thus for a high–availability application, you must use the command pserver -a "(SCSI_ID)" -A no lpanname/pservername "(X.0)" to allocate the SCSI path device(s) that contain the high–availability application to the primary and failover pServers.

-b, --boot lpanname/pservername

Boots the specified pServer configuration after it is created and defined within an LPAN. Booting can cause resource conflicts when two or more pServers share disk resources. LPAN Administrators should contact the PAN Administrator if they experience difficulty obtaining their configuration resources.

The pServer boots using either an assigned boot image or, if no image is specified, the default pServer boot image (set by PAN Administrators using the pan --set-system-evbs-image evbs_image_name).

Administrators assign a boot image to a pServer using the -I (boot-image) option before they boot the pServer. They can also override the default pServer boot image one time, the next time, the pServer boots by combining this option with the -I (boot-image) option in the same line. This feature is used for booting the installation RAM disk for an operating system installation on a blade.


2-172 PM5.2_BF

For specific examples of using this “one-shot-boot” practice to install a pServer, see the appropriate pServer Guide or the Guest OS Installation for vBlades.

For specific examples of using this “one-shot-boot” practice to install a pServer, see the appropriate pServer Guide.

-B, --set-primary-pblade {platformname/pn[-n] |localpoolname |"none"}

Specifies whether the primary pServer pBlade for booting is a specific blade, vBlade, a blade from a local pool, or unspecified. To specify a pBlade or vBlade, that blade must be allocated to the same LPAN in which the pServer is located, and the pBlade cannot be assigned to any pool.

-B, --set-primary-pblade {platformname/pn |localpoolname |"none"}

Specifies whether the primary pServer pBlade for booting is a specific blade, a blade from a local pool, or unspecified. To specify a pBlade, that blade must be allocated to the same LPAN in which the pServer is located.

Specifying localpoolname configures the use of a pool of pBlades. PAN and LPAN Administrators use the pool command to set up global or local pools. See PAN Manager Administrator’s Guide for more information.

Note: For a pServer to have access to pBlades in a global pool, PAN Administrators first create the global pool using the pool command and then authorize an LPAN to access this pool using the lpan -P -G globalpoolname command. See the lpan command for option details.

Specifying “none” deletes the current pBlade allocation. Use this option to remove the current setting. If you want to change the assignment from a specific pBlade to a local pool, or from a local pool to a specific pBlade, you do not need to delete the original assignment: your new setting overwrites your old assignment.

PSERVER

PM5.2_BF 2-173

-c, --create lpanname/pservername

Creates a new pServer within an LPAN. For a complete set of instructions to create a pServer, see the appropriate pServer Guide for the software release you want to install on the pServer. You can get this document from the appropriate installation media, or from your authorized support website or vendor.

-d, --delete lpanname/pservername

Removes a specified pServer from an LPAN.

-D, --devicename {"(SCSI_ID)"|switchname}

Specifies either the SCSI path device or the name of a switch.

-e, --enabledevice DVDROMname

Allows cBlade DVD-ROM drive access for the specified pServer for a specified DVD-ROM if the pServer is in an access-enabled LPAN. By default, a newly created pServer derives its DVD-ROM access from the LPAN’s access state.

--eject-vcd lpanname/pservername

Specifies that PAN Manager should release the current media image from the virtual CD-ROM (VCD) on a specified pServer. If you force eject an image using the pserver --eject-vcd -f lpanname/pservername command, you must log on to a console on this pServer and clear the mount point the VCD had on the pServer. Failing to clear the mount point from the pServer may return I/O errors on your next attempt to access an image inserted into the pServer’s VCD.

-f, --force

Forces a pServer operation without a prompt. LPAN Administrators use this option with the -a (adddevice) or -d (delete) options to remove the verification prompt or with the -s (shutdown) or -x (reboot) options to shut down or reboot a pServer when a PAN Agent is unavailable. Forcing the --eject-vcd option ejects the media image even though it is mounted by means of the pServer. Forcing a VCD image ejection requires administrators to log on to a


2-174 PM5.2_BF

console on this pServer and clear the mount point the VCD had on the pServer.

-F, --set-failover-pblade {platformname/pn[-n] |localpoolname |none}

-F, --set-failover-pblade {platformname/pn |localpoolname |none}

Specifies whether a pServer uses a pool of pBlades or a specified pBlade as a backup if its primary pBlade becomes disabled. By default, there is no failover assignment. To specify a pBlade, that pBlade must be assigned to the same LPAN in which the pServer is located, and the pBlade cannot be assigned to any pool.

Specifying localpoolname enables the use of a pool of pBlades. PAN and LPAN Administrators use the pool command to set up global or local pools. See PAN Manager Administrator’s Guide for more information.

Note: If any pServer in an LPAN is to have failover access to a global pool, PAN Administrators first create the global pool using the pool command and then authorize an LPAN to access this pool for failover pBlades using the lpan -F -G globalpoolname command (see the lpan command for option details).

Specifying “none” deletes the current pBlade allocation. Use this option to remove the current setting. If you want to change the assignment from a specific pBlade to a local pool, or from a local pool to a specific pBlade, you do not need to delete the original assignment: your new setting overwrites your old assignment.

--fc --firmware-clear

Clears all firmware settings. This option tells PAN Manager to use the default pBlade configuration during the next pServer boot.

--fd --firmware-disable {ht|ni|ve|hp}

Disables one of the following firmware setting arguments on a specified pServer:

PSERVER

PM5.2_BF 2-175

• ht—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

• ni—Node interleaving (default is Off)—Interleaves a single page of memory from each processor. It is AMD-pBlade specific. 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

• ve—Virtualization extensions (default is On)—Used by hypervisors to enable guest operating systems to improve performance when using virtual device drivers to access the vBlade processing resource on a pBlade.

• hp—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 them. This feature improves the performance of most applications.

Not all blades support each of these features. Check the pBlade release notes to determine which hardware features your blade supports. Disabling a setting through PAN Manager that is not supported on a pBlade will have no effect on the pBlade the next time the pBlade boots.

--fe --firmware-enable {ht|ni|ve|hp}

Enables a firmware setting on a specified pServer. See the pserver --firmware-disable option for a list of supported option arguments. Not all blades support each of these features. Check the pBlade release notes to determine which hardware features your blade supports. Enabling a setting through PAN Manager that is not supported on a pBlade will have no effect on the pBlade the next time the pBlade boots.

-G, --mac-address mac_address

Specifies a MAC address for a virtual Ethernet connection (vEth).


2-176 PM5.2_BF

-i, --reset-default-image

Sets the specified pServer boot image to the default image for the PAN domain (set by the PAN Administrator using the PAN Manager pan -y command). LPAN Administrators can use the PAN Manager pan -i command to list all images and see which is set as the default image for pServers in the LPAN.

-I, --boot-image boot_image

Assigns a boot image to the specified pServer. Only a boot image registered to PAN Manager is a valid argument to this option. Use the pan -i command to list all registered images.

You can use this option either when you create a pServer, using the -c (create) command, or after you create it by specifying the pServer. In either case, the pServer will boot using this boot image assignment each time the pServer boots or reboots. Only boot images that are registered with PAN Manager (using the pan -I image_name command) can be used to boot a pServer.

Administrators can override this boot image assignment one time if they use this option in combination with the -b (boot) option. For instance, after you set the pServer boot image, you can override the default boot configuration one time, on the next boot, by using the pserver -b -I image_name command. This “one-shot boot” feature is used for booting the installation RAM disk for an operating system installation on a blade.

For specific examples of using this “one-shot-boot” practice to install a pServer, see the appropriate pServer Guide or the Guest OS Installation for vBlades.

For specific examples of using this “one-shot-boot” practice to install a pServer, see the appropriate pServer Guide.

After a PAN Administrator configures a default boot image for the PAN administrative domain, LPAN Administrators are not required to provide an argument to this option. Use the pan -i command to determine the default boot image for the LPAN. See the pan man

PSERVER

PM5.2_BF 2-177

page or PAN Manager Administrator’s Guide for more information about registering images with PAN Manager.

--insert-vcd {image_name} lpanname/pservername

Inserts a specified media image into the pServer virtual CD-ROM (VCD). This media image must be a registered media image available for pServers within the PAN.

To access the image, LPAN Administrators log onto the pServer and mount the image. The VCD is attached to the first SCSI device of the pServer.

The VCD status for a pServer is displayed in the pserver -l command output under the DVD-ROM column as (VCD-ROM).

-K, --boot-arguments “arg1,arg2,arg3...”

Specifies a comma-separated string to use as a boot argument for a pServer boot image. Administrators can pass arguments to a pServer during a boot (-b option) or a reboot (-x option).

PAN Manager supports two types of booting images: EVBS and TFTP boot images. The default pServer boot image is the system EVBS image (set by PAN Administrators using the pan --set-system-evbs-image evbs_image_name).

EVBS Image Arguments — Boot Device Order

With pServers configured to boot using EVBS, Administrators pass a boot device order to EVBS using the -K (--boot-arguments) option followed by “boot-order=dev1,dev2,dev3,dev4” where the devN argument specifies:

• vcd - Virtual CDROM.

• disk - A SAN disk. If there is more than one disk, the lowest number, or unit ID, is used.

• vethn - A vEth (0 through 30). (Use is limited to two vEths in a command.)


2-178 PM5.2_BF

By specifying a boot order when you boot the pServer, EVBS attempts to boot with the first selection and, if that device is not available, it attempts to boot with the second device, and so on. After you specify a boot order, that order persists the next time you boot this pServer.

For instance, pserver -K “boot-order=disk,veth2,vcd” lpanname/pservername specifies EVBS to boot the pServer from the disk, then veth2, then VCD on the next boot of the pServer.

You can specify up to four devices, delimited with either semi-colons (;) or commas (,).

If you do not specify a boot device order, EVBS presents a timed menu of all the devices that provide a bootable operating system image. You can select a device, or (after 10 seconds) allow EVBS to boot from the first suitable device in the default boot order.

EVBS boot image arguments are not supported for TFTP boot images.

TFTP Boot Image Arguments - Kernel Arguments

With pServers configured to boot using a registered TFTP boot image, you must provide kernel arguments that are supported exclusively for the TFTP boot image arguments. For an extensive list of valid arguments, see www.tldp.org at the Linux BootPrompt-HOWTO.

TFTP boot image arguments are not supported by EVBS.

For more information on using valid boot arguments in a variety of situations, see PAN Manager Administrator’s Guide or appropriate pServer Guide or section in Guest OS Installation for vBlades.

For more information on using valid boot arguments in a variety of situations, see PAN Manager Administrator’s Guide or appropriate pServer Guide.

PSERVER

PM5.2_BF 2-179

-l, --long

This option lists each pServer configured in an administrator’s LPAN domain and includes a display of description, properties, status information, pBlades, devices, kernel image arguments, hyper-threading status, and user-defined arguments for all pServers within the domain. Specifying a pServer argument following this option only lists these details for the specified pServer.

[??The following para. for DMC, BXPS, omits mention of hyperthreading status. Is HT (and other related settings) supported on these platforms?]

This option lists each pServer configured in an administrator’s LPAN domain and includes a display of description, properties, status information, pBlades, devices, kernel image arguments, and user-defined arguments for all pServers within the domain. Specifying a pServer argument following this option only lists these details for the specified pServer.

Without the -l option, the pserver command lists the following status information for all the pServer configurations within the user’s administrative domain: pServer name, status, agent, pBlade, hostname, up time.

LPAN Administrators can use the pserver -l command to display hypervisor details because PAN Manager treats each hypervisor as a special type of pServer. The output on a hypervisor includes categories similar to the long listing for a regular pServer, but with hypervisor configuration information.


Adds descriptive information to a pServer configuration, for human reference.

-m, --modifydevice {vethn|"(X.0)"} -D {switchname| "(SCSI_ID)"} lpanname/pservername

Modifies a pServer device assignment by specifying a switch or SCSI path device using the -D (devicename) option. You can also modify the current autoenabled state of the SCSI path device using


2-180 PM5.2_BF

the -A (autoenable) option and the optional state using the -o (optional) option. For vEths, you can modify the switch name or the MAC address for a vEth using the -G (devicemap-arg) option.

You can combine this option with the -o option to designate any or all of a pServer’s disks as required. A pServer with required disks will not boot, reboot, or recover until all of its required disks are available. If you specify a boot or reboot command for a pServer that has required disks and one or more disks are unavailable, the pServer will enter or remain in one of the following expected states:

• On a boot command, the pServer will remain shut down.

• On a reboot command from the PAN Manager, the pServer will stay booted.

• On a reboot command from the pServer, the pServer will shut down.

-M, --migrate platformname/pn-n lpanname/pservername

Indicates that you want to migrate the target pServer from its current vBlade to the specified vBlade. Migration to or from a pBlade is not supported.

Migration is impacted by a number of vBlade restrictions and has several minimum requirements. Before attempting pServer migrations be sure to review the restrictions and requirements presented in full detail in the PAN Manager Administrator’s Guide.


Specifies an optional shutdown message to be displayed on a Linux-based pServer to warn users that the pServer is to be shut down (shutdown messaging is not supported for pServers running the Windows operating system). This message is displayed in both telnet and console windows open to a pBlade. LPAN Administrators can use this option to provide details to LPAN Operators and LPAN Monitors of how long before a shutdown will occur. LPAN Administrators can only use this option with the -s (shutdown), or -x (reboot) options.

PSERVER

PM5.2_BF 2-181

-n, --rename new_name

Allows an LPAN Administrator to rename the specified pServer.

-o, --optional {yes|no}

Specifies whether an LPAN can boot if the specified pServer does not boot. For example, if you set this to "no" for a specified pServer, you prevent the LPAN of the pServer from booting if this pServer does not boot.

-O, --bootorder integer

Specifies the pServer’s place in the boot order of pServers within an LPAN.

-p, --map-disk-subpaths {yes|no}

Specifies whether the subpath mappings of disks of a pServer are visible to the pServer. By default, a pServer only recognizes the PAN Manager path device SCSI ID for any disk attached to the pServer (not tape devices). If you specify -p “yes” you enable the pServer to see the subpath mappings for its disks, and the pServer displays the subpaths for each of its disks, next to the path device SCSI ID.

-P, --rate-control {10Mb|100Mb|no}

Sets an upper limit rate, if any, in megabits per second, at which network traffic flows through a pServer interface. To use this option, create the interface with the -a (adddevice) option or modify the traffic rate limit with the -m (modifydevice) option.

NOTE: Rate limiting is not supported by the Windows(TM) operating system or any operating system running as a vBlade guest on a platform.

NOTE: Rate limiting is not supported by the Windows(TM) operating system.

The vEth interface(s) of a pServer can be assigned to more than one vSwitch. Therefore, an LPAN Administrator can map any vSwitch assigned to an LPAN to more than one vEth for each pServer in the


2-182 PM5.2_BF

LPAN. You need to have multiple vEths on a pServer connected to the same vSwitch if your applications are limited in the rate that they transmit data.

--pan-boot-image image_name

Specifies that you want PAN Manager to extract the boot image of a pServer, copy the image to the /images directory on the cBlades, and register the image as image_name in the PAN. This operation subsequently deploys this boot image for use by all other pServers in the PAN. After you use this option, you can see the image, image_name, displayed among all boot images registered in the PAN, in the output of the pan -i command.

-q, --quiet

Combined with the -w (wait) option, this option suppresses any information messages and the progress indicator during a boot or shutdown process. Use the -q and -w options only in combination with the -b (boot), -s (shutdown), or -x (reboot) options.

-r, --detachdevice lpanname/pservername {vethn|"(X.0)"}

Removes a specified vEth, disk, or Fibre Channel tape device currently attached to a pServer.

-R, --resume [platformname/pn-n] lpanname/pservername

Specifies that you want to resume the target pServer (from the corresponding suspend disk) on the appropriate vBlade. For details and cautions on using this option, see the PAN Manager Administrator’s Guide guide.

During this operation, PAN Manager marks the status of the pServer as Resuming. It then maps the corresponding suspend disk to the hypervisor and loads the state of the pServer from that disk to the chosen vBlade.

PSERVER

PM5.2_BF 2-183

When the operation is complete, the status of the pServer changes to Booted. The suspend disk is unmapped from the hypervisor and cleaned up. PAN Manager removes the suspend-related partitions from the disk and unmarks it as a suspend disk. However, PAN Manager does not scrub the disk’s contents.

-s, --shutdown lpanname/pservername

Halts the processing of a pServer, allowing the current pServer configuration to be resumed at a later time.

LPAN Administrators use this option with the -T (number_of_minutes), -M (message), -w (wait), or -x (reboot) options to create a conditional shutdown.

Note: The most current configuration of a pServer is rebooted, which means the exact pBlade a pServer reboots on depends upon its configuration. If a pServer is configured to run on a pBlade from a local pool, or if a pServer failed over to a pBlade pool, the pServer will reboot on the first available pBlade within that pool.

-S, --suspend "(SCSI_ID)" lpanname/pservername

Indicates that you want to suspend the target pServer (currently running on a vBlade) to the specified SAN disk.

Caution: This option’s underlying operation repartitions the specified SAN disk for use as a suspend disk. Do not select a disk that is currently used for another purpose or that contains data you need to keep. Only one suspend image (one pServer’s saved state) is supported at a time per disk.

During this operation, PAN Manager marks the status of the pServer as Suspending and the specified SAN disk as a suspend disk for that pServer. PAN Manager then repartitions the disk, maps it to the hypervisor, and writes the suspend image (the entire machine state of the pServer, including all RAM contents).

When the operation is complete, the status of the pServer changes to Suspended and the vBlade becomes available for allocation (according to your configuration). The suspend disk is unmapped


2-184 PM5.2_BF

from the hypervisor, but the disk’s data (the suspend image) is retained for a future resume.

While a pServer is suspended, the only runtime operations it supports are resume or shutdown. I/O and network configuration changes (such as attaching or detaching disks and eths) are not supported for a suspended pServer. If you boot an LPAN that includes a suspended pServer, that pServer remains suspended.

For additional details and cautions on using this option, see the PAN Manager Administrator’s Guide guide.

--set-keyboard-map keyboardmapname

Specifies the name of a keyboard map that associates a keyboard with keystrokes in the pServer console. PAN Manager supports various language keyboard maps. By default, PAN Manager uses the en-us keyboard map for the specified pServer. See PAN Manager Release Notes or contact Fujitsu Technology Solutions customer support or your authorized support vendor for a list of other supported keyboard maps.


Specifies an interval of time (in minutes) before a pServer shuts down or reboots. LPAN Administrators use this option after the -s (shutdown) option.

-u, --disabledevice DVDROMname

Removes cBlade DVD-ROM drive access for the specified pServer for a specified DVD-ROM. Use the lpan -u lpanname command to disable access for all pServers within the LPAN.

-w, --wait

Causes the pserver command to pause while a boot or shutdown process is underway and display a progress indicator. Use this option with the -b (boot), -s (shutdown), or -x (reboot) option in cases in which you would like to suspend command-line operations until the boot or shutdown is completed.

PSERVER

PM5.2_BF 2-185

-x, --reboot lpanname/pservername

Reboots a pServer. You can force a reboot using the -f (force) option.

EXAMPLES Specify a primary blade for a pServer in the development LPAN (on platform PlatformOne). This pBlade cannot be assigned to a pool by a PAN Administrator:

pserver -B PlatformOne/p3 development/webdev1

Configure three pServers in the production LPAN using a local pool of pBlades named webpool for the primary pBlade for each:

pserver -B "webpool" production/web1pserver -B "webpool" production/web2pserver -B "webpool" production/web3

Here there is no need to use the -F (failover) option, because in the case of pServer failover, the failed pServer gets an available pBlade from a local pool. If none is available, PAN Manager looks to see if the local pool is linked to a global pool. If it is linked and the LPAN has access to this linked global pool (the PAN Administrator uses the lpan -F -G globalpoolname command), the failed pServer gets an available pBlade from the linked global pool. If none are available, the pServer fails.

Utilize a local pool of pBlades named pool2 for pServer webdev1 in the development LPAN:

pserver -F pool2 development/webdev1

Failover works the same for this pServer. The difference between pServers web1 and webdev1 appears when failover occurs and the original pBlade is repaired. With web1 failover, a repaired pBlade is returned to the pool after the PAN Manager recognizes it, making it immediately available to all the pServers in the LPAN. With webdev1 failover, the pBlade remains inaccessible until you shut it down and reboot webdev1.


2-186 PM5.2_BF

Configure the pServer production/web5, to boot using the image named RHEL42_32bit_bootimage:

pserver -I RHEL42_32bit_bootimage production/web5

Configure the pServer production/web5, to boot using the default PAN domain boot image:

pserver -i production/web5

Boot the pServer production/web5 (which is set to use the default PAN domain boot image) one time using an installation RAM disk image, RHEL45_installimage:

pserver -b -I RHEL45_installimage production/web5

Specify a boot-order of devices (VCD first, then disk) for the pServer mylpan/win2003:

pserver -b -K "boot-order=vcd,disk" mylpan/win2003

Modify the boot-order of devices (veth1, then disk, then VCD) for the pServer mylpan/win2003:

pserver -b -K "boot-order=veth1,disk,vcd" mylpan/win2003

Attach a disk already configured with a root filesystem on it to the pServer web2 within the staging LPAN:

pserver -a "(9.0.0.10)" staging/web2 "(0.0)"

Attach a second disk to the same pServer:

pserver -a "(9.0.0.4)" staging/web2 "(1.0)"

Remove the device (unit name “(3.0)”) from the pServer web3 in the LPAN production:

pserver -r production/web3 "(3.0)"

PSERVER

PM5.2_BF 2-187

Create veth2 with switch2 without a verification prompt using a specific MAC assignment to a pServer within an LPAN:

pserver -a switch2 -f -G "02:00:03:00:01:00" production/web5 veth2

Remove veth2 from the pServer web5:

pserver -r production/web5 veth2

Assign the pServer webdev1 the second position within the development LPAN to boot:

pserver -O 2 development/webdev1

List the details for the hypervisor _hv-zeus-p7 in the doc LPAN:

pserver -l doc/_hv-zeus-p7

Assign vBlade p7-3 (on platform zeus) as a primary blade for the pServer named docps1 in the doc LPAN:

pserver -B zeus/p7-3 doc/docps1

Assign vBlade p5-2 (on platform zeus) as a failover blade for the pServer named docps1 in the doc LPAN:

pserver -F zeus/p5-2 doc/docps1

Migrate the pServer named docps3 (in the doc LPAN) from its current vBlade to vBlade p5-1 (on platform zeus):

pserver -M zeus/p5-1 doc/docps3

Modify the keyboard map to de (standard German keyboard) for the pServer named docps1 in the doc LPAN:

pserver --set-keyboard-map de doc/docps1


2-188 PM5.2_BF

Suspend the pServer named docps2 in the doc LPAN and save its state to the SAN disk 9.0.1.54:

pserver -S "(9.0.1.54)" doc/docps2

Resume the suspended pServer named docps5 in the doc LPAN on vBlade p7-3 (on platform zeus):

pserver -R zeus/p7-3 doc/docps5



SEE ALSO BFRAME

BLADE

CONSOLE

DISK

ETH

EVENTTYPE

FOP

LPAN

MON

PAN

POOL

SW


RETH

PM5.2_BF 2-189

RETH

NAME reth - creates, lists, or modifies a redundant Ethernet configuration

SYNOPSIS reth [-l] [rethname]

reth -d rethname

reth -f {"link"|"ping"} rethname

reth -c rethname -1 ethn@platformname/c1 -2 ethn@platformname/c2 [-F yes|no][-p {1|2|none}] [-P|-S]

reth [-F yes|no][-p {1|2|none}] rethname

DESCRIPTION The reth command creates, lists, or modifies a redundant Ethernet (rEth) configuration. A rEth is a pair of Ethernet interfaces, on each of the Ethernet Network Interface Cards (NICs) physically installed on the two cBlades, with the same external connectivity.

A rEth provides redundant load-balancing and failover capability for platform network connectivity. PAN Administrators use the reth command to configure the following rEth settings:

• A unique name that conforms to the PAN Manager naming conventions.

• An Ethernet interface on each cBlade network controller you pair to form the rEth. The two eths must be the same type and have identical VLAN ID settings. Fujitsu Technology Solutions strongly recommends using the same Eth port numbers to form the rEth pair.

• A MAC address. PAN Manager automatically assigns a MAC address, by default. 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.


2-190 PM5.2_BF

Caution: If the assigned MAC address conflicts with another MAC address on your network, you might experience network outages.

• A load-balancing policy—either “pair” (the default) or “static”.

• Flow control for external network multicast traffic flowing through the rEth.

PAN Manager Intelligent Network Failover

By default, PAN Manager uses “link status mode” to detect a network failover. PAN Administrators have the option to configure rEths to report Ethernet device failures based on ping results (ping failover detection mode, or just "ping mode"). The “ping mode” option uses ICMP (Internet Control Message Protocol) ECHO_REQUEST and ECHO_REPLY packets to determine the status of Ethernet devices, while “link status mode” checks for physical connectivity with the external Ethernet switch.

To choose ping mode instead of link status mode, PAN Administrators must configure several required parameters for each Ethernet device with the PAN Manager eth command, then use the -f (failover-mode) option to enable “ping mode” on the rEth. (“Ping mode” status parameters set with the eth command are retained but ignored if you do not enable “ping mode” with the reth -f command.) Use one of the following commands to choose how you want PAN Manager to manage network failover on each rEth:

• reth -f ping — Enables PAN Manager to determine Ethernet device failure using “ping mode” for each Eth device in the rEth.

• reth -f link — Enables PAN Manager to determine Ethernet device failure using “link status mode” for each Eth device in the rEth. This is the default behavior.

RETH

PM5.2_BF 2-191

PAN Manager enforces that both Ethernet devices in a rEth operate with the same failover detection mode. In other words, PAN Manager does not allow you to specify “ping mode” for one device and link status mode for the other device in the same rEth.




ethn@platformname/cn

Specifies a device on a cBlade Network Interface Card (NIC). PAN Manager naming conventions require you to use a forward slash (/) between the platform name and cBlade number. For example ethn on cBlade 2 on the platform named production, would be referred to as ethn@production/c2.

The PAN Manager NIC naming conventions vary depending upon your platform. Use the eth -l command to list the details for your particular platform configuration.

Important: On a BladeFrame BF400 S2, a valid rEth consists of paired devices Eth1, Eth2, Eth3, Eth4, Eth15, Eth16, Eth17, and Eth18 on different cBlades; on a BladeFrame BF200, a valid rEth consists of paired devices Eth1 and Eth2 on different cBlades.


Important: A valid rEth consists of paired devices Eth6 or Eth7 on each cBlade.

OPTIONS -1, --interface1 ethn@platformname/c1

Specifies the first cBlade or NIC of a rEth.


2-192 PM5.2_BF

-2, --interface2 ethn@platformname/c1

Specifies the second cBlade NIC of a rEth.

-c, --create rethname

Creates a redundant Ethernet configuration. Use this option along with the -1 (EthernetNIC1) and -2 (EthernetNIC2) options to specify the NIC on each cBlade. The two Eths must be of the same type. Fujitsu Technology Solutions strongly recommends using the same Eth port numbers to form the rEth pair. Each pair of cBlade NICs can only be used by one rEth on a platform at a time. For example, two rEths on one platform require two separate, redundant cBlade NICs.

See PAN Manager Administrator’s Guide for information about setting the Maximum Transmission Unit (MTU) value for a rEth.

Caution: After you create a rEth, you can only modify a -F (flow control) or -p (primary-eth) setting. To make other modifications to a rEth after it is created, delete it using the -d (delete) option and re-create it using the -c (create) option while making the appropriate modifications.

-d, --delete rethname

Removes a specified rEth from a platform. All vSwitch uplinks specifying a rEth must be cleared using the sw -r switchname command before a rEth can be deleted.

-f, --failover-mode {"link"|"ping"}

Specify the mode PAN Manager uses to determine Ethernet device failure. By default, PAN Manager uses “link status mode” (failures are determined solely by the link status of the Ethernet device).

To enable “ping mode” (Ethernet device failures are determined by ping results), specify “ping.” PAN Manager requires you to configure both Ethernet devices that comprise the rEth to have “ping mode” failure detection set (use the eth -R command to set a remote IP Address to ping) before you can enable “ping mode” on the rEth.

RETH

PM5.2_BF 2-193

You disable “ping mode” by issuing the “link” option.

-F, --flow-control {yes|no}

Activates or deactivates flow control for all external unicast and broadcast network traffic flowing through a specified rEth and internal broadcast traffic flowing between pServers.

NOTE: Flow control is not supported for vBlades or any pServers running the Microsoft Windows(TM) operating system.

NOTE: Flow control is not supported for any pServers running the Microsoft Windows(TM) operating system.

PAN Administrators activate flow control on a specific rEth (-F “yes”) to ensure no network packet loss between a pServer and its destination on an external network using this rEth. Activating flow control for a rEth affects only broadcast traffic between pServers, and unicast and broadcast traffic between pServers and an external network.

Activating flow control on a specific rEth is different from activating global flow control in a PAN. The latter enables flow control only for internal broadcast traffic between pServers. To activate global flow control in a PAN, PAN Administrators must use the pan -W yes command. Activating PAN-wide global flow control does not affect unicast traffic between pServers, or pServers and the external network.

By default, flow control for a rEth is not activated. Activating flow control does not affect existing load-balancing configurations.

-l, --long

Lists information about the current rEth configuration(s) for a platform.

-m, --mtu-size

Sets the frame MTU size to a value other than the default of 1500, to support larger “jumbo” frames for greater throughput and higher


2-194 PM5.2_BF

network utilization. You can only use this option for rEths that use e1000 NIC devices.

-p, primary-eth {"1"|"2"|"none"}

Specifies which, if any, cBlade NIC is used as the rEth’s primary interface. In addition, this option is used to disable and reinstate automatic rEth failback on an as-needed basis.

This option is only available for a “pair” rEth. In general, you can achieve more uniform distribution of network traffic between the NICs on both cBlades using two “pair” rEths each specifying a primary NIC on a different cBlade.

Specifying "none" for a rEth with a primary interface configuration disables automatic rEth failback. After automatic rEth failback is disabled, it can be reinstated using the eth -p n rethname command where n indicates the number of the Ethernet interface (1 or 2) that had been the primary (active) eth. If nothing is specified, the default is 1.

-P, --pair

Sets the load-balancing option of the specified rEth to “pair” mode. This option is the default.

In “pair” mode, packets are transmitted on the same Ethernet interface that is receiving packets. For “pair” mode rEths, you can specify one eth as the primary (active) interface and the other as the secondary (standby) interface.

If the primary (active) Ethernet interface of a “paired” rEth cannot transmit or receive packets, such as in a cBlade failure or a failed uplink, rEth failover occurs. The failover policy associated for “paired” rEths is to fail over all rEth send and receive responsibility to the other cBlade. Failover allows processing to continue on the secondary (standby) Ethernet interface. If the uplink is reestablished on the primary Ethernet interface that was down, the rEth configuration can automatically failback to the original configuration.

RETH

PM5.2_BF 2-195

When the failed cBlade returns, it resumes its original send and receive responsibilities.

When automatic rEth failback occurs, there can be an interruption of service if there is an interval between the time the external link is reestablished and the time that the external network is fully configured. To avoid this kind of interruption of service, you can disable automatic rEth failback using the reth -p none command.

-S, static

Sets the load-balancing option of the specified rEth to “static” mode. The failover policy associated with this configuration is to fail over all traffic to the remaining cBlade. When the failed cBlade returns, the original “static” assignment resumes.

In “static” mode, incoming and outgoing pBlade traffic is statically divided between the two network cBlades and is assigned to a cBlade NIC based on the MAC address of the pBlade. As long as pBlade MAC addresses end with an even split of even and odd numbers, both cBlades balance the traffic volume. This option is most useful when you know that some pBlades within the platform will see a higher volume of network traffic.

This load-balancing option can be undermined if pBlade MAC assignments are overweighted with odd or even numbers. If administrators do not auto-assign these addresses, it is possible to send all static rEth traffic through one cBlade which will affect performance.

EXAMPLES List information about the current rEth configuration(s) for a platform.

reth -l

View the status of redundant Ethernet device reth2.

reth -l reth2


2-196 PM5.2_BF

Create a “paired” rEth Reth1 (“paired” is the default load-balancing option) on PlatformOne:

reth -c Reth1 -1 eth1@PlatformOne/c1 -2 eth1@PlatformOne/c2

Specify eth1@PlatformOne/c2 as the primary Ethernet interface on this Reth1, which enables automatic rEth failback on the rEth as well:

reth -p 2 Reth1

Reset Reth1 to have no primary interface setting, which disables automatic rEth failback on the rEth as well:

reth -p none Reth1

Create a “static” rEth statReth on PlatformOne:

reth -c statReth -1 eth1@PlatformOne/c1 -2 eth1@PlatformOne/c2 -S

Create a “paired” rEth Reth1 (“paired” is the default load-balancing option) on PlatformOne:

reth -c Reth1 -1 eth7@PlatformOne/c1 -2 eth6@PlatformOne/c2

Specify eth7@PlatformOne/c2 as the primary Ethernet interface on this Reth1, which enables automatic rEth failback on the rEth as well:

reth -p 2 Reth1

Reset Reth1 to have no primary interface setting, which disables automatic rEth failback on the rEth as well:

reth -p none Reth1

RETH

PM5.2_BF 2-197

Create a “static” rEth statReth on PlatformOne:

reth -c statReth -1 eth7@PlatformOne/c1 -2 eth6@PlatformOne/c2 -S

Enable “ping” mode failover detection on Reth1, which requires each Eth device in Reth1 to be configured for ping failover detection mode:

reth -f ping Reth1

Modify Reth1 to use “link” mode failover detection

Activate flow control on Reth1 to ensure no packet-loss for externally-bound unicast traffic going through this rEth:

reth -F yes Reth1



SEE ALSO BFRAME

BLADE

ETH

IP

LPAN

SW



2-198 PM5.2_BF

ROLE

NAME role - Lists the roles within the PAN or an LPAN administrative domain.

SYNOPSIS role [-l] [rolename]

role [-l] [-P lpanname]

role [-l] -U rolename

DESCRIPTION The role command lists the roles within a domain for which the user has administrative privileges. PAN Administrators use the role command to list the exact name of roles they use as arguments for the user command when assigning roles to PAN Manager users.

To see all the roles within the PAN domain, use the role command without options or arguments.

OPTIONS -l, --long

Adds a description for each role within the PAN domain.

-P, --lpanname lpanname

Lists all roles associated with the specified LPAN.

-U, --users rolename

Lists the PAN Manager users for a specified role.

EXAMPLES Lists all the roles and a description of each role for the PAN domain:

role -l

ROLE

PM5.2_BF 2-199

List the users with the role of PAN administrator:

role -U PAN-Administrator

List the users with the Operator role for the development LPAN:

role -U development-LPAN-Operator


SEE ALSO ACCOUNT

UMON



2-200 PM5.2_BF

SAN

NAME san - lists configuration information and controls operations on SCSI devices that are physically connected to a PAN.

SYNOPSIS san [-l] [-A |-C |-U |"(SCSI_ID)"]

san -s

san [-i |-m]

san [-a |-d |-p] "(SCSI_ID)"

san [-X |-P] [-f]

san -n "(new_SCSI_ID)" {"(SCSI_ID)" | "UID"}

DESCRIPTION The san command allows you to manage disk and tape devices in a Storage Area Network (SAN). After a SAN disk or Fibre Channel tape device is physically connected and configured to a platform, PAN Administrators use the san command to:

• Display information about these SCSI devices.

• Manually scan SCSI resources to discover newly added SCSI devices.

• Configure PAN Manager to manually or automatically import newly discovered SCSI devices into a PAN.

• Remove a specified SCSI device or all SCSI devices from a PAN. This is commonly referred to as disk purging.

• Rename a SAN device (disk or tape) to have a specific SCSI ID (useful if you want the PAN Manager display names (SCSI IDs) for SAN devices to remain the same, despite changes to the PAN’s overall SAN configuration).

See the disk or tape command for operations that are limited to a disk- or tape-based SCSI device.

SAN

PM5.2_BF 2-201

The discovery process for SCSI path device resources takes place automatically during a cBlade boot.

We recommend that you add SCSI device resources during off-hours, or other low traffic times, to minimize the I/O impact that the discovery process might have on the storage network.

See PAN Manager SAN Integration Guide for details.

You should scan for new SCSI devices (using the san -s option) before initiating a SCSI device purge to ensure that PAN Manager is aware of any recent device subpath changes.




"(SCSI_ID)"








2-202 PM5.2_BF

OPTIONS -a, --add-san-device "(SCSI_ID)"

Allows you to manually add a specified path device SCSI ID to the PAN after PAN Manager discovers it. PAN Administrators only use this option to manually import disks into the PAN after they disable auto-import mode using the -m (manual-pan-import) option.

-A, --all-san-devices

Displays all PAN and non-PAN discovered path device SCSI IDs.

-C, --configured-san-devices

Lists all path device SCSI IDs that are currently allocated to LPANs, assigned pServers, or reserved to archive DR resources. This listing displays each allocated device’s storage capacity, type of storage array, and storage array serial number.

-d, --remove-san-device "(SCSI_ID)"

Removes a path device SCSI ID from the PAN. This command option fails if the path device SCSI ID is allocated to an LPAN, if PAN Manager is in auto-import mode, or if the disk is reserved to archive DR resources. PAN Administrators can remove and purge a path device SCSI ID and UID from the cBlade kernel and PAN Manager by adding the -p (purge-san-device) option (san -dp "(SCSI_ID)").


-f, --force

Forces a san command operation without a prompt.

-i, --auto-pan-import

Enables PAN Manager auto-import mode and disables manual device-import mode. With the auto-import mode enabled, all devices discovered outside of the PAN are brought into the PAN when either a scan (using the -s (scan) option) or PAN Manager startup takes place. If auto-import is enabled, you cannot delete a path device. Auto-import mode is enabled by default.

SAN

PM5.2_BF 2-203

-l, --long

Lists UID, I/O path details, and partition information by SCSI device in addition to storage capacity, type of storage array, storage array serial number, and LPAN assignment. This option displays a partition table for each path device in a data format you can use as the basis for a new partition table file. To do so, copy this data into any text editor and edit appropriately.

Important: Under some circumstances, the names of some devices can have an unexpected form, or can change after a cBlade reboots. This can occur if:

• You change the SAN configuration (including adding or removing one or more disks)

• You change the cBlade kernel’s SCSI settings

• You change path groups on existing devices, then reboot (which may change the UIDs of existing devices)

These changes can impact device names in two ways:

• A device’s path device name can change from 9.n.n.n to 9.n.128.n

• A device’s PAN Manager device name can change from 9.n.n.n to 10.n.n.n.

Although this condition is harmless, it may cause confusion. To help prevent the situation in which a single device is identified by multiple path device names, be sure to check to see that any disk or tape SCSI ID target you expose is visible on all paths as the same SCSI ID number when you initially configure the SAN disk or Fibre Channel tape device. See PAN Manager SAN Integration Guide for details.

-m, --manual-pan-import

Enables manual device import mode and disables auto-import mode. In manual device-import mode, newly discovered SCSI devices using the -s (scan) option remain outside a PAN until a PAN Administrator manually adds each device using the -a


2-204 PM5.2_BF

(add-san-device) option. PAN Administrators must enable this mode to allow purging of one or more path device SCSI IDs and UIDs from PAN Manager using the -p (purge-san-device) or -P (purge-all-san-devices) options. By default this option is disabled.

-n "(new_SCSI_ID)" {"(SCSI_ID)" | "UID"}

Renames the current SCSI ID of a SAN device to a different SCSI ID. To identify which SAN device you are renaming, you can specify either its current SCSI ID or its unique identifier (UID).

-p, --purge-san-device "(SCSI_ID)"

Removes a specified path device SCSI ID from PAN Manager memory. You can combine this option with the -d (remove-san-device) to purge a path device from PAN Manager memory or you can delete the specific path device(s) first and then use this option later.


IMPORTANT: To permanently remove any path device SCSI ID from PAN Manager memory, remove access to the devices in the SAN before you reboot the cBlades.

-P, --purge-all-san-devices

Removes all path device SCSI IDs from PAN Manager memory. You can combine this option with the -X (remove-all-san-devices) to purge all path device SCSI IDs from PAN Manager memory or you can delete all path device SCSI IDs first and then use this option later.


SAN

PM5.2_BF 2-205

-s, --scan

Instructs PAN Manager to scan its resources for SCSI devices added after the cBlades have booted and PAN Manager is running. This option returns a list of changes found during the scan, along with warnings, if any. When the prompt returns, use the -l (long) option to see newly added disks.

-U, --unconfigured-san-devices

Displays information only about SCSI devices in a PAN that are not currently assigned to an LPAN.

-X, --remove-all-san-devices

Removes all path device SCSI IDs for devices that are not currently allocated to an LPAN or pServer. If the force option (-f) is not used, PAN Manager prompts the user for a confirmation. PAN Administrators can purge all path device SCSI IDs and UIDs from the cBlade kernel and PAN Manager by adding the -P (purge-all-san-device) option (san -XP "(SCSI_ID)").

Before you purge all devices, you should manually scan (using the -s option) to ensure that PAN Manager is aware of all sub paths to the path device before the purge.

EXAMPLES Search for newly added SAN storage devices:

san -s

List detailed information about all SCSI devices:

san -l

List detailed information about SCSI device (9.0.1.76):

san -l "(9.0.1.76)"

List brief information about all unconfigured SCSI devices:

san -U


2-206 PM5.2_BF

Remove all disks that are not currently allocated for another use; do not prompt for confirmation:

san -X -f

Remove SCSI device (9.0.1.76) (it must not be currently allocated for another use):

san -d "(9.0.1.76)"

Remove SCSI device (9.0.1.76) (it must not be currently allocated for another use) and purge all references to its UID from PAN Manager memory:

Remove SCSI device (9.0.1.76) (it must not be currently allocated for another use) and purge all references to its UID from PAN Manager memory:

san -dp "(9.0.1.76)"

Rename the device 9.0.1.25 to 12.3.0.58:

# san -n “(12.3.0.58)” “(9.0.1.25)”

Specify a new SCSI ID (9.0.3.78) for a device whose UID is EMC-SYMMETRIX-WWN-6006048000038722003753594d323741:

# san -n “(9.0.3.78)” “EMC-SYMMETRIX-WWN-6006048000038722003753594d323741”



SEE ALSO DISK

LPAN

PSERVER

SAN

PM5.2_BF 2-207

TAPE



2-208 PM5.2_BF

SMTPSVR

NAME smtpsvr - lists and modifies the PAN administrative domain’s configuration for the Simple Mail Transport Protocol (SMTP) server at your site.

SYNOPSIS smtpsvr [-l] [domainname]

smtpsvr [-i ipaddress] [-p port] [-U username] [-P password] [-s send-address] [domainname]

DESCRIPTION The smtpsvr command lists and modifies the configuration to allow a PAN to communicate with the Simple Mail Transport Protocol (SMTP) server at your site. PAN Administrators use the smtpsvr command to allow a PAN to send email messages from their SMTP server as well as set up the sender address of the PAN Manager mail gateway. Though it is possible to have more than one PAN Administrator enabled to configure a PAN’s SMTP server, PAN Administrators can only configure one mail gateway for a platform.

Only PAN Administrators can use the smtpsvr command.

OPTIONS -i, --ipaddress ipaddress

Modifies the IP address to match your SMTP server. To clear the setting, PAN Administrators must leave an empty string (““) for this argument. If this configuration is empty, PAN Manager cannot send any email notifications.

-l, --list

Displays the current configuration for your SMTP server and the PAN Manager mail gateway.

-p, --port port_number

Modifies the port number to match your SMTP server.

SMTPSVR

PM5.2_BF 2-209

-P, --password "text"

Modifies the password associated with the account designated with the -U (user) option.

-s, --send-address emailaddress

Modifies the sender of the PAN Manager mail gateway. There can only be one ‘send’ address for a platform. This email address must match an existing account on your SMTP server.

-U, --user username

Modifies the Linux account name of the PAN Administrator(s) you designate as the sender. Only accounts that have PAN Administrator roles are valid.

EXAMPLES Configure PAN Manager not to send emails for the LPAN domain development:

smtpsvr -i "" PlatformOne/p3 development



SEE ALSO PAN



2-210 PM5.2_BF

SNMP

NAME snmp - lists or modifies the configuration for a PAN Manager Simple Network Management Protocol (SNMP) agent.

SYNOPSIS snmp -l [-v {1|2} [-t trapname] [-e eventtype]

snmp [-I ipaddress] [-P port] [-R readstring] [-S {monitor|control|disable}] [-W writestring][-T sysContact] [-N sysLocation]{-G |-L lpanname}

DESCRIPTION The snmp command lists or modifies SNMP agent settings for a specified administrative domain — global (the PAN domain) or LPAN domain. PAN Manager SNMP agents support SNMP versions 1 and 2c. PAN Manager provides an SNMP agent for each administrative domain. You are required to have the PAN or LPAN Administrator role to use the snmp command, depending on the SNMP agent’s domain.

For example, if there is one platform in a PAN and it has four LPANs, this system would have a total of five SNMP agents:

• One PAN domain agent

• Four LPAN agents

SNMP agents are disabled by default in PAN Manager. To enable SNMP, administrators use the snmp command to configure each agent. It is recommended that you use non-default values when enabling your community strings. All SNMP agents reside on the master cBlade, each one with a unique combination of IP address and UDP port used to communicate with a set of SNMP managers. This pair must not be bound to a specific cBlade. See the PAN Manager extnet command or PAN Manager Administrator’s Guide for more information about SNMP agents.

Use the snmp command to set attributes of each agent including:

SNMP

PM5.2_BF 2-211

• IP address — the IP address to which the agent binds.

• UDP Port — the User Datagram Protocol (UDP) port to which the agent binds.

• Community Strings — the accepted authorization string required from an SNMP manager to send valid read or read/write requests to an agent. It is recommended that you enter a non-default value for read-only and read/write community strings.

• Monitor and Control — the level of authority an agent has. SNMP agent action is an escalating scale ranging from disable, to monitor only, to monitor and control. You enable a level using the -S option.

PAN Manager Administrators also need to authorize external SNMP managers, which may send requests to or receive traps from a specified SNMP agent. You use the snmpmgr command for these configuration options. Each SNMP agent can respond to more than one SNMP manager.

See PAN Manager Administrator’s Guide for more information on configuring events, triggers, and SNMP.

OPTIONS -e, --event-type eventtype

Used with the -l (list trap) option, displays a trap name associated with a specified event type.

-G, --global-pan-domain

Specifies a global (PAN) agent.

-I, --ipaddress ipaddress

Specifies the IP address of the specified SNMP agent.

-l, --list-traps

Lists all traps in the administrative domain for which you have PAN Manager Administrator privileges.


2-212 PM5.2_BF

-L, --lpan lpanname

Specifies an LPAN agent.

-N, --location System_Location_String

Specifies the physical location of the platform running the managed node. See PAN Manager Administrator’s Guide for details about configuring SNMP traps and managers.


Specifies the UDP port number of the specified SNMP agent. This option takes a valid port number as an argument. While the default SNMP port is 161, you can choose a non-default setting, providing it is unused.

-R, --read-community "text"

Specifies a read-only community string accepted by the SNMP agent. A non-default setting for read-only community strings is recommended.

-S, --agent-scope {monitor|control|disable}

Specifies the SNMP agent functions and provides a way to enable or disable the SNMP monitor and control functions.

-t, --trap-name

Used with the -l (list trap) option, displays an event type associated with a specified trap.

-T, --contact System_Contact_String

Specifies the contact information for the System Contact. See PAN Manager Administrator’s Guide for details about configuring SNMP traps and managers.

-v, --snmp-version {1|2}

Used with the -l (list trap) option, displays all traps associated with either SNMP Version 1 or 2c.

SNMP

PM5.2_BF 2-213

-W, --write-community "text"

Specifies a read-write community string accepted by the SNMP agent. A non-default setting for read/write community strings is recommended.

EXAMPLES Enable an SNMP agent for the staging LPAN, specifying port 161 on IP address 12.24.48.96 with a read community string cgable24, a read/write community string cgable45, and with monitor and control enabled:

snmp -I 12.24.48.96 -P 161 -R cgable24 -W cgable45 -S control -L staging

Modify this agent to have a new read/write community string cgable28

snmp -W cgable28



SEE ALSO EVENTTYPE

EXTNET

SNMPMGR

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_snmpmgr).


2-214 PM5.2_BF

SNMPMGR

NAME snmpmgr - lists or modifies the set of authorized Simple Network Management Protocol (SNMP) managers with which a PAN Manager SNMP agent interacts.

SYNOPSIS snmpmgr -I ipaddress [-P port -C trapstring] [-M manageripmask |-m] [-V {1|2}]{-G |-L lpanname}

snmpmgr -r ipaddress {-G |-L lpanname}

snmpmgr {-G |-L lpanname}

DESCRIPTION The snmpmgr command lists or modifies the set of authorized SNMP managers with which each SNMP agent communicates. To list all the SNMP managers to which an agent responds, use the IP address as a command argument and identify the agent by its administrative domain (-G for global PAN domain or -L for LPAN domain). Using the snmpmgr command, you can specify the IP address of an SNMP manager with which an agent interacts, or specify a UDP trap port, a trap community string, and IP address of an SNMP manager to which you want an SNMP agent to send traps. PAN Manager software provides an SNMP agent for each administrative domain of the PAN structure - global (the PAN domain) or LPAN. You are required to have the PAN Administrator or LPAN Administrator role to use the snmpmgr command, depending on the area of responsibility the SNMP agent is assigned.

The snmpmgr command allows you to specify the following attributes:

• IP addresses — the IP address(es) and the network mask(s) of the SNMP manager(s) with which an agent interacts.

• UDP Trap Port — the UDP port assignment of the SNMP manager with which an agent interacts.

SNMPMGR

PM5.2_BF 2-215

• Trap community string — the community string sent in each trap to the specified SNMP manager.

Administrators use the snmpmgr command to establish the set of SNMP managers, which may request and/or receive traps from a specified SNMP agent. Use the snmp command to set up the attributes for each SNMP agent.

OPTIONS -C, --trap-community "text"

Specifies a community string an agent uses to send traps to an SNMP manager.

-G, --global-pan-domain

Specifies the agent that responds to the global (PAN domain) manager you are configuring.

-I, --ipaddress ipaddress

Specifies the IP address of an SNMP manager with which an agent interacts. Use this option alone to print out the specified SNMP manager setting or with the -P (port) and -C (trap–community) options to assign the port setting and trap community string for an SNMP manager with which a specified agent interacts.

-L, --lpan lpanname

Specifies the agent that responds to the LPAN domain manager you are configuring.

-M, --ip-mask manageripmask

Specifies the IP address for a network mask. By default, the network mask is set to 255.255.255.255. See PAN Manager Administrator’s Guide for details in configuring SNMP managers and trap destinations.

-m, --reset-mask

Resets the manager network mask to 255.255.255.255.


2-216 PM5.2_BF


Specifies the UDP port number to which a specified SNMP agent sends traps. For the agent to send traps to this manager, the port number must be greater than zero. To prevent an agent from sending traps to this manager, assign the UDP port to zero.

-r, --remove-ipaddress ipaddress

Removes an SNMP manager from the set of managers with which an SNMP agent interacts.

-V, --version {1|2}

Specifies an administrator’s trap version choice between SNMPv1 or SNMPv2c. See PAN Manager Administrator’s Guide for details about configuring the SNMP trap version.

EXAMPLES Create a staging LPAN SNMP manager with the IP address 12.24.48.95 with which the staging SNMP agent interacts:

snmpmgr -I 12.24.48.95 staging

Create the staging LPAN SNMP manager with the IP address 12.24.48.95. The staging SNMP agent sends traps to this SNMP manager using the community string cgable to port 1090:

snmpmgr -I 12.24.48.95 -P 1090 -C cgable staging

Remove the staging SNMP manager:

snmpmgr -r 12.24.48.95 staging



SEE ALSO EVENTTYPE

SNMPMGR

PM5.2_BF 2-217

SNMP

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_snmp).


2-218 PM5.2_BF

SW

NAME sw - creates, modifies, or lists the configuration for a Virtual Switch (vSwitch).

SYNOPSIS sw -n newvswitchname oldvswitchname

sw [-l] [vswitchname]

sw [-c |-d |-r] vswitchname

sw [-c] [-U -E {rethname} [-V VLAN_ID | -N VLAN_name]] vswitchname

sw -m [on | off] vswitchname

DESCRIPTION The sw command creates, modifies, or lists the configuration for a virtual switch (vSwitch). vSwitches establish connectivity among pServers, or between pServers and external networks. PAN Administrators use the sw command to create enough vSwitches to accommodate requests from the LPAN Administrators for vEths to provide one of two types of connectivity:

• Internal Connectivity—LPAN Administrators can create vEths for pServer-to-pServer communication using any vSwitch they have permission to access.

If two pServers connect to the same vSwitch, the two pServers can communicate.

• External Connectivity—PAN architecture only supports external network communication through Redundant Ethernet (rEth) configurations. PAN Administrators can only create vSwitches for external connectivity using an uplink configured with the reth command. PAN Administrators create vSwitches for external connectivity with the sw command by specifying the rEth and optional VLAN ID the vSwitch uses.

SW

PM5.2_BF 2-219

External traffic through an uplink can be non-VLAN tagged over any rEth, or VLAN-tagged over the Gigabit rEths. Only uplinked vSwitches on a rEth can have a VLAN setting.




vswitch_name

Specifies a switch name. You cannot name a vSwitch beginning with the three characters eth, because these characters are reserved for switch-related devices (such as names for LPANs or pServers).

rethname

Specifies a rEth created with the reth command.

VLAN_ID

Specifies a VLAN ID configured using the eth command.

OPTIONS -c, --create vswitchname

Creates a vSwitch. You cannot create a vSwitch and an uplink on the same command line.

-d, --delete vswitchname

Removes the specified vSwitch configuration. This option can be combined with the -f (force) option.

-E, --reth-device {rethname}

Specifies a rEth for a vSwitch’s external network connectivity.


2-220 PM5.2_BF

Note: You are required to configure a rEth using the reth command before you can associate a vSwitch with it. You must clear this uplink using the -r (clear-uplink) option before you can delete this rEth with the reth command.

-l, --long

Lists the current vSwitches within a platform and includes a listing for each vSwitch’s external connectivity and uplink settings.

-m, --multicast-snoop [on | off] vswitchname

Enables (on) or disables (off) IGMP multicast snooping on the vSwitch. IGMP snooping is on by default.

-n, --rename newvswitchname oldvswitchname

Renames the specified existing vSwitch.

-N, --vlan-name VLAN_name

Specifies an optional VLAN name assigned to a specified Ethernet card for the -U (set-uplink) option.

-r, --clear-uplink vswitchname

Clears the current assignment of a specified vSwitch configuration. Clearing a vSwitch uplink makes it unusable as a conduit to an external network. You must use this option when you want to remove or modify a rEth.

-U, --set-uplink vswitchname

Associates a vSwitch with a specified rEth and its uplink information. Use the reth -l rethname command to list the available uplinks configured for your rEth. You cannot create a vSwitch and add an uplink at the same time.

Caution: You must clear this uplink with the -r (clear-uplink) option before you can remove or modify this rEth at a later time with the reth command.

SW

PM5.2_BF 2-221

-V, --vlan-id VLAN_ID

Specifies an optional VLAN ID assigned for a rEth. Use this option with the -U (set-uplink) option. To see the list of valid (if any) VLAN IDs for a rEth, use the reth -l rethname command for the Gigabit cBlade NICs that comprise the rEth.

Note: You can only assign one VLAN ID to a vSwitch. For example, if you have five VLAN IDs configured for a rEth that LPAN Administrators will use for external network connectivity, you must create five vSwitches.

EXAMPLES Create a vSwitch, ext_sw:

sw -c ext_sw

Delete the vSwitch ext_sw without displaying a verification prompt:

sw -d -f ext_sw



SEE ALSO ETH

IP

PSERVER

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_eth).


2-222 PM5.2_BF

TAPE

NAME tape - lists tape devices physically connected to a PAN.

SYNOPSIS tape [-l] [-A |-C |-U |"(SCSI_ID)"]

tape -L "text" "(SCSI_ID)"

DESCRIPTION The tape command displays information about tape devices physically connected to a platform.

Issuing the tape command with no options displays a brief listing of all tape devices.

You can produce brief or detailed listings for a specific tape device, for all tape devices, or for just those that are configured or unconfigured for an LPAN. You can also specify a descriptive text string that will be displayed as part of the long information listing.



Addition naming conventions for this command include:

"(SCSI_ID)"



TAPE

PM5.2_BF 2-223





OPTIONS -A, --all-tapes

Displays I/O path information about all tape devices attached to the PAN.

-C, --configured-tapes

Displays I/O path information about only configured tape devices attached to the PAN.

-l, --long

Displays a detailed listing of the specified tape device(s).


Sets a text string that will be displayed in the Description field of long listings for a specified tape device.

-U, --unconfigured-tapes

Displays I/O path information about only unconfigured tape devices attached to the PAN.

EXAMPLES Set the descriptive text string "StorageTek 9840B" for the tape device at “(9.0.0.170)”:

tape -L "StorageTek 9840B" "(9.0.0.170)"

Produce a detailed listing of the tape device at “(9.0.0.170)”:

tape -l "(9.0.0.170)"


2-224 PM5.2_BF

Produce a brief listing of just those tape devices that are assigned to any LPAN:

tape -C



SEE ALSO LPAN

PSERVER

SAN


UMON

PM5.2_BF 2-225

UMON

NAME umon - creates, modifies, or lists user-defined monitor resources for an LPAN.

SYNOPSIS umon [-c] -E exec [-L description] [-I interval][-D delay] [-U unit] [-a eventname -C {"<"|">"|"=="|"<="|">="|"!="} -T value -S {1-6}] lpanname/monitorname

umon -m eventname [-N newname] [-C {"<"|">"|"=="|"<="|">="|"!="}] [-T value][-S {1-6}] lpanname/monitorname

umon -n newname lpanname/monitorname

umon -r eventname lpanname/monitorname

umon -d lpanname/monitorname

umon [-l] lpanname[/monitorname]

DESCRIPTION The umon command provides the ability to create a set of health, status, or statistical monitors defined by the user to monitor the activity in an LPAN. The events tracked by these monitors can help monitor and subsequently control PAN Manager behavior. Output can be used to monitor applications and, if necessary, trigger application fail-over.

User-defined monitor resources let a user create a set of health, status, or statistical monitors and use the monitor’s events to control PAN Manager behavior. Administrators configure resources for a specific monitor by specifying the following attributes:

• Monitor name

• Monitor description

• Names of the health, status, or statistical events connected with this user-defined monitor

• Value used for the comparison


2-226 PM5.2_BF

• Time to delay the start of the user-defined monitor

• Path to the executable script

• Frequency with which the user-defined monitor runs

• Event severity

OPTIONS -a, --add-event event_name

Specifies the health, status, or statistical event to be added to the user-defined monitor.

-C, --comparator-type {"<"|">"|"=="|"<="|">="|"!="}

Specifies a comparing symbol to allow a user to compare a target value with a return value from a user monitor.

-c, --create

Creates a basic user monitor when an executable script path is specified using the -E (executable) option.

-D, --startup-delay time_in_seconds

Specifies the number of seconds to wait after the start of the application or load balancer before starting the monitor.

-d, --delete

Deletes the specified user-defined monitor.

-E, --executable "text"

Specifies the path to the executable script when the user-defined monitor is first created.

-I, --schedule-interval {time_in_seconds}

Defines the frequency with which the specified monitor will run. The default and the minimum time interval is 10 seconds.


Specifies an optional description of the user-defined monitor when it is first created.

UMON

PM5.2_BF 2-227

-l, --long

Lists information about current user-defined monitors. Without an additional argument, the list option displays the Name, Description, path to the executable, the schedule Interval, and Startup Delay, and Units for the frequency with which a monitor runs for all user-defined monitors within a specified LPAN.

-m, --modify-event event_name

Specifies the health, status, or statistical event to be modified in an existing user-defined monitor.

-N, --new-event-name event_name

Renames the specified event.

-n, --rename new_monitor_name

Renames the specified existing user-defined monitor.

-r, --remove-event event_name

Specifies the health, status, or statistical event to be removed from an existing user-defined monitor.

-S, --event-severity {1-6}

Specifies the severity of the event as an integer between 1 and 6.

-T, --target-value integer

Specifies an integer indicating the value that the returned monitor value will be compared against.

-U, --set-unit unit

Assigns a unit measure for the monitor value, for example bytes/sec or percentage.

EXAMPLES Create a standard VMware status application monitor vm_status:

umon -c -E "/opt/panmgr/templates/vmware/status.sh" MyLPAN/vm_status


2-228 PM5.2_BF

Create a PAN Manager event vmstuck of severity 3 whenever your VMware status application monitor vm_status returns a value equal to 1:

umon -a vmstuck -C "==" -T -1 -S 3 MyLPAN/vm_status

Create a PAN Manager event vmerror of severity 3 whenever your VMware status application monitor vm_status returns a value greater than 0:

umon -a vmerror -C ">" -T 0 -S 3 MyLPAN/vm_status



SEE ALSO EVENT

LPAN


USER

PM5.2_BF 2-229

USER

NAME user - creates or modifies attributes, including role assignments, for each PAN Manager software user.

SYNOPSIS user [-a |-m] [-N fullname][-T title][-E emailaddress][-D deptname] username

user -r [-f] username

user [-l] [username]

user [-l] [-O |-S |-P lpanname]

user [-aR |-rR] rolename username

DESCRIPTION The user command creates or modifies attributes, including role assignments, for each PAN Manager software user. PAN Administrators can create PAN Manager users with the same username on the cBlades using either the account command or another Linux account management tool.

PAN Manager users require a Linux user account created with the PAN Manager command, account, for cBlade access. You should create PAN Manager accounts for those administrators who will use PAN Manager to manage a PAN or an LPAN. PAN Manager users with only a PAN Manager user account cannot access the cBlades directly.

Using the user -l command without an argument displays a list of current users.




2-230 PM5.2_BF


username

Reference to the username PAN Manager uses to identify a PAN Manager user.

lpanname|platformname

Specifies the LPAN or platform name to which you are adding users.

OPTIONS -a, --add username

Adds a specified Linux account user as a PAN Manager user.

-aR, --assign rolename username

Assigns a role to a user. You can get a complete list and description of current roles using the role -l command.

-D, --deptname "deptname

Specifies a user’s department. Department names cannot contain spaces.

-E, --email emailaddress

Specifies the email address for a user.

-f, --force

Forces a user command operation without displaying a prompt.

-l, --long

Lists information about current users. Without an additional argument, the list option displays the roles, full name, title, email, and department name for all users. You can use this option in combination with the -S (sysadmins) and -O (roles) options to display a filtered list of users.

USER

PM5.2_BF 2-231

-m, --modify username

Modifies the settings for a specified PAN Manager user.

-N, --fullname fullname

Specifies the full name of a user, if needed. Full names cannot contain spaces.

-O, --roles

Lists all the users by username, and the roles they have been assigned. Use this option in combination with the -l (long) option.

-P, --lpanusers lpanname

Displays a list of users in a specified LPAN. Use this option in combination with the -l (list) option.

-r, --remove username

Removes a specified PAN Manager user.

-rR, --un-assign rolename username

Removes a role from a user.

-S, --sysadmins

Lists all the users assigned the role of System administrators. Use this option in combination with the -l (long) option.

-T, --title "title"

Specifies the title of a user, if needed. Titles cannot contain spaces.

EXAMPLES Add a full name and an email address to the user cgable:

user -m -N Clark_Gable -E [email protected] cgable

List the users that have the LPAN Administrator role in the LPAN development:

user -l development-LPAN-Administrator


2-232 PM5.2_BF

Give user cgable an LPAN Administrator role in the development LPAN:

user -aR development-LPAN-Administrator cgable



SEE ALSO ACCOUNT

ROLE

To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_role).

VERSION

PM5.2_BF 2-233

VERSION

NAME version - Lists versions of software packages installed on a cBlade or pServer.

SYNOPSIS version [-c |-p |-e |-x |-g] [platformname/cn |-s lpanname/pservername]

version -r {"egenkern"|"panmgr"}[platformname/cn|-s lpanname/pservername]

DESCRIPTION The version command lists versions of software packages (RPMs) installed on a platform. Specific information displayed includes:

• Software installation history, detailing release and build number, and build date for either a specified cBlade or a pServer.

• The version(s) of Installation media, Linux kernel, egen kernels, PAN Manager software, and egen RPMs that have been installed on a specified cBlade or pServer.

• A log of all egen RPM installations made to date.

PAN Administrators use the version command to list the history, version number, and kernel type of software running on a specified cBlade or pServers. LPAN administrators use the version command to list the history, version number, and kernel type of software running on a specified pServer in their LPAN.

All users can use the version command without arguments to display a list of all version information for the platform. The specified cBlade or pServer you are interested in must be currently booted for the information to be updated or displayed.


2-234 PM5.2_BF




platformname/sN

Specifies a Switch Blade. PAN Manager naming conventions require you to use a forward slash (/) between the platform name and the sBlade number. For example, sBlade 2 on the platform named production would be referred to as production/s2.

lpanname/pservername

Specifies a pServer. PAN Manager naming conventions require you to use a forward slash (/) between the LPAN name and the pServer name. For example, the pServer, Web1, to be designated as a MON server in the production LPAN, would be referred to as production/Web1. PAN Administrators use the lpan command to name LPANs, and LPAN Administrators use the pserver command to name pServers.

OPTIONS -c, --cd-version

Displays the release and build number of the installation media for a cBlade or a pServer as well as the date the installation was built.

-e, --egen-kernel

Displays the release and build number of the production kernel and user packages for pServers as well as the date the kernel package was built.

-g, --revision-log

Displays a list of the production RPMs installed on the cBlade.

VERSION

PM5.2_BF 2-235

-p, --panmgr-version

Displays the release number, compatibility number, and build number of PAN Manager running on the specified cBlade or pServer, as well as the date the package was built. For example, specifying this option displays information similar to the following:

Egenera, Inc.Pan Manager ServerVersion: 5.2.9Compatibility: 7Build: 1670Package: panmgrDate: 02-18-2010

(The compatibility number is for internal use only, and does not represent or indicate any part of the PAN Manager release number.)

-r, --rpm {"egenkern"|"panmgr"}

Displays the RPMs used to install the specified component, the production kernel, or the PAN Manager software.

-s, --pserver lpanname/pservername

Specifies a pServer’s version information. Without this option, you can only display version information about cBlade software.

-x, --linux-kernel

Displays the kernel version of the operating system running on the cBlade.

SEE ALSO To view the man page for a PAN Manager command, enter the following (in all lowercase letters) at the Linux prompt: man egenera_commandname (for example, man egenera_lpan).

PAN Manager Command Reference - Fujitsu …manuals.ts.fujitsu.com/file/3640/commands.pdfPM5.2_BF vi...

Documents

Transcript of PAN Manager Command Reference - Fujitsu …manuals.ts.fujitsu.com/file/3640/commands.pdfPM5.2_BF vi...