1. Manuals
  2. Brands
  3. Bull Manuals
  4. Server
  5. NovaScale 5 5 Series
  6. User manual

Bull NovaScale 5 5 Series User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Bull NovaScale 5xx5 & 6xx5
User's Guide
ORDER REFERENCE
86 A1 41EM 00

Advertisement

Table of Contents
loading

Related Manuals for Bull NovaScale 5 5 Series

Summary of Contents for Bull NovaScale 5 5 Series

  • Page 1 Bull NovaScale 5xx5 & 6xx5 User’s Guide ORDER REFERENCE 86 A1 41EM 00...
  • Page 3 Bull NovaScale 5xx5 & 6xx5 User’s Guide Hardware February 2005 BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE ORDER REFERENCE 86 A1 41EM 00...
  • Page 4 Linus Torvalds. The information in this document is subject to change without notice. Bull will not be liable for errors contained herein, or for incidental or consequential damages in connection with the use of this material.

  • Page 5: Table Of Contents

    ........Bull NovaScale Server Overview .
  • Page 6 1-21 Bull NovaScale Server Resources .........
  • Page 7 Microsoft Windows Domain ..........2-22 Linux Domain .
  • Page 8 Firmware Tab (Core MFL & PMB only) ....... . . 4-15 Thermal Zones (CSS module only) .
  • Page 9 Section II – Using EFI Utilities ..........5-11 Using the EFI Boot Manager .
  • Page 10 Appendix B. Cabling Diagrams ......... . NovaScale 5085 Server Data Cabling Diagram .
  • Page 11 Figure 3. Bull NovaScale Server cabinets ..........
  • Page 12 Figure 47. View Domain dialog ............3-27 Figure 48.
  • Page 13 Figure 96. Archive properties ............4-32 Figure 97.
  • Page 14 Figure 145. E–mail accounts configuration page ......... . . 5-90 Figure 146.
  • Page 15 List of Tables Table 1. PAM illegal characters ............xxiii Table 2.
  • Page 16 Table 47. Resources checklist – part 2 ..........5-83 Table 48.

  • Page 17: Intended Readers

    Intended Readers This guide is intended for use by the Administrators and Operators of NovaScale 5xx5/6xx5 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.

  • Page 18: Related Publications

    Server operation. This guide is intended for use by qualified support personnel. Bull 1300H/L & 1100H/L Cabinets, 86 A1 91EM explains how to install and fit out rack cabinets for Bull NovaScale Servers and peripheral devices. Documentation Overview, 86 A2 27EM describes the hardware, software and online documentation available for Bull NovaScale Servers, related Operating Systems, and licensed programs.

  • Page 19: Regulatory Specifications And Disclaimers

    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.

  • Page 20: Federal Communications Commission (Fcc) Statement

    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.

  • Page 21: Definition Of Safety Notices

    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.

  • Page 22: Laser Safety Information

    Data Integrity and Verification Warning: Bull NovaScale Servers are designed to reduce the risk of undetected data corruption or loss. However, if unplanned outages or system failures occur, users are strongly advised to check the accuracy of the operations performed and the data saved or transmitted by the system at the time of outage or failure.

  • Page 23: Administrator's Memorandum

    Administrator’s Memorandum Domains • Manage Domain Schemes, on page 3-5 • Power ON Domain, on page 3-14 • Power OFF Domain, on page 3-16 • Perform a Manual Domain Reset, on page 3-17 • Perform a Domain Force Power OFF, on page 3-18 •...
  • Page 24 Configuration • Set up Server Users, on page 5-4 • Use the EFI Boot Manager, on page 5-12 • Use the EFI Shell, on page 5-14 • Set Up and Configure the EFI Network, on page 5-18 • Set up PAP Unit Users, on page 5-21 •...

  • Page 25: Pam Writing Rules

    PAM Writing Rules Illegal Characters The following table lists the illegal characters that must not be used in PAM identifiers. Illegal Characters à, é, è, ù, ^, ¨ Accentuated letters Slash Backslash “ Double quote ’ Simple quote ‘ Inverted comma &...

  • Page 26: Registry Keys

    Two versions of PAM software can be installed and used indifferently on the same machine: each new version is installed in a new directory. • SiteRoot: Contains site data file paths. Site data remains valid when the PAM software version changes. Registry keys are generally stored under: HKEY_LOCAL_MACHINE\SOFTWARE\BULL\PAM xxiv User’s Guide...

  • Page 27: Azerty/Qwerty Keyboard Lookup Table

    AZERTY/QWERTY Keyboard Lookup Table Figure 1. AZERTY keyboard Figure 2. QWERTY keyboard Preface...

  • Page 28: Operator's Memorandum

    Operator’s Memorandum Domains • Power ON a Domain, on page 3-14 • Power OFF a Domain, on page 3-16 • Perform a Domain Force Power OFF, on page 3-18 • Perform a Manual Domain Reset, on page 3-17 • Perform a Domain Memory Dump, on page 3-20 •...

  • Page 29: Chapter 1. Introducing The Server

    This chapter describes the main hardware components and user environment for NovaScale 5xx5/6xx5 Servers. It includes the following topics: • Bull NovaScale Server Overview, on page 1-2 • Accessing Server Components, on page 1-20 • Bull NovaScale Server Resources, on page 1-22 •...

  • Page 30: Bull Novascale Server Overview

    Bull NovaScale Server Overview Bull NovaScale Servers for business and scientific applications are based upon the FAME architecture (Flexible Architecture for Multiple Environments), leveraging the latest generation of Intelr Itaniumr 2 processors. NovaScale 5xx5 Servers are designed to operate as single SMP systems and are delivered with one pre–configured domain englobing all the hardware and software resources...

  • Page 31: Extended Configurations

    Several Bull NovaScale Servers may be administered through a single instance of PAM software. Cluster Configurations Several Bull NovaScale Servers may be grouped to act like a single system, enabling high availability, load balancing and parallel processing. Introducing the Server...

  • Page 32: Server Features

    Server Features The main features of Bull NovaScale Servers are: Intelr Itaniumr Processor Family architecture: – Modularity, predictable performance and growth High availability: – Component redundancy – Capacity to isolate or replace a faulty component without service disruption – Global and unified system visibility –...

  • Page 33: Server Hardware

    Server Hardware Note: Abbreviations and acronyms are documented in the Glossary. Main server hardware components are: Central SubSystem Module (CSS Module) Main server hardware components are housed in the CSS Module. For easy access and servicing, the CSS Module is composed of three interconnected units: Front Unit Core Unit Rear Unit...

  • Page 34: Rear Unit

    Rear Unit IO board Compact (IOC) The IOC provides 6 x 133 MHz PCI buses for the connection of up to 6 (2 long and 4 short) PCI–X boards, and a PCI Hot Plug Board (HPB). The IOC communicates with the rest of the system through the high–speed bidirectional link Scalability Port Switches (SPS) located on the MSX.

  • Page 35: Conformance To Standards

    • IPMI (Intelligent Platform Management Interface) • EFI (Extended Firmware Interface) • SMBIOS (System Management BIOS) • DIG64 (Developer Interface Guide for Intel Itanium Architecture) Windows Bull NovaScale Servers conform to the standards set out in the Windows Hardware Design Guide. Introducing the Server...

  • Page 36: Getting To Know The Server

    Getting to Know the Server Note: Abbreviations and acronyms are documented in the Glossary. NovaScale 5085 Server Note: Server components and configuration may differ according to the version chosen. The server is delivered rack–mounted and pre–cabled in a low or high cabinet, typically containing the following components: Front Rear...

  • Page 37: Novascale 5165 Server

    NovaScale 5165 Server Note: Server components and configuration may differ according to the version chosen. The server is delivered rack–mounted and pre–cabled in a low or high cabinet, typically containing the following components: Rear Front CSS module with core unit, power supply and AC power cable, including: IO Box (IOC) with: IO Box (IOC) with: IOL board –...

  • Page 38: Novascale 6085 Server

    NovaScale 6085 Server Note: Server components and configuration may differ according to the version chosen. The server is delivered rack–mounted and pre–cabled in a low or high cabinet, typically containing the following components: Front Rear XXXXXXXX XXXXXXXXXXXXXXXXXXXX CSS module with core unit, power supply and AC power cable, including: 2xIO Boxes (IOC) each with: IOL board –...

  • Page 39: Novascale 6165 Server

    NovaScale 6165 Server Note: Server components and configuration may differ according to the version chosen. The server is delivered rack–mounted and pre–cabled in a low or high cabinet, typically containing the following components: Front Rear CSS module with core unit, power supply and AC power cable, including: IO Box (IOC) with: IO Box (IOC) with: IOL board –...

  • Page 40: Server Components

    Server Components Note: Server components and configuration may differ according to the version chosen. Central Subsystem (CSS) Module The CSS module houses main hardware components: Front Rear Front 1 or 2 QBB (Quad Brick Board) subset(s) Each QBB subset houses: •...

  • Page 41: Integrated Platform Administration Processor (Pap) Unit

    Integrated Platform Administration Processor (PAP) Unit Warning: The PAP unit has been specially configured for Bull NovaScale Server administration and maintenance. NEVER use the PAP unit for other purposes and NEVER change PAP unit configuration unless instructed to do so by an authorized Customer Service Engineer.

  • Page 42: Integrated Console

    Integrated Console According to version, the console is located in the center of a high cabinet or at the top of a low cabinet. The inegrated slideaway Console contains the keyboard, monitor and touch pad used for local access to the server and to the Platform Administration Processor (PAP) Unit. •...

  • Page 43: Keyboard / Video / Mouse (Kvm) Switch

    Keyboard / Video / Mouse (KVM) Switch The KVM Switch allows the use of the integrated console for the local server and the local Platform Administration and Maintenance console. 8–Port KVM Switch • 8 ports • 1 power cable Figure 11. 8–port KVM switch features 16–Port KVM Switch •...

  • Page 44: Sr-0812 Scsi Raid / Sj-0812 Scsi Jbod Disk Racks

    SR–0812 SCSI RAID / SJ–0812 SCSI JBOD Disk Racks Optionally, SR–0812 SCSI RAID / SJ–0812 SCSI JBOD Disk Racks are delivered with pre–installed system disks (two RAID#1 and one spare disk per domain). Empty slots can be used for data disks. According to version, the Disk Rack is located in the main or I/O cabinet.

  • Page 45: Fda 1X00 Fc Disk Rack

    FDA 1x00 FC Disk Rack Optionally, the FDA 1x00 FC Disk Rack is delivered with pre–installed system disks (two RAID#1 and one spare disk per domain). Empty slots can be used for data disks. According to version, the Disk Rack is located in the main or I/O cabinet. •...

  • Page 46: Fda 1X00 Fc Extension Disk Rack

    FDA 1x00 FC Extension Disk Rack The FDA 1x00 FC Extension Disk Rack offers15 empty slots for data disks. According to version, the Disk Rack is located in the main or I/O cabinet. • 15 slots • 2 power cables (redundant power supply) Figure 17.

  • Page 47: Ethernet Hub

    Ethernet Hub The optional Maintenance LAN Ethernet Hub is used to connect PMB, PAP Unit and external FDA FC Disk Rack Ethernet ports. Ethernet Hub – 8 ports – 1 power cable – 1 power bar Figure 18. Ethernet hub features USB Modem The optional USB modem is used to transmit Autocalls to the Remote Maintenance Center, if your maintenance contract includes the Autocall feature.

  • Page 48: Accessing Server Components

    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: •...

  • Page 49: Opening / Closing The Slideaway Console

    Opening / Closing the Slideaway Console The server is equipped with an integrated console for local administration and maintenance operations. Figure 22. Slideaway console To open the slideaway console: 1. Slide the console forward until it clicks into place. 2. Use the front bar to lift the screen panel into position. To close the slideaway console: 1.

  • Page 50: Bull Novascale Server Resources

    Bull NovaScale Server Resources Note: According to server configuration and version, certain features and functions described in this guide may not be accessible. Please contact your Bull Sales Representative for sales information. System Resource and Documentation CD–Roms The Bull NovaScale Server System Resource and Documentation CD–Roms contain all the firmware and documentation referred to in this guide.

  • Page 51: Efi Utilities

    EFI Utilities The Bull NovaScale Server EFI utilities provide a complete set of configuration, operation, and maintenance tools: • EFI driver, • EFI Shell, • EFI system utility, • EFI system diagnostic, • Operating System loader. For further details, see Chapter 5. Tips and Features for Administrators.
  • Page 52 1-24 User’s Guide...

  • Page 53: Chapter 2. Getting Started

    Chapter 2. Getting Started This chapter explains how to connect to and start server domains. It includes the following topics: • Connecting to the PAM Web Site, on page 2-2 • PAM User Interface, on page 2-5 • Toggling the Local / Integrated Console Display, on page 2-8 •...

  • Page 54: Connecting To The Pam Web Site

    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.

  • Page 55: Connecting To The Pam Web Site From A Remote Computer

    Connecting to the PAM Web Site from a Remote Computer 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. The PAM Software utility can be accessed from any PC running Microsoft Windows with the Internet Explorer (6 or later) browser installed and/or from any workstation running Linux with the Mozilla (1.6 or later) browser installed.

  • Page 56: Simultaneous Connection To The Pam Web Site

    Simultaneous Connection to the PAM Web Site Several users can access the PAM Web site simultaneously. Important: If configuration changes are made, they may not be visible to other users unless they refresh the PAM Tree. As Customer Administrator, you can view the list of PAM users currently logged onto the PAM Web site by clicking Hardware Monitor →...

  • Page 57: Pam User Interface

    PAM User Interface PAM User Interface The PAM user interface is divided into three areas in the browser window: a Status pane, a PAM Tree pane, and a Control pane. Status Pane Control Pane PAM Tree Pane Figure 26. PAM user interface Note: For further details about the PAM user interface, please consult the User’s Guide.

  • Page 58: Checking Server Status Via Pam

    Checking Server Status via PAM The PAM user interface allows you to check system status at a glance. If the Functional Status icon in the Status pane and the CSS Availability Status bar are green, the server is ready to be powered up. PAM Status Pane The Status pane, which is automatically refreshed every few seconds, provides quick access to the following synthetic information:...

  • Page 59: Pam Tree Pane

    PAM Tree Pane Note: The PAM tree builiding process may take one to two minutes. The PAM tree pane is refreshed on request. The PAM Tree pane provides access to server administration and maintenance features: Tree Nodes Function to power on / off and manage domains. See Chapter 3. Manag- Domain Manager ing Domains.

  • Page 60: Toggling The Local / Integrated Console Display

    Toggling the Local / Integrated Console Display During the powering up / down sequences, you will be requested to toggle the local / integrated console from the PAP unit display to the server domain display, or vice versa, as explained below. CAUTION: Access to the local / integrated console should be restricted to Customer / Support Administrators and Operators ONLY to avoid inadvertent damage to software and/or...

  • Page 61: Powering Up / Down Server Domains

    Powering Up / Down Server Domains To power up / down the server, see: • Powering Up / Down the NovaScale 5xx5 Server Domain, on page 2-9 • Powering Up / Down NovaScale 6085 Server Domains, on page 2-11 • Powering Up / Down NovaScale 6165 Server Domains, on page 2-15 Powering Up the NovaScale 5xx5 Server Domain NovaScale 5xx5 Servers are designed to operate as single SMP systems and are delivered with one pre–configured domain.

  • Page 62: Powering Down The Novascale 5Xx5 Server Domain

    Figure 31. Domain state 5. Toggle the local / integrated console from the PAP unit display to the server display. See Toggling the Local / Integrated Console Display, on page 2-8. 6. Wait for the Operating System to load completely. The domain is now fully functional. 7.

  • Page 63: Powering Up Novascale 6085 Server Domains

    Powering Up NovaScale 6085 Server Domains The NovaScale 6085 Server is designed to operate as two hardware–independent SMP systems, or domains. For easy configuration and optimum use of the physical and logical resources required for simultaneous operation, domains are defined by the Customer Administrator via the PAM Domain Scheme wizard.

  • Page 64: Table 5. Myoperationsscheme Organization - Mono-Module Server

    MyOperationsScheme Organization Domain Identity: MyOperations–1 Hardware Cell Cell_0 Operating System Linux Windows (customer–specific) EFI LUN** *<MyServer>_0LU0 Module0_IOC0 QBBs Module0_QBB0 Domain KVM Ports ***CSS0_Mod0_IO0 Domain Identity: MyOperations–2 Hardware Cell Cell_1 Operating System Linux Windows (customer–specific) EFI LUN** *<MyServer>_0LU1 Module0_IOC1 QBBs Module0_QBB1 Domain KVM Ports ***CSS0_Mod0_IO1 * <MyServer>...

  • Page 65: Figure 32. Domain Schemes List Dialog

    3. Select MyOperationsScheme and click Apply. Figure 32. Domain schemes list dialog 4. When requested, click Yes to confirm. MyOperations–1 and MyOperations–2 domains are loaded in the Control pane. If the domains are ready to be powered up, INACTIVE is displayed in the Domain State boxes and the Power On button is accessible for each domain.

  • Page 66: Powering Down Novascale 6085 Server Domains

    6. Select MyOperations–2 in the Control pane and click Power On to power up the domain and associated hardware components. 7. Follow the power–on steps displayed in the Domain State boxes, until RUNNING is displayed in both Domain State boxes. Figure 34.

  • Page 67: Powering Up Novascale 6165 Server Domains

    Powering Up NovaScale 6165 Server Domains The NovaScale 6165 Server is designed to operate as four hardware–independent SMP systems, or domains. For easy configuration and optimum use of the physical and logical resources required for simultaneous operation, domains are defined by the Customer Administrator via the PAM Domain Scheme wizard.

  • Page 68: Table 6. Myoperations Scheme Organization - Bi-Module Server

    MyOperationsScheme Organization Domain Identity: MyOperations–1 Hardware Cell Cell_0 Operating System Linux Windows (customer–specific) EFI LUN** *<MyServer>_0LU0 Module0_IOC0 QBBs Module0_QBB0 Domain KVM Ports ***CSS0_Mod0_IO0 Domain Identity: MyOperations–2 Hardware Cell Cell_1 Operating System Linux Windows (customer–specific) EFI LUN** *<MyServer>_0LU1 Module0_IOC1 QBBs Module0_QBB1 Domain KVM Ports ***CSS0_Mod0_IO1 Domain Identity: MyOperations–3...

  • Page 69: Figure 35. Domain Schemes List Dialog

    To power up server domains: 1. From the PAM Tree, click Domain Manager to open the Control pane. You are invited to load a domain configuration scheme. 2. Click Schemes. The Schemes List dialog opens displaying the pre–configured scheme. 3. Select MyOperationsScheme and click Apply. Figure 35.

  • Page 70: Powering Down Novascale 6165 Server Domains

    5. Select MyOperations–1 in the Control pane and click Power On to power up the domain and associated hardware components. 6. Repeat Step 5 for each domain in the Control pane. 7. Follow the power–on steps displayed in the Domain State boxes, until RUNNING is displayed in all Domain State boxes.

  • Page 71: Preparing Server Domains For Remote Access Via The Enterprise Lan

    Preparing Server Domains for Remote Access via the Enterprise LAN CAUTION: Access to the local / integrated console should be restricted to Customer / Support Administrators and Operators ONLY to avoid inadvertent damage to software and/or hardware components. Note: Required networking data is indicated in the Read Me First document delivered with the server and is also recorded under the corresponding PAM Domain Identity.

  • Page 72: Linux Suse Domain

    8. Click Apply changes to apply all changes. 9. Click Return to index. 10.Click Log Out to exit Webmin. 11. Toggle the integrated console to the PAP unit port. 12.From the Customer Administrator PAM tree, click Configuration Tasks → Domains → Identities to open the Identities page.

  • Page 73: Preparing Server Domains For Remote Access Via The Web

    Preparing Server Domains for Remote Access via the Web CAUTION: Remote access via the Web is a potential security hazard. Customers are strongly advised to protect their systems with up–to–date protection devices such as virus–prevention programs and firewalls, and to maintain a detailed record of authorized users.

  • Page 74: Connecting To A Server Domain Via The Enterprise Lan

    Connecting to a Server Domain via the Enterprise LAN Microsoft Windows Domain 1. Check that Client for Microsoft Networks is installed on the remote computer and that the remote computer is connected to the same LAN as the server domain. 2.

  • Page 75: Connecting To The Server Via The Web

    Connecting to the Server via the Web Microsoft Windows Domain 1. Check that Internet Explorer (6 or later) and Terminal Server Client are installed on the remote computer. 2. Launch the Internet Explorer or Netscape browser and connect to the server desktop, url: http://<networkname>/tsweb/, where <networkname>...
  • Page 76 2-24 User’s Guide...

  • Page 77: Chapter 3. Managing Domains

    Chapter 3. Managing Domains This chapter explains how, as Customer Administrator and/or Customer Operator, you can manage server domains. It includes the following topics: • Introducing PAM Domain Management Tools, on page 3-2 • Managing Domain Configuration Schemes, on page 3-5 •...

  • Page 78: Introducing Pam Domain Management Tools

    Please contact your Bull Sales Representative for sales information. A Bull NovaScale Server domain englobes all the hardware and software resources managed by an Operating System instance. NovaScale 5xx5 Servers are designed to operate as single SMP systems and are delivered with one pre–configured domain.
  • Page 79 From the PAM Tree, click Domain Manager to open the Control pane. Toolbar Status Panel Command Bar Toolbar Powering View Dynamically displays domain power sequences and gives ac- cess to Power Logs, see details on page 3-22 and BIOS Info, see details on page 3-24.
  • Page 80 Command Bar Power On Powers on the selected domain, see details on page 3-14. Power Off Powers off the selected domain, see details on page 3-16. Reset Resets the selected domain, see details on page 3-17. Force Power Off Forcibly powers off the selected domain, see details on page 3-18.

  • Page 81: Managing Domain Configuration Schemes

    Managing Domain Configuration Schemes Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. What You Can Do Via the Schemes tool in the Domain Manager Control pane toolbar, you can: • Synchronize domains •...

  • Page 82: Synchronizing Novascale 5Xx5 Server Domains

    Synchronizing NovaScale 5xx5 Server Domains The Synchronize Domains command is used to load the NovaScale 5xx5 Server domain. Each NovaScale 5xx5 Server is delivered with one pre–configured domain. To load the server domain: Click Synchronize Domains in the toolbar. The server domain(s) appear(s) in the Control pane for management.

  • Page 83: Figure 39. Scheme Properties Dialog

    NovaScale 6085 Server NovaScale 6165 Server CellBlocks Shows the Central Subsystems included in the scheme and how they are partitioned into domains. Identifies physical partitions. Identities Shows the Identities allocated to each domain. EFI LUNs Indicates the EFI LUNs used to boot each domain. Indicates domain configuration status.

  • Page 84: Loading A Domain Configuration Scheme

    Loading a Domain Configuration Scheme To power on server domains, you must first load the required Domain Configuration Scheme from the Domain Manager Control pane. Once the domain configuration scheme has been loaded, domains can be powered up simultaneously or independently. To load a scheme: 1.

  • Page 85: Figure 41. Domain Manager Control Pane

    If the domains are ready to be powered up, INACTIVE is displayed in the Domain State boxes. The Power On button becomes accessible once a domain has been selected. NovaScale 6085 Server Functional status icon & Domain selected CSS availability status indicator Operating System type Power On button accessible GREEN...

  • Page 86: Adding Domains To The Current Domain Configuration

    Adding Domains to the Current Domain Configuration A scheme can include domains from one or more Central Subsystems. More domains can be made available for domain management by adding one or more schemes to the current domain configuration. Notes: • New domains must only include resources that are INACTIVE in the current domain configuration.

  • Page 87: Saving The Current Domain Configuration Snapshot

    Saving the Current Domain Configuration Snapshot You may want to save the current domain configuration, in particular if more than one scheme has been loaded and/or if you have modified domain configuration. When you save the current domain configuration, you create a new domain configuration scheme which is then available for domain management.

  • Page 88: Table 8. Myoperations Scheme Organization - Novascale 6Xx5 Servers

    MyOperationsScheme Organization – NovaScale 6xx5 Servers Domain Identity: MyOperations–1 Hardware Cell Cell_0 Operating System Linux Windows (customer–specific) EFI LUN** *<MyServer>_0LU0 Module0_IOC0 QBBs Module0_QBB0 Domain KVM Ports ***CSS0_Mod0_IO0 Domain Identity: MyOperations–2 Hardware Cell Cell_1 Operating System Linux Windows (customer–specific) EFI LUN** *<MyServer>_0LU1 Module0_IOC1 QBBs...
  • Page 89 Notes: • In the screen shots, tables, and examples in this guide: – MyOperationsScheme–xx is referred to as MyOperationsScheme – MyOperations–xx–1 is referred to as MyOperations–1 – MyOperations–xx–2 is referred to as MyOperations–2 – MyOperations–xx–3 is referred to as MyOperations–3 –...

  • Page 90: Powering On A Domain

    Important: Certain domain configuration and management tools are reserved for use with partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Once connected to the Customer’s site power supply, the server initializes to the stand–by mode and the integrated PAP unit powers up.

  • Page 91: Table 9. Power-On States

    2. Select the required domain. If the domain is in the stand–by mode, INACTIVE is displayed in the Domain Status panel and the Power On button is accessible. Important: If INACTIVE is not displayed in the Domain Status panel and the Power On button is not accessible, check whether another user has already launched the power–up sequence on this domain.

  • Page 92: Powering Off A Domain

    Powering Off a Domain What You Can Do During the domain power–off sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status Server domains can either be powered off from the Operating System (RECOMMENDED) or from the PAM Domain Manager, according to Operating System power settings.

  • Page 93: Manually Resetting A Domain

    Manually Resetting a Domain What You Can Do During the domain reset sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status The Reset command is used to restart the current Operating System without powering off/on the domain.

  • Page 94: Forcing A Domain Power Off

    Forcing a Domain Power Off What You Can Do During the domain force power–off sequence, you can: • View functional status • View power logs • View powering sequences • View BIOS info • View request logs • View domain configuration, resources and status The Force Power Off command powers down domain hardware to the standby mode independently of the Operating System.
  • Page 95 For a detailed view of the Force Power Off sequence, click Powering View in the Toolbar. See Viewing Powering Sequences, on page 3-23. 5. Repeat Steps 2 to 4 for each domain to be forcibly powered down. Note: If an error message is displayed in the Domain Status panel, the Power Off sequence has failed.

  • Page 96: Performing A Domain Memory Dump

    Performing a Domain Memory Dump The Dump command is used when the Operating System hangs and allows technicians to diagnose software problems by saving domain memory. Warning: The Dump command should only be used if the Operating System is not able to respond to a standard Power OFF command.

  • Page 97: Viewing Domain Functional Status

    Viewing Domain Functional Status The Domain Functional Status indicator in the Domain Manager Control pane shows the functional status of the last action performed on each domain, e.g. if the last Power ON/OFF sequence was successful, the indicator is green. As Customer Administrator, you can toggle the PAM Tree to display the synthetic functional status (round, colored indicator next to the Domain Manager node) of all the domains loaded in the Domain Manager Control pane , e.g.

  • Page 98: Viewing Domain Power Logs

    Viewing Domain Power Logs Power logs are recorded during domain power ON/OFF sequences. This information is particularly useful for troubleshooting. See What To Do if an Incident Occurs, on page 3-47. During a Power ON/OFF Sequence 1. Click Domain Manager to open the Control pane. 2.

  • Page 99: Viewing Domain Powering Sequences

    Viewing Domain Powering Sequences A detailed view of powering sequences can be displayed by clicking Powering View in the Domain Manager Toolbar after a power request. Status Panel Item Explanation Domain Selected domain identity. Central Subsystem Name of the Central Subsystem containing the domain. Domain State Current power sequence step.

  • Page 100: Viewing Domain Bios Info

    Viewing Domain BIOS Info BIOS information is particularly useful for troubleshooting. See What To Do if an Incident Occurs, on page 3-47. To view BIOS information: 1. Click Domain Manager to open the Control pane. 2. Select the required domain. 3.

  • Page 101: Viewing Domain Request Logs

    Viewing Domain Request Logs The Request Logs dialog gives direct access to a trace of major domain operations (requests) and indicates their initiators (requestors). To view Request logs: 1. Click Domain Manager to open the Control pane. 2. Select the required domain. 3.

  • Page 102: Viewing Domain Configuration, Resources And Status

    Viewing Domain Configuration, Resources and Status Notes: • In the screen shots, tables, and examples in this guide: – MyOperationsScheme–xx is referred to as MyOperationsScheme – MyOperations–xx–1 is referred to as MyOperations–1 – MyOperations–xx–2 is referred to as MyOperations–2 – MyOperations–xx–3 is referred to as MyOperations–3 –...

  • Page 103: Viewing Domain Configuration

    Viewing Domain Configuration 1. Click Domain Manager to open the Control pane. 2. Select the required domain. 3. Click View in the Command bar to open the View Domain dialog. * Module 1 (Cell_2 & Cell_3): does not equip mono–module servers Figure 47.

  • Page 104: Figure 47. View Domain Dialog

    View Domain Dialog Items Domain Item Explanation Central Subsystem Name of the Central Subsystem containing the domain. Domain Identity Logical name and profile given to the domain. EFI LUN Boot LUN device location: NovaScale 5xx5 Server 0LU0 located in Module0_DIB0 or connected to Module0_IOC0 NovaScale 6085 Server 0LU0 located in Module0_DIB0 or connected to Module0_IOC0 0LU1 located in Module0_DIB1 or connected to Module0_IOC1...

  • Page 105: Viewing Domain Hardware Resources

    Viewing Domain Hardware Resources 1. Click Domain Manager to open the Control pane. 2. Select the required domain and click View Resources in the View Domain dialog to open the Domain Hardware Resources dialog. Figure 49. Domain Hardware Resources dialog 3-29 Managing Domains...

  • Page 106: Viewing Domain Details And Status

    Viewing Domain Details and Status 1. Click Domain Manager to open the Control pane. 2. Select the required domain and click Resources → More Info... in the Command bar to open the Domain Hardware Details dialog. 1. Click Domain Manager to open the Control pane. 2.

  • Page 107: Table 15. Domain Hardware Details Icons

    Domain Hardware Details icons are explained in the following table. Item Icon Meaning Memory Memory available per QBB. No problem detected, operating correctly. No problem detected, operating correctly. Green Green Minor problem reported, still operational. Minor problem reported, still operational. Yellow Serious problem reported, no longer capable of Functional Status...

  • Page 108: Table 14. Domain Functional Status Indicators

    Note: When the domain is INACTIVE, the Domain Hardware Details dialog indicates the resources that PAM will try to initialize for the domain during the next Power ON sequence. When the domain is RUNNING, the Domain Hardware Details dialog indicates the resources that PAM successfully initialized for the domain during the last Power ON or Reset sequence.

  • Page 109: Modifying Domain Configuration

    Modifying Domain Configuration Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. What You Can Do • Add Cells to a Domain • Remove Cells from a Domain • Change a Domain EFI boot LUN •...
  • Page 110 Your server is designed to operate as: NovaScale 6085 Server • two SMP systems, one using the hardware resources in Cell_0, the other using the hardware resources in Cell_1 (default configuration), • a single SMP system, using the hardware resources in both Cell_0 and Cell_1, •...

  • Page 111: Adding Cells To A Domain

    Adding Cells to a Domain Notes: • At least one Cell, containing one IOC and one QBB, must be available. • The Operating System must support added hardware. • The domain must be INACTIVE before configuration changes can be made. •...

  • Page 112: Figure 52. Add Cells To Domain Dialog (Mono-Module Server)

    NovaScale 6085 Server Figure 52. Add Cells to Domain dialog (mono–module server) NovaScale 6165 Server Figure 53. Add Cells to Domain dialog (bi–module server) 5. Select the required configuration and click OK. The letter A indicates the cell that will be added to the domain.

  • Page 113: Figure 54. Modify Domain - Add Cell Confirmation Dialog (Mono-Module Server)

    The new domain configuration is displayed in the Modify Domain dialog. NovaScale 6085 Server Cell_1 is added * Module 1 (Cell_2 & Cell_3): does not equip mono–module servers Figure 54. Modify Domain – Add Cell confirmation dialog (mono–module server) NovaScale 6165 Server Cells_1, _2, and _3 are added Figure 55.

  • Page 114: Removing Cells From A Domain

    Removing Cells from a Domain Notes: • At least one Cell, containing one IOC and one QBB, must remain. • The domain must be INACTIVE before configuration changes can be made. • When you remove a Cell from a NovaScale 6085 Server domain, the server can either operate as a single SMP system, using only the hardware resources in the remaining Cell, or as two SMP systems if the removed Cell is allocated to another domain.

  • Page 115: Figure 56. Modify Domain - Remove Cell Dialog (Mono-Module Server)

    NovaScale 6085 Server Remove Cell button * Module 1 (Cell_2 & Cell_3): does not equip mono–module servers Figure 56. Modify Domain – Remove Cell dialog (mono–module server) NovaScale 6165 Server Remove Cell button Figure 57. Modify Domain – Remove Cell dialog (bi–module server) 3-39 Managing Domains...

  • Page 116: Figure 58. Remove Cells From Domain Dialog (Mono-Module Server)

    4. Click Remove Cell. The Remove Cells from Domain dialog opens. NovaScale 6085 Server Figure 58. Remove Cells from Domain dialog (mono–module server) NovaScale 6165 Server Figure 59. Remove Cells from Domain dialog (bi–module server) 5. Select the required configuration and click OK. The letter R indicates the cell that will be removed from the domain.

  • Page 117: Figure 60. Modify Domain - Remove Cell Confirmation Dialog (Mono-Module Server)

    The new domain configuration is displayed in the Modify Domain dialog. NovaScale 6085 Server Cell_1 is free * Module 1 (Cell_2 & Cell_3): does not equip mono–module servers Figure 60. Modify Domain – Remove Cell confirmation dialog (mono–module server) NovaScale 6165 Server Cell_1 is free Figure 61.

  • Page 118: Changing The Domain Efi Boot Lun

    Changing the Domain EFI Boot LUN Notes: • At least two Cells must be included in the Domain. • The domain must be INACTIVE before configuration changes can be made. • When you change the EFI boot LUN, you will also change the Operating System instance.

  • Page 119: Figure 64. Modify Domain - Configure Lun Confirmation Dialog

    6. Select the required LUN and click OK. New domain configuration is displayed in the Modify Domain dialog. New boot LUN * Module 1 (Cell_2 & Cell_3): does not equip mono–module servers Figure 64. Modify Domain – Configure LUN confirmation dialog 7.

  • Page 120: Deleting A Domain

    Deleting a Domain Note: The domain must be INACTIVE to be deleted. Once loaded in the Domain Manager Control pane, a domain can be deleted from the current configuration. When the domain has been deleted, the corresponding resources can be re–allocated to another domain. To delete a domain from the current configuration: 1.

  • Page 121: Figure 66. Delete Domain Dialog - Bi-Module Server

    NovaScale 6165 Server Figure 66. Delete Domain dialog – bi–module server 4. Click Yes to confirm deletion of the selected domain from the current configuration. 3-45 Managing Domains...

  • Page 122: Figure 67. Domain Deleted Information Box

    An information box opens, informing you that the domain has been successfully deleted. The domain is no longer visible in the Control pane. Figure 67. Domain deleted information box 5. Click OK to continue. You can now re–allocate the resources of the deleted domain. See Adding a Cell to a Domain, on page 3-35 Note: Domain modifications are not saved and are only applicable while the selected domain is...

  • Page 123: What To Do If An Incident Occurs

    • the PAM Web interface (Status Pane and/or User History files), • e–mail (users with an appropriate Event Message subscription), • an autocall to the Bull Service Center (according to your maintenance contract) for analysis and implementation of the necessary corrective or preventive maintenance measures, where applicable.

  • Page 124: Dealing With Incidents

    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-24. Checking Hardware Exclusion Status If you are requested to check hardware exclusion status, see Excluding / Including Hardware Elements, on page 4-21.

  • Page 125: Chapter 4. Monitoring The Server

    Chapter 4. Monitoring the Server This chapter explains how, as Customer Administrator, you can supervise server operation. It includes the following topics: • Introducing PAM Monitoring Tools, on page 4-2 • Using the Hardware Search Engine, on page 4-9 • Viewing PAM Web Site User Information, on page 4-10 •...

  • Page 126: Introducing Pam Monitoring Tools

    Introducing PAM Monitoring Tools Main Central SubSystem (CSS) hardware components are managed by the comprehensive Platform Administration and Maintenance (PAM) software specifically designed for Bull NovaScale Servers. Note: Peripheral devices such as disk racks, PCI adapters, KVM switch, local console, and the PAP unit are managed by the Operating System and/or by dedicated software.

  • Page 127: Viewing System / Component Status

    Viewing System / Component Status What You Can Do • Check system status • Check CSS module availability status • Check event message status • View hardware presence status • View hardware functional status • View server hardware status • View FRU information •...

  • Page 128: Css Availability Status

    CSS Availability Status NovaScale 5085 Servers and NovaScale 6085 Servers When the CSS Module is operating correctly, the CSS Availabilty Status bar is green. If the CSS Module is not operating correctly, the bar is red. NovaScale 5165 Servers and NovaScale 6165 Servers The CSS Availabilty Status bar is divided into two zones.

  • Page 129: Pam Tree Pane

    PAM Tree Pane As Customer Administrator, you can view the presence and functional status of each hardware element from the PAM Tree pane. The PAM Tree pane is refreshed at your request. Use the Refresh PAM Tree button to update the display when required. Important: To maintain a trace of transient faults, PAM Tree functional and/or presence status indicators will not change color until the domain has been powered OFF/ON, even if...

  • Page 130: Table 19. Hardware Presence Status Indicators

    Presence Status Indicators Indicator Status Explanation This hardware element: This hardware element: NORMAL NORMAL – is physically present and accessible. Green This hardware element: MISSING MISSING – was present in a previous configuration but has – was present in a previous configuration but has disappeared.

  • Page 131: Displaying Functional Status

    Displaying Functional Status You can toggle the PAM Tree to view system / hardware functional status (round, colored indicator next to the Hardware Monitor node). If you expand the PAM Tree, the functional status of all hardware elements is displayed. Functional Status is a composite indicator summarizing Failure Status, Fault Status, Power Status, and Temperature Status indicators, where applicable.

  • Page 132: Figure 72. Pam Tree - Automatically Expanded Functional Status Display

    Important: To maintain a trace of transient faults, PAM Tree functional and/or presence status indicators will not change color until the domain has been powered OFF/ON, even if the error has been corrected. Overall server functional status is indicated by the system Functional Status icon in the Status pane.

  • Page 133: Using Pam Utilities

    Using PAM Utilities What You Can Do • Search for excluded hardware elements • Search for missing hardware elements • View PAM Web site information • View PAM version information • Exclude / include hardware elements Using the Hardware Search Engine The Hardware Search engine allows you to search for and view hardware elements corresponding to selected criteria, for example Excluded or Missing hardware elements.

  • Page 134: Viewing Pam Web Site User Information

    3. Once the search is complete, results are displayed in the control pane. Figure 74. Hardware Search result list (example) 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 →...

  • Page 135: Viewing Pam Version Information

    Viewing PAM Version Information PAM version information may be useful to help your Customer Service Engineer solve software–related problems. To view PAM version information, click Hardware Monitor → PAP. Complete PAM resource file information is displayed in the Control pane. Figure 76.

  • Page 136: Viewing Server Hardware Status

    Viewing Server Hardware Status When you click the CSS Name in the PAM tree (e.g. MYSERVER in the figure), the Hardware Monitor displays a visual representation of the presence and functional status of CSS module components in the Control pane. Each primary hardware element functional status indicator is a clickable hotspot leading directly to the detailed Hardware Status page.

  • Page 137: Viewing Detailed Hardware Information

    Viewing Detailed Hardware Information For detailed information about module / component / sub–component status, you can either click the corresponding hotspot in the Hardware Monitor Control pane or click the required hardware element in the PAM Tree to open the Hardware Status page. General Tab The General tab gives access to the following information: Indicates if the hardware element is physcially present and correctly...

  • Page 138: Fru Info Tab

    Failure Status Indicators: Indicator Status Explanation PAM software has detected no failures on this hardware PAM software has detected no failures on this hardware NORMAL NORMAL element. element. Green PAM software has detected that this hardware element DEGRADED DEGRADED is running at sub–standard capacity but is not is running at sub–standard capacity but is not Orange jeopardizing system performance.

  • Page 139: Firmware Tab (Core Mfl & Pmb Only)

    Firmware Tab (Core MFL & PMB only) The Firmware tab gives access to firmware version data for the hardware element. Note: Firmware versions may differ. Figure 80. Firmware data (example) Thermal Zones (CSS module only) Thermal Zones, accessible via the Thermal zones tab, shows the thermal zones monitored by PAM software.

  • Page 140: Power Tab

    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 Indicator, on page 4-7. Once connected to the Customer’s site power supply, server hardware elements initialize to the stand–by mode.

  • Page 141: Css Module Power Tab

    CSS Module Power Tab The Power tab gives access to power status data for the CSS module DPS units. 48V Presence Meaning At least 1 DPS unit is ON. PRESENT All DPS units are OFF. ABSENT PAM software cannot read CSS module power status. Not Found 48V Value Current intensity in Amperes (varies according to configuration).

  • Page 142: Temperature Tab

    Temperature Tab The Temperature tab gives access to temperature status data for the hardware element, indicating overtemperature or temperature–specific faults. Figure 84. Temperature probe status details (example) Indicator Status Explanation Hardware element temperature is normal. NORMAL Green PAM software has detected a rise in temperature on this WARNING WARNING hardware element, but it is still operational and is not...

  • Page 143: Fan Status (Fanboxes Only)

    Fan Status (Fanboxes only) Fan Status, accessible via the Fans tab, indicates fan status, speed and supply voltage. See Functional Status Indicator , on page 4-7. During normal operation, the display depicts fan rotation. Each fanbox is equipped with 2 hot–swap, redundant, automatically controlled fans. Note: If all fans are halted in the display, check that your browser allows you to play animations in Web pages.

  • Page 144: Pci Slots (Ioc Only)

    PCI Slots (IOC only) PCI Slot Status, accessible via the PCI Slots tab, shows PCI board type and the functional and power status of PCI slots at the last domain power–on. When a fault is detected on a PCI slot, a fault message is generated and an IOC Faults List button gives direct access to the list of faults recently encountered on the IOC.

  • Page 145: Excluding / Including Hardware Elements

    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. The Exclusion / Inclusion function can also be used to logically limit access to certain hardware resources, such as system disks.

  • Page 146: Figure 90. Example Hardware Status Page

    Note: If you want to check domain hardware status, click Domain Manager → Resources → More info... to open the Domain Hardware Details page. Hardware elements to be logically excluded at the next domain power ON are marked with a green icon in the Excluded State column.
  • Page 147 Hardware Exclusion Guidelines Hardware Element Exclusion Guidelines IMPORTANT: If the following hardware elements are excluded, the corresponding server domain will not power up: • Master IOC • Master IOC HubLink 1 • Master IOC PCI Slots 1 & 2 • Master IOL Note: When a domain comprises more than one cell (therefore more than one IOC), the Master IOC is the one hosting the boot disk.

  • Page 148: Viewing And Managing Pam Event Messages And History Files

    • e–mail (non–connected recipients – Customer Administrator / Operator / other) • SNMP traps (non–connected recipients – Customer Administrator / Operator / other), • an autocall to the Bull Service Center (according to your maintenance contract). Note: Subscriptions can be customized to suit your working environment. For further details, see Customizing the PAM Event Messaging System, on page 5-85.

  • Page 149: Understanding Message Severity Levels

    Understanding Message Severity Levels Messages are graded into four severity levels as shown in the following table. Icon Severity Level Explanation SUCCESS An action requested by a user has been performed correctly or a function has been completed successfully. Information message, for guidance only. INFORMATION System operation is normal, but status has changed.

  • Page 150: Consulting Event Messages, Hardware Faults And History/Archive Files

    Consulting Event Messages, Hardware Faults and History/Archive 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 Button Acknowledge selected events To remove viewed messages from the pending event list. Select all events To select all Ack checkboxes.

  • Page 151: Viewing And Acknowledging Pam Web Event Messages

    Specimen Message Help File The Help File explains the message and indicates related actions, where applicable, as shown in Figure 92. Figure 92. Specimen message help file 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.

  • Page 152: Sorting And Locating Messages

    To acknowledge Web event messages: 1. Select the required checkbox(es) in the Ack column or click Select all events to automatically select all checkboxes in the Ack column. 2. Click Acknowledge selected events. Acknowledged messages are removed from the pending event list and are no longer accessible via the Status pane.

  • Page 153: Viewing, Archiving And Deleting History Files

    Viewing, Archiving and Deleting History Files History and archive files are systematically stored in the PAMSiteData directory: <WinDrive>:\Program Files\BULL\PAM\PAMSiteData\<DataCompatibilityRelease> The PAM History Manager allows you to view, archive and delete history files online and provides you with the tools required to download and view history and archive files offline.
  • Page 154 Viewing History Properties To view history properties: 1. From the PAM Tree pane, click History Manager to open the Control pane. 2. Select the Histories tab. 3. Highlight the required type of history and click Properties. The History Properties dialog opens. Name History name.

  • Page 155: Manually Archiving History Files

    Manually Archiving History Files In general, history files are automatically archived at regular periods. However, you can choose to manually archive a history file at any time, if required. Note: Empty history files cannot be archived. To manually archive a history file: 1.
  • Page 156 4. Select the message you want to view in detail. The resulting display is the same as for event messages. See Table 91 Display Events list, on page 4-26. Viewing Archive Properties To view archive properties: 1. From the PAM Tree pane, click History Manager to open the Control pane. 2.

  • Page 157: Manually Deleting A History Archive File

    Manually Deleting a History Archive File In general, history archive files are automatically deleted at regular periods. However, you can choose to manually archive a history archive file at any time, if required. To manually delete a history archive file: 1.
  • Page 158 Viewing History / Archive Files Offline 1. Click the HistoryViewer.htm file to open the View History File page. 2. Complete the History File Name field and click Read, or click Browse to search for and load the required history or archive file. 3.

  • Page 159: What To Do If An Incident Occurs

    • Event Message / History file, • e–mail / SNMP traps (users with an appropriate Event Message subscription), • an Autocall to the Bull Service Center (according to your maintenance contract). In most cases, PAM software handles the incident and ensures operational continuity while the Bull Service Center analyzes the incident and implements the necessary corrective or preventive maintenance measures.

  • Page 160: Table 27. Css Functional Status / Domain State

    – If the domain is operating normally, RUNNING is displayed in the Domain State field. – If the domain has been automatically powered down, INACTIVE is displayed in the Domain State field. See Table 27. System Functional Status / Expected Domain State, on page 4-36 and Chapter 3.
  • Page 161 7. Click Display Faults List for direct access to server logs. If the Display Faults List button is not accessible, click History Manager → System → PAM History for the corresponding log. See Displaying Detailed Hardware Status, on page 4-13. 8.

  • Page 162: Dealing With Incidents

    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. This section explains how to respond to the following requests: • Check Environmental Conditions •...

  • Page 163: Checking Hardware Connections

    Checking Hardware Connections If you are requested to check hardware connections, use Cabling Diagrams to manually and visually ensure that all cables are correctly inserted in their corresponding hardware ports. 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.

  • Page 164: Checking Snmp Settings

    Checking SNMP Settings If you are requested to check SNMP settings, IP address, or server name for an event subscription: 1. From the PAM Tree, click Configuration Tasks → Events → Channels and check that the SNMP Channel is enabled. 2.

  • Page 165: Modifying Lun Properties

    Modifying LUN Properties If you are requested to modify LUN properties: • Refer to Configuring SCSI Data Disks, on page 5-5 and to the appropriate Disk Subsystem documentation. • Refer to Configuring FDA Data Disks, on page 5-8 and to the appropriate Disk Subsystem documentation.

  • Page 166: Pmb Leds And Code Wheels

    PMB LEDs and Code Wheels Up to 16 Central Subsystems can be linked, via Platform Management Boards (PMBs) to a single PAP unit, to provide a single point of administration and maintenance. Each PMB is equipped with two code wheels used to identify each Central Subsystem and each CSS module in your configuration.

  • Page 167: Chapter 5. Tips And Features For Administrators

    For further information about user accounts and passwords, see Setting up PAP Unit Users, on page 5-21. Important: Certain domain configuration and management tools are reserved for use with partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Tips and Features for Administrators...
  • Page 168 User’s Guide...

  • Page 169: Section I - Setting Up Server Users And Configuring Data Disks

    Section I – Setting up Server Users and Configuring Data Disks This section explains how to: • Set up Server Users, on page 5-4 • Configure SR–0812 SCSI RAID and SR–1422 SCSI RAID Data Disks, on page 5-5 • Configure FDA 1x00 FC and FDA 2x00 FC Data Disks, on page 5-8 Tips and Features for Administrators...

  • Page 170: Setting Up Server Users

    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.

  • Page 171: Configuring Scsi Data Disks

    Configuring SCSI Data Disks Optionally, for optimum storage, security and performance, the server may be delivered with pre–configured disk racks. The addition of data disks involves the creation of a new array and new array partitions (LUNs) via the embedded Disk Array Administrator software. Note: Delivered storage sub–systems vary according to Customer requirements.

  • Page 172: Sr-0812 Scsi Raid Disk Rack

    SR–0812 SCSI RAID Disk Rack Optionally, the server may be delivered with two SR–0812 SCSI RAID disk racks (one per domain). Each disk rack contains two RAID #1 system disks and one pool spare disk, and offering five free slots for data disks. OS Disks (RAID #1) Spare Disk SR–0812 SCSI RAID disk rack 1...

  • Page 173: Creating A New Array Partition

    8. Select Array parameters. 9. Select the required number of free drives: Free Slots (population order) SJ–0812 SCSI JBOD disk rack SR–0812 SCSI RAID disk rack Ch 2 Id 03 Ch 2 Id 04 Ch 1 Id 01 Ch 1 Id 02 Ch 1 Id 03 Table 29.

  • Page 174: Configuring Fc Data Disks

    Configuring FC Data Disks FDA 1x00 FC Disk Rack Optionally, the server may be delivered with one or two FDA 1x00 FC disk rack(s) each containing two RAID #1 system disks per domain and one pool spare disk, and offering ten free slots for data disks.

  • Page 175: Creating A New Logical Data Disk

    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 desktop on the PAP unit, launch iSM Client. Figure 100. iSM Client interface 2.
  • Page 176 . Disk Rack 1, Controller 1 for Cell 2 and Cell 3 (CSS Module_1, IOB_0, IOB_1) 12.Click OK. A confirmation dialog box opens. 13.Click Yes → OK to return to the LD Individual Bind/Unbind page and click Close. The new logical disk appears in the iSM Server tree. Note: For further details, refer to the appropriate Disk Subystem documentation.

  • Page 177: Section Ii - Using Efi Utilities

    Section II – Using EFI Utilities This section explains how to: • Use the EFI Boot Manager, on page 5-12 • Use the EFI Shell, on page 5-14 • Use the EFI to Set up and Configure a Network, on page 5-18 •...

  • Page 178: Using The Efi Boot Manager

    Using the EFI Boot Manager The EFI (Extensible Firmware Interface) Boot Manager allows you to control the server’s booting environment. From the Boot Manager, you can choose to invoke the Extensible Firmware Interface (EFI) Shell or to go to the Boot Option Maintenance Menu. To enter the EFI Boot Manager: 1.

  • Page 179: Table 31. Boot Option Maintenance Menu

    Boot Option Description Boot from a File This option searches all the EFI System Partitions in the system. For each partition it looks for an EFI directory. If the EFI directory is found, it looks in each of the subdirectories below EFI. In each of those subdirectories, it looks for the first file that is an execut- able EFI Application.

  • Page 180: Using The Efi Shell

    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.
  • Page 181 The Shell maintains a special variable, named lasterror. The variable contains the return code of the most recently executed Shell command. Wildcard Expansion The *, ? and [ characters can be used as wildcard characters in filename arguments to Shell commands. If an argument contains one or more of these characters, the Shell processes the argument for file meta–arguments and expands the argument list to include all filenames matching the pattern.

  • Page 182: Executing Batch Scripts

    not treated specially by the Shell in any way. Empty strings are treated as valid command line arguments. Executing Batch Scripts The EFI Shell has the capability of executing commands from a file (batch script). EFI Shell batch script files are named using the .nsh extension. Batch script files can be either UNICODE or ASCII format files.

  • Page 183: Table 34. List Of Efi Shell Commands

    Command Batch Description only alias Displays, creates, or deletes aliases in the EFI Shell attrib Displays or changes the attributes of files or directories bcfg Displays/modifies the driver/boot configuration break Executes a break point Displays or changes the current directory Clears the standard output with an optional background color comp Compares the contents of two files...

  • Page 184: Efi Network Setup And Configuration

    Note: These utilities are installed in the EFI partition of the system disk in the EFI\Tools directory. The list and respective manual pages for each utility can be found on the Bull NovaScale Server Resource CD–Rom. Network stack configuration commands must be executed after booting to EFI Shell. To simplify network setup, these commands should be grouped, via an EFI batch script, to form a single one–line command.

  • Page 185: File Transfer Protocol (Ftp)

    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).

  • Page 186: Section Iii - Customizing Pam Software

    Section III – Customizing PAM Software This section explains how to: • Set up PAP Unit Users, on page 5-21 • Modify Customer Information, on page 5-23 • Configure Autocalls, on page 5-24 • Customize PAM Settings, on page 5-26 •...

  • Page 187: Setting Up Pap Unit Users

    PAP Customer Administrator user group. For further details about user management, refer to the Microsoft Windows documentation on the Bull NovaScale Server System Resource CD. Note: You are advised to change the temporary Administrator password (administrator) used for setup purposes and to maintain a detailed record of authorized users.

  • Page 188: Table 35. User Access To Pam Features

    PAM Tools Associated Actions Load/delete domains Power on/off/reset domains View/modify domain settings View domain status View domain resources Domain Manager View BIOS info View BIOS version View loaded BIOS image View power logs View request logs Request a system dump View hardware functional/presence status View detailed hardware status information Use the hardware Search engine...

  • Page 189: Modifying Customer Information

    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.

  • Page 190: Configuring Autocalls

    Configuring Autocalls The Autocall feature is part of the BULL Remote Maintenance contract. It is used to automatically route system events to the Remote Maintenance Center. Full details are given in the BULL Remote Maintenance Guide. If your maintenance contract includes the Autocall feature, configure Autocall parameters as follows: 3.
  • Page 191 8. If FTP dispatch mode is selected, complete the FTP Settings fields with the following information: Field Explanation Value Server name Remote Maintenance Center server IP address 127.0.0.1 Server port Default server port Target directory Default server directory /autocall Login Declared authorized user name Password Declared authorized user password...

  • Page 192: Setting Thermal Units

    Setting Thermal Units By default, PAM software displays thermal measurements in degrees Celsius. As Customer Administrator, you may change the default setting to degrees Fahrenheit. To change PAM thermal units: 1. Click Configuration Tasks → PAM. The PAM Configuration control pane opens. 2.

  • Page 193: Deploying A New Pam Release

    3. Select Complete to install all program features and to accept the default path for the installation folder: <WinDrive>:\Program Files\BULL\PAM\installation\<Release Version> (e.g. d:\Program Files\BULL\PAM\installation\ 2.1.9 ). or, select Custom to select program features and to define a path for the installation folder.

  • Page 194: Activating A Pam Version

    The default PAM Release directory for all the files delivered as part of PAM software is: <WinDrive>:\Program Files\BULL\PAM\<Release Version> (e.g. d:\Program Files\BULLl\PAM\ 2.1.9 ). The default PAM Site Data directory for all the files produced by PAM software (history files, configuration files) concerning Customer site definition and activity is: <WinDrive>:\Program Files\BULL\PAM\PAMSiteData\<DataCompatibilityRelease>...
  • Page 195 4. Click Install to begin activation. 5. Select the Launch PAP Configuration utility checkbox if you want to configure or reconfigure PAP unit settings. Otherwise, click OK to complete activation. 6. From the local PAP unit console, right click the Microsoft Internet Explorer icon on the desktop and click Properties →...

  • Page 196: Backing Up And Restoring Pam Configuration Files

    PAM configuration data is automatically saved to the default PAM Site Data directory on the PAP unit: <WinDrive>:\Program Files\BULL\PAM\PAMSiteData\<DataCompatibilityRelease> To ensure carefree, reliable and regular configuration data backup, the Bull NovaScale Server Resource CD contains two scripts, PamBackupData.js and PamRestoreData.js, that can be scheduled to run via the Microsoft Windows Task Scheduler.
  • Page 197 Restoring PAM Configuration Data To restore PAM configuration data: 1. If required, install the same PAM software release on the backup PC as on the PAP unit. See Deploying a New PAM Release, on page 5-27 and Activating a PAM Version, on page 5-28.

  • Page 198: Section Iv - Configuring Domains

    This section describes domain configuration and management tools that are reserved for use with partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. This section explains how to: • Partition your Server, on page 5-33 •...

  • Page 199: Partitioning Your Server

    Partitioning your Server Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Bull NovaScale Servers are designed around a flexible, cell–based, midplane architecture allowing dynamic partitioning into physically independent domains. A domain is a coherent set of hardware and software resources managed by a single Operating System instance.
  • Page 200 A Domain Configuration Scheme is used to define and manage a set of domains that can be active simultaneously. The Schemes control pane allows you to create, edit, copy, delete, and rename domain configuration schemes and update default test schemes. A Domain Identity is used to define and manage domain context information.

  • Page 201: Assessing Configuration Requirements

    Assessing Configuration Requirements Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. At least one IOC and one QBB are required for each server domain. You can use the following checklist to help you make an accurate plan of how you want to partition and manage your system.

  • Page 202: Creating, Editing, Copying, Deleting, Renaming A Domain Configuration Scheme

    Creating, Editing, Copying, Deleting, Renaming a Domain Configuration Scheme Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Note: Domain Identities can either be created via the Domain Scheme wizard or, independently, via the Identities configuration page.

  • Page 203: Figure 108. Scheme Creation And Central Subsystem Configuration Dialogs

    NovaScale 6085 Server NovaScale 6165 Server Figure 108. Scheme Creation and Central Subsystem Configuration dialogs 5-37 Tips and Features for Administrators...

  • Page 204: Figure 109. Scheme Management Dialog

    6. Select a Central Subsystem and use the Number of Parts dropdown list to select the required number of hardware partitions (2 in the example). 7. Select the required partition configuration and click OK to return to the Scheme Management dialog. NovaScale 6085 Server NovaScale 6165 Server Figure 109.
  • Page 205 9. If the required identity is in the list, go to Step 10. If you want to create a new identity for this domain, click New to open the Create New Identity dialog. See Creating a Domain Identity, on page 5-42. 10.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog.

  • Page 206: Figure 110. Edit Scheme Dialog

    NovaScale 6085 Server NovaScale 6165 Server Central Subsystem Click here to add another Central Subsystem to your scheme. See Creating a Domain Configuration Scheme, on page 5-36. Remove Click here to remove a Central Subsystem from your scheme. Modify Click here to change the number of hardware partitions in your scheme. Domains Remove Click here to remove the selected domain from the scheme.

  • Page 207: Updating Test Schemes

    5. Make the required changes and click Save. The modified domain configuration scheme is now available for domain management. Copying a Domain Configuration Scheme To copy a domain configuration scheme: 1. Click Configuration Tasks → Domains → Schemes in the PAM tree to open the Schemes pane.

  • Page 208: Creating, Editing, Copying, Deleting A Domain Identity

    Creating, Editing, Copying, Deleting a Domain Identity Important: Reserved for partitioned servers and extended systems. Please contact your Bull Sales Representative for sales information. Note: Domain Identities can either be created via the Domain Configuration Scheme wizard or, independently, via the Identities configuration page. See Creating a Domain Configuration Scheme, on page 5-36.

  • Page 209: Figure 112. Create New Identity Dialog

    3. Click New in the toolbar to open the Create New Identity dialog. Figure 112. Create New Identity dialog 4. Complete the Name, Description, Domain Settings, and Management Parameters fields, as required. See Assessing Configuration Requirements, on page 5-35. 5. Click OK. The new identity appears in the Identities List page and can be applied to a hardware partition via the Domain Configuration Scheme wizard.
  • Page 210 Copying a Domain Identity To copy a domain identity: 1. Click Configuration Tasks → Domains → Identities in the PAM tree to open the Identities Management page. See Figure 111 above. 2. Select the required identity from the list. 3. Click Copy in the toolbar. The Copy Identity dialog opens. 4.

  • Page 211: Creating A Mono-Domain Scheme Using All Server Resources

    Scheme configuration criteria – example 1 – bi–module server Note: A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring Extended Systems, on page 5-76. 5-45 Tips and Features for Administrators...

  • Page 212: Figure 113. Scheme Creation Dialog - Example 1

    To create a mono–domain scheme using all server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2.

  • Page 213: Figure 114. Central Subsystem Configuration Dialog - Example 1

    5. Click Central Subsystem → Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens. NovaScale 6085 Server NovaScale 6165 Server Figure 114. Central Subsystem configuration dialog – example 1 5-47 Tips and Features for Administrators...

  • Page 214: Figure 115. Scheme Management Dialog - Example 1

    6. Check that the required Central Subsystem is highlighted and select 1 in the Number of Parts dropdown list. 7. Select the required partition configuration and click OK to return to the Scheme Management dialog. The Status icons are red because a Domain Identities are required to complete domain configuration.

  • Page 215: Figure 116. Identities List Dialog - Example 1

    NovaScale 6085 Server NovaScale 6165 Server Figure 116. Identities list dialog – example 1 9. If the required identity is in the list, go to Step 12. If you want to create a new identity for this domain, click New to open the Create New Identity dialog.

  • Page 216: Figure 117. Create New Identity Dialog - Example 1

    10.Complete the Name, Description, Domain Settings, and Management Parameters fields. Figure 117. Create new identity dialog – example 1 11. Click OK. The new identity appears in the Identities List dialog. 12.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog.

  • Page 217: Figure 118. Scheme Management Dialog - Example 1

    NovaScale 6085 Server NovaScale 6165 Server Figure 118. Scheme Management dialog – example 1 13.Check that the EFI Boot Lun for the domain is correct. If the EFI Boot Lun is correct, go to Step 14. If the EFI Boot Lun is not correct, double–click the EFI LUNs field. The LUN List dialog opens, allowing you to choose the required EFI Boot Lun from the list of available Luns 5-51 Tips and Features for Administrators...

  • Page 218: Figure 119. Lun List Dialog - Example 1

    NovaScale 6085 Server NovaScale 6165 Server Figure 119. Lun list dialog – example 1 14.Select the required EFI Boot Lun from the list of available Luns and click OK to return to the Scheme Management dialog. 15.Click Save. The domain configuration scheme is now available for domain management. 5-52 User’s Guide...

  • Page 219: Creating A Mono-Domain Scheme Using A Part Of Server Resources

    Creating a Mono–Domain Scheme using a Part of Server Resources The configuration criteria set out in the following tables is used to illustrate this example. NovaScale 6085 Server Scheme Name MyOffpeakProdScheme Description Mono–domain, Cell 1, Boot 0Lun1, MyOffpeakProd Central Subsystem(s) MyServer Number of domains Domain size...

  • Page 220: Figure 120. Scheme Creation Dialog - Example 2

    Note: A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring Extended Systems, on page 5-76. To create a mono–domain scheme using a part of server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...).

  • Page 221: Figure 121. Central Subsystem Configuration Dialog - Example 2

    NovaScale 6085 Server NovaScale 6165 Server Figure 121. Central Subsystem configuration dialog – example 2 6. Check that the required Central Subsystem is highlighted and select 2 (mono–module server) or 4 (bi–module server) in the Number of Parts dropdown list. 5-55 Tips and Features for Administrators...

  • Page 222: Figure 122. Remove Domain Confirmation Dialog - Example 2

    7. Select the required partition configuration and click OK to return to the Scheme Management dialog. 8. As you want this scheme to only use Cell 1, you must remove the domains using the other cells. Hover the mouse over the cells represented in the CellBlocks diagram to identify the domain using Cell 1.

  • Page 223: Figure 123. Scheme Management Dialog - Example 2

    10.Repeat Step 11 for D3 and D4, where applicable. 12.Now, only one domain appears in the Scheme Management dialog. The Status icon is red because a Domain Identity is required to complete domain configuration. NovaScale 6085 Server NovaScale 6165 Server Figure 123.

  • Page 224: Figure 124. Identities List Dialog - Example 2

    NovaScale 6085 Server NovaScale 6165 Server Figure 124. Identities list dialog – example 2 14.If the required identity is in the list, go to Step 17. If you want to create a new identity for this domain, click New to open the Create New Identity dialog.

  • Page 225: Figure 125. Create New Identity Dialog - Example 2

    15.Complete the Name, Description, Domain Settings, and Management Parameters fields. Figure 125. Create new identity dialog – example 2 16.Click OK. The new identity appears in the Identities List dialog. 17.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog.

  • Page 226: Figure 126. Scheme Management Dialog - Example 2

    NovaScale 6085 Server NovaScale 6165 Server Figure 126. Scheme Management dialog – example 2 18.Check that the EFI Boot Lun for the domain is correct and click Save. The domain configuration scheme is now available for domain management. 5-60 User’s Guide...

  • Page 227: Creating A Multi-Domain Scheme Using All Server Resources

    Creating a Multi–Domain Scheme using all Server Resources The configuration criteria set out in the following tables is used to illustrate this example. NovaScale 6085 Server Scheme Name MyProd_PayrollScheme Description Multi–domain, Cells 0 & 1, Boot 0Lun0 & 0Lun1 MyProduction & MyPayroll Central Subsystem(s) MyServer Number of domains...
  • Page 228 Scheme configuration criteria – example 3 – bi–module server Note: A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring Extended Systems, on page 5-76. 5-62 User’s Guide...

  • Page 229: Figure 127. Scheme Creation Dialog - Example 3

    To create a multi–domain scheme using all server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2.

  • Page 230: Figure 128. Central Subsystem Configuration Dialog - Example 3

    5. Click Central Subsystem → Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens. NovaScale 6085 Server NovaScale 6165 Server Figure 128. Central Subsystem configuration dialog – example 3 5-64 User’s Guide...

  • Page 231: Figure 129. Scheme Management Dialog - Example 3

    6. Check that the required Central Subsystem is highlighted and select 2 in the Number of Parts dropdown list. 7. Select the required partition configuration and click OK to return to the Scheme Management dialog. The Status icons are red because Domain Identities are required to complete domain configuration.

  • Page 232: Figure 130. Identities List Dialog - Example 3

    8. Double–click the empty D1 Identities field. The Identities List dialog opens. NovaScale 6085 Server NovaScale 6165 Server Figure 130. Identities list dialog – example 3 9. If the required identity is in the list, go to Step 12. To create a new identity for this domain, click New to open the Create New Identity dialog.

  • Page 233: Figure 131. Create New Identity Dialog - Example 3

    10.Complete the Name, Description, Domain Settings, and Management Parameters fields for Domain Identity D1. Figure 131. Create new identity dialog – example 3 11. Click OK. The new identity appears in the Identities List dialog. 12.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog.

  • Page 234: Figure 132. Scheme Management Dialog - Example 3

    NovaScale 6085 Server NovaScale 6165 Server Figure 132. Scheme management dialog – example 3 14.Click Save. The domain configuration scheme is now available for domain management. 5-68 User’s Guide...

  • Page 235: Creating A Multi-Domain Scheme Using A Part Of Server Resources

    Scheme configuration criteria – example 4 – bi–module server Note: A domain configuration scheme can include more than one Central Subsystems. If you have more than one Bull NovaScale Server, see Configuring Extended Systems, on page 5-76. 5-69 Tips and Features for Administrators...

  • Page 236: Figure 133. Scheme Creation Dialog - Example 4

    To create a multi–domain scheme using a part of server resources: 1. Check that the required hardware resources are available (at least one IOC and one QBB are required for each server domain) and that the domain Operating System supports the required hardware resources (CPUs, DIMMs, ...). 2.

  • Page 237: Figure 134. Central Subsystem Configuration Dialog - Example 4

    5. Click Central Subsystem → Add to select the Central Subsystem to be used by the domain configuration scheme. The Central Subsystem Configuration dialog opens. Figure 134. Central Subsystem configuration dialog – example 4 6. Check that the required Central Subsystem is highlighted and select 3 in the Number of Parts dropdown list.

  • Page 238: Figure 135. Scheme Management Dialog - Example 4

    The Status icons are red because Domain Identities are required to complete domain configuration. Figure 135. Scheme Management dialog – example 4 8. As you want this scheme to only use Cells 1, 2 and 3, you must remove the domain using Cell 0.

  • Page 239: Figure 137. Scheme Management Dialog - Example 4

    10.Now, only two domains appear in the Scheme Management dialog. The Status icons are red because Domain Identities are required to complete domain configuration. Figure 137. Scheme Management dialog – example 4 5-73 Tips and Features for Administrators...

  • Page 240: Figure 138. Identities List Dialog - Example 4

    11. Double–click the empty D1 Identities field. The Identities List dialog opens. Figure 138. Identities list dialog – example 4 12.f the required identity is in the list, go to Step 15. To create a new identity for this domain, click New to open the Create New Identity dialog.

  • Page 241: Figure 140. Scheme Management Dialog - Example 4

    15.Select the required identity from the list of available identities and click OK to return to the Scheme Management dialog. The corresponding Status icon turns green. 16.Repeat Steps 11 to 15 for Domain Identity D2. The scheme is now completely configured.

  • Page 242: Configuring And Managing Extended Systems

    Configuring and Managing Extended Systems A single PAP unit can administer, monitor, and manage several Central Subsystems. The PAM Domain Configuration Scheme Wizard allows easy configuration of extended systems. Please contact your BULL Customer Sales Representative for details. 5-76 User’s Guide...

  • Page 243: Clearing, Loading, Saving Nvram Variables

    Clearing, Loading, Saving NVRAM Variables NVRAM variables are available for each LUN. According to requirements, these variables can be cleared, saved and/or loaded. Note: NVRAM variables can only be saved when the corresponding domain is active. To clear, save and/or load NVRAM variables: 1.

  • Page 244: Updating The Lun List

    2. Select the required LUN from the list of available LUNs and click NVRAM. The NVRAM Variables dialog opens: a. Click Clear to clear displayed NVRAM variables. When requested, click OK to confirm. b. Click Save to save NVRAM variables for the selected LUN (currently used by an active domain).

  • Page 245: Limiting Access To Hardware Resources

    Limiting Access to Hardware Resources As Customer Administrator, you can use the PAM software Exclusion / Inclusion function to logically limit access to certain hardware resources, such as: IOCs When a domain comprises more than one cell (therefore more than one IOC), the Master IOC is the one hosting the boot disk.

  • Page 246: Scheme, Domain Identity, And Resources Checklists

    Scheme, Domain Identity, and Resources Checklists Important: At least one QBB and one IO box is required for each server domain. Scheme Checklist Name What name do I want to use for my Scheme? Description How can I describe my Scheme to reflect its scope? Central Subsystem(s) Which Central Subsystem(s) do I want to use? Number of domains...
  • Page 247 Domain Identity Checklist Name What name do I want to use for my Domain Identity to reflect the tasks/jobs it will run? Description How can I describe my Domain Identity to reflect its use? Operating System Which OS do I want to run on this domain? Will this OS sup- port assigned hardware (CPUs, DIMMs)? Domain network name Which network name will be used to identify this domain?

  • Page 248: Table 46. Resources Checklist - Part

    Resources Checklist Central Subsystem: Cell 0 Cell 1 QBBs QBBs QBB0 QBB0 QBBs QBBs QBB1 QBB1 IO Box IO Box IOC0 IOC1 EFI Boot Lun 0Lu0 EFI Boot Lun 0Lu1 OS instance OS instance I/O Resources I/O Resources IOC0_Slot 1 IOC1_Slot 1 IOC0_Slot 2 IOC1_Slot 2...

  • Page 249: Table 47. Resources Checklist - Part

    Resources Checklist Cell 2 Cell 3 QBBs QBBs QBB0 QBB0 QBBs QBBs QBB1 QBB1 IO Box IO Box IOC0 IOC1 EFI Boot Lun 1Lu0 EFI Boot Lun 1Lu1 OS instance OS instance I/O Resources I/O Resources IOC0_Slot 1 IOC1_Slot 1 IOC0_Slot 2 IOC1_Slot 2 IOC0_Slot 3...

  • Page 250: Section V - Creating Event Subscriptions And User Histories

    Section V – Creating Event Subscriptions and User Histories This section explains how to: • Customize the PAM Event Messaging System, on page 5-85 • Set up Event Subscriptions, on page 5-86 • Create, Edit, Delete an E–mail Server, on page 5-88 •...

  • Page 251: Customizing The Pam Event Messaging System

    Customizing the PAM Event Messaging System During operation, all Central Subsystem activity messages are automatically logged in predefined System Histories that can be viewed and archived by members of the Customer Administrator group. In addition, PAM software reports and logs environmental, command, and hardware errors.

  • Page 252: Setting Up Event Subscriptions

    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.

  • Page 253: Event Subscription Flowcharts

    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-110, or Create an Event Filter, on page 5-111.

  • Page 254: Creating, Editing, Deleting An E-Mail Server

    Creating, Editing, Deleting an E–mail Server To send messages via the e–mail channel, you must first create an e–mail server. Several e–mail accounts can then be attached to the same e–mail server, see Creating an E–mail Account, on page 5-90. Creating an E–mail Server To create an e–mail server: 1.
  • Page 255 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 144 above. 2. Select the required server from the e–mail servers list. 3.

  • Page 256: Creating, Editing, Deleting An E-Mail Account

    Creating, Editing, Deleting an E–mail Account To send messages via the e–mail channel, you must first create an e–mail server and then attach an e–mail address to this e–mail server. Several e–mail accounts can be attached to the same e–mail server. Creating an E–mail Account To create an e–mail account: 1.
  • Page 257 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 145 above. 2. Select the required account from the e–mail accounts list. 3.

  • Page 258: Creating, Editing, Deleting A User History

    Creating, Editing, Deleting a User History There are two types of histories: System histories and User histories. System histories cannot be modified and are are only accessible to members of the Customer Administrator group. User histories can be created, edited and deleted and are accessible to members of both the Customer Administrator and Customer Operator groups.

  • Page 259: Figure 146. Create A New User History Dialog

    Creating a User History Note: The Site Data Directory will be used, by default, if you do not specify a different directory when you create a user history.See Viewing PAM Version Information, on page 4-11 To create a user history: 1.
  • Page 260 5. Use the drop–down menu to select an automatic archiving policy Type: Type Automatic Archiving Policy Number of Days The system will automatically create an archive for this history after the number of days specified in the Value field. Size in KBytes The system will automatically create an archive when this history reaches the size in KBytes specified in the Value field.
  • Page 261 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-99 to attach these event subscriptions to another history, or •...

  • Page 262: Enabling / Disabling Event Channels

    Enabling / Disabling Event Channels An event channel must be selected and enabled for all event subscriptions. The following table provides the Customer Administrator with guidelines for selecting an event channel. Channel Target Enabled Disabled Allows a specific re- cipient to directly re- EMAIL Specific recipient.

  • Page 263: Figure 147. Event Channels Configuration Page

    Figure 147. Event Channels configuration page 2. Select the Yes or No radio button in the Enable column to enable or disable the required channel. 3. Click the Save icon to confirm the new configuration. 5-97 Tips and Features for Administrators...

  • Page 264: Creating, Editing, Deleting An Event Subscription

    Creating, Editing, Deleting an Event Subscription Once event subscription prerequisites have been set up, you can create the event subscriptions required to send messages to their destinations. See Event Subscription Flowcharts, on page 5-87. Creating an Event Subscription To create an event subscription: 1.
  • Page 265 8. Click OK to confirm the creation of the new event subscription. 9. The event subscription configuration page is automatically updated with the new subscription. 10.Click Test Subscription to check that the event subscription has been configured correctly. Subscription parameters will be used to send a test message. Note: The OK button is accessible once all mandatory fields have been completed.

  • Page 266: Understanding Event Message Filtering Criteria

    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.

  • Page 267: Figure 150. Event Message Advanced Filtering Criteria Chart

    3. Click Advanced to display the Advanced Filter page. Figure 150. Event message advanced filtering criteria chart 4. Carefully analyze Tables 52 and 53 to understand the various options. 5-101 Tips and Features for Administrators...

  • Page 268: Standard Event Message Filtering Criteria

    Standard Event Message Filtering Criteria Criteria Description S (Select) All the checkboxes in this column are selected by default. When an event message S checkbox is deselected, the event message is re- moved from the filter. Actions – Select the S checkbox if you want to include the event message in the new filter.
  • Page 269 Criteria Description Duration 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 auto- matically. Note: The PAM Web interface stores up to 150 event messages maximum per user group (100 by default).

  • Page 270: Table 52. Standard Event Message Filtering Criteria

    Criteria Description Severity Level 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. –...

  • Page 271: Advanced Event Message Filtering Criteria

    Advanced Event Message Filtering Criteria Note: Advanced filtering criteria are reserved for advanced users and are to be used with care. Criteria Description Thresholding 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.
  • Page 272 Criteria Description Clipping 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.
  • Page 273 Criteria Description Source Each event message refers to a source (the component that gener- ated 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.
  • Page 274 Criteria Description Target Each event message refers to a target (the component referred to in the message) and a source (the component that generated the mes- sage) (see above). This feature allows messages to be filtered ac- cording to one or more Target string(s) and is particularly useful for debugging and troubleshooting.

  • Page 275: Table 53. Advanced Event Message Filtering Criteria

    Criteria Description Keyword 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. –...

  • Page 276: Preselecting, Creating, Editing, Deleting An Event Filter

    Preselecting, Creating, Editing, Deleting an Event Filter An event filter must be selected for all event subscriptions. The event messaging system is delivered with a set of predefined filters. Preselecting an Event Filter Before proceeding to set up an event subscription, you are advised to check which predefined filter is adapted to your needs: 1.

  • Page 277: Figure 152. New Filter Configuration Page - Standard Event Message Filtering Criteria Table

    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.

  • Page 278: Figure 153. New Filter Configuration Page - Advanced Event Message Filtering Criteria Table

    7. If required, click Advanced to access advanced filtering criteria. The advanced event message filtering criteria chart is displayed. Figure 153. New Filter configuration page – advanced event message filtering criteria table 8. When you have finished configuring your event filter, click Create. 9.

  • Page 279: Appendix A. Specifications

    Appendix A. Specifications • NovaScale 5085 server specifications, on page A-2 • NovaScale 5165 server specifications, on page A-4 • NovaScale 6085 server specifications, on page A-6 • NovaScale 6165 server specifications, on page A-8 Server Specifications...

  • Page 280: Novascale 5085 Server Specifications

    NovaScale 5085 Server Specifications NovaScale 5085 Servers are delivered rack–mounted in 40U or 19U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. 40U Cabinet Dimensions / Weight Unpacked Packed Height: Height: 195.5 cm (77.0 in) 195.5 cm (77.0 in)

  • Page 281: Table 54. Novascale 5085 Server Specifications

    ° ° Acoustic Power at Room Temperature +20 C (+68 System Running System Idle Lw(A) 6.3 Bels Lw(A) 6.1 Bels Power Cables PDU–2–4–M–32A AC (32A) 1 par PDU Cable type 3 x AWG10 Connector type IEC60309–32A It is mandatory for power lines and terminal boxes to be located within the imme- diate vicinity of the system and to be easily accessible.

  • Page 282: Novascale 5165 Server Specifications

    NovaScale 5165 Server Specifications The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. 40U Cabinet Dimensions / Weight Unpacked Packed Height: 192 cm (75.1 in) Height: 192 cm (75.1 in) Height: 202 cm (79.5 in) Height: 202 cm (79.5 in) Width: 60 cm (23.6 in)

  • Page 283: Table 55. Novascale 5165 Server Specifications

    Lw(A) 6.3 Bels Lw(A) 6.1 Bels Power Cables AC (20A) 1 per PDU Cable type 3 x 4mm@ / AWG # 12 (US) Connector type C22 Appliance Coupler It is mandatory for power lines and terminal boxes to be located within the imme- diate vicinity of the system and to be easily accessible.

  • Page 284: Novascale 6085 Server Specifications

    NovaScale 6085 Server Specifications NovaScale 6085 Servers are delivered rack–mounted in 40U or 19U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. 40U Cabinet Dimensions / Weight Unpacked Packed Height: Height: 195.5 cm (77.0 in) 195.5 cm (77.0 in)

  • Page 285: Table 56. Novascale 6085 Server Specifications

    ° ° Acoustic Power at Room Temperature +20 C (+68 System Running System Idle Lw(A) 6.3 Bels Lw(A) 6.1 Bels Power Cables PDU–2–4–M–32A AC (32A) 1 par PDU Cable type 3 x AWG10 Connector type IEC60309–32A It is mandatory for power lines and terminal boxes to be located within the imme- diate vicinity of the system and to be easily accessible.

  • Page 286: Novascale 6165 Server Specifications

    NovaScale 6165 Server Specifications NovaScale 6165 Servers are delivered rack–mounted in 40U or 19U cabinets. The following web site may be consulted for general site preparation information: http://www.cs.bull.net/aise. 40U Cabinet Dimensions / Weight Unpacked Packed Height: Height: 195.5 cm (77.0 in) 195.5 cm (77.0 in)

  • Page 287: Table 57. Novascale 6165 Server Specifications

    ° ° Acoustic Power at Room Temperature +20 C (+68 System Running System Idle Lw(A) 6.3 Bels Lw(A) 6.1 Bels Power Cables PDU–2–4–M–32A AC (32A) 1 par PDU Cable type 3 x AWG10 Connector type IEC60309–32A It is mandatory for power lines and terminal boxes to be located within the imme- diate vicinity of the system and to be easily accessible.
  • Page 288 A-10 User’s Guide...

  • Page 289: Appendix B. Cabling Diagrams

    Appendix B. Cabling Diagrams NovaScale 5085 Server Internal disk configuration, on page B-3. External Disk configuration, on page B-4: SJ–0812 SCSI JBOD disk configuration, on page B-4. SR–0812 SCSI RAID disk configuration, on page B-4. Extension disk rack (SJ–0812 SCSI JBOD – SR–0812 SCSI RAID), on page B-5. FDA 1x00 FC disk configuration, on page B-5.
  • Page 290 NovaScale 6165 Server Internal disk configuration, on page B-16. External Disk configuration, on page B-18: SJ–0812 SCSI JBOD disk configuration, on page B-18. SR–0812 SCSI RAID disk configuration, on page B-19. Extension disk rack (SJ–0812 SCSI JBOD – SR–0812 SCSI RAID), on page B-20. FDA 1x00 FC disk configuration, on page B-21.

  • Page 291: Novascale 5085 Server Data Cabling Diagram

    NovaScale 5085 Server Data Cabling Diagram Internal Disk Configuration Mark Cable Type From Video/PS2/PS2 cable KVM (video) Console (video) PS2/USB converter KVM (USB) Console (PS2/PS2) Combined PS2/VGA cable KVM Port 1 PAP (VGA/PS2) Combined USB/VGA cable KVM Port 2 IOL (Video/USB) RJ45 –...

  • Page 292: Figure 155. Sj-0812 Scsi Jbod Disk Rack Data Cabling Diagram

    External Disk Configuration SJ–0812 SCSI JBOD Disk Ra Mark Cable Type From SCSI–3 68–pin HBA SCSI RAID S/S Disk 1 VHDCI to VHDCI cable (IOC0) Extension port Figure 155. SJ–0812 SCSI JBOD disk rack data cabling diagram SR–0812 SCSI RAID Disk Ra Mark Cable Type From...

  • Page 293: Figure 157. Sj-0812 Scsi Jbod Extension Disk Rack Data Cabling Diagram

    Extension Disk Rack (SJ–0812 SCSI JBOD – SR–0812 SCSI RAID) Mark Cable Type From SCSI–3 68–pin SR–0812 SCSI RAID SJ–0812 SCSI JBOD VHDCI to VHDCI cable extension port extension port Figure 157. SJ–0812 SCSI JBOD extension disk rack data cabling diagram Disk Rack (FDA 1x00 FC) Mark Cable Type...

  • Page 294: Figure 159. Fda 1X00 Fc - Fda 1X00 Fc Extension Disk Rack Data Cabling Diagram

    Extension Disk Rack (FDA 1x00 FC – FDA 1x00 FC) Mark Cable Type From HSSDC–HSSDC cable S/S Disk S/S Disk Extension DE diagnosis cable S/S Disk S/S Disk Extension Figure 159. FDA 1x00 FC – FDA 1x00 FC extension disk rack data cabling diagram User’s Guide...

  • Page 295: Novascale 6085 Server Data Cabling Diagram

    NovaScale 6085 Server Data Cabling Diagram Internal Disk Configuration Mark Cable Type From Video/PS2/PS2 cable KVM (video) Console (video) PS2/USB converter KVM (USB) Console (PS2/PS2) Combined PS2/VGA cable KVM Port 1 PAP (VGA/PS2) Combined USB/VGA cable KVM Port 2 IOL#0 (Video/USB) Combined USB/VGA cable KVM Port 3 IOL#1 (Video/USB)

  • Page 296: External Disk Configuration

    External Disk Configuration SJ–0812 SCSI JBOD Disk Ra Mark Cable Type From SCSI–3 68–pin HBA SCSI RAID S/S Disk 1 VHDCI to VHDCI cable (IOC0) Extension port SCSI–3 68–pin HBA SCSI RAID S/S Disk 2 VHDCI to VHDCI cable (IOC1) Extension port Figure 161.

  • Page 297: Figure 163. Sj-0812 Scsi Jbod Extension Disk Rack Data Cabling Diagram

    Extension Disk Rack (SJ–0812 SCSI JBOD – SR–0812 SCSI RAID) Mark Cable Type From SCSI–3 68–pin SR–0812 SCSI RAID SJ–0812 SCSI JBOD VHDCI to VHDCI cable extension port extension port Figure 163. SJ–0812 SCSI JBOD extension disk rack data cabling diagram Disk Rack (FDA 1x00 FC) Mark Cable Type...

  • Page 298: Extension Disk Rack (Fda 1X00 Fc - Fda 1X00 Fc

    Extension Disk Rack (FDA 1x00 FC – FDA 1x00 FC) Mark Cable Type From HSSDC–HSSDC cable S/S Disk S/S Disk Extension DE diagnosis cable S/S Disk S/S Disk Extension Figure 165. FDA 1x00 FC – FDA 1x00 FC extension disk rack data cabling diagram B-10 User’s Guide...

  • Page 299: Power Cabling Diagram

    Power Cabling Diagram All power supply cables are connected to the internal PDU(s), as shown below: Internal Disk configuration Console Drawer KVM Switch PAP Unit CSS Module Mains Mark Cable Type From Power cable Console PDU J6 Power cable KVM switch PDU J5 Power cable PAP Pwr...

  • Page 300: Novascale 5165 Server Data Cabling Diagrams

    NovaScale 5165 Server Data Cabling Diagrams Internal Disk Configuration B-12 User’s Guide...

  • Page 301: External Disk Configuration

    Mark Cable Type From video/PS2/PS2 cable Console KVM switch USB cable PAP USB Modem USB RJ11 – RJ11 cable Modem (Line) Telephone network socket RJ45 – RJ45 Ethernet cable PAP (VGA and PS2) KVM Port 1 via AVRIQ (4) RJ45/RJ45 cable IOL Module 0 KVM Port 3 VGA and USB...

  • Page 302: Figure 169. Sr-0812 Scsi Raid Disk Rack Data Cabling Diagram

    SR–0812 SCSI RAID Disk Ra Mark Cable Type From DB9 to Jack cable (optional) Nport server S/S Disk (1) RS232 SCSI–3 68–pin HBA SCSI S/S Disk (1) Host port VHDCI to VHDCI cable (IOC0 Module 0) Figure 169. SR–0812 SCSI RAID disk rack data cabling diagram Extension Disk Rack (SJ–0812 SCSI JBOD –...

  • Page 303: Figure 171. Fda 1X00 Fc Disk Rack Data Cabling Diagram

    Disk Rack (FDA 1x00 FC) Mark Cable Type From RJ45 – RJ45 Ethernet cable S/S Disk Ethernet Hub port 6 LC–LC cable S/S Disk (CTL 0) FC Adapter (IOC 0 Module 0) DB9 to DB9 serial cable (optional) PAP COM 1 S/S Disk RS232 Figure 171.

  • Page 304: Novascale 6165 Server Data Cabling Diagrams

    NovaScale 6165 Server Data Cabling Diagrams Internal Disk Configuration B-16 User’s Guide...

  • Page 305: Figure 173. Novascale 6165 Server Data Cabling Diagram

    Mark Cable Type From video/PS2/PS2 cable Console KVM switch USB cable PAP USB Modem USB RJ11 – RJ11 cable Modem (Line) Telephone network socket RJ45 – RJ45 Ethernet cable PAP (VGA and PS2) KVM Port 1 via AVRIQ (4) RJ45/RJ45 cable IOL #0 Module 0 KVM Port 3 VGA and USB...

  • Page 306: External Disk Configuration

    External Disk Configuration SJ–0812 SCSI JBOD Disk Ra Mark Cable Type From SCSI–3 68–pin HBA SCSI RAID S/S Disk 1 VHDCI to VHDCI cable (IOC0) Extension port SCSI–3 68–pin HBA SCSI RAID S/S Disk 2 VHDCI to VHDCI cable (IOC1) Extension port Figure 174.

  • Page 307: Figure 175. Sr-0812 Scsi Raid Disk Rack Data Cabling Diagram

    SR–0812 SCSI RAID Disk Ra Mark Cable Type From RJ45 – RJ45 Ethernet cable Nport Server (Module 0) Hub RJ45 – RJ45 Ethernet cable Nport Server (Module 1) Hub RJ45 – RJ45 Ethernet cable Hub Ethernet port 7 PAP LAN Maint DB9 to Jack cable (optional) Nport server S/S Disk 1 RS232...

  • Page 308: Figure 176. Sj-0812 Scsi Jbod Extension Disk Rack Data Cabling Diagram

    Extension Disk Rack (SJ–0812 SCSI JBOD – SR–0812 SCSI RAID) Mark Cable Type From SCSI–3 68–pin SR–0812 SCSI SJ–0812 SCSI JBOD VHDCI to VHDCI cable RAID extension port extension port Figure 176. SJ–0812 SCSI JBOD extension disk rack data cabling diagram B-20 User’s Guide...

  • Page 309: Figure 177. Fda 1X00 Fc Disk Rack Data Cabling Diagram

    Disk Rack (FDA 1x00 FC) Mark Cable Type From RJ45 – RJ45 Ethernet cable PAP Ethernet Hub port 1 LC–LC cable S/S Disk (CTL 0) FC Adapter IOC 0 Module 0 LC–LC cable S/S Disk (CTL 1) FC Adapter IOC 1 Module 0 LC–LC cable S/S Disk (CTL 0) FC Adapter...

  • Page 310: Figure 178. Fda 1X00 Fc - Fda 1X00 Fc Extension Disk Rack Data Cabling Diagram

    Extension Disk Rack (FDA 1x00 FC – FDA 1x00 FC) Mark Cable Type From HSSDC–HSSDC cable S/S Disk S/S Disk Extension DE diagnosis cable S/S Disk S/S Disk Extension Figure 178. FDA 1x00 FC – FDA 1x00 FC extension disk rack data cabling diagram B-22 User’s Guide...

  • Page 311: Figure 179. Fda 2X00 Fc Disk Rack Data Cabling Diagram

    Disk Rack (FDA 2x00 FC) Mark Cable Type From RJ45 – RJ45 Ethernet cable PAP Ethernet Hub port 1 LC–LC cable S/S Disk (CTL0–HF0) FC Adapter IOB 0 Module 0 LC–LC cable S/S Disk (CTL0–HF1) FC Adapter IOB 1 Module 0 LC–LC cable S/S Disk (CTL1–HF0) FC Adapter IOB 0 Module 1 LC–LC cable...

  • Page 312: Figure 180. Fda 2X00 Fc - Fda 1X00 Fc Extension Data Cabling Diagram

    Extension Disk Rack (FDA 2x00 FC – FDA 1x00 FC) Mark Cable Type From HSSDC–HSSDC cable S/S Disk S/S Disk Extension DE diagnosis cable S/S Disk S/S Disk Extension Figure 180. FDA 2x00 FC – FDA 1x00 FC extension data cabling diagram B-24 User’s Guide...

  • Page 313: Power Cabling Diagram

    Power Cabling Diagram Internal Disk configuration PDU–2 PDU–1 Console Drawer NPort Server KVM Switch PAP Unit CSS Module 1 CSS Module 0 Mains Mains Mark Cable Type From Power cable Console PDU–1 J4 Power cable KVM switch PDU–1 J3 Power cable PDU–2 J5 Power cable NPort server...

  • Page 314: Figure 181. Novascale 5165 Server / Novascale 6165 Server Power Cabling Diagram

    SCSI or FC Disk configuration PDU–2 PDU–1 Console Drawer NPort Server KVM Switch PAP Unit Disk SCSI Disk SCSI Power bar Disk SCSI or FC Disk SCSI or FC CSS Module 1 CSS Module 0 Mains Mains Mark Cable Type From Power cable Power bar...

  • Page 315: Appendix C. Error Messages And Recovery Information

    During initialization, POST codes are generated by the BIOS for each QBB in the configuration. These POST codes may be used for troubleshooting purposes. Bull NovaScale Server POST codes can be viewed by clicking BIOS Info in the PAM Domain Manager and are organized as follows:...

  • Page 316: Bios Error Messages

    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 Page Boot Error Messages...

  • Page 317: Sal-A Post Codes

    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. Program SNC static registers 0x8FEA System BSP election (case with SPS) 0x8FD7 (1) Looks for PEloader (case without SPS) 0x8FD7 (2) Looks for PEloader (case with SPS)
  • Page 318 POST Codes 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...
  • Page 319 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...

  • Page 320: Table 61. Sal-A Post Codes (For Releases B600 And Later)

    POST Codes Meaning 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...

  • Page 321: Sal-A Hang Post Codes

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

  • Page 322: Table 63. Sal-A Hang Post Codes (For Releases B600 And Later)

    0xD104 Autoscan returned an error on B–SPS based conf. 0xD105 Autoscan returned an error on SIOH based conf. 0xD106 QBB number too large 0xD107 QBB number Multi–defined 0xD108 QBB Number not contiguous 0xD109 No SNC found in system 0xD10A No Master QBB defined 0xD10B IOB / IOC number too large 0xD10C...

  • Page 323: Sal-B Post Codes

    SAL–B POST Codes POST Codes 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).

  • Page 324: Table 64. Sal-B Post Codes

    POST Codes Meaning 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.

  • Page 325: Sal-B Hang Post Codes

    SAL–B Hang POST Codes POST Codes Meaning 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.

  • Page 326: Sal-F Post Codes

    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.

  • Page 327: Sal-F Hang Post Codes

    SAL–F Hang POST Codes POST Codes Meaning 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.

  • Page 328: Ia-32 Post Codes

    IA–32 POST Codes IA–32 Meaning POST Codes 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.
  • Page 329 IA–32 Meaning POST Codes 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.
  • Page 330 IA–32 Meaning POST Codes 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 vec- tors. Next, checkpoint 0x0024. 0x0024 Perform any OEM specific initialization before interrupt vector initialization. Interrupt vector initialization is about to begin.
  • Page 331 IA–32 Meaning POST Codes 0x002D The video ROM has returned control to BIOS POST Performing any re- quired processing after the video ROM had control. Uncompress and initial- ize 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.
  • Page 332 IA–32 Meaning POST Codes 0x003A Display message to press a key Hit <DEL> or OEM defined key to enter set- up. Display entering setup message “Entering Setup” if DEL key has been pressed. Next, checkpoint 0x0040. 0x0040 Check for <ESC> or <DEL> keys to limit wait for <DEL> key press. The DEL and ESC keys are also checked in the majority of the checkpoints from checkpoint 0x0040 to checkpoint 0x0059.
  • Page 333 IA–32 Meaning POST Codes 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.
  • Page 334 IA–32 Meaning POST Codes 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 Initiali- zation Manager sub–codes.
  • Page 335 IA–32 Meaning POST Codes 0x008E 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.
  • Page 336 IA–32 Meaning POST Codes 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.
  • Page 337 IA–32 Meaning POST Codes 0x00A8 Initialization before passing control to the adapter ROM at E000h com- pleted. 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.

  • Page 338: Device Initialization Manager (Dim) Code Checkpoints

    Device Initialization Manager (DIM) Code Checkpoints The Device Initialization Manager module gets control at various times during BIOS POST to initialize different BUSes. The following table describes the main checkpoints where the DIM module is accessed: DIM Codes Meaning 0x??2A Initialize different BUSes and perform the following functions: Reset, Detect, and Disable (function 0);...

  • Page 339: Pci Diagnostic Post Codes

    PCI Diagnostic POST Codes POST Codes Name Meaning 31–16 Post code main part See below 15–12 Ext3 Module number (0 or 1) 11–08 Ext2 IOB / IOC number (0 or 1) 07–04 Ext1 Hub link number for the PCI (1 to 4) 03–00 Ext0 P64H2 secondary bus (0x“A”...

  • Page 340: Efi Post Code Map

    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 –...

  • Page 341: Recovery Port 80 Post Codes

    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.

  • Page 342: Table 75. Recovery Port 80 Post Codes (For Releases B600 And Later)

    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_NO_ACTIVE_FAT16_PART 0xAAEF CD_NO_ACTIVE_BOOT_SECTOR 0xAAC0 PMB_BAD_MAGIC_NUMBER1 0xAAC1 PMB_TIME_OUT...

  • Page 343: Runtime Post Codes

    Runtime POST Codes POST Codes Module 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...

  • Page 344: Pam - Bios Interface Post Codes

    PAM – BIOS Interface Post Codes These Post codes are issued on execution of the commands sent by the BIOS to the PAM. POST Module Display Codes 0xA000 BIOS Ready command is to be sent 0xA001 BIOS Ready command has been sent 0xA002 BIOS Ready command has returned KO (status 1=–1) 0xA004...
  • Page 345 POST Module Display Codes 0xA052 Reset System command has returned KO (status 1=–1) 0xA055 Reset System command has returned normal (status1=0, status2=0) PAM 0xA05F No response to Reset System command after time out 18 sec 0xA060 Set Time command is to be sent 0xA061 Set Time command has been sent 0xA062...

  • Page 346: Table 77. Pam - Bios Interface Post Codes (For Releases B740 And Later)

    POST Module Display Codes 0xA0B0 Send Message command is to be sent 0xA0B1 Send Message command has been sent 0xA0B2 Send Message command has returned KO (status 1=–1) 0xA0B5 Send Message command has returned normal (status1=0, sta- tus2=0) 0xA0BF No response to Send Message command after time out 18 sec 0xA0C0 Notify command is to be sent 0xA0C1...

  • Page 347: Boot Error Messages

    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 BIOS could not find a bootable device in the system device or Insert Boot Media in and/or removable media drive does not contain media.

  • Page 348: System Configuration Error Messages

    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.

  • Page 349: Cmos Error Messages

    CMOS Error Messages Message Displayed Description CMOS Date/Time Not 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.

  • Page 350: Pam Help Messages

    PAM Help Messages Message severity levels, on page C-36 Message list, on page C-36 Message Severity Levels PAM event messages or histories are graded into four severity levels as explained in Understanding Event Message and History Severity Levels, in the User’s Guide. Note: According to the message severity level, the first character 2 of 2B2Bxxxx (Success, Information or Warning level) may change to A (AB2Bxxxx) (Error level).
  • Page 351 Description 2B2B101A Component irrelevant 2B2B101B PAM internal error 2B2B101C Factory Bootrom used to load MAESTRO 2B2B101D Updated Bootrom used to load MAESTRO 2B2B101E Running MAESTRO loaded from PMB flash ROM 2B2B101F Running MAESTRO loaded from PAP disk 2B2B1020 MAESTRO image choice: “PMB flash ROM” 2B2B1021 MAESTRO image choice: PAP disk 2B2B1022...
  • Page 352 Description 2B2B2015 Renaming object forbidden 2B2B2016 Method not applicable 2B2B2017 PAM object should not be reentered 2B2B2018 Unexpected variant type 2B2B2019 Error detected by the PAP Operating System 2B2B201A Cannot create object 2B2B201B Command in progress 2B2B201C Asynchronous command not issued 2B2B201D Service status 2B2B201E...
  • Page 353 Description 2B2B2223 Domain <domain name>, <command> failed 2B2B2224 BIOS command received: <command name> 2B2B2225 Reset action requested 2B2B2226 Domain creation error 2B2B2227 Domain not running 2B2B2228 Domain <domain name> is already powered on 2B2B2229 Incorrect BIOS data length 2B2B222A Domain group cannot be removed 2B2B222B Domain cannot be removed because it is not in an INACTIVE state...
  • Page 354 Description 2B2B224D Domain power off after virtual power on 2B2B224E BIOS Post Code not accessible 2B2B224F Cannot delete BIOS image file 2B2B2250 Cannot update an EFI variable 2B2B2251 Cannot read recovery status 2B2B2252 Scheme incompatible with current domain configuration 2B2B2253 Resource missing in scheme 2B2B2254 BIOS postcodes logged after time–out...
  • Page 355 Description 2B2B2503 CPU KO (Performance restricted) 2B2B2504 CPU KO (Functionally restricted) 2B2B2505 CPU KO (Unresponsive) 2B2B2508 Unknown BIOS status 2B2B2509 Unknown PIROM format 2B2B2510 Invalid PIROM data 2B2B2511 Invalid memory size 2B2B2512 CPU FRU–EEPROM written 2B2B2513 Module Power configuration: normal 2B2B2514 Module Power configuration: critical 2B2B2515...
  • Page 356 Description 2B2B2541 Check EEPROM failed 2B2B2600 HistoryManager internal error 2B2B2601 History internal error 2B2B2602 Archive internal error 2B2B2603 EVT files not available 2B2B2604 HistoryMaster missing 2B2B2605 XML description not found 2B2B2606 Event Logging failed 2B2B2607 Static History illegal operation 2B2B2608 Current history not locked for any PUID 2B2B2609 Current history not locked for PUID...
  • Page 357 Description 2B2B2809 Invalid Hardware Type 2B2B2900 NVRAM area modified 2B2B2901 S@N.IT command failed 2B2B2902 Check internal SAN – only one fabric allowed 2B2B2903 Property or method not available 2B2B2904 Parameter must have hexadecimal characters 2B2B2905 method or property modification forbidden 2B2B2906 S@N.IT discovery failed 2B2B2907...
  • Page 358 Description 2B2B3210 PMB firmware reload: started 2B2B3211 MAESTRO reboot after having reloaded PMB firmware 2B2B3212 MAESTRO reboot before reloading PMB firmware 2B2B3213 PMB firmware: missing File or Version information 2B2B321E PMB firmware OK 2B2B321F PMB Firmware information 2B2B3220 PMB confidence test not performed 2B2B3221 PMB confidence test error 2B2B3222...
  • Page 359 Description 2B2B3322 P64H2_<P64H2 number> hot–plug request 2B2B3323 P64H2_<P64H2 number> hot–plug acknowledge. 2B2B3324 ACPI signal asserted 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...
  • Page 360 Description 2B2B3602 BIOS log queue overflow control 2B2B3700 ERC mode 2B2B3701 ERC interrupt 2B2B3702 Error in Machine Check processing 2B2B3703 ERC signal configuration state 2B2B3704 ERC log queue overflow control 2B2B3705 BIOS log queue state 2B2B3706 Burst of machine check errors 2B2B3707 Burst of machine check errors terminated 2B2B3708...

  • Page 361: Table 83. Pam Message List

    Description 2B2B4002 XML node missing 2B2B4003 Web session initialization error 2B2B4004 Page loading error 2B2B4005 Error discarded 2B2B4006 Error loading an ASP page, generally due to a loading time limit 2B2B4007 Error occurred on the WEB Client 2B2B4008 Intervention report 2B2B400A WEB Session started 2B2B400B...
  • Page 362 C-48 User’s Guide...

  • Page 363: Glossary

    Glossary Bit: Derived from BInary digiT. A bit is the smallest unit of information a computer handles. BTU: British Thermal Unit. Alternating Current generated by the power Byte: A group of eight binary digits (bit) long that supply. See DC. represents a letter, number, or typographic symbol.
  • Page 364 COM +: Component Object Model +. Microsoft DIMM: Dual In-line Memory Module – the smallest technology for component based application system memory component. development under Windows. The external part of Disk Drive: A device that stores data on a hard or the PAM software package is a COM+ application.
  • Page 365 EFIMTA: EFI Modular Test Architecture. EFI Shell: The EFI (Extensible Firmware Interface) Shell is a simple, interactive user interface that Fail–over: Failover is a backup operational mode allows EFI device drivers to be loaded, EFI in which the functions of a system component applications to be launched, and operating systems (such as a processor, server, network, or database, to be booted.
  • Page 366 FRU: Field Replaceable Unit. A component that is Hot plugging: The operation of adding a replaced or added by Customer Service Engineers component without interrupting system activity. as a single entity. Hot swapping: The operation of removing and FSS: FAME Scalability Switch. Each CSS Module replacing a faulty component without interrupting is equipped with 2 Scalability Port Switches system activity.
  • Page 367 IOC: Input / Output Board Compact. The IOC LED: Light Emitting Diode. A small electronic connects up to 6 PCI–X boards. device that glows when current flows through it. IOL: I/O Board Legacy. The IOL provides: Legacy Application: An application in which a –...
  • Page 368 MQB: Midplane QBB board. The MQB connects one or two QBBs and one or two IPDs. See QBB and IPD. PAL: Processor Abstraction Layer. See SAL. MSX: Midplane SPS & XPS board. The MSX houses a B–SPS switch and is connected to the PAM: Platform Administration &...
  • Page 369 SCI: Scalable Coherent Interface. QBB: Quad Brick Board. The QBB is the heart of the Bull NovaScale Server, housing 4 Itanium R 2 SCSI: Small Computer System Interface. An input processors and 16 DIMMs. Each QBB and output bus that provides a standard interface...
  • Page 370 Serial Port: Connector that allows the transfer of data between the computer and a serial device. See COM1 or COM 2.Shell is a Unix term for the interactive user interface with an operating system. Target: Each message refers to a target (the component referred to in the message), identified SIO: Server I/O / Super I/O.
  • Page 371 USB: Universal Serial Bus. A plug–and–play WBEM: Web Based Enterprise Management. interface between a computer and add–on devices. WMI: Windows Management Interface. The USB interface allows a new device to be added to your computer without having to add an WOL: A feature that provides the ability to remotely adapter card or even having to turn the computer...
  • Page 372 G-10 User’s Guide...

  • Page 373: Index

    Index Web, 2-23 Connection, hardware, 3-48 Access, front door, 1-20 Console, 1-14 opening / closing, 1-21 Alarm, tamper, 1-20 Archive toggling, 2-8 history, 4-31 CSS , functional status / domain state, 4-36 viewing, online, 4-31 CSS hardware, functional status, 4-4 Array partition, creating, 5-7 CSS Module, PMB, 4-42 CSS module, 1-12...
  • Page 374 reset, 3-17, 3-48 customizing, 5-85 Domain configuration, 3-33 e–mail, viewing, 4-28 adding a cell, 3-35 enabling / disabling channels, 5-96 adding domains, 3-10 managing, 4-24 removing a cell, 3-38 severity, 5-105 replacing, 3-10 severity levels, 4-25 Domain identity. See identity sorting / locating, 4-28 Domain manager, 3-2 source, 5-105...
  • Page 375 Hardware faults list consulting, 4-26 displaying, 4-28 Laser safety, xx Hardware monitor, CSS module power, 4-17 LEDs, PMB, 4-42 Hardware resources Linux, system users, 5-4 checklist, 5-80 Linux domain, remote access, Web, 2-21 domain, 3-26 Linux Redhat, remote access, enterprise LAN, 2-19 Highlighting, documentation, xv Linux SuSE domain, remote access, enterprise Histories...
  • Page 376 Power–up server domain, 2-9, 2-10, 2-11 system domains, 2-15, 2-18 Powering ON / OFF, domains, 4-40 connection, 2-2 customizing, 5-85 Preface, documentation, iii details pane, 2-7 Processors, 1-12 event messaging, 5-85 messages, C-36 simultaneous connection, 2-4 QBBs, 1-12 software package, 1-22 status pane, 2-6, 4-3 toolbar, 2-7 RAID controller, 1-16...
  • Page 377 IOB, 1-12 String lengths, xxiii IOL, 1-12 Subscriptions keyboard, 1-14 advanced filtering criteria, 5-105 KVM switch, 1-15 channels, 5-96 memory boards, 1-12 creating, 5-98 modem, 1-19 deleting, 5-99 monitor, 1-14 e–mail account, 5-90 mother boards, 1-12 e–mail server, 5-88 mouse, 1-14 editing attributes, 5-99 NPort Server, 1-19 filter, 5-111...
  • Page 378 User’s Guide...
  • Page 379 SOCIETE / COMPANY : ADRESSE / ADDRESS : Remettez cet imprimé à un responsable BULL ou envoyez-le directement à : Please give this technical publication remark form to your BULL representative or mail to: BULL CEDOC 357 AVENUE PATTON B.P.20845...
  • Page 380 Customer Code / Code Client : For Bull Internal Customers / Pour les Clients Internes Bull : Budgetary Section / Section Budgétaire : For Others / Pour les Autres : Please ask your Bull representative. / Merci de demander à votre contact Bull.
  • Page 382 BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE ORDER REFERENCE 86 A1 41EM 00...
  • Page 383 Utiliser les marques de découpe pour obtenir les étiquettes. Use the cut marks to get the labels. NovaScale 5xx5 & 6xx5 User’s Guide 86 A1 41EM 00 NovaScale 5xx5 & 6xx5 User’s Guide 86 A1 41EM 00 NovaScale 5xx5 & 6xx5 User’s Guide 86 A1 41EM 00...

This manual is also suitable for:

Novascale 6 5 seriesNovascale 5085Novascale 5165Novascale 6085Novascale 6165

Table of Contents