Upload
nguyenlien
View
231
Download
1
Embed Size (px)
Citation preview
PAN Manager GUI Guide
For BladeFrame® BF400 S2 and BladeFrame® BF200
Document Number 430-SB0076
August 2008
PM5.2_BF
Contents
Introduction ............................................................................................................. 1-1PAN Manager Release Information ................................................................ 1-1Using the PAN Manager GUI ......................................................................... 1-1Logging On....................................................................................................... 1-1
pServers ................................................................................................................... 1-1Viewing the pServer Dashboard....................................................................... 1-1About Viewing pServers 1View Information About a PAN’s pServers 3View Information About a PAN’s pServers (CLI) 3Configuring pServers........................................................................................ 1-1Configure a SCSI Disk for a pServer 1Specify a Boot Image and Boot Options for a pServer 1Enable or Disable Hyperthreading at the BIOS Level for a pServer 2About pServers 2Controls for a pServer 19About the pServer Console 21Configure a pServer 22Configure a pServer (CLI) 23Managing a pServer Boot Image...................................................................... 1-1About Managing a pServer Boot Image 1Manage a pServer Boot Image 2Manage a pServer Boot Image (CLI) 3Managing a pServer Root Disk Image ............................................................. 1-1About Managing a pServer Root Disk Image 1Manage a Root Disk Image 3Manage a Root Disk Image (CLI) 3Managing a Media Image................................................................................. 1-1About Managing a Media Image 1Manage a Media Image 2
PANs ....................................................................................................................... 1-1
PM5.2_BF iii
PAN Manager GUI Guide
Viewing PANs.................................................................................................. 1-1About Viewing PANs 1View Information About a PAN (CLI) 2Managing the PAN........................................................................................... 1-1About Managing the PAN 1Manage the PAN 8Manage the PAN (CLI) 9Disaster Recovery............................................................................................. 1-1Managing PAN Archives 1Managing a PAN Archive 1Modifying a Schedule for PAN Archives 1Mapping Resources 1Managing PAN Access .................................................................................... 1-1Security: A Brief Overview 1About Managing Users and Roles 3Manage PAN Manager Users and Their Roles 6Manage PAN Manager Users and Their Roles (CLI) 7Modifying a PAN Manager User .................................................................... 1-1About Editing a PAN Manager User 1Edit a PAN Manager User 3Edit a PAN Manager User (CLI) 3Editing Your PAN Manager User Profile ....................................................... 1-1About Editing Your PAN Manager User Profile 1Edit Your PAN Manager User Profile 2Edit Your PAN Manager User Profile (CLI) 2
Platforms ................................................................................................................. 1-1Viewing Platforms............................................................................................ 1-1About Viewing Platforms 1View Information About a Platform (CLI) 1Managing a Platform ........................................................................................ 1-1About Platform Systems 1Controls for Managing the Platform 7Configure Management Settings for the Platform 7Configure Management Settings for the Platform (CLI) 8Managing Domain Settings .............................................................................. 1-1About Domain Settings 1Manage Domain Settings 7Manage Domain Settings (CLI) 7Configuring a Power Input Module.................................................................. 1-1
iv PM5.2_BF
Contents
About Power Input Modules (PIMs) 1Configure PIM Settings 4Configure PIM Settings (CLI) 4Events and Monitors......................................................................................... 1-1Managing Events 1Managing Event Types 1Configuring an Event Type 1Modifying User-defined Monitors 1Selecting and Displaying Monitor Data 1
Blades ...................................................................................................................... 1-1Viewing Blades ................................................................................................ 1-1About Blade Resources 1Manage Blade Resources 3Manage Blade Resources (CLI) 3Managing a Blade............................................................................................. 1-1Control Blade 1Processing Blade 7Switch Blade 16blade -- Manages the blades of a platform. 20vBlade 20 Managing Pools ............................................................................................... 1-1About Managing Pools 1Manage Global Pools 2Manage Pools (CLI) 3Configuring a Pool ........................................................................................... 1-1About Configuring a Pool 1Configure a Pool 4Configure a Pool (CLI) 4
Storage and Media ................................................................................................... 1-1Configuring SCSI Disk Resources ................................................................... 1-1About Configuring SCSI Disk Resources 1Viewing PAN Disk Resources 4Manage SCSI Disk Resources 5Manage SCSI Disk Resources (CLI) 5Managing a SCSI Disk ..................................................................................... 1-1About Managing a SCSI Disk 1Manage a SCSI Disk 7Manage a SCSI Disk (CLI) 8
PM5.2_BF v
PAN Manager GUI Guide
Configuring SCSI Tape Devices ...................................................................... 1-1About Configuring SCSI Tape Devices 1Manage SCSI Tape Devices 3Manage SCSI Tape Devices (CLI) 4Managing a SCSI Tape Device ........................................................................ 1-1About Managing a SCSI Tape Device 1Manage a SCSI Tape Device 3Manage a SCSI Tape Device (CLI) 3Managing DVD-ROM Resources .................................................................... 1-1About Managing DVD-ROMs 1Manage DVD-ROM Access 2Manage DVD-ROM Access (CLI) 2
Networking .............................................................................................................. 1-1Viewing PAN Network Resources ................................................................... 1-1About PAN Network Resources 1Manage PAN Network Resources 6Manage PAN Network Resources (CLI) 6Managing a Virtual Switch............................................................................... 1-1About Managing a Virtual Switch 1Manage a Virtual Switch 3Manage a Virtual Switch (CLI) 3Managing a Redundant Ethernet Interface ....................................................... 1-1About Redundant Ethernet Interfaces 1Manage Redundant Ethernet Interfaces 4Manage Redundant Ethernet Interfaces (CLI) 5Managing an Ethernet Interface ....................................................................... 1-1About Ethernet Interfaces 1Manage Ethernet Interfaces 3Manage Ethernet Interfaces (CLI) 3
LPANs ..................................................................................................................... 1-1Viewing Logical Processing Area Networks (LPANs).................................... 1-1About LPANs 1Manage LPANs 2Manage LPANs (CLI) 2Managing an LPAN.......................................................................................... 1-1About Configuring an LPAN 1Controls for Managing an LPAN 12Maintenance LPAN 12
vi PM5.2_BF
Contents
Configure an LPAN 13Configure an LPAN (CLI) 14Managing a Hypervisor .................................................................................... 1-1About Hypervisor Characteristics 1Controls for a Hypervisor 5Manage a Hypervisor 6High Availability .............................................................................................. 1-1Managing High-availability Applications 1Creating High-availability Applications 1Creating High-availability Load Balancing 1Managing Executable Resources for Applications 1Managing Failover Policy Resources for Application Services 1Managing Health Monitor Resources for Application Services 1Managing Network Resources for Application Services 1Managing Network File System Resources for Applications 1Managing SCSI File System Resources for Applications 1
PM5.2_BF vii
PAN Manager GUI Guide
viii PM5.2_BF
Introduction
The following topics provide an introduction to the PAN Manager GUI:
• PAN Manager Release Information
• Using the PAN Manager GUI
• Logging On
1-1
Book Title
1-2
PAN Manager Release Information
This version of the PAN Manager software’s online help supports PAN Manager PM5.2_BF.
For information relating to any last minute changes to the hardware, software, or documentation, see PAN Manager Release Notes. Copies of the release notes are available in PDF format at http://www.fujitsu-siemens.com/support.
1-1
Book Title
1-2
Using the PAN Manager GUI
The PAN Manager graphical user interface (GUI) allows you to configure, control, and monitor resources in the Processing Area Network, according to your administrative role. PAN Manager provides tools and information to help you manage these resources.
The left pane of the PAN Manager GUI provides the following information and navigation aids:
1-1
Book Title
The following PAN Manager tabs allow you to manage and monitor resources. The Help button provides context-sensitive online help about the system or resources displayed:
1-2
Logging On On the Login page:
Enter a valid login name and password. To log on successfully, do the following:
• You must already be a PAN Manager user. (If you are not a PAN Manager user, have the PAN Administrator set up a user account for you.)
• Your browser must have cookies and JavaScript turned on.
Important: To use the full functionality of the PAN Manager GUI, your web browser must have Java plugin JRE1.5 or higher. This Java plugin is available from http://java.sun.com.
Logging On to the GUI Initially
1-1
Book Title
1-2
pServers
This section of the PAN Manager GUI Guide provides descriptions for viewing and managing pServers. Topics include:
• Viewing the pServer Dashboard
• Configuring pServers
• Managing a pServer Boot Image
• Managing a pServer Root Disk Image
• Managing a Media Image
1-1
Book Title
1-2
Viewing the pServer Dashboard
(pServer Dashboard)
Depending on your PAN Manager administrative role, some information described here might not be visible on this page.
On the pServer Dashboard page:
This page lists all pServers in the Processing Area Network (PAN). A pServer is a combination of a single pBlade, an optional failover pBlade, disk resources, a root file system, and network resources that provides the capabilities of a conventional server.
About Viewing pServers
View Information About a PAN’s pServers
View Information About a PAN’s pServers (CLI)
Tip: Hovering over a pServer icon in the Name column displays additional information; click the icon to freeze the display.
About Viewing pServers
You can view the pServer Dashboard page to display the following information about each pServer in the PAN:
Name
The pServer’s name, in the form LPANname/pserver_name.
Status
The current boot status of the pServer:
An Up arrow indicates that the pServer is booted.
A Down arrow indicates that the pServer is shutdown.
Tip: If additional symbols appear in this field, hover over the field to learn the details.
Health
1-1
Book Title
Indicates the current number of one of three categories of unresolved events associated with the pServer:
High-severity events (levels 1 and 2)
Medium-severity events (levels 3 and 4)
Low-severity events (levels 5 and 6)
Uptime
In the format days hours:minutes (such as 30d 17:34), indicates how long a booted pServer has been running.
Controls
The pServer Dashboard page provides controls (Boot/Reboot, Shutdown, and Console) for managing a pServer.
Boot
Causes the pServer to power up, to boot-load its operating system, and run its initialization scripts.
Reboot
Causes the pServer to shut down, to power up, to boot-load its operating system, and run its initialization scripts.
Shutdown
Causes the pServer to be shut down, and powers off its pBlade.
Console
Opens a window in which you can type console input to the pServer, and which displays console output. The console displays the same output as would appear on the console of a conventional standalone computer, such as informational messages that the operating system generates during boot and shutdown.
Virtual Desktop (Windows only)
Opens a Virtual VGA desktop session on a pServer that is running Microsoft Windows Server 2003. If this icon is
1-2
shaded, one or more of the following is true:
– Virtual VGA desktop sessions are not supported on the pServer’s operating system.
– Microsoft Windows Server 2003 is installed on the pServer, but the pServer is not booted.
– You are using a browser other than Microsoft Internet Explorer, Version 5.5 or higher (required because a Virtual VGA desktop session uses Microsoft ActiveX controls).
View Information About a PAN’s pServers
Use the following procedure to view information about all pServers in a PAN:
Displaying pServer Information
View Information About a PAN’s pServers (CLI)
Use the following PAN Manager command to view information about all pServers in a PAN:
pan -- Lists hardware and configuration information about a specified PAN.
pserver -- Creates, lists, or modifies a pServer configuration.
1-3
Book Title
1-4
Configuring pServers
(LPANs > lpan_name > pServers > pserver_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the pServer pserver_name page:
A pServer is a collection of resources that provides the capabilities of a conventional server. The LPAN Administrator creates pServers by combining the LPAN’s processing, disk, network, and media drive resources.
About pServers
Controls for a pServer
About the pServer Console
Configure a pServer
Configure a pServer (CLI)
Configure a SCSI Disk for a pServer
You can partition and root a SCSI disk before or after you map the disk to the pServer.
Specify a Boot Image and Boot Options for a pServer
You can specify custom boot arguments for a pServer at the same time you specify a boot image. For specific information about using valid Linux boot arguments, see the pserver man page. For a complete list of valid Linux kernel arguments, see the HOWTOs at qThe Linux Documentation Project.
If you have disabled hyperthreading at the BIOS level for a pServer, you cannot enable hyperthreading using a boot argument.
1-1
Book Title
Enable or Disable Hyperthreading at the BIOS Level for a pServer
You can enable or disable hyperthreading either at the BIOS level for a pServer, or you can specify a boot image and boot options for a pServer. See the above topic.
Note: If you disable hyperthreading at the BIOS level for a pServer, you cannot enable hyperthreading using a boot argument.
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About pServers
To create useful networks on a platform, the LPAN Administrator combines LPAN resources to create functional servers, called pServers. A pServer consists of (at least one):
• Processing Blade
• Disk resource
• Network resources
• Media drive (optional)
• Application resources (optional)
(In the case of a Ramdisk boot, a pServer requires only a pBlade.) After you configure the pServers, you can assign application resources to them.
Clicking Edit...
The Edit pServer dialog box lets you rename the pServer or modify its description.
Clicking Advanced Configuration...
The Advanced pServer Configuration dialog box displays the following headings and fields:
1-2
UUID
PAN Manager generates the Universally Unique Identifier (UUID) for pServers.
Disk subpaths
Some applications might require the pServer’s disk subpaths to be visible to PAN Manager. By default, PAN Manager displays a single device ID for each physical disk. Each physical disk is associated with two underlying subpaths; each subpath has its own device ID and is associated with one of the Control Blades.
Before selecting the Map all disk subpaths check box, be sure that the pServer’s operating system supports disk submapping.
You cannot use this feature with a disk that has SCSI-3 persistent reservations enabled.
Firmware Options:
You can configure firmware option settings on each pServer. The options have the following states:
– Default — The pServer uses the hardware default setting of the pBlade.
– Enabled — The pServer can run the option if its pBlade supports it.
– Disabled — The pServer does not run the option.
You can see the current state in the Current Status column. Use the Configuration drop-down list to change the state.
The firmware settings are only applicable to pServers booted on pBlades that support the associated hardware feature. You cannot, for example, enable hyperthreading when a pServer is booted on a pBlade that does not support hyperthreading. If the pBlade does not support the option, it displays as “N/A” in the Current Status column.
You can make firmware option changes at any time but they will not take effect until the next reboot.
1-3
Book Title
Hyperthreading
This is useful when considering the processing needs of the applications that run on the pServer. By default, hyperthreading is configurable (the Disable hyperthreading in firmware check box is cleared).
A pServer can run in hyperthreading mode if its pBlade supports it and its operating system has it enabled (by means of boot arguments).
Node Interleaving
This option uses the hardware features of certain pBlades to interleave a single page of memory from each processor at a time.
Virtualization Extensions
Hypervisors use these extensions so that guest operating systems can use virtual device drivers to access the vBlade processing resource on a pBlade.
Hardware Prefetch
This option uses the hardware features of certain pBlades to bring data and instructions into higher-speed memory before the processor needs it to minimize latency. The hardware prefetch option can improve the performance of pServers running Oracle applications.
For more information about Firmware options, see PAN Manager Administrator’s Guide.
Keyboard Map
By default, a standard U.S. English (en-us) keyboard map is used when you access the vVGA desktop for a Windows HVM guest on a vBlade pServer. To establish proper keyboard operation, PAN Manager enables you to change the keyboard map for a particular pServer. Alternative keyboard maps that are currently supported include:
– de — standard German keyboard
1-4
– fr — standard French keyboard
You can change this setting whether or not your Windows guest is currently running on its vBlade pServer.
For more information, see Guest OS Installation for vBlades: Microsoft Windows.
Learn more about specific areas of this page:
• Blades (Current, Primary, Failover)
• Current Blade
• Primary Blade
• Failover Blade
• SCSI Disks
• SCSI Tapes
• vEths
• Media Drives
• Boot Image/Options
• High-Availability Usage
Blades (Current, Primary, Failover)
The blade areas of the pServer pserver_name page let you manage the processing resources of the pServer.
Each pServer must have a primary blade. You can also assign a failover blade to a pServer, which allows the pServer to resume processing if the primary blade fails.
A primary blade is a pServer’s default processing device. For the pServer's primary blade, you can select a specific blade, or designate that the blade come from the LPAN’s local blade pool (or a pBlade from the global pool if the LPAN is currently enabled to access it). This is also the case for the pServer’s failover blade.
Clicking the name of a blade displays its characteristics in detail.
1-5
Book Title
If a blade is physically removed from the platform, the name of the pBlade appears in red.
Current Blade
This area of the pServer pserver_name page shows the blade associated with the pServer, if the pServer is booted. The following are examples:
• If the pServer is running using its originally configured primary blade, the pServer’s current blade and primary blade are one and the same.
• If the blade originally configured as the pServer’s failover blade is now handling the pServer's processing tasks, the current blade and the failover blade are one and the same.
Primary Blade
This area of the pServer pserver_name page lets you specify a primary blade for the pServer. A pServer’s primary blade is one that was originally configured to handle the processing needs of the pServer. Even if a pServer’s blade fails over to a failover blade, the pServer’s configuration retains its primary blade, in case it fails back to the original configuration.
The pServer can acquire its primary blade either statically from a specific named blade or dynamically from a local (LPAN-wide) or global (PAN-wide, pBlade only) pool of blades. You can reconfigure the primary or failover blade while the pServer is running.
Clicking Assign/Unassign...
The Assign/Unassign blade as Primary dialog box displays the following headings and fields:
Blade
The available pBlades in the form MyFrame/pn or vBlades in the form MyFrame/pn-n, where MyFrame is the name of the platform, pn indicates the physical location of the
1-6
pBlade in the chassis (Slot numbers appear on the outside rail of the chassis.), and -n indicates the vBlade.
Selecting Pool allows the pServer to acquire its pBlade or vBlade from a local pool of pBlades and vBlades. Selecting Pool also allows you to acquire its pBlade from a global pool of pBlades. If you select Pool, be sure to populate the LPAN’s local pool with one or more pBlades or vBlades; to populate the global pBlade pool, ask a PAN Administrator at your site for assistance.
If the pServer already has a primary pBlade or vBlade, selecting None removes the pBlade or vBlade from the pServer, making it available for use elsewhere in the LPAN.
CPU/Speed/RAM
The number of processors in the pBlade or vBlade, its clock speed in MegaHertz (MHz) or GigaHertz (GHz), and its random access memory in gigabytes (GB).
Assignments
The name of the pServer, if any, to which an available pBlade or vBlade is currently assigned, and whether it is currently a pServer’s primary or failover blade.
Failover Blade
This area of the pServer pserver_name page lets you specify a failover blade for the pServer. A failover blade handles the processing needs of the pServer, if the pServer’s primary blade fails. The pServer can acquire its failover blade either statically from a specific named blade, or dynamically from a local (LPAN-wide) pool. In addition, a pServer can acquire a failover pBlade from a global (PAN-wide) pool of pBlades. vBlades are not available for global pools.
Note: A pServer on a vBlade can fail over only to another vBlade. Typically, this is a vBlade on a different pBlade (to handle failure of the original pBlade). A pServer cannot fail over from a pBlade to a vBlade.
1-7
Book Title
Clicking Assign/Unassign...
The Assign/Unassign Blade as Failover dialog box displays headings and fields that are identical to those for a Primary Blade.
SCSI Disks
This area of the pServer pserver_name page shows the physical storage components of this pServer, including its logical and physical characteristics. If a disk becomes functionally unavailable to the LPAN, the disk’s name appears in red with an accompanying caution symbol and error (NOT IN PAN).
Clicking a disk’s name displays its characteristics in detail.
Clicking Add...
The Map SCSI Disks to pServer dialog box contains the following fields:
Unit
The disk’s virtual device address, in the form (x.y). This sequence number determines the ordering on a pServer that has multiple disks: for example, disk 1.0 precedes disk 3.0.
Auto-enable disk at pServer boot
A checkmark indicates that the disk will be made available for I/O automatically when the pServer boots.
If you are not sure whether the pServer will be running a high-availability application, placing a checkmark in this field has no adverse effects, and ensures that any future application will successfully fail over if it is configured to do so.
Clear this check box if you are configuring the pServer to run one or more high-availability applications, because a pServer’s disk(s) must be allocated to each of the failover pServers that you plan to use for the application. In this case, disk enabling occurs later, during application bootup and
1-8
failover.
Disk is required to be present for pServer boot
If selected (the default), indicates that the pServer will not boot, reboot, or recover until this disk is available. (If a required disk becomes unavailable because of a power outage, the pServer enters the Boot Pending boot state; when the disk again becomes available, the pServer boots automatically.)
Choose physical SCSI disk to use for this pServer disk
This pull-down list contains all physical disk devices in the LPAN available to assign to the pServer. If you want a disk not in the LPAN, you need to allocate it first to the LPAN. See Allocating Disk Resources to add disks to the LPAN.
Clicking Remove...
The Remove SCSI Disk Mappings from pServer dialog box lists all SCSI disks currently assigned to the pServer, and lets you remove one or more disks from the pServer.
Clicking Modify...
The Modify SCSI Disk dialog box lists the disks that are currently assigned to the pServer. Select a unit number from the Unit drop-down list. The unit number identifies the disk’s virtual device address, in the form (x.y). This sequence number determines the ordering on a pServer that has multiple disks: for example, disk 1.0 precedes disk 3.0. After you select a unit number, the following fields are populated:
SCSI ID
A unique identifier for the physical disk.
Details
The company that produces the disk product, and the model number and revision number of the disk product. This information is not available if the disk is not in the PAN.
Assignments
1-9
Book Title
Shows each pServer, if any, to which the disk is assigned. A value of None indicates that the disk is not assigned to a pServer.
Auto-enable disk at pServer boot
A checkmark indicates that the disk will be made available for I/O automatically when the pServer boots.
If you are not sure whether the pServer will be running a high-availability application, placing a checkmark in this field has no adverse effects, and ensures that any future application will successfully fail over if it is configured to do so.
Clear this check box if you are configuring the pServer to run one or more high-availability applications, because a pServer’s disk(s) must be allocated to each of the failover pServers that you plan to use for the application. In this case, disk enabling occurs later, during application bootup and failover.
Disk is required to be present for pServer boot
If selected (the default), indicates that the pServer will not boot, reboot, or recover until this disk is available. (If a required disk becomes unavailable because of a power outage, the pServer enters the Boot Pending boot state; when the disk again becomes available, the pServer boots automatically.)
In the Replace SCSI disk with area, select a disk that you want to replace the current one with. The list of disks shows the SCSI IDs, details, and assignments for all of the disks available to the pServer.
SCSI Tapes
This area of the pServer pserver_name page shows the tape backup resources associated with this pServer, including its logical and physical characteristics. If a tape becomes functionally unavailable to the LPAN, the tape’s name appears in red with an accompanying caution symbol and error (NOT IN PAN).
1-10
Clicking a tape’s name displays its characteristics in detail.
Clicking Add...
The Map Tapes to pServer dialog box contains the following fields:
Unit
The tape’s virtual device address, in the form (x.y). This sequence number determines the ordering on a pServer that has multiple tape devices: for example, disk 230.0 precedes disk 245.0.
Choose physical SCSI tape to use for this pServer tape
This pull-down list contains all physical tape devices in the LPAN available to assign to the pServer. If you want a tape not in the LPAN, you need to allocate it first to the LPAN. See Allocating Tape Devices to add tape device to the LPAN.
Clicking Remove...
The Remove SCSI Tape Mappings from pServer dialog box lists all SCSI tape devices currently assigned to the pServer, and lets you remove one or more tape devices from the pServer.
Clicking Modify...
The Modify SCSI Tape dialog box lists the SCSI tape devices that are currently assigned to the pServer. Select a unit number from the Unit drop-down list. The unit number identifies the tape’s virtual device address, in the form (x.y). This sequence number determines the ordering on a pServer that has multiple tape devices: for example, tape 230.0 precedes tape 245.0. After you select a unit number, the following fields are populated:
SCSI ID
A unique identifier for the physical tape device.
Details
1-11
Book Title
The company that produces the tape device product, and the model number and revision number of this product. This information is not available if the tape device is not in the PAN.
Assignments
Shows each pServer, if any, to which the tape device is assigned. A value of None indicates that the tape device is not assigned to a pServer.
Auto-enable tape at pServer boot
A checkmark indicates that the tape device will be made available for I/O automatically when the pServer boots.
If you are not sure whether the pServer will be running a high-availability application, placing a checkmark in this field has no adverse effects, and ensures that any future application will successfully fail over if it is configured to do so.
Clear this check box if you are configuring the pServer to run one or more high-availability applications, because a pServer’s tape device(s) must be allocated to each of the failover pServers that you plan to use for the application. In this case, tape device enabling occurs later, during application bootup and failover.
The Replace SCSI disk with area lists all tape devices allocated to the current LPAN. Select a tape that you want to replace the current tape with. The list of tape devices shows the SCSI IDs, details, and assignments.
vEths
This area of the pServer pserver_name page shows the virtual Ethernet interfaces (vEths) that connect a pServer to the network. Each vEth connects a pServer to a Virtual Switch (vSwitch). Each pServer can have up to 31 vEths (veth0 through veth30).
Clicking the name of a vSwitch to which a vEth is connected displays the vSwitch’s characteristics in detail.
1-12
Clicking Add...
The Assign vEth dialog box contains the following fields:
vEth Name
The name of the vEth. (You can select veth0 through veth30; veth31 is reserved for the management network.)
MAC Address
The unique 48-bit Ethernet address of the interface, also known as a hardware or media access control (MAC) address. You can allow the PAN Manager software to assign a MAC address for this vEth (Auto-Generate), or specify a different MAC address in the Custom field.
Rate Limit
This enables you to control the rate of network traffic for each vEth that resides on a pServer. Rate Limiting is particularly useful when a pServer is connected to a vSwitch through multiple vEths. The rate control lets you accommodate applications that transmit different data at different speeds.
Rate limiting is not supported by the Windows operating system or any operating system running as a vBlade guest on a platform.
Choose a vSwitch to connect to this vEth
Lists any existing Virtual Switches to which to connect the pServer, and the following basic information:
Name
The name of the vSwitch.
Uplink
The name of the redundant Ethernet interface (rEth), if any, through which the vSwitch is connected to the external network. Not Uplinked indicates that the vSwitch is not connected to a rEth. In parentheses, non-vlan indicates that the rEth is not associated with a VLAN on the external
1-13
Book Title
network; otherwise, the name of the VLAN appears.
pServers
Indicates either that the vSwitch is not allocated to the LPAN in which the pServer resides, or lists any pServer (and its vEth) that is currently connected to the vSwitch.
Clicking Remove...
The Remove vEth dialog box lets you delete one or more of the pServer’s virtual Ethernet interfaces (vEths). This dialog box lists any existing vEths and the following characteristics of each:
Name
The interface name of the vEth and, in parentheses, the vSwitch to which the pServer’s vEth is connected.
vSwitch Uplink
The name of the redundant Ethernet interface (rEth), if any, through which the vSwitch is connected to the external network. Not Uplinked indicates that the vSwitch is not connected to a rEth. In parentheses, non-vlan indicates that the rEth is not associated with a VLAN on the external network; otherwise, the name of the VLAN appears.
MAC Address
The unique 48-bit media access control (MAC) address, or hardware address, of the vEth.
Clicking Modify...
The Modify vEths dialog box lists any existing virtual Ethernet interfaces and lets you change their characteristics. Select a vEth from the vEth drop-down list. After you select a vEth, the following fields are populated:
vSwitch
1-14
The vSwitch connected to this vEth.
MAC Address
The unique 48-bit Ethernet address of the interface, also known as a hardware or media access control (MAC) address. You can allow the PAN Manager software to assign a MAC address for this vEth (Auto-Generate), or specify a different MAC address in the Custom field.
Rate Limit
This enables you to control the rate of network traffic for each vEth that resides on a pServer. Rate Limiting is particularly useful when a pServer is connected to a vSwitch through multiple vEths. The rate control lets you accommodate applications that transmit different data at different speeds.
Rate limiting is not supported by the Windows operating system or any operating system running as a vBlade guest on a platform.
The Choose a vSwitch to connect to this vEth area lists any existing Virtual Switches that you can connect to the pServer. This area contains the following fields:
Name
The name of the vSwitch.
Uplink
The name of the redundant Ethernet interface (rEth), if any, through which the vSwitch is connected to the external network. Not Uplinked indicates that the vSwitch is not connected to a rEth. In parentheses, non-vlan indicates that the rEth is not associated with a VLAN on the external network; otherwise, the name of the VLAN appears.
Assignments
Indicates either that the vSwitch is not allocated to the LPAN in which the pServer resides, or lists any pServer (and its vEth) that is currently connected to the vSwitch.
1-15
Book Title
Media Drives
This area of the pServer pserver_name page lists the platform media drives. To determine whether a drive is accessible to the pServer, hover over the drive’s icon.
On each cBlade there is one DVD-ROM.
A Virtual CD (VCD) is a device pServers and hypervisors use to access media images registered with PAN Manager. Once registered, an image is available for use by all pServers in the PAN. In general, PAN Manager attaches one VCD to a pServer and recognizes the device using unit number (125.0).
For vBlades running a hypervisor, PAN Manager allocates up to 32 VCDs, one for each guest operating system running on the hypervisor. For more information on using VCDs with vBlades, see Using vBlades.
For specific information about VCDs and operating systems, see PAN Manager Administrator’s Guide.
Clicking Load/Eject...
The Load/Eject Media in Virtual CD-ROM dialog box lets you load stored CD images into the pServer’s VCD, or release the current media image from the VCD on a specified pServer.
The Loaded Media drop-down list provides all of the CD images available to the pServer. Select the media image that you want to insert and click Submit to complete the loading. Select EMPTY to eject the media.
When checked, the Force media ejection check box ejects the media image immediately without unmounting.
Clicking Enable/Disable...
The Enable/Disable DVD-ROM Access dialog box lets you control whether the pServer is to have access to the BladeFrame DVD-ROM drives.
1-16
To enable a drive for the pServer, the PAN Administrator must also enable access to the drive for the entire LPAN in which the pServer resides. This dialog box contains the following fields:
Name
The name of the DVD-ROM drives, in the form (scsi)@MyPlatform/cn, where scsi is the hardware device number format, MyPlatform is the name of the platform in which the drive is located, and cn indicates whether the drive is on cBlade 1 or cBlade 2.
Model
The model number of the DVD-ROM drive.
Boot Image/Options
This area of the pServer pserver_name page lists all operating system boot images that are available to the pServer. The PAN Administrator determines which boot image(s) are available to the PAN domain, and of these, which is the System default boot image for pServers in the PAN. Available boot images reside on the Control Blades.
Clicking Modify...
The pServer Boot Image/Options dialog box lets you change the pServer’s boot image, or configure optional settings for a pServer before it has been booted. This dialog box contains the following fields:
Boot Image
The images are split into two groups, EVBS and other boot images. EVBS is the standard booting method. The top group lists the EVBS boot images. If you have other boot images, they are listed in the bottom group.
For each boot image, the following information appears (The PAN Administrator provided this information when the boot image was registered.):
Name
1-17
Book Title
The display name of the boot image. The selected radio button indicates the pServer’s currently configured boot image; the PAN’s default boot image appears in bold and is marked with an asterisk (*).
OS Type
The type of operating system contained in the boot image.
Description
A brief description about the operating system release and build number, such as whether the image is for installation (Install) or recovery (Rescue) purposes.
– vethn — Available vEths numbered from 0 through 30. In order to boot from the network, you need to have a PXE server available to transfer the image over the network.
Image Boot Arguments
(Read-only) The Linux boot arguments embedded in the boot image. (To change these boot arguments, enter the appropriate arguments in the User Defined Boot Arguments field.)
User Defined Boot Arguments
Lets you add to, or override, the boot image’s embedded boot arguments.
You can specify a device or the desired order in which to scan the pServer’s assigned devices for a bootable operating system image
If you are configuring the pServer to have its root file system installed on network-attached storage (NAS), you can specify the location for the root file system in this field.
For specific information about using certain boot arguments, see the pserver man page. For a
1-18
complete list of valid Linux kernel arguments, see the HOWTOs at The Linux Documentation Project.
For more information on EVBS, see Using Egenera Virtualized Boot Services.
pServer is optional (failure does not terminate LPAN boot sequence).
This option is available for EVBS and custom images. If selected (the default behavior), indicates that the LPAN can boot successfully even if this pServer experiences a failure. Important: If you clear this field, and if the pServer fails when its LPAN boots, pServers that are lower down in the boot order than this pServer will not boot.
High-Availability Usage
(This area of the pServer pserver_name page is visible only if there is at least one application configured on the pServer.)
This area of the pServer pserver_name page lists any applications, load balancers, or application health monitors currently configured on the pServer.
Clicking High Availability...
Lets you configure applications or application resources on this pServer.
Controls for a pServer
The bottom border of the pServer pserver_name page has controls (Boot/Reboot, Shutdown, and Console) for managing a pServer:
Boot
Causes the pServer to power up, boot-load its operating system, and run its initialization scripts. When booting on a vBlade, PAN Manager boots the pServer if:
1-19
Book Title
• The pServer’s primary blade assignment specifies a vBlade or a local pool containing vBlades — see the Primary Blade area in the pServer pserver_name page.
• The pServer’s boot image assignment is compatible with the underlying hypervisor of the vBlade (which runs on the supporting pBlade) — see the Boot Image/Options area in the pServer pserver_name page.
Reboot
Causes the pServer to shut down, power up, boot-load its operating system, and run its initialization scripts. When you reboot a pServer on a vBlade, the considerations that apply are the same as for shutting down and booting a pServer.
Shutdown
Causes the pServer to shut down, and powers off its pBlade. When you shutdown a pServer running on a vBlade, the vBlade powers off and, depending on your configuration, makes it available for allocation during subsequent pServer boot or failover operations
Suspend
Causes the pServer to suspend. When PAN Manager suspends a pServer, you need to specify a disk to store the suspended state of the guest.
Caution: The suspend operation will repartition 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. For more information, see Using vBlades.
Resume
1-20
Causes the pServer to resume from suspension. When the operation is complete, the pServer’s status changes to Booted and PAN Manager discards the file containing the suspended state.
Migrate
Causes the pServer to migrate from one vBlade to another. After the migration is complete, the destination vBlade becomes the pServer’s current blade and the pServer’s status changes to Booted. The original vBlade becomes available for allocation (according to your configuration).
Console
Opens a virtual text console in which you can type console input to the pServer, and which displays console output. The console displays the same output as would appear on the console of a conventional standalone computer, such as informational messages that the operating system generates during boot and shutdown.
Virtual Desktop (Windows only)
Opens a Virtual VGA desktop session on a pServer that is running Microsoft Windows Server 2003. If this icon is shaded, one or more of the following is true:
• Microsoft Windows Server 2003 is installed on the pServer, but the pServer is not booted.
• You are using a browser other than Microsoft Internet Explorer, Version 5.5 or higher (required because a Virtual VGA desktop session uses Microsoft ActiveX controls).
About the pServer Console
The pServer console provides terminal access to the pServer’s operating system.
1-21
Book Title
The top border of the console provides a summary of the operating status of the pServer.
Configure a pServer
Use the following PAN Manager procedures to configure a pServer:
Controls for the pServer:
Booting and Rebooting a pServer
Shutting Down a pServer
To suspend and resume a pServer on a vBlade, see the Administering vBlades chapter in Using vBlades.
To migrate a pServer to another vBlade, see the Administering vBlades chapter in Using vBlades.
Opening a Console
Creating a pServer
Modifying a pServer Name or Description
To map all disk subpaths to a pServer:
Configuring pServer Boot Attributes
Boot Arguments
Assigning a Primary pBlade
Assigning a Failover pBlade
Assigning a Disk to a pServer
Assigning a Tape Device to a pServer
Creating Network Connections
Enabling a DVD-ROM Drive for a pServer
Registering Images as Virtual CD-ROMs
Managing Virtual CD-ROMs
1-22
Configure a pServer (CLI)
Use the following PAN Manager commands to configure a pServer:
pserver -- Creates, lists, or modifies a pServer configuration within an LPAN.
version -- Lists versions of software packages installed on a cBlade or pServer.
Use the following PAN Manager command to list the current tftp boot images available for a pServer:
lpan -- Creates, lists, or modifies an LPAN configuration.
1-23
Book Title
1-24
Managing a pServer Boot Image
(PAN_name > boot_image_name)
On the pServer Boot Image image_name page:
This page displays information about an operating system boot image available to pServers in the PAN.
About Managing a pServer Boot Image
Manage a pServer Boot Image
Manage a pServer Boot Image (CLI)
About Managing a pServer Boot Image
pServer boot images can be used to boot any pServer in the PAN, provided the pServer’s blade architecture supports the operating system image.
Each boot image is defined by the following characteristics:
image_name
(In the left portion of the page) The name that you assigned to the boot image.
Location
The physical location on the cBlade of the image.
OS Type
Information about the operating system or type of image (install or rescue).
System Default
Indicates whether this boot image is the default for the PAN. The default image is used to boot a pServer if no other image is specified.
1-1
Book Title
Clicking Modify...
The Modify Boot Image dialog box lets you modify the information about the boot image.
Caution: Changing an image’s source will cause all pServers associated with this image to use the new source upon reboot.
The Modify Boot Image dialog box has the following fields:
Name
The display name that administrators use to identify this pServer boot image for pServers.
Source
Use current source boot image (no changes)
If selected, PAN Manager continues to use the currently configured boot image.
cBlade File
If selected, specify the full pathname of the boot image file on the cBlade.
Local File
If selected, specify the full pathname of the boot image. You can also use the Browse button to navigate to the image.
OS Type
Descriptive text about the operating system associated with this pServer boot image.
Description
Descriptive text for this pServer boot image for administrators to know or remember.
Manage a pServer Boot Image
Use the following PAN Manager procedure to manage a boot image:
1-2
Modifying a Boot Image
You must have the PAN Administrator role to perform these tasks.
Manage a pServer Boot Image (CLI)
Use the following PAN Manager command to manage a boot image:
pan -- Registers or modifies a pServer’s boot image with the PAN.
1-3
Book Title
1-4
Managing a pServer Root Disk Image
(PAN_name > root_image_name)
On the pServer Root Image image_name page:
This page displays information about a root disk image available to pServers in the PAN.
About Managing a pServer Root Disk Image
Manage a Root Disk Image
Manage a Root Disk Image (CLI)
About Managing a pServer Root Disk Image
pServer root disk images can be used by any pServer in the PAN, provided the pServer’s operating system supports the root image file type.
Each root image is defined by the following characteristics:
image_name
(In the left portion of the page) The name that you assigned to the root image.
Location
The physical location on the cBlade of the image.
OS Type
Information about the operating system or type of image.
File system
The supported file system types for this root image.
System Default
1-1
Book Title
Indicates whether this root image is the default for the PAN. The default image is used to root the disk of a pServer if no other image is specified.
Hypervisor: default
This section of the pServer Root Image image_name page provides information about the default hypervisor.
Provider
The software vendor providing the hypervisor.
Version
The hypervisor version number.
Architecture
The architecture type of the pBlade processor used by the hypervisor.
FS Size
File system size for the hypervisor.
Description
Descriptive text for this hypervisor root image for administrators to know or remember.
Clicking Modify...
The Modify Root Image dialog box lets you modify information about the boot image.
The Modify Root Image dialog box has the following fields:
Name
The display name that administrators use to identify this
1-2
pServer boot image for pServers.
Source
Use current source root image (no changes)
If selected, PAN Manager continues to use the currently configured root image.
cBlade file
If selected, specify, in the field provided, the full pathname of the root image file on the cBlades.
OS Type
Descriptive text about the operating system associated with this pServer root image.
Description
Descriptive text for this pServer root image for administrators to know or remember.
Supported file systems
Indicates the file system(s) associated with this root disk image.
Manage a Root Disk Image
Use the following PAN Manager procedure to manage a root disk image:
Modifying a Boot Image
Manage a Root Disk Image (CLI)
Use the following PAN Manager command to manage a root disk image:
pan -- Registers or modifies a pServer’s root disk image with the PAN.
1-3
Book Title
1-4
Managing a Media Image
(PAN_name > media_image_name)
On the Media Image image_name page:
This page displays information about a media image available to pServers in the PAN.
About Managing a Media Image
Manage a Media Image
About Managing a Media Image
You can use media images with any pServer in the PAN. Each image is defined by the following characteristics:
image_name
(In the left portion of the page) The name that you assigned to the media image.
Location
The physical location of the image on the cBlade.
Type
Information about the type of image.
Hypervisor default
Indicates whether this media image is the hypervisor default for the PAN. The default image is used to boot a hypervisor blade if no other image is specified.
Note: This field displays for hypervisor media images only.
1-1
Book Title
Clicking Modify...
The Modify Media Image dialog box lets you modify information about the media image.
This dialog box has the following fields:
Name
The display name that administrators use to identify this media image for pServers.
Source
Use current source media image (no changes)
If selected, PAN Manager continues to use the currently configured media image.
cBlade file
If selected, specify, in the field provided, the full pathname of the media image file on the Master cBlade.
Type
Descriptive text about the operating system associated with this media image.
Description
Descriptive text for this media image for administrators to know or remember.
Manage a Media Image
Use the following procedure to manage your media images:
Modifying Virtual CD-ROM Images
Registering Images as Virtual CD-ROMs
Managing Virtual CD-ROMs
1-2
PANs
This section of the PAN Manager GUI Guide provides GUI descriptions for viewing and configuring PANs. Topics include:
• Viewing PANs
• Managing the PAN
• Disaster Recovery
• Managing PAN Access
• Modifying a PAN Manager User
• Editing Your PAN Manager User Profile
1-1
Book Title
1-2
Viewing PANs (Discovered PANs)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the Discovered PANs and Platforms page:
This page lists all of the discovered Processing Area Networks (PANs) and details about each PAN’s configuration.
About Viewing PANs
View Information About a PAN (CLI)
Tip: Hovering over the PAN icon displays additional information; click the icon to freeze the display.
About Viewing PANs
You can view the Discovered PANs page to display all the discovered PANs, each PAN’s management IP address, PAN Manager version, and member platforms.
Clicking Local PAN...
Takes you to the local PAN where you can manage and configure the PAN.
Each PAN displays the following information:
Name
The name of the PAN.
Management IP
The IP address for the PAN Manager login.
PAN Manager Version
The release number of the PAN Manager software running on the cBlades.
1-1
Book Title
Member Platforms
The name and ID number of the platforms in the PAN. The icons indicate which platform is the PAN Master.
Tip: To examine the characteristics of each PAN, hover over the PAN icon next to its name.
To log on to another PAN, click the login>> link next to the PAN name.
View Information About a PAN (CLI)
Use the following PAN Manager command to view information about a specified PAN:
pan -- Lists hardware and configuration information about a specified PAN.
1-2
Managing the PAN
(PAN_name)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the PAN pan_name page:
This page lists the current Processing Area Network (PAN), information about any additional platforms in the same PAN, and the available root and boot images.
About Managing the PAN
Manage the PAN
Manage the PAN (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing the PAN
This page lets you specify the configuration of the PAN:
• Set PAN Manager control of user accounts
• Configure the SMTP mail server
• Register pServer root and boot images
• Allow or prevent multicast flow control
This page also links to the Disaster Recover page and the Domain Settings page for the PAN.
Learn more about specific areas of this page:
• Disaster Recovery
• Domain Settings
• Current PAN
• PAN Platforms Section
1-1
Book Title
• pServer Boot Images Section
• Root Images Section
• Media Images Section
Disaster Recovery
Clicking the Disaster Recovery button displays the Disaster Recovery page where the PAN Administrator can create and manage PAN archives.
Domain Settings
Clicking on the Domain Settings button displays the Domain Settings page for the PAN where the PAN Administrator can configure the event settings, SNMP Agents and Managers, and assign a user to the PAN Administrator role.
Current PAN
This area of the PANs page displays the characteristics of the currently active Processing Area Network.
Clicking Edit...
The Edit PAN Information dialog box displays the following fields:
PAN Name
The name of the entire Processing Area Network, as currently configured. Only one PAN can exist at a time, although the PAN might be associated with one or more existing PAN archives. (The name of the PAN may or may not be identical to any archives associated with the PAN.)
Owner
The person who manages this security domain, and how to contact them (such as phone number or e-mail address).
Location
1-2
The data center and/or site location of this platform.
Description
A brief distinguishing comment about this platform.
Clicking Accounts...
The PAN Account Control dialog box allows PAN Manager control of operating system user accounts on the cBlade.
Note: Although PAN Manager lets you manage Linux user accounts on the Control Blades, using it for this purpose prevents you from using other account management utilities to manage those accounts. This is important to note if, for example, you are accustomed to using a user management tool to manage existing user accounts in an external database.
Clicking Multicast...
The PAN Multicast setting dialog box allows multicast flow control setting.
If the external network in which the platform resides is using the multicast network protocol, under heavy network traffic, some network configurations allow packets to be dropped silently. To prevent this from happening, you can activate network flow control, which regulates packet exchange between internal components.
This setting lets you activate flow control explicitly for the entire PAN. If explicit flow control is not activated, you can also activate flow control implicitly on individual redundant Ethernet interfaces (rEths).
Clicking SMTP...
The PAN SMTP settings dialog box displays the following fields:
Host
The host name or IP address of the SMTP mail server to be
1-3
Book Title
used for e-mail notification of PAN Manager events.
Port
The port number of the SMTP mail server.
‘From’ Address
The full e-mail address from which the PAN Administrator, or the PAN Manager software acting on behalf of the PAN Administrator, can send e-mail messages.
SMTP User
The user account name of the administrator you specify in the From Address field.
SMTP Password
A password associated with the SMTP user account.
Confirm Password
Verification of the password.
Clicking Templates...
The PAN Templates dialog box lists the application templates available to LPANs within this PAN. Templates are imported to the LPAN at the LPAN page.
PAN Platforms Section
The PAN Platforms section lists information about all of the platforms currently in the PAN.
Click the name of the platform to display the Platform page for that frame.
Clicking Synchronize...
The Synchronize PAN Platforms dialog box the PAN Administrator distribute a snapshot of the PAN Master’s configuration settings all cBlade members of the PAN.
1-4
pServer Boot Images Section
This section displays the pServer boot images available to pServers in the PAN.
Clicking on the boot image name displays the pServer Boot Image page.
Clicking Import...
You can import images as large as 2.5 GB. The Create Boot Image dialog box displays the following fields:
Name
The display name of a pServer boot image as it will appear in PAN Manager; for example, RHEL35I001205 for Red Hat Enterprise Linux.
Source
The source of the boot image that can come from:
cBlade File
If selected, specify the full pathname of the boot image file on the cBlade.
Local File
If selected, specify the full pathname of the boot image. You can also use the Browse button to navigate to the image.
From pServer
If selected, specify from the list which pServer image that you want PAN Manager to extract and copy on the cBlades. This operation subsequently deploys this boot image for use by all other pServers in the PAN.
OS Type
The operating system that the boot image contains.
Description
1-5
Book Title
A brief identifying note about the boot image.
Clicking Delete...
The Delete Boot Images dialog box displays the boot images currently configured in PAN Manager.
Clicking Default...
The Set Default Boot Image dialog box lets you specify a default boot image for all pServers to be configured in the PAN.
Root Images Section
This section displays the root disk images available to pServers in the PAN.
Clicking on the boot image name displays the pServer Boot Image page.
Clicking Import...
You can import images as large as 2.5 GB. The Create Root Image dialog box displays the following fields:
Name
The display name of a pServer root disk image as it will appear in PAN Manager; for example, RHEL31I001205 for Red Hat Enterprise Linux.
Source
The root image’s pathname on the cBlades.
OS Type
The operating system that the root image contains.
Description
A brief identifying note about the root image.
Supported File Systems
1-6
A list of Linux file system types that the root disk image supports, and which of these types is the default file system type for the root disk image.
Clicking Delete...
The Delete Root Images dialog box displays the root images currently configured in PAN Manager.
Clicking Default...
The Set Default Root Image dialog box lets you specify a default root image for all pServers to be configured in the PAN.
WinPE Image Available:
A WinPE (Windows Pre-installation Environment) image is a Windows operating system image (for use by pServers).
A checkmark indicates that a WinPE image has been installed on the Control Blades; an X indicates that no WinPE image resides on the Control Blades.
Media Images Section
This section displays the media images available to pServers in the PAN. Clicking on the image name displays the Media Image page.
Clicking Import...
You can import images as large as 2.5 GB. The Create Media Image dialog box displays the following fields:
Name
The display name of the media image that will appear in PAN Manager.
Source
The source of the media image that can come from:
cBlade File
If selected, specify the full pathname of the media
1-7
Book Title
image file on the cBlade.
Local File
If selected, specify the full pathname of the media image. You can also use the Browse button to navigate to the image.
Type
The operating system that the media image contains.
Description
A brief identifying note about the media image.
Clicking Delete...
The Delete Media Images dialog box displays the media images currently configured in PAN Manager.
Clicking Default Hypervisor...
The Set Default Hypervisor Media Image dialog box lets you specify a default image for all hypervisors.
Clicking Hypervisor Password...
The Hypervisor Root Password dialog box lets you set the root password for all hypervisors in the PAN.
Manage the PAN
Use the following PAN Manager procedures to manage the PAN:
Editing the PAN General Information
Enabling Linux Account Management
Activating Flow Control
Configuring the SMTP Server
Displaying Available Application Templates
1-8
To register pServer boot images, see the appropriate pServer Guide for your operating system.
Setting the Default Boot Image
To register a root disk image, see the appropriate pServer Guide for your operating system.
Setting the Default Root Disk Image
Registering Images as Virtual CD-ROMs
Managing Virtual CD-ROMs
You must have the PAN Administrator role to perform the previous tasks.
To set a default hypervisor root image for the PAN domain, see the appropriate pServer Guide for your operating system.
Manage the PAN (CLI)
Use the following PAN Manager commands to manage the PAN:
pan -- Lists and modifies the PAN configuration.
smtpsvr -- Creates, lists, or modifies an SMTP server on a platform.
user -- Creates or modifies attributes, including role assignments, for each PAN Manager user.
1-9
Book Title
1-10
Disaster Recovery
This section of the PAN Manager GUI Guide provides GUI descriptions for configuring disaster recovery. Topics include:
• Managing PAN Archives
• Managing a PAN Archive
• Modifying a Schedule for PAN Archives
• Mapping Resources
1-1
Book Title
1-2
Managing PAN Archives
(PAN_name > Disaster Recovery)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the Disaster Recovery page:
This page lets you create and manage backup copies of your PAN configuration.
About Managing PAN Archives
Manage PAN Archives
Manage PAN Archives (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing PAN Archives
This page lets you manage PAN archives. You can create PAN archives as needed, or schedule them to be created on a regular basis. A PAN archive preserves the configuration settings of the entire PAN. The archive consists of a file (archive_name.par) that can reside on the Control Blade(s), be saved locally on a client machine, or saved to external disk (SAN) storage.
A PAN archive is useful for the following:
• To restore a PAN configuration to another platform in the event of a disaster situation in which the platform is destroyed or incapacitated.
• To repair damaged configuration files: if portions of a PAN configuration become unusable because of hardware or software errors, or because both cBlades are replaced simultaneously, you can import and validate a PAN archive to restore the settings.
1-1
Book Title
• To support day/night PAN configurations, based on the time-affected demand for platform services.
Learn more about specific areas of this page:
• PAN Archives
• Image Archives
• PAN Archiving Schedules
Clicking Save Current PAN...
The Archive Current PAN dialog box displays the following headings and fields:
Archive name
The name of a PAN archive associated with the current PAN. The suggested (default) name is the same as the name of the current PAN.
Include internal log files
A checkmark indicates that you want to include audit log information in the PAN archive. (Fujitsu Siemens Computers customer support or your authorized support vendor can later examine this log, if a problem arises.)
PAN Archives
This area lists all existing PAN archives that reside on the Control Blades. If an archive is corrupt, the file cabinet drawers display as open and empty. You cannot access a corrupt archive’s contents.
In order to restore a PAN archive file to use as the new PAN, you must do the following:
• Import the archive file.
• (Optionally) Map its resource settings to those in the current PAN configuration.
• (Optionally) Merge any settings unique in the current PAN configuration with those in the PAN archive.
1-2
• (Optionally) Test the resource mappings that you have created.
• Swap in the PAN archive to use as the current PAN configuration.
Swapping a PAN archive is equivalent to performing a full PAN Manager restart on both cBlades. PAN Manager GUI users are automatically logged out. PAN Manager is inaccessible to CLI and GUI users during the swap operation. After the swap operation is completed, PAN Manager automatically restarts. You must log back into the PAN Manager GUI again.
Clicking Import...
The Import Archive dialog box displays the following fields:
Under Source Archive:
Local file
The location of a PAN archive file that currently resides on a client machine on the local network.
cBlade file
The location of a PAN archive file that currently resides on the cBlade.
On SAN Disk
The location of a PAN archive file that currently resides on disk storage external to the platform. The pull-down list displays all SAN disk devices on which at least one PAN archive is currently stored.
Rename archive
A way to rename the archive as you import it.
Clicking Export...
The Export Archive dialog box allows you to specify the location at which to store a PAN archive for disaster recovery purposes: to a local client machine, to a location on the cBlade, or to a SAN disk (specified with the device ID of the disk).
1-3
Book Title
Selecting SAN Disk displays a pull-down list that contains all SAN disk devices currently set aside for the purpose of storing PAN archives.
Clicking Delete...
The Delete Archives dialog box lists all existing PAN archives.
Selecting Rename...
The Rename Archive dialog box displays a list of all existing PAN archives.
Image Archives
A PAN configuration archive does not contain images (except for non-registered boot images), because of their large size. The PAN Administrator can, however, use another facility to archive and later restore any of the images not included in a PAN archive:
• Registered pServer boot images
• Root disk images
• Media images (VCDs)
This area lists all existing archived images.
Clicking Restore...
The Restore PAN Images dialog box allows you to restore images. The facility checks the current PAN configuration, and restores images selectively:
• Boot, root, and media images — The facility restores registered images that do not match an existing image.
The dialog box contains these fields:
Source Image Archive
cBlade file system
The location on the cBlade that contains the image
1-4
archive that you want to restore.
SAN Disk
Displays a pull-down list that shows all SAN disk devices on which at least one image archive is currently stored.
Include Image Types:
boot images
Check this box to restore boot images.
root images
Check this box to restore root images.
media images
Check this box to restore media images.
Overwrite existing image files
Check this option to replace the image files currently being used by PAN Manager with the matching image files in the archive. An image is considered matching if its original pathname (before export) was the same as an image in the current PAN. When you select Overwrite, the facility restores all registered images o the current PAN, overwriting existing images if necessary.
Clicking Export...
The Export PAN Images dialog box allows you to specify the location at which to store an image for disaster recovery. The dialog displays the following:
Destination:
cBlade file system
The location on the cBlade to which you want to export the image archive.
SAN Disk
Selecting SAN Disk displays a pull-down list that
1-5
Book Title
contains all SAN disk devices currently set aside for the purpose of storing image archives.
Archive name
Provide a name for the image archive.
Include Image Types:
boot images
Check this box to export boot images.
root images
Check this box to export root images.
media images
Check this box to export media images.
Clicking Delete...
The Delete PAN Images dialog box lists all existing PAN images.
PAN Archiving Schedules
This area displays any existing schedules for creating PAN archives on a regular basis. You can schedule the backups to occur weekly or daily. You can create additional schedules to create archives at various intervals, and export them to various locations external to the platform.
To preserve the configuration settings in the Processing Area Network (PAN), it is wise to set up a backup schedule that suits the specific needs of your site. For disaster recovery purposes, we recommend exporting the PAN archive file to network attached storage (disk).
As part of an overall backup strategy, you can create multiple schedules, and then for each schedule, export the archive to a different disk.
1-6
Creating an archive schedule always saves the archive as the same name, and overwrites the previous version.
Clicking Create...
The Create Archive Schedule dialog box displays the following headings and fields:
Schedule name
Specifies the name of the schedule that PAN Manager will use to back up the PAN configuration. (For clarity, specify a name that describes the backup frequency, such as “weeklysched1”.)
Time
Specifies the hour and minute of the day that the archive will be created, and whether the time is early (AM) or late (PM) in the day.
Frequency
Specifies whether the archive is created Daily or Once a week on a specific day of the week. If weekly, you can select the day of the week on which the archive will be created.
Destination
Specifies the location to which PAN Manager will export the PAN archive. You can do either of the following:
– Select the Default location on cBlade radio button to have PAN Manager save the archive on the Control Blade(s)
– (Advisable for disaster recovery) Select the SAN Disk radio button, then select a disk from the pull-down list to store the newly created PAN archive on a SAN disk (which is not already assigned to an LPAN).
1-7
Book Title
Clicking Delete...
Lets you delete an existing archive schedule; see “Clicking Create...” for a description of these parameters.
Manage PAN Archives
Use the following PAN Manager procedures to manage PAN archives:
Creating a PAN Archive
Importing the PAN Archive
Exporting a PAN Archive
Deleting a PAN Archive
Renaming the PAN Archive (Optional)
Exporting and Restoring an Image Archive
Creating a Schedule
Deleting Schedules
Modifying a Schedule for PAN Archives
Manage PAN Archives (CLI)
Use the following PAN Manager commands to manage PAN archives:
disk -- Controls or lists operations on a disk that is physically connected to a platform and recognized by PAN Manager software by means of the sfdisk utility.
pan -- Lists and modifies the PAN configuration.
1-8
Managing a PAN Archive
(pan_name > Disaster Recovery> archive_name)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the PAN Archive archive_name page:
This page lists the contents of a single PAN archive. A PAN archive preserves the configuration settings of a Processing Area Network (PAN).
About Managing a PAN Archive
Manage a PAN Archive
Manage a PAN Archive (CLI)
Tip: Hovering over an icon displays additional information.
About Managing a PAN Archive
This page lists all configuration settings in the PAN archive. Settings are grouped into the following categories:
• PAN Configuration
• Security
• Platforms
• Physical Resources
• LPANs
Each link lets you jump to the top of that specific grouping.
Replacing the configuration settings in the current PAN with those in a PAN archive can involve the following four steps. (Only Swapping In an Archive is required.)
About Mapping PAN Resources
1-1
Book Title
About Merging an Archive With the Current PAN
About Validating an Archive
About Swapping In an Archive
About Mapping PAN Resources
The following specific names of resources:
• pBlade slots
• SAN disk
• Tape device IDs
• Physical Ethernet interfaces
can differ between the PAN archive and the current PAN. Because of this, you might have to associate each resource in the archive to use an actual counterpart resource in the current PAN. The process of mapping resources updates the PAN archive file.
Clicking Map Resources displays the Resource Mapping for Archive archive_name page. Refer to Mapping Resources for more information.
About Merging an Archive With the Current PAN
Merging a PAN archive with the resources in the current PAN completely replaces some PAN settings, modifies others (including any resources that you have mapped), and leaves others untouched. It completely replaces the following settings:
• Owner, description, and location, using PAN Manager to manage user accounts
• PAN Manager IP setup
• Registration information for boot images and root disk images
• SNMP configuration
• Mail Gateway (from address and SMTP server information)
• Default event actions
1-2
• Archive schedules
The current PAN replaces the following platform configuration information in the PAN archive:
• The platform name and power settings
• SNMP configuration
• Default event actions
• Multicast flow control settings for each rEth interface
The current PAN also replaces the PAN archive’s list of PAN Manager users to reflect the user list of the current PAN. Invalid roles (those that were assigned to removed users) are also removed.
Completing the merge operation means that the configuration settings are ready to be validated.
About Validating an Archive
Validating a PAN archive determines whether the configuration settings in the PAN archive map correctly to those in the current PAN. PAN Manager provides details if there are any remaining issues to resolve. Although swapping the PAN archive in automatically validates the archive, validating an archive without swapping it in confirms that the archive’s settings are valid, and that it might be useful to swap in later.
About Swapping In an Archive
Swapping in the PAN archive replaces the current PAN with the configuration settings in the PAN archive.
After the swap operation is complete, PAN Manager automatically restarts. You must log on to the PAN Manager GUI again.
After PAN Manager restarts automatically, the current PAN uses the new resources.
1-3
Book Title
Manage a PAN Archive
Use the following PAN Manager procedures to manage PAN archives:
Merging the Archive
Validating the Archive
Swapping the Current PAN for a PAN Archive
Manage a PAN Archive (CLI)
Use the following PAN Manager command to manage PAN archives:
pan -- Lists and modifies the PAN configuration.
1-4
Modifying a Schedule for PAN Archives
(PAN_name > Disaster Recovery > Archive Schedule)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the Archive Schedule page:
This page shows an existing schedule for creating backup copies of the Processing Area Network (PAN) configuration.
About Modifying a Schedule for Creating PAN Archives
Modify a Schedule for Creating PAN Archives
Modify a Schedule for Creating PAN Archives (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Modifying a Schedule for Creating PAN Archives
A schedule for creating PAN archives contains the following information.
Clicking Modify...
The Modify Schedule dialog box displays the following headings and fields:
Schedule name
Specifies the name of the schedule that PAN Manager will use to back up the PAN configuration.
Time
Specifies the hour and minute of the day that the archive will be created, and whether the time is early (AM) or late (PM) in the day.
Frequency
1-1
Book Title
Specifies whether the archive is created Daily or Once a week on a specific day of the week. If weekly, you can select the day of the week on which the archive will be created.
Destination
Specifies the location to which PAN Manager will export the PAN archive. You can do either of the following:
– Select the Default location on cBlade radio button to have PAN Manager save the archive on the Control Blade(s)
– (Advisable for disaster recovery) Select the SAN Disk radio button, then select a disk from the pull-down list to store the newly created PAN archive on a SAN disk (which is not already assigned to an LPAN).
Modify a Schedule for Creating PAN Archives
Use the following PAN Manager procedure to modify a schedule for creating PAN archives:
Editing a Schedule
Modify a Schedule for Creating PAN Archives (CLI)
Use the following PAN Manager commands to modify a schedule for creating PAN archives:
disk -- Controls or lists operations on a disk that is physically connected to a platform and recognized by PAN Manager software by means of the sfdisk utility.
pan -- Lists and modifies the PAN configuration.
1-2
Mapping Resources
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the Resource Mapping for Archive archive_name page:
This page lets you compare and, if necessary, map the contents of a PAN archive with the contents of the current PAN. Adding an individual mapping to the resource map file adds an entry to the table.
About Mapping Resources
Map PAN Resources
About Mapping Resources
On this page you can map one resource to another between a PAN archive and the current PAN. You configure these options separately:
• pBlades
• Disks
• Eths
• Tapes
The mapping for each resource displays in the individual resource areas.
Clicking Apply...
After you have finished mapping each type of resource, clicking Apply at the top of the page saves your changes and returns you to the PAN Archive archive_name page.
Clicking Reset...
1-1
Book Title
The Clear mapping dialog box allows you to cancel any mappings you have specified in this session.
Clicking Upload Map File...
The Upload mapping file dialog box allows you to clear the current mappings and replace them with the mapping file. Uploading a map file does not apply it immediately. You can still modify these mappings before applying them.
Clicking Save Map File...
The Opening resourceMap.xml dialog box allows you to save the file or open and edit it.
Learn more about specific areas of this page:
• Archive Validation Result
• Options
• pBlades
• Disks
• Eths
• Tapes
Archive Validation Result
This area tells you whether or not the archive is valid and eligible for swapping. The validation process determines whether the configuration settings in the PAN archive map correctly to those in the current PAN. Validation occurs during resource mapping (validation warnings are suppressed during resource mapping), during PAN swapping, or when specified by running the pan -v command.
1-2
Options
This area of the Resource Mapping for Archive archive_name page lets you specify the options for mapping. It contains the following check boxes:
Map SAN devices (disk and tapes) by unique ID
If selected, PAN Manager maps disks in the PAN archive to disks in the current PAN, based on unique IDs.
If selected, PAN Manager maps tapes in the PAN archive to tapes in the current PAN, based on unique IDs.
Delete Invalid rEths
If selected, indicates that you want to eliminate invalid rEth settings contained in the PAN archive.
If the platform to which you are importing the PAN archive contains fewer Ethernet interfaces than are listed in the PAN archive, the PAN archive likely contains redundant Ethernet (rEth) configuration settings that will not be preserved when the PAN archive is swapped in.
pBlades
This area of the Resource Mapping for Archive archive_name page lets you compare and, if necessary, map pBlades in the PAN archive with pBlades in the current PAN.
If mapping already exists, the following fields are shown:
Archive
A pBlade resource in the PAN archive.
Current PAN
A pBlade resource in the current PAN that maps to the pBlade resource in the PAN archive.
1-3
Book Title
Adding pBlade mapping to the resource map file adds another entry to this area.
Clicking Add...
The Add Blade Mapping dialog box lists all Processing Blades in the PAN and in the PAN archive. In this dialog box you can add multiple pBlade mappings at once. This dialog box contains the following fields:
Archive
A pBlade resource in the PAN archive.
Current PAN
A pBlade resource in the current PAN that maps to the pBlade resource in the PAN archive.
Clicking Remove...
The Remove Blade Mapping dialog box lists the current mapping of pBlades. The dialog box contains the following fields:
Archive
A pBlade resource in the PAN archive.
Current PAN
A pBlade resource in the current PAN that maps to the pBlade resource in the PAN archive.
Disks
This area of the Resource Mapping for Archive archive_name page lets you compare and, if necessary, map disks in the PAN archive with disks in the current PAN.
If mapping already exists, the following fields are shown:
Archive
1-4
A disk resource in the PAN archive.
Current PAN
A disk resource in the current PAN that maps to the disk resource in the PAN archive.
Adding disk mapping to the resource map file adds another entry to this area.
Clicking Add...
The Add Disk Mapping dialog box list all of the disks in the archive and the current PAN. In this dialog box you can add multiple disk mappings at once. This dialog contains the following fields:
Archive
This scroll list displays the device ID and Unique ID for each disk resource listed in the PAN archive.
Current PAN
This scroll list displays the device ID and Unique ID for each disk resource listed in the current PAN.
Clicking Remove...
The Remove Disk Mapping dialog box lists the current mapping of disks. The dialog box contains the following fields:
Archive
A pBlade resource in the PAN archive.
Current PAN
A pBlade resource in the current PAN that maps to the pBlade resource in the PAN archive.
1-5
Book Title
Eths
This area of the Resource Mapping for Archive archive_name page lets you compare and, if necessary, map the Ethernet interfaces in the PAN archive with the Ethernet interfaces in the current PAN.
Eths are on the cBlade.
If mapping already exists, the following fields are shown:
Archive
An eth resource in the PAN archive.
Current PAN
A eth resource in the current PAN that maps to the eth resource in the PAN archive.
Adding eth mapping to the resource map file adds another entry to this area.
Clicking Add...
The Add Eth Mapping dialog box list all of the eths in the archive and the current PAN. In this dialog box you can add multiple eth mappings at once. This dialog box contains the following fields:
Archive
This scroll list displays each Ethernet interface (eth) listed in the PAN archive.
Current PAN
This scroll list displays each Ethernet interface (eth) listed in the current PAN.
Clicking Remove...
1-6
The Remove Eth Mapping dialog box lists the current mapping of eths. The dialog box contains the following fields:
Archive
An eth resource in the PAN archive.
Current PAN
An eth resource in the current PAN that maps to the eth resource in the PAN archive.
Tapes
This area of the Resource Mapping for Archive archive_name page lets you compare and, if necessary, map tape devices in the PAN archive with tape devices in the current PAN. (The parameters are identical to those for mapping SCSI disk devices, as described in the previous section.)
Map PAN Resources
Use the following PAN Manager procedure to map PAN resources:
Mapping PAN Resources
1-7
Book Title
1-8
Managing PAN Access
(Security)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the PAN Security page:
PAN Manager system access control is based on the software’s users and the roles that they are assigned. After creating a PAN Manager user, you can assign one or more roles to the user, depending upon what type of access the user needs, and which system objects they will access.
Security: A Brief Overview
About Managing Users and Roles
Manage PAN Manager Users and Their Roles
Manage PAN Manager Users and Their Roles (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
Security: A Brief Overview
PAN Manager controls access to the physical and virtual objects in the system, based on the privileges granted to a user and the security domain of the object being accessed. The following are the three security domains:
• PAN -- Includes all objects in the entire Processing Area Network (PAN): all resources, users, and LPANs.
• LPAN -- Includes only the objects within a single LPAN: its resources and pServers.
1-1
Book Title
The only role associated with the entire PAN security domain as a whole is Administrator; for LPAN security domains, PAN Manager automatically creates three predefined static roles:
• Administrator -- Configures (creates, edits, and deletes), controls (starts and stops), and monitors (observes) the objects in the given security domain.
• Operator -- Controls (starts and stops) and monitors (observes) the objects in the given security domain, but cannot configure (create, edit, or delete) those objects.
• Monitor -- Can only monitor (observe) objects in the given security domain.
You cannot modify the predefined roles.
PAN
At this broad PAN level:
• A PAN Administrator can configure, control, and monitor a PAN’s objects.
Example: Set up and configure multiple LPANs.
LPAN
When setting up a specific LPAN, the PAN Administrator assigns each predefined role for that LPAN to a specific user:
• An LPAN Administrator can configure, control, and monitor a specific LPAN’s objects.
Example: Set up and configure this LPAN.
• An LPAN Operator can control and monitor a specific LPAN’s objects.
Example: Start and stop any LPAN or component in this LPAN.
• An LPAN Monitor can monitor only a specific LPAN’s objects.
1-2
Example: Observe the status of this LPAN or any of its components.
About Managing Users and Roles
The PAN Security page lets you manage PAN Manager user accounts, the security roles associated with those accounts, and the Linux user groups (on the Control Blades) to which users can belong.
Learn more about specific areas of this page:
• Users
• Security Roles
• System User Groups
Users
This area of the PAN Security page lets you manage PAN Manager user accounts, and their associated Linux system accounts (on the Control Blades).
Clicking Create...
The Create new User dialog box displays the following headings and fields:
User Name
The name that the user will use to log on to PAN Manager.
Full Name
The user’s actual full name.
Title
The user’s title within your organization.
Department
The user’s department name.
1-3
Book Title
The user’s e-mail address.
Password and Confirm
(Required) The password with which this user will log on to PAN Manager. (Only root can modify root’s password.)
System Account
System account information is configurable only if PAN Manager is currently configured to manage system user accounts. If the check box is selected, you can create a new operating system account on the Control Blades for the user. (The PAN Manager user name and its associated operating system account will be identical.) If the new PAN Manager user already has an operating system account on the Control Blades, the characteristics of that existing user account (user ID, group ID, home directory, and default shell) remain unchanged.
Note: Although PAN Manager lets you manage Linux user accounts on the Control Blades, using it for this purpose prevents you from using other account management utilities to manage those accounts. This is important to note if, for example, you are accustomed to using a user management tool to manage existing user accounts in an external database.
Roles
Allows to you assign one or more PAN Manager security roles to a PAN Manager user.
In order for a PAN Manager user to log on, you must assign a security role. For information about the available roles from which to choose, see Security: A Brief Overview.
Select Role
Lists all existing PAN Manager security roles in the PAN.
Assigned Roles
Lists the PAN Manager security roles currently selected for the PAN Manager user. Clicking Submit saves your selections.
1-4
Clicking Delete...
The Delete Users dialog box lists all PAN Manager user accounts, and lets you delete one or more user accounts and (optionally) their associated operating system accounts. The following fields appear:
User Name
The name of the PAN Manager user account.
Assigned Roles
The PAN Manager security role(s) assigned to the PAN Manager user account.
Delete system account for each selected user
If selected, removes (for each PAN Manager user account selected) the Linux operating system user account on the Control Blades.
Recursively
If selected, deletes the user’s home directory on the Control Blades.
Security Roles
This area of the PAN Security page lists all PAN Manager security roles in the PAN: the PAN Administrator and the three roles (also Administrator, Operator, and Monitor) associated with each existing LPAN.
Clicking Assign...
The Assign Roles dialog box lets you manage which PAN Manager users are assigned a particular security role. Each heading is a security role; click a heading to expand its contents.
User Name
Lists all PAN Manager users. A checkmark indicates that a user has this particular security role.
1-5
Book Title
System User Groups
System user groups are configurable only if PAN Manager is currently configured to manage system user accounts. This area of the PAN Security page is visible only if system user groups are configurable.
This area of the PAN Security page lets you manage the Linux operating system groups (on the Control Blades) to which PAN Manager users may belong. You can create a new group, or change a PAN Manager user’s group (by default, a user is assigned to the users operating system group). You cannot delete a group that contains members. PAN Manager can manage one group for each user.
Clicking Create...
The Create new User Group dialog box lets you enter the name of the new Linux operating system group. Linux automatically assigns a group ID to the group name that you specify.
Clicking Delete...
The Delete User Groups dialog box lists all operating system groups on the Control Blades, by group name and group ID (GID), and lets you delete one or more groups. You can delete a group only if it contains no members.
Manage PAN Manager Users and Their Roles
Use the following PAN Manager procedures to manage PAN Manager users, their PAN Manager security roles, and the operating system user and groups associated with PAN Manager users:
Creating Users and Accounts
Deleting Users and Accounts
Assigning Roles to Users
1-6
Creating User Groups
Deleting User Groups
Manage PAN Manager Users and Their Roles (CLI)
Use the following PAN Manager commands to manage PAN Manager users, their PAN Manager security roles, and the operating system user and groups associated with PAN Manager users:
account -- Creates, lists, or modifies a user’s Linux account on a Control Blade.
role -- Lists the roles within the PAN or an LPAN.
user -- Creates or modifies attributes, including role assignments, for each PAN Manager user.
1-7
Book Title
1-8
Modifying a PAN Manager User
On the User username page:
This page displays the details of a PAN Manager user profile, and lets you modify the information.
About Editing a PAN Manager User
Edit a PAN Manager User
Edit a PAN Manager User (CLI)
About Editing a PAN Manager User
This user profile was created by the PAN Administrator.
Clicking Modify...
The Modify PAN Manager User dialog box lets you edit a PAN Manager user’s full name, title, department, and email address.
Clicking Change Password...
The Change User Password dialog box lets you reset a user’s PAN Manager password. The dialog box has these fields:
New password
Enter the user’s new password.
Confirm new password
Reenter the user’s new password to confirm the change with PAN Manager.
This page displays the following information:
User Name
The name of the PAN Manager account.
Full Name
1-1
Book Title
The actual full name of the user.
Title
The user’s job title within the organization.
Department
The name of the user’s work department.
The user’s e-mail address, in the form [email protected].
cBlade system account information for this user
This area displays the Linux user account information associated with a PAN Manager user.
User ID
The Linux user ID of the user.
Group
The user’s group.
Shell
The full pathname of the user’s shell.
Home Dir
The full pathname of the user’s home directory.
Clicking Modify...
The Modify cBlade System Account dialog box lets you change the Linux user account information associated with a PAN Manager user:
Clicking Delete...
The Delete cBlade System Account dialog box lets you delete the cBlade Linux user account information for a PAN Manager user.
1-2
To use PAN Manager, a user must have an underlying Linux system account on the cBlade. Deleting this account prevents the user from using PAN Manager.
Delete all traces of account on cBlades (including home directory)
Selecting this check box also removes the files and directories on the cBlade that support the user’s system account.
Security Roles
This area displays the PAN Manager administrative roles assigned to this user.
Clicking Assign/Unassign...
The Assign/Unassign Security Roles dialog box displays the list of roles available for this user.
Edit a PAN Manager User
Use the following PAN Manager procedure to edit the attributes for a PAN Manager user:
Modifying Users and Accounts
Edit a PAN Manager User (CLI)
Use the following PAN Manager command to edit the attributes for a PAN Manager user:
user -- Creates or modifies attributes, including role assignments, for each PAN Manager user.
1-3
Book Title
1-4
Editing Your PAN Manager User Profile
On the username profile page:
This page displays the details of your PAN Manager user profile, and lets you modify parts of it.
About Editing Your PAN Manager User Profile
Edit Your PAN Manager User Profile
Edit Your PAN Manager User Profile (CLI)
Tip: Hovering over your user icon displays additional information; click the icon to freeze the display.
About Editing Your PAN Manager User Profile
This page lets you change your PAN Manager user information. This user profile was established for you by your PAN Administrator. (Your PAN Manager username appears at the top of the left pane.)
If PAN Manager is not configured to manage user accounts, you can still modify your password. To modify other portions of your PAN Manager user profile, contact your PAN Administrator.
Roles
(Read-only) Lists the PAN Manager administrative roles that the PAN Administrator assigned to you.
Full Name
Your actual full name.
Your e-mail address, in the form [email protected].
Title
1-1
Book Title
Your job title within your organization.
Department
The name of your work department.
Change Password
This area is visible only if PAN Manager is configured to manage user passwords. If the message External control of system accounts is enabled. PAN Manager cannot change passwords appears, and you want to change your password, contact your PAN Administrator.
Current
The password with which you log on to PAN Manager.
New and Confirm New
The password you want to use to log on to PAN Manager.
Edit Your PAN Manager User Profile
Use the following PAN Manager procedure to edit the attributes for a PAN Manager user:
Managing Users and Accounts
Edit Your PAN Manager User Profile (CLI)
Use the following PAN Manager command to edit the attributes for a PAN Manager user:
user -- Creates or modifies attributes, including role assignments, for each PAN Manager user.
1-2
Platforms
This section of the PAN Manager GUI Guide provides descriptions for viewing and managing platforms. Topics include:
• Viewing Platforms
• Managing a Platform
• Managing Domain Settings
• Configuring a Power Input Module
• Events and Monitors
1-1
Book Title
1-2
Viewing Platforms
(Platforms)
On the Platforms page:
This page presents a graphical view of all processing resources available within the entire Processing Area Network (PAN). A PAN is a distributed set of resources including processors, network connections, and external storage devices that can be configured into servers.
About Viewing Platforms
View Information About a Platform (CLI)
Tip: Hovering over the Platform icon displays additional information; click the icon to freeze the display.
About Viewing Platforms
You can view the Platforms page to display all the systems in the PAN. (If you have only one system, only one appears.) To examine the characteristics of a specific platform, click its name.
View Information About a Platform (CLI)
Use the following PAN Manager command to view information about a specified platform or the PAN:
bframe -- Lists hardware and configuration information about a specified platform.
1-1
Book Title
1-2
Managing a Platform
(Platforms >platform_name)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Only your PAN Administrator can perform some configuration tasks.
On the Platform platform_name page:
This page displays a photo-realistic view of the platform, and provides information about its cBlades, pBlades, sBlades, and vBlades and power configuration settings.
About Platform Systems
Controls for Managing the Platform
Configure Management Settings for the Platform
Configure Management Settings for the Platform (CLI)
Tip: Hovering over the Platform icon displays statistics about platform components.
On the BladeFrame BF400 S2, in the Power Domains area, hovering over a power domain highlights the platform components that belong to that power domain.
About Platform Systems
This page displays the primary resources of an entire platform security domain. This security domain includes only the objects associated with a single platform system. This page provides a comprehensive view of the platform system’s pBlades, cBlades, sBlades, and vBlades and the power these resources are consuming.
Clicking Edit...
The Edit Platform dialog box lets you rename the platform.
1-1
Book Title
Clicking Power...
On the BladeFrame BF400 S2, if you have a platform with PIM-Rs, the Power Configuration dialog box displays the following fields:
Voltage
The Voltage of your BladePlane.
Amperage
The Amperage of your BladePlane. You cannot modify amperage when using PIM-Rs.
Voltage Trigger
The minimum value at which the voltage can drop to before causing the PIM to fail over.
If you have a platform without PIM-Rs, the Power Configuration dialog box displays the following fields:
Voltage
The Voltage of your BladePlane.
Amperage
The Amperage of your BladePlane.
Clicking Network...
The Platform Network Configuration dialog box displays the following headings and fields:
External Management Network Settings
The external management network provides PAN Manager communication between platforms in a PAN.
PAN-wide Settings
Broadcast
The broadcast address of your site’s management network.
Netmask
1-2
The network mask of your site’s management network.
Gateway
The gateway address of your site’s management network.
Platform specific IP settings
Frame Master
The IP address used to access the PAN Manager software on this master cBlade of this platform.
cBlade 1
The IP address of the bottom cBlade in this chassis.
cBlade 2
The IP address of the top cBlade in this chassis.
External Management Discovery Settings
External multicast group
The IP address on which applications on your site’s management network communicate.
External multicast port
A specific service within the multicast group.
Internal Platform Network Settings
The internal management network provides PAN Manager communication within a platform.
Subnet
The subnet of the internal management network specific to this platform.
Broadcast
The broadcast IP address of the internal management network.
1-3
Book Title
Netmask
The network mask of the internal management network.
Clicking Leave PAN...
The Leave this PAN dialog box allows you to remove the selected platform from its current PAN.
Clicking Platform ID...
The Edit Platform ID dialog box displays the current Platform ID.
The following are the platform areas on this page:
• Platform platform_name
• Power Domains
Platform platform_name
(located in the top banner) The name of the platform that you designate.
Tip: Hovering over a blade highlights its information in the table; likewise, hovering over a table row highlights the physical location of the blade. Click the blade icon to freeze the display.
Slot
The physical location of the blade in the chassis.
Some slots might be empty, depending on whether your chassis is fully populated.
Tip: The color of the slot number indicates the health status of the blade; clicking a slot number displays the statistics for that blade.
1-4
Status
The current boot status of the blade:
An Up arrow indicates that the blade is booted.
A Down arrow indicates that the blade is shutdown.
Tip: If additional symbols appear in this field, hover over the field to learn the details.
LPAN/pServer
The LPAN (if any) and pServer (if any) in which the blade is being used and if there is a vBlade defined.
Uptime
In the format days hours:minutes (such as 30d 17:34), indicates how long a booted blade has been running.
Events
The current number of three categories of unresolved events associated with the blade:
High-severity events (levels 1 and 2)
Medium-severity events (levels 3 and 4)
Low-severity events (levels 5 and 6)
Power Domains
On the BladeFrame BF400 S2, this shows the power settings and power usage for this platform.
Important: Before updating these settings, be sure that the new settings reflect the physical properties of the platform.
Tip: Hovering over a power domain highlights the platform components that belong to that power domain.
1-5
Book Title
Spine is rated for...
The configured amperage and voltage of the platform BladePlane (or spine). Changing the amperage to 30 requires that the four power domains be separate.
Voltage settings indicate the configured voltage of the platform power supply: 200 (default), 208, or 230.
Power Domain Configuration
If each power domain has its own power source (the default), each power domain appears by itself; if the power domains are paired (A and C combined; B and D combined), each pair shares a power source.
Displays the following statistics (in Watts) for each of the four power domains (A, B, C, and D):
Used Power/Standby Power/Free Power/(Total)
Used Power (blue)
Power being used by booted blades.
Standby Power (gold)
Power that would be used if blades in standby mode were booted.
Used power + Standby Power = Attached Power
Standby Power (red)
When Attached Power exceeds the allowed total capacity, PAN Manager will not allow all blades in this power domain to boot.
Free Power (gray)
Any unused power in a power domain. This usually indicates that there are empty blade slots in the platform.
Total (black)
The power capacity of the power domain.
1-6
The values shown are the maximum possible values. PAN Manager uses these values to calculate the total possible power consumption of the platform. The actual power consumption will fluctuate and may be less at any given time.
If you have a platform with Redundant Power Input Modules (PIM-Rs), clicking or hovering over the PIM-R icon displays the PIM-R’s current configuration. Clicking on the name of the PIM-R allows you to modify the Power Input Module configuration settings.
Controls for Managing the Platform
The bottom border of the Platform platform_name page contains controls (Reboot and Shutdown) for managing an entire platform.
Because shutting down the platform terminates the PAN Manager software on which it runs, you cannot use PAN Manager to boot the platform from a shutdown state; you must have physical access to the platform in order to restore its power manually. After PAN Manager starts, you must reconnect to PAN Manager.
Reboot
Causes the cBlades and pBlades to shut down, to boot-load their operating systems, and to run their initialization scripts.
Shutdown
Causes the cBlades and pBlades to be shut down and powered off. Be sure that you have physical access to the platform before shutting it down.
Configure Management Settings for the Platform
The following procedures are required to initially set up your Platform:
Naming the Platform
Configuring Power for Platforms Without PIM-Rs
1-7
Book Title
Displaying Available Application Templates
Disabling the Manual Power Preference Button
Specifying the Preferred Power Cord
Specifying the Event Trigger Limits
Modifying Internal and External Management Settings
Rebooting a Platform
Shutting Down a Platform
Warning: Because shutting down the platform terminates the PAN Manager software on which it runs, you cannot use PAN Manager to boot the platform from a shut down state; you must have physical access to the chassis in order to restore its power manually. After the PAN Manager software starts, you must reconnect to the PAN Manager software.
These procedures assume the following:
• The platform has been installed, populated with blades, and tested by Fujitsu Siemens Computers customer support or your authorized support vendor.
• The platform is configured to access your network and Storage Area Network (SAN).
• The platform has not been renamed from the default name, MyPlatform. If it has, the new name shows up in the left pane as Platforms > MyPlatform.
If you have questions about any of these procedures, contact Fujitsu Siemens Computers customer support or your authorized support vendor.
Configure Management Settings for the Platform (CLI)
Use the following PAN Manager commands to configure management settings for the platform:
bframe -- Lists hardware and configuration information about a specified platform.
1-8
blade -- Lists or controls manual diagnostic tools on a specified Control Blade, Processing Blade, and sBlade (or cBlade switch).
snmp -- Lists or modifies the configuration for a Simple Network Management Protocol (SNMP) agent that supports PAN Manager.
snmpmgr -- Lists or modifies the configuration for a Simple Network Management Protocol (SNMP) manager.
user -- Creates or modifies attributes, including role assignments, for each PAN Manager software user.
1-9
Book Title
1-10
Managing Domain Settings
(PAN_name > Domain Settings)
(LPAN_name > Domain Settings)
PAN Manager system access control spans domains. Domains are predefined administrative areas. A Processing Area Network (PAN) consists of a PAN domain and at least one LPAN domain. The PAN domain includes all objects in the entire PAN: all resources, users, and LPANs. The LPAN domain includes only the objects within a single LPAN: its resources and pServers.
PAN Manager displays a Domain Settings page for each available domain. The settings configured on this page apply only to the specified domain. Only the appropriate administrator can see the Domain Settings page for his or her domain (an LPAN Administrator can only access the Domain Settings page for his or her LPAN). However, the PAN Administrator can access the Domain Settings page for every domain in the PAN.
The PAN domain settings become the default settings for the LPAN domain. Each LPAN Administrator may override the default settings for their domain.
On the Domain Settings page:
About Domain Settings
Manage Domain Settings
Manage Domain Settings (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Domain Settings
The Domain Settings page lets you manage settings for the selected domain, PAN or LPAN.
1-1
Book Title
Learn more about specific areas of this page:
• Event Settings
• SNMP Agent
• SNMP External Managers
• Users
Event Settings
This area of the Domain Settings page lets you specify the default event action to be executed upon an event’s occurrence.
Clicking Event Settings...
The Configure Event Settings dialog box lets you determine how PAN Manager will respond when it encounters an event of any type in the security. You can determine the type of notification that PAN Manager sends when it encounters an event (e-mail and/or an SNMP trap), and the minimum severity of the event that generates the notification. (Severity ranges from 1 to 6, where 1 is the most severe.)
These settings represent the default actions for the PAN or LPAN security domain. The Administrator can also customize the following settings for a specific event type. The following fields appear:
Send Email notification to:
The e-mail address(es) of the person or group to which PAN Manager sends system messages about events. If you specify multiple addresses, delimit them with commas.
SNMP
If selected, indicates that an SNMP agent generates an SNMP trap on behalf of the entity that is reporting an event.
Minimum Severity
A threshold that defines the condition that caused the event. The pull-down list provides severity values from 1 (most severe) to 6 (least severe).
1-2
SNMP Agent
This area of the Domain Settings page defines the characteristics of an SNMP agent: whether the agent is enabled, how to contact the agent, whether the agent can invoke management operations, and the set of authorized SNMP managers that can access the agent.
If an SNMP agent allows an operation (read or write), the SNMP manager must be listed as an authorized manager, and provide the correct SNMP agent community string in order to invoke the operation. If an SNMP agent disallows an operation, no SNMP manager can invoke the operation on the agent.
Clicking SNMP Agent...
The Configure SNMP Agent Settings dialog box lets you configure the SNMP Agent. The following fields appear:
Operational Status: (Active or Inactive)
Indicates whether the LPAN’s SNMP agent is currently functioning. The agent is not active if one or more of the following is true:
— Its IP address is 0.0.0.0.
— Its port number is 0.
— Its scope is set to Disable.
IP Address
The external management IP address on which an SNMP agent listens for requests.
Port
The user datagram protocol (UDP) port of the external management IP address on which an SNMP agent listens for requests.
Contact
The person who manages this security domain, and how to contact them (such as phone number or e-mail address).
1-3
Book Title
Location
The physical whereabouts of the system object being monitored.
Community Strings
Community strings authenticate SNMP managers and enforce the access policy for each SNMP agent. Each SNMP agent requires a single read community and a single read-write community. The following are default values, as shipped:
Read -- 'public'
Write -- 'private'
To invoke an operation on any entity represented by the SNMP agent, an SNMP manager must provide the correct community string.
(An SNMP agent can reject SNMP requests from SNMP managers who specify an incorrect community string.)
Scope
Setting the scope of control determines to what extent SNMP managers can use SNMP to manage the LPAN. The following are the three possible settings:
Disabled
Disables all SNMP management in the LPAN.
Monitor
Allows authorized SNMP managers only to read information from the SNMP agent.
Monitor and Control
Allows authorized SNMP managers to read information from the SNMP agent, and to have the SNMP agent perform SNMP set operations on their behalf.
1-4
SNMP External Managers
This area of the Domain Settings page displays the available SNMP managers.
SNMP managers (also known as SNMP management stations) can monitor and control system entities, and receive trap messages from these entities, depending on the access provided to them by the PAN Administrator.
Configuring an external SNMP manager for the security domain determines whether an SNMP manager can monitor and control the domain, or receive SNMP traps from the SNMP agent for that domain.
Clicking Add...
The Add new SNMP External Manager dialog box displays the following fields:
IP Address
The IP address of an authorized SNMP manager. (PAN Manager ignores SNMP requests from managers that are not listed in the External Managers table.)
Netmask
The netmask associated with the IP address of the SNMP manager. The netmask effectively allows an administrator to authenticate either a specific host or an entire group of hosts.
Trap port
Specifies a port number on which the SNMP manager receives trap messages from the LPAN’s SNMP agent. The default is 0, which means that the trap port is unable to receive traps.
Community String
The PAN agent must specify this community string when sending trap messages to the SNMP manager. If the PAN
1-5
Book Title
agent specifies an incorrect community string, the SNMP manager can reject traps sent by the PAN agent. The default community string is public.
Trap Version
The version of SNMP software, either SNMP v1 (default) or SNMP v2c, which determines the trap format that the SNMP manager uses.
Clicking Delete...
The Delete SNMP External Manager dialog box displays the list of all configured SNMP Managers and allows you to delete a Manager by selecting the check box.
Clicking Modify...
The Modify SNMP External Manager dialog box displays a list of all configured SNMP Managers. Click on an SNMP Manager to expand the heading a display configuration information about that manager.
Users
This area of the page lists all of the PAN Administrators. The PAN domain only support users in the Administrator role. The PAN Administrator has complete control over all objects in the PAN. Be selective in assigning the PAN Administrator role to PAN Manager users.
Clicking Add...
The Assign User to Domain dialog box lets you select a user to be assigned to the PAN Administrator role. The dialog box contains the following field:
User
The users recognized by the PAN Manager system are available in a drop-down list.
1-6
Clicking Unassign...
The Unassign a User from Domain dialog box lets you remove a user from the PAN Administrator role. This does not remove the user from the PAN Manager system. This dialog box displays the following information:
User
The username of the person currently assigned to the PAN Administrator role.
Current Role in Domain
The name of the role currently assigned to the user.
Manage Domain Settings
Use the following PAN Manager procedures to manage the PAN domain settings:
Configuring the Domain
Configure the SNMP Agent(s)
Configure the SNMP Manager(s)
Assigning Roles to Users
You must have the PAN Administrator role to perform these tasks.
Manage Domain Settings (CLI)
Use the following PAN Manager commands to manage the PAN domain settings:
pan -- Configures the default event actions for the PAN domain.
lpan -- Configures the default event actions for the LPAN domain.
snmp -- Configures the SNMP Agent settings for the PAN domain.
snmpmgr -- Adds or modifies settings for an SNMP Manager for the PAN domain.
1-7
Book Title
user-- Configures the role assigned to a PAN Manager user.
1-8
Configuring a Power Input Module
(Platforms > platform_name > PIM)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Only your PAN Administrator can perform some configuration tasks.
On the Power Input Module platform_name/PIM page:
This page shows information about the selected Power Input Module (PIM) and allows you to configure certain settings.
About Power Input Modules (PIMs)
Configure PIM Settings
Configure PIM Settings (CLI)
About Power Input Modules (PIMs)
The following are the PIM characteristics on this page:
frame_name/PIM
(Located in the top banner) The number of the selected PIM. PIMs are numbered from bottom to top.
The LED indicator of the PIM is represented by a blue or amber circle on the photo-realistic representation. An amber LED indicates that the PIM initially has been recognized by PAN Manager. A steady blue LED indicates that the PIM is fully functional and ready to transmit power. A flashing blue LED indicates that the PIM has been selected for administrative purposes.
Power Cord A or B
Each PIM has two power cords, A and B. For each power cord, the following characteristics appear:
Power cord is in active use -- Appears only if this cord is conducting power to the platform.
1-1
Book Title
Power cord is preferred -- Appears only if the cord has been configured as the preferred cord for this PIM.
Status -- Indicates whether the cord is on or off
Input voltage -- Displays the current (actual) voltage of the cord
Frequency -- Displays the current frequency of the cord
Manual power preference
Indicates whether the physical preference button on the PIM has been enabled or disabled. If the physical button is enabled, you cannot set the cord preference with PAN Manager (the options are grayed-out). If the physical button is disabled, you cannot set the cord preference with the button (it does nothing).
You can configure this setting, by clicking Configure.
Output Power (limit)
The configured limit at which PAN Manager will generate an event. This setting is configured in the Configure PIM Settings dialog box (see below).
Output Current (limit)
The configured limit at which PAN Manager will generate an event. This setting is configured on the Configure PIM Settings dialog box (see below).
Serial Number
The serial number that uniquely identifies the physical PIM.
Part Number
The product code associated with this PIM.
Firmware Revision
The version number of the firmware currently running on the PIM.
Clicking Configure....
1-2
The Configure PIM Settings dialog box contains the following fields:
Preferred Power Cord
You may select a power cord as preferred. A preferred power cord transmits power to the blades in its domain. The other cord acts as a failover cord in the case of the preferred cord reaching the failover voltage limit.
You can select a preferred power cord either by selecting a radio button here, or by pressing the physical button on the PIM.
Output Limits
Enter the desired values that will trigger PAN Manager events if the configured values are exceeded.
Power (Watts)
Enter the wattage limit for the event trigger.
Current (Amps)
Enter the amperage limit for the trigger.
Enable manual power preference button on physical device
Select this check box to use the button on the physical PIM to set the preferred power cord; clear this check box to use this PAN Manager dialog box to set the preferred power cord. You must use either the physical button or PAN Manager, but not both. Using the physical button disables the Preferred Power Cord selections in this dialog box; using PAN Manager makes the physical button inoperable.
Selecting Select/Deselect...
The Select/Deselect button lets you designate the PIM as ready for an administrative action. Clicking the button on an unselected PIM will select it. Clicking the button on a selected PIM will unselect it.
A selected PIM’s indicator light in the chassis flashes blue.
1-3
Book Title
Configure PIM Settings
Use the following procedures to configure the settings for a PIM:
Disabling the Manual Power Preference Button
Specifying the Preferred Power Cord
Specifying the Event Trigger Limits
Configure PIM Settings (CLI)
Use the following PAN Manager command to configure the settings for a PIM:
pim -- Configures the attributes of the Power Input Modules (PIMs).
1-4
Events and Monitors
This section of the PAN Manager GUI Guide provides descriptions for managing and creating events and monitors. Topics include:
• Managing Events
• Managing Event Types
• Configuring an Event Type
• Selecting and Displaying Monitor Data
• Modifying User-defined Monitors
1-1
Book Title
1-2
Managing Events
On the Events page:
Use this page to display system events that pertain to a specific physical or logical system component (such as a Control Blade or an LPAN). The events displayed are those that PAN Manager allows, based on your PAN Manager user role, and the filtering parameters that you establish.
About Managing Events
About Applying an Event Filter
Apply an Event Filter
Apply an Event Filter (CLI)
About Managing Events
This page lists events that have been generated by the logical or physical component that is now selected in the PAN Manager GUI’s left pane.
Each component is associated with a specific set of event types. When an event is generated, PAN Manager logs the event, displays the event (based on the filter parameters that you set), and invokes the actions, if any, that are associated with the event’s type.
All events are directed to log files. As new events are added to log files, older ones are purged, so the set of events that is visible in PAN Manager might change over time.
The events displayed on this page are filtered according to guidelines that you specify.
Clicking Set Filter...
The Set Event Filter dialog box lets you specify which events appear for the component that is selected in the PAN Manager GUI's left pane.
1-1
Book Title
Severity
Lets you filter the display of events by their importance. Severity ranges from 1 (most severe) through 6 (least severe):
All
Displays all events, regardless of severity.
More severe than or equal to
Displays events that equal or exceed in importance the severity that you specify. (For example, setting this value to 2 displays all events that have a severity level of 1 or 2.)
Less severe than or equal to
Displays events that are equal in importance to or less important than the severity that you specify. (For example, setting this value to 4 displays all events that have a severity level of 4, 5, or 6.)
Between (more severe or equal)and (less severe or equal)
Lets you display a range of severities, delimited by the severities that you specify. (For example, setting these values to 2 and 4, respectively, displays all events that have a severity level of 2, 3, or 4.)
ID
Lets you filter the current component’s events, by event ID number.
All
Displays all events for this component.
Less than or equal to
Displays events for which the event ID is the same or smaller than the ID that you specify.
Greater than or equal to
Displays events for which the event ID number is
1-2
the same or larger than the ID that you specify.
Between... and ...
Lets you display a range of events, delimited by the event ID numbers that you specify.
Time Stamp (mm/dd/yy hh:mm:ss)
Lets you filter the display of events, by when they occur, down to the level of granularity of one second.
All
Displays all events, regardless of when they occur.
After or at
Displays all events that occur on or after a specific date and time.
Before or at
Displays all events that occur on or before a specific date and time.
Between... and ...
Displays a range of events, delimited by the dates and times that you specify.
Status
Lets you filter the current component’s events by their current investigation state:
All
Displays events of all status types: Open, Investigating, and Resolved.
Open
Displays only the events that are currently open.
Investigating
Displays only the events that are currently under investigation.
Resolved
1-3
Book Title
Displays only the events that are resolved.
Event Message Contains
Displays only the events whose descriptions contain the string that you specify.
Clicking Resolve Events...
Lets you toggle the status of all events for the current component to Resolved.
Clicking Event Types...
Opens the Managing Event Types page. Displays a one-line summary for each possible event associated with the current component.
Event Blocks
The Event Blocks area provides links to one or more pages of the list of events displayed for the current component, and shows the number of events (and their severity level) in each page. The current page number appears in bold. (In a multipage listing, the most recent events appear in the bottom screenful on the highest page number.)
ID
(Read-only) A unique identifier that PAN Manager assigns to an event instance.
Severity
(Read-only) The severity level of the event, as follows:
1 = Critical2 = Error3 = Warning
1-4
4 = Unusual5 = Information6 = Debug
Events of severity 1 or 2 display a red health light.
Events of severity 3 or 4 display a yellow health light.
Events of severity 5 or 6 display a green health light.
Status
The current investigation status of this event: open, resolved, or investigating.
User
The name of the PAN Manager user that generated the event. (Events that PAN Manager generates have the user name system.)
Time
(Read-only) The time (to the granularity of a second) at which PAN Manager received the event from the component’s SNMP agent.
Type ID
A preset identifier for this specific type of event. To view the details about a single event instance, click the event instance's identifier in this column.
Message
(Read-only) A brief description of the event.
1-5
Book Title
About Applying an Event Filter
This page displays the current parameters that are reducing the number of events being displayed for this component. A value of none indicates that all events for the current component are displayed.
Status
The current status of the event, as follows:
Open (O)
Investigating (I)
Resolved (R)
To change an event’s status, click the icon.
Message
A brief description of the event.
Apply an Event Filter
Use the following PAN Manager procedures to filter a list of event instances on a platform system or to modify the status of a specific event:
View the Event Instance Details
Apply a Filter and View a List
Update the Event Instance Status
Apply an Event Filter (CLI)
Use the following PAN Manager command to filter a list of event instances on a platform system or to modify the status of a specific event:
event -- Lists the details of an instance of a triggered event on a platform.
1-6
1-7
Book Title
1-8
Managing Event Types
On the Event Types page:
Each logical or physical component in the PAN is associated with a specific set of event types. This page lists each event type associated with the component that is currently selected. Each event type has a predetermined name, description, and severity.
You can configure what action(s) PAN Manager will take, if any, if it encounters an event instance of a certain type. To associate an event type with one or more actions, click the Name of the event type.
To list all event occurrences for the current component, click the Events button.
You can also list a component’s event types by using a PAN Manager command.
The following are characteristics of an event type:
ID
A preset identifier for this specific type of event.
Severity
The seriousness of an event of this type (1 through 6; 1 is the most severe).
Name
A brief summary of a type of event.
Description
1-1
Book Title
The circumstances under which PAN Manager generates an event of this type.
1-2
Configuring an Event Type
On the Event Type page:
An event type is a category of events that is associated with a specific logical or physical component in the PAN. This page describes a single event type, and lets you configure the action(s) that PAN Manager takes when it encounters an event of this type.
About Event Type
Configure an Event Type
Configure an Event Type (CLI)
About Event Type
Each logical or physical component in the PAN is associated with a specific set of event types. This page describes a single event type associated with the component that is currently selected in the PAN Manager GUI's left pane.
Learn more about specific areas of this page:
• Field Descriptions
• Hardware/Software Monitor Threshold
• Actions
Field Descriptions
An event type has the following characteristics:
Name
(Read-only) A brief summary of the current event type.
ID
A preset identifier for this specific type of event.
1-1
Book Title
Description
(Read-only) The circumstances under which PAN Manager generates an event of this type.
Severity
(Read-only) The seriousness of an event of this type (1 through 6; 1 is the most severe).
Hardware/Software Monitor Threshold
(Read-only) The threshold at which PAN Manager generates an event of this event type.
Actions
The responses that PAN Manager makes to an event of this event type.
PAN Level, LPAN LPAN Level, or Platform platform_name Level
(PAN Administrator only) The security domain for which there are default and custom event actions configured.
(The PAN security domain encompasses all logical and physical resources in all LPANs. An LPAN security domain encompasses all the logical and physical resources of a single LPAN.)
Default Actions
Indicates which actions that the administrator for a security domain (the PAN or an LPAN) has specified for all events generated in the security domain.
If specified, the e-mail address of the person or group to which PAN Manager sends an e-mail message about any
1-2
event in the security domain. (The default behavior is not to send e-mail messages in response to an event.)
SNMP Trap
A checkmark indicates that an SNMP agent generates an SNMP trap on behalf of any component in the security domain. (The default behavior is to send a trap in response to an event.)
Custom Actions
The actions PAN Manager takes (to send an e-mail message or an SNMP trap) when it encounters events of this particular type.
If specified, the e-mail address of the person or group to which PAN Manager sends an e-mail message about events of this type.
SNMP Trap
A checkmark indicates that an SNMP agent generates an SNMP trap on behalf of the component that is reporting an event of this type.
Configure an Event Type
Use the following PAN Manager procedures to modify (overriding the default event action for a security domain) the actions for a specific event type:
Configure the Trigger(s) for a Monitor
Configure and Enable the Event Action(s) for an Event Type
You can customize a single event type action that differs from the default event action and notification for all events within the security domain.
1-3
Book Title
Configure an Event Type (CLI)
Use the following PAN Manager command to modify (overriding the default event action for a security domain) the actions for a specific event type:
eventtype -- Lists or modifies the event types monitored on a platform
Use the following PAN Manager command to modify the triggers for a specific system monitor (hardware monitors are noneditable):
mon -- Lists or modifies the monitors for a pServer.
1-4
Modifying User-defined Monitors
On the User Monitor monitor page:
Use this page to modify previously defined monitors. User-defined monitor resources are a collection of attributes that allows you to create a set of health, status, or statistical monitors whose events you can use to enhance control over PAN Manager behavior.
About Modifying Monitors
Modifying User-defined Monitors
Modifying User-defined Monitors (CLI)
About Modifying Monitors
This page lets you change characteristics of individual monitors.
Learn more about specific areas of the page:
• Rules
• Service Assignments
Clicking Modify...
The Edit monitor dialog box lets you modify the action of a user-defined monitor:
Name
The name of the monitor.
Description
A brief identifying note about the monitor.
Executable
Enter the full pathname (on the pServer) of the command that this user-defined monitor runs (for example, an executable script that runs the application that monitors your service(s)).
1-1
Book Title
Data Unit
The units in which the monitor reports its data. This label appears on this monitor's charts and graphs.
Frequency (seconds)
The interval, in seconds, in which the monitor reports its data. Use an integer with a minimum value of ten.
Start Up Delay (seconds)
The time, in seconds, that the monitor waits before beginning to report data about its associated object. (Setting an appropriate time delay allows the object’s initialization process to complete, preventing the monitor from reporting bogus errors.)
Each monitor is defined by the following characteristics:
Name
The name of the monitor.
Executable
The full pathname (on the pServer) of the monitor’s executable program. (If the user monitor was generated from a monitor template, the executable file’s pathname begins with /opt/panmgr/templates/template_tag.)
Data Unit
The units in which the monitor reports its data.
Frequency (sec.)
The interval, in seconds, in which the monitor reports its data.
Start Up Delay (sec.)
The time, in seconds, that the monitor waits before beginning to report data about its associated object.
1-2
Rules
This area of the User Monitor monitor page lets you view and establish rules for the monitor.
Clicking Create...
The Create Rule dialog box lets you define the action (failover or restart) that PAN Manager performs on the system object associated with the monitor. This dialog box contains the following fields:
Name
The name of the rule that you are specifying.
Operator
A Boolean symbol that sets the threshold for the values that the monitor reports:
> greater than
> = greater than or equal to
< less than
< = less than or equal to
= = equal to
! = not equal to
Value
Specifies an integer indicating the value that the returned monitor value will be compared against.
Severity
The seriousness of the event that PAN Manager generates when the rule is met.
Action
(This field appears only when an application service is selected in the PAN Manager left pane).
Lets you associate an action (either failover or restart) that
1-3
Book Title
PAN Manager takes (on the system object associated with the monitor) in response to a rule.
Clicking Delete...
The Delete Rule dialog box lets you remove a rule from the monitor. This dialog box contains the following field:
Name
The name of the rule that you want to delete.
Clicking Modify...
The Modify Rule dialog box lists all of the established rules. Click a rule to expand it to see the following fields:
Name
The name of the rule that you are modifying.
Operator
A Boolean symbol that sets the threshold for the values that the monitor reports:
> greater than
> = greater than or equal to
< less than
< = less than or equal to
= = equal to
! = not equal to
Value
The number of Data Units that the monitor must report before the rule is met.
Severity
The seriousness of the event that PAN Manager generates when the rule is met.
1-4
Service Assignments
This area of the User Monitor monitor page lets you view and establish service assignments.
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lets you assign or unassign resources. The dialog box contains the following fields:
Service
The name of the service or application that you can assign or unassign.
Current pServer
The pServer on which the application is either Started or Starting. If no current pServer appears, it means that the application is Stopped.
Status
The current run state of the application, such as Started or Stopped.
Modifying User-defined Monitors
Use the following PAN Manager procedures to list hardware and system monitors that an administrator can access:
Assign User Defined Monitor Resources for an Application
Assign a User Defined Monitor to a Load Balancer
Configure Event Trigger Rules for the User Defined Monitor
Configure Service Assignments for User Defined Monitors
Modifying User-Defined Monitor Resource Configurations
1-5
Book Title
Modifying User-defined Monitors (CLI)
Use the following PAN Manager commands to list hardware and system monitors that an administrator can access:
mon -- Lists and modifies the system monitors for system processes on pBlades, LPANs, or a platform.
umon -- Creates, modifies, or lists an LPAN's user-defined monitor resources.
1-6
Selecting and Displaying Monitor Data
On the User Monitors page:
This page displays groups of system monitors that lets you learn more about the security domain (PAN or LPAN) that is currently selected in the PAN Manager left pane. You can display monitor data in table format or in various graphical formats.
About Listing and Selecting Monitors
List the Available Monitors and Their Triggers
Manage Hardware, System, and User-Defined Monitors
Manage Hardware, System, and User-Defined Monitors (CLI)
Viewing an individual monitor displays a link to the event type of an event monitor. Clicking this link takes you to the Event Type page.
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Listing and Selecting Monitors
This page lists groups of system resource monitors for the physical or virtual object that is selected in the PAN Manager left pane.
When a platform starts, the Intelligent Platform Management Interface (IPMI) software’s discovery process generates the platform system resource monitors.
You can monitor the following objects in the PAN Manager security domains:
PANs>
1-1
Book Title
This security domain’s monitors lets you collect data from all physical components in the PAN (the platform and each of its cBlades and pBlades), as well as all pServers in each of the LPANs in the PAN.
Platforms>MyFrame
This security domain’s monitors lets you collect data only from all physical components in the PAN (the platform and each of its blades).
LPANs>lpan_name>
This security domain’s monitors lets you collect data only from all pServers, and their physical components, in the selected LPAN.
For a pServer’s monitors to be visible, the pServer must be booted.
Learn more about the specific areas of the page:
• User-defined Monitors
• Monitor Groups
User-defined Monitors
This area of the Monitors page lets you assign customized monitors. You can define how often the monitor checks the system or application object that it monitors, and the units in which the monitor reports its data.
An application service can have multiple user-defined monitors.
Hint: To set rules by which PAN Manager generates an event about the data that the monitor is reporting, first create the monitor, and then click Edit to define its rules.
1-2
Clicking Create...
The Create monitor dialog box lets you create a monitor for the selected application:
Name
Enter a name for the user-defined monitor.
Description
A brief identifying note for the user-defined monitor.
Executable
Enter the full pathname (on the pServer) of the command that this user-defined monitor runs (for example, an executable script that runs the application that monitors your service(s)).
Data Unit
Enter a descriptive label for the data that this user-defined monitor generates. This label appears on this monitor's charts and graphs.
Frequency (seconds)
Enter an integer with a minimum value of ten to set the frequency that this monitor checks the status of you service(s).
Start Up Delay (seconds)
Enter an integer in this field to avoid false failures when the application starts up. You can specify a delay for activating its health monitor.
Clicking Delete...
The Delete monitor dialog box enables you to delete a monitor. The dialog box contains the following fields:
Name
The name of the monitor.
Service Assignment
1-3
Book Title
The service the monitor is currently assigned to.
Selecting Charts...
Displays graphically, in the form selected under Chart Type, the data from the monitors that you selected.
Selecting Table...
Displays, in columns, the data from the monitors that you have selected.
Monitor Groups
This area of the Monitors page lists groups of system resource monitors for the physical or virtual object that is selected in the PAN Manager left pane. Each monitor is associated with one event type.
The number of monitors in each group appears in parentheses in the group’s heading. Click the heading to display the monitors in the group. You can then select one, many, or all monitors of the monitor type for display.
Selecting a monitor group or user-defined monitor displays the following fields:
Chart Type
This pull-down list lets you select the graphical display format for a particular monitor or set of monitors. The following formats are available:
Line
Presents data as one or more horizontal lines, for time-line history; for example:
1-4
If two monitors display identical data, the lines are superimposed. To verify this, click the legend entry for each.
Bar 1
Plots data vertically in bars, side by side, one monitor per bar. This format is best when comparing numerous monitors. For example:
1-5
Book Title
Bar 2
Plots data vertically in bars, side by side, one monitor per bar, with time-line history. This format is best when comparing a small number of monitors. For example:
1-6
Stacked Bar
Plots vertical aggregate values for all monitors, with time-line history. This format is best when the cumulative value of the monitors is meaningful, such as for platform power consumption. For example:
1-7
Book Title
Pie
Presents monitor data in pie chart form; for example:
1-8
Monitor
The monitors within a monitor group.
Event Triggers
(Optional) For each monitor, an event type for which notification guidelines are established. To learn more about an event type that is associated with a monitor, click the name of the event type in the Event Triggers column.
Manage Hardware, System, and User-Defined Monitors
Use the following PAN Manager procedures to list hardware and system monitors that an administrator can access:
Create User-Defined Monitor Resources with the GUI
1-9
Book Title
Assign User Defined Monitor Resources for an Application
Assign a User Defined Monitor to a Load Balancer
Configure Event Trigger Rules for the User Defined Monitor
Modifying User-Defined Monitor Resource Configurations
You can configure a user-defined monitor’s event trigger rules only after you create the user-defined monitor.
Manage Hardware, System, and User-Defined Monitors (CLI)
Use the following PAN Manager command to list hardware and system monitors that an administrator can access:
mon -- Lists and modifies the system monitors for system processes on pBlades, LPANs, or a platform.
umon -- Creates, modifies, or lists an LPAN's user-defined monitor resources.
1-10
Blades
This section of the PAN Manager GUI Guide provides descriptions for viewing and managing blades and blade pools. Topics include:
• Viewing Blades
• Managing a Blade
• Managing Pools
• Configuring a Pool
1-1
Book Title
1-2
Viewing Blades (Resources > Blades)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Some configuration tasks can only be performed by your PAN Administrator.
On the Blades page:
This page lets you manage all blades in the PAN.
About Blade Resources
Manage Blade Resources
Manage Blade Resources (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Blade Resources
This page displays the physical characteristics of all pBlades and vBlades in the PAN, including whether the pBlades are allocated to an LPAN or to a global (PAN-wide) pBlade pool.
Clicking Allocate pBlades...
(For PAN Administrators only) The Change pBlade Allocation dialog box displays all pBlades in the PAN.
In the area 1. Choose pBlade(s) to allocate:
pBlade
The name of the pBlade.
Current Allocation
The LPAN or global blade pool to which the pBlade is currently allocated.
1-1
Book Title
Selecting an unallocated pBlade activates the fields in the area 2. Choose Allocation parameters:
None (Unallocated)
If selected, indicates that the pBlade is not currently allocated to either an LPAN or a global blade pool.
Global Pool
If selected, indicates that the pBlade is currently allocated to a global blade pool.
LPAN lpan_name
If selected, indicates that the pBlade is allocated to the LPAN that currently appears in the pull-down list.
Name
Indicates the physical location of the blade in the chassis, in the form platform_name/pn, where platform_name is the name of the platform in which the blade resides, and n is the slot number in the chassis.
The naming convention for vBlades is an extension of the way pBlades are named in PAN Manager. A vBlade name uses the following format, platform_name/pn-n, where the -n is a number (from 1 to 32) that uniquely identifies this vBlade on its pBlade.
Note: The hyphen (-) is a required separator for vBlade names.
CPU
Indicates the number of processors in the pBlade.
Speed
The pBlade clock speed in MegaHertz (MHz) or GigaHertz (GHz).
Arch.
1-2
Indicates the pBlade processor type.
RAM
The pBlade random access memory in gigabytes (GB).
Allocation
The LPAN or global blade pool to which the pBlade is allocated.
Assignment
The name of the pServer or local (LPAN-wide) blade pool, if any, to which the pBlade is currently assigned, and whether the blade is configured as the pServer’s primary or failover pBlade, and whether the pBlade is the pServer’s active (current) pBlade.
Manage Blade Resources
Use the following PAN Manager procedure to manage the PAN’s blade resources:
Allocating pBlades
Manage Blade Resources (CLI)
Use the following PAN Manager commands to manage the PAN’s blade resources:
blade -- Manages the blades of a platform.
pool -- Creates, lists, or modifies a set of blades for a failover pool.
1-3
Book Title
1-4
Managing a Blade
(Platforms > platform_name > Blade)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Only a PAN Administrator can perform some configuration tasks.
On the Blade page:
Displaying a blade (Control Blade, Processing Blade, or Switch Blade) identifies its operating status, uptime, and manufacturer’s data. You can use the controls in the bottom of the page to perform operations on the blade.
See additional information about a specific blade type:
• Control Blade
• Processing Blade
• Switch Blade
• vBlade
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
Control Blade
(Platforms > platform_name > Control Blade)
On the cBlade cBlade_name page:
Displaying a Control Blade identifies its operating status, uptime, and manufacturer’s data. You can use the controls at the bottom of the page to perform operations on this cBlade.
About the Control Blade
Controls for Managing a Control Blade
Manage a Control Blade
1-1
Book Title
Manage a Control Blade (CLI)
About the Control Blade
The Control Blade is a component in the platform that controls overall communications functions and system management, including external network traffic I/O, system administration functions, and network configurations.
Each platform contains two cBlades. The following are the identifying characteristics of a Control Blade:
cBlade platform_name/cn
The page’s top banner displays the name of the platform in which the cBlade resides (such as MyFrame) and the physical location of the cBlade in the chassis (such as c2). The slot number appears next to the component on the chassis front rail.
Version
(Located on the left side of the page’s top banner) Displays version information about the software (PAN Manager and operating system) currently installed on this cBlade.
Clicking Hostname...
If you would like to change the default cBlade hostnames to something more meaningful for you, click this button. Enter the new name in the Set cBlade hostname dialog box. These hostname changes take effect immediately; you do not need to reboot the cBlades to have them persist.
When you name cBlades, it is helpful to retain an indication of the cBlade number.
Status
The current operating state of the cBlade, such as Booted or Shutdown. If the cBlade is booted, its role as either the master or slave cBlade appears in parentheses.
CPU
The number and type of processors in this Control Blade.
1-2
Hostname
The name of the cBlade host.
RAM
The amount of random access memory (in gigabytes) that this Control Blade supports.
Cache
The amount of cache memory that this Control Blade supports.
Uptime
The time (expressed in days, hours, and minutes) that the cBlade has been running since it was in a powered down state.
Power
The amount of power (in Watts) currently being consumed by this cBlade.
Serial #
The serial number that uniquely identifies the physical cBlade. You can determine the cBlade release by its serial number:
– A serial number of CT1... is a cBlade
– A serial number of CT2... is a cBlade EP
– A serial number of CT4... is a cBlade EX
– A serial number of CS1... is a cBlade ES
Part #
The product code associated with this cBlade.
ECO Rev
The revision number of the Engineering Change Order. This provides the latest hardware upgrade release number.
Firmware
The revision number of the firmware on the cBlade.
1-3
Book Title
BMC Rev
The revision number of the Baseboard Management Controller (BMC). This is a cBlade and pBlade firmware component that records significant platform events in the Hardware Event Log (HEL) and the System Event Log (SEL).
BIOS Rev
The revision number of the Basic Input/Output System (BIOS). This is a cBlade and pBlade firmware component that provides boot services for the operating system.
CMOS Rev
The revision number of the Complimentary Metal Oxide Semiconductor (CMOS). This is a cBlade and pBlade firmware component that stores the date, time, and system setup parameters.
OPT Rev
The revision number of the Option ROM. This is a pBlade firmware component that stores the giganet device driver.
PCI Information
The cBlade Peripheral Component Interconnect (PCI) data provides information about the physical configuration and original manufacturer of the cBlade PCI controllers. A cBlade supports four PCI controllers; each resides in a numbered PCI slot.
Name
The device’s original manufacturer and revision number.
Type
The type of PCI device.
Bus
The identifier number for a PCI controller. Each bus is associated with multiple devices. Devices that share a common bus share bandwidth on that bus.
1-4
Device
The identifier number of the PCI device on a given bus. Each device is associated with multiple functions.
Function
The means by which the driver software recognizes the physical PCI device. The function number represents the port number associated with a given device.
HBA Information
The cBlade HBA data provides information about the host bus adapter’s SCSI port number and status:
World-wide Name (node):
The unique global identifier for a specific HBA node process.
World-wide Name (port):
The unique global identifier for a specific HBA port.
Status
Indicates the loop state of the host adapter line. A status of READY indicates that the HBA port is properly flashed and that both ends of the cable are powered up. A status of dead indicates either that the HBA port is improperly flashed, or that one or both ends of the cable are not powered up.
Controls for Managing a Control Blade
The bottom border of the blade page has controls for managing one of the Control Blades.
Power on/off blade
Applies or removes power for the Control Blade. Be aware that the software does not perform an orderly clean up when you power off a cBlade.
1-5
Book Title
Power cycle blade
Resets all hardware on the Control Blade to its initialized state, immediately interrupting any software without allowing it to shut down gracefully, and then reboots the operating system and runs the initialization scripts. (Applying reset to a powered off cBlade has no effect.)
Important: Your cBlades are equipped with a utility called CIO (Customer Information Operation). CIO will automatically alert Fujitsu Siemens Computers customer support or your authorized support vendor in the case of a severe cBlade event, such as an unresponsive cBlade. However, there may be times when such an event is expected, typically during routine maintenance. In such cases, you must use the PAN Manager command-line interface to place a cBlade into maintenance mode. This prevents unnecessary alerts from being sent to service personnel.
Send NMI (Non-Maskable Interrupt) to blade
Causes the Control Blade to behave as if it had panicked. The cBlade default panic behavior is to generate a crash dump, and then reboot. (You can also configure a cBlade to reboot without generating a crash dump. For more information about adjusting a blade’s default panic behavior, see PAN Manager Administrator’s Guide.)
Power on/off cBlade switch
On BladeFrame BF200, applies or removes power for this Control Blade cBlade switch, which provides point-to-point connectivity among all pBlades and cBlades.
Power cycle cBlade switch
On BladeFrame BF200, resets the cBlade switch hardware on the Control Blade to its initialized state.
1-6
Select blade
Marks the cBlade as ready for an administrative action.
After you select it, the cBlade indicator light in the chassis flashes blue. A cBlade that is selected can be either In Service or Out Of Service.
Put blade out of service
Places a booted cBlade in an Out of Service Pending state. The next time it powers down, the cBlade moves to Out of Service. If the cBlade is shutdown, selecting Out of Service immediately places it out of service.
Manage a Control Blade
Use the following PAN Manager procedures to manage a Control Blade:
Maintenance Mode
Controlling a cBlade
Controlling a cBlade switch (BladeFrame BF200 only)
Manage a Control Blade (CLI)
Use the following PAN Manager commands to manage a Control Blade:
blade -- Manages the blades for a platform.
version -- Lists versions of software packages installed on a cBlade or pServer.
Processing Blade
(Platforms > platform_name > Processing Blade)
On the pBlade pBlade_name page:
1-7
Book Title
Displaying a Processing Blade identifies its operating status, uptime, manufacturer’s data, and to which LPAN and pServer, if any, it is currently assigned. You can use the controls at the bottom of the page to perform operations on this pBlade.
About the Processing Blade
Allocating pBlades
Controls for Managing a Processing Blade
Manage a Processing Blade
Manage a Processing Blade (CLI)
About the Processing Blade
The following are the identifying characteristics of a Processing Blade:
Clicking Allocate...
The Change pBlade Allocation dialog box contains the following fields:
None (unallocated)
The pBlade does not reside in an LPAN or in a global pBlade pool.
Global Pool
The pBlade resides in a PAN-wide pool of pBlades.
LPAN
The pBlade is allocated to the LPAN that is visible in the pull-down list.
Clicking Priority...
The Management Domain CPU priority dialog box enables you to set the pBlade CPU priority for the hypervisor. This enables you to set the relative weighting of each vBlade in terms of CPU processing time. For more information about hypervisor domains, see Using vBlades.
1-8
pBlade platform_name/pn
The page’s top banner displays the name of the platform in which the pBlade resides (such as platform_name) and the physical location of the pBlade in the chassis (such as p2). The slot number appears next to the component on the chassis rail.
Status
The current operating state of the pBlade, such as Booted or Shutdown.
CPU
The number and type of processors in this pBlade.
RAM
The amount of random access memory (in gigabytes) that this pBlade supports.
Cache
The a mount of cache memory that this pBlade supports.
Uptime
The time (expressed in days, hours, and minutes) that the pBlade has been running since it was in a powered down state.
Power
The amount of power (in Watts) currently being consumed by this pBlade.
Serial #
The serial number that uniquely identifies the physical pBlade.
Part #
The product code associated with this pBlade.
ECO Rev
The revision number of the Engineering Change Order. This provides the latest hardware upgrade release number.
1-9
Book Title
Firmware
The revision number of the firmware on the pBlade.
BMC Rev
The revision number of the Baseboard Management Controller (BMC). This is a cBlade and pBlade firmware component that records significant platform events in the Hardware Event Log (HEL) and the System Event Log (SEL).
BIOS Rev
The revision number of the Basic Input/Output System (BIOS). This is a cBlade and pBlade firmware component that provides boot services for the operating system.
CMOS Rev
The revision number of the Complimentary Metal Oxide Semiconductor (CMOS). This is a cBlade and pBlade firmware component that stores the date, time, and system setup parameters.
OPT Rev
The revision number of the Option ROM. This is a pBlade firmware component that stores the giganet device driver.
Hardware Features
If the pBlade supports the feature and it is enabled, a green checkmark displays next to it. If the pBlade supports the feature and it is disabled an X displays next to it. If the pBlade does not support the feature it is not listed. Hardware features include the following:
Hardware Prefetch
A firmware option for pServers that uses the hardware features of certain pBlades to bring data and instructions into higher-speed memory before the processor needs it, to minimize latency. The hardware prefetch option can improve the performance of pServers running Oracle applications.
1-10
Hyperthreading
A firmware option for pServers that uses the Hyper-Threading Technology feature of certain Intel pBlades to improve the performance of multithreaded applications.
Memory Node Interleaving
A firmware option for pServers that uses the hardware features of certain pBlades to interleave a single page of memory from each processor at a time.
Virtualization Extensions
Hypervisors use these extensions so that guest operating systems can use virtual device drivers to access the vBlade processing resource on a pBlade.
For more information about Firmware options, see PAN Manager Administrator’s Guide.
Allocation
The LPAN or global blade pool (if any) to which the pBlade is currently allocated.
Assignments
An assignment includes the name of the pServer or local (LPAN-wide) blade pool, if any, to which the pBlade is currently assigned. It also includes whether the blade is configured as the pServer primary or failover pBlade, and whether the pBlade is the pServer active (current) pBlade.
If the pBlade is configured with a hypervisor, that configuration is listed here in the following format:lpanname/hypervisorname:primary
For example:doc/_hv-zeus-p7:primary
1-11
Book Title
vBlades
This area of the pBlade platform_name/pn page displays all vBlades currently on the pBlade, and lets you add more vBlades or remove existing ones.
Clicking a vBlade displays its characteristics in detail.
Clicking Create...
The Create vBlade dialog box lets you configure a vBlade. This dialog box contains these following fields:
• vBlade number — Specifies the number given to the vBlade (from 1 to 32).
• Number of CPUs — Specifies the number of processors allocated to the vBlade.
• RAM Amount — Specifies the amount of RAM in MB or GB allocated to the vBlade.
• vBlade priority — Specifies the relative weighting of each vBlade in terms of CPU processing.
Clicking Delete...
The Delete vBlades dialog box lets you remove vBlades from a pBlade. The dialog box contains these following fields:
• vBlades — The name of the vBlades configured on the pBlade.
• CPU/Speed/RAM — The number of processors, the speed of the processors, and the amount of RAM allocated to the vBlade.
• Assignments — This field lists the name of the pServer or local (LPAN-wide) blade pool, if any, to which the vBlade is currently assigned. It also lists whether the blade is configured as the pServer primary or failover blade, and whether the vBlade is the pServer’s active (current) vBlade.
1-12
The following fields describe the characteristics of the vBlades:
Name
In the form platform_name/pn-n, where platform_name/pn is the name of the pBlade that hosts the vBlade, and n is a number (from 1 to 32) that uniquely identifies this vBlade on the pBlade.
CPU
Indicates the number of processors in the vBlade.
Speed
The vBlade clock speed in MegaHertz (MHz) or GigaHertz (GHz).
Arch.
Indicates the vBlade processor type.
RAM
The vBlade random access memory in megabytes (MB) or gigabytes (GB).
Allocation
The LPAN or global blade pool to which the vBlade is allocated.
Assignment
The name of the pServer or local (LPAN-wide) blade pool, if any, to which the vBlade is currently assigned. In addition, whether the vBlade is configured as the pServer’s primary or failover vBlade, and whether the vBlade is the pServer’s active (current) vBlade.
1-13
Book Title
Controls for Managing a Processing Blade
The bottom border of the blade page has controls for managing one of the Processing Blades:
Power on/off blade
Applies or removes power for the Processing Blade. Be aware that the software does not perform an orderly clean up when you power off a pBlade.
Warm up blade
A "warm pBlade" is powered up, but disabled from booting. Having a warm pBlade as a failover pBlade can minimize failover time.
Warm pBlades have live hardware monitors that can detect IPMI sensor events, but they consume power because they are powered on.
Cool down blade
Changes a "warm pBlade" to a “cool pBlade.” A "warm pBlade" is powered up, and when used for pServer failover, can minimize failover time; a cool pBlade is in a powered off state.
Power cycle blade
Resets all hardware on the Processing Blade to its initialized state, immediately interrupting any software without allowing it to shut down gracefully, and then reboots the operating system, and runs the initialization scripts. (Applying reset to a powered off pBlade has no effect.)
1-14
Send NMI (Non-Maskable Interrupt) to blade
Causes the Processing Blade to behave as if it had panicked. The default panic behavior of a pBlade is to generate a crash dump, and then reboot. (You can also configure a pBlade to reboot without generating a crash dump. For more information about adjusting a blade’s default panic behavior, see PAN Manager Administrator’s Guide.)
Select blade
Marks the pBlade as ready for an administrative action.
The indicator light of the selected pBlade in the chassis flashes blue. A pBlade that is selected can be either In Service or Out Of Service.
Put blade out of service
Places a booted pBlade in an Out of Service Pending state. The next time it powers down, the pBlade moves to Out of Service. If the pBlade is shutdown, selecting Out of Service immediately places it out of service.
Set maintenance
Adds a pBlade to the .maint LPAN which makes it unavailable to its original LPAN.
Unset maintenance
Removes a pBlade from the .maint LPAN and makes it available to its original LPAN.
Configure hypervisor on a blade
1-15
Book Title
Configures a particular pBlade to use a hypervisor. The pBlade needs to belong to an LPAN before you can configure it with a hypervisor.
Manage a Processing Blade
Use the following PAN Manager procedure to manage a Processing Blade:
Controlling a pBlade
To configure a pBlade to use a hypervisor or to cancel this configuration, and to create, modify, or delete a vBlade, see the Administering vBlades chapter in Using vBlades.
Manage a Processing Blade (CLI)
Use the following PAN Manager command to manage a Processing Blade:
blade -- Manages the blades of a platform.
Switch Blade
(Platforms > platform_name > Switch Blade)
On the sBlade sBlade_name page:
Displaying a Switch Blade identifies the operating status, uptime, and manufacturer’s data about a specific Switch Blade. You can use the controls at the bottom of the page to perform operations on this sBlade.
About the Switch Blade
Controls for Managing a Switch Blade
Manage a Switch Blade
Manage a Switch Blade (CLI)
1-16
About the Switch Blade
The Switch Blade is a platform component that provides point-to-point connectivity among all Processing Blades and Control Blades.
Each platform system contains two Switch Blades: sBlade1 and sBlade2. The top sBlade is sBlade2; the bottom sBlade is sBlade1.
The following are the identifying characteristics of a Switch Blade (all read-only):
sBlade platform_name/sn
The page’s top banner displays the name of the platform in which the sBlade resides (such as My_frame) and the physical location of the sBlade in the chassis (such as s2). The slot number appears next to the component on the rail.
Status
The current operating state of the sBlade, such as On or Off.
CPU
The number and type of processors in this sBlade.
RAM
The amount of random access memory (in gigabytes) that this sBlade supports.
Cache
The amount of cache memory that this sBlade supports.
Uptime
Expressed in days, hours, and minutes, indicates how long the sBlade has been running since it was in a powered down state.
1-17
Book Title
Power
The amount of power (in Watts) currently being consumed by this sBlade.
Serial #
The serial number uniquely identifying this physical sBlade.
Part #
The product code associated with this sBlade
ECO Rev
The revision number of the Engineering Change Order. This provides the latest hardware upgrade release number. This field represents the sBlade ECO Rev.
Firmware
The revision number of the firmware on the sBlade.
BMC Rev
The revision number of the Baseboard Management Controller (BMC). This is a firmware component that records significant platform events in the Hardware Event Log (HEL) and the System Event Log (SEL).
BIOS Rev
The revision number of the Basic Input/Output System (BIOS). This is a firmware component that provides boot services for the operating system.
1-18
CMOS Rev
The revision number of the Complimentary Metal Oxide Semiconductor (CMOS). This is a firmware component that stores the date, time, and system setup parameters.
OPT Rev
The revision number of the Option ROM. This is a pBlade firmware component that stores the giganet device driver.
Controls for Managing a Switch Blade
The bottom border of the blade page has controls for managing one of the Switch Blades:
Power on/off blade
Applies or removes power for the Switch Blade. Be aware that the software does not perform an orderly clean up when you power off an sBlade.
Power cycle blade
Resets all hardware on the Switch Blade to its initialized state, immediately interrupting any software without allowing it to shut down gracefully, and then reboots the operating system and runs the initialization scripts.
Send NMI (Non-Maskable Interrupt) to blade
Causes the Switch Blade to behave as if it had panicked. The default panic behavior of an sBlade is to generate a crash dump, and then reboot. (You can also configure an sBlade to reboot without
1-19
Book Title
generating a crash dump. For more information about adjusting a blade’s default panic behavior, see PAN Manager Administrator’s Guide.)
Select blade
Marks an sBlade as ready for an administrative action. The indicator light of the selected sBlade in chassis flashes blue.
Put blade out of service
Places a booted sBlade in an Out of Service Pending state. The next time it powers down, the sBlade moves to Out Of Service. If the sBlade is shutdown, selecting Out of Service immediately places it Out of Service.
Manage a Switch Blade
Use the following PAN Manager procedure to manage a Switch Blade:
Controlling a cBlade switch (BladeFrame BF200 only)
Manage a Switch Blade (CLI)
Use the following PAN Manager command to manage a Switch Blade:
blade -- Manages the blades of a platform.
vBlade
(LPANs > lpan_name > Blades > vBlade_name)
On the vBlade vBlade_name page:
1-20
Displaying a vBlade identifies its operating status, uptime, manufacturer’s data, and to which LPAN and pServer, if any, it is currently assigned. You can use the controls at the bottom of the page to perform operations on this vBlade.
About the vBlade
Controls for Managing a vBlade
Manage a vBlade
Manage a vBlade (CLI)
About the vBlade
The following are the identifying characteristics of a vBlade:
Clicking Modify...
The Modify vBlade dialog box lets you change the vBlade configuration. This dialog box contains the following fields:
Number of CPUs
The number of processors assigned to this vBlade.
RAM Amount
The amount of random access memory (in megabytes or gigabytes) that this vBlade supports.
vBlade priority
The CPU processing time of the vBlade relative to other vBlades on the pBlade. This does not guarantee a minimum or maximum amount of processor utilization. It is a method to prioritize CPU usage by vBlades.
vBlade platform_name/pn-n
The page’s top banner displays the name of the platform in which the vBlade resides (such as My_frame) and the physical location of the pBlade in the chassis (such as p2). The -n is a number (from 1 to 32) that uniquely identifies this vBlade on the pBlade.
1-21
Book Title
Status
The current operating state of the vBlade, such as Booted or Shutdown.
CPU
The number and type of processors in this vBlade.
RAM
The amount of random access memory (in megabytes or gigabytes) that this vBlade supports.
Cache
The amount of cache memory that this vBlade supports.
Uptime
The time (expressed in days, hours, and minutes) that the vBlade has been running since it was in a powered down state.
Power
Not applicable for vBlades. To view the amount of power (in Watts) currently being consumed, check the pBlade.
Serial #
The serial number that uniquely identifies the vBlade. It is based on the pBlade number with -n appended to it.
Part #
PAN Manager generates this number and bases it on the following vBlade attributes:
– Architecture
– Number of CPUs
– RAM size (MB)
If you change attributes (for example, increase or decrease the number of CPUs), the vBlade part number also changes. PAN Manager first looks at the part number when failing over a pServer from one vBlade to another.
ECO Rev
1-22
The revision number of the Engineering Change Order. This provides the latest hardware upgrade release number. This field represents the pBlade ECO Rev.
Firmware
The revision number of the firmware on the pBlade.
BMC Rev
The revision number of the Baseboard Management Controller (BMC). This is a cBlade and pBlade firmware component that records significant platform events in the Hardware Event Log (HEL) and the System Event Log (SEL).
BIOS Rev
The revision number of the Basic Input/Output System (BIOS). This is a cBlade and pBlade firmware component that provides boot services for the operating system.
CMOS Rev
The revision number of the Complimentary Metal Oxide Semiconductor (CMOS). This is a cBlade and pBlade firmware component that stores the date, time, and system setup parameters.
OPT Rev
The revision number of the Option ROM. This is a pBlade firmware component that stores the giganet device driver.
Hardware Features
If the pBlade that the vBlade resides on supports the feature and it is enabled, a green checkmark displays next to it. If the pBlade supports the feature and it is disabled, an X displays next to it. If the pBlade does not support the feature it is not listed. Hardware features include the following:
Hardware Prefetch
A firmware option for pServers that uses the hardware features of certain pBlades to bring data and instructions into higher-speed memory before
1-23
Book Title
the processor needs it to minimize latency. The hardware prefetch option can improve the performance of pServers running Oracle applications.
Hyperthreading
A firmware option for pServers that uses the Hyper-Threading Technology feature of certain Intel pBlades to improve the performance of multithreaded applications.
Node Interleaving
A firmware option for pServers that uses the hardware features of certain pBlades to interleave a single page of memory from each processor at a time.
Virtualization Extensions
Hypervisors use these extensions so that guest operating systems can use virtual device drivers to access the vBlade processing resource on a pBlade.
For more information about Firmware options, see PAN Manager Administrator’s Guide.
Allocation
The LPAN (if any) to which the vBlade is currently allocated.
Assignments
The name of the pServer or local (LPAN-wide) blade pool, if any, to which the vBlade is currently assigned, and whether the vBlade is configured as the pServer’s primary or failover vBlade, and whether the vBlade is the pServer’s active (current) vBlade.
1-24
Controls for Managing a vBlade
The bottom border of the blade page has controls for managing one of the vBlades:
Power on
Powers on the vBlade (if currently off). If the vBlade is assigned as a primary blade for a particular pServer, this tells PAN Manager to boot that pServer on the vBlade. (If no pServer is eligible to boot on this vBlade, PAN Manager displays an error message.)
Power off
Powers off the vBlade (if currently on). This shuts down the pServer currently running on the vBlade.
Reset
Power cycles the vBlade (if currently on). This is similar to powering off and powering on the vBlade.
Send NMI (Non-Maskable Interrupt) to blade
This button is disabled because NMI is not currently available for vBlades.
Note: vBlade boot operations require a supported hypervisor to be running on the underlying pBlade of the vBlade. We recommend that administrators configure and boot the hypervisor on a pBlade in preparation for vBlade use. But if these steps have not been completed, PAN Manager will automatically try to configure and boot the hypervisor (using appropriate default values) so that vBlade operations can proceed.
1-25
Book Title
Manage a vBlade
To control a vBlade, use the procedures found in the Administering vBlades chapter in Using vBlades.
Manage a vBlade (CLI)
Use the following PAN Manager commands to manage a vBlade:
blade -- Manages the blades of a platform.
pan -- Configures the default event actions for the PAN domain.
1-26
Managing Pools (Pools)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the Global Pools page:
This page displays all global blade pools in the PAN, the blades that each contains, and any LPANs that have boot access or failover access to each pool.
About Managing Pools
Manage Global Pools
Manage Pools (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing Pools
The PAN Administrator can create global pools, manage existing pools, delete pools, and control LPAN access to global pools.
Global pools contain pBlades available to all pServers in the PAN for primary and failover use. You may create up to 20 global pools in a PAN. Local pools (pools restricted to pBlades in a specific LPAN) may link to global pools.
Name
Indicates the name of the global blade pool. (Pools are listed alphabetically: to reverse the order, click the Name heading and then click the handle that appears next to the heading.)
Blades Available
1-1
Book Title
Indicates how many blades in each global pool are available for pServers to use. (To list these totals in ascending or descending order, click the Blades Available heading and then click the handle that appears next to the heading.)
Blade Summary
For each global pool, lists available pBlades in the form MyFrame/pn, where MyFrame is the name of the platform, and n indicates the physical location of the pBlade in the chassis.
A green checkmark indicates that a pBlade is available for use. A red pBlade name indicates the pBlade is allocated to the pool but currently unavailable (not in the chassis).
LPAN Access
Lists the LPANs that are currently configured to obtain pBlades from a global pool. A blue Up Arrow indicates that the LPAN’s pServers can boot from a blade in the pool.
Clicking Create...
The Create Global Pool dialog box lets you specify a pool name and identifying description.
Clicking Delete...
The Delete Global Pool dialog box lets you select one or more global pools to delete from the PAN. You cannot delete a global pool if it contains pBlades that pServers are actively using, or if an LPAN is configured to access it.
Manage Global Pools
Use the following PAN Manager procedures to manage global pools:
Creating a Global Pool
Enabling LPAN Access to a Global Pool
1-2
Deleting a Global Pool
You must have the PAN Administrator role to create a global pool, and the LPAN Administrator role to create a local pool.
Manage Pools (CLI)
Use the following PAN Manager command to manage global pools:
pool -- Creates, modifies, or deletes a global pool configuration.
1-3
Book Title
1-4
Configuring a Pool
(Resources > Pools > pool_name)
On the Global Pool pool_name page:
This page of the PAN Manager graphical user interface is for PAN Administrators only.
This page displays the pBlades allocated to the current global pool, and lists any LPANs that have access to the pool. It also lets you modify the resource allocations, name, and description of the current pool.
(LPANs > lpan_name)
On the LPAN Local Pool pool_name page:
This page of the PAN Manager graphical user interface is for PAN Administrators or LPAN Administrators only.
This page displays all pBlades allocated to the current local pool, and lets you add pBlades to the pool, remove pBlades from the pool, and link the local pool to a global pool of pBlades.
About Configuring a Pool
Configure a Pool
Configure a Pool (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Configuring a Pool
This page lets you manage an existing global or local pool. A global pool contains pBlades that can be accessed by any LPAN in the PAN for which access has been enabled. pBlades can be used as failover or primary blades for pServers. By contrast, a local pool contains pBlades that can be accessed only by pServers in a specific LPAN.
1-1
Book Title
On the Global Pool page only:
Clicking Edit...
The Edit Global Pool dialog box lets you rename the pool or modify its description.
Clicking LPAN Access...
The Edit LPAN Access dialog box allows you to enable or disable LPAN access to this global pool and to specify whether pServers have failover or boot (primary) access.
On the LPAN Local Pool page only:
Clicking Edit...
The Edit pool description dialog box lets you rename the pool or modify its description.
Clicking Global Pool Link...
The Link Global Pool dialog box lets you select a global pool to which pServers in the current LPAN can gain access for boot or failover purposes.
Blades
This area of the Pool page lets you add and remove processing resources (Processing Blades, or pBlades) for the pool.
If a pBlade allocated to a pool is physically removed from the chassis, or if the pBlade becomes functionally unavailable to the pool, the pBlade name appears in red.
Clicking Add...
The Add blades to pool dialog box lists all Processing Blades in the platform that are not currently allocated to another LPAN or to a global pBlade pool.
This dialog box contains the following fields:
Blade
1-2
The name of the Processing Blade, in the form MyFrame/pn, where MyFrame is the name of the platform, and n indicates the physical location of the pBlade in the chassis.
(For Global Pools only) In the Manual Entry field, you can also specify a name of your own choosing for a pBlade, in the standard MyFrame/pn format.
CPU/Speed/RAM
The number of processors in the pBlade, its clock speed in MegaHertz (MHz), and its random access memory in gigabytes (GB).
Clicking Remove...
The Remove blades from Pool dialog box lists all pBlades currently allocated to the pool. This dialog box contains the following fields:
Blade
The name of the Processing Blade, in the form MyFrame/pn where MyFrame is the name of the platform, and n indicates the physical location of the pBlade in the chassis.
CPU/Speed/RAM
The number of processors in the pBlade, its clock speed in MegaHertz (MHz), and its random access memory in gigabytes (GB).
pServer Use
The pServer to which a pBlade is currently assigned, and whether the pBlade is the pServer’s primary or failover pBlade.
You can remove a pBlade from the LPAN only if the pBlade is not currently assigned to a pServer.
1-3
Book Title
Configure a Pool
Use the following PAN Manager procedures to configure a blade pool:
Modifying a Global Pool
Creating a Local Pool
Allocating Blades to a Local Pool
You must have the LPAN Administrator role to create a local pool.
Configure a Pool (CLI)
Use the following PAN Manager command to configure a blade pool:
pool -- Creates, lists, or modifies a blade pool configuration.
1-4
Storage and Media
This section of the PAN Manager GUI Guide provides descriptions for creating and managing storage and media. Topics include:
• Configuring SCSI Disk Resources
• Managing a SCSI Disk
• Configuring SCSI Tape Devices
• Managing a SCSI Tape Device
• Managing DVD-ROM Resources
1-1
Book Title
1-2
Configuring SCSI Disk Resources
(Resources > Disks)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the SCSI Disks page:
This page lists the characteristics of all disk resources in the entire PAN.
About Configuring SCSI Disk Resources
Viewing PAN Disk Resources
Manage SCSI Disk Resources
Manage SCSI Disk Resources (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Configuring SCSI Disk Resources
This page lists all disk resources in the PAN.
PAN Manager scans the SAN every few minutes to update its display of disks. To run this scan manually, click Scan SAN.
Clicking Scan SAN...
In the Scan SAN dialog box, you can run the PAN Manager scan manually and display any changes in the PAN’s device resources since the previous refresh operation, the previous PAN Manager browser session, the previous PAN Manager restart operation, or the previous platform restart operation.
The scan finds any new devices:
• Tapes
• Disk
1-1
Book Title
The can then provides the availability of the current devices. Click the Show detailed results of scan check box to see more details with the scan results.
Clicking Allocate Disks...
In the Allocate disks dialog box, the scroll list displays all disks in the PAN.
In the area 1. Choose SCSI disks(s) to allocate:
SCSI Disk
The device ID of the disk. (A check box to the left of the disk’s device ID indicates that it is available to allocate to an LPAN.)
Capacity
The amount of storage space that the disk contains.
Current Allocation
Indicates the LPAN (if any) and the pServer (if any) to which the disk is currently allocated.
Selecting an unallocated disk activates the fields in the area 2. Choose New Allocation parameters:
None (Unallocated)
If selected, indicates that the disk is not allocated to an LPAN.
Disaster Recovery
If selected, specifies that the disk is reserved for the purpose of storing PAN archive files. (PAN archive files preserve the configuration information for the entire PAN, and are used to reconstitute a PAN configuration in the event of a disaster.)
LPAN lpan_name
If selected, indicates that the disk is allocated to the LPAN currently displayed in the pull-down list.
1-2
Clicking Persistent Reservations...
The Persistent Reservations dialog box lets you allow multiple booted pServers to access the same disk (LUN) without writing to the disk at the same time. Typically you enable, disable, or clear persistent reservations before adding a disk to a pServer. You can, however, force PAN Manager to enable, disable, or clear persistent reservations for a disk already configured for use with a booted pServer by checking the Force box. (If Veritas Cluster Server is running, you must shut down Veritas before using the Force check box.)
By default, PAN Manager enables all disks with SCSI-2 reservations, which allow a single booted pServer to access a single disk. There is no GUI interface for the SCSI-2 default; PAN Manager enables it automatically.
When you enable SCSI-3 persistent reservations for a disk in this dialog box, you disable the default SCSI-2 reservations for the disk. In order to use persistent reservations, you need to make sure that you map the disk to a pServer that supports SCSI-3. See PAN Manager Release Notes for the SCSI-3 support list.
Learn more about specific areas of this page:
• PAN Disks
PAN Disks
This area of the SCSI Disks page displays all disks currently in the PAN, and lets you add disk resources to the PAN, or remove disk resources from the PAN.
Clicking a disk’s device ID displays its characteristics in detail.
Clicking Add...
The Add disk(s) to PAN dialog box lists disks that PAN Manager has discovered but which do not reside in the PAN.
1-3
Book Title
Clicking Remove...
The Remove disk(s) from PAN dialog box lists all disks in the PAN, and lets you place outside of the PAN one or more disks that are not already allocated for other use. Removed disks still remain “discovered.”
The Purge disk(s) after removal from PAN check box enables you to permanently remove an unwanted disk from the PAN.
Discovered Disks (Not in PAN)
This area of the Disks page displays any disk, discovered by PAN Manager, that is not currently in the PAN. If all discovered disks are automatically imported into the PAN, the message Discovered disks are automatically imported to PAN appears here instead of specific disks.
Clicking Auto-Import...
In the Auto-Import to PAN dialog box, selecting the Auto-Import Discovered Disks to PAN check box ensures that any disk PAN Manager discovers is automatically imported into the PAN. Clearing the check box means that you must manually add any disks that you want to add to the PAN.
Clicking Purge...
In the Purge Discovered Disk(s) not in the PAN dialog box, select the check box next to the disk(s) you want purged to fully delete disks that do not belong to the PAN. Purge removes the device ID entry from PAN Manager memory. The purge action removes the device immediately, and the complete removal from memory occurs after the next cBlade reboot. You cannot use Purge if Auto-Import to PAN is enabled.
Viewing PAN Disk Resources
The PAN Disks area in the Disks page displays the current PAN disk resources, with the following PAN disk resource status icons:
1-4
• —Disk assigned to a booted pServer and unavailable for a new allocation, partitioning, or a root file system.
• —Disk allocated to an LPAN.
• —Disk allocated for storing PAN archives.
Manage SCSI Disk Resources
Use the following PAN Manager procedures to manage disk resources within a PAN:
Scanning for New PAN Disk Resources
Adding PAN Disk Resources
Removing PAN Disk Resources
Removing and Purging PAN Disk Resources
Purging Discovered Disk Resources
Reserving a Disk for Exclusive Storage of PAN Archives
Automatically Importing PAN Disk Resources
About SCSI-3 Persistent Reservations
Enabling Persistent Reservations
Disabling Persistent Reservations
Clearing Persistent Reservations
Manage SCSI Disk Resources (CLI)
Use the following PAN Manager commands to manage disk resources within a PAN:
disk -- Controls or lists operations on a disk that is physically connected to a platform system and recognized by PAN Manager software by means of the sfdisk utility.
pan -- Lists and modifies the PAN configuration.
san -- Lists configuration information and controls operations on SCSI devices that are physically connected to a platform.
1-5
Book Title
1-6
Managing a SCSI Disk
(Resources > Disks > disk_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the disk_name page:
Use this page to create or modify partitions on a disk, including one or more root partitions, and to assign the disk to an LPAN.
About Managing a SCSI Disk
Manage a SCSI Disk
Manage a SCSI Disk (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing a SCSI Disk
The disk_name page lists the physical characteristics of the disk and lets you perform various disk operations.
Learn more about the specific areas of the page:
• Field Descriptions
• Partitions
Clicking Edit...
The Edit Disk dialog box lets you enter a comment about the disk or its purpose.
1-1
Book Title
Clicking Install Root Partition...
The Install Root Partition dialog box lets you specify how the Linux operating system is installed on the disk. (The disk must be partitioned before you can create a Linux root partition on it. Be sure that the partition you select is large enough to contain the root file system.)
For complete installation and configuration details about creating Linux pServers, see the pServer Integration Note document that accompanies the pServer software.
The Install Root Partition dialog box contains the following fields:
Root Image
This pull-down list lets you select a root disk image from all those available in the PAN.
File System
This pull-down list lets you select a file system type that is supported by the root image that you selected.
Partition Number
The recommended partition to contain the disk’s root file system. (The Partition Number does not indicate the disk’s current root partition.)
Clicking Persistent Reservations...
The Persistent Reservations dialog box lets you allow multiple booted pServers to access the same disk (LUN) without writing to the disk at the same time. In this dialog box, you can do the following actions:
• Enable — Enables SCSI-3 persistent reservations for the disk. Check the Force box to force PAN Manager to enable persistent reservations even if the disk is in use on a booted pServer.
1-2
• Disable — Disables SCSI-3 persistent reservations for the disk. Check the Force box to force PAN Manager to disable persistent reservations even if the disk is in use on a booted pServer.
• Clear — Clears any stale SCSI-2 reservations and SCSI-3 persistent reservations (whichever is enabled on the disk). The Clear operation removes all stale registrations and reservations (SCSI-3 and SCSI-2), but does not disable or enable persistent reservations. Check the Force box to force PAN Manager to clear reservations even if the disk is in use on a booted pServer.
If Veritas Cluster Server is running, you must shut down Veritas before using the Force check box.
By default, PAN Manager enables all disks with SCSI-2 reservations, which allow a single booted pServer to access a single disk. There is no GUI interface for the SCSI-2 default; PAN Manager enables it automatically.
When you enable SCSI-3 persistent reservations for a disk in this dialog box, you disable the default SCSI-2 reservations for the disk, and when you disable SCSI-3, you enable the default SCSI-2.
To use persistent reservations, you need to make sure that you map the disk to a pServer that supports SCSI-3. For the SCSI-3 support list, see PAN Manager Release Notes.
Field Descriptions
These fields describe the disk’s characteristics:
Capacity
Total size of the physical disk.
Free
The amount of unused space on the disk.
Type
1-3
Book Title
The disk vendor name, model number, and version information.
Unique ID
The disk’s universal unique identifier.
Serial Number
The disk’s vendor number.
Suspend disk for
If the disk is used as a suspend disk, the pServer name displays here. The Clear button appears only if this SAN disk is currently marked as a suspend disk. Use this only if you discover that PAN Manager has failed to clear the suspend disk automatically after resuming or shutting down a suspended pServer.
Caution: This operation is not intended to be performed on the suspend disk of a normally-functioning suspended pServer. Improper use may destroy suspend data and prevent you from later resuming a pServer’s state. For more information, see Using vBlades.
Allocation
The name of the LPAN to which the disk is allocated.
Clicking Allocate...
The Change Disk Allocation dialog box lets you add this disk to a specific LPAN, reserve it to store PAN configuration archives (for use in disaster recovery), or remove it from use by any LPAN or for storing PAN configuration archives. (You cannot remove a disk from an LPAN if the disk is configured on a booted pServer.) The dialog box contains the following fields:
None
If selected, indicates that the disk is not allocated to an LPAN.
1-4
Disaster Recovery (DR)
If selected, specifies that the disk is reserved for the purpose of storing PAN archive files. PAN archive files preserve the configuration information for the entire PAN, and are used to restore a PAN configuration in the event of a disaster.
LPAN lpan_name
If selected, indicates that the disk is allocated to the LPAN currently displayed in the pull-down list.
Assignments
The name(s) of the pServer(s) to which the disk is assigned. After you configure a disk and assign it to a pServer, you can still use PAN Manager to reassign the same disk (and its configuration) to a different pServer, LPAN, or pool.
IO Paths
The two disk subpaths associated with the disk, one for each Control Blade. If only one disk subpath is visible, it means that the platform is not operating in a redundant manner.
Partitions
This area of the disk_name page provides details about the disk’s partitions (if any), and lets you partition or repartition the disk. The partitions are numbered, starting with partition 1 at the top.
In PAN Manager, Windows disk partitions (such as HPFS/NTFS, FAT16, or Win95 FAT32) are read-only. To modify a pServer’s Windows disk partitions, you must use the standard Windows disk management interface.
Type (Id)
1-5
Book Title
The nature of the partition, such as Linux or Extended. The Id in parentheses is the partition type as reported by the pServer’s operating system.
Size
The size of a partition.
Special Notes
(Read-only) If applicable, a PAN Manager generated comment about the partition type or its characteristics.
Clicking Add...
The Add Partition dialog box lets you specify a new partition for the disk, starting with the next available partition number.
Partition Size
Specifies the size of the partition in the units available in the adjacent pull-down list. To use all remaining space on the disk for this partition, click the Fill button.
Partition Type
The nature of the partition, such as Linux or Extended. (To add a 5th (or higher) partition to the disk, be sure that one of the first four partitions is of the Extended type.)
Clicking Modify...
The Modify Partitions dialog box lets you edit the size and type of one or more of the disk’s partitions. (Any changes you make become permanent when you click the Save button.)
Clicking Clear...
The Clear Partitions dialog box lets you delete all partitions on the disk. (Any changes you make become permanent when you click the Save button.)
1-6
Clicking Reset...
In the Reset Partitions dialog box, clicking OK cancels any changes you made to the disk.
Clicking Save...
In the Save Partitions dialog box, clicking OK erases all data and partitions from the disk, and replaces them with the partitions you have specified.
Manage a SCSI Disk
Use the following PAN Manager procedures to manage a specified disk:
Editing a PAN Disk Resource Description
To install a Linux root partition on the disk, see the appropriate pServer Guide for your operating system.
To create a disk image containing WinPE, see the appropriate pServer Guide for your operating system.
Reserving a Disk for Exclusive Storage of PAN Archives
Assigning a Disk to a pServer
About SCSI-3 Persistent Reservations
Enabling Persistent Reservations
Disabling Persistent Reservations
Clearing Persistent Reservations
To release a disk from hypervisor use, see the Administering vBlades chapter in Using vBlades.
1-7
Book Title
Manage a SCSI Disk (CLI)
Use the following PAN Manager commands to manage a specified disk:
disk -- Controls or lists operations on a disk that is physically connected to a platform and recognized by PAN Manager software by means of the sfdisk utility.
san -- Lists configuration information and controls operations on SCSI devices that are physically connected to a platform.
Use the following PAN Manager command to allocate or reallocate a disk to an LPAN:
lpan -- Creates, lists, or modifies an LPAN configuration.
1-8
Configuring SCSI Tape Devices
(Resources > Tapes)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the SCSI Tapes page:
This page lists the characteristics of all tape devices in the entire PAN.
About Configuring SCSI Tape Devices
Manage SCSI Tape Devices
Manage SCSI Tape Devices (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Configuring SCSI Tape Devices
This page lists all tape devices in the PAN. PAN Manager scans the SAN every few minutes to update its display of tape devices.
Clicking Scan SAN...
In the Scan SAN dialog box, you can run the PAN Manager scan manually and display any changes in the PAN’s device resources since the previous refresh operation, the previous PAN Manager browser session, the previous PAN Manager restart operation, or the previous platform restart operation.
The scan finds any new devices, both tapes and disks, and provides the availability of the current devices. Click the Show detailed results of scan check box to see more details with the scan results.
Clicking Allocate Tapes...
In the Allocate tapes dialog box, the scroll list displays all tape devices in the PAN.
1-1
Book Title
In the area 1. Choose tapes(s) to allocate:
Tapes
The device ID of the tape device. (A check box to the left of the tape device’s ID indicates that it is available to allocate to an LPAN.)
Current Allocation
Indicates the LPAN (if any) and the pServer (if any) to which the tape device is currently allocated.
Selecting an unallocated tape device activates the fields in the area 2. Choose New Allocation parameters:
None (Unallocated)
If selected, indicates that the tape device is not allocated to an LPAN.
LPAN lpan_name
If selected, indicates that the tape device is allocated to the LPAN currently displayed in the pull-down list.
Learn more about specific areas of this page:
• PAN Tapes
• Discovered Tapes (Not in PAN)
PAN Tapes
This area of the SCSI Tapes page displays all tape devices currently in the PAN, and lets you add tape device resources to the PAN, or remove tape device resources from the PAN.
Clicking a tape device’s device ID displays its characteristics in detail.
1-2
Clicking Add...
The Add tape(s) to PAN dialog box lists tape devices that PAN Manager has discovered but which do not reside in the PAN.
Clicking Remove...
The Remove tape(s) from PAN dialog box lists all tape devices in the PAN, and lets you place outside of the PAN one or more tape devices that are not already allocated to LPANs.
Discovered Tapes (Not in PAN)
This area of the SCSI Tapes page displays any tape device, discovered by PAN Manager, that is not currently in the PAN. If all discovered tape devices are automatically imported into the PAN, the message Discovered SAN devices are automatically imported into PAN appears here instead of specific tape devices.
Clicking Auto-Import...
In the Auto-Import to PAN dialog box, selecting the Auto-Import Discovered SAN devices to PAN check box ensures that any tape device PAN Manager discovers is automatically imported into the PAN.
Manage SCSI Tape Devices
Use the following PAN Manager procedures to manage tape devices within a PAN:
Scanning for New PAN Tape Resources
Manually Adding Discovered Tape Devices
Manually Removing Discovered Tape Devices
Allocating Tape Devices
Automatically Importing PAN Tape Devices
Editing a PAN Tape Device Description
1-3
Book Title
Manage SCSI Tape Devices (CLI)
Use the following PAN Manager commands to manage tape devices within a PAN:
tape -- Controls or lists operations on a tape device that is physically connected to a platform system and recognized by PAN Manager software.
pan -- Lists and modifies the PAN configuration.
1-4
Managing a SCSI Tape Device
(Resources > Tapes > SCSI Tape tape_device_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the SCSI Tape tape_device_name page:
Use this page to edit a tape device’s description or to assign the tape device to an LPAN.
About Managing a SCSI Tape Device
Manage a SCSI Tape Device
Manage a SCSI Tape Device (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing a SCSI Tape Device
The SCSI Tape tape_device_name page lists the physical characteristics of the tape device:
Type
The tape device’s vendor name, model number, and version information.
Unique ID
The tape device’s universal unique identifier.
Serial Number
The tape device’s vendor number.
LPAN
The name of the LPAN to which the tape device is allocated.
1-1
Book Title
Clicking Allocate...
The Change Tape Allocation dialog box lets you modify the tape device’s current allocation.
None
If selected, indicates that the tape device is not allocated to an LPAN.
LPAN lpan_name
If selected, indicates that the tape device is allocated to the LPAN currently displayed in the pull-down list.
You cannot allocate a tape device if it is already assigned to a pServer.
pServers
The name(s) of the pServer(s) to which the tape device is assigned. After you configure a tape device and assign it to a pServer, you can still use PAN Manager to reassign the same tape device (and its configuration) to a different pServer, LPAN, or pool.
IO Paths
Unlike disks which use redundant I/O subpaths, tape devices support only a single I/O subpath.
Clicking Edit...
The Edit Tape dialog box lets you enter a comment about the tape device or its purpose.
Clicking Allocate...
The Allocate Tape dialog box displays all tape devices in the PAN and allows you to allocate one or more available tape devices to an LPAN.
1-2
Manage a SCSI Tape Device
Use the following PAN Manager procedures to manage a specified tape device:
Viewing PAN Tape Devices
Editing a PAN Tape Device Description
Allocating Tape Devices
Manage a SCSI Tape Device (CLI)
Use the following PAN Manager command to manage a specified tape device:
tape -- Controls or lists operations on a tape device that is physically connected to a platform and recognized by PAN Manager software.
Use the following PAN Manager command to allocate or reallocate a tape device to an LPAN:
lpan -- Creates, lists, or modifies an LPAN configuration.
1-3
Book Title
1-4
Managing DVD-ROM Resources
(Resources > DVD-ROMs)
This page of the PAN Manager graphical user interface is for PAN Administrators only.
On the DVD-ROMs page:
This page lists all DVD-ROM drives in the entire PAN, and shows for which LPAN(s), if any, each is enabled.
About Managing DVD-ROMs
Manage DVD-ROM Access
Manage DVD-ROM Access (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing DVD-ROMs
This page lists all DVD-ROM resources in the entire PAN.
Each BladeFrame system provides two DVD-ROM drives, one on each Control Blade. The PAN Administrator can enable a DVD-ROM drive to one or more LPANs. (For an LPAN’s pServers to gain access to a DVD-ROM drive, the LPAN Administrator must also enable the drive on each pServer individually.) Only one pServer can use a DVD-ROM drive at any time.
Clicking LPAN Access...
The LPAN Access for DVD-ROMs dialog box lists all LPANs in the PAN, and the DVD-ROM drives that you can enable for each LPAN.
LPAN
This column lists all LPANs in the PAN. For each LPAN shown, you can use the two check boxes to enable or disable, respectively, all DVD-ROMs for all pServers in the
1-1
Book Title
LPAN.
DVD-ROMs
This column lists all DVD-ROM drives that you can enable. To enable a specific drive, select its check box.
Each DVD-ROM drive name is in the form (scsi)@MyPlatform/cn, where:
• scsi is the SCSI device name.
• MyPlatform is the name of the platform where the DVD-ROM drive resides.
• cn is the name of the Control Blade on which the DVD-ROM drive resides (c1 or c2).
Manage DVD-ROM Access
Use the following PAN Manager procedure to enable DVD-ROM access within a PAN:
Enabling the Physical DVD-ROM Drive
Manage DVD-ROM Access (CLI)
Use the following PAN Manager command to list DVD-ROM access within a PAN:
pan -- Lists and modifies the PAN configuration.
1-2
Networking
This section of the PAN Manager GUI Guide provides descriptions for viewing and managing network resources. Topics include:
• Viewing PAN Network Resources
• Managing a Virtual Switch
• Managing a Redundant Ethernet Interface
• Managing an Ethernet Interface
1-1
Book Title
1-2
Viewing PAN Network Resources
(Resources > Networking)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Some configuration tasks can only be performed by your PAN Administrator.
On the Network Resources page:
Lists the network resources for the entire PAN: Ethernet devices, redundant Ethernet devices, and vSwitches.
About PAN Network Resources
Manage PAN Network Resources
Manage PAN Network Resources (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About PAN Network Resources
This page lets you manage various network resources used to configure network connectivity within the platform, and to the external network.
Each platform has physical Ethernet interfaces (eths) on the:
• cBlade
The blades that provide the connection from the platform to the external network. Using PAN Manager, you combine two identical eths, one from each blade, to form a redundant Ethernet interface (rEth). This rEth lets you balance network I/O between the:
• cBlade
and provides a failover mechanism in the event of an eth or blade failure.
1-1
Book Title
Also using PAN Manager, you create a Virtual Switch (vSwitch), associate it with specific external networks (VLAN or non-VLAN), and then connect it to a rEth. You can then allocate the vSwitch to one or more LPANs to provide its pServers with internal or external (uplinked) network connectivity.
Learn more about specific areas of this page:
• Ethernet Devices
• Redundant Ethernet
• vSwitches
Ethernet Devices
This area of the Network Resources page displays the Ethernet interfaces available on:
• Control Blades
Clicking on the eth name displays the Ethernet page where you can manage the Ethernet interfaces.
Redundant Ethernet
This area of the Network Resources page lets you create redundant Ethernet interfaces (rEths). A rEth is formed in software from two identical physical Ethernet interfaces (eths) one from each:
• Control Blade
The rEth lets you balance network I/O between the blades and provides a failover mechanism in the event of an eth or blade failure.
The number of rEths you can create is limited by the number of physical Ethernet interfaces available. Each rEth requires two physical Ethernet interfaces.
1-2
Clicking on the rEth name displays the Redundant Ethernet page where you can manage the rEths.
Clicking Create...
The Create Redundant Ethernet dialog box lets you configure a redundant Ethernet interface. It contains the following fields:
Name
The name of the physical Ethernet interface.
Load Balancing Mode
The options for managing the incoming and outgoing network traffic on the platform.
Pair
(Default value) If selected, indicates that incoming and outgoing traffic is sent and received on a single:
cBlade
From the Primary Interface scroll list, select the Ethernet interface that will send and receive network traffic.
Static
Incoming and outgoing traffic is statically divided between the two network blades. Traffic is assigned to one blade or the other based on the pServer’s vEth MAC address. Traffic from even-numbered MAC addresses is assigned to one blade; traffic from odd-numbered MAC addresses is assigned to the other blade.
For more information about load balancing, see PAN Manager Administrator’s Guide.
MTU
The Maximum Transmission Unit (in bytes) allowed is 1500. You cannot change this value.
Flow Control
1-3
Book Title
If the external network in which the platform resides is using the multicast network protocol, under heavy network traffic, some network configurations allow packets to be dropped silently. To prevent this from happening, you can activate network flow control, which regulates packet exchange between the BladeFrame internal components.
This setting activates flow control implicitly for a specific redundant Ethernet interface, whether explicit flow control is configured for the entire PAN.
NOTE: Flow control is not supported for pServers that are running the Microsoft Windows® operating system.
Ethernet Device Membership
Each column (Network Interface 1 and Network Interface 2) lists the physical Ethernet interfaces (eths) on:
– cBlades
Ethernet Device
The device name of the eth, in the form eth1@MyFrame/cn where eth1 is the device name, MyFrame is the name of the platform, and cn is the Control Blade that contains the device (c1 or c2).
Driver
The type of Network Interface Controller (NIC) driver for this Ethernet interface.
Supports NICs with speeds of 10/100/1000 or 1GigE.
Clicking Delete...
The Delete Redundant Ethernet dialog box lets you delete one or more rEths.
1-4
vSwitches
This area of the Network Resources page lets you create and delete the PAN’s Virtual Switches (vSwitches). (To edit a vSwitch, click its name to display the vSwitch vswitch_name page.)
A Virtual Switch provides the network connectivity between pServers, and, if configured, between pServers and the external network. The PAN Administrator creates a vSwitch, connects it to a rEth, and then allocates it to one or more LPANs to provide the LPAN’s pServers with internal or external (uplinked) network connectivity.
Clicking Create...
The Create vSwitch dialog box lets you configure a vSwitch. This dialog box contains the following fields:
vSwitch Name
The name of the Virtual Switch.
Uplink
If selected, lets you select a redundant Ethernet (rEth) interface through which the vSwitch connects to the external network. (If not selected, the vSwitch only handles network traffic that is internal to the platform.)
Device
The list of available rEths.
Driver
The Network Interface Controller (NIC) type of this rEth’s two Ethernet interfaces.
VLAN
A unique identifier for a Virtual LAN to which the vSwitch is uplinked. (e100 drivers do not support VLANs.)
1-5
Book Title
Manage PAN Network Resources
Use the following PAN Manager procedures to manage network resources:
Viewing the Network Topology with PAN Manager
Creating a New vSwitch
Deleting a vSwitch
Creating a rEth
Deleting a rEth
Manage PAN Network Resources (CLI)
Use the following PAN Manager commands to manage network resources:
eth -- Creates, lists, or modifies the configuration for a physical Ethernet controller on a:
• cBlade
pan -- Lists and modifies the PAN configuration.
reth -- Creates, lists, or modifies a redundant Ethernet (rEth) configuration.
sw -- Creates, lists, or modifies the configuration for a Virtual Switch (vSwitch).
1-6
Managing a Virtual Switch
(Resources > Networking > vSwitches > vswitch_name)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Some configuration tasks can only be performed by your PAN Administrator.
On the vSwitch vSwitch_name page:
This page lets you manage internal and externally connected Virtual Switches (vSwitches) that the LPAN Administrator uses to create networks in the LPAN.
About Managing a Virtual Switch
Manage a Virtual Switch
Manage a Virtual Switch (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Managing a Virtual Switch
Only the PAN Administrator can add Virtual Switches (vSwitches) to an LPAN. A vSwitch provides connectivity among pServers for network traffic that is internal to the platform. Attaching the vSwitch to an uplink allows it to manage network traffic that passes between an internal network and the external network to which the platform is connected.
Each vSwitch is defined by the following characteristics:
vswitch_name
(In the left portion of the page) The name that you assigned to the vSwitch. Directly above the name of the vSwitch is the name of the redundant Ethernet interface (rEth) to which the vSwitch is attached, and in parentheses, the VLAN ID (if any) with which the rEth’s uplink is associated.
1-1
Book Title
Uplink Device
The name of the redundant Ethernet interface (rEth) to which the vSwitch is attached, and the Ethernet network interface controllers (NICs) that the rEth is using.
Uplink VLAN
A unique identifier for the virtual LAN (if any) to which the vSwitch is uplinked. (e100 drivers do not support VLANs.)
LPANs
All LPANs to which the vSwitch is currently allocated. To allow pServers in two different LPANs to communicate with each other, add a specific vSwitch to both LPANs.
Clicking Allocate...
The Allocate vSwitch to LPANs dialog box lets you make this vSwitch resource available to one or more LPANs.
pServers
All pServers that are connected to the vSwitch, in the form lpan_name/pserver_name:veth#, where:
lpan_name is the name of the LPAN.
pserver_name is the name of the pServer.
veth# is the name of the virtual Ethernet interface (vEth) through which the pServer is connected to the vSwitch.
Clicking Edit...
The Edit vSwitch uplink dialog box lets you modify the way in which the vSwitch connects to the external network.
Caution: Changing a vSwitch’s configuration might cause communication errors on running pServers.
The Edit vSwitch uplink dialog box has the following fields:
1-2
Uplink
If selected, lets you select a redundant Ethernet (rEth) interface through which the vSwitch connects to the external network. (If not selected, the vSwitch only handles network traffic that is internal to the platform.)
Device
The name of the rEth.
Driver
The Network Interface Controller (NIC) type of this rEth’s two Ethernet interfaces.
VLAN
A unique identifier for a virtual LAN to which the vSwitch is uplinked. (e100 drivers do not support VLANs.)
Manage a Virtual Switch
Use the following PAN Manager procedures to create a vSwitch:
Creating a New vSwitch
Modifying a vSwitch
Deleting a vSwitch
Allocating vSwitches
You can configure a vSwitch that is configured with a Redundant Ethernet (rEth) connection to handle VLAN- or non-VLAN-tagged network traffic. To have non-VLAN-tagged network traffic flow over a rEth, configure only one vSwitch to use this rEth.
Manage a Virtual Switch (CLI)
Use the following PAN Manager commands to manage a vSwitch:
lpan -- Creates, lists, or modifies an LPAN configuration.
sw -- Creates, lists, or modifies the configuration for a Virtual Switch.
1-3
Book Title
1-4
Managing a Redundant Ethernet Interface
(Resources > Networking > reth_name)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Some configuration tasks can only be performed by your PAN Administrator.
On the Redundant Ethernet reth_name page:
This page displays detailed information about the selected Redundant Ethernet interface (rEth) and lets you manage its configuration.
About Redundant Ethernet Interfaces
Manage Redundant Ethernet Interfaces
Manage Redundant Ethernet Interfaces (CLI)
About Redundant Ethernet Interfaces
This page lets you manage the Redundant Ethernet interfaces (rEths).
Clicking Modify...
The Modify rEth Settings dialog box displays the following fields:
Load Balancing Mode
The options for managing the incoming and outgoing network traffic on the platform.
Pair
(Default value) If selected, indicates that incoming and outgoing traffic is sent and received on a single:
cBlade
From the Primary Interface scroll list, select the Ethernet interface that will send and receive
1-1
Book Title
network traffic.
The Ethernet interface you do not select remains ready to handle all network I/O if the primary interface experiences a failure.
Static
Incoming and outgoing traffic is statically divided between the two network controller blades. Traffic is assigned to one blade or the other based on the pServer’s vEth MAC address. Traffic from even-numbered MAC addresses is assigned to one blade; traffic from odd-numbered MAC addresses is assigned to the other blade.
For more information about load balancing, see PAN Manager Administrator’s Guide.
Flow Control is on
This setting activates flow control implicitly for a specific rEth, whether explicit flow control is configured for the entire PAN.
MTU
The Maximum Transmission Unit (in bytes) allowed is 1500. You cannot change this value.
Failover Detection Mode
The options for detecting failure:
Link
(Default value) If selected, indicates that link status mode will be used. (Link status mode determines the health of the network connection based on the status of the Ethernet interface’s link.)
Ping
If selected, indicates that ping mode will be used. (Ping mode determines the health of the network connection based on ICMP ECHO_REQUEST and ICMP_ECHO REPLY packets.)
1-2
These fields describe the rEth's characteristics:
Load Balance Policy
The policy for managing the incoming and outgoing network traffic on the platform between the:
• cBlades
Pair
(Default value) Indicates that incoming and outgoing traffic is sent and received on a single:
– cBlade
Static
Incoming and outgoing traffic is statically divided between the two network controller blades. Traffic is assigned to one blade or the other based on the pServer’s vEth MAC address. Traffic from even-numbered MAC addresses is assigned to one blade; traffic from odd-numbered MAC addresses is assigned to the other blade.
Eth Driver Type
The Network Interface Controller (NIC) type of this Ethernet interface. The speeds are: 10/100/1000 or 1GigE.
Flow Control
If the external network in which the platform resides is using the multicast network protocol, under heavy network traffic, some network configurations allow packets to be dropped silently. To prevent this from happening, you can activate network flow control, which regulates packet exchange between the BladeFrame internal components.
This setting activates flow control implicitly for a specific redundant Ethernet interface, whether explicit flow control is configured for the entire PAN.
1-3
Book Title
NOTE: Flow control is not supported for pServers that are running the Microsoft Windows® operating system.
Failover Detection
The mode for failover detection:
Link
(Default value) Indicates that link status mode will be used.
Ping
Indicates that ping mode will be used.
MTU
The Maximum Transmission Unit (in bytes) allowed is 1500. You cannot change this value.
Uplinks
A unique identifier for the virtual LAN (if any) to which the vSwitch is uplinked. (e100 drivers do not support VLANs.)
Interface 1 Ethernet Device
An Ethernet interface that sends and receives network traffic. The Ethernet interface you do not select remains ready to handle all network I/O if the primary interface experiences a failure.
Interface 2 Ethernet Device
An Ethernet interface that sends and receives network traffic. The Ethernet interface you do not select remains ready to handle all network I/O if the primary interface experiences a failure.
Manage Redundant Ethernet Interfaces
The following procedures are required to create, modify, or delete a Redundant Ethernet (rEth) resource:
Modifying a rEth
1-4
Activating Ping Failover Detection Mode on a rEth
You must have the PAN Administrator role to perform these tasks.
You can modify certain rEth settings such as:
• Flow Control enabled or disabled
• Its “primary” interface
• Load-balancing mode
any time after you create it. However, be aware that any modifications to an existing rEth will affect all vSwitches currently uplinked to the rEth.
For rEths in Pair mode, when rEth failover is followed by rEth failback to the original configuration (the default behavior), there can be an interruption of service if there is an interval between the time that the external link is re-established and the time that the external network is fully configured. To avoid this kind of interruption of service, you can disable automatic rEth failback by configuring the rEth’s Primary Interface to none.
Manage Redundant Ethernet Interfaces (CLI)
Use the following PAN Manager command to manage network resources:
reth -- Creates, lists, or modifies the configuration for a redundant Ethernet (rEth) configuration.
1-5
Book Title
1-6
Managing an Ethernet Interface
(Resources > Networking > eth_name)
Depending on your administrative role, some information on this page of the PAN Manager graphical user interface might not appear. Some configuration tasks can only be performed by your PAN Administrator.
On the Ethernet eth_name page:
This page displays detailed information about the selected Ethernet interface (eth) and allows you to manage its configuration.
About Ethernet Interfaces
Manage Ethernet Interfaces
Manage Ethernet Interfaces (CLI)
About Ethernet Interfaces
This page lets you manage the Ethernet interfaces (eths) on:
• cBlades
that provide the connection from the platform to the external network.
Clicking Failover Settings...
The Modify Failover Detection Settings dialog box lets you configure failover settings. Assign an IP address on the private network for each Ethernet device on the:
• cBlade
The IP address of the Ethernet device must be able to contact the IP address to be pinged.
The dialog box displays the following fields:
Network Stack
IP Address: The IP address of the Ethernet device to be
1-1
Book Title
used for connectivity testing. Use a different IP address for each Ethernet device.
Netmask: The netmask of the Ethernet device
Gateway: The gateway used by the ping failover detection.
VLAN: The VLAN id if applicable
MAC Address: Select either Use existing hardware MAC address or Specify custom MAC address
Ping failover settings:
Ping IP address: The IP address external to the platform to be pinged.
Missed Ping Count Threshold: The number of consecutive missed ICMP echo replies that result in a failure in the given time threshold. Default is 3.
Missed Ping Time Threshold: The amount of time in milliseconds in which the given number of missed ICMP echo replies need to occur before a failure is detected. Default is 5000. The minimum Ping Threshold value is 1000 ms (1 second). A threshold value below 1000 ms is not valid.
Note: 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..
These fields describe the eth's characteristics:
Membership
The rEth(s) that the eth belongs to.
Driver Type
The Network Interface Controller (NIC) type of this Ethernet interface. The speeds are: 10/100/1000 or 1GigE.
MAC Address
1-2
The unique 48-bit Ethernet address of the interface, also known as a hardware or media access control (MAC) address.
Ping Failover Detection Settings
This functionality allows administrators to configure rEths to report Ethernet device failures based on ping results.
Manage Ethernet Interfaces
The following procedures are required to configure or specify settings on an Ethernet interface (eth):
Checking or Naming Connectivity Setting
Setting the Ping Mode Parameters
You must have the PAN Administrator role to perform these tasks.
You may specify certain uplink settings on an eth, however they are informational only and should reflect the physical settings of your network.
You may also configure an eth’s failover detection mode.
Manage Ethernet Interfaces (CLI)
Use the following PAN Manager command to manage ethernet resources:
eth -- Creates, lists, or modifies the configuration for a physical Ethernet controller.
1-3
Book Title
1-4
LPANs
This section of the PAN Manager GUI Guide provides descriptions for viewing and managing LPANs and pServers. Topics include:
• Viewing Logical Processing Area Networks (LPANs)
• Managing an LPAN
• Managing a Hypervisor
• High Availability
1-1
Book Title
1-2
Viewing Logical Processing Area Networks (LPANs)
(LPANs)
On the LPANs page:
If you logged on using the Processing Area Network (PAN) Administrative Role: this page lists all LPANs in the entire PAN.
If you logged on using the LPAN Administrative Role: this page lists all LPANs for which you have LPAN Administrator privileges.
About LPANs
Maintenance LPAN
Manage LPANs
Manage LPANs (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About LPANs
The PAN Administrator can create new LPANs, manage existing LPANs, and delete LPANs. An LPAN consists of resources: Processing Blades, disk storage devices, Virtual Switches (vSwitches), and (optionally) one or more media drives.
Using these resources, the LPAN Administrator creates pServers, and then connects them to vSwitches to create networks.
The LPAN Administrator can also configure applications on the pServers, and enable them for failover and high availability.
Maintenance LPAN
The Maintenance LPAN is an area administrators can use for diagnostic and maintenance purposes. It is automatically created each time PAN Manager starts. The display name for this LPAN is .maint. It appears as the first LPAN on the LPANs page. There is one Maintenance LPAN in each PAN.
1-1
Book Title
The Maintenance LPAN has the same interface as other LPANs; however, it does have a few restrictions:
• You cannot change the name, .maint.
• You cannot change the description.
• You cannot delete this LPAN.
• You can configure a local pool in .maint, but it cannot obtain additional pBlades from the global pool.
Manage LPANs
Use the following PAN Manager procedure to manage an LPAN:
Creating an LPAN
Using the Maintenance LPAN
Manage LPANs (CLI)
Use the following PAN Manager command to manage an LPAN:
lpan -- Creates, modifies, or deletes an LPAN configuration.
1-2
Managing an LPAN
(LPANs > lpan_name)
This page of the PAN Manager graphical user interface is for PAN Administrators and LPAN Administrators, Operators, and Monitors only.
On the LPAN lpan_name page:
This page displays the resources allocated to the current LPAN. It also lets you modify the resource allocations of an existing LPAN.
About Configuring an LPAN
Controls for Managing an LPAN
Maintenance LPAN
Configure an LPAN
Configure an LPAN (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Configuring an LPAN
This page lets you manage an existing LPAN. An LPAN consists of physical and virtual components that the PAN Administrator allocates to the LPAN Administrator. An LPAN Administrator then uses these resources to create pServers, and connects the pServers by means of Virtual Switches (vSwitches).
Clicking Edit...
The Edit LPAN dialog box lets you rename the LPAN or modify its description.
1-1
Book Title
Clicking Domain Settings...
Clicking the Domain Settings button displays the Domain Settings page for the LPAN where the PAN or LPAN Administrator can configure the event settings, SNMP Agents and Managers, and assign a user to the LPAN Administrator role.
Clicking High Availability...
Clicking the High Availability button displays the High Availability page, which lets you manage applications and application resources in the LPAN.
Learn more about specific areas of this page:
• pServers
• Blades
• Local pBlade Pools
• SCSI Disks
• SCSI Tape
• vSwitches
• DVD-ROMs
pServers
This area of the LPAN page lets you create and manage the pServers that run in the LPAN.
Clicking a pServer’s name displays the pServer’s configuration in detail.
Clicking Create...
The Create pServer dialog box lets you specify the pServer’s name, and (optionally) begin configuring the pServer immediately.
1-2
Clicking Delete...
The Delete pServer dialog box lets you delete one or more pServers from the LPAN. To delete a pServer, the pServer must be shutdown.
To delete on these platforms, you cannot have any applications, load balancers, or failover policies associated with it.
When you delete a pServer that has disks with SCSI-3 persistent reservations enabled, PAN Manager deletes the SCSI-3 reservations that were associated with the pServer.
The Delete pServer dialog box contains the following fields:
Name
The pServer’s name.
HA Use
The names and types of high-availability (HA) applications and application resources currently configured on the pServer.
State
The current operating state of the pServer, typically Booted or Shutdown.
Clicking Boot Order...
The Configure pServer Boot Order dialog box lets you set the order in which the pServers in the LPAN boot when the LPAN restarts. This dialog box contains the following fields:
Order
The numeric order in which a pServer starts. (The pServer with the lowest number boots first; the highest boots last. pServers that have the same boot order number boot simultaneously.)
Name
The pServer’s name.
1-3
Book Title
State
The current operating state of the pServer, typically Booted or Shutdown.
Clicking Show Hypervisors...
The Toggle Hypervisor Display dialog box lets you turn on the display of hypervisors in all LPANs (for your current PAN Manager session). PAN Manager will display the current LPAN’s hypervisors in the pServers area (at the end of the list).
The dialog box prompts you to confirm your request. To proceed, click Submit, otherwise, click Cancel.
When the pServers area displays hypervisors, you can click a hypervisor name to view its details.
Clicking Hide Hypervisors...
The Toggle Hypervisor Display dialog box lets you turn off the display of hypervisors in all LPANs. PAN Manager will hide the current LPAN’s hypervisors in the pServers area. (This is the default whenever you start a PAN Manager session.)
The dialog box prompts you to confirm your request. To proceed, click Submit, otherwise, click Cancel.
The Show/Hide Hypervisors buttons appear only if the LPAN includes at least one hypervisor.
Clicking Group Hypervisors...
The Group Hypervisors dialog enables you to group hypervisors. You must turn on this setting to use the vBlades migration feature in this LPAN. Grouping enables the hypervisors in the LPAN to interact so they can support migration operations for guests across their vBlades.
Note: Before you can group or ungroup the hypervisors in an LPAN, all of the hypervisors in that LPAN must be shut down.
For more information, see Using vBlades.
1-4
The Group Hypervisors button appear only if the LPAN includes at least one hypervisor.
Blades
This area of the LPAN page lets you obtain and manage processing resources (Processing Blades, or pBlades and Virtual Blades, or vBlades) for the LPAN.
If a pBlade associated with an LPAN is physically removed from the chassis, or if the pBlade becomes functionally unavailable to the LPAN, the pBlade name appears in red.
Clicking Add...
The Add pBlades to LPAN dialog box lists all Processing Blades in the PAN that are not currently allocated to another LPAN or to the global pBlade pool.
This dialog box contains the following fields:
Name
The name of the Processing Blade, in the form MyFrame/pn, where MyFrame is the name of the platform, and n indicates the physical location of the pBlade in the chassis.
In the Manual Entry field, you can also specify a name of your own choosing for a pBlade, in the standard MyFrame/pn format.
CPU/Speed/RAM
The number of processors in the pBlade, its clock speed in MegaHertz (MHz), and its random access memory in gigabytes (GB).
The smallest processing unit that you can allocate to an LPAN is a pBlade. vBlades are automatically allocated to an LPAN when their host pBlade is allocated.
1-5
Book Title
Clicking Remove...
The Remove pBlades from LPAN dialog box lists all pBlades currently allocated to the LPAN. This dialog box contains the following fields:
Name
The name of the Processing Blade, in the form MyFrame/pn where MyFrame is the name of the platform, and n indicates the physical location of the pBlade in the chassis.
CPU/Speed/RAM
The number of processors in the pBlade, its clock speed in MegaHertz (MHz), and its random access memory in gigabytes (GB).
Allocations
The pServer to which a pBlade is currently assigned, and whether the pBlade is the pServer’s primary or failover pBlade.
You can remove a pBlade from the LPAN only if the pBlade is not currently assigned to a pServer.
Local pBlade Pools
This area of the LPAN page lets you create and manage a local pool of pBlades and to enable or restrict the LPAN’s access to a PAN-wide (global) pool of pBlades.
Clicking Create...
The Create LPAN Local Pool dialog box lets you specify the Name and Description of the local pool, and optionally proceed to the Pool page to begin configuring the pool.
Clicking Delete...
The Delete LPAN Local Pools dialog box lets you delete a pool. It displays the following fields:
1-6
Name
The Name of the pool.
Blades
The number of pBlades in the pool.
pServer Assignment
The name of the pServer currently using that blade.
Clicking Global Pool Access...
The Configure Global Pool Access dialog box lets you allow access to global pools from this LPAN. This dialog box displays the following fields:
Access
If selected, pServers may obtain a failover blade from the global pool.
Boot
If selected, a pServer can boot on a blade from the global pool.
Name
The name of the global pool.
Blades
The number of blades in the global pool.
Local Pool Links
The LPANs that currently have access to this global pool.
SCSI Disks
This area of the LPAN page lets you obtain and manage disk storage resources for pServers in the LPAN. If a disk becomes functionally unavailable to the LPAN, the disk’s name appears in red with an accompanying caution symbol and error (NOT IN PAN).
1-7
Book Title
Clicking Add...
The Add SCSI Disks to LPAN dialog box lets you allocate one or more disks to the LPAN. This dialog box contains the following fields:
SCSI Disk
The device ID of the disk.
Details
The disk’s storage capacity in gigabytes (GB), and its manufacturer, model, and revision number.
Allocation LPAN
The name of the LPAN, if any, to which the disk is currently allocated.
Clicking Remove...
The Remove SCSI Disks dialog box lets you remove one or more disks from the LPAN. After a disk is removed, it is available for use in another LPAN.
This dialog box contains the following fields:
SCSI Disk
The device ID of the disk.
pServers
The name of the pServer that the disk is associated with, and the disk’s virtual device address, in the form (x.y). This sequence number determines the ordering on a pServer that has multiple disks: for example, disk 1.0 precedes disk 3.0.
Other Use
The names and types of high-availability (HA) file system resources currently configured on the disk.
You can remove a disk only if it is neither connected to a pServer nor associated with any high-availability file system resources.
1-8
SCSI Tape
This area of the LPAN page lets you obtain and manage tape storage resources for pServers in the LPAN. If a tape becomes functionally unavailable to the LPAN, the tape’s name appears in red with an accompanying caution symbol and error (NOT IN PAN).
Clicking Add...
The Add SCSI Tapes to LPAN dialog box lets you allocate one or more tapes to the LPAN. This dialog box contains the following fields:
Tapes
The device ID of the tape.
Details
The tape’s manufacturer, model, and revision number.
Allocation LPAN
The name of the LPAN, if any, to which the tape is currently allocated.
Clicking Remove...
The Remove SCSI Tape dialog box lets you remove one or more tapes from the LPAN. After a tape is removed, it is available for use in another LPAN.
This dialog box contains the following fields:
Tapes
The device ID of the tape.
pServers
The name of the pServer that the tape is associated with, and the tape’s virtual device address, in the form (x.y). This sequence number determines the ordering on a pServer that has multiple tapes: for example, disk 1.0 precedes disk 3.0.
1-9
Book Title
You can remove a tape only if it is not connected to a pServer.
vSwitches
This area of the LPAN page lets you obtain and manage existing PAN network resources (Virtual Switches, or vSwitches) for pServers in the LPAN. (It is possible for a vSwitch to belong to multiple LPANs.)
Clicking Add...
The Add vSwitch to LPAN dialog box lets you allocate a vSwitch to the LPAN. This dialog box contains the following fields:
Name
The name of the vSwitch.
Uplink
The name of the redundant Ethernet interface (rEth) through which the vSwitch is connected to the external network. If a vSwitch is not uplinked, it cannot manage network traffic to and from the platform.
Assigned LPANs
The LPAN(s), if any, to which the vSwitch is allocated.
Clicking Remove...
The Remove vSwitches dialog box lets you remove one or more vSwitches from the LPAN. This dialog box contains the following fields:
Name
The name of the vSwitch.
Uplink
The name of the redundant Ethernet interface (rEth) through which the vSwitch is connected to the external network. If a vSwitch is not uplinked, it cannot manage network traffic
1-10
to and from the platform.
pServers
The name of the pServer(s) currently connected to the vSwitch, and the virtual Ethernet interface (vEth) through which each is connected.
HA Use
The names and types of high-availability (HA) network resources for which the pServer is currently using the vSwitch.
You can remove a vSwitch only if it is neither connected to a pServer nor associated with any high-availability network resources.
DVD-ROMs
This area of the LPAN page lets you make the DVD-ROM drives in the Control Blades available for use in the LPAN. Enabling a DVD-ROM drive for an LPAN makes it available to all pServers in the LPAN that exist on the same physical platform as the DVD-ROM drive; disabling a DVD-ROM drive for an LPAN makes it unavailable to all pServers in the LPAN.
Clicking Enable/Disable...
The Enable/Disable DVD-ROM Access dialog box displays both BladeFrame DVD-ROM drives.
Name
In the form scsi@MyPlatform/cn, where scsi is the device ID of the drive, MyPlatform is the name of the BladeFrame, and n is the slot number of the cBlade on which the drive resides (c1 or c2).
Model
The DVD-ROM drive’s model and revision number.
1-11
Book Title
Controls for Managing an LPAN
The bottom border of the LPAN lpan_name page has controls for managing the current LPAN:
Boot LPAN
Causes the LPAN’s pServers to power up, boot-load their operating systems, and run their initialization scripts.
Shutdown
Causes the LPAN’s pServers to be shut down, and their pBlades to be powered off.
Reboot LPAN
Causes the LPAN’s pServers to shut down, boot-load their operating systems, and run their initialization scripts.
Maintenance LPAN
The Maintenance LPAN is an area administrators can use for diagnostic and maintenance purposes. It is automatically created each time PAN Manager starts. The display name for this LPAN is .maint. It appears as the first LPAN on the LPANs page. There is one Maintenance LPAN in each PAN.
The Maintenance LPAN has the same interface and behavior as other LPANs; however, it does have a few restrictions:
• You cannot change the name, .maint.
• You cannot change the description.
• You cannot delete this LPAN.
• You can configure a local pool in .maint, but it cannot obtain additional pBlades from the global pool.
1-12
While in the.maint LPAN:
• The pBlade appears as Not available in PAN in its original LPAN.
• You can still configure the pBlade (assign to a pServer) in its original LPAN.
• You can allocate or deallocate the pBlade to other LPANs.
Like with any other LPAN:
• You cannot share SCSI disks between .maint and a different LPAN.
• You can managed it only if your the .maint LPAN administrator or the PAN Administrator.
Disaster recovery of the .maint LPAN is the same as other LPANs. If any pBlades were in the .maint LPAN when you restore the archive, they remain in .maint and are marked as Out of Service.
Configure an LPAN
Use the following PAN Manager procedures to configure an LPAN
Booting an LPAN
Rebooting an LPAN
Shutting Down an LPAN
Creating an LPAN
Allocating pBlades
Allocating Disk Resources
Allocating Tape Devices
Allocating vSwitches
Enabling the Physical DVD-ROM Drive
Using the Maintenance LPAN
1-13
Book Title
Some of these tasks require the PAN Administrator role; others require the LPAN Administrator role.
Configure an LPAN (CLI)
Use the following PAN Manager command to configure an LPAN:
lpan -- Creates, lists, or modifies an LPAN configuration.
1-14
Managing a Hypervisor
(LPANs > lpan_name > hypervisor)
On the platform_name/pn Hypervisor page:
Use this page to display the characteristics of the hypervisor software that enables you to use vBlades. When you use vBlades, you can allocate a pBlade processing resource in a more granular way.
About Hypervisor Characteristics
Controls for a Hypervisor
Manage a Hypervisor
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Hypervisor Characteristics
The following are the identifying characteristics of a Hypervisor:
Clicking Advanced Configuration...
The Advanced pServer Configuration dialog box displays the following headings and fields:
UUID
PAN Manager generates the Universally Unique Identifier (UUID) for pServers.
Firmware Options:
You can configure firmware option settings on each hypervisor. The options have the following states:
– Default — The hypervisor uses the hardware default setting of the pBlade.
– Enabled — The hypervisor can run the option if its pBlade supports it.
1-1
Book Title
– Disabled — The hypervisor does not run the option.
You can see the current state in the Current Status column. Use the Configuration drop-down list to change the state.
The firmware settings are only applicable to the hypervisor pServers booted on pBlades that support the associated hardware feature. You cannot, for example, enable hyperthreading when a pServer is booted on a pBlade that does not support hyperthreading. If the pBlade does not support the option, it displays as “N/A” in the Current Status column.
You can make firmware option changes at any time but they will not take effect until the next reboot.
Hyperthreading
This is useful when considering the processing needs of the applications that run on the pServer. By default, hyperthreading is configurable (the Disable hyperthreading in firmware check box is cleared).
A pServer can run in hyperthreading mode if its pBlade supports it and its operating system has it enabled (by means of boot arguments).
Node Interleaving
This option uses the hardware features of certain pBlades to interleave a single page of memory from each processor at a time.
Virtualization Extensions
Hypervisors use these extensions so that guest operating systems can use virtual device drivers to access the vBlade processing resource on a pBlade.
Hardware Prefetch
This option uses the hardware features of certain pBlades to bring data and instructions into higher-speed memory before the processor needs it to minimize latency. The hardware prefetch option
1-2
can improve the performance of pServers running Oracle applications.
For more information about Firmware options, see PAN Manager Administrator’s Guide.
frame_name/pn Hypervisor
The page’s top banner displays the name of the platform system (such as My_frame) and the physical location of the pBlade in the chassis (such as p2) on which the hypervisor resides. The slot number appears next to the component on the chassis rail.
Blade
The pBlade used by the hypervisor.
Hypervisor ISO
The current image being used by the hypervisor
Version information for the hypervisor.
Hypervisor Description
A description of the hypervisor.
LPAN group status
If this hypervisor is the group master for its LPAN, this field displays: Current master. If this hypervisor is a group slave, then a link is provided to the group master hypervisor.
Uptime
The time (expressed in days, hours, and minutes) that the hypervisor has been running since it was in a powered down state.
Internal Name
1-3
Book Title
PAN Manager automatically generates a name for each hypervisor. The name is based on the platform and pBlade where that hypervisor runs. The format is:_hv-platformname-pn
where:
• _hv- indicates that this is a generated hypervisor name.
• platformname-pn is the platform name and the name of the pBlade (such as p5) that hosts this hypervisor.
Boot Image
The display name of the hypervisor boot image. The selected radio button indicates the hypervisor’s currently configured boot image; the PAN’s default boot image appears in bold and is marked with an asterisk (*).
SCSI Disks
This area of the page shows the physical storage components allocated to the hypervisor, including its logical and physical characteristics.
Unit
The pServer unit number for this SCSI disk.
ID
The device ID of the disk.
Size
Total size of the physical disk.
Details
The manufacturer and model type of the disk.
vEths
This area of the page shows the network interfaces available to the hypervisor. Each vEth connects a pServer to a vSwitch.
1-4
Name
The display name of the vEth.
vSwitch
The available vSwitches that the vEths connect the hypervisor to.
MAC
The software Media Access Control (MAC) address associated with the network resource.
IP Addresses
The IP address of the network resource. This is the address at which an application service makes itself available to the network.
Virtual CDs
This area of the page shows the available virtual CDs. VCDs are devices pServers and hypervisors use to access media images registered with PAN Manager. PAN Manager attaches a VCD to pServers and hypervisors during start up.
Unit
The pServer unit number for this virtual CD.
Media
The ISO image of each CD stored on the cBlade.
Controls for a Hypervisor
The bottom border of the platform_name/pn Hypervisor page has controls (Boot, Reboot, Shutdown, and Console). The Boot, Reboot, and Shutdown buttons are disabled on the Hypervisor page. Use the buttons on the Hypervisor’s pBlade page to perform those operations.
Console
1-5
Book Title
Opens a window in which you can type console input to the hypervisor, and which displays console output. The console displays the same output as would appear on the console of a conventional standalone computer, such as informational messages that the operating system generates during boot and shutdown operations.
De-configure the hypervisor
Cancels a hypervisor configuration for a pBlade. After you do this, the pBlade will no longer 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). You can use a pBlade without a hypervisor to boot a regular pServer, but it does not support vBlades.
Manage a Hypervisor
To perform hypervisor control operations, see the Administering vBlades chapter in Using vBlades.
1-6
High Availability This section of the PAN Manager GUI Guide provides descriptions for managing high-availability applications. Topics include:
• Managing High-availability Applications
• Creating High-availability Applications
• Creating High-availability Load Balancing
• Managing Executable Resources for Applications
• Managing Failover Policy Resources for Application Services
• Managing Health Monitor Resources for Application Services
• Managing Network Resources for Application Services
• Managing Network File System Resources for Applications
• Managing SCSI File System Resources for Applications
1-1
Book Title
1-2
Managing High-availability Applications
(LPANS > lpan_name > High Availability)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the High Availability for LPAN lpan_name page:
An LPAN’s application services under PAN Manager control consist of applications and their supporting resources. The goal is to configure application services to be highly available.
About Applications and High Availability
Configure High-availability Applications
Configure High-availability Applications (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Applications and High Availability
This page provides a top-level view for managing high-availability applications. Essentially, high availability consists of application services (applications and load-balancing services), and the application resources that support them.
Associating the proper application resources with application services allows those services to run with minimal down time for long periods of time.
For applications, configure them to continue processing on a failover pServer if the primary pServer fails. To do this, use PAN Manager to specify a failover policy to run the same application, to respond at the same IP address, and to have access to the same application data. (See Applications.)
1-1
Book Title
For load balancers, configure each application that is a member of a load balancer to run an instance of the same application, and to share incoming client requests for the service that the application provides. (See Load Balancers.)
Learn more about specific areas of this page:
• Applications
• Load Balancers
• Executable Resources
• Failover Policy Resources
• Health Monitor Resources
• Network Resources
• Network File System Resources
• SCSI File System Resources
To configure a user-defined monitor for monitoring an application or a load balancer, in the left pane, click LPANs > LPANname > High Availability, click the Monitor tab at the top of the page, and then scroll down to the User Defined Monitors area.
Clicking Templates...
The Extract Template dialog box lets you make available to the current LPAN a predefined set of resources for applications and load balancers to use.
Name
If selected, the application template is available for use by applications and load balancers in the current LPAN.
Tag
Indicates that an application resource was created using an application template.
1-2
Applications
This area of the High Availability for LPAN lpan_name page lets you manage applications that are available to pServers in the current LPAN.
You can add or remove resources while a service is running; however, you cannot modify a resource while a service is running. For example, you can add a SCSI disk to a running application service, but you cannot change a mount point with a running application service.
Clicking Create...
The Create Application dialog box lets you specify a name for a new application. (Choose a meaningful name to help other administrators easily identify the application.)
Selecting the check box labeled Proceed directly to Application page after creation lets you configure immediately the resources and failover behavior of the application.
Clicking Delete...
The Delete Applications dialog box lets you remove one or more applications for pServers in the current LPAN. You can delete an application only if it is Stopped. This dialog box displays the following fields:
Name
The name of the application.
Membership
Standalone indicates that the application is not a member of a load-balancing service. A value other than Standalone indicates the name of the application load-balancing service of which the application is a member.
Current pServer
The pServer on which the application is either Started or
1-3
Book Title
Starting. If no current pServer appears, it means that the application is Stopped.
Status
The current run state of the application, such as Started or Stopped.
Load Balancers
This area of the High Availability for LPAN lpan_name page lets you manage applications, each of which serves as an application load balancer for multiple cooperating instances of a specific application.
The load balancer forwards incoming requests to its member instances to allow for sustained performance. The load balancer runs on a pServer; each member application instance must always run on a pServer other than the load balancer’s pServer, and run on a separate pServer.
Clicking Create...
The Create Load Balancer dialog box lets you specify a name for a load-balancing service. (Choose a meaningful name to help other administrators easily identify the load balancer.)
Selecting the check box labeled Proceed directly to Load Balancer page after creation lets you configure immediately the resources and failover behavior of the load balancer.
Clicking Delete...
The Delete Load Balancers dialog box lets you remove one or more load balancers from the current LPAN. You can delete a load balancer or a load balancer member only if it is Stopped. This dialog box contains the following fields:
Name
The name of the load balancer.
Current pServer
1-4
The pServer on which the load balancer is either Started or Starting. (If this field is empty, it means that the load balancer is Stopped.)
Status
The current run state of the load balancer.
Delete Members
Selecting the Yes check box deletes application members of the load-balancing service. You can delete a load balancer member only if it is Stopped.
Executable Resources
This area of the High Availability for LPAN lpan_name page lets you manage executable programs that are available as resources to applications in the current LPAN. (Executable resources are not available for load balancers.)
Clicking Create...
The Create Executable Resource dialog box lets you configure an executable program for use in the current LPAN. This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief identifying description of the program and its purpose.
Command
Specifies the pServer operating system command line of the executable program itself. You can also specify command arguments for the following specific purposes:
Start Arguments
The arguments used when an application
1-5
Book Title
configured to have an executable resource starts.
Stop Arguments
The arguments used when an application configured to have an executable resource stops.
Execute Arguments
The arguments that cause the executable program to run in a specific manner.
Run as user
The name of the pServer operating system user account as which the executable resource will run.
Leaving this field blank causes the executable resource to runs as the same user as the PAN Agent, which on Linux is root.
source user environment
A checkmark indicates that PAN Manager sources the user environment of the user you specify in the Run as user field. This means that the existing environment, and any variables specified in the application that is associated with this executable resource, will be lost.
If no checkmark appears (the default), the application’s environment and variables are preserved.
Proceed directly to resource page after creation
Selecting this check box lets you assign this resource to one or more application services (applications and/or load balancers).
Clicking Delete...
The Delete Executable Resources dialog box lets you remove one or more executable programs for use in the current LPAN.
You can delete a resource only if it is not assigned to any application services. (If the resource cannot be deleted, its check box is grayed.)
1-6
This dialog box contains the following fields:
Name
The name of the executable program.
Command
Specifies the pServer operating system command line of the executable program.
Service Assignments
The applications (if any) to which this resource is assigned.
Failover Policy Resources
This area of the High Availability for LPAN lpan_name page lets you manage failover policies to be available as resources to application services (applications and/or load balancers) in the current LPAN.
A failover policy governs how application services can continue running in the event of an application or pServer failure: which pServers run the application service and in which order they are selected.
Clicking Create...
The Create Failover Policy Resource dialog box lets you configure a failover policy for use in the current LPAN.
This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief note about the failover policy.
Selection Policy
The method for selecting failover pServers (round-robin or ordered):
1-7
Book Title
round robin
Selects the next member pServer based on its order number relative to other pServer members of the failover policy.
ordered
Selects the first member pServer based on its order number relative to other pServer members of the failover policy. (pServers that have a lower Order number are selected first; pServers that have the same Order number are equally available for selection. pServers that have an order of zero are selected last.)
Reboot pServer
A checkmark indicates that the PAN Manager should attempt to reboot the pServer when an application fails.
Auto Failback
A checkmark indicates that when the primary pServer again becomes available, the application automatically moves back to it.
pServer Configuration
The pServers that can be used in the event of an application service failure.
Important: For each pServer in a failover policy, be sure its operating system supports the application service, and that the PAN agent is present on the pServer.
Name
The name of the pServer.
Ordering
The sequence, if any, in which each application service to which this failover policy is assigned selects pServers, when failing over or moving. pServers that have a lower Order number are selected first; pServers that have the same Order
1-8
number are equally available for selection. (pServers that have an order of zero are selected last.)
HA Use
Each application service and application resource assigned to the pServer. For each application service, after a colon (:), shows whether the primary instance of the application is assigned to the pServer.
State
The current boot status of the pServer.
Clicking Delete...
The Delete Failover Policy Resources dialog box lets you remove one or more failover policies from the current LPAN.
You can delete a resource only if it is not assigned to any application services. (If the resource cannot be deleted, its check box is grayed.)
This dialog box contains the following fields:
Name
The name of the failover policy.
Configured pServers
The pServer(s), if any, to which this failover policy is assigned.
Service Assignments
The application service (if any) to which this resource is assigned.
1-9
Book Title
Health Monitor Resources
This area of the High Availability for LPAN lpan_name page lets you manage application health monitors to be available as resources to application services (applications and/or load balancers) in the current LPAN.
A health monitor is a program or script that monitors the status of one or more application services. By default, the Control Blade software provides a set of health monitors on each Linux pServer (in either /usr/lib/mon/mon.d or /opt/egenera/mon/mon.d, depending on the pServer release). These health monitors are provided as samples, and do not guarantee a specific level of monitoring coverage on the pServer. For best results, use customized health monitor programs to monitor your application services; for information about defining your own monitors, see Create User-Defined Monitor Resources with the GUI.
An application service can have multiple health monitors.
Clicking Create...
The Create Health Monitor Resource dialog box lets you configure an application health monitor for use in the current LPAN.
This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief note about the health monitor.
Script
The filename of the monitor program, such as http.monitor.
Application Monitoring Escalation Policies
The conditions under which PAN Manager takes actions
1-10
when it detects that application services have failed. These policies cooperate, so that the actions escalate as the number of consecutive failures of application services increases.
1) Restart if...
Indicates how widespread a failure must be for PAN Manager to restart an application service:
all started
(Default) Restart the failed application service only when all started monitors detect the configured number of consecutive failures in each of their associated application services.
any started
Restart all application services if any monitor detects the configured number of consecutive failures in each of its associated application services.
2) Failover if...
Indicates how widespread a failure must be for PAN Manager to fail over an application service to a configured failover pServer:
all started
(Default) Fail over the failed application service only when all started monitors detect the configured number of consecutive failures in each of their associated application services.
any started
Fail over all application services if any monitor detects the configured number of consecutive failures in each of its associated application services.
3) Giveup if...
Indicates how widespread a failure must be before
1-11
Book Title
the application service gives up and no longer responds to the health monitor:
all started
(Default) The application service will stop only when all started monitors detect the configured number of consecutive failures in each of their associated application services.
any started
The application service will stop if the monitor detects a failure in one of its associated application services.
Monitor pServer
The behavior of the pServer, if any, on which the health monitor is configured to run.
pServer
Lets you select a pServer on which the health monitor program runs. Local (same as service) indicates that the health monitor is a local monitor. A local monitor is configured on the same pServer as the application service it is monitoring and accompanies the application service in the event of a failover.
Startup Delay
The time period, expressed in integers of seconds, minutes, or hours, to delay invocation of the health monitor. (Setting this delay avoids false errors by allowing the application service’s initialization process to complete.)
Poll Interval
The frequency with which the monitor checks application status, expressed in integers of seconds, minutes, or hours.
Thresholds (in order of occurrence)
1-12
The actions that PAN Manager takes when it detects a specific number of application failures. These policies cooperate, so that the actions escalate as the number of consecutive failures increases.
Restart after...
The number of consecutive failures that PAN Manager allows before it attempts to restart the application. (For example, setting this value to 4 configures PAN Manager to restart the application when it detects the fourth failure.) A successful restart sets the failure counter back to zero.
Failover after...
The number of consecutive failures that 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. (For example, if you have set Restart if to 4, setting Failover if to 2 configures PAN Manager to fail over the application when it detects the sixth failure.) A successful failover sets the failure counter back to zero.
Giveup after...
The number of consecutive failures that PAN Manager allows before the application gives up and no longer responds to the health monitor. (For example, if you have set Restart if to 4, and Failover if to 2, setting Giveup if to 3 configures PAN Manager to suspend the application when it detects the ninth failure.)
Proceed directly to resource page after creation
Selecting this check box lets you select a monitor pServer, or to assign this health monitor resource to one or more application services. Local (same as service) indicates that
1-13
Book Title
the health monitor is a local monitor. A local monitor is configured on the same pServer as the application service it is monitoring and accompanies the application service in the event of a failover.
Clicking Delete...
The Delete Health Monitor Resources dialog box lets you remove one or more health monitor programs for use in the current LPAN.
You can delete a resource only if it is not assigned to any application services. (If the resource cannot be deleted, its check box is grayed.)
This dialog box contains the following fields:
Name
The name of the health monitor.
Script
The filename of the monitor program.
Service Assignments
The application service, if any, to which this resource is assigned.
Network Resources
This area of the High Availability for LPAN lpan_name page lets you manage network resources for application services (applications and/or load balancers) in the current LPAN.
These internet protocol (IP) resources provide connectivity between applications and the internal or external networks on which their pServers are configured.
Clicking Create...
1-14
The Create Network Resource dialog box lets you configure an IP resource for use by application services in the current LPAN.
This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief identifying note about the network resource or its use.
Interface
The interface to which the IP resource is mapped. Select one of the following:
Ethernet
A specific virtual Ethernet interface (vEth). (This vEth interface is potentially shared among one or more applications or processes running on the pServer.)
vSwitch
A Virtual Switch to which the vEth connects. (This vEth interface is less likely to be shared among one or more applications or processes running on the pServer.)
None
If selected, indicates either that you must select an interface by selecting Ethernet or vSwitch, or that you want to dissociate the network resource from a vSwitch in order to delete that vSwitch.
Network Settings
The network addresses of the network resource:
IP Address
The IP address of the network resource. This is the
1-15
Book Title
address at which an application service makes itself available to the network.
Broadcast Address
The network segment over which the IP resource broadcasts packets.
Netmask Address
The network address that determines the scope of the network in which the IP resource resides.
Proceed directly to resource page after creation
Selecting this check box lets you modify the network resource (such as configure its packet rate limiting or specify additional IP addresses), or to assign this network resource to one or more application services.
Clicking Delete...
The Delete Network Resources dialog box lets you remove one or more application IP resources for use in the current LPAN.
You can delete a resource only if it is not assigned to any application services. (If the resource cannot be deleted, its check box is grayed.)
This dialog box contains the following fields:
Name
The name of the network resource.
IP Address
The network address at which an application resource makes itself available to the network.
Service Assignments
The application service, if any, to which this resource is assigned.
1-16
Network File System Resources
This area of the High Availability for LPAN lpan_name page lets you manage file system resources for applications in the current LPAN.
Network file system resources include the file systems and mount points on which the applications and their data reside. An application can have multiple file systems.
Clicking Create...
The Create Network File System Resource dialog box lets you set the characteristics of a network file system resource for use by applications in the current LPAN.
This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief identifying note about the file system resource or its use.
Host
The IP address or hostname of the server on which the exported file system resource exists.
Host Path
The share path of the host.
Access Mode
Whether the file system is read/write or read-only.
Mount point
The specified point of access into a remote file system or directory, such as /mnt/nfs1.
Mount options
1-17
Book Title
All other mount options supported by the pServer’s version of the Linux operating system, including those corresponding to the mount command’s -t and -o flags and arguments.
Create mount point if it does not exist
Selecting this check box creates a mount point on the pServer for this network file system resource when the application starts.
Clearing this check box requires you to create the mount point manually from the operating system’s command line.
Proceed directly to resource page after creation
Selecting this check box lets you modify the network resource (such as create additional mount points or change the access mode), or to assign this file system resource to one or more applications.
Clicking Delete...
The Delete Network File System Resources dialog box lets you remove one or more file system resources for use in the current LPAN.
You can delete a resource only if it is not assigned to any applications. (If the resource cannot be deleted, its check box is grayed.)
This dialog box contains the following fields:
Name
The name of the network file system resource.
Host
The IP address or hostname of the pServer on which the exported file system resource exists.
Service Assignments
The applications to which this resource is assigned.
1-18
SCSI File System Resources
This area of the High Availability for LPAN lpan_name page lets you manage SCSI file system resources for applications in the current LPAN.
SCSI file system resources include information about the physical disk on which a file system resides, as well as the file systems and mount points on which the applications and their data reside. An application can have multiple SCSI file system resources.
Clicking Create...
The Create SCSI File System Resource dialog box lets you set the characteristics of a SCSI file system resource for use by applications in the current LPAN.
This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief identifying note about this SCSI file system resource or its use.
SCSI Disk
The available disk resources on which an application’s file system resource can reside.
Selecting None indicates that the SCSI file system resource is not associated with any SCSI disk. (To remove a disk from an LPAN, the disk must contain no SCSI file system resources.)
SCSI Id
The name of the physical disk on which the file system resource is to reside.
Details
1-19
Book Title
The capacity and manufacturer of the physical disk.
Mount Point
Information about the point of access into a SCSI file system or directory:
Path
The name of the SCSI file system or directory, such as /mnt/fs1
Partition
The number of the disk partition on which the SCSI file system resides
Mount Order
The order in which the partitions are mounted. When the application stops or fails over, the partitions are unmounted in the reverse order.
Mount Options
All other mount options supported by the pServer’s version of the Linux operating system, including those corresponding to the mount command’s -t and -o flags and arguments.
Mode
Whether the SCSI file system is read/write or read-only.
Create mount point if it does not already exist
Selecting this check box creates a mount point for this file system resource.
Clearing this check box requires you to create the mount point manually from the operating system’s command line.
Scan partition before mounting
If selected, checks, and optionally repairs, the partition before the partition is mounted.
Scan options (optional)
1-20
If you selected the Scan partition before mounting check box, you can also specify any options, such as the partition’s file system type, to allow the scan to run successfully.
Proceed directly to resource page after creation
Selecting this check box lets you modify the SCSI file system resource (such as select a different physical disk, create additional mount points, or change the access mode), or to assign this SCSI file system resource to one or more applications.
Clicking Delete...
The Delete SCSI File System Resources dialog box lets you remove one or more SCSI file system resources for use in the current LPAN. You can delete a resource only if it is not assigned to an application. If a resource cannot be deleted, its check box is grayed.
This dialog box contains the following fields:
Name
The name of the SCSI file system resource.
SCSI Id
The name of the physical disk on which the file system resource resides.
Service Assignments
The application, if any, to which this resource is assigned.
Configure High-availability Applications
Use the following PAN Manager procedures to configure application services within an LPAN:
Extract Application Templates with the GUI
Enabling and Disabling Application Services
Create an Application
Enabling the Physical DVD-ROM Drive
1-21
Book Title
Open a Connection to the pServer Console
Complete the Installation
Create or Delete a Load Balancer
Create Executable Resources
Create Failover Policy Resources with the GUI
Create Health Monitor Resource Configurations with the GUI
Create Network Resources
Create Network File System Resources
Creating a SCSI File System Resource
Deleting a SCSI File System Resource
Configure High-availability Applications (CLI)
Use the following PAN Manager commands to configure application services within an LPAN:
app -- Creates, lists, or modifies an application configuration within an LPAN.
lb -- Creates, lists, or modifies a load-balancing service within an LPAN.
Use the following PAN Manager commands to configure resources for application services:
exeres -- Creates or modifies an LPAN’s executable resources.
fop -- Creates, lists, or modifies a failover policy within an LPAN.
fs -- Creates, lists, or modifies a file system mount point within an LPAN.
hmon -- Creates, lists, or modifies a health monitor within an LPAN.
ip -- Creates, lists, or modifies the IP resources for an application or load-balancing service.
1-22
nfs -- Creates, lists, or modifies the IP resources for an application.
umon -- Creates, modifies, or lists an LPAN’s user-defined monitor resources.
1-23
Book Title
1-24
Creating High-availability Applications
(LPANS > lpan_name > High Availability > application_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Application application_name page:
This page lets you configure a specific high-availability application, and the application resources that support it. (After configuring this application, you have the option of making it part of a load-balancing service.)
About Configuring an Application
Controls for Managing an Application
Configure an Application
Configure an Application (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Configuring an Application
The goal is to associate the proper application resources with the application to allow it to run with minimal down time for long periods of time. To make this happen, use PAN Manager to configure the application to continue processing on a failover pServer if the primary pServer fails: specify a failover policy to run the same application, to respond at the same IP address, and to have access to the same application data.
The Application application_name page’s top banner displays the application’s name, whether it is a member of a load-balancing service, and if so, the name of the load-balancing service.
1-1
Book Title
You can add or remove resources while a service is running; however, you cannot modify a resource while a service is running. For example, you can add a SCSI disk to a running application service, but you cannot change a mount point with a running application service.
Learn more about specific areas of this page:
• Current pServer
• Primary pServer
• Failover Policy
• Executable Resources
• SCSI File System Resources
• Network Resources
• Health Monitors
• Network File System Resources
In addition, see Create User-Defined Monitor Resources with the GUI for information about defining your own monitors.
Clicking Edit...
The Edit Application dialog box lets you modify the application’s name and description.
Clicking Advanced Configuration...
The Advanced Application Configuration dialog box displays the following headings, and the fields within them. Click a heading to display its contents:
Auto-start
If selected, indicates that the application starts automatically when the pServer’s PAN agent connects to PAN Manager.
Environment Variables
Lets you define the values of variables that are potentially
1-2
present in one or more executable resources and/or user monitors.
Load Balancer Membership
Shows whether this application is a member of a load-balancing service, and if so, the name of the load-balancing service.
Assign to load balancer
This pull-down list shows all load balancers in the LPAN, and lets you assign the application to one (or none) of them.
Use network resource
Lets you select an existing network resource. (A network resource provides connectivity between an application service and the internal or external networks on which its pServers are configured.)
Membership weight
(For weighted round robin or weighted least connected policies only) A numeric weight value for each member; highest number indicates strongest weight. (A member that has a weight of 2 will be forwarded twice as many connections as a member that has a weight of 1.)
Start member as load balancer starts
If selected, indicates that the application starts automatically when the load balancer starts.
Current pServer
This area of the Application application_name page shows the pServer on which the application is either Started or Starting. (If no pServer appears in the Current pServer area, it means that the application is Stopped.)
1-3
Book Title
Primary pServer
This area of the Application application_name page shows the pServer on which the application first attempts to run.
Clicking Assign/Unassign...
The Assign/Unassign pServer as Primary dialog box lists all pServers in the LPAN and lets you select the pServer on which the application will run.
Name
The name of the pServer.
HA Assignments
Shows the name (and type) of application services and application resources installed on the pServer. For applications, the value to the right of the colon (:) indicates whether the pServer is the application’s primary pServer.
State
The current run status of the pServer, such as Booted or Shutdown.
Failover Policy
This area of the Application application_name page shows the application’s failover policy. A failover policy governs how application services can continue running in the event of an application or pServer failure: which pServers will run the application service, and in which order they are selected. An application service can have only one failover policy.
Clicking Assign/Unassign...
The Assign/Unassign Failover Policy dialog box lists the failover policies available in the LPAN for applications to use.
Name
The name of the failover policy.
1-4
Configured pServers
The pServers that can be used in the event of an application service failure.
Important: For each pServer that you select, be sure its operating system supports the application service, and that the PAN agent is present on the pServer.
The value in parentheses is the sequence, if any, in which each application service to which this failover policy is assigned will select pServers, when failing over or moving.
Configured Services
Indicates which application services (if any) are assigned this failover policy.
Executable Resources
This area of the Application application_name page lets you manage an application’s executable programs.
Clicking Assign...
The Add executable resources dialog box lists all executable programs available for applications in the current LPAN to use.
Name
The name of the executable resource.
Execute on
The conditions that will cause the executable program to run.
Start
If selected, the executable program will run whenever the application starts.
Stop
If selected, the executable program will run whenever the application stops.
1-5
Book Title
User Request
Indicates that the resource can only be run by the user when the service is Started, using the execute argument in the resource.
Order
The order in which this application resource is started, relative to others of the same type. A resource that has an Order of 1 is started first, followed by numbers of increasing value; an Order of 0 is started last. (If two resources have the same Order, either can start before the other.)
If the application service stops or fails over, the resources of this type are Stopped in reverse order.
Clicking Remove...
The Remove executable resources dialog box lists all executable programs assigned to the application. This dialog box contains the following fields:
Name
The name of the executable program.
Command
Specifies the pServer operating system command line of the executable program itself.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which this executable resource is assigned.
Clicking Modify...
The Modify executable resources dialog box lets you change the execute behavior of one or more executable resources assigned to the application.
1-6
(The field descriptions are identical to those in the Add executable resources dialog box.)
SCSI File System Resources
This area of the Application application_name page lets you manage SCSI file system resources for an application.
SCSI file system resources include information about the physical disk on which a file system resides, as well as the file systems and mount points on which applications and their data reside. An application can have multiple SCSI file system resources.
Clicking Assign...
The Add SCSI file system resources dialog box lists all SCSI file system resources available for applications in the current LPAN to use. This dialog box contains the following fields:
Name
The name of the SCSI file system resource.
SCSI Id
The name of the physical disk on which the file system resource will reside.
Service Assignments
The applications in the current LPAN to which this SCSI file system resource is currently assigned. (You cannot assign a SCSI file system resource to a load balancer.)
Order
The order in which this application resource is started, relative to others of the same type. A resource that has an Order of 1 is started first, followed by numbers of increasing value; an Order of 0 is started last. (If two resources have the same Order, either can start before the other.)
If the application service stops or fails over, the resources of this type are Stopped in reverse order.
1-7
Book Title
Clicking Remove...
The Remove SCSI file system resources dialog box lets you remove one or more SCSI file system resources assigned to the application.
This dialog box contains the following fields:
Name
The name of the SCSI file system resource.
SCSI Id
The name of the physical disk on which the file system resource resides.
Service Assignments
The application services (applications) in the current LPAN to which this SCSI file system resource is currently assigned.
Clicking Set Order...
The Order SCSI file system resources dialog box lets you specify the sequence in which resources of this type are started.
Network Resources
This area of the Application application_name page lets you manage an application’s network resources. These internet protocol (IP) resources provide connectivity between an application and the internal or external networks on which its pServer is configured.
Clicking Assign...
The Add network resources dialog box lists all network resources available for applications in the current LPAN to use. This dialog box contains the following fields:
Name
The name of the network resource.
1-8
IP Address
The IP address of the network resource. This is the address at which an application service makes itself available to the network.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Order
The order in which this application resource is started, relative to others of the same type. A resource that has an Order of 1 is started first, followed by numbers of increasing value; an Order of 0 is started last. (If two resources have the same Order, either can start before the other.)
If the application service stops or fails over, the resources of this type are Stopped in reverse order.
Clicking Remove...
The Remove network resources dialog box lets you remove one or more network resources assigned to the application.
You can remove a network resource from an application only if it is neither assigned to a health monitor, nor to a load balancer. (If the resource cannot be deleted, its check box is grayed.)
This dialog box contains the following fields:
Name
The name of the network resource.
IP Address
The IP address of the network resource. This is the address at which an application service makes itself available to the network.
Use on Service
1-9
Book Title
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Clicking Set Order...
The Order network resources dialog box lets you specify the sequence in which resources of this type are started.
Health Monitors
This area of the Application application_name page lets you manage an application’s health monitor resources.
A health monitor is a program or script that monitors the status of one or more application services. By default, the Control Blade software provides a set of health monitors on each Linux pServer (in either /usr/lib/mon/mon.d or /opt/egenera/mon/mon.d, depending on the pServer release). These health monitors are provided as samples, and do not guarantee a specific level of monitoring coverage on the pServer. For best results, use customized health monitor programs to monitor your application services. For information about defining your own monitors, see Create User-Defined Monitor Resources with the GUI.
To assign a health monitor to an application, you must first assign a network resource to the application. The health monitor relies on the network resource to monitor the application.
Clicking Assign...
The Add Health Monitor resource dialog box lists all health monitors available for applications in the current LPAN to use. This dialog box contains the following fields:
Name
The name of the health monitor.
Script
The filename of the monitor program, such as
1-10
http.monitor.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Network Resource
The application’s network resource to which the health monitor is connected.
Clicking Remove...
The Remove health monitor resources dialog box lets you remove one or more health monitors assigned to the application. This dialog box contains the following fields:
Name
The name of the health monitor.
Script
The filename of the monitor program, such as http.monitor.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Clicking Modify...
The Modify Health Monitor Assignments dialog box lets you change the health monitor assignments of the application. (The field descriptions for Name and Network are identical to those in the Add Health Monitor Resource dialog box.)
Network File System Resources
This area of the Application application_name page lets you manage an application’s network file system resources.
1-11
Book Title
Network file system resources include the file systems and mount points on which an application and its data reside. An application can have multiple network file systems.
Clicking Assign...
The Add network file system resources dialog box lists all network file system resources available for applications in the current LPAN to use. This dialog box contains the following fields:
Name
The name of the network file system.
Host
The IP address or hostname of the server on which the exported file system resource exists.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network file system resource is currently assigned.
Order
The order in which this application resource is started, relative to others of the same type. A resource that has an Order of 1 is started first, followed by numbers of increasing value; an Order of 0 is started last. (If two resources have the same Order, either can start before the other.)
If the application service stops or fails over, the resources of this type are Stopped in reverse order.
Clicking Remove...
The Remove network file system resources dialog box lets you remove one or more network file systems assigned to the application. This dialog box contains the following fields:
Name
1-12
The name of the network file system.
Host
The IP address or hostname of the pServer on which the exported file system resource exists.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network file system resource is currently assigned.
Clicking Set Order...
The Order network file system resources dialog box lets you specify the sequence in which resources of this type are started.
Controls for Managing an Application
The bottom border of the Application application_name page has controls for managing an application.
To use these controls, the pServer on which the application is installed must have the PAN agent running. If an action is currently prohibited on the application, the button is shaded.
Start Application
Starts a stopped application.
Stop Application
Stops an application.
Move Application
Causes a Started application to resume running on another pServer, which you specify, in the LPAN.
1-13
Book Title
Run an executable resource
Runs an executable resource on the application’s current pServer, and displays the following information about its results:
Command
The executable program command and its arguments.
Status
The operating system’s exit status for the process.
Standard out
The command’s output text.
Standard error
The command’s error text.
Exception
Any error conditions that caused the executable program not to run, for example, if the executable program does not exist, if the script exists but is not executable, or if the current pServer’s PAN agent is unavailable.
Configure an Application
Use the following PAN Manager procedures to configure an application within an LPAN:
Create an Application
Modifying Advanced Settings for an Application
Modifying Resource Assignments for an Application
Starting, Stopping, and Moving an Application
1-14
Configure an Application (CLI)
Use the following PAN Manager command to configure an application within an LPAN:
app -- Creates, lists, or modifies an application configuration within an LPAN.
Use the following PAN Manager commands to configure resources for an application:
exeres -- Creates or modifies an LPAN’s executable resources.
fop -- Creates, lists, or modifies a failover policy within an LPAN.
fs -- Creates, lists, or modifies a file system mount point within an LPAN.
hmon -- Creates, lists, or modifies a health monitor within an LPAN.
ip -- Creates, lists, or modifies the IP resources for an application or load-balancing service.
nfs -- Creates, lists, or modifies the IP resources for an application.
1-15
Book Title
1-16
Creating High-availability Load Balancing
(LPANS > lpan_name > High Availability > load_balancer_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Load Balancer load_balancer_name page:
A load-balancing service is a set of applications that run the same or cooperating instances of a certain application. Incoming requests for the service are balanced across the member applications to provide scalable performance.
About Configuring a Load Balancer
Controls for Managing a Load Balancer
Configure a Load Balancer
Configure a Load Balancer (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Configuring a Load Balancer
A load balancer is an application service that includes a set of member applications, each of which is a separate instance of the same application.
The following are the goals when configuring a load balancer:
• To associate the proper application resources with the load balancer to allow it to run with minimal down time for long periods of time
• To configure each application that is a member of a load balancer to run an instance of the same application, and to share incoming client requests for the service that the application provides
1-1
Book Title
When a client sends a request to a load-balancing service (that is, the load balancer’s IP address), the load balancer first receives the request, and then using the service’s load balancing policy, forwards the request to the appropriate member pServer.
Learn more about specific areas of this page:
• Application Members
• Current pServer
• Primary pServer
• Load Balancing Connections
• Failover Policy
• Health Monitors
• Network Resources
In addition, see Create User-Defined Monitor Resources with the GUI for information about defining your own monitors.
Clicking Edit...
The Edit Load Balancer dialog box lets you modify the load balancer’s name and description.
Clicking Advanced Configuration...
The Advanced Load Balancer Configuration dialog box displays the following heading:
Auto-start
If selected, indicates that the load balancer starts automatically when the pServer’s PAN agent connects to PAN Manager.
Application Members
This area of the Load Balancer load_balancer_name page lets you manage the members of a load-balancing service.
1-2
The members of a load balancer are instances of an application, each of which runs on a pServer. These application instances appear to clients to be sharing a single IP address and port number. The load balancer distributes incoming requests to the members, based on a configurable scheduling policy.
Clicking Add...
The Add Member dialog box lets you add member applications to a load-balancing service. This dialog box contains the following fields:
Choose Application to add
This pull-down list contains all applications in the LPAN. Be sure to use multiple instances of the same application.
Weight
(For weighted round robin or weighted least connected policies only) A numeric weight value for each member; highest number indicates strongest weight. (A member that has a weight of 2 will be forwarded twice as many connections as a member that has a weight of 1.)
Application Network
This pull-down list contains all network resources assigned to the application. (A network resource provides connectivity between an application service and the internal or external networks on which its pServer is configured.)
Start with Load Balancer
If selected, indicates that the application starts automatically when the load balancer starts.
Clicking Remove...
The Remove Member dialog box lets you remove one or more applications from a load balancer.
Member
The name of the member of the load balancer.
1-3
Book Title
Weight
(For weighted round robin or weighted least connected policies only) A numeric weight value for each member; highest number indicates strongest weight. (A member that has a weight of 2 will be forwarded twice as many connections as a member that has a weight of 1.)
Network
The network resource that provides connectivity between an application service and the internal or external networks on which its pServer is configured.
Start
A checkmark indicates that the application starts automatically when the pServer’s PAN agent connects to PAN Manager.
Clicking Modify...
The Modify Member dialog box lets you change the behavior of one or more members of the load balancer. Each heading is a member; click a heading to display its fields:
Weight
(For weighted round robin or weighted least connected policies only) A numeric weight value for each member; highest number indicates strongest weight. (A member that has a weight of 2 will be forwarded twice as many connections as a member that has a weight of 1.)
Network
The network resource that provides connectivity between an application service and the internal or external networks on which its pServer is configured.
Start with Load Balancer
If selected, indicates that the application starts automatically when the load balancer starts.
1-4
Current pServer
This area of the Load Balancer load_balancer_name page shows the pServer on which the load balancer is either Started or Starting. (If no pServer appears in the Current pServer area, it means that the load balancer is Stopped.)
Primary pServer
This area of the Load Balancer load_balancer_name page shows the pServer on which the load balancer is installed.
Clicking Assign/Unassign...
The Assign/Unassign pServer as Primary dialog box lists all pServers in the LPAN, and lets you select the pServer on which the load balancer will run.
Name
The name of the pServer.
HA Assignments
The name (and type) of high-availability application services and application resources installed on the pServer. For applications, the value to the right of the colon (:) indicates whether the pServer is the application’s primary pServer.
State
The current run status of the pServer, such as Booted or Shutdown.
Load Balancing Connections
This area of the Load Balancer load_balancer_name page lets you manage the flow of network connections between clients and the member pServers of the load balancer.
1-5
Book Title
Clicking Create...
The Create Connection dialog box lets you define how the load balancer handles requests from clients. This dialog box contains the following fields:
Protocol
The transport method (TCP, TCP (persist) or UDP) that the load balancer uses when forwarding packets to or from the external network. If selected TCP (persist) is selected, it indicates that after a client establishes a connection to a member pServer; its requests will continue to be handled by the same member pServer as long as the connection exists.
Port
The port number associated with the entire load-balancing service.
Policy
A load balancer’s member selection policy determines how the load balancer forwards client requests to its member pServers:
Round Robin (rr)
The load balancer cycles through the list of member pServers, and selects the next in the list to which to forward the request.
Weighted Round Robin (wrr)
In addition to a round-robin policy, an ordinal weight can apply to one or more member pServers in the load balancer. (If a member has a weight of 3, the load balancer forwards client requests to it three times more often than to a member that only has a weight of 1.)
Least Connected (lc)
The member pServer that has the least number of established service connections.
Weighted Least Connected (wlc)
1-6
In addition to a least connected policy, an ordinal weight can apply to one or more member pServers in the load-balancing service. (If a member has a weight of 3, the load balancer forwards client requests to it three times more often than to a member that only has a weight of 1.)
Clicking Delete...
The Delete Connections dialog box lets you delete a load balancing connection. (The field descriptions for this dialog box are identical to those in the Create Connections dialog box.)
Clicking Modify...
The Modify Connection dialog box lets you change how the load balancer handles requests from clients.
Each heading is a connection; click a heading to display its fields. (The field descriptions are identical to those in the Create Connection dialog box.)
Failover Policy
This area of the Load Balancer load_balancer_name page shows the load balancer’s failover policy. A failover policy governs how application services can continue running in the event of a load balancer or pServer failure: which pServers will run the load balancer, and in which order they are selected. An application service can have only one failover policy.
Clicking Assign/Unassign...
The Assign/Unassign Failover Policy dialog box lists the failover policies available in the LPAN for application services to use.
Name
The name of the failover policy.
Configured pServers
1-7
Book Title
The pServers that can be used in the event of a load balancer failure.
Important: For each pServer that you select, be sure its operating system supports the application service, and that the PAN agent is present on the pServer.
The value in parentheses, if any, is the sequence in which each load balancer associated with this failover policy will select pServers when failing over or moving.
Service Assignments
Indicates which application services, if any, that are assigned this failover policy.
Health Monitors
This area of the Load Balancer load_balancer_name page lets you manage a load balancer’s health monitor resources.
A health monitor is a program or script that monitors the status of one or more application services. By default, the Control Blade software provides a set of health monitors on each Linux pServer (in either /usr/lib/mon/mon.d or /opt/egenera/mon/mon.d, depending on the pServer release). These health monitors are provided as samples, and do not guarantee a specific level of monitoring coverage on the pServer. For best results, use customized health monitor programs to monitor your application services. For information about defining your own monitors, see Create User-Defined Monitor Resources with the GUI.
To assign a health monitor to a load balancer, you must first assign a network resource to the load balancer. The health monitor relies on the network resource to monitor the load balancer.
Clicking Assign...
The Add Health Monitor resource dialog box lists all health monitors available for application services in the current LPAN to use. This dialog box contains the following fields:
Name
1-8
The name of the health monitor.
Script
The filename of the monitor program, such as http.monitor.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Network Resource
The load balancer’s IP address to which the health monitor is connected.
Clicking Remove...
The Remove Health Monitor resources dialog box lets you remove one or more health monitors assigned to the load balancer. This dialog box contains the following fields:
Name
The name of the health monitor.
Script
The filename of the monitor program, such as http.monitor.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Network Resources
This area of the Load Balancer load_balancer_name page lets you manage a load balancer’s network resources. These internet protocol (IP) resources provide connectivity between a load balancer and the internal or external networks on which its pServer is configured.
1-9
Book Title
Clicking Assign...
The Add network resources dialog box lists all network resources available for application services in the current LPAN to use. This dialog box contains the following fields:
Name
The name of the network resource.
IP Address
The IP address of the network resource. This is the address at which an application service makes itself available to the network.
Service Assignments
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned.
Order
The order in which this application resource is started, relative to others of the same type. A resource that has an Order of 1 is started first, followed by numbers of increasing value; an Order of 0 is started last. (If two resources have the same Order, either can start before the other.)
If the application service stops or fails over, the resources of this type are Stopped in reverse order.
Clicking Remove...
The Remove network resources dialog box lets you remove one or more network resources assigned to the load balancer.
This dialog box contains the following fields:
Name
The name of the network resource.
IP Address
1-10
The IP address of the network resource. This is the address at which an application service makes itself available to the network.
Use on Service
The application services (applications and/or load balancers) in the current LPAN to which each network resource is currently assigned
Clicking Set Order...
The Order network file system resources dialog box lets you specify the sequence in which resources of this type are started.
Controls for Managing a Load Balancer
The bottom border of the Load Balancer load_balancer_name has controls for managing a load balancer. To use these controls, the pServer on which the load balancer is installed must have the PAN agent running. If an action is currently prohibited on this load balancer, the button is shaded.
Start Load Balancer
Starts a stopped load balancer.
Stop Load Balancer
Stops a load balancer.
Move Load Balancer
Causes a Started load balancer to resume running on another pServer, which you specify, in the LPAN.
1-11
Book Title
Configure a Load Balancer
Use the following PAN Manager procedures to configure a load balancer within an LPAN:
Modifying Load Balancer Control Configurations
Modifying Advanced Settings for a Load Balancer Control Configuration
Add Members to the Load Balancing Service
Modifying Resource Assignments for a Load Balancer Control Configuration
Start, Stop, or Move a Load Balancing Service
Configure a Load Balancer (CLI)
Use the following PAN Manager command to configure a load balancer within an LPAN:
lb -- Creates, lists, or modifies a load balancer and its members within an LPAN.
Use the following PAN Manager commands to configure resources for a load balancer:
fop -- Creates, lists, or modifies a failover policy within an LPAN.
hmon -- Creates, lists, or modifies a health monitor within an LPAN.
ip -- Creates, lists, or modifies the IP resources for an application or load-balancing service.
1-12
Managing Executable Resources for Applications
(LPANS > lpan_name > High Availability > executable_resource_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Executable Resource executable_resource_name page:
Use this page to modify an executable program and to assign it to one or more application services (applications only) in the current LPAN.
About Executable Resources
Configure an Executable Resource
Configure an Executable Resource (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Executable Resources
Clicking Modify...
The Modify Executable Resource dialog box lets you configure an executable program for use in the current LPAN. An application can have multiple executable resources.
This dialog box contains the following fields:
Name
A unique name among all resources of this type in the LPAN.
Description
A brief identifying description of the program and its purpose.
1-1
Book Title
Command
The pServer operating system command line of the executable program itself. You can also specify command arguments for the following:
Start Arguments
The arguments used when an application configured to have an executable resource starts.
Stop Arguments
The arguments used when an application configured to have an executable resource stops.
Execute Arguments
The arguments that cause the executable program to run in a specific manner.
Run as user
The name of the pServer operating system user account as which the executable resource will run. (Leaving this field blank causes the executable resource to runs as the same user as the PAN Agent, which on Linux is root.)
Source user environment
A checkmark indicates that PAN Manager sources the user environment of the user you specify in the Run as user field. This means that the existing environment, and any variables specified in the application that is associated with this executable resource, will be lost.
If no checkmark appears (the default), the application’s environment and variables are preserved.
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lets you assign the executable program to one or more applications in the current LPAN.
This dialog box contains the following fields:
1-2
Service
The applications, if any, to which this resource is assigned.
Current pServer
The pServer to which the application is assigned.
Status
The current run state of the application, such as Started or Stopped.
Configure an Executable Resource
Use the following PAN Manager procedures to modify or assign an executable resource:
Modifying Executable Resources
Assign Executable Resources
Configure an Executable Resource (CLI)
Use the following PAN Manager commands to modify or assign an executable resource:
app -- Creates, lists, or modifies an application configuration within an LPAN.
exeres -- Creates or modifies an LPAN’s executable resources.
1-3
Book Title
1-4
Managing Failover Policy Resources for Application Services
(LPANS > lpan_name > High Availability > failover_policy_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Failover Policy failover_policy_name page:
Use this page to modify a failover policy and to assign it to one or more application services (applications and/or load balancers) in the current LPAN.
About Failover Policy Resources
Configure a Failover Policy
Configure a Failover Policy (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Failover Policy Resources
A failover policy governs how application services can continue running in the event of an application or pServer failure: which pServers will run the application service, and in which order they are selected. An application service can have only one failover policy.
Clicking Modify...
The Modify Failover Policy dialog box lets you configure a failover policy for use in the current LPAN. This dialog box contains the following fields:
Name
A unique name for this policy.
1-1
Book Title
Description
A brief identifying description of the failover policy and its purpose
Selection Policy
The method you want to use to select a pServer to receive an application service that fails over or moves (round-robin or ordered):
round robin
Selects the next member pServer based on its order number relative to other pServer members of the failover policy.
ordered
Selects the first member pServer based on its order number relative to other pServer members of the failover policy. (pServers that have a lower Order number are selected first; pServers that have the same Order number are equally available for selection. pServers that have an order number of zero are selected last.)
Reboot pServer
If not selected (the default) — If the pServer is running other applications that are not associated with a failover policy, it is best to leave this check box clear.
If selected — When an application service fails over from a pServer (as opposed to moving or stopping), the pServer that the application service was running on is rebooted.
Auto Failback
A checkmark in the Enabled check box indicates that when the primary pServer again becomes available, the application will automatically move back to it.
1-2
pServer Members
This area of the Failover Policy failover_policy_name page shows which pServers are ready to continue running an application service if the service or the service’s pServer fails.
Important: For each pServer that you select, be sure its operating system supports the application service, and that the PAN agent is present on the pServer.
Clicking Modify...
The Modify pServer Members dialog box lists all pServers in the LPAN. Selecting the check box next to a pServer’s name makes it a member of this failover policy.
Name
The name of the pServer.
Ordering
The sequence, if any, in which each application service to which this failover policy is assigned will select pServers, when failing over or moving. pServers that have a lower Order number are selected first; pServers that have the same Order number are equally available for selection. pServers that have an order number of zero are selected last.
HA Use
Lists each application service and application resource assigned to the pServer. For each application service, after a colon (:), shows whether the primary instance of the application is assigned to the pServer.
State
Shows the current boot status of the pServer.
1-3
Book Title
Service Assignments
This area of the Failover Policy failover_policy_name page shows all application services to which the failover policy is assigned.
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lists all application services (applications or load balancers) in the current LPAN, and lets you assign the failover policy to one or more services. This dialog box contains the following fields:
Service
The application services, if any, to which this resource is assigned. The value in parentheses can be either application or load balancer.
Current pServer
The pServer to which the application service is assigned.
Status
The current run state of the application service, such as Started or Stopped.
Configure a Failover Policy
Use the following PAN Manager procedures to configure a failover policy within an LPAN:
Modifying Failover Policy Resources
Modifying pServer Members of a Failover Policy Resource
Assign Failover Policy Resources
Configure a Failover Policy (CLI)
Use the following PAN Manager commands to configure a failover policy within an LPAN:
app -- Creates, lists, or modifies an application configuration within an LPAN.
1-4
fop -- Creates, lists, or modifies a failover policy within an LPAN.
lb -- Creates, lists, or modifies a load-balancing service within an LPAN.
1-5
Book Title
1-6
Managing Health Monitor Resources for Application Services
(LPANS > lpan_name > High Availability > health_monitor_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Health Monitor health_monitor_name page:
Use this page to modify a health monitor and to assign it to one or more application services (applications and/or load balancers) in the current LPAN.
About Health Monitor Resources
Configure a Health Monitor
Configure a Health Monitor (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Health Monitor Resources
A health monitor is a program or script that monitors the status of one or more application services. By default, the Control Blade software provides a set of health monitors on each Linux pServer (in either /usr/lib/mon/mon.d or /opt/egenera/mon/mon.d, depending on the pServer release). These health monitors are provided as samples, and do not guarantee a specific level of monitoring coverage on the pServer. For best results, use customized health monitor programs to monitor your application services. For information about defining your own monitors, see Create User-Defined Monitor Resources with the GUI.
An application service can have multiple health monitors.
1-1
Book Title
Clicking Modify...
The Modify Health Monitor dialog box lets you configure a health monitor for use in the current LPAN. This dialog box contains the following fields:
Name
A unique name for this health monitor.
Description
A brief note about the health monitor.
Script
The filename of the monitor program, such as http.monitor.
Application Monitoring Escalation Policies
The conditions under which PAN Manager takes actions when it detects that application services have failed. These policies cooperate, so that the actions escalate as the number of consecutive failures of application services increases.
1) Restart if...
Indicates how widespread a failure must be for PAN Manager to restart an application service:
all started
(Default) Restart the failed application service only when all started monitors detect the configured number of consecutive failures in each of their associated application services.
any started
Restart all application services if any monitor detects the configured number of consecutive failures in each of its associated application services.
2) Failover if...
Indicates how widespread a failure must be for
1-2
PAN Manager to fail over an application service to a configured failover pServer:
all started
(Default) Fail over the failed application service only when all started monitors detect the configured number of consecutive failures in each of their associated application services.
any started
Fail over all application services if any monitor detects the configured number of consecutive failures in each of its associated application services.
3) Giveup if...
Indicates how widespread a failure must be before the application service gives up and no longer responds to the health monitor.
all started
(Default) The application service will stop only when all started monitors detect the configured number of consecutive failures in each of their associated application services.
any started
The application service will stop if the monitor detects a failure in one of its associated application services.
Monitor pServers
This area of the Health Monitor health_monitor_name page shows the pServers, if any, on which the health monitor program is configured to run.
1-3
Book Title
Clicking Create...
The Create Monitor pServer dialog box lets you install the health monitor program on one or more pServers in the LPAN. This dialog box contains the following fields:
pServer
Lets you select a pServer on which the health monitor program runs. Local (same as service) indicates that the health monitor is a “local” monitor. A local monitor a) is configured on the same pServer as the application service it is monitoring, and b) accompanies the application service in the event of a failover.
Startup Delay
The time period, expressed in integers of either seconds, minutes, or hours, to delay invocation of the health monitor. (Setting this delay avoids false errors by allowing the application service’s initialization process to complete.)
Poll Interval
The frequency that the monitor checks application status, expressed in integers of seconds, minutes, or hours.
Thresholds (in order of occurrence)
The actions that PAN Manager takes when it detects a specific number of application failures. These policies cooperate, so that the actions escalate as the number of consecutive failures increases.
Restart after...
The number of consecutive failures that PAN Manager allows before it attempts to restart the application. (For example, setting this value to 4 configures PAN Manager to restart the application when it detects the fourth failure.) A successful restart sets the failure counter back to zero.
Failover after...
The number of consecutive failures that
1-4
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 0 if no failover policy is configured. (For example, if you have set Restart if to 4, setting Failover if to 2 configures PAN Manager to fail over the application when it detects a sixth failure.) A successful failover sets the failure counter back to zero.
Giveup after...
The number of consecutive failures that PAN Manager allows before the application gives up and no longer responds to the health monitor. (For example, if you have set Restart if to 4, and Failover if to 2, setting Giveup if to 3 configures PAN Manager to suspend the application when it detects a ninth failure.)
Clicking Delete...
The Delete Health Monitor dialog box lets you unassign the health monitor program from one or more monitor pServers.
Clicking Modify...
The Modify Health Monitor dialog box lets you change the behavior of the health monitor program on one or more pServers in the LPAN.
(The field descriptions are identical to those in the Create Health Monitor dialog box.)
Service Assignments
This area of the Health Monitor health_monitor_name page shows all application services to which the health monitor is assigned.
1-5
Book Title
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lists all application services (applications or load balancers) in the current LPAN, and lets you assign the health monitor to one or more services.
An application service must already have a network resource in order to assign a health monitor to the service.
This dialog box contains the following fields:
Service
The application services, if any, to which this resource is assigned. The value in parentheses can be either application or load balancer.
Status
The current run state of the application service, such as Started or Stopped.
Network Resource
The network resource associated with the application service. (You cannot assign the health monitor to an application resource that has no network resource.)
Configure a Health Monitor
Use the following PAN Manager procedures to configure an application health monitor within an LPAN:
Modifying Health Monitor Resource Configurations
Adding a Monitor pServer to a Health Monitor Resource Configuration
Assign Health Monitor Resources
1-6
Configure a Health Monitor (CLI)
Use the following PAN Manager command to configure an application health monitor within an LPAN:
hmon -- Creates, lists, or modifies a health monitor within an LPAN.
1-7
Book Title
1-8
Managing Network Resources for Application Services
(LPANS > lpan_name > High Availability > network_resource_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Network Resource network_resource_name page:
Use this page to modify a network resource and to assign it to one or more application services (applications and/or load balancers) in the current LPAN.
About Network Resources
Configure Network Resources
Configure Network Resources (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Network Resources
An internet protocol (IP) resource provides connectivity between an application service and the internal or external networks on which its pServers are configured. An application service can have multiple network resources.
Clicking Modify...
The Modify Network Resource dialog box lets you configure an IP resource for use by application services in the current LPAN.
This dialog box contains the following fields:
Name
The name of the network resource.
1-1
Book Title
Description
A brief identifying note about the network resource or its use.
Interface
The interface to which the IP resource is mapped. Select one of the following:
Ethernet
Indicates a specific virtual Ethernet interface (vEth). (This vEth interface is potentially shared among one or more applications or processes running on the pServer.)
vSwitch
Indicates a Virtual Switch to which the vEth will connect. (This vEth interface is less likely to be shared among one or more applications or processes running on the pServer.)
MAC Address
The software Media Access Control (MAC) address associated with the network resource. PAN Manager can auto-generate a MAC address for the network resource, or you can supply your own custom MAC address.
Rate Limit
Rate limiting is not supported by the Windows operating system or any operating system running as a vBlade guest on a platform.
In a typical network environment, a system administrator can control the rate of network traffic by using NICs that operate at different speeds. Similarly, you can control the rate of network traffic for each network resource.
Selecting Unlimited places no restriction on the flow of network traffic through this network resource (vEth); selecting a specific
1-2
value limits the flow of network traffic through this network resource.
None
If selected, indicates either that you must select an interface by selecting Ethernet or vSwitch, or that you want to dissociate the network resource from a vSwitch in order to delete that vSwitch.
Network Settings
This area of the Network Resource network_resource_name page lets you create and manage the network addresses associated with this network resource.
Clicking Create...
The Create Network Setting dialog box lets you add an IP address (and associated broadcast and netmask addresses) for a network resource to use. This dialog box contains the following fields:
IP Address
The IP address of the network resource. This is the address at which an application service makes itself available to the network.
Broadcast
(Optional) The network segment over which the IP resource broadcasts packets. Leaving this field blank allows PAN Manager to generate the appropriate broadcast address.
Netmask
(Optional) The network address that determines the scope of the network in which the IP resource resides. Leaving this field blank allows PAN Manager to generate the appropriate netmask address.
1-3
Book Title
Clicking Delete...
The Delete Network Settings dialog box lets you remove an IP address (and its associated broadcast and netmask addresses) from a network resource.
Clicking Modify...
The Modify Network Setting dialog box lets you change the broadcast and netmask addresses associated with one or more of the network resource’s IP addresses.
Each heading is a network setting (IP address). Click a heading to display and modify its broadcast and netmask addresses.
Service Assignments
This area of the Network Resource network_resource_name page shows all application services to which the network resource is assigned.
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lists all application services (applications or load balancers) in the current LPAN, and lets you assign the network resource to one or more services. This dialog box contains the following fields:
Service
The application services, if any, to which this resource is assigned. The value in parentheses can be either application or load balancer.
Current pServer
The pServer to which the application service is assigned.
Status
The current run state of the application service, such as Started or Stopped.
1-4
Configure Network Resources
Use the following PAN Manager procedures to configure IP resources for use by applications:
Modifying Network Resources
Modifying Network Settings for a Network Resource
Assign Network Resources
Configure Network Resources (CLI)
Use the following PAN Manager command to configure IP resources for use by applications:
ip -- Creates, lists, or modifies an LPAN’s IP resources for an application or load-balancing service.
1-5
Book Title
1-6
Managing Network File System Resources for Applications
(LPANS > lpan_name > High Availability > nfs_resource_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the Network File System Resource nfs_resource_name page:
Use this page to modify a network file system resource and to assign it to one or more applications in the current LPAN.
About Network File System Resources
Configure a Network File System Resource
Configure a Network File System Resource (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About Network File System Resources
Network file system resources include the file systems and mount points on which the applications and their data reside. An application can have multiple network file systems.
Clicking Modify...
The Modify Network File System Resource dialog box lets you configure network mounted file systems for use by application services in the current LPAN.
This dialog box contains the following fields:
Name
The name of the network file system resource.
Description
1-1
Book Title
A brief identifying note about the network file system resource or its use.
Host
The IP address or hostname of the server on which the exported file system resource exists.
Host Path
The share path of the host.
Access Mode
Whether the file system is read/write (rw) or read only (ro).
Mount point
The specified point of access into a remote file system or directory, such as /mnt/nfs1.
Mount options
All other mount options supported by the pServer’s version of the Linux operating system, including those corresponding to the mount command’s -t and -o flags and arguments.
Create mount point if it does not exist
Selecting this check box creates a mount point on the pServer for this network file system resource when the application starts.
Clearing this check box requires you to create the mount point manually from the operating system’s command line.
Service Assignments
This area of the Network File System Resource nfs_resource_name page shows all application services to which a network mounted file system resource is assigned.
1-2
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lists all applications in the current LPAN, and lets you assign this network file system resource to one or more of them. This dialog box contains the following fields:
Service
The application, if any, to which this resource is assigned. (The value in parentheses is always application; you cannot assign a file system resource to a load balancer.)
Current pServer
The pServer to which the application is assigned.
Status
The current run state of the application, such as Started or Stopped.
Configure a Network File System Resource
Use the following PAN Manager procedures to configure IP resources for use by applications:
Modifying Network File System Resources
Assign Network File System Resources
Configure a Network File System Resource (CLI)
Use the following PAN Manager command to configure IP resources for use by applications:
nfs -- Creates, lists, or modifies the IP resources for an application.
1-3
Book Title
1-4
Managing SCSI File System Resources for Applications
(LPANS > lpan_name > High Availability > scsi_file_system_resource_name)
This page of the PAN Manager graphical user interface is for PAN and LPAN Administrators only.
On the SCSI File System Resource scsi_file_system_resource_name page:
Use this page to modify a disk-based (SCSI) file system resource and to assign it to one or more applications in the current LPAN.
About SCSI File System Resources
Configure a SCSI File System Resource
Configure a SCSI File System Resource (CLI)
Tip: Hovering over an icon displays additional information; click the icon to freeze the display.
About SCSI File System Resources
SCSI file system resources include information about the physical disk on which a file system resides, as well as the file systems and mount points on which the applications and their data reside. An application can have multiple SCSI file system resources.
Clicking Modify...
The Modify SCSI File System Resource dialog box lets you configure SCSI file systems for use by application services in the current LPAN.
This dialog box contains the following fields:
Name
The name of the SCSI file system resource.
1-1
Book Title
Description
A brief identifying note about this SCSI file system resource or its use.
SCSI Disk
Lists the available disk resources on which an application’s file system resource can reside.
Selecting None indicates that the SCSI file system resource is not associated with any SCSI disk. (To remove a disk from an LPAN, the disk must contain no SCSI file system resources.)
SCSI Id
The name of the physical disk on which the file system resource is to reside.
Details
The capacity and manufacturer of the physical disk.
Assignments
The SCSI file system resource assignments.
Mount Points
This area of the SCSI File System Resource scsi_file_system_resource_name page lets you manage file system mount points for a SCSI file system resource.
Clicking Create...
The Create Mount Point dialog box lets you create a point of access into a SCSI file system or directory.
Path
The name of the SCSI file system or directory, such as /mnt/fs1.
Partition
The number of the disk partition on which the SCSI file
1-2
system resides.
Mount Order
The order in which the partitions are mounted. When the application stops or fails over, the partitions are unmounted in the reverse order.
Mount Options
All other mount options supported by the pServer’s version of the Linux operating system, including those corresponding to the mount command's -t and -o flags and arguments.
Mode
Whether the SCSI file system is read/write (rw) or read-only (ro).
Create Mount Point if it does not already exist
Selecting this check box creates a mount point for this file system resource.
Clearing this check box requires you to create the mount point manually from the operating system’s command line.
Scan partition before mounting
If selected, checks, and optionally repairs, the partition before the partition is mounted.
Scan options (optional)
If you selected the Scan partition before mounting check box, you can also specify any options, such as the partition’s file system type, to allow the scan to run successfully.
Clicking Delete...
The Delete Mount Points dialog box lets you remove one or more mount points from the SCSI file system resource.
1-3
Book Title
Clicking Modify...
The Modify Mount Point dialog box lets you change the characteristics of one or more mount points on a SCSI file system resource.
(The field descriptions are identical to those in the Create Mount Point dialog box.)
Service Assignments
This area of the SCSI File System Resource scsi_file_system_resource_name page shows all applications to which a SCSI file system resource is assigned.
Clicking Assign/Unassign...
The Assign/Unassign Resource dialog box lists all applications in the current LPAN, and lets you assign this SCSI file system resource to one or more of them. This dialog box contains the following fields:
Service
The application, if any, to which this resource is assigned. (The value in parentheses is always application; you cannot assign a file system resource to a load balancer.)
Current pServer
The pServer to which the application is assigned.
Status
The current run state of the application, such as Started or Stopped.
Configure a SCSI File System Resource
Use the following PAN Manager procedures to configure SCSI file system resources for use by applications:
Modifying SCSI File System Resources
1-4
Assign SCSI Disk Resources
Modifying Mount Points for a SCSI File System Resource
Configure a SCSI File System Resource (CLI)
Use the following PAN Manager command to configure SCSI file system resources for use by applications:
fs -- Creates, lists, or modifies the SCSI file system resources for an application.
1-5
Book Title
1-6
Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.
This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.
Copyright Fujitsu Technology Solutions, 2009
Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.
Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009