Bull NovaScale 5000 Series User’s Guide ORDER REFERENCE 86 A1 89EF 02
Bull NovaScale 5000 Series User’s Guide Hardware January 2004 BULL CEDOC 357 AVENUE PATTON B.P.
The following copyright notice protects this book under the Copyright laws of the United States of America and other countries which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works. Copyright Bull S.A. 1992, 2004 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.
Table of Contents List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii x Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv Simultaneous Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toggling the Local / Integrated Console Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Powering Up / Down the Server Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating a PAM Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing the PAM Event Messaging System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Event Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Subscription Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an E–Mail Server . . . . . . . . . . . .
vi Appendix C. Error Messages and Recovery Information . . . . . . . . . . . . . . . . . . . BIOS POST Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIOS Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAL–A POST Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAL–B POST Codes . . . . . . . . . . . . . . .
List of Figures Figure 1. Figure 2. Figure 3. Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Figure 10. Figure 11. Figure 12. Figure 13. Figure 14. Figure 15. Figure 16. Figure 17. Figure 18. Figure 19. Figure 20. Figure 21. Figure 22. Figure 23. Figure 24. Figure 25. Figure 26. Figure 27. Figure 28. Figure 29. Figure 30. Figure 31. Figure 32. Figure 33. Figure 34. Figure 35. Figure 36. Figure 37. Figure 38. Figure 39. Figure 40. Figure 41. Figure 42. Figure 43. Figure 44. Figure 45. Figure 46.
Figure 48. Figure 49. Figure 50. Figure 51. Figure 52. Figure 53. Figure 54. Figure 55. Figure 56. Figure 57. Figure 58. Figure 59. Figure 60. Figure 61. Figure 62. Figure 63. Figure 64. Figure 65. Figure 66. Figure 67. Figure 68. Figure 69. Figure 70. Figure 71. Figure 72. Figure 73. Figure 74. Figure 75. Figure 76. Figure 77. Figure 78. Figure 79. Figure 80. Figure 81. Figure 82. Figure 83. Figure 84. Figure 85. Figure 86. Figure 87. Figure 88. Figure 89. Figure 90. Figure 91. Figure 92. Figure 93.
List of Tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Table 10. Table 11. Table 12. Table 13. Table 14. Table 15. Table 16. Table 17. Table 18. Table 19. Table 20. Table 21. Table 22. Table 23. Table 24. Table 25. Table 26. Table 27. Table 28. Table 29. Table 30. Table 31. Table 32. Table 33. Table 34. Table 35. Table 36. Table 37. Table 38. Table 39. Table 40. Table 41. Table 42. Table 43. Table 44. Table 45. Table 46. PAM Tree nodes . . . . . . . . . . . . . . .
Table 47. Table 48. Table 49. Table 50. Table 51. Table 52. Table 53. Table 54. Table 55. Table 56. Table 57. Table 58. Table 59. Table 60. Table 61. Table 62. x IA–32 POST Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIM Code checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI diagnostic POST code format . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview Intended Readers This guide is intended for use by the Administrators and Operators of Bull NovaScale 5000 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. Chapter 4. Monitoring the Server explains how to supervise server operation. Chapter 5.
Related Publications Site Preparation Guide, 86 A1 87EF explains how to prepare a Data Processing Center for Bull NovaScale Servers, in compliance with the standards in force. This guide is intended for use by all personnel and trade representatives involved in the site preparation process. Installation Guide, 86 A1 88EF explains how to set up and start Bull NovaScale 5000 Series servers for the first time. This guide is intended for use by qualified support personnel.
Regulatory Specifications and Disclaimers Declaration of the Manufacturer or Importer We hereby certify that this product is in compliance with European Union EMC Directive 89/336/EEC, using standards EN55022 (Class A) and EN55024 and Low Voltage Directive 73/23/EEC, 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 a 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.
AZERTY/QWERTY Keyboard Lookup Table Figure 1. AZERTY keyboard Figure 2.
xviii User’s Guide
Administrator’s Memorandum Domains • Power ON the a Domain, on page 3-3 • Power OFF the a Domain, on page 3-4 • Perform a Domain Force Power OFF, on page 3-5 • Perform a Manual Domain Reset, on page 3-6 • Perform a Domain Memory Dump, on page 3-7 • View Domain Functional Status, on page 3-8 • View Power Logs, on page 3-8 • View BIOS Info, on page 3-8 • View Domain Hardware Resources, on page 3-9 • Solve Incidents, on page 3-11 Monitoring • Refresh the PAM Display, on page 4-2 • View PAM Web Site User Inform
Configuration • Set up Server Users, on page 5-2 • Configure SR–0812 / SR–1422 Data Disks, on page 5-3 • Configure Storeway FDA 1300 / 2300 Data Disks, on page 5-6 • Use the EFI Boot Manager, on page 5-8 • Use the EFI Shell, on page 5-11 • Set Up and Configure the EFI Network, on page 5-16 • Set up PAP Unit Users, on page 5-18 • Modify Customer Information, on page 5-18 • Configure PAM Autocall Parameters, on page 5-21 • Customize PAM Settings, on page 5-22 • Deploy a New PAM Release, on page 5-23 • Activat
Operator’s Memorandum Domains • Power ON a Domain, on page 3-3 • Power OFF a Domain, on page 3-4 • Perform a Domain Force Power OFF, on page 3-5 • Perform a Manual Domain Reset, on page 3-6 • Perform a Domain Memory Dump, on page 3-7 • View Domain Functional Status, on page 3-8 • View Power Logs, on page 3-8 • View BIOS Info, on page 3-8 • View Domain Hardware Resources, on page 3-9 • Solve Incidents, on page 3-11 Histories • View, Manage PAM Event Messages, History Files, on page 4-20 • Understand Event Me
xxii User’s Guide
Chapter 1. Introducing Bull NovaScale 5000 Series Servers This chapter describes the main hardware components and user environment for Bull NovaScale 5000 Series Servers.
Bull NovaScale Server Overview Bull NovaScale Servers for business and scientific applications are based upon the FAME architecture (Flexible Architecture for Multiple Environments) and leverage the latest generation of Intel Itanium 2 processors. Bull NovaScale Servers are delivered rack–mounted and ready–to–use in a high cabinet. Figure 3.
The main features of Bull NovaScale Servers are: Intel Itanium Processor Family architecture: – Modularity, predictable performance and growth. Simultaneous support of multiple environments: – Microsoft Windows Server, – Linux . High performance computing capabilites: – Business Intelligence: . Datawarehousing. . Datamining. – Large enterprise applications: . ERP. . CRM. . SCM, ... – Large database applications for Internet transactions. – Large business sector applications: . Online billing. .
Getting to Know Bull NovaScale Servers Note: Abbreviations and acronyms are documented in the Glossary.
NovaScale 5160 Server The cabinet contains the following components: Front 1 CSS module with midplane, redundant power supply and AC power cable Rear 11 Console drawer with monitor, keyboard and mouse 2 DPS units 12 KVM switch 3 1 or 2 IOB (s) with: 13 1 or two SCSI or FC disk rack(s) with RAID controller(s) and disks 4 IOR 14 PAP unit with CD–ROM drive, FDD and disk(s) 5 LS240 disk drive (optional) 15 PDU with AC power cable 16 Ethernet hub with power bar (FC disk rack) 6 DVD / CD–
Server Components Central Subsystem (CSS) Module The CSS Module houses core hardware components. The CSS Module is located at the bottom of the cabinet. 1 MPI (MidPlane) This active board is used to interconnect the QBBs, IOBs and the PMB. 2 SPS fan boxes Each MPI is equipped with two redundant fan boxes for cooling.
Console Drawer The Console Drawer contains the keyboard, monitor and mouse used for local access to the server and to the Platform Administration Processor (PAP) Unit. The Console drawer is located in the center of the cabinet for easy access and comfortable use. • 1 pull–out table top • 1 monitor • 1 QWERTY keyboard and mouse kit • 1 power cable Figure 7. Console drawer features Note: The server is designed for remote access. See Configuring Remote Access to the Server, on page 2-10.
SR–0812 Disk Rack The SR–0812 SCSI Disk Rack is delivered with four system disks (two RAID#1 and two spare disks) and offers four empty slots for Customer data disks. The Disk Rack is located in the center of the cabinet, above the PAP Unit. 1 OS disks 2 Spare disks 3 Optional data disks • 8 slots • 1 RAID controller card • 4 disks (configuration: 2 in RAID#1 + 2 in pool spare) • 2 power cables (redundant power supply) Figure 9.
SJ–0812 Disk Rack Extension The SJ–0812 Extension Disk Rack offers eight empty slots for Customer data disks. The Extension Disk Rack is located in the center of the cabinet, above the Main Disk Rack. • 8 slots • 2 power cables (redundant power supply) Figure 11. SJ–0812 SCSI extension disk rack features Storeway FDA 1300 Disk Rack The Storeway FDA 1300 Disk Rack is delivered with three system disks (two RAID#1 and one spare disks) and offers 12 empty slots for Customer data disks.
Storeway FDA 2300 Disk Rack The Storeway FDA 2300 Disk Rack is delivered with three system disks (two RAID#1 and one spare disks) and offers 12 empty slots for Customer data disks. The Controller Unit and Disk Unit are located in the center of the cabinet, above the PAP Unit.
Platform Administration Processor (PAP) Unit The PAP unit is linked to the server via the Platform Management Board (PMB). It hosts platform administration software. The PAP unit is located in the center of the cabinet, above the Console Drawer.
Power Distribution Unit (PDU) The PDU supplies mains power to the PAP unit, the Disk Rack, the KVM Switch, and the Monitor. When the server is equipped with a Storeway FDA 1300 / 2300 disk rack, the PDU also supplies mains power to the Hub Power Bar. The PDU is located in the top left part of the cabinet. Front Rear • 6 (8A) sockets (front): – PAP Unit – Disk Rack(s) • 2 (1A) sockets (rear): – Monitor – KVM Switch • 1 (20A) power cable Figure 17.
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 18. Opening the front door 1. Unlock the front door with the key. 2. Pull out the locking mechanism and turn to open. 3.
Setting up the Console Drawer Figure 19. Lowering the console drawer flap 1. Pull out the console drawer and lower the magnetic front flap. Figure 20. Extending the mouse tray 2. Pull on the tab to extend the mouse tray. Figure 21. Positioning the monitor 3. Manually position the monitor and check that the vacation switch on the right–hand side of the monitor is ON.
Figure 22. Console ready for use 4. Install the mouse on the extendable tray, ready for use. Closing the Console Drawer 1. Replace the mouse on the pad inside the drawer and push on the tab to replace the mouse tray in its housing. 2. Raise the magnetic front flap. 3. Manually lower the monitor. 4. Press firmly on the tabs on each side of the drawer and push the drawer back into the cabinet. (1) Tab (1 on each side of the drawer) Figure 23.
Accessing the PAP Unit CD–Rom and Diskette Drives Tools Required: • PAP unit key The PAP unit CD–Rom and diskette drives are located behind the front bezel. To access the CD–Rom and/or diskette drives, unlock the front bezel with the PAP unit key and remove. Figure 24.
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 CD The Bull NovaScale Server System Resource CD contains all the firmware and documentation referred to in this guide.
The PAM Web–based administration and maintenance tools give you immediate insight into system status and configuration. You will use PAM software to operate, monitor, and configure your Bull NovaScale Server. As soon as your system is connected to the power supply, the PAP unit running Microsoft Windows 2000 Server and PAM software also powers up. For further information about connecting to PAM, see Connecting to the PAM Web Site, on page 2-2.
Chapter 2. Getting Started This chapter describes how to connect to and use the Bull NovaScale 5000 Series server.
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 2000 Server.
Remote Connection 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. You can connect to PAM from any remote computer running under Microsoft Windows using Microsoft Internet Explorer 6: 1. From the remote computer, configure Microsoft Internet Explorer 6 to connect directly to the PAM Web site: a.
PAM User Interface The PAM user interface is divided into three areas: a Status pane, a PAM Tree pane, and a Control pane.
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 Meaning 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 28. PAM Tree toolbar Note: The PAM Tree pane is refreshed at your request.
Simultaneous Connection 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. 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. Figure 29.
Setting up Users As Customer Administrator, you must set up user accounts and passwords to control access to the PAP unit. See Setting up PAP Unit Users, on page 5-18.
Powering Up / Down the Server Domain The Bull NovaScale 5000 Series server is designed to operate as a single SMP system and is 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. Powering Up the Domain 1. From the PAM Tree, click Domain Manager to open the Control pane.
Powering Down the Domain 1. Shut down the server domain from the Operating System. 2. Toggle the local / integrated console from the server display to the PAP unit display. See Toggling the Local / Integrated Console Display, on page 2-6. Note: For further details about the Power OFF sequence, see Powering OFF the Domain, on page 3-4. Note: If required, the server domain can also be powered OFF from the PAM Domain Manager.
Connecting to the Server via the Local / Integrated Console CAUTION: Access to the local / integrated console should be restricted to Customer / Service Administrators and Operators ONLY to avoid inadvertent damage to software and/or hardware components. The KVM Switch allows the integrated keyboard, monitor and mouse to be used as the local server / PAP unit console. To toggle from the local PAP unit display to the local server display: 1. Press the Control key twice to display the KVM Switch Comand Menu.
Connecting to the Server via the Enterprise LAN Microsoft Windows Preparing the Server for Remote Access via the Enterprise LAN 1. Toggle the integrated console to the corresponding Windows domain port. See Toggling the Local / Integrated Console Display, on page 2-6. 2. From the Windows desktop, right click My Computer and select Properties → Remote. 3. Check the Allow remote connection box. 4. Share the \system32\clients\tsclient directory via the Explorer.
Linux Redhat Preparing the Server for Remote Access via the Enterprise LAN 1. Toggle the integrated console to the corresponding Linux domain port. See Toggling the Local / Integrated Console Display, on page 2-6. 2. From the Linux desktop, enable remote connection via telnet, rlogin, ftp, ...: 3. From the PAP unit Microsoft Internet Explorer 6 or Linux Mozilla browser, enter the Webmin URL: http://:10000. The Login to Webmin dialog box opens. 4. Click the Networking icon.
Connecting to the Server via the Web CAUTION: Remote access is a 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 Preparing the Server for Access via the Web 1. Toggle the integrated console to the corresponding Windows domain port. See Toggling the Local / Integrated Console Display, on page 2-6. 2.
2-14 User’s Guide
Chapter 3. Managing the Server Domain This chapter explains how, as Customer Administrator and/or Customer Operator, you can manage the Bull NovaScale 5000 Series server domain.
Introducing PAM Domain Management Tools The Bull NovaScale 5000 Series server is designed to operate as a single SMP system and is delivered with one pre–configured domain englobing all the hardware and software resources managed by the Operating System. The PAM Domain Manager is at the heart of server operation. Customer Administrators and Operators have equal access rights to Domain Manager functions and the Control pane will be frequently used during normal operation.
Powering ON the Domain Once connected to the Customer’s site power supply, the server initializes to the stand–by mode and the integrated PAP unit powers up. The server is not equipped with a physical power button and is powered up from the Domain Manager Control pane of the PAM Web–based software installed on the PAP unit. Check server functional status via the PAM Status Pane. If functional status is normal and the CSS Availability bar is green, the server can be powered up.
Powering OFF the Domain The server can either be powered OFF from the Operating System or from the PAM Domain Manager Control pane, according to Operating System configuration. The PAM Power OFF command is a shutdown request posted to the Operating System. If the Operating System is configured to accept a PAM Power OFF request, it will save data, close open applications and shut down. Server hardware will power down to stand–by mode.
Performing a Domain Force Power OFF The Force Power OFF command powers down domain hardware to the standby mode, independently of the Operating System. This command should only be used if the Operating System is not running or is not configured to respond to a standard Power OFF command. In the event of a critical fault, PAM software automatically performs a Force Power OFF. CAUTION: The Force Power OFF command may result in domain data loss and file corruption.
Performing a Manual Domain Reset The Reset command is used to restart the current Operating System without powering OFF/ON the domain. CAUTION: 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. The Reset command may result in domain data loss and file corruption. The Reset command does not power down domain hardware (warm reboot). To perform a manual domain Reset from the PAM Domain Manager: 1.
Performing a Domain Memory Dump The Dump command is used when the Operating System hangs and allows technicians to diagnose software problems. CAUTION: 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). To perform a domain memory Dump from the PAM Domain Manager: 1.
Viewing Domain Functional Status Domain functional status is indicated in the PAM Tree (round, colored indicator next to the Domain Manager node) and in the Domain Manager Control pane. The Domain Functional Status indicator shows the functional status of the last action performed on the domain, e.g. if the last Power ON/OFF sequence was successful, the indicator is green. Table 9 explains possible domain functional status indications.
Viewing Domain Hardware Resources The PAM Domain Manager Resources page gives permanent access to domain resource information. Click Domain Manager → Resources to open the Domain Manager Hardware Resource dialog box, which gives the following information for each domain: • number of QBBs, • total number of CPUs, • total memory, • number of IOBs & IORs, • functional / presence / power status. Click More Info ... to open the Domain Hardware Details page. Figure 32.
Domain Hardware Details Item Icon Memory Meaning Memory available per QBB. Green Yellow Functional Status Orange Red Purple Green Presence Status Red No problem detected, operating correctly. Minor problem reported, still operational. Serious problem reported, no longer capable of operating correctly. PAM may generate an OS shutdown request. Major problem reported. PAM may automatically shut down the OS. System integrity is jeopardized. Cannot be computed (detection circuit error).
What To Do if an Incident Occurs When an incident occurs during a domain Power ON / Power OFF / Force Power OFF / Reset / Dump sequence, a message is displayed in the Domain Status panel and a trace is recorded in the Domain POWER Logs. Table 11 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 Power Logs, on page 3-8. Checking Hardware Exclusion Status If you are requested to check hardware exclusion status, see Excluding / Including Hardware Elements, on page 4-17.
Chapter 4. Monitoring the Server This chapter explains how, as Customer Administrator, you can supervise Bull NovaScale 5000 Series server operation.
Introducing 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, server console, and the PAP unit are managed by the Operating System and/or by dedicated software.
Status Pane When you log onto the PAM Web site, you are able to check system status at a glance via the Status pane which provides quick access to CSS Module availability status, server functional status, and pending event message information. Figure 33. PAM Status pane CSS Availability Status When the CSS Module is operating correctly, the CSS Availabilty Status bar is green. If the CSS Module is not responding to PAM software, the bar is red.
Event Message Status The New Event Message icon informs you that new messages have arrived and that you can click the View Event Message icon to view them (the number of unprocessed event messages is also displayed). See Consulting Event Messages, the Hardware Faults List, and History Files, on page 4-21 The Event Message Severity icon indicates the set maximum severity level of unprocessed event messages. See Understanding Event Message and History Severity Levels , on page 4-20.
Presence Status Indicators Indicator Status Explanation NORMAL This hardware element: – is physically present and accessible. MISSING This hardware element: – was present in a previous configuration but has disappeared. MISSING A sub–component of this hardware element: – was present in a previous configuration but has disappeared. NOT ACCESSIBLE This hardware element: – cannot be computed (detection circuit error).
Functional Status Indicators Indicator Status NORMAL No problem detected. This hardware element is operating correctly. WARNING Minor problem reported. This hardware element is still operational. CRITICAL Serious problem reported. This hardware element is no longer capable of operating correctly. PAM may generate an OS shutdown request. FATAL Major problem reported. PAM may automatically shut down the OS. System integrity is jeopardized.
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. Note: The icon indicates the current session. Your connection Figure 37.
Viewing Server Hardware Status When you click the CSS Name in the PAM tree (e.g. PROTO1 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.
Displaying 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 physcially present and correctly configured. See Presence Status Indicators, on page 4-5.
Failure Status Indicators: Indicator Status 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 (Midplane & PMB only) The Firmware tab gives access to firmware version data for the hardware element. Figure 42. Firmware data (example) Thermal Zones (CSS module only) Thermal Zones, accessible via the Thermal zones tab, shows the 5 thermal zones monitored by PAM software. A cooling error in a thermal zone will affect all the hardware elements in that zone. See Functional Status Indicators , on page 4-6. Figure 43.
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 Functional Status Indicators , on page 4-6. 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. Figure 44.
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. Figure 45. CSS module power status details Note: When a power–specific fault is detected, a fault message is generated and the General tab Display Faults List button gives direct access to the corresponding logs.
Temperature Tab The Temperature tab gives access to power status data for the hardware element, indicating overtemperature or temperature–specific faults. Figure 46. Indicator Temperature probe status details (example) Status Explanation 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 (QBB and SPS Fanboxes only) Fan Status, accessible via the Fans tab, indicates fan status, speed and supply voltage. See Functional Status Indicators , on page 4-6. Figure 47. Fanbox details (example) Jumper Status (IOB only) Jumper Status, accessible via the Jumpers tab, indicates the current position of jumpers corresponding to advanced BIOS settings. Reserved for Customer Service Engineers. Figure 48.
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. To search for specific hardware: 1. Click Hardware Monitor in the PAM tree to open the Hardware Search page. Figure 49. Hardware Search engine 2. Select the required search criteria from the dropdown box and click OK. 3. Once the search is complete, results are displayed in the control pane. Figure 50.
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-16. Important: Hardware elements must be excluded with care.
Including a Hardware Element Important: The inclusion of a hardware element is only effective once the domain has been powered OFF/ON. 1. Click the required hardware element in the PAM Tree to open the Hardware Status page. Exclude checkbox Figure 52. Example Hardware Status page 2. Uncheck the Exclude box and click Apply. The Include dialog box opens. 3. Click Yes to confirm inclusion of the selected hardware element. Inclusion will be taken into account at the next power ON.
Hardware Exclusion Guidelines Hardware Element Exclusion Guidelines IMPORTANT: To ensure server operation and availability, the following core hardware elements MUST NOT be excluded from the domain: • • • • IOB_0, IOB_0 HubLink_1, IOR_0, QBB FanBox_0. • IOB_0 CANNOT be excluded from the domain. The domain will not power up if IOB_0 is excluded. IOB Note: If IOB_0 is excluded, IOR_0 will be automatically excluded. • IOB_1 can be excluded, but connected peripherals will no longer be accessible.
Viewing and Managing PAM Event Messages and History Files In addition, a comprehensive set of Event Message subscriptions allows connected and non–connected users to be notified of system status and activity.
Consulting Event Messages, the Hardware Faults List, and History Files Whether you consult a Web Event Message, the Hardware Faults List, a System / User History or Archive, the resulting display and utilities are the same. Access to Help Message Figure 53. Display Events page The Help File explains the message and indicates related actions, where applicable, as shown in Table 20. Specimen Message Help File Table 20.
Viewing and Acknowledging PAM Web Event Messages To consult Web event messages: 1. From the Status pane, click the icon to open the Display Events page. See Figure 53. Display Events page, on page 4-21. 2. Click the + sign to expand the required message. 3. Click the Help on message button at the bottom of the message page for direct access to the corresponding Help File. See Table 20 Specimen message help file, on page 4-21.
Viewing, Archiving, and Deleting History Files The System / User History page allows you to view, archive and delete history files. Viewing a System / User History or Archive To view a history or archive: 1. From the PAM Tree pane, click History Manager → System / User. 2. Select the required History or Archive from the list. 3. Click View to open the System / User History or Archive page. Manually Archiving a History File In general, history files are automatically archived at regular periods.
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.
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 (users with an appropriate Event Message subscription), • an autocall to the Bull Service Center (according to your maintenance contract).
CSS Functional Status / Domain State Icon Explanation Green System functional status: NORMAL. Expected domain state: RUNNING. Yellow System functional status: WARNING. Expected domain state: RUNNING. System functional status: CRITICAL. Expected domain state: INACTIVE (auto Power OFF) / RUNNING.
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.
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. Hardware exclusion status can be viewed from the Domain Hardware Details page. See Excluding / Including Hardware Elements, on page 4-17.
Checking Environmental Conditions If you are requested to check environmental conditions, ensure that your computer room is compliant with the specifications set out in Appendix A. Server Specifications. Checking Power Status If you are requested to check hardware power status: 1. Click the corresponding hardware element to open the Hardware Status page. 2. Check the Power tab. If a power indicator is NOT green, a power–specific fault has occurred. See Power Status Indicators, on page 4-12.
4-30 User’s Guide
Chapter 5. Tips and Features for Administrators This chapter explains how, as Customer Administrator, you can configure the Bull NovaScale 5000 Series server to suit your working environment.
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 SR–0812 / SR–1422 SCSI Data Disks For optimum storage, security and performance, the server is delivered with a disk rack containing two RAID #1 Operating System disks and two pool spare disks. OS Disks (RAID #1) Spare Disks (Pool) SR–0812 SCSI disk rack Ch 2 Id 01 Ch 2 Id 02 Ch 1 Id 03 Ch 1 Id 04 SR–1422 SCSIdisk rack Ch 1 Id 08 Ch 1 Id 05 Ch 2 Id 01 Ch 2 Id 00 Table 22.
Creating a New Disk Array 1. From the Microsoft Windows 2000 Server desktop on the PAP unit, launch a HyperTerminal session with the following parameters: Parameter Value Name Disk Rack Connect using COM1 or COM2 Bits per second 115200 Data bits 8 Parity None Stop bits 1 Flow control None Emulation ANSI Table 23. HyperTerminal parameters 2. Press CTRL–R to refresh the screen and display the initial Disk Array Administrator screen. 3. Press Enter to display the System Menu. 4.
Creating a New Array Partition 1. Select Array Menu. 2. Select Data Array and press Enter. 3. Select Add a Partition. 4. Enter the size of the disk partition, e.g. 10,000 MB. 5. Enter the name of the disk partition: e.g. USER1. 6. Enter a LUN number or select the suggested LUN number (from 0 to 63). 7. Repeat this procedure for each new disk partition. The new Array and associated disk partitions are now configured for use. For further details, refer to: • SR–0812 User’s Guide, 86 A1 45EG.
Configuring Storeway FDA 1300/2300 Data Disks For optimum security and performance, the server is delivered with a disk rack containing two RAID #1 Operating System disks and one spare disk. OS Disks (RAID #1) Storeway FDA 1300 /2300 disk rack PD0 Spare Disk PDe PD1 Table 24. Storeway FDA 1300/2300 system disk configuration Note: The Storeway FDA 1300/2300 disk rack provides 12 free slots for data disks. Slots are numbered from 0 to e.
Creating a New Logical Data Disk Note: For optimum storage, performance, and reliability, you are advised to use RAID level 5 for data disk configuration. 1. From the Microsoft Windows 2000 Server desktop on the PAP unit, launch iSM Client. 2. Select the disk subsystem and click the Configuration icon. The Select Operation Mode page opens. 3. Click Setting. The Configuration [Setting Mode] page opens. 4. Click LD Bind/Unbind. The LD Individual Bind/Unbind page opens. 5.
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. Entering the EFI Boot Manager To enter the EFI Boot Manager: 1. From the PAM Tree, click Domain Manager → Power ON to power up the required domain. 2. Press the Control key twice to access the Command Menu. 3.
Boot Option Maintenance Menu The EFI Boot Maintenance Manager allows the user to add boot options, delete boot options, launch an EFI application, and set the auto boot time out value. If there are no boot options in the system (and no integrated shell), the Boot Maintenance Menu is presented. If boot options are available, then the set of available boot options is displayed, and the user can select one or choose to go to the Boot Maintenance Menu.
Boot Option Description Cold Reset Performs a platform–specific cold reset of the system. A cold reset traditionally means a full platform reset. Exit Returns control to the EFI Boot Manager main menu. Selecting this option will display the active boot devices, including a possible integrated shell (if the implementation is so constructed). Table 26.
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. Warning: The EFI shell can only manage QWERTY keyboards. If you have an AZERTY keyboard, please refer to the AZERTY/QWERTY keyboard lookup table on page xvii.
EFI Shell Command Syntax The EFI Shell implements a programming language that provides control over the execution of individual commands. When the Shell scans its input, it always treats certain characters specially: (#, >, %, *, ?, [, ^, space, and newline). When a command contains a defined alias, the Shell replaces the alias with its definition (see alias command in this chapter).
Output Redirection Output of EFI Shell commands can be redirected to files, according to the following syntax: Command Output Redirection > unicode_output_file_pathname standard output to a unicode file >a ascii_output_file_pathname standard output to an ascii file 1> unicode_output_file_pathname standard output to a unicode file 1>a ascii_output_file_pathname standard output to an ascii file 2> unicode_output_file_pathname standard error to a unicode file 2>a ascii_output_file_pathname standar
By default, both the input and output for all commands executed from a batch script are echoed to the console. Display of commands read from a batch file can be suppressed via the echo –off command (see echo). If output for a command is redirected to a file, then that output is not displayed on the console. Note that commands executed from a batch script are not saved by the Shell for DOSkey history (up–arrow command recall).
Command Batch–only Description alias attrib bcfg break cd cls comp connect cp date dblk devices devtree dh disconnect dmem dmpstore drivers drvcfg drvdiag echo edit err exit for/endfor goto guid help hexedit if/endif load loadbmp ls map memmap mkdir mm mode mount 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 No No No No No No No No No No Yes Yes No No No Yes No No No No No No No No No No No No No No No No No No No No No No No Table
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 (IOB #0). Intel PRO 1000 T and 1000 F 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.
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 2000 Server 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 Table 31.
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 and to complete Intervention Reports. As Customer Administrator, you may modify this information. To modify Customer information: 1. From the PAM Tree, click Configuration Tasks → Customer Information. The Customer Information configuration page opens. 2.
Configuring PAM Autocall Parameters Autocall parameters are configured during the initial installation procedure, via the PAM configuration setup Wizard. These parameters are used by PAM software to send event messages (autocalls) to the Bull Support Center. As Customer Administrator, you may check or uncheck the Enable Autocalls, Network id, and IP address boxes. 1. From the PAM Tree, click Configuration Tasks → Autocalls. The Autocalls configuration page opens. 2. Check / uncheck the required boxes. 3.
Customizing PAM Settings 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 page 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 60.
Deploying a New PAM Release As Customer Administrator, you can deploy a new PAM release by running the new PAM Installation package x.y.z. msi (x.y.z being the PAM version e.g. 6.1.0) file. To install a new PAM Release: 1. Power down all server domains. 2. Double click the .msi file to launch the PAM Installation InstallShield Wizard. 3.
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.
5. Check the Launch PAP Configuration utility box 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.
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, 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-49 and Creating an Event Filter, on page 5-50.
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-49, or Create an Event Filter, on page 5-50. Select or Create an E–mail Server, on page 5-29. Select or Create an E–mail Account, on page 5-31.
Creating an E–Mail Server This page allows you to declare the e–mail server you intend to use to send messages via the e–mail channel. Several e–mail accounts can then be attached to the same e–mail server, see Creating an E–mail Account, on page 5-31. To create an e–mail server: 1. Click Configuration Tasks → Events → E–mail servers in the PAM tree. The e–mail servers configuration page opens. Figure 64. E–mail servers configuration page 2. Click New in the toolbar. 3.
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 64 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 an E–mail Account This page allows you to attach an e–mail address to an e–mail server. Several e–mail accounts can be attached to the same e–mail server. 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 65. E–mail accounts configuration page 2. Click New in the toolbar. 3. Enter the new account name in the Account field and corresponding e–mail address in the URL Address field. 4.
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 65 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.
Creating a User History System histories are only accessible to members of the Customer Administrator group, whereas user histories are accessible to members of both the Customer Administrator and Customer Operator groups. 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-7 To create a user history: 5. Click Configuration Tasks → Histories in the PAM tree.
9. 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. Number of KBytes The system will automatically create an archive when this history reaches the number of KBytes specified in the Value field.
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-38 to attach these event subscriptions to another history, or • see Deleting an Event Subscription, on page 5-38 to delete these event subscriptions. To delete a user history: 1.
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 EMAIL Target Specific recipient. LOG (User History) All user groups. SNMP SNMP application. WEB (PAM Interface) Selected users. Table 34. Enabled Disabled Allows a specific recipient to directly receive specific messages.
Creating 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-28. 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 68. New Event Subscription dialog box 3.
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. Subscription parameters will be used to send a test message. Note: The OK button is accessible once all mandatory fields have been completed.
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.
Figure 70. Event message advanced filtering criteria chart 4. Carefully analyze Tables 35 and 36 to understand the various options.
Standard Event Message Filtering Criteria Criteria S (Select) Description All the boxes in this column are checked by default. When an event message S box is unchecked, the event message is removed from the filter. Actions – Check the S box if you want to include the event message in the new filter. – Uncheck the S box if you do not want to include the event message in the new filter. Message/Identifier Gives a message description and provides a clickable link to the associated help messages.
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. – All severity levels are selected by default. Uncheck the required box to remove a severity level from the filter. – Check the Apply to all messages box to apply this severity level to all the messages included in 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. – Check 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. – 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. – 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 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. 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 71. Filters configuration page 2. Check that the required filter is present.
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 72.
Figure 73. 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. Click Configuration Tasks → Events→ Filters in the PAM tree. The filter configuration page opens with the list of existing event message filters. See Figure 72 above.
5-52 User’s Guide
Appendix A. Specifications The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise NovaScale 5080/5160 Server Specifications Dimensions / Weight Unpacked Packed Height: 177.5 cm (70 in) Width: 65.0 cm (25.6 in) Depth: 113 cm (44.5 in) Height: 202 cm (79.5 in) Width: 80.0 cm (31.5 in) Depth: 127.5 cm (50.
Power Cables AC (20A) Cable type Connector type 2 per cabinet 3 x 4mm / AWG # 12 (US) C22 Appliance Coupler 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. The PDU requires an extra cable length of 1.5 meters for connection inside the cabinet.
Appendix B.
Console Data Cables Mark From To 1 HD15 video cable Monitor (blue) KVM switch (blue) 2 PS2 mini–DIN6 cable + PS2/PS2 extension cable Keyboard (mauve) KVM switch (mauve) 3 PS2 mini–DIN6 cable + PS2/PS2 extension cable Mouse (green) KVM switch (green) Figure 74.
KVM Switch Data Cables (Windows) Mark Cable Type From 1 HD15 video cable 2 PS2 mini–DIN6 cable + PS2/PS2 extension cable Keyboard (mauve) KVM (mauve) 3 PS2 mini–DIN6 cable + PS2/PS2 extension cable Mouse (green) KVM (green) 4 Combined PS2/VGA cable KVM Port A PAP VGA/PS2 10 Combined USB/VGA cable (Windows) KVM Port B IOR Video/USB Figure 75.
KVM Switch Data Cables (Linux) Mark Cable Type To 1 HD15 video cable Monitor (blue) KVM (blue) 2 PS2 mini–DIN6 cable + PS2/PS2 extension cable Keyboard (mauve) KVM (mauve) 3 PS2 mini–DIN6 cable + PS2/PS2 extension cable Mouse (green) KVM (green) 4 Combined PS2/VGA cable KVM Port A PAP VGA/PS2 10 Combined PS2/VGA cable (Linux) KVM Port C IOR Video/ PS2/USB 11 USB/PS2 converter (Linux) PS2 cable (mark 10) Figure 76.
IOR Data Cables (Windows) Mark Cable Type From To 7 RJ45/DB9 to DB9 cross cable PAP COM 2 IOR COM 2 10 Combined USB/VGA cable (Windows) KVM Port B IOR Video/USB Figure 77.
IOR Data Cables (Linux) Mark From To 7 RJ45/DB9 to DB9 cross cable PAP COM 2 IOR COM 2 10 Combined PS2/VGA cable (Linux) KVM Port C IOR Video/ PS2/USB 11 USB/PS2 converter (Linux) PS2 cable (mark 10) IOR USB Figure 78.
PAP Unit Data Cables (SR–0812 Disk Rack) Mark Cable Type From To 4 Combined PS2/VGA cable KVM Port A PAP VGA/PS2 5 RJ45 to RJ45 Ethernet cable PAP LAN Enter Enterprise LAN 6 RJ45 – RJ45 Ethernet cross cable PAP LAN Maint PMB Ethernet 7 RJ45/DB9 to DB9 cross cable PAP COM 2 IOR COM 2 8 DB9 to Jack cable PAP COM 1 S/S Disk RS232 Figure 79.
PAP Unit Data Cables (SR–1422 Disk Rack) Mark From To 4 Combined PS2/VGA cable KVM Port A PAP VGA/PS2 5 RJ45 to RJ45 Ethernet cable PAP LAN Enter Enterprise LAN 6 RJ45 – RJ45 Ethernet cross cable PAP LAN Maint PMB Ethernet 7 RJ45/DB9 to DB9 cross cable PAP COM 2 IOR COM2 8 DB9 to mini–din 6 cable PAP COM 1 S/S Disk RS232 Figure 80.
PAP Unit Data Cables (Storeway FDA 1300 Disk Rack) Mark Cable Type From To 4 Combined PS2/VGA cable KVM Port A PAP VGA/PS2 5 RJ45 – RJ45 Ethernet cable PAP LAN Enter Enterprise LAN 6 RJ45 – RJ45 Ethernet cable PAP LAN Maint Hub Ethernet port 7 7 RJ45/DB9 to DB9 cross cable PAP COM 2 IOR COM 2 8 DB9 to DB9 serial cable * PAP COM 1 S/S Disk RS232 9 RJ45 – RJ45 Ethernet cable FDA 1300 Ethernet Hub Ethernet port 6 10 RJ45 – RJ45 Ethernet cable PMB Ethernet Hub Ethernet port 8 * o
PAP Unit Data Cables (Storeway FDA 2300 Disk Rack) Mark Cable Type From 4 Combined PS2/VGA cable KVM Port A PAP VGA/PS2 5 RJ45 – RJ45 Ethernet cable PAP LAN Enter Enterprise LAN 6 RJ45 – RJ45 Ethernet cable PAP LAN Maint Hub Ethernet port 7 7 RJ45/DB9 to DB9 cross cable PAP COM 2 IOR COM 2 8 DB9 to DB9 serial cable * PAP COM 1 S/S Disk RS232 9 RJ45 – RJ45 Ethernet cable FDA 2300 Ethernet Hub Ethernet port 6 10 RJ45 – RJ45 Ethernet cable PMB Ethernet Hub Ethernet port 8 * opti
SR–0812 Disk Rack Data Cables Mark Cable Type From To 8 DB9 to Jack cable PAP COM 1 S/S Disk RS232 9 SCSI–3 68–pin VHD to VHD cable HBA SCSI S/S Disk Host a9 SCSI–3 68–pin VHD to VHD cable S/S Disk Extension S/S Disk Extension Figure 83.
SR–1422 Disk Rack Data Cables Mark Cable Type DB9 to Jack cable 9 SCSI–3 68–pin VHD to VHD cable HBA SCSI S/S Disk Host a9 SCSI–3 68–pin VHD to VHD cable S/S Disk Extension S/S Disk Extension User’s Guide PAP COM 1 To 8 Figure 84.
SR–1422 SCSI Disk Rack Dual HBA Data Cables Optionally, the SR–1422 SCSI disk rack can be equipped with two SCSI HBAs, cabled as shown below: Mark Cable Type From To 9 SCSI–3 68–pin VHD to VHD cable HBA SCSI S/S Disk Host 9 SCSI–3 68–pin VHD to VHD cable HBA SCSI S/S Disk Host Figure 85.
Storeway FDA 1300 Disk Rack Data Cables a Mark Cable Type From 6 RJ45 – RJ45 Ethernet cable S/S Disk Ethernet Hub port 6 6a RJ45 – RJ45 Ethernet cable PAP LAN Maint Ethernet Hub port 7 7 LC–LC cable S/S Disk FC Adapter 8 DB9 to DB9 serial cable * PAP COM 1 S/S Disk RS232 * optional cable used to configure the S/S disk IP address. Figure 86.
Storeway FDA 1300 Extension Disk Rack Data Cables Mark Cable Type From To 1 HSSDC–HSSDC cable S/S Disk S/S Disk Extension 2 DE diagnosis cable S/S Disk S/S Disk Extension Figure 87.
Storeway FDA 1300 Disk Rack Dual HBA Data Cables Mark From To 1 LC–LC cable S/S Disk controller 0 FC Adapter 1 2 LC–LC cable S/S Disk controller 1 FC Adapter 2 Figure 88.
Storeway FDA 2300 Disk Rack Data Cables a Mark Cable Type From To 6 RJ45 – RJ45 Ethernet cable S/S Disk Ethernet Hub port 6 6a RJ45 – RJ45 Ethernet cable PAP LAN Maint Ethernet Hub port 7 7 LC–LC cable S/S Disk FC Adapter 8 DB9 to DB9 serial cable * PAP COM 1 S/S Disk RS232 * optional cable used to configure the S/S disk IP address. Figure 89.
Storeway FDA 2300 Disk Rack Dual HBA Data Cables Mark From To 1 LC–LC cable S/S Disk controller 0 FC Adapter 1 2 LC–LC cable S/S Disk controller 1 FC Adapter 2 Figure 90.
Storeway FDA 2300 Extension Disk Rack Data Cables Mark Cable Type From To 1 HSSDC–HSSDC cable S/S Disk S/S Disk Extension 2 DE diagnosis cable S/S Disk S/S Disk Extension Figure 91.
PMB – PAP Data Cables (SCSI Storage Subsystem) Mark 6 Cable Type From RJ45 – RJ45 Ethernet cross cable Figure 92. To PAP LAN Maint PMB Ethernet PMB – PAP (SCSI Storage) data cabling diagram PMB – PAP Data Cables (FC Storage Subsystem) Mark From To 6 RJ45 – RJ45 Ethernet cable PAP LAN Maint 6 RJ45 – RJ45 Ethernet cable Ethernet Hub port 8 PMB Ethernet Figure 93.
Ethernet Hub Data Cables (Storeway FDA 1300 Disk Rack) Mark Cable Type From To 1 RJ45 – RJ45 Ethernet cable Hub Ethernet port 8 PMB Ethernet 2 RJ45 – RJ45 Ethernet cable Hub Ethernet port 7 PAP LAN Maint 3 RJ45 – RJ45 Ethernet cable Hub Ethernet port 6 FDA 1300 Figure 94.
Ethernet Hub Data Cables (Storeway FDA 2300 Disk Rack) Mark From To 1 RJ45 – RJ45 Ethernet cable Hub Ethernet port 1 PMB Ethernet 2 RJ45 – RJ45 Ethernet cable Hub Ethernet port 2 PAP LAN Maint 3 RJ45 – RJ45 Ethernet cable Hub Ethernet port 3 FDA 2300 Figure 95.
Power Cables The CSS Module is equipped with a dedicated power supply cable.
B-24 User’s Guide
Appendix C. Error Messages and Recovery Information BIOS POST codes, on page C-1 PAM message list, on page C-32 BIOS POST Codes During initialization, POST codes are generated by the BIOS for each QBB in the configuration. These POST codes may be used for troubleshooting purposes.
BIOS Error Messages Error messages are generated by the BIOS when errors are detected during initialization. Bull NovaScale Server error messages can be viewed from the Windows or Linux operating system and are organized as follows: Error Messages Boot Error Messages C-29 Storage Device Error Messages C-29 System Configuration Error Messages C-30 CMOS Error Messages C-31 Miscellaneous Error Messages C-31 Table 39.
SAL–A POST Codes Note: In this document, Post Codes are presented in chronological order. POST Codes Meaning 0x8FED Initialize base memory 0x8FEC Levelization OK 0x8FEE Enable SNC ports.
POST Codes C-4 Meaning 0x8FD9 Check if all mandatory modules are available in North Firmware 0x8FD8 Search for the SAL_A extension written in ”C” (autoscan) 0x8FD7 Load the SAL_A ”C” extension into memory 0x8FCF Enter into SAL–A ”C” extension 0x8FCE Scan for devices behind SNC scalability ports 0x8FCD ISPS Path: Initialize CBC registers, NID_DEF registers, Scan SPS SP ports 0x8FCC Start of processing for SPS based platforms 0x8FCB SPS Path: Search for SNC and SIOH devices 0x8FCA SPS Path
POST Codes Meaning 0x8FB4 Node BSP, BSPS: Set Synchronization Point SYNCMap_870 (in SNC SPAD register) 0x8FB3 System BSP, BSPS: Wait for NBSPs to reach Synchronization Point SYNCMap_870 0x8FB2 System BSP, BSPS: Initialize snoop filters on BSPS 0x8FB1 System BSP, BSPS: Wait for ”other” SBSP to fulfil its duties 0x8FAF System BSP, BSPS: Select Super–System–BSP (SSBSP) 0x8FAE Super SBSP, BSPS: Search devices (SNCs, SIOHs, BSPSs) 0x8FAD SBSP, BSPS: Init CBport and VGAport on all BSPS devices 0x8
POST Codes 0x8F94 Reset Path: Wait for all processors (hopefully) 0x8F93 Path: Set Recovery and Rest bit in all SNC SPAD registers 0x8F92 Check if all SNCs are Bx steppings or higher 0x8F91 Program MMCFG register of all SNCs 0x8F90 BSP will reset By use of MMCFG interface 0x8F8F APs wait loop 0x8F8E Jump to same code in memory (BSP + APs) 0x8F8D Get data for APs, stored by BSP (BSP + APs) 0x8F8C Get Recovery module info (thru PELoader, BSP only) 0x8F8B Load Recovery module into memory (th
SAL–A Hang POST Codes POST Codes Meaning 0xDEAD0100 Unable to levelize local RAM 0xDEAD0200 Wrong chip under SNC (neither SPS, nor SIOH) 0xDEAD0300 PEL module not found, local firmware might be corrupted 0xDEAD0400 South Bridge Vendor ID is incorrect, expected ICH2 or ICH4 0xDEAD0500 Scalability Port 0 presence bit is not set 0xDEAD0600 Scalability Port 1 presence bit is not set 0xDEAD0700 Scalability Port 0 framing failed ( Idle Flits Ack.
SAL–B POST Codes SAL–B POST Codes C-8 Meaning 0x87FF First check point. Initialize cr.iva/ar.eflag/ar.cflg/cr.lrr0/cr.lrr1/cr.ifa/cr.itir 0x87FE Initialize io_base address, CPU#, health, etc. for CPU’s. Initialize min_state_area for all CPUs (cpu_data_base+cpu_bspstore_base+cpu_health) cpu_data_base points to min state save area. TOM below and above 4G. Allocate sal_mp_info_table data and sal_efi stack area and legacy_stack (temp).
SAL–B POST Codes Meaning 0x87F0 BSP Shadow PAL module, initialize PAL shadow base, size, proc ptr initialize PAL procedure address entry & checksum AP’s PAL PMI base will be set. 0x87EF Cache flush after PAL shadow. 0x87EE Find PAL shadow size + align through SAL call. 0x87ED Find # of CPU’s present in the system, # of CPU, # of IOAPIC. 0x87EC Search for addition information EFI module (sal_efi_module_15) size, align, and scratch buff size. Initialize scratch buffer.
SAL–B Hang POST Codes POST Codes 0x07FD Then hang, if not found. See 0x87FD. If found copy top 64K legacy boot block ROM at xxxx:0000. 0x07FC Then hang, if not found. See 0x87FC. Else continue by saving in RAM. 0x07FB Then hang, if not found. See 0x87FB. Else continue by saving in RAM. Reserve 128k memory for NVM emulation. 0x07FA Then hang, if not found. See 0x87FA. Else continue by saving in RAM. 0x07F9 Then hang, if not found. See 0x87F9. Else continue by saving in RAM.
SAL–F POST Codes POST Codes Meaning 0x87BF First check point. Checkpoint in v6b00_83_ip2x. Update EBDA entry inside SST Create EFI memory descriptor Update SST checksum. 0x87BE Check point near v6b00_83_5 Search FIT for ACPI module (SAL_C_module_17) and get size, align, scratch buff size. 0x87BD Load image by module type (sal_c_module_17). Use PELoader. 0x87BC Load image by module type (sal_c_module_17). Flush cache. 0x87BB Initialize memory manager (0x0) by call to SAL_C.
SAL–F Hang POST Codes POST Codes 0x07BE Hang if ERROR. See 0x87BE. 0x07BD Hang if not found. Get entry point, and GP value. See 0x87BD. 0x07BC Hang on ERROR. Build MP & ACPI table. See 0x87BC. 0x07BB Hang on ERROR. See 0x87BB. 0x07BA Hang on ERROR. See 0x87BA. 0x07B9 Hang on ERROR. See 0x87B9. 0x07B8 Hang on ERROR. See 0x87B8. 0x07B7 Hang on ERROR. See 0x87B7. 0x07B6 Hang on ERROR. See 0x87B6. 0x07B5 Hang on ERROR. See 0x87B5. 0x07B4 Hang on ERROR. Get entry point, and GP value.
IA–32 POST Codes IA–32 POST Codes Meaning 0x00D0 Starting POINT control from SAL Set direction. Create Stack. Next checkpoint 0x00D5. 0x00D5 Get address and size of legacy BIOS. Clear the BootBlock flag. Next checkpoint 0x00D6. 0x00D6 Form the ROM image in memory. Next checkpoint 0x00D7. 0x00D7 Search for compressed RUNTIME interface module. If not found HANG checkpoint 0x00DE, else next checkpoint 0x00D8. 0x00D8 Decompress RUNTIME module to RAM segment.
IA–32 POST Codes C-14 Meaning 0x0008 Check CMOS diagnostic byte to determine if battery power is OK and set error flags if necessary. Verify CMOS checksum manually by reading storage area, if not O.K. load with power–on default values and clear password. Clear CMOS pending interrupt. Initialize Status Registers A in CMOS. Next, checkpoint 0x0007. 0x0007 Initialize the BIOS update data area (BUP), and update the communication vector between BIOS and INT13. Initialize RT_CMOS_BYTE.
IA–32 POST Codes Meaning 0x0023 Read the 8042 input port and save switch setting, check for green KBC, and disable the keyboard controller password. Performing any necessary configuration before initializing the interrupt vectors. Next, checkpoint 0x0024. 0x0024 Perform any OEM specific initialization before interrupt vector initialization. Interrupt vector initialization is about to begin. Next, checkpoint 0x0025. 0x0025 Initializes interrupt vector table.
IA–32 POST Codes Meaning 0x002D The video ROM has returned control to BIOS POST Performing any required processing after the video ROM had control. Uncompress and initialize ADM (Advanced Display Manager) module. If ADM not available HALT! Uncompress and initialize small BIOS and/or silent logos, detect and reset mouse, perform any required chipset or OEM initialization processing after video ROM initialization. Establish link for console Redirection. Next, checkpoint 0x002E.
IA–32 POST Codes Meaning 0x003A Display message to press a key Hit or OEM defined key to enter setup. Display entering setup message “Entering Setup” if DEL key has been pressed. Next, checkpoint 0x0040. 0x0040 Check for or keys to limit wait for key press. The DEL and ESC keys are also checked in the majority of the checkpoints from checkpoint 0x0040 to checkpoint 0x0059. Initialize the global data area with variables used during quick boot and tick sound.
IA–32 POST Codes C-18 Meaning 0x0060 The DMA page register test passed. Test DMA#1 Registers. If error found, display DMA error string. HALT! Next, checkpoint 0x0062. 0x0062 The DMA controller 1 base register test passed. Test DMA#2 Registers. If error found, display DMA error string. HALT! Next, checkpoint 0x0065. 0x0065 The DMA controller 2 base register test passed. Enable DMA#1, enable DMA#2, and initialize DMA #1 and DMA #2. Next, checkpoint 0x0066.
IA–32 POST Codes Meaning Note that there The convention for the DIM POST codes is as follows: will be 15–bit Port 80 = 0x84 post codes in Port 81 = DIM Function number | DI number this area. These indicate Device Initialization Manager sub–codes. 0x0085 Display error messages. Display F1/F2 message if bad CMOS Wait for F1/F2 or key press. Determine whether setup can be executed according to POST flag. Load CMOS and GPNV default values if F2 was pressed and go to checkpoint 0x0089.
IA–32 POST Codes 0x008E Meaning Uncompress INT 13 module. If module not found, go to checkpoint 0x0093. Update BIOS to INT 13 communication segment. Build INT 13 module header. Update communication between POST, Runtime, and INT 13. Check whether to initialize floppy or not. Next, checkpoint 0x0093. 0x0093 Test for SCSI boot. If yes SCSI boot, scan for option ROMs, activate ADM if not already activated, initialize SCSI drive numbers in BIOS data area, and continue on.
IA–32 POST Codes Meaning 0x009A Set the RS–232 base address. Next, checkpoint 9Bh. 0x009B Perform any chipset or OEM initialization. If needed check Coprocessor at checkpoint 0x009C else next, checkpoint A2h. 0x009C Coprocessor test done. Next, checkpoint 9Dh. 0x009D Initialization after the Coprocessor test is complete. Update equipment byte in CMOS and CMOS checksum. Next, checkpoint A2h. 0x00A2 Display any SMART error messages. Test for floppy drive.
IA–32 POST Codes 0x00A8 Initialization before passing control to the adapter ROM at E000h completed. Pass control to the adapter ROM at E000h. Next, checkpoint 0x00A9. 0x00A9 Return control from ROM. If ROM found, enable E000 shadow and copy ROM to shadow. Next, checkpoint 0x00AA. 0x00AA Clear screen and display system configuration if no OEM logo. Enable/disable USB according to CMOS setting. Enable/disable Num Lock according to CMOS setting. Initialize extended keyboard.
DIM Code Checkpoints DIM Codes Meaning 0x??2A Initialize different BUSes and perform the following functions: Reset, Detect, and Disable (function 0); Static Device Initialization (function 1); Boot Output Device Initialization (function 2). Function 0 disables all device nodes, PCI devices, and PnP ISA cards. It also assigns PCI bus numbers.
PCI Diagnostic POST Codes POST Codes Name 31–16 Post code main part See below 15–12 Ext3 Module number (0 or 1) 11–08 Ext2 IOB number (0 or 1) 07–04 Ext1 Hub link number for the PCI (1 to 4) 03–00 Ext0 P64H2 secondary bus (0x“A” or 0x“B”) Table 49.
EFI POST Code MAP The following rules apply to POST code encoding: Bit 15: 1 – IA64 code being executed, 0 – IA–32 code being executed Bit 14: 1 – system stopped due to known failure, 0 – progress indication Bit 13: 1 – fault or trap (no change in module numbers), 0 – normal execution In the event of a fault or trap, only bit 13 is set to allow fault detection. Bit 12: Reserved Bit 11–4: Module type Bit 3–0: Sub–module type The module number identifies major modules such as memory, PCI, ACPI, etc.
Recovery Port 80 POST Codes POST Codes Meaning 0xAA00 BIOS image loaded OK. 0xAA10 BIOS Image File loading from the media is in progress. 0xAA11 Removable Magnetic ATAPI device has been detected. 0xAA2X Flash update operation status. X – can have a value from 0 to 0xF. This is number of the block being updated. 0xAA80 ATAPI device has been reset to recover from a reading error. BIOS Image File loading from the media is in progress. 0xAA81 Waiting for ATAPI device ready.
POST Codes Meaning 0xAAD2 CD_TAIL_READ_ERROR 0xAAD3 LS120_READ_ERROR 0xAAE0 FILE_SYSTEM_ERROR 0xAAE1 FILE_NOT_FOUND_ERROR 0xAAE2 UNKNOWN_DEVICE_ERROR 0xAAE3 READ_ERROR 0xAAE4 CD_BOOT_REC_READ_ERROR 0xAAE5 CD_BOOT_REC_BYTE_0_BAD 0xAAE6 CD_BOOT_REC_CD001_ERROR 0xAAE7 CD_CATALOG_READ_ERR 0xAAE8 CD_INVALID_DEFAULT_HDR_ID 0xAAE9 CD_SEARCH_BOOTABLE_IMAGE 0xAAEA CD_SECTION_NOT_BOOTABLE 0xAAEB CD_MEDIA_TYPE_NOT_HD 0xAAEC CD_NO_BOOT_IMAGE_FOUND 0xAAED CD_LOAD_MBR_FAILURE 0xAAEE CD_
Runtime POST Codes POST Codes 0xAFCD IA–32 Intercept Trap due to an unsupported IA–32 instruction 0xAFE8 Normal SAL Machine Check Handling in Progress 0xAFE9 Could Not Correct MC Error, Halting CPU 0xAFEA MCA successfully completed, passing control back to PAL (Resume) 0xAFEB Calling OS MCA for Machine Check error handling 0xAFEC Machine Check Handler Processing Rendezvous Request 0xAFED OS request for SAL Clear Processor/Platform Error/State Log in progress 0xAFEE SAL Platform OEM MCA Error
Boot Error Messages Message Displayed Description Boot Failure ... This is a generic message indicating the BIOS could not boot from a particular device. This message is usually followed by other information concerning the device. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device BIOS could not find a bootable device in the system and/or removable media drive does not contain media. Table 56.
System Configuration Error Messages Message Displayed Description DMA–2 Error Error initializing secondary DMA controller. This is a fatal error, often indication a problem with system hardware. DMA Controller Error POST error while trying to initialize the DMA controller. This is a fatal error, often indication a problem with system hardware. Checking NVRAM. Update Failed BIOS could not write to the NVRAM block.
CMOS Error Messages Message Displayed Description CMOS Date/Time Not Set The CMOS Date and/or Time are invalid. This error can be resolved by readjusting the system time in AMIBIOS Setup. CMOS Battery Low CMOS Battery is low. This message usually indicates that the CMOS battery needs to be replaced. It could also appear when the user intentionally discharges the CMOS battery. CMOS Settings Wrong CMOS settings are invalid. This error can be resolved by using AMIBIOS Setup.
PAM Message List PAM messages can be consulted online and/or printed at the user’s request. The following table indicates PAM message IDs with a brief description.
Description 2B2B1025 Failure status: Degraded 2B2B1026 Failure status: Failed 2B2B1027 Error validating XML document 2B2B1028 Invalid length 2B2B1029 Unable to create directory 2B2B102A Unit excluded 2B2B102B Unit reinserted 2B2B102C Bad clock frequency in PIROM 2B2B102D PIROM information not accessible 2B2B102E QBB clock ratio 2B2B102F No network adapter present 2B2B1030 Disk full 2B2B1031 Cannot copy XML file 2B2B1032 New release activated 2B2B2000 Method not implemented 2B2B
Description C-34 2B2B201D Service 2B2B201E File operation failed 2B2B2100 Cannot add CellBlock 2B2B2101 Cannot remove CellBlock 2B2B2102 Hardware identifier out of range 2B2B2103 CellBlock Hardware identifier already assigned 2B2B2104 PAP software started 2B2B2105 Incorrect signature 2B2B2106 Config information successfully applied to cellblock 2B2B2107 Cannot apply config information using file 2B2B2200 Object copied successfully 2B2B2201 Object lock
Description 2B2B222A Domain group cannot be removed 2B2B222B Domain cannot be removed because it is not in an INACTIVE state 2B2B222C Domain command rejected 2B2B222D MAESTRO Domain power state unknown 2B2B222E Domain synchronization with MAESTRO failed 2B2B222F Fan box is not available 2B2B2230 IOR not available 2B2B2232 Not enough DPS 2B2B2233 No SPS fan box is available on module 2B2B2234 Domain cannot be powe
Description C-36 2B2B2303 PAM software checks the connection with PMB 2B2B2304 PAM software detected a connection error with PMB 2B2B2305 RPC trace message (PAP <–> PMB dialog) 2B2B2306 RPC connection error 2B2B2307 RPC error 2B2B2400 Cannot add object 2B2B2401 Cannot remove object 2B2B2402 Object added to collection 2B2B2403 Object removed from collection 2B2B2404 Inconsistency in filter 2B2B2405 Subscription test (used to validate a new event subscription) 2B2B2406
Description 2B2B2519 FRU active (in use in a running domain) 2B2B2520 FRU inactive (not used in a running domain) 2B2B2521 FRU ready for maintenance 2B2B2522 FRU not ready for maintenance 2B2B2523 No maintenance procedure for this FRU 2B2B2524 Module main off 2B2B2525 Only x out of y Mbytes have been initialized 2B2B2526 FRU or system EEPROM successfully written / updated 2B2B2527 Unable to write / update FRU EEPROM 2B2B2528 Unable to read the System EEPROM 2B2B2529 Cannot access CPU LI
Description C-38 2B2B270F FTP session opened 2B2B2710 Engineering modes were reset to their default value 2B2B2711 ZIP error 2B2B2712 Zip file already created 2B2B2713 Zip file already closed 2B2B2714 NEC Alarm 2B2B2800 Incorrect FTP server configuration on PAP 2B2B2801 Firmware version identifier not found 2B2B2802 Remove reference firmware denied 2B2B2803 BootRom version of PMB firmware does not match BootRom version of MAESTRO firmware 2B2B2804 The reference version
Description 2B2B3001 Unknown PUID 2B2B3002 Function not supported 2B2B3005 Process in progress 2B2B3006 Debug message 2B2B3007 MAESTRO component fault ON 2B2B3008 MAESTRO component fault OFF 2B2B3009 MAESTRO internal error 2B2B300A Operation failed 2B2B3100 MAESTRO is starting 2B2B3101 MAESTRO is ready 2B2B3200 PMB firmware successfully reloaded 2B2B3201 PMB firmware reloading failed 2B2B3202 PMB firmware: starting MAESTRO from flash–prom failed 2B2
Description C-40 2B2B3325 ACPI signal deasserted 2B2B3326 FRU connected 2B2B3327 FRU isolated 2B2B3328 Cabinet door opened 2B2B3329 Cabinet door closed 2B2B3330 Cabinet intrusion detector cable is connected 2B2B3331 Cabinet intrusion detector cable is disconnected 2B2B3332 Battery failed 2B2B3333 I2C loop back error 2B2B3334 Clock frequency unknown 2B2B3335 PHPB fault 2B2B3400 Device missing. 2B2B3401 Device failed. 2B2B3402 SM bus access denied.
Description 2B2B3802 IPMI response 2B2B3803 IPMI watchdog timer expiration 2B2B3900 Trace of request received by DomainPool object 2B2B3901 Module hardware resources left unchanged 2B2B3902 Request rejected 2B2B3A00 JTAG illegal command 2B2B3A01 JTAG not supported command 2B2B3A02 JTAG illegal end state 2B2B3A03 JTAG cannot read 2B2B3A04 JTAG illegal end of file 2B2B3A05 JTAG illegal transition state 2B2B3A06 JTAG illegal TAP state 2B2B3A07 JTAG TDO mismatch 2B2B3A08 JTAG max retr
String Lengths Some messages indicate string length errors. The following table lists for each type of string the authorized string lengths. String Type CellBlock Name Scheme Name History Name Archive Name LUN Name Switch Event Description Identity System Name Table 62.
Glossary BIOS: Basic Input / Output System. A program stored in flash EPROM or ROM that controls the system startup process. 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.
Clipping: A PAM Event filter criterion. Clipping is defined on a Count / Time basis aimed at routing a pre–defined number of messages only. Identical messages are counted and when the number of messages indicated in the Count field is reached within the period of time indicated in the Time field, no other messages will be selected for routing. DC: Direct Current generated by the power supply. See AC. CMC: Corrected Memory Check.
E Event message: A message sent by a software component to the Event Manager for routing to a destination that is configured by an administrator. EEPROM: Electrically Erasable Programmable Read-Only Memory. A type of memory device that stores password and configuration data. See also EPROM. Event subscription: An object that defines the event channel, address, and filter for sending an event message. If no such object is defined, the event message is discarded. EFI: Extensible Firmware Interface.
FRB: Fault Resilient Boot. A server management feature. FRB attempts to boot a system using the alternate processor or DIMM. History Manager: The component running on the PAP Windows operating system that logs messages to history files. FRU: Field Replaceable Unit. A component that is replaced or added by Customer Service Engineers as a single entity. HPC: High Performance Computing. FSS: FAME Scalability Switch.
IIS: Internet Information Server. A group of Internet servers (including a Web or HTTP server and a FTP server) with additional capabilities for Microsoft) Windows) NT and Microsoft Windows 2000 Server (and later) operating systems. I/O: Input /Output. Describes any operation, program, or device that transfers data to or from a computer. Interface: A connection between a computer and a peripheral device enabling the exchange of data. See Parallel Port and Serial Port. IOB: Input / Output Board.
Module: a Midplane Board with all its connected components and utility devices. See CSS Module and MP. MP, MPI, MPB: Mid–Plane. All system hardware components are connected to the MP, which also houses the FAME Scalability Switch (FSS) and the internal clock. MTBF: Mean Time Between Failure. An indicator of expected system reliability calculated on a statistical basis from the known failure rates of various components of the system. Note: MTBF is usually expressed in hours.
PIROM: Processor Information ROM. Processor Information ROM (PIROM) contains information about the specific processor in which it resides. This information includes robust addressing headers to allow for flexible programming and forward compatibility, core and L2 cache electrical specifications, processor part and S–spec numbers, and a 64–bit processor number. RJ45: 8–contact regular jack. RMC: Remote Maintenance Console. ROM: Read-Only Memory.
SIO: Server I/O / Super I/O. 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. SIOH: Server I/O Hub. SMBIOS: System Management BIOS. SM–BUS: System Management Bus. SMIC: Server Management Interface Chip. SMP: Symmetrical Multi Processor.
USB: Universal Serial Bus. A plug–and–play interface between a computer and add–on devices. The USB interface allows a new device to be added to your computer without having to add an adapter card or even having to turn the computer off. distinguishes a broader telecommunication structure from a local area network (LAN). WBEM: Web Based Enterprise Management. WMI: Windows Management Interface. WOL: A feature that provides the ability to remotely power on a system through a network connection.
G-10 User’s Guide
Index A Access, front door, 1-13 Alarm, tamper, 1-13 Array partition (SR–0812/1422), creating, 5-5 Autocalls, configuring, 5-21 B BIOS error messages, C-2 POST codes, 3-12 post codes, C-1 BIOS info, domain, 3-8 Boot error messages, C-29 options, 5-8 Boot manager, EFI, 5-8 C CD–ROM drive, 1-11 accessing, 1-16 Channels, enabling / disabling, 5-36 Checking events, 4-29 hardware availability, 4-27 hardware connections, 4-27 histories, 4-29 PMB, 4-28 power status, 4-29 temperature status, 4-29 Clipping, 5-44 C
boot manager options, 5-8 entering Boot Manager, 5-8 file transfer protocol, 5-17 manual network configuration, 5-16 network setup and configuration, 5-16 shell, 5-11 EFI shell command syntax, 5-12 commands, 5-14 script, 5-13 starting, 5-11 Electrical safety, xvi Error messages BIOS, C-2 boot, C-29 CMOS, C-31 miscellaneous, C-31 storage device, C-29 system configuration, C-30 Ethernet hub, 1-11 data cables, B-21, B-22 Ethernet ports, 1-6, 1-11 Event filter advanced filtering criteria, 5-44 creating a new fi
IOR, 1-6 K Keyboard, 1-7 Keys, registry, C-42 KVM switch, 1-7 IOR (Linux), data cables, B-6 IOR (Windows), data cables, B-5 KVM Switch (Linux), data cables, B-4 KVM Switch (Windows), data cables, B-3 L Laser safety, xvii Linux, system users, 5-2 Locked state, details, 3-10 LS240 drive, 1-6 LUN properties, modifying, 4-29 M Managing, domains, 3-2 Memory, details, 3-10 Memory boards, 1-6 Message, severity levels, C-41 Messages, PAM, C-32 Microsoft Windows, system users, 5-2 Midplane, firmware information,
Power status checking, 4-29 details, 3-10 Power supply cables, server, B-23 Power–up, system domains, 2-8 Processors, 1-6 Q QBB, fan status, 4-15 QBB fan boxes, 1-6 QBBs, 1-6 R RAID controller, 1-8 Rebooting, PAP application, 4-29 Related publications, documentation, xiii Reset, domain, 3-6 Resetting, PMB, 4-28 Resources, server, 1-17 S Safety, notices, xvi SCSI HBA, 1-6 SCSI rack, 1-8, 1-9 Search, hardware, 4-16 Serial ports, 1-6, 1-11 Server component breakdown, 1-4 monitoring, 4-1, 4-2 power supply ca
prerequisites, 5-27 setting up, 5-27 standard filtering criteria, 5-41 understanding filters, 5-39 System dimensions, A-1 domains, 2-8 weight, A-1 System components, DVD/CD–ROM drive, 1-6 System configuration, error messages, C-30 System users Linux, 5-2 Microsoft Windows, 5-2 setting up, 5-2 T Tamper alarm, 1-13 Temperature status, checking, 4-29 Testing, PMB, 4-28 Thermal zone, 4-11 Thresholding, 5-44 U USB ports, 1-6 User group, PAP, 5-18 V VGA port, 1-6 Index X-5
X-6 User’s Guide
Vos remarques sur ce document / Technical publication remark form Titre / Title : Bull NovaScale 5000 Series User’s Guide Nº Reférence / Reference Nº : 86 A1 89EF 02 Daté / Dated : January 2004 ERREURS DETECTEES / ERRORS IN PUBLICATION AMELIORATIONS SUGGEREES / SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION Vos remarques et suggestions seront examinées attentivement. Si vous désirez une réponse écrite, veuillez indiquer ci-après votre adresse postale complète.
Technical Publications Ordering Form Bon de Commande de Documents Techniques To order additional publications, please fill up a copy of this form and send it via mail to: Pour commander des documents techniques, remplissez une copie de ce formulaire et envoyez-la à : BULL CEDOC ATTN / Mr. L. CHERUBIN 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE Phone / Téléphone : FAX / Télécopie E–Mail / Courrier Electronique : +33 (0) 2 41 73 63 96 +33 (0) 2 41 73 60 19 srv.Cedoc@franp.bull.
PLACE BAR CODE IN LOWER LEFT CORNER 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.
