User's Guide REFERENCE 86 A1 41EM 06 NOVASCALE NovaScale 5xx5
BLANK
NOVASCALE NovaScale 5xx5 User's Guide Hardware September 2007 BULL CEDOC 357 AVENUE PATTON B.P.
The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works. Copyright Bull SAS 1992, 2007 Printed in France Suggestions and criticisms concerning the form, content, and presentation of this book are invited. A form is provided at the end of this book for this purpose.
Preface Table of Contents Intended Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regulatory Specifications and Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . .
NovaScale 5325 Partitioned Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Subsystem (CSS) Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Platform Administration Processor (PAP) Unit . . . . . . . . . . . . . . . . . . . . . . Integrated Console . . . . . . . . . . . . . . . . . . . . .
Connecting to the Server via the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microsoft Windows Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Detailed Hardware Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FRU Info Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware Tab (Core MFL & PMB only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thermal Zones (CSS module only) . .
Modifying LUN Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking, Testing and Resetting the PMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMB LEDs and Code Wheels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Action Request Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Default Action Request Package . . . . . . . .
Managing Logical Units (Servers Connected to a SAN) . . . . . . . . . . . . . . . . . . . . . . . . Updating SAN LUN Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Declaring Local LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Local LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing LUNs . . . . . . . . . . . . . . . . . .
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x User's Guide
List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45.
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88.
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 96. Customer Information configuration page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97. Autocalls Channel Settings control pane .
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 145. Create new identity advanced setting dialog - example 2 . . . . . . . . . . . . . . . . . . . . . . . . . 146. Select EFI LUN dialog - example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147.
List of Tables Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. PAM illegal characters . . . . . . . . . . .
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. Scheme configuration criteria - example 3 - bi-module server . . . . . . . . . . . . . . . . . . . . . . . Scheme configuration criteria - example 3 - 3 modules server . . . . . . . . . . . . . . . . . . . . . . Scheme configuration criteria - example 3 - 4 modules server . . . . . . . . .
Intended Readers This guide is intended for use by the Administrators and Operators of NovaScale 5xx5 Servers. It will also prove useful to the Administrators and Operators of Bull NovaScale 7000 Series and Bull NovaScale 9000 Series servers. Chapter 1. Introducing the Server describes server hardware components and user environment. Chapter 2. Getting Started explains how to connect to and use the server. Chapter 3. Managing Domains describes how to perform straightforward server domain management tasks.
Regulatory Specifications and Disclaimers Declaration of the Manufacturer or Importer We hereby certify that this product is in compliance with European Union EMC Directive 2004/108/CE, using standards EN55022 (Class A) and EN55024 and Low Voltage Directive 2006/95/CE, using standard EN60950. The product has been marked with the CE Mark to illustrate its compliance.
Federal Communications Commission (FCC) Statement Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Definition of Safety Notices DANGER A Danger notice indicates the presence of a hazard that has the potential of causing death or serious personal injury. CAUTION: A Caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury. Warning: A Warning notice indicates an action that could cause damage to a program, device, system, or data.
Laser Safety Information The optical drive in this system unit is classified as a Class 1 level Laser product. The optical drive has a label that identifies its classification. The optical drive in this system unit is certified in the U.S. to conform to the requirements of the Department of Health and Human Services 21 Code of Federal Regulations (DHHS 21 CFR) Subchapter J for Class 1 laser products.
PAM Writing Rules Illegal Characters The following table lists the illegal characters that must not be used in PAM identifiers. Illegal Characters à, é, è, ù, ^, ¨ Accentuated letters / Slash \ Backslash " Double quote ' Simple quote ` Inverted comma & Ampersand + Plus * Asterisk % Percent = Equal sign < Less-than sign > Greater-than sign : Colon ! Exclamation mark ? Question mark ; Semi-colon , Comma ~ Tilde I Pipe operator Space.
String Lengths The following table lists authorized string lengths. String Type CellBlock / System Name Scheme Name History Name Archive Name LUN Name Switch Name Event Name Description Domain Identity Name Table 2. Length 16 32 64 75 (History Name: + 11 (_JJMMAA_nnn) 32 32 32 256 (Scheme: unlimited) 16 String length rules Registry Keys PAM obtains file paths via 2 registry keys: • ReleaseRoot: Contains PAP application file paths (DLL, WEB pages, models,...).
AZERTY/QWERTY Keyboard Lookup Table Figure 1. AZERTY keyboard Figure 2.
Administrator's Memorandum Domains • Manage Domain Schemes, on page 3-5 • Synchronize NovaScale 5xx5 SMP Server Domains, on page 3-6 • Power ON a Domain, on page 3-14 • Power OFF a Domain, on page 3-18 • Perform a Manual Domain Reset, on page 3-25 • Perform a Domain Force Power OFF, on page 3-21 • Perform a Domain Memory Dump, on page 3-24 • View Domain Functional Status, on page 3-29 • View Domain Power Logs, on page 3-31 • View Domain Powering Sequences, on page 3-32 • View Domain BIOS Info, on page 3-33
Configuration • Set up Server Users, on page 5-4 • Configure System and Data Disks, on page 5-5 • Use the EFI Boot Manager, on page 5-7 • Use the EFI Shell, on page 5-9 • Set Up and Configure the EFI Network, on page 5-14 • Set up PAP Unit Users, on page 5-17 • Modify Customer Information, on page 5-17 • Configure PAM Autocall Parameters, on page 5-20 • Customize PAM Settings, on page 5-22 • Deploy a New PAM Release, on page 5-23 • Activate a PAM Version, on page 5-24 • Back Up and Restore PAM Configuration
Operator's Memorandum Domains • Synchronize NovaScale 5xx5 SMP Server Domains, on page 3-6 • Power ON a Domain, on page 3-14 • Power OFF a Domain, on page 3-18 • Perform a Domain Force Power OFF, on page 3-21 • Perform a Manual Domain Reset, on page 3-25 • Perform a Domain Memory Dump, on page 3-24 • View Domain Functional Status, on page 3-29 • View Power Logs, on page 3-31 • View Domain Powering Sequences, on page 3-32 • View BIOS Info, on page 3-33 • View Domain Request Logs, on page 3-34 • View Domain C
xxviii User's Guide
Chapter 1. Introducing the Server This chapter describes the main hardware components and user environment for NovaScale 5xx5 Servers.
Bull Novascale Server Overview Bull NovaScale Servers for business and scientific applications are based upon the FAME architecture (Flexible Architecture for Multiple Environments), leveraging the latest generation of Intel Itanium 2 processors. Servers are designed to operate as one to eight hardware-independent SMP systems or domains, each running an Operating System instance and a specific set of applications.
Server Features The main features of Bull NovaScale Servers are: Intel Itanium Processor Family architecture: - Modularity, predictable performance and growth High availability: - Component redundancy - Capacity to isolate or replace a faulty component without service disruption - Global and unified system visibility - Round-the-clock operation Scalability: - Dynamic partitioning - Power on demand: capacity to dynamically adapt resources and processor frequency to load requirement Simultaneous suppo
Server Hardware Note: Abbreviations and acronyms are documented in the Glossary. Main server hardware components are: Central SubSystem Module (CSS Module) Main server hardware components are housed in the CSS Module.
Midplane Fan & Logistics Board (MFL) 16 Fans and various logistics components are implemented on the MFL. The MFL is connected to both the MIO and the MQB. Fanboxes 8 Fanboxes, each housing 2 fans, provide redundant cooling. Rear Unit IO board Compact (IOC) The IOC provides 4 x PCI -X and 2 x PCI-Express buses and a PCI Hot Plug Board (HPB). The IOC communicates with the rest of the system through the high-speed bidirectional link Scalability Port Switches (SPS) located on the MSX.
BIOS The BIOS controls the server startup process, dynamic resource allocation (Domain reconfiguration, hot-plugging), and error handling. The BIOS also includes: • The Extended Firmware Interface (EFI), which provides the OS with system services. • The EFI Shell, an autonomous environment used to run Off-line Test & Diagnostic suites. Platform Administration and Maintenance (PAM) suite The PAM Web-based software suite is used to operate, monitor, and configure the server.
Getting to Know the Server NovaScale 5085 Partitioned Server Note: Server components and configuration may differ according to the version chosen.
NovaScale 5165 Partitioned Server Note: Server components and configuration may differ according to the version chosen. The server is delivered rack-mounted and pre-cabled in a high cabinet, typically containing the following components: XXXXXXXX 1, 15 10* 11 12 13** 14 16 User's Guide XXXXXXXXXXXXXXXXXXXX Rear 8Ux 2 1U 1U 1U 3Ux 2 Free space for additional components (SCSI or FC disks) 14 U * Slideaway console. For an external console, use a KVM extender kit (150m max.).
NovaScale 5245 Partitioned Server Note: Server components and configuration may differ according to the version chosen.
NovaScale 5325 Partitioned Server Note: Server components and configuration may differ according to the version chosen. The server is delivered rack-mounted and pre-cabled in two high cabinets, typically containing the following components: Main Cabinet XXXXXXXX 1, 15, 16, 17 11 13* 18 User's Guide XXXXXXXXXXXXXXXXXXXX Rear 2 or 4 PDU(s) with AC power cable KVM extender (local) * Redundant servers are connected to 2 PDUs and have 4 DPS units. Figure 7.
I/O Cabinet 10 PAP unit with CD-ROM writer, FDD and 2 disks 13 2 PDU(s) with AC power cable 14 2 FC disks 18 KVM extender (remote) Figure 8.
Server Components Note: Server components and configuration may differ according to the version chosen.
Central Subsystem (CSS) Module The CSS module houses main hardware components: Front Rear Front 1 or 2 QBB (Quad Brick Board) subset(s): Each QBB subset houses: • 1 mother board • 2 memory boards • 1 to 4 processors • 16 DIMMs 1 or 2 Internal Peripheral Drawer(s): Each drawer houses: • 2 internal SCSI RAID system disks • 1 DVD-ROM drive • 1 USB port Chaine d DIBs: Two Internal Peripheral Drawers can be inter-connected to house: • 4 SCSI RAID disks, 1 DVD-ROM drive, 1 USB port Rear 1 or 2 IO Box(es) (Inp
Integrated Platform Administration Processor (PAP) Unit Warning: The PAP unit has been specially configured for Bull NovaScale Server administration and maintenance. NEVER use the PAP unit for other purposes and NEVER change PAP unit configuration unless instructed to do so by an authorized Customer Service Engineer. The PAP unit is linked to the server via the Platform Management Board (PMB). It hosts Platform Administration Software (PAM).
Integrated Console According to version, the console is located in the center of a high cabinet or at the top of a low cabinet. The inegrated console contains the keyboard, monitor and touch pad used for local access to the server and to the Platform Administration Processor (PAP) Unit. or • 1 monitor • 1 QWERTY keyboard and touch pad • 1 power cable Figure 11.
Keyboard / Video / Mouse (KVM) Switch The KVM Switch allows the use of the integrated console for the local server and the local Platform Administration and Maintenance console. 8-Port KVM Switch Or Or • 8 ports • 1 power cable Figure 12. 8-port KVM switch features 16-Port KVM Switch • 16 ports • 1 power cable Figure 13. 16-port KVM switch features KVM Extender Figure 14. KVM extender (local & remote) 300m maxi.
FDA 1x00 FC Disk Rack Optionally, the FDA 1x00 FC Disk Rack is delivered with pre-installed system disks (two RAID#1 and one spare disk per domain). Empty slots can be used for data disks. According to version, the Disk Rack is located in the main or I/O cabinet. • 15 slots • 2 FC RAID controller cards, 1 FC port per controller • 3 disks per domain (2 RAID#1 + 1 spare) • 2 power cables (redundant power supply) Figure 15.
FDA 1x00 FC Extension Disk Rack The FDA 1x00 FC Extension Disk Rack offers15 empty slots for data disks. According to version, the Disk Rack is located in the main or I/O cabinet. • 15 slots • 2 power cables (redundant power supply) Figure 17.
Ethernet Hub The optional Maintenance LAN Ethernet Hub is used to connect PMB, PAP Unit and external FDA FC Disk Rack Ethernet ports. Ethernet Hub - 8 ports - 1 power cable - 1 power bar Figure 18. Ethernet hub features USB Modem The optional USB modem is used to transmit Autocalls to the Remote Maintenance Center, if your maintenance contract includes the Autocall feature. USB Modem - 1 USB cable - 1 RJ11 cable Figure 19.
Accessing Server Components During normal operation, cabinet components can be accessed from the front. Customer Service Engineers may also remove the rear and side covers for certain maintenance operations. Important: Optimum cooling and airflow is ensured when the cabinet door is closed. Opening the Front Door Tools Required: • Cabinet key Figure 21. Opening the front door 1. Unlock the front door with the key. 2. Pull out the locking mechanism and turn to open. 3. Open the door as required.
Opening / Closing the Integrated Console The server is equipped with an integrated console for local administration and maintenance operations. Figure 22. Integrated console example To open the integrated console: 1. Slide the console forward until it clicks into place. 2. Use the front bar to lift the screen panel into position. To close the integrated console: 1. Press the 2 buttons marked PUSH on either side of the keyboard panel to release the console. 2. Lower the front bar to close the screen panel.
Bull NovaScale Server Resources Note: According to server configuration and version, certain features and functions described in this guide may not be accessible. Please contact your Bull Sales Representative for sales information. System Resource and Documentation CD-Roms The Bull NovaScale Server System Resource and Documentation CD-Roms contain all the firmware and documentation referred to in this guide.
EFI Utilities The Bull NovaScale Server EFI utilities provide a complete set of configuration, operation, and maintenance tools: • EFI driver, • EFI Shell, • EFI system utility, • EFI system diagnostic, • Operating System loader. For further details, see Chapter 5. Tips and Features for Administrators.
1-24 User's Guide
Chapter 2. Getting Started This chapter explains how to connect to and start server domains.
Connecting to the PAM Web Site The server is equipped with an integrated Platform Administration and Maintenance software package, otherwise known as PAM software. One part of PAM software is an embedded application (MAESTRO) running on the Platform Management Board (PMB) and the other is an external application running on the Platform Administration Processor (PAP) unit under Microsoft Windows.
Connecting to the PAM Web Site from a Remote Computer The PAM Software utility can be accessed from any PC running Microsoft Windows with the Internet Explorer (6 or later) browser installed and/or from any workstation running Linux with the Mozilla (1.7 or later) or Firefox (1.0) browsers installed. Important: Before connecting to PAM from a remote computer, you are advised to disconnect from your local Windows session on the PAP unit by clicking Start → Log Off.
Simultaneous Connection to the PAM Web Site Several users can access the PAM Web site simultaneously. Important: If configuration changes are made, they may not be visible to other users unless they refresh the PAM Tree. As Customer Administrator, you can view the list of PAM users currently logged onto the PAM Web site by clicking Hardware Monitor -> PAM Web Site. The Web site version and a list of connected users and session details are displayed in the Control pane.
PAM User Interface The PAM user interface is divided into three areas in the browser window: a Status pane, a PAM Tree pane, and a Control pane. A Status pane, on page 2-6 B PAM Tree pane, on page 2-7 C Control pane, on page 2-6 Figure 26.
Checking Server Status via PAM The PAM user interface allows you to check system status at a glance. If the Functional Status icon in the Status pane and the CSS Availability Status bar are green, the server is ready to be powered up.
CSS Availability Status Bar The CSS availability status bar reflects the operational status of the data link(s) between the Platform Management Board (PMB) embedded in each CSS Module and the PAP Unit. Each CSS module is represented by a zone in the status bar. • When a CSS Module PMB is detected as PRESENT, the corresponding zone in the status bar is GREEN. • When a CSS Module PMB is detected as ABSENT, the corresponding zone in the status bar is RED.
PAM Tree Toolbar The PAM Tree toolbar, located at the top of the PAM Tree, is used to refresh, expand, or collapse the tree display. Toolbar Buttons Explanation Refresh /rebuild the PAM Tree to view changes. Expand the complete tree. Collapse the complete tree. Expand selected node. Collapse selected node. View the related Help topic. Figure 29. PAM Tree toolbar Setting up Users As Customer Administrator, you must set up user accounts and passwords to control access to the PAP unit.
Toggling the Local / Integrated Console Display During the powering up / down sequences, you will be requested to toggle the local / integrated console from the PAP unit display to the server domain display, or vice versa, as explained below. CAUTION: Access to the local / integrated console should be restricted to Customer / Support Administrators and Operators ONLY to avoid inadvertent damage to software and/or hardware components.
Powering Up / Down Server Domains To power up / down the server, see: • Powering Up / Down the NovaScale 5xx5 Partitioned Server Domains, on page 2-12 Powering Up the NovaScale 5xx5 SMP Server Domain NovaScale 5xx5 SMP Servers are designed to operate as single SMP systems and are delivered with one pre-configured domain. When server status has been checked - functional status icon and CSS availability status bar green in the Status pane - the server domain can be powered up.
7. Follow the power-on steps displayed in the Domain State box, until RUNNING is displayed. Figure 31. Domain state 8. Toggle the local / integrated console from the PAP unit display to the server display. See Toggling the Local / Integrated Console Display, on page 2-9. 9. Wait for the Operating System to load completely. The domain is now fully functional. 10.Check the Operating System environment pre-installed on the domain. 11.
Powering Up NovaScale 5xx5 Partitioned Server Domains According to version, NovaScale 5xx5 Partitioned Servers are designed to operate as up to eight hardware-independent SMP systems, or domains. For easy configuration and optimum use of the physical and logical resources required for simultaneous operation, domains are defined by the Customer Administrator via the PAM Domain Scheme wizard. For further details about domain configuration, see Configuring Domains, on page 5-28.
To power up server domains: 3. From the PAM Tree, click Domain Manager to open the Control pane. You are invited to load a domain configuration scheme. 4. Click Schemes. The Schemes List dialog opens displaying the pre-configured scheme. 5. Select MyOperationsScheme and click Apply. Figure 32. Domain schemes list dialog 6. When requested, click Yes to confirm. The default domains are loaded in the Control pane.
8. Click Power On All → Execute to simultaneously power on the domains and associated hardware components. Figure 34. Multiple power dialog - example with 4 domains Note: Domains can also be powered on sequentially from the Control pane: • Select a domain in the Control pane and click Power On to power up the domain and associated hardware components. Repeat this step for each domain in the Control pane. 9.
16.As Customer Administrator, you can now prepare each domain for remote access via the Enterprise LAN and/or via the Web. See Preparing Server Domains for Remote Access via the Enterprise LAN, on page 2-16 and Preparing Server Domains for Remote Access via the Web, on page 2-18. Powering Down NovaScale 5xx5 Partitioned Server Domains 1. Shut down each Operating System to power down the corresponding domain to the stand-by mode. 2. Toggle the local / integrated console to the PAP unit display.
Preparing Server Domains for Remote Access via the Enterprise LAN CAUTION: Access to the local / integrated console should be restricted to Customer / Support Administrators and Operators ONLY to avoid inadvertent damage to software and/or hardware components. Note: Required networking data is indicated in the Read Me First document delivered with the server and is also recorded under the corresponding PAM Domain Identity. Customer Administrator rights are required for all PAM configuration tasks.
9. Click Return to index. 10.Click Log Out to exit Webmin. 11.Toggle the integrated console to the PAP unit port. 12.From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Identities to open the Identities page. 13.Select the corresponding Linux domain from the list and click Edit to open the Edit an Identity dialog. 14.Check that the Network Name, IP Address, and URL fields are completed.
Preparing Server Domains for Remote Access via the Web CAUTION: Remote access via the Web is a potential security hazard. Customers are strongly advised to protect their systems with up-to-date protection devices such as virus-prevention programs and firewalls, and to maintain a detailed record of authorized users. Microsoft Windows Domain 1. Toggle the integrated console to the corresponding Windows domain port. See Toggling the Local / Integrated Console Display, on page 2-9. 2.
Connecting to a Server Domain via the Enterprise LAN Microsoft Windows Domain 1. Check that Client for Microsoft Networks is installed on the remote computer and that the remote computer is connected to the same LAN as the server domain. 2. Check that Client for Remote Desktop is installed on the remote computer. If the Remote Desktop Connection menu does not exist: a. Click Start → Run. b. Type \\\tsclient\win32\setup.
Connecting to the Server via the Web Microsoft Windows Domain 1. Check that Internet Explorer (6 or later) and Terminal Server Client are installed on the remote computer. 2. Launch the Internet Explorer or Netscape browser and connect to the server desktop, url: http:///tsweb/, where is the network name given to the server domain during the Windows setup completion procedure. See the Read Me First document delivered with the server.
Installing Applications Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. When you install an application protected by a system serial number, you are requested to supply this serial number.
2-22 User's Guide
Chapter 3. Managing Domains This chapter explains how, as Customer Administrator and/or Customer Operator, you can manage server domains.
Introducing PAM Domain Management Tools Important: Certain domain configuration and management tools are reserved for use with partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. A Bull NovaScale Server domain englobes all the hardware and software resources managed by an Operating System instance. NovaScale 5xx5 SMP Servers are designed to operate as single SMP systems and are delivered with one pre-configured domain.
From the PAM Tree, click Domain Manager to open the Control pane. Multiple Power Powering View Toolbar (1) Allows you to simultaneously power on /off several domains. See Powering ON a Domain, on page 3-14 and Powering OFF a Domain, on page 3-18. Dynamically displays domain power sequences and gives access to Power Logs, see details on page 3-31 and BIOS Info, see details on page 3-33.
Power On Command Bar (3) Powers on the selected domain, see details on page 3-14. Power Off Powers off the selected domain, see details on page 3-18. Reset Resets the selected domain, see details on page 3-25. Force Power Off Forcibly powers off the selected domain, see details on page 3-21. Displays power sequence logs, see details on page 3-31. Displays Power On, Power Off, and Reset requests and requestors, see details on page 3-34. Gives access to the domain fault list, see details on page 3-28.
Managing Domain Configuration Schemes Important: Reserved for partitioned servers and extended systems. Certain features described below are only available if you are connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information.
NovaScale 5325 Partitioned Server The NovaScale 5325 Partitioned Server is designed to operate as from one to heigh hardware-independent domains. The server is delivered with a pre-configured domain configuration scheme called MyOperationsScheme containing four domains, MyOperations-1, MyOperations-2, MyOperations-3, MyOperations-4, MyOperations-5 MyOperations-6, MyOperations-7 and MyOperations-8, allowing you to manage and administer all server resources.
2. Click Schemes in the Toolbar to open the Schemes List dialog. Figure 36. Schemes list dialog 3. Select the required Scheme from the list and click Preview to view scheme properties. CellBlocks Shows the Central Subsystems included in the scheme and how they are partitioned into domains. D Identifies physical partitions. Domain Identities Shows the Identities allocated to each domain. EFI LUNs Indicates the EFI LUNs used to boot each domain. Data LUNs Indicates the Data LUNs used by each domain.
Loading a Domain Configuration Scheme To power on server domains, you must first load the required Domain Configuration Scheme from the Domain Manager Control pane. Once the domain configuration scheme has been loaded, domains can be powered up simultaneously or independently. To load a scheme: 1. Click Domain Manager to open the Control pane. If a scheme has not been previously loaded, you are invited to load one. Note: If the required scheme is already loaded, it is available for domain management.
If the domains are ready to be powered up, INACTIVE is displayed in the Domain State boxes. The Power On button becomes accessible once a domain has been selected. Functional status icon & CSS availability status indicator GREEN Operating System type Select a domain to access the Power On button Figure 39.
Adding Domains to the Current Domain Configuration A scheme can include domains from one or more Central Subsystems. More domains can be made available for domain management by adding one or more schemes to the current domain configuration. Notes: • New domains can only include resources that are INACTIVE in the current domain configuration.
Saving the Current Domain Configuration Snapshot Note: Reserved for Customer Administrators. You may want to save the current domain configuration, in particular if more than one scheme has been loaded and/or if you have modified domain configuration. When you save the current domain configuration, you create a new domain configuration scheme which is then available for domain management. To save the current domain configuration snapshot: 1. Click Domain Manager to open the Control pane. 2.
MyOperationsScheme Organization - NovaScale 5xx5 Partitioned Servers Domain Identity: MyOperations-1 Hardware Cell Cell_0 Operating System Windows or (customer-specific) Linux EFI LUN** *_0LU0 / _LUN0 IOC Module0_IOC0 QBBs Module0_QBB0 Domain KVM Ports ***CSS0_Mod0_IO0 Domain Identity: MyOperations-2 Hardware Cell Cell_1 Operating System Windows or (customer-specific) Linux EFI LUN** *_0LU1 / _LUN1 IOC Module0_IOC1 QBBs Module0_QBB1 Domain KVM Ports *
Operating System type is indicated by the Microsoft Windows or Linux logo in the Domain Identities box. Table 6.
Powering On a Domain What You Can Do During the domain power-on sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status Important: Certain domain configuration and management tools are reserved for use with partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information.
- If a Scheme is already loaded, but is not the required Scheme, see Adding Domains to the current Domain Configuration and Replacing the current Domain Configuration, on page 3-10. 2. Select the required domain. If the domain is in the stand-by mode, INACTIVE is displayed in the Domain Status panel and the Power On button is accessible.
- If the required domain configuration scheme is already loaded, the corresponding domain(s) are available for domain management. Go to Step 2. - If a scheme has not been previously loaded, you are invited to select and load a scheme. See Viewing a Domain Configuration Scheme, on page 3-6 and Loading a Domain Configuration Scheme, on page 3-8.
POWERED ON - LOADING BIOS BIOS READY - STARTING EFI EFI STARTED - BOOTING OS RUNNING Table 8. Power-on states Once the Power On sequence has been successfully completed, RUNNING is displayed in the Domain Status panel and the Power Off, Reset and Force Power Off buttons become accessible. For a detailed view of the Power On sequence, click Powering View in the Toolbar. See Viewing Domain Powering Sequences, on page 3-32.
Powering Off a Domain What You Can Do During the domain power-off sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status Server domains can either be powered off from the Operating System (RECOMMENDED) or from the PAM Domain Manager, according to Operating System power settings. The PAM Power Off command is a shutdown request to the Operating System.
Once the Power Off sequence has been successfully completed, INACTIVE is displayed in the Domain Status panel and the Power On button becomes accessible. For a detailed view of the Power Off sequence, click Powering View in the Toolbar. See Viewing Domain Powering Sequences, on page 3-32. 5. Repeat Steps 2 to 4 for each domain to be powered down. Note: If an error message is displayed in the Domain Status panel, the Power Off sequence has failed. See What To Do if an Incident Occurs, on page 3-42.
The Operating System saves data, closes open applications and shuts down. Domain hardware is powered down from the main mode to the stand-by mode. As the power-off sequence progresses, power-off steps and domain state are displayed in the Domain Status panel, as shown in the following table. Power Off States POWERING DOWN INACTIVE Table 10.
Forcing a Domain Power Off What You Can Do During the domain force power-off sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status The Force Power Off command powers down domain hardware to the standby mode independently of the Operating System.
Forcibly Powering Off a Single Domain To forcibly power off a single domain from the PAM Domain Manager: 1. Click Domain Manager to open the Control pane. 2. Select the required domain. If INACTIVE is NOT displayed in the Domain Status panel, the Force Power Off button is accessible. 3. Click Force Power Off to override the Operating System and forcibly power down the domain and associated hardware components without closing running applications and saving data.
Deselect All Cancels all selected operations. Power On All Powers on all INACTIVE domains. Power Off All Powers off all RUNNING domains. Force Power Off All Forcibly powers off all RUNNING or HUNG domains. Deselect Cancels the selected operation for this domain. Power On Powers on this domain if INACTIVE. Power Off Powers off this domain if RUNNING. Force Power Off Forcibly powers of this domain if RUNNING or HUNG. Execute Applies all selected operations.
Performing a Domain Memory Dump The Dump command is used when the Operating System hangs and allows technicians to diagnose software problems by saving domain memory. Warning: The Dump command should only be used if the Operating System is not able to respond to a standard Power OFF command. The Dump command may result in domain data loss and file corruption. The Dump command does not power down domain hardware (automatic warm reboot). The Operating System must be configured to accept a dump command.
Manually Resetting a Domain What You Can Do During the domain reset sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status The Reset command is used to restart the current Operating System without powering off/on the domain. Warning: The Reset command should only be used if the Operating System is not running or is not able to respond to a standard Power Off command.
Deleting a Domain Notes: • Reserved for Customer Administrators. • The domain must be INACTIVE to be deleted. Once loaded in the Domain Manager Control pane, a domain can be deleted from the current configuration. When the domain has been deleted, the corresponding resources can be re-allocated to another domain. To delete a domain from the current configuration: 1. Click Domain Manager to open the Control pane. 2. Select the required domain. 3. Click Delete in the Command bar.
An information box opens, informing you that the domain has been successfully deleted. The domain is no longer visible in the Control pane. Figure 47. Domain deleted information box 5. Click OK to continue. Note: Domain modifications are not automatically saved and are only applicable while the selected domain is loaded in the Domain Manager Control pane. If required, you can manually save the new configuration for future use. See Saving the Current Domain Configuration Snapshot, on page 3-11.
Viewing a Domain Fault List The Domain Fault List page allows you to view messages about the faults encountered since the beginning of the last power-on sequence on the selected domain. The fault list is automatically cleared when a new domain power-on sequence is started. Note: For details about PAM messages, see Viewing and Managing PAM Messages, History Files and Archives, on page 4-31. To view the domain fault list: 1. Click Domain Manager to open the Control pane. 2.
Viewing Domain Functional Status The Domain Functional Status indicator in the Domain Manager Control pane shows the functional status of the last action performed on each domain, e.g. if the last Power ON/OFF sequence was successful, the indicator is green, and also reflects the status of domain hardware components.
Indicator Green Yellow Orange Red Table 15. 3-30 User's Guide Status Explanation Control Pane The last command on this domain was successful. or The domain fault list has been cleared. Note: NORMAL Domain functional status is reset to NORMAL when a new domain power-on sequence is started. PAM Tree The last command on all domains was successful. or All domain fault lists have been cleared. Control Pane An automatic Recovery command has been launched on this domain.
Viewing Domain Power Logs Power logs are recorded during domain power ON/OFF sequences. This information is particularly useful for troubleshooting. See What To Do if an Incident Occurs, on page 3-42. During a Power ON/OFF Sequence 1. Click Domain Manager to open the Control pane. 2. Select the required domain and launch the domain power ON/OFF sequence, as required. 3. Select the View Power Logs checkbox in the Power Confirmation dialog to automatically display power logs during the powering sequence.
Viewing Domain Powering Sequences A detailed view of powering sequences can be displayed by clicking Powering View in the Domain Manager Toolbar after a power request. Status Panel Item Explanation Domain Selected domain identity. Central Subsystem Name of the Central Subsystem containing the domain. Domain State Current power sequence step. Functional Status Functional status of the last action performed on the domain. See Viewing Domain Functional Status, on page 3-29.
Viewing Domain BIOS Info BIOS information is particularly useful for troubleshooting. See What To Do if an Incident Occurs, on page 3-42. To view BIOS information: 1. Click Domain Manager to open the Control pane. 2. Select the required domain. 3. Click Powering View -> BIOS Info in the Toolbar. The BIOS Info dialog opens, displaying the following information: - BIOS version used by the domain, - BIOS boot post codes. See BIOS POST Codes. 4. Click Refresh to update BIOS information. Figure 51.
Viewing Domain Request Logs The Request Logs dialog gives direct access to a trace of major domain operations (requests) and indicates their initiators (requestors). To view Request logs: 1. Click Domain Manager to open the Control pane. 2. Select the required domain. 3. Click Request Logs in the Command bar. The Request Logs dialog displays the following information: - Power On requests and requestors, - Power Off requests and requestors, - Reset requests and requestors. Figure 52.
Viewing Domain Configuration, Resources and Status Note: Certain features described below are only available if you are connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. Information about the resources allocated to each domain is permanently accessible from the Domain Manager Control pane: • Graphic representation of domain configuration. • Non-graphic summary of the hardware resources allocated to a domain.
View Domain Dialog Items Domain Item Explanation Central Subsystem Name of the Central Subsystem containing the domain. Domain Identity Logical name and profile given to the domain.
Domain Item Cell Explanation Cell(s) or hardware partition(s) used by the domain.
Viewing Domain Hardware Resources 1. Click Domain Manager to open the Control pane. 2. Select the required domain and click View Resources in the View Domain dialog to open the Domain Hardware Resources dialog. Figure 56.
Figure 57. Domain Hardware Details dialog Domain Hardware Details icons are explained in the following table.
Item Icon Green Red Pink Power Status Gray Gray Yellow/ red Gray Green Red Purple Green Yellow Functional Status Orange Red Purple Memory Board Main power is OFF. Stand-by power is OFF. Main power is Faulty. Stand-by power may be ON, OFF or Faulty. Main power status is Unknown. To be logically included at the next domain power ON. To be logically excluded at the next domain power ON. To be functionally excluded from the domain (locked). Green Presence Status Main power is OFF.
Note: When the domain is INACTIVE, the Domain Hardware Details dialog indicates the resources that PAM will try to initialize for the domain during the next Power ON sequence. When the domain is RUNNING, the Domain Hardware Details dialog indicates the resources that PAM successfully initialized for the domain during the last Power ON or Reset sequence.
What To Do if an Incident Occurs When an incident occurs during a domain Power ON / Power OFF / Force Power OFF / Reset sequence, a message is displayed in the Domain Status panel and a trace is recorded in the Domain POWER Logs. Table 17 indicates the messages that may be displayed during an incorrect power sequence.
Dealing with Incidents When you open the incident Help File, you may be requested to contact your Customer Service Engineer or perform straightforward checks and actions: Checking POST Codes If you are requested to check POST Codes, see Viewing Domain BIOS Info, on page 3-33. Checking Hardware Exclusion Status If you are requested to check hardware exclusion status, see Excluding / Including Hardware Elements, on page 4-23.
3-44 User's Guide
Chapter 4. Monitoring the Server This chapter explains how, as Customer Administrator, you can supervise server operation and how as Customer Administrator and/or Operator you can view and manage PAM Messages, Histories, Archives and Fault Lists.
Introducing PAM Monitoring Tools Main Central SubSystem (CSS) hardware components are managed by the comprehensive Platform Administration and Maintenance (PAM) software specifically designed for Bull NovaScale Servers. Note: Peripheral devices such as disk racks, PCI adapters, KVM switch, local console, and the PAP unit are managed by the Operating System and/or by dedicated software.
Viewing System / Component Status What You Can Do • Check system status • Check CSS module availability status • Check event message status • View hardware presence status • View hardware functional status • View server hardware status • View FRU information • View firmware information • View thermal status • View power status • View temperature status • View fan status • View jumper status • View PCI slot status PAM Status Pane When you log onto the PAM Web site, you are able to check system status at a g
CSS Availability Status The CSS availability status bar reflects the operational status of the data link(s) between the Platform Management Board (PMB) embedded in each CSS Module and the PAP Unit. Each CSS module is represented by a zone in the status bar. • When a CSS Module PMB is detected as PRESENT, the corresponding zone in the status bar is GREEN. • When a CSS Module PMB is detected as ABSENT, the corresponding zone in the status bar is RED.
PAM Tree Pane As Customer Administrator, you can view the presence and functional status of each hardware element from the PAM Tree pane. The PAM Tree pane is refreshed at your request. Use the Refresh PAM Tree button to update the display when required. Important: To maintain a trace of transient faults, PAM Tree functional and/or presence status indicators will not change color until the domain has been powered OFF/ON, even if the error has been corrected.
When hardware presence status is normal, all presence status indicators are green. The following table explains possible hardware presence status indications. Presence Status Indicators Indicator Status Green Red Red/white Purple NORMAL This hardware element: - is physically present and accessible. MISSING This hardware element: - was present in a previous configuration but has disappeared.
Displaying Functional Status You can toggle the PAM Tree to view system / hardware functional status (round, colored indicator next to the Hardware Monitor node). If you expand the PAM Tree, the functional status of all hardware elements is displayed. Functional Status is a composite indicator summarizing Failure Status, Fault Status, Power Status, and Temperature Status indicators, where applicable.
When hardware functional status is normal, all functional status indicators are green. Table 20. explains possible hardware functional status indications. Functional Status Indicators Indicator Green Yellow Orange Red Purple Table 20. Status Explanation NORMAL No problem detected. This hardware element is operating correctly. WARNING Minor problem reported. This hardware element is still operational. CRITICAL Serious problem reported.
1 Functional status: Warning 2 PAM Tree automatically expanded to faulty CPU Figure 62.
Using PAM Utilities What You Can Do • Search for excluded hardware elements • Search for missing hardware elements • View PAM Web site information • View PAM version information • Exclude / include hardware elements Using the Hardware Search Engine The Hardware Search engine allows you to search for and view hardware elements corresponding to selected criteria, for example Excluded or Missing hardware elements. Notes: • Excluded hardware elements are those that have been logically excluded from the server.
3. Once the search is complete, results are displayed in the control pane. Figure 64.
Viewing PAM Web Site User Information As Customer Administrator, you can view the list of PAM users currently logged onto the PAM Web site by clicking Hardware Monitor → PAM Web Site. The Web site version and a list of connected users and session details are displayed in the Control pane. The current session is indicated by the icon. Note: You can view user roles by selecting a user and clicking View Roles in the toolbar.
Viewing PAM Version Information PAM version information may be useful to help your Customer Service Engineer solve software-related problems. To view PAM version, site data and release data, click Hardware Monitor → PAP. The PAP Unit Information Control pane opens, indicating PAM software version details along with PAM Site Data and Release Data directory paths: • the PAM Release Data directory is used for all the files delivered as part of PAM software to ensure configuration consistency.
Viewing Server Hardware Status When you click the CSS Name in the PAM tree (e.g. MYSERVER in the figure), the Hardware Monitor displays a visual representation of the presence and functional status of CSS module components in the Control pane. Each primary hardware element functional status indicator is a clickable hotspot leading directly to the detailed Hardware Status page.
Viewing Detailed Hardware Information For detailed information about module / component / sub-component status, you can either click the corresponding hotspot in the Hardware Monitor Control pane or click the required hardware element in the PAM Tree to open the Hardware Status page. General Tab The General tab gives access to the following information: Presence Status Indicates if the hardware element is physically present and correctly configured. See Presence Status Indicators, on page 4-6.
Failure Status Indicators: Indicator Green Orange Red Status Explanation NORMAL PAM software has detected no failures on this hardware element. DEGRADED PAM software has detected that this hardware element is running at sub-standard capacity but is not jeopardizing system performance. FAILED PAM software has detected a failure that may be jeopardizing system performance. UNKNOWN PAM software is not receiving diagnostic information from this hardware element.
Firmware Tab (Core MFL & PMB only) The Firmware tab gives access to firmware version data for the hardware element. Note: Firmware versions may differ. Figure 70. Firmware data (example) Thermal Zones (CSS module only) Thermal Zones, accessible via the Thermal zones tab, shows the thermal zones monitored by PAM software. A cooling error in a thermal zone will affect all the hardware elements in that zone. See Displaying Functional Status, on page 4-7. Figure 71.
Power Tab The Power tab gives access to power status data for the hardware element, indicating main and standby power state and/or power-specific faults for each converter. See Displaying Functional Status, on page 4-7. Once connected to the Customer's site power supply, server hardware elements initialize to the stand-by mode. Server hardware elements initialize to the main mode when the domain is powered up. Measured values Nominal values Figure 72.
CSS Module Power Tab The Power tab gives access to power status data for the CSS module DPS units. 48V Presence Meaning PRESENT At least 1 DPS unit is ON. ABSENT All DPS units are OFF. Not Found PAM software cannot read CSS module power status. 48V Value Current intensity in Amperes (varies according to configuration). Figure 73.
Temperature Tab The Temperature tab gives access to temperature status data for the hardware element, indicating overtemperature or temperature-specific faults. Figure 74. Temperature probe status details (example) Indicator Green Yellow Status NORMAL Hardware element temperature is normal. WARNING PAM software has detected a rise in temperature on this hardware element, but it is still operational and is not jeopardizing system performance.
Fan Status (Fanboxes only) Fan Status, accessible via the Fans tab, indicates fan status, speed and supply voltage. See Displaying Functional Status, on page 4-7. During normal operation, the display depicts fan rotation. Each fanbox is equipped with 2 hot-swap, redundant, automatically controlled fans. Note: If all fans are halted in the display, check that your browser allows you to play animations in Web pages. Figure 75.
PCI Slots (IOC only) PCI Slot Status, accessible via the PCI Slots tab, shows PCI board type and the functional and power status of PCI slots at the last domain power-on. PCI-Express boards are indicated by a symbol. Power status indicators Figure 77.
Excluding / Including Hardware Elements As Customer Administrator, if a redundant hardware element is faulty, you can logically Exclude it from the domain until it has been repaired or replaced. To be taken into account, exclusion requires domain power OFF/ON. A complete list of logically excluded hardware elements can be obtained via the Hardware Monitor search engine. See Using the Hardware Search Engine, on page 4-10. Important: Hardware elements must be excluded with care.
Notes: • If you want to check domain hardware status, click Domain Manager → Resources → More info... to open the Domain Hardware Details page. • Hardware components to be logically excluded from the domain at the next domain icon in the Lock Request column in the power ON are marked with a red / yellow Domain Hardware Details page. See Viewing Domain Configuration, Resources and Status, on page 3-35.
Hardware Exclusion Guidelines Hardware Element Exclusion Guidelines IMPORTANT: If the following hardware elements are excluded, the corresponding server domain will not power up: • Master IOC, Master IOC HubLink 1, Master IOC PCI Slots 1 & 2, Master IOL Note: When a domain comprises more than one cell (therefore more than one IOC), the Master IOC is the one hosting the boot disk. The other IOCs in the domain are Slave IOCs.
Hardware Element QBB • At least one QBB must be "included" in a domain. Memory Rows • At least one Memory Row must be "included" in a QBB. CPU • At least one CPU must be "included" in a QBB. Note: If all CPUs are excluded from a QBB, the QBB itself is excluded. SPS • At least one SPS must be "included" in a Core Unit. Note: If all SPS are excluded from a Core Unit, the domain will not power up. Clock • At least one Clock must be "included" in a Core Unit.
Excluding / Including Clocks, SPS, XSP Cables and Sidebands PAM software automatically manages and optimizes server ring connections. There are four types of ring connections: • Clocks • SPS • XSP cables • Sidebands (dedicated to error and reset logs) In the event of a failure, your Customer Service Engineer may request you to logically exclude a clock, SPS, XSP cable and/or sideband until the failure has been repaired.
3. Select the required clock(s) by clicking the corresponding icon or table entry. 4. Click Save in the Tool bar to logically exclude / include the clock at the next power-on. Note: The legend at the bottom of the Control pane explains different clock states. In the above figure, no exclusions have been requested / applied.
Excluding / Including XSP Cables For high flexibility, availability and optimum performance, each CSS module is equipped with two XSP cables for inter-module communication. Each XSP cable routes SPS data and clock signals. If an XSP cable is faulty, you can logically exclude it to ensure correct server operation until replaced. Once the fault has been repaired, you can logically include the excluded XSP cable. To logically exclude / include an XSP cable: 1.
Excluding / Including Sidebands The sidebands route reset and error logs. If a sideband is faulty, you can logically exclude it to ensure correct server operation until replaced. Once the fault has been repaired, you can logically include the excluded sideband. To logically exclude / include a sideband: 1. From the PAM Tree pane, click Configuration Tasks → Ring Exclusion to open the Control pane. 2. Select the Sideband tab to display sideband configuration. Figure 84.
Managing PAM Messages, Histories, Archives and Fault Lists What You Can Do • View Web event messages • Acknowledge Web event messages • Sort and locate Web event messages • View e-mailed event messages • Display the hardware faults list • View history files online • View archive files online • View history files offline • View archive files offline • Manually archive history files • Manually delete archive files A comprehensive set of Event Message subscriptions allows connected and non-connected users to
Understanding PAM Message Severity Levels Messages are graded into four severity levels as shown in the following table. Icon Severity Level SUCCESS INFORMATION WARNING ERROR Table 26. Explanation An action requested by a user has been performed correctly or a function has been completed successfully. Information message, for guidance only. System operation is normal, but status has changed. Information message, for guidance and verification.
Viewing PAM Messages and Fault Lists Whether you consult a Web Event Message, a Faults List, a System / User History or Archive, the resulting display and utilities are the same. Access to Help Message Button Use Acknowledge selected events To remove viewed messages from the pending event list. Select all events To select all Ack checkboxes. Unselect all events To deselect all Ack checkboxes. Help Search - String - Contained in attribute - Case sensitive Reset To access context sensitive help.
Specimen Message Help File The Help File explains the message and indicates related actions, where applicable, as shown in Figure 86. Figure 86. Specimen message help file Viewing and Acknowledging PAM Web Event Messages To view Web event messages: icon to open the Display Events page. See Figure 85. 1. From the Status pane, click the Display Events page, on page 4-33. 2. Click the + sign to expand the required message. 3.
Sorting and Locating Messages From the message display, when you hover the mouse in the Type column, an InfoTip gives a brief summary of the message allowing you to rapidly scan the list for the required message(s). Use the standard + and - signs to expand and collapse selected messages. It may be difficult to locate a message if the list is long, the following short-cuts can be used to organize the display and to locate required messages.
Viewing, Archiving and Deleting History Files History and archive files are systematically stored in the PAMSiteData directory: :\Program Files\BULL\PAM\PAMSiteData\ The PAM History Manager allows you to view, archive and delete history files online and provides you with the tools required to download and view history and archive files offline. As Customer Administrator / Operator, you will frequently consult PAMHistory files for information about system operation.
Viewing History Properties To view history properties: 1. From the PAM Tree pane, click History Manager to open the Control pane. 2. Select the Histories tab. 3. Highlight the required type of history and click Properties. The History Properties dialog opens. Name History name. Description Optional description of history contents. Directory Pathname of the directory used to store histories. If this field is blank, the default Histories directory is used.
Manually Archiving History Files In general, history files are automatically archived at regular periods. However, you can choose to manually archive a history file at any time, if required. Note: Empty history files cannot be archived. To manually archive a history file: 1. From the PAM Tree pane, click History Manager to open the Control pane. 2. Select the Histories tab. 3. Select the required type of history checkbox or select the Archive All checkbox to archive all histories. 4.
Viewing Archive Properties To view archive properties: 1. From the PAM Tree pane, click History Manager to open the Control pane. 2. Select the Archived histories tab. 3. Use the scroll-down menu to select the type of history archive you want to display. The corresponding list of archived histories appears in the Archiving date zone. 4. Highlight the required archiving date and click Properties. The Archive Properties dialog opens. Name History name, archiving date and time.
Manually Deleting a History Archive File In general, history archive files are automatically deleted at regular periods. However, you can choose to manually delete a history archive file at any time, if required. To manually delete a history archive file: 1. From the PAM Tree pane, click History Manager to open the Control pane. 2. Select the Archived histories tab. 3. Use the scroll-down menu to select the type of history archive you want to delete.
5. Click Download Compressed File to compress and download the histories/archives to the required local or network directory for offline viewing. Viewing History / Archive Files Offline 1. Unzip all the files in the History.zip file to a directory of your choice. 2. Click the HistoryViewer.htm file to open the View History File page. 3. Complete the History File Name field and click Read, or click Browse to search for and load the required history or archive file. 4.
What to Do if an Incident Occurs Server activity is systematically logged in the System History files, which you can view as Customer Administrator at any time. When an incident occurs, PAM software informs users via: • the Status pane, • Event Message / History file, • e-mail / SNMP traps (users with an appropriate Event Message subscription), • an Autocall to the Bull Service Center (according to your maintenance contract).
System Functional Status / Expected Domain State Icon Green Yellow System Functional Status Expected Domain State NORMAL RUNNING WARNING RUNNING Orange Flashing CRITICAL Red Flashing FATAL Purple Table 27. INACTIVE (auto Power OFF) / RUNNING An automatic Power OFF request may be sent by PAM software to the domain Operating System: - If the domain Operating System is configured to accept PAM Power OFF requests, it automatically saves data, closes open applications and shuts down.
The following tables list server domain cell resources.
NovaScale Partitioned Server Domain Cell Resources NovaScale 5085 Partitioned Server Cell 0 Module0_IOC0, Module0_QBB0, Module0_DIB0 Cell 1 Module0_IOC1, Module0_QBB1, Module0_DIB1 NovaScale 5165 Partitioned Server Cell 0 Module0_IOC0, Module0_QBB0, Module0_DIB0 Cell 1 Module0_IOC1, Module0_QBB1, Module0_DIB1 Cell 2 Module1_IOC0, Module1_QBB0, Module0_DIB0 Cell 3 Module1_IOC1, Module1_QBB1, Module0_DIB1 NovaScale 5245 Partitioned Server Cell 0 Module0_IOC0, Module0_QBB0, Module0_DIB0 Cell 1 M
Dealing with Incidents When you open the incident Help File, you may be requested to perform straightforward checks and actions or to contact your Customer Service Engineer.
Checking Hardware Connections If you are requested to check hardware connections, manually and visually ensure that all cables are correctly inserted in their corresponding hardware ports. See Cabling Guide, 86 A1 34ER. Excluding a Hardware Element and Checking Exclusion Status As Customer Administrator, you can logically Exclude a redundant hardware element from the domain until it has been repaired or replaced. Exclusion is taken into account at the next domain power ON.
Checking SNMP Settings If you are requested to check SNMP settings, IP address, or server name for an event subscription: 1. From the PAM Tree, click Configuration Tasks → Events → Channels and check that the SNMP Channel is enabled. 2. Click Subscriptions to view configured subscriptions. Channel type is indicated in the Channel column. 3. Select the required SNMP Channel subscription from the list and click Edit to view / modify SNMP settings.
Modifying LUN Properties If you are requested to modify LUN properties: • Refer to Configuring Disks, on page 5-5 and to the appropriate Disk Subsystem documentation. Checking, Testing and Resetting the PMB The PMB is located in the module at the base of the cabinet and links the server to the PAP unit via an Ethernet link.
PMB LEDs and Code Wheels Up to 16 Central Subsystems can be linked, via Platform Management Boards (PMBs) to a single PAP unit, to provide a single point of administration and maintenance. Each PMB is equipped with two code wheels used to identify each Central Subsystem and each CSS module in your configuration. These code wheels are set prior to shipping (factory default setting), according to configuration.
Creating an Action Request Package PAM software allows you to collect all the files required to troubleshoot a Bull NovaScale Server via the Action Request Package tool. Once collected, files are compressed to ZIP format for easy transfer to the BULL Remote Maintenance Center. Note: Before PAM Release 8, use the BackUpRestore utility to copy and restore the files stored in the PAM SiteData directory. Creating a Default Action Request Package 1.
4-52 User's Guide
Creating a Filtered Action Request Package Important: To ensure the consistency of Action Request Package contents, you are advised to only use filtering options if specifically required. 1. From the PAM Tree pane, click Downloads to open the Control pane. 2. Select the AR Package tab and enter the Action Request reference given by the Customer Support Center. 3. Click Show Details to display filtering options.
5. Click Build Action Request package to collect, compress and download files. 6. Transfer the ZIP file to the BULL Remote Maintenance Center for analysis. Creating a Custom Package PAM software allows you to collect one or more selected files from the PAM Site Data Directory via the Custom Package tool. Once collected, files are compressed to ZIP format. This option allows you to precisely select the files you want to collect and download for analysis. To create a Custom Package: 1.
Figure 95. Custom Package Add files pane 4. Click Build Custom Package to collect, compress and download the selected files. 5. Save the resulting ZIP file as required.
4-56 User's Guide
Chapter 5. Tips and Features for Administrators This chapter explains how, as Customer Administrator, you can configure the server to suit your working environment.
5-2 User's Guide
Section I - Setting up Users and Configuring Data Disks This section explains how to: • Set up Server Users, on page 5-4 • Configure System and Data Disks, on page 5-5 Tips and Features for Administrators 5-3
Setting up Server Users As Customer Administrator, you must set up user accounts and passwords to control access to the server. The operating system pre-installed on the server provides standard security features for controlling access to applications and resources. For further details, refer to the Microsoft Windows / Linux documentation, as applicable. Note: You are advised to maintain a detailed record of authorized users.
Configuring System and Data Disks Optionally, for optimum storage, security and performance, the server may be delivered with pre-configured disk racks. New system and/or data disks can be created via the utility delivered with the storage sub-system. Note: For further details about configuring system and data disks, refer to the appropriate Disk Subsystem documentation.
Section II - Using EFI Utilities This section explains how to: • Use the EFI Boot Manager, on page 5-7 • Use the EFI Shell, on page 5-9 • Use the EFI to Set up and Configure a Network, on page 5-14 • Use the EFI to Load FTP Server / Client, on page 5-15 5-6 User's Guide
Using the EFI Boot Manager The EFI (Extensible Firmware Interface) Boot Manager allows you to control the server's booting environment. From the Boot Manager, you can choose to invoke the Extensible Firmware Interface (EFI) Shell or to go to the Boot Option Maintenance Menu. To enter the EFI Boot Manager: 1. From the PAM Tree, click Domain Manager → Power ON to power up the required domain. 2. From the keyboard, press the Control key twice to display the KVM Switch Command Menu. 3.
Description Boot Option Boot from a File This option searches all the EFI System Partitions in the system. For each partition it looks for an EFI directory. If the EFI directory is found, it looks in each of the subdirectories below EFI. In each of those subdirectories, it looks for the first file that is an executable EFI Application. Each of the EFI Applications that meet this criteria are automatically added as a possible boot option.
Using the EFI Shell The EFI (Extensible Firmware Interface) Shell is a simple, interactive user interface that allows EFI device drivers to be loaded, EFI applications to be launched, and operating systems to be booted. In addition, the Shell provides a set of basic commands used to manage files and the system environment variables. The EFI Shell supports command line interface and batch scripting. Entering the EFI Shell To enter the EFI Shell: 1.
Variable Substitution Environment variables can be set and viewed through the use of the set command (see set command in this chapter). To access the value of an environment variable as an argument to a Shell command, delimit the name of the variable with the % character before and after the variable name; for example, %myvariable%. The Shell maintains a special variable, named lasterror. The variable contains the return code of the most recently executed Shell command.
Quoting Quotation marks in the EFI Shell are used for argument grouping. A quoted string is treated as a single argument to a command, and any whitespace characters included in the quoted string are just part of that single argument. Quoting an environment variable does not have any effect on the de-referencing of that variable. Double quotation marks “” are used to denote strings. Single quotation marks are not treated specially by the Shell in any way.
Command 5-12 alias attrib bcfg Batch only No No No Displays, creates, or deletes aliases in the EFI Shell Displays or changes the attributes of files or directories Displays/modifies the driver/boot configuration break No Executes a break point cd cls comp No No No Displays or changes the current directory Clears the standard output with an optional background color Compares the contents of two files connect cp date dblk devices devtree dh disconnect dmem dmpstore drivers drvcfg drvdiag echo edit
Command mount Batch only No Mounts a file system on a block device mv openInfo pause pci reconnect reset rm set stall time type unload ver vol No No No No No No No No No No No No No No Moves one or more files/directories to destination Displays the protocols on a handle and the agents Prints a message and suspends for keyboard input Displays PCI devices or PCI function configuration space Reconnects one or more drivers from a device Resets the system Deletes one or more files or directories Displays, c
EFI Network Setup and Configuration The EFI (Extensible Firmware Interface) Utilities delivered with the system provide a complete set of TCP/IPv4 network stack and configuration tools. Ethernet adapters utilizing 6 bit UNDI option ROMs are supported. Important: To access this feature, please connect the Enterprise network to the embedded Ethernet board on the IOR of the domain master IO board. Intel PRO 1000T and 1000F adapters are not supported.
Example Network Configuration Batch File An example network configuration batch file named NetConf.nsh is installed in the EFI directory of the EFI Service Partition. This file loads the TCP/IP, configures the Ethernet interface to the IP address given as first argument to this file, configures the optional second argument as the gateway, and loads the FTP Server (daemon). echo –off if %1empty == empty then echo usage netconf {local ip–addr} [router ip addr] goto End endif load fs0:\efi\tools\tcpipv4.
Section III - Customizing PAM Software This section explains how to: • Set up PAP Unit Users, on page 5-17 • Modify Customer Information, on page 5-19 • Configure Autocalls, on page 5-20 • Set Thermal Units, on page 5-22 • Deploy a New PAM Release, on page 5-23 • Activate a PAM Version, on page 5-24 • Back up and Restore PAM Configuration Files, on page 5-26 5-16 User's Guide
Setting up PAP Unit Users As Customer Administrator, you must set up user accounts and passwords to control access to the PAP unit. The Microsoft Windows operating system pre-installed on the PAP unit provides standard security features for controlling access to applications and resources. PAM software security is based on Windows user management and you are advised to give Windows administrator rights to at least one member of the PAP Customer Administrator user group.
PAM Tools Domain Manager Hardware Monitor History Manager Configuration Tasks Status Pane Associated Actions CA CO Synchronize domains X X View/load a domain configuration scheme X X Add domains to the current domain configuration X X Replace the current domain configuration X X Delete domains from the current domain configuration X Save the current domain configuration snapshot X Power on/off and reset domains X X Forcibly power off domains X X Perform a domain memory dump X
Modifying Customer Information Customer information is configured during the initial installation procedure, via the PAM configuration setup Wizard. This information is used by PAM software: • for the PAM Tree display: the name entered in the Site name field will be used for the PAM tree root node, • to complete Customer Service Engineer Intervention Reports, • to configure the Email server used to send messages via the e-mail channel. See Creating an E-mail Server, on page 5-136.
Configuring Autocalls The Autocall feature is part of the BULL Remote Maintenance contract. It is used to automatically route system events to the Remote Maintenance Center. Full details are given in the BULL Remote Maintenance Guide. If your maintenance contract includes the Autocall feature, configure Autocall parameters as follows: 3. Click Configuration Tasks → Autocalls. The Autocalls configuration page opens. Figure 97. Autocalls Channel Settings control pane 4. Select the Enable Autocalls checkbox.
8. If FTP dispatch mode is selected, complete the FTP Settings fields with the following information: Field Explanation Value Server name Remote Maintenance Center server IP address 127.0.0.1 Server port Default server port 21 Target directory Default server directory /autocall Login Declared authorized user name X Password Declared authorized user password X Passive mode FTP connection mode check box 9. If a modem connection is to be used: a.
Setting Thermal Units By default, PAM software displays thermal measurements in degrees Celsius. As Customer Administrator, you may change the default setting to degrees Fahrenheit. To change PAM thermal units: 1. Click Configuration Tasks → PAM. The PAM Configuration control pane opens. 2. Click the Celsius or Fahrenheit radio button, as required. 3. Click Save. A green icon appears in the top left corner of the control pane to confirm the change. Figure 98.
Deploying a PAM Release As Customer Administrator, you can re-deploy a PAM release on a backup PAP Unit by running the PAM Installation package x.y.z. msi (x.y.z being the PAM version e.g. 2.1.9 ) file. Important: This procedure should only be used to re-deploy a current PAM Release on a backup PAP Unit. PAM software can only be updated by authorized Customer Service Engineers. To install a PAM Release: 1. From the local PAP unit console, power down all server domains and close the current PAM session. 2.
Activating a PAM Version The PAM InstallShield Wizard automatically creates a shortcut to the PAM Activation utility on the PAP unit desktop that can be used at any time to activate an installed PAM Version. Note: A previous PAM Version can be re-activated at any time, in the event of a problem with the current release. To activate / re-activate a PAM Version: 1. From the local PAP unit console, power down all server domains and close the current PAM session. 2.
4. Click Install to begin activation. 5. Select the Launch PAP Configuration utility checkbox if you want to configure or reconfigure PAP unit settings. Otherwise, click OK to complete activation. 6. From the local PAP unit console, right click the Microsoft Internet Explorer icon on the desktop and click Properties → General → Delete Files to delete all the files in the Temporary Internet Folder. 7. Launch a new PAM session.
Backing Up and Restoring PAM Configuration Files As Customer Administrator, you are advised to regularly save PAM configuration data to a removable media or to a network directory so that it can be rapidly restored in the event of PAP unit failure. PAM software can be deployed on any standard PC running the appropriate version of Microsoft Windows and you can restore your configuration data to rebuild your working environment.
Restoring PAM Configuration Data Warning: The same PAM software release must be deployed on the PAP unit and on the backup PC to allow data restoration. See Deploying a New PAM Release, on page 5-23 and Activating a PAM Version, on page 5-24. PAM releases use the same data directory to ensure configuration consistency. Before activating / re-activating a PAM Version, ensure that the level of deployed releases is compatible.
Section IV - Configuring Domains Important: This section describes domain configuration and management tools that are reserved for use with partitioned servers and extended systems. Please contact your BullSales Representative for sales information.
Partitioning your Server Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Bull NovaScale Servers are designed around a flexible, cell-based, midplane architecture allowing dynamic partitioning into physically independent domains. A domain is a coherent set of hardware and software resources managed by a single Operating System instance.
Figure 101. Schemes and Identites panes A Domain Configuration Scheme is used to define and manage a set of domains that can be active simultaneously. The Schemes control pane allows you to create, edit, copy, delete, and rename domain configuration schemes and update default test schemes. A Domain Identity is used to define and manage domain context information. The Identities control pane allows you to create, edit, copy, and delete domain identities.
Assessing Configuration Requirements Important: Reserved for partitioned servers and extended systems. Certain features described below are only available if you are connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. At least one IOC and one QBB are required for each server domain. You can use the following checklist to help you make an accurate plan of how you want to partition and manage your system.
Domain Identity Checklist What name do I want to use for my Domain Identity to reflect the tasks/jobs it will run? Examples: • MyDataMiningIdentity • MyDataBaseIdentity • MyProductionIdentity • MyTestIdentity Name Description How can I describe my Domain Identity to reflect its use? Examples: • OS and applications • Time zone • Boot path • IP address • Network name • URL • Production / test conditions Operating System Which OS do I want to run on this domain? Does this OS support assigned hardware (CPU
Managing Domain Configuration Schemes Important: Reserved for partitioned servers and extended systems. Certain features described below are only available if you are connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information.
To create a domain configuration scheme: 1. Assess your configuration requirements. See Assessing Configuration Requirements, on page 5-31. 2. If required: - Create EFI and/or Data LUNs from the utility delivered with the storage subsystem. You are advised to use RAID level 1 for EFI LUNs and RAID level 5 for Data LUNs. - Update the SAN LUN and/or Local LUN lists from the Logical Units page. See Updating SAN LUNs, on page 5-59 and/or Updating Local LUNs, on page 5-60 and on page 5-56.
4. Click New in the toolbar to open the Scheme Management dialog. Central Subsystem Scheme Name Name used to identify the scheme. Description Brief description of scheme configuration. Add Select the Central Subsystem used in the scheme. Remove Remove a Central Subsystem from the scheme. Modify Select the number of hardware partitions in the scheme. Domains Remove Remove the selected domain from the scheme. Identity Select a domain identity. EFI LUNs Select an EFI Boot LUN.
NovaScale 5085 Server NovaScale 5165 Server Note: If two CSS Module cells are linked by a Chained DIBs icon module.
NovaScale 5245 Server NovaScale 5325 Server Figure 104. Scheme Creation and Central Subsystem Configuration dialogs Note: If two CSS Module cells are linked by a Chained DIBs icon module. , you cannot partition this 7. In the Central Subsystem list, select the required Central Subsystem. The graphic representation of the selected Central Subsystem appears in the bottom right part of the window.
8. Use the Number of Partitions dropdown list to select the required number of hardware partitions (2 in the examples). The partitions appear in the partition list. 9. Click the first partition in the list and select the cells to be included in this partition. Repeat this step for each partition in the list. Important: For optimum performance, selected cells should be contiguous, as shown in the following figure. Incorrect Correct Figure 105. Optimizing partitioning 10.
NovaScale 5165 Server NovaScale 5245 Server Tips and Features for Administrators 5-39
NovaScale 5325 Server Figure 106. Scheme Management dialog - Central Subsystem configured 11.Click Domains -> Identities to open the Identities Management dialog. Figure 107. Domain Identities list 12.If the required identity is in the list, go to Step 13. If you want to create a new identity for this domain, click New to open the Create New Identity dialog. See Creating a Domain Identity, on page 5-50. 13.
14.Click Domains -> EFI LUNs to open the Select EFI LUN dialog. 1 2 1 SAN storage subystem 2 Local storage subsystem Figure 108. EFI LUN selection list 15.If the required EFI LUN is in the list, go to Step 16. If the required EFI LUN is not in the list, you must exit the Domain Scheme wizard to configure the EFI LUN. See Pre-requisites, on page 5-33. 16.Select the required EFI Boot Lun from the list of available Luns and click OK to return to the Scheme Management dialog.
18.If the EFI LUN is a Local LUN and you do not want to add one or more Data LUNs to the domain, go to Step 28. If the EFI LUN is a SAN LUN and you do not want to add one or more Data LUNs to the domain, go to Step 22. If the EFI LUN is a Local or SAN LUN and you want to add one or more SAN Data LUNs to the domain, click Domains -> Data LUNs to open the Select Data LUN dialog. Figure 109.
19.Select the LUN you want to add to the domain in the Data LUNs available list and click Details to view LUN parameters, if required. Name Name given to the LUN when created. Description Brief description of the LUN. LUN Number Number allocated to the LUN when created. LUN State If the LUN is ready for use, READY is displayed. Type LUN configuration mode. Size LUN size. Subsystem Name Name of the subsystem containing the LUN. Subsystem Model Type of subystem containing the LUN.
20.Click Add. The selected Data LUN is moved to the Data LUNs selected list. Figure 111. Select Data LUN dialog - Data luns selected list 21.Repeat Steps 19 and 20 for each Data LUN you want to add to the domain and click OK to return to the Scheme Management dialog. Data LUN set is now displayed in the Data LUNs field. The Status icon remains red and the No Link icon is displayed. You must now link the selected EFI and Data LUNs to the Fibre Channel Host you want to use to access these LUNs. 22.
23.Select the Redundant checkbox if you want to define two links to the LUN. Note: If you select the Redundant mode, you will be informed that dedicated software is required to enable this mode and you will be requested to confirm your choice. 24.Click Set Primary Link to define the main access path to the SAN. The Select HBA dialog opens, allowing you to select the domain PCI slot you want to use to access the LUN. Figure 113. Select an HBA dialog 25.
NovaScale 5085 Server NovaScale 5165 Server 5-46 User's Guide
NovaScale 5245 Server NovaScale 5325 Server Figure 114. Scheme Management dialog 29.If you do not want to functionally limit access to certain hardware elements, go to Step 30. If you want to functionally limit domain access to certain hardware elements, click Domains → Lock Hardware to open the Lock Domain Hardware Resources dialog. See Limiting Access to Hardware Resources, on page 5-66. 30.Click Save. The domain configuration scheme is now available for domain management.
Editing a Domain Configuration Scheme To edit a domain configuration scheme: 1. Assess your configuration requirements. See Assessing Configuration Requirements, on page 5-31. 2. Click Configuration Tasks → Domains → Schemes in the PAM tree to open the Schemes pane. See Figure 102 above. 3. Select the required scheme from the list. 4. Click Edit in the toolbar to open the Edit Scheme dialog. Central Subsystem Add Click here to add another Central Subsystem to your scheme.
Copying a Domain Configuration Scheme To copy a domain configuration scheme: 1. Click Configuration Tasks → Domains → Schemes in the PAM tree to open the Schemes pane. See Figure 102 above. 2. Select the required scheme from the list. 3. Click Copy in the toolbar. The Copy Scheme dialog opens. 4. Enter a name for the new scheme and click OK. The new domain configuration scheme is now available for domain management. Deleting a Domain Configuration Scheme To delete a domain configuration scheme: 1.
Creating, Editing, Copying, Deleting a Domain Identity Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Note: Domain Identities can either be created via the Domain Configuration Scheme wizard or, independently, via the Identities configuration page. See Creating a Domain Configuration Scheme, on page 5-33. Creating a Domain Identity To create a domain identity: 1. Assess your configuration requirements.
3. Click New in the toolbar to open the Create New Identity dialog. Identity Name Name reflecting the tasks/jobs to be run by the domain. Description Brief description reflecting domain use. Operating System and Version OS and OS version to be run on this domain. Note: Check that the selected OS supports assigned hardware (CPUs, DIMMs)? Network Name Network name used to identify this domain. IP Address IP address used to reach this domain. URL URL used to reach the domain Web site (if any).
5. Click Advanced Settings to open the Advanced Identity Settings dialog. CPU Parameters Enable / disable multithreading. Note: Check that the CPUs used by this domain support the multithreading mode. High Memory IO Space Enable / disable extended PCI gap memory space. Note: Only use if this domain uses PCI boards requiring more than 4GB PCI gap space. Compatibility problems may arise under Windows. IO Memory Space Optimization Enable / disable IO space overlap.
6. Complete the Advanced Identity Settings dialog fields as required: a. CPU Parameters: . Select Multithreading Mode if you want this domain to use multithreading features (if the CPUs used by the domain support the multithreading mode) . Select Monothreading Mode if you do not want this domain to use multithreading features or if the CPUs used by the domain do not support the multithreading mode. b.
Note: An error message (2B2B221F) may be displayed although the domain has been successfully restarted. This error message, generated following the loss of the mains power supply, is not significant. 7. Click OK. The new identity appears in the Identities List page and can be applied to a hardware partition via the Domain Configuration Scheme wizard. Editing a Domain Identity To modify domain identity settings, management parameters and/or description: 1. Assess your configuration requirements.
Managing Logical Units (Servers Not Connected to a SAN) Your server is delivered with default EFI Boot LUNs. You can use the software delivered with your storage subsystem to define data LUNs. What You Can Do • Clear, Load, Save NVRAM Variables • Update the Local LUN Lists To open the Logical Units management page: 1. Click Configuration Tasks -> Domains -> LUNs in the PAM tree. Name Default LUN name EFI EFI This LUN is a boot LUN. DATA This LUN is a data LUN.
Updating the Local LUN Lists The lists of available local LUNs are automatically created when a Central Subsystem is declared and/or added. You can update the lists of available local LUNs at any time to reflect configuration changes. To update the local LUN lists: 1. Click Configuration Tasks → Domains → LUNs in the PAM tree to open the Logical Units page. 2. Click Update. When requested, click OK to confirm. The new LUN lists are displayed in the Logical Units page.
Managing Logical Units (Servers Connected to a SAN) Important: Certain features described below are only available if you are connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. What You Can Do • Update SAN LUN Lists • Declare Local LUNs • Delete Local LUNs • Edit LUNs • Rename LUNs • Clear, Load, Save NVRAM Variables Note: EFI LUNs and Data LUNs must be created from the utility delivered with the storage subsystem.
• Data LUNs, on which data can be stored, are listed at the bottom of the pane. Command Bar SAN Update Update the lists of SAN LUNs. Edit LUN Modify the LUN name, description, and change a Data LUN into an EFI LUN and vice-versa. Rename LUN Modify the LUN name. NVRAM Clear, load and save EFI Boot LUN NVRAM variables. Declare Local LUN Declare a new local LUN. Delete Local LUN Delete a non-allocated local LUN. LUN List Name LUN name. LUN Number Number allocated to the LUN.
Updating SAN LUN Lists Important: Reserved for systems connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. When new LUNs are added to / removed from your Storage Area Network, they can be automatically added to / removed from the list of available LUNs by using the PAM SAN Update command, which allows you to update the lists of available LUNs on the SAN at any time. Notes: • This command CANNOT be used to update the lists of local LUNs.
Declaring Local LUNs When you create a new LUN via the software delivered with your local storage subsystem, you must also declare this new LUN by using the PAM Declare Local LUN command. Note: This command CANNOT be used to declare new SAN LUNs. To update the list of available local LUNs: 1. Create the required LUNs from the utility delivered with the storage subsystem(s). 2. Click Configuration Tasks → Domains → LUNs in the PAM tree to open the Logical Units page. 3.
Deleting Local LUNs Notes: • A LUN CANNOT be deleted if it is allocated to a Scheme. To delete a LUN: 1. Click Configuration Tasks → Domains → LUNs in the PAM tree to open the Logical Units page. 2. Select the required LUN from the lists of available local LUNs and click Delete LUN to open the Delete LUN dialog. Figure 123. Delete LUN dialog 3. Click Yes to confirm. The LUN is removed from the list of available LUNs.
Editing LUNs Important: Reserved for systems connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. Notes: • A LUN CANNOT be edited if it is allocated to a Scheme. • The NVRAM button is NOT ACCESSIBLE if no NVRAM variables are available for the selected LUN. If required, you can modify the EFI / Data LUN names, description, NVRAM variables, and/or change a Data LUN into an EFI LUN or vice-versa. To edit a LUN: 1.
Renaming LUNs Important: Reserved for systems connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. Note: A LUN CANNOT be renamed if it is allocated to a Scheme. To rename a LUN: 1. Click Configuration Tasks → Domains → LUNs in the PAM tree to open the Logical Units page. 2. Select the LUN you want to rename from the lists of available LUNs and click Rename LUN to open the Rename LUN dialog. Figure 125. Rename LUN dialog 3.
Checking and Updating Fibre Channel HBA World Wide Names Important: Reserved for servers and connected to a Storage Area Network (SAN). Please contact your Bull Sales Representative for sales information. To control LUN access, Bull NovaScale Servers use LUN masking at Host Bus Adapter (HBA) driver level. Each Fibre Channel HBA driver contains a masking utility using the World Wide Name (WWN) to limit LUN access. As a result, users are only aware of the LUNs to which they have access.
4. Double-click the required PCI board to update the WWN. The Modify PCI HBA Worldwide Name dialog opens. Figure 127. Modify PCI HBA Worldwide Name dialog 5. Enter the WWN supplied with the HBA and click Save to apply changes.
Limiting Access to Hardware Resources You can functionally limit access to certain hardware elements. Locked elements can no longer be accessed by the current domain, but are still physically available for access by other domains. Previously locked elements can be unlocked so that they can be accessed by the domain. Notes: • The domain must be INACTIVE before configuration changes can be made. • Hardware locking / unlocking is only taken into account at the next domain power ON.
Locking / Unlocking Hardware Elements To lock / unlock a domain hardware element: 1. Open the Lock Domain Hardware Resources dialog: a. If you are configuring a domain scheme: From the Scheme Management dialog, select the required domain and click Lock Hardware. b. If you want to edit a previously defined domain scheme: . From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Schemes → Edit. . Select the required domain and click Lock Hardware Figure 128.
Figure 129. Lock domain hardware resources dialog - PCI slot selected 4. Click OK → Apply to return to the Schemes Management pane.
Creating a Mono-Domain Scheme Using All Server Resources Notes: • A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring and Managing Extended Systems, on page 5-125.
NovaScale 5165 Server Scheme Name MyBusinessScheme Description Mono-domain, Cells 0, 1, 2 & 3, Boot 0Lun0, MyBusiness-1 Central Subsystem(s) MYSERVER-01 Number of domains 1 Domain size 4 cells: Cell0, Cell1, Cell2 & Cell 3 EFI boot LUNs SAN: FDA1300 LUN1 Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 Fibre channel hosts (SAN only) Primary Link: Cell_0: Module_0/IOC_0/PCISLOT_1 Secondary Link: Cell_3: Module_1/IOC_1/PCISLOT_1 IO resource location 0IOC0 mandatory, 0IOC1, 1IOC0, & 1IOC1 option
NovaScale 5245 Server Scheme Name MyBusinessScheme Description Mono-domain, Cells 0 to 5, Boot 0Lun0, MyBusiness-1 Central Subsystem(s) MYSERVER-02 Number of domains 1 Domain size 6 cells: Cell0 to Cell5 EFI boot LUNs SAN: FDA1300 LUN1 Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 Fibre channel hosts (SAN only) Primary Link: Cell_0: Module_0/IOC_0/PCISLOT_1 Secondary Link: Cell_3: Module_1/IOC_1/PCISLOT_1 IO resource location 0IOC0 mandatory, 0IOC1, 1IOC0, 1IOC1, 2IOC0 & 2IOC1 optional Re
NovaScale 5325 Server Scheme Name MyBusinessScheme Description Mono-domain, Cells 0 to 7, Boot 0Lun0, MyBusiness-1 Central Subsystem(s) MYSERVER-03 Number of domains 1 Domain size 8 cells: Cell0 to Cell 7 EFI boot LUNs SAN: FDA1300 LUN1 Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 Fibre channel hosts (SAN only) Primary Link: Cell_0: Module_0/IOC_0/PCISLOT_1 Secondary Link: Cell_3: Module_1/IOC_1/PCISLOT_1 IO resource location 0IOC0 mandatory, 0IOC1, 1IOC0, 1IOC1, 2IOC0, 2IOC1, 3IOC0 & 3IO
To create a mono-domain scheme using all server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2. From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Schemes to open the Schemes Management pane. 3. Click New to open the Scheme Creation dialog. 4. Complete the Scheme and Description fields.
5. Click Central Subsystem -> Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens.
NovaScale 5245 Partitioned Server NovaScale 5325 Partitioned Server Figure 131. Central Subsystem configuration dialog - example 1 6. In the Central Subsystem list, select the required Central Subsystem. The graphic representation of the selected Central Subsystem appears in the bottom right part of the window.
7. To create a mono-domain scheme, in the Number of Partitions dropdown list select 1 hardware partition. 8. To configure the partition in order to use all server resources, in the Central Subsystem graphic representation select all the cells. 9. Click OK to return to the Scheme Management dialog. The Status icon is red because a Domain Identity and an EFI LUN are required to complete domain configuration.
NovaScale 5245 Partitioned Server NovaScale 5325 Partitioned Server Figure 132. Scheme Management dialog - example 1 10.In the partition list, double-click the empty cell of the P1 line and the Domain Identities column. The Identity List dialog opens.
Figure 133. Identity list dialog - example 1 11.If the required identity is in the list, go to Step 16. If you want to create a new identity for this domain, click New to open the Create New Identity dialog. See Creating a Domain Identity, on page 5-50 for details. Figure 134. Create new identity dialog - example 1 12.Complete the Name, Description, Domain Settings and Management Parameters fields as required. 13.Click Advanced Settings to open the Advanced Identity Settings dialog.
Figure 135. Create new identity advanced setting dialog - example 1 14.Complete the Advanced Identity Settings dialog fields as required and click OK to return to the Create new identity dialog. 15.Click OK. The new identity appears in the Identities List dialog. 16.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog. The selected identity is now displayed in the Domain Identities field. 17.Double-click the EFI LUNs field.
20.Select the required Data LUNs from the list of available LUNs and click Add to move the selected Data LUNs to the Data LUNs selected list. Figure 137. Select Data LUN dialog - example 1 21.Click OK to return to the Scheme Management dialog. Data LUN set is now displayed in the Data LUNs field. is displayed. You must now link the The Status icon remains red and the No Link icon selected EFI and Data LUNs to the Fibre Channel Host you want to use to access these LUNs.
22.Click Domains -> Link to open the Link LUNs to HBA dialog. Figure 138. Link LUN to HBA dialog - example 1 23.Select the first LUN in the list and select the Redundant mode. You are informed that dedicated software is required to enable this mode and you are requested to confirm your choice. Click OK to confirm. 24.Click Set Primary Link to define the main access path to the SAN. The Select HBA dialog opens, allowing you to select the domain PCI slot you want to use to access the LUN. Figure 139.
28.Repeat Steps 23 to 27 for each LUN in the list and click OK → Apply to return to the Scheme Management dialog. The Status icon turns green and the Linked icon appears. 29.Click Save. The domain configuration scheme is now available for domain management.
Creating a Mono-Domain Scheme Using a Selection of Server Resources Notes: • A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring and Managing Extended Systems, on page 5-125.
NovaScale 5165 Partitioned Server Scheme Name MyOffpeakProdScheme Description Mono-domain, Cell 1, Boot 0Lun1, MyOffpeakProd Central Subsystem(s) MYSERVER-01 Number of domains 1 Domain size 1 cell: Cell 1 EFI boot LUNs SAN: FDA1300 LUN1 Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 Fibre channel hosts (SAN only) Primary Link: Cell_1: Module_0/IOC_1/PCISLOT_1 IO resource location 0IOC1 Resource access All resources unlocked Domain Identity Name MyOffpeakProd Description Time zone: Par
NovaScale 5245 Partitioned Server Scheme Name MyOffpeakProdScheme Description Mono-domain, Cell 1, Boot 0Lun1, MyOffpeakProd Central Subsystem(s) MYSERVER-02 Number of domains 1 Domain size 1 cell: Cell 1 EFI boot LUNs SAN: FDA1300 LUN1 Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 Fibre channel hosts (SAN only) Primary Link: Cell_1: Module_0/IOC_1/PCISLOT_1 IO resource location 0IOC1 Resource access All resources unlocked Domain Identity Name MyOffpeakProd Description Time zone: Par
NovaScale 5325 Partitioned Server Scheme Name MyOffpeakProdScheme Description Mono-domain, Cell 1, Boot 0Lun1, MyOffpeakProd Central Subsystem(s) MYSERVER-03 Number of domains 1 Domain size 1 cell: Cell 1 EFI boot LUNs SAN: FDA1300 LUN1 Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 Fibre channel hosts (SAN only) Primary Link: Cell_1: Module_0/IOC_1/PCISLOT_1 IO resource location 0IOC1 Resource access All resources unlocked Domain Identity Name MyOffpeakProd Description Time zone: Par
To create a mono-domain scheme using a part of server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2. From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Schemes to open the Schemes Management pane. 3. Click New to open the Scheme Creation dialog. 4.
5. Click Central Subsystem -> Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens.
NovaScale 5245 Partitioned Server NovaScale 5325 Partitioned Server Figure 141. Central Subsystem configuration dialog - example 2 6. In the Central Subsystem list, select the required Central Subsystem. The graphic representation of the selected Central Subsystem appears in the bottom right part of the window.
7. To create a mono-domain scheme, in the Number of Partitions dropdown list select 1 hardware partition. 8. To configure the partition in order to use a particular cell, in the Central Subsystem graphic representation select the required cell. 9. Click OK to return to the Scheme Management dialog. The Status icon is red because a Domain Identity and an EFI LUN are required to complete domain configuration.
NovaScale 5245 Partitioned Server NovaScale 5325 Partitioned Server Figure 142. Scheme Management dialog - example 2 10.In the partition list, double-click the empty cell of the P1 line and the Domain Identities column. The Identity List dialog opens.
Figure 143. Identity list dialog - example 2 11.If the required identity is in the list, go to Step 16. If you want to create a new identity for this domain, click New to open the Create New Identity dialog. See Creating a Domain Identity, on page 5-50 for details. Figure 144. Create new identity advanced setting dialog - example 2 12.Complete the Name, Description, Domain Settings and Management Parameters fields as required. 13.Click Advanced Settings to open the Advanced Identity Settings dialog.
Figure 145. Create new identity advanced setting dialog - example 2 14.Complete the Advanced Identity Settings dialog fields as required and click OK to return to the Create new identity dialog. 15.Click OK. The new identity appears in the Identities List dialog. 16.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog. The selected identity is now displayed in the Domain Identities field. 17.Double-click the EFI LUNs field.
20.Select the required Data LUNs from the list of available LUNs and click Add to move the selected Data LUNs to the Data LUNs selected list. Figure 147. Select Data LUN dialog - example 2 21.Click OK to return to the Scheme Management dialog. Data LUN set is now displayed in the Data LUNs field. is displayed. You must now link the The Status icon remains red and the No Link icon selected EFI and Data LUNs to the Fibre Channel Host you want to use to access these LUNs.
22.Click Domains -> Link to open the Link LUNs to HBA dialog. Figure 148. Link LUN to HBA dialog - example 2 23.Select the first LUN in the list and click Set Primary Link to define the main access path to the SAN. The Select HBA dialog opens, allowing you to select the domain PCI slot you want to use to access the LUN. Figure 149. Select HBA dialog - example 2 24.Select the required PCI slot and click OK. The primary link is now set. 25.
Creating a Multi-Domain Scheme Using All Server Resources Notes: • A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring and Managing Extended Systems, on page 5-125.
NovaScale 5085 Partitioned Server Name Scheme MyProd_PayrollScheme Description Multi-domain, Cells 0 & 1, MyProduction & MyPayroll Central Subsystem(s) MYSERVER-00 Number of domains 2 Domain size 1 cell per domain: Cell 0 for MyProduction (Domain 1) Cell 1 for MyPayroll (Domain 2) EFI boot LUNs SAN: FDA 1300 LUN1 for MyProduction Local: 0Lun1 for MyPayroll Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyProduction SAN: FDA 1300 LUN4 for MyPayroll Fibre channel hosts (SAN only) MyProducti
NovaScale 5165 Partitioned Server Scheme MyProd_PayrollScheme Name Description Multi-domain, Cells 0, 1, 2 & 3, MyProduction & MyPayroll Central Subsystem(s) MYSERVER-01 Number of domains 2 EFI boot LUNs SAN: FDA 1300 LUN1 for MyProduction Local: 0Lun3 for MyPayroll Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyProduction SAN: FDA 1300 LUN4 for MyPayroll Fibre channel hosts (SAN only) MyProduction: Primary Link: Cell_0: Module_0/IOC_0/PCISLOT_1 MyPayroll: Primary Link: Cell_3: Module_1/IO
NovaScale 5245 Partitioned Server Name Scheme MyProd_PayrollScheme Description Multi-domain, Cells 0 to 5, MyProduction & MyPayroll Central Subsystem(s) MYSERVER-02 Number of domains 2 EFI boot LUNs SAN: FDA 1300 LUN1 for MyProduction Local: 0Lun3 for MyPayroll Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyProduction SAN: FDA 1300 LUN4 for MyPayroll Fibre channel hosts (SAN only) MyProduction: Primary Link: Cell_0: Module_0/IOC_0/PCISLOT_1 MyPayroll: Primary Link: Cell_3: Module_1/IOC_1
NovaScale 5325 Partitioned Server Name Scheme MyProd_PayrollScheme Description Multi-domain, Cells 0 to 7, MyProduction & MyPayroll Central Subsystem(s) MYSERVER-03 Number of domains 2 EFI boot LUNs SAN: FDA 1300 LUN1 for MyProduction Local: 0Lun3 for MyPayroll Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyProduction SAN: FDA 1300 LUN4 for MyPayroll Fibre channel hosts (SAN only) MyProduction: Primary Link: Cell_0: Module_0/IOC_0/PCISLOT_1 MyPayroll: Primary Link: Cell_3: Module_1/IOC_1
To create a multi-domain scheme using all server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2. From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Schemes to open the Schemes Management pane. 3. Click New to open the Scheme Creation dialog. 4. Complete the Scheme and Description fields.
5. Click Central Subsystem -> Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens.
NovaScale 5245 Partitioned Server NovaScale 5325 Partitioned Server Figure 151. Central Subsystem configuration dialog - example 3 6. In the Central Subsystem list, select the required Central Subsystem. The graphic representation of the selected Central Subsystem appears in the bottom right part of the window.
7. To create a 2 domains scheme, in the Number of Partitions dropdown list select 2 hardware partitions. 8. Configure the 2 partitions by proceeding as follows: a. Select Partition 1 and select the cells required for domain 1 b. Select Partition 2 and select the cells required for domain 2 9. Click OK to return to the Scheme Management dialog. The Status icons are red because Domain Identities and EFI LUNs are required to complete domain configuration.
NovaScale 5165 Partitioned Server NovaScale 5245 Partitioned Server Tips and Features for Administrators 5-105
NovaScale 5325 Partitioned Server Figure 152. Scheme Management dialog - example 3 10.In the partition list, double-click the empty cell of the P1 line and the Domain Identities column. The Identity List dialog opens. Figure 153. Identities list dialog - example 3 11.If the required identity is in the list, go to Step 16. To create a new identity for this domain, click New to open the Create New Identity dialog. See Creating a Domain Identity, on page 5-50 for details.
Figure 154. Create new identity dialog - example 3 12.Complete the Name, Description, Domain Settings and Management Parameters fields as required. 13.Click Advanced Settings to open the Advanced Identity Settings dialog. Figure 155. Create new identity advanced setting dialog - example 3 14.Complete the Advanced Identity Settings dialog fields as required and click OK to return to the Create new identity dialog. 15.Click OK. The new identity appears in the Identities List dialog.
16.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog. The selected identity is now displayed in the Domain Identities field. 17.Repeat Steps 10 to 16 for the empty cell of the P2 line and the Domain Identities column. 18.Double-click the D1 EFI LUNs field. The Select EFI LUN dialog opens, allowing you to choose the required EFI Boot LUN from the list of available LUNs. Figure 156. Select SAN EFI LUN dialog - example 3 19.
22.Select the required Data LUNs from the list of available LUNs and click Add to move the selected Data LUNs to the Data LUNs selected list. Figure 158. Select Data LUN dialog - example 2 23.Click OK to return to the Scheme Management dialog. Data LUN set is now displayed in the Data LUNs field. is displayed. You must now link the The Status icon remains red and the No Link icon selected EFI and Data LUNs to the Fibre Channel Host you want to use to access these LUNs. 24.
25.Double-click the D1 No Link icon to open the Link LUNs to HBA dialog. Figure 159. Link LUN to HBA dialog - example 3 26.Select the first LUN in the list and click Set Primary Link to define the main access path to the SAN. The Select HBA dialog opens, allowing you to select the domain PCI slot you want to use to access the LUN. Figure 160. Select HBA dialog - example 3 27.Select the required PCI slot and click OK. The primary link is now set. 28.
Creating a Multi-Domain Scheme Using a Selection of Server Resources Notes: • A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring and Managing Extended Systems, on page 5-125.
NovaScale 5165 Partitioned Server Name Scheme MyTest_DevptScheme Description Multi-domain, Cells 1, 2 & 3, MyTest & MyDevpt Central Subsystem(s) MYSERVER-01 Number of domains 2 Domain size Cell 1 for MyTest (Domain 1) Cells 2 & 3 for MyDevpt (Domain 2) EFI boot LUNs SAN: FDA 1300 LUN1 for MyTest Local: 0Lun3 for MyDevpt Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyTest SAN: FDA 1300 LUN4 for MyDevpt Fibre channel hosts (SAN only) MyTest: Primary Link: Cell_1: Module_0/IOC_0/PCISLOT_1
NovaScale 5245 Partitioned Server Name Scheme MyTest_DevptScheme Description Multi-domain, Cells 0, 1, 2 & 4, MyTest & MyDevpt Central Subsystem(s) MYSERVER-02 Number of domains 2 Domain size Cells 0, 1 & 2 for MyTest (Domain 1) Cell 4 for MyDevpt (Domain 2) EFI boot LUNs SAN: FDA 1300 LUN1 for MyTest Local: 0Lun3 for MyDevpt Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyTest SAN: FDA 1300 LUN4 for MyDevpt Fibre channel hosts (SAN only) MyTest: Primary Link: Cell_1: Module_0/IOC_1/PCIS
NovaScale 5325 Partitioned Server Name Scheme MyTest_DevptScheme Description Multi-domain, Cells 0 to 6, MyTest & MyDevpt Central Subsystem(s) MYSERVER-03 Number of domains 2 Domain size Cells 0, 1, 2 & 3 for MyTest (Domain 1) Cells 4, 5 & 6 for MyDevpt (Domain 2) EFI boot LUNs SAN: FDA 1300 LUN1 for MyTest Local: 0Lun3 for MyDevpt Data LUNs (SAN only) SAN: FDA 1300 LUN10, LUN6 for MyTest SAN: FDA 1300 LUN4 for MyDevpt Fibre channel hosts (SAN only) MyTest: Primary Link: Cell_1: Module_0/IOC_
To create a multi-domain scheme using a part of server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2. From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Schemes to open the Schemes Management pane. 3. Click New to open the Scheme Creation dialog. 4.
5. Click Central Subsystem -> Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens.
NovaScale 5325 Partitioned Server Figure 162. Central Subsystem configuration dialog - example 4 6. In the Central Subsystem list, select the required Central Subsystem. The graphic representation of the selected Central Subsystem appears in the bottom right part of the window. 7. To create a 2 domains scheme, in the Number of Partitions dropdown list select 2 hardware partitions. 8. Configure the 2 partitions by proceeding as follows: a. Select Partition 1 and select the cells required for domain 1 b.
NovaScale 5165 Partitioned Server NovaScale 5245 Partitioned Server 5-118 User's Guide
NovaScale 5325 Partitioned Server Figure 163.
10.Double-click the empty D1 Identities field. The Identities List dialog opens. The Identity List dialog opens. Figure 164. Identities list dialog - example 4 11.If the required identity is in the list, go to Step 16. If you want to create a new identity for this domain, click New to open the Create New Identity dialog. See Creating a Domain Identity, on page 5-50 for details. Figure 165. Create new identity dialog - example4 12.
Figure 166. Create new identity advanced setting dialog - example 4 14.Complete the Advanced Identity Settings dialog fields as required and click OK to return to the Create new identity dialog. 15.Click OK. The new identity appears in the Identities List dialog. 16.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog. The selected identity is now displayed in the Domain Identities field. 17.
20.Double-click the D2 EFI LUNs field. The Select EFI LUN dialog opens, allowing you to choose the required EFI Boot LUN from the list of available LUNs. As the selected EFI LUN is a Local LUN, the Status icon turns green. 21.Double-click the D1 Data LUNs field. The Select Data LUN dialog opens, allowing you to choose the required Data LUNs from the list of available LUNs. 22.
25.Double-click the D1 No Link icon to open the Link LUNs to HBA dialog. Figure 169. Link LUN to HBA dialog - example 2 26.Select the first LUN in the list and click Set Primary Link to define the main access path to the SAN. The Select HBA dialog opens, allowing you to select the domain PCI slot you want to use to access the LUN. Figure 170. Select HBA dialog - example 4 27.Select the required PCI slot and click OK. The primary link is now set. 28.
30.Select D2 and click Lock Hardware to open the Lock Domain Hardware Resources dialog. Figure 171. Lock domain hardware resources - example 4 31.Select the resources you want to lock and click OK to return to the Scheme Management dialog. See Limiting Access to Hardware Resources, on page 5-66 for details. 32.Click Save. The domain configuration scheme is now available for domain management. Note: Cell 0 is free and available for use by another scheme, if required.
Configuring and Managing Extended Systems A single PAP unit can administer, monitor, and manage several Central Subsystems. The PAM Domain Configuration Scheme Wizard allows easy configuration of extended systems. Please contact your BULL Customer Sales Representative for details.
Scheme, Domain Identity, and Resources Checklists Scheme Checklist Name What name do I want to use for my Scheme? Description How can I describe my Scheme to reflect its scope? Central Subsystem(s) Which Central Subsystem(s) do I want to use? Number of Domains How many domains do I need? Domain Size How many cells do I want to assign to each domain? EFI Boot LUNs Which EFI boot LUN do I want to use for each domain? Data LUNs * Which data LUNs do I want to assign to each domain? Fibre Channel H
Domain Identity Checklist Name What name do I want to use for my Domain Identity to reflect the tasks/jobs it will run? Description How can I describe my Domain Identity to reflect its use? Operating System Which OS do I want to run on this domain? Will this OS support assigned hardware (CPUs, DIMMs)? Domain Network Name Which network name will be used to identify this domain? Domain IP Address Which IP address will be used to reach this domain? Domain URL Which URL can be used to reach my domain
Resources Checklist Central Subsystem: Cell 0 Cell 1 QBBs QBB0 QBBs QBB1 IO Box IOC0 IO Box IOC1 EFI Boot Lun 0Lu0 EFI Boot Lun 0Lu1 OS instance OS instance I/O Resources IOC0_Slot 1 IOC1_Slot 1 IOC0_Slot 2 IOC1_Slot 2 IOC0_Slot 3 IOC1_Slot 3 IOC0_Slot 4 IOC1_Slot 4 IOC0_Slot 5 IOC1_Slot 5 IOC0_Slot 6 IOC1_Slot 6 Table 55.
Resources Checklist Cell 2 Cell 3 QBBs QBB0 QBBs QBB1 IO Box IOC0 IO Box IOC1 EFI Boot Lun 1Lu0 EFI Boot Lun 1Lu1 OS instance OS instance I/O Resources IOC0_Slot 1 XXXXXXXXXXXXXXXXXX I/O Resources IOC1_Slot 1 IOC0_Slot 2 IOC1_Slot 2 IOC0_Slot 3 IOC1_Slot 3 IOC0_Slot 4 IOC1_Slot 4 IOC0_Slot 5 IOC1_Slot 5 IOC0_Slot 6 IOC1_Slot 6 Table 56.
Resources Checklist Cell 4 Cell 5 QBBs QBB0 QBBs QBB1 IO Box IOC0 IO Box IOC1 EFI Boot Lun 1Lu0 EFI Boot Lun 1Lu1 OS instance OS instance I/O Resources IOC0_Slot 1 IOC1_Slot 1 IOC0_Slot 2 IOC1_Slot 2 IOC0_Slot 3 IOC1_Slot 3 IOC0_Slot 4 IOC1_Slot 4 IOC0_Slot 5 IOC1_Slot 5 IOC0_Slot 6 IOC1_Slot 6 Table 57.
Resources Checklist Cell 6 Cell 7 QBBs QBB0 QBBs QBB1 IO Box IOC0 IO Box IOC1 EFI Boot Lun 1Lu0 EFI Boot Lun 1Lu1 OS instance OS instance I/O Resources IOC0_Slot 1 XXXXXXXXXXXXXXXXXX I/O Resources IOC1_Slot 1 IOC0_Slot 2 IOC1_Slot 2 IOC0_Slot 3 IOC1_Slot 3 IOC0_Slot 4 IOC1_Slot 4 IOC0_Slot 5 IOC1_Slot 5 IOC0_Slot 6 IOC1_Slot 6 Table 58.
Section V - Creating Event Subscriptions and User Histories This section explains how to: • Customize the PAM Event Messaging System, on page 5-133 • Set up Event Subscriptions, on page 5-134 • Create, Edit, Delete an E-mail Server, on page 5-136 • Create, Edit, Delete an E-mail Account, on page 5-138 • Create, Edit, Delete a User History, on page 5-156 • Enable / Disable Event Channels, on page 5-140 • Create, Edit, Delete an Event Subscription, on page 5-141 • Understand Event Message Filtering Criteria,
Customizing the PAM Event Messaging System During operation, all Central Subsystem activity messages are automatically logged in predefined System Histories that can be viewed and archived by members of the Customer Administrator group. In addition, PAM software reports and logs environmental, command, and hardware errors. A comprehensive set of Event Message subscriptions allows connected and non-connected users to be notified of system status and activity.
Setting up Event Subscriptions Before creating an event subscription, you should establish: • the set of messages you want a user or a group of users to receive (Filter), • how you want the user or group of users to receive messages (Channel). Selecting a Filter The comprehensive event message filtering system allows you to use a predefined filter or to create a specific filter, according to your needs. See Preselecting an Event Filter, on page 5-153 and Creating an Event Filter, on page 5-154.
Event Subscription Flowcharts Once you have established who the targeted recipients are and which channel you want to use, you can use the following flowcharts as a quick guide to event subscription procedures. E-mail Event Subscription Allows a specific user to receive system notifications/alerts via e-mail. Preselect an Event filter, on page 5-153, or Create an Event Filter, on page 5-154. Select or Create an E-mail Server, on page 5-136. Select or Create an E-mail Account, on page 5-138.
Creating, Editing, Deleting an E-mail Server To send messages via the e-mail channel, you must first create an e-mail server. Several e-mail accounts can then be attached to the same e-mail server, see Creating an E-mail Account, on page 5-138. Creating an E-mail Server Important: Before creating an E-mail server, you must first complete the Site engineer email account field on the Customer Information page. This account will be displayed in the Sender email field, as shown in the following screen shot.
Editing E-mail Server Attributes To modify an e-mail server URL / description: 1. Click Configuration Tasks → Events → E-mail servers in the PAM tree. The e-mail server configuration page opens. See Figure 173 above. 2. Select the required server from the e-mail servers list. 3. Click Edit in the toolbar to modify the server URL / description. 4. Enter a new address in the URL field and/or a new description in the Description field, as applicable. 5. Click OK to confirm the modification.
Creating, Editing, Deleting an E-mail Account To send messages via the e-mail channel, you must first create an e-mail server and then attach an e-mail address to this e-mail server. Several e-mail accounts can be attached to the same e-mail server. Creating an E-mail Account To create an e-mail account: 1. Click Configuration Tasks → Events → E-mail accounts in the PAM tree. The e-mail accounts configuration page opens. Figure 174. E-mail accounts configuration page 2. Click New in the toolbar. 3.
Editing E-mail Account Attributes To modify an e-mail account name, address, server and/or description: 1. Click Configuration Tasks → Events → E-mail accounts in the PAM tree. The e-mail accounts configuration page opens. See Figure 174 above. 2. Select the required account from the e-mail accounts list. 3. Click Edit in the toolbar to modify the account name, address, server and/or description. 4. Enter the new attributes in the corresponding fields, as applicable.
Enabling / Disabling Event Channels An event channel must be selected and enabled for all event subscriptions. The following table provides the Customer Administrator with guidelines for selecting an event channel. Channel Target Enabled Specific recipient. Allows a specific recipient to directly receive specific messages. All user groups. Allows all users to access specific messages. SNMP SNMP application. Forwards specific messages as SNMP traps to the selected SNMP application for processing.
Creating, Editing, Deleting an Event Subscription Once event subscription prerequisites have been set up, you can create the event subscriptions required to send messages to their destinations. See Event Subscription Flowcharts, on page 5-135. Creating an Event Subscription To create an event subscription: 1. Click Configuration Tasks → Events → Subscriptions in the PAM tree. The event subscription configuration page opens. 2. Click New in the toolbar. Figure 176. New Event Subscription dialog box 3.
6. Select a pre-configured E-mail Account, User History, or User Group from the drop-down menu or enter an SNMP Manager IP address or server name. 7. Select a pre-configured filter from the Filter drop-down menu. 8. Click OK to confirm the creation of the new event subscription. 9. The event subscription configuration page is automatically updated with the new subscription. 10.Click Test Subscription to check that the event subscription has been configured correctly.
Understanding Event Message Filtering Criteria The set of predefined filters supplied with PAM software covers everyday event messaging requirements. However, a comprehensive filtering system allows you to finely tune event messaging criteria, if required. Before creating a new event filter, you should get to know filtering criteria options. 1. Click Configuration Tasks → Events → Filters in the PAM tree. The filter configuration page opens with the list of existing event message filters. 2.
3. Click Advanced to display the Advanced Filter page. Figure 178. Event message advanced filtering criteria chart 4. Carefully analyze Tables 61 and 62 to understand the various options.
Standard Event Message Filtering Criteria Criteria Select Description All the checkboxes in this column are selected by default. When an event message S checkbox is deselected, the event message is removed from the filter. Actions - Select the S checkbox if you want to include the event message in the new filter. - Message/Identifier Deselect the S checkbox if you do not want to include the event message in the new filter.
Criteria Duration Description This column is only applicable to messages sent to the PAM Web interface and is interactive with the Ack column (see above). When the specified duration expires, the event message is deleted automatically. Note: The PAM Web interface stores up to 150 event messages maximum per user group (100 by default). Once this limit has been reached, messages may be deleted in order of arrival, even if the set duration has not expired.
Criteria Severity Level Description This column is used to set message severity level(s): Information, Success, Warning, and Error. At least one severity level must be selected to define the filter. Actions - Double click the Severity cell to open the dialog box. Table 61. - All severity levels are selected by default. Deselect the required checkbox to remove a severity level from the filter.
Advanced Event Message Filtering Criteria Note: Advanced filtering criteria are reserved for advanced users and are to be used with care. Criteria Thresholding Description Thresholding is defined on a Count / Period basis aimed at routing significant messages only. Identical messages are counted and when the number of messages indicated in the Threshold Count field is reached within the period of time indicated in the Threshold Period field, this message is selected for routing.
Criteria Clipping Description Clipping is defined on a Count / Period basis aimed at routing a pre-defined number of messages only. Identical messages are counted and when the number of messages indicated in the Clipping Count field is reached within the period of time indicated in the Clipping Period field, no other messages will be selected for routing. Actions - Double click the Clipping cell to open the dialog box. - Select the Clipping Inactive radio button to deactivate clipping.
Criteria Source Description Each event message refers to a source (the component that generated the message) and a target (the component referred to in the message) (see below). This feature allows messages to be filtered according to one or more Source string(s) and is particularly useful for debugging and troubleshooting. Actions - Double click the Source cell to open the dialog box. 5-150 User's Guide - Select a source filter from the Event Sources list.
Criteria Target Description Each event message refers to a target (the component referred to in the message) and a source (the component that generated the message) (see above). This feature allows messages to be filtered according to one or more Target string(s) and is particularly useful for debugging and troubleshooting. Actions - Double click the Target cell to open the dialog box. - Select a target filter from the Event Targets list.
Criteria Keyword Description This feature allows messages to be filtered according to a Keyword contained in the messages. Any relevant word(s) contained in source / target strings can be used. Actions - Double click the Keywords cell to open the dialog box. Table 62. 5-152 - Select a keyword filter from the Event Keywords list. - If the list is empty, enter a keyword in the Keyword filter field and click Add. The new keyword filter is displayed in the Event Keywords list.
Preselecting, Creating, Editing, Deleting an Event Filter An event filter must be selected for all event subscriptions. The event messaging system is delivered with a set of predefined filters. Preselecting an Event Filter Before proceeding to set up an event subscription, you are advised to check which predefined filter is adapted to your needs: 1. Click Configuration Tasks → Events → Filters in the PAM tree. The filter configuration page opens. Figure 179. Filters configuration page 2.
Creating an Event Filter Once you have established which filtering criteria you want to apply to your new filter, you can proceed to create a new event filter: 1. Click Configuration Tasks → Events → Filters in the PAM tree. The filter configuration page opens with the list of existing event message filters. 2. Click New to display the Create a New Event Filter page. The standard event message filtering criteria table is displayed. Figure 180.
7. If required, click Advanced to access advanced filtering criteria. The advanced event message filtering criteria chart is displayed. Figure 181. New Filter configuration page - advanced event message filtering criteria table 8. When you have finished configuring your event filter, click Create. 9. Repeat steps 3 to 8 for each new event filter you want to create. 10.Click Close to save changes. The new filter appears in the Filters list. Editing Event Filter Attributes 1.
Creating, Editing, Deleting a User History There are two types of histories: System histories and User histories. System histories cannot be modified and are are only accessible to members of the Customer Administrator group. User histories can be created, edited and deleted and are accessible to members of both the Customer Administrator and Customer Operator groups.
Creating a User History Note: The Site Data Directory will be used, by default, if you do not specify a different directory when you create a user history. See Viewing PAM Version Information, on page 4-13 To create a user history: 1. Click Configuration Tasks -> User Histories in the PAM tree. The User Histories control pane opens. 2. Click New in the toolbar. The Create a New User History dialog opens. Figure 182. Create a New User History dialog 3.
5. Use the drop-down menu to select an automatic archiving policy Type: Type Automatic Archiving Policy Number of Days The system will automatically create an archive for this history after the number of days specified in the Value field. Size in KBytes The system will automatically create an archive when this history reaches the size in KBytes specified in the Value field. Note: Size in KBytes must be greater than 10.
Deleting a User History Important: Before deleting a user history, all the event subscriptions attached to that history must be attached to another history, or deleted. System histories cannot be deleted. If event subscriptions are attached to this history: • see Editing Event Subscription Attributes, on page 5-142 to attach these event subscriptions to another history, or • see Deleting an Event Subscription, on page 5-142 to delete these event subscriptions. To delete a user history: 1.
5-160 User's Guide
Appendix A.
NovaScale 5085 Server Specifications NovaScale 5085 Servers are delivered rack-mounted in 40U or 19U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. Cabinet Dimensions / Weight Unpacked 1300H Height: Width: Depth: Weight (max): 1300L Height: Width: Depth: Weight (max.): Packed 195.5 cm (77.0 in) 60.0 cm (23.6 in) 129.5 cm (51.0 in) 340 kg (725 lb) 1300H Height: Width: Depth: Weight (max): 200.0 cm (78.7 in) 80.0 cm (31.5 in) 140.
Power Cables PDU-2-4-M-32A AC (32A) Cable type Connector type 1 per PDU 3 x AWG10 ( 3 x 6 mm2 / #10US) IEC60309-32A It is mandatory for power lines and terminal boxes to be located within the immediate vicinity of the system and to be easily accessible. Each power line must be connected to a separate, independent electrical panel and bipolar circuit breaker. PDUs require an extra cable length of 1.5 meters for connection inside the cabinet.
NovaScale 5165 Server Specifications NovaScale 5165 Servers are delivered rack-mounted in 40U or 19U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. Cabinet Dimensions / Weight Unpacked 1300H Height: Width: Depth: Weight (max): 1300L Height: Width: Depth: Weight (max.): Packed 195.5 cm (77.0 in) 60.0 cm (23.6 in) 129.5 cm (51.0 in) 450 kg (959 lb) 1300H Height: Width: Depth: Weight (max): 200.0 cm (78.7 in) 80.0 cm (31.5 in) 140.
Acoustic Power at Room Temperature +20° C (+68° F) System Running Lw(A) 6.3 Bels System Idle Lw(A) 6.1 Bels Power Cables PDU-2-4-M-32A AC (32A) Cable type Connector type 1 per PDU 3 x AWG10 (3 x 6 mm2 / #10US) IEC60309-32A It is mandatory for power lines and terminal boxes to be located within the immediate vicinity of the system and to be easily accessible. Each power line must be connected to a separate, independent electrical panel and bipolar circuit breaker. PDUs require an extra cable length of 1.
NovaScale 5245 Server Specifications NovaScale 5245 Servers are delivered rack-mounted in 40U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. Cabinet Dimensions / Weight Unpacked 1300H Height: Width: Depth: Weight (max): Packed 195.5 cm (77.0 in) 60.0 cm (23.6 in) 129.5 cm (51.0 in) 560 kg (1193 lb) 1300H Height: Width: Depth: Weight (max): 200.0 cm (78.7 in) 80.0 cm (31.5 in) 140.0 cm (55.
Power Cables PDU-2-4-M-32A AC (32A) Cable type Connector type 1 per PDU 3 x AWG10 (3 x 6 mm2 / #10US) IEC60309-32A It is mandatory for power lines and terminal boxes to be located within the immediate vicinity of the system and to be easily accessible. Each power line must be connected to a separate, independent electrical panel and bipolar circuit breaker. PDUs require an extra cable length of 1.5 meters for connection inside the cabinet.
NovaScale 5325 Server Specifications NovaScale 5325 Servers are delivered rack-mounted in 40U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. Cabinet Dimensions / Weight Unpacked 1300H Height: Width: Depth: Weight (max): Packed 195.5 cm (77.0 in) 60.0 cm (23.6 in) 129.5 cm (51.0 in) 670 kg (1427 lb) 1300H Height: Width: Depth: Weight (max): 200.0 cm (78.7 in) 80.0 cm (31.5 in) 140.0 cm (55.
Power Cables PDU-2-4-M-32A AC (32A) Cable type Connector type 1 per PDU 3 x AWG10 (3 x 6 mm2 / #10US) IEC60309-32A It is mandatory for power lines and terminal boxes to be located within the immediate vicinity of the system and to be easily accessible. Each power line must be connected to a separate, independent electrical panel and bipolar circuit breaker. PDUs require an extra cable length of 1.5 meters for connection inside the cabinet.
A-10 User's Guide
Glossary A AC: Alternating Current generated by the power supply. See DC. ACPI: Advanced Configuration and Power Interface. An industry specification for the efficient handling of power consumption in desktop and mobile computers. ACPI specifies how a computer's BIOS, operating system, and peripheral devices communicate with each other about power usage. Address: A label, name or number that identifies a location in a computer memory. AMI: American Megatrends Incorporated.
CMCV: Corrected Memory Check Vector. CMOS: Complementary Metal Oxide Semiconductor. A type of low-power integrated circuits. System startup parameters are stored in CMOS memory. They can be changed via the system setup utility. COM: Component Object Model. Microsoft technology for component based application development under Windows. COM +: Component Object Model +. Microsoft technology for component based application development under Windows.
ECC: Error Correcting Code. Event channel: Defines how the Event Manager sends an event message. An event channel is one of: HISTORY (the message is logged in a history file), EMAIL (the message is sent to an e-mail address), WEB (the message is stored for analysis from the PAM web user interface), SNMP (the message is sent as an SNMP trap to the selected SNMP application). EEPROM: Electrically Erasable Programmable Read-Only Memory. A type of memory device that stores password and configuration data.
FCAL: Fibre Channel Arbitrated Loop. FCA: Fibre Channel Adapter. FCBQ: Fan Control Board for QBB. FCBS: Fan Control Board for SPS. Global MCA: Machine Check Abort is visible to all processors, in a multiprocessor system and will force all of them to enter machine check abort. GUI: Graphical User Interface. GTS: Global Telecontrol Server. FDA: Fibre Disk Array. FDD: Floppy Disk Drive. Flash EPROM: Flash Erasable Programmable Read-Only Memory.
I I2C: Intra Integrated Circuit. The I2C (Inter-IC) bus is a bi-directional two-wire serial bus that provides a communication link between integrated circuits (ICs). The I2C bus supports 7-bit and 10-bit address space devices and devices that operate under different voltages. IA64: is a 64-bit Intel processor Architecture based on Explicitly Parallel Instruction Computing (EPIC). The Itanium processor is the first in the Intel line of IA-64 processors. IB: Infini Band. IC: Integrated Circuit.
LD: Logical Disk. A Storeway FDA 1x00/2x00 logical disk (or LUN) is visible to the OS as a Disk. See LUN and PD (Physical Disk). LED: Light Emitting Diode. A small electronic device that glows when current flows through it. Legacy Application: An application in which a company or organization has already invested considerable time and money. Typically, legacy applications are database management systems (DBMSs) running on mainframes or minicomputers.
Multitasking: The ability to perform several tasks simultaneously. Multitasking allows you to run multiple applications at the same time and exchange information among them. See Task. PAM Tree pane: One of the three areas of the PAM web page. Server hardware presence and functional status are displayed in the PAM Tree pane. See Status pane and Control pane. Multithreading: The ability of a processor core to execute more than one independent instruction thread simultaneously.
PMB: Platform Management Board. Links the server to the PAP unit. PNP: Plug aNd Play. The ability to plug a device into a computer and have the computer recognize that the device is there. POST: Power On Self Test. When power is turned on, POST (Power-On Self-Test) is the diagnostic testing sequence (or "starting program") that a computer runs to determine if hardware is working correctly. ROM: Read-Only Memory. A type of memory device that is used to store the system BIOS code.
SIO: Server I/O / Super I/O. SSI: Server System Infrastructure. Shell: The Shell is the layer of programming that understands and executes the commands a user enters. As the outer layer of an operating system, the Shell can be contrasted with the kernel, the inmost layer or core of services of an operating system. See EFI Shell. Status Pane: One of the three areas of the PAM web page. Provides quick access to CSS Module availability status, server functional status, and pending event message information.
UML: Unified Modeling Language. A standard notation for the modeling of real-world objects as a first step in developing an object-oriented design methodology. UPS: Uninterruptible Power Supply. A device that allows uninterrupted operation if the primary power source is lost. It also provides protection from power surges. URL: Uniform / Universal Resource Locator. The address of a file (resource) accessible on the Internet. USB: Universal Serial Bus.
Index A Access, front door, 1-20 Action Request Package default, creating, 4-51 filtering, 4-53 troubleshooting tools, creating, 4-51 Archive history, 4-38 viewing, online, 4-38 Autocall settings, checking, 4-48 Autocalls configuring, 5-20 FTP parameters, 5-20 Automatic restart, 5-52 B Back Up, PAM software, 5-26 BIOS, POST codes, 3-43 BIOS info, domain, 3-33 Boot, options, 5-7 Boot manager, EFI, 5-7 C CD-ROM drive, 1-14 Channels, enabling / disabling, 5-140 Checking environmental conditions, 4-46 events,
EFI deleting an e-mail account, 5-139 deleting an e-mail server, 5-137 editing e-mail account attributes, 5-139 editing e-mail server attributes, 5-137 boot manager, 5-7 boot manager options, 5-7 file transfer protocol, 5-15 manual network configuration, 5-14 network setup and configuration, 5-14 shell, 5-9 EFI boot, options, 5-7 EFI shell command syntax, 5-9 commands, 5-11 script, 5-11 starting, 5-9 EFI utilities, using, 5-6 Electrical safety, xviii Enterprise LAN, server domain Linux, connecting, 2-19 W
copying, 5-54 creating, 5-50 deleting, 5-54 editing, 5-54 managing, 5-50 Illegal characters, xx Incident investigating, 4-42 what to do, 4-42, 4-46 Incidents dealing with, 3-43 domain, 3-42 Include / exclude, monitoring, 4-15 Including clocks, 4-27 hardware, 4-23, 4-24 sidebands, 4-27 SPS, 4-27 XSP cables, 4-27 Indicators fault status, 4-15, 4-16 failure status, 4-15, 4-16 functional status, 4-8, 4-15 power status, 4-18 presence status, 4-6, 4-15 temperature status, 4-20 IO memory space, 5-52 IOB, 1-13 IOC
status pane, 2-6, 4-3 toolbar, 2-8 tree pane, 4-5 user information, 4-12 user interface, 2-5 writing rules, xx PAM settings, customizing, 5-22 PAM software acivating a version, 5-24 back up / restore, 5-26 deploying a release, 5-23 monitoring, 4-2 PAM tree pane, 2-7 PAM version, checking, 4-48 PAM version information, viewing, 4-13 PAP application, rebooting, 3-43, 4-48 PAP unit, 1-14 CD-ROM drive, 1-14 disks, 1-14 Ethernet ports, 1-14 FDD, 1-14 mirroring, 1-22 serial ports, 1-14 PAP users, setting up, 5-17
power cables, 1-14, 1-15, 1-16, 1-17, 1-18 processors, 1-13 QBBs, 1-13 serial ports, 1-13, 1-14 USB ports, 1-13 VGA port, 1-13 Server status, checking, 2-6 Setting up PAP users, 5-17 system users, 5-4 Severity, event message, 4-32 Snapshot, saving the current configuration, 3-11 SNMP settings, checking, 4-48 Specifications NovaScale 5085 Servers, A-2 NovaScale 5165 Server, A-4 NovaScale 5245 Server, A-6 NovaScale 5325 Server, A-8 system, A-1 Status CSS module, 2-7, 4-4 event message, 4-4 exclude / include,
X-6 User's Guide
Technical publication remarks form Title : NOVASCALE NovaScale 5xx5 User's Guide Reference: 86 A1 41EM 06 Date: September 2007 ERRORS IN PUBLICATION SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION Your comments will be promptly investigated by qualified technical personnel and action will be taken as required. If you require a written reply, please include your complete mailing address below.
Technical publications ordering form To order additional publications, please fill in a copy of this form and send it via mail to: BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE +33 (0) 2 41 73 72 66 +33 (0) 2 41 73 70 66 srv.Duplicopy@bull.
BLANK
BULL CEDOC 357 AVENUE PATTON B.P.
Utiliser les marques de découpe pour obtenir les étiquettes. Use the cut marks to get the labels.