OSM Service Connection User's Guide HP Part Number: 527274-045 Published: August 2014 Edition: J06.03 and subsequent J-series RVUs and H06.03 and subsequent H-series RVUs.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents What's New in This Guide...........................................................................32 About This Guide........................................................................................40 Related Reading..........................................................................................41 1 Introducing OSM......................................................................................42 OSM Interfaces..................................................................
State Indicators..................................................................................................................58 Alarm Indicators................................................................................................................59 In the tree pane............................................................................................................59 On the alarms tab and detail..........................................................................................
Physical.......................................................................................................................78 Logical........................................................................................................................78 Actions.............................................................................................................................78 Power Off............................................................................................................
Attributes..........................................................................................................................86 Blade Element...............................................................................................................86 Physical.......................................................................................................................86 Physical Location.......................................................................................................
Abort..........................................................................................................................94 Start............................................................................................................................94 Stop............................................................................................................................94 Test Verify............................................................................................................
Logical......................................................................................................................104 Process Pair................................................................................................................104 Disk Pair....................................................................................................................104 Firmware....................................................................................................................
Start Primary Path........................................................................................................111 Start Volume...............................................................................................................111 Stop Backup Path........................................................................................................111 Stop Disk...................................................................................................................
Firmware Update........................................................................................................117 Get Logical Disk(s)......................................................................................................117 Replace.....................................................................................................................117 Set LED State..............................................................................................................
Process Pair................................................................................................................123 Actions...........................................................................................................................124 Abort Backup Path.......................................................................................................124 Abort Disk..................................................................................................................
Switch to Primary Path.................................................................................................129 Test Verify..................................................................................................................129 Validate Checksum......................................................................................................129 External Disk Collection.........................................................................................................
Firmware....................................................................................................................134 Actions...........................................................................................................................134 BIOS Update..............................................................................................................134 Firmware Update........................................................................................................
FCSA FSAC................................................................................................................142 Actions...........................................................................................................................143 Responsive Test...........................................................................................................143 FESA (Fast Ethernet ServerNet Adapter)...................................................................................
Stop..........................................................................................................................149 G4SA SAC..........................................................................................................................149 Attributes........................................................................................................................149 G4SA SAC..........................................................................................................
Group Connectivity ServerNet Path Test..........................................................................156 Processor-to-Processor Connectivity Test..........................................................................156 Start ServerNet...........................................................................................................156 Stop ServerNet...........................................................................................................156 IO Module..................
Disable Processor Freeze..............................................................................................163 Enable Processor Freeze...............................................................................................164 Halt...........................................................................................................................164 Power Cycle LSU.........................................................................................................
Actions...........................................................................................................................170 Firmware Update........................................................................................................170 Replace.....................................................................................................................171 Optical Extender PIC...........................................................................................................
Attributes........................................................................................................................180 Power Supply..............................................................................................................180 Physical.....................................................................................................................181 Actions....................................................................................................................
Actions...........................................................................................................................186 Configure Power Source as AC.....................................................................................186 Configure Power Source as UPS....................................................................................186 Delete the Power Source Configuration...........................................................................187 Replace.....................
Write LCD Line............................................................................................................194 SAC (ServerNet Addressable Controller)..................................................................................194 Attributes........................................................................................................................195 SAC..........................................................................................................................
Physical.....................................................................................................................201 Actions...........................................................................................................................201 Replace.....................................................................................................................201 ServerNet PIC............................................................................................................
Processor Boot Millicode Firmware................................................................................208 Actions...........................................................................................................................209 Reset.........................................................................................................................209 Responsive Test...........................................................................................................
SWAN CLIP.........................................................................................................................216 Attributes........................................................................................................................216 CLIP $ZZWAN...........................................................................................................216 Logical...................................................................................................................
Operating System.......................................................................................................222 Data Collection Services..............................................................................................222 System Load Configuration...........................................................................................222 Incident Report Configuration........................................................................................223 Actions...................
Test Verify..................................................................................................................232 TRSA (Token Ring ServerNet Adapter).....................................................................................232 Attributes........................................................................................................................232 TRSA.........................................................................................................................
ME FPGA...................................................................................................................238 ME Firmware..............................................................................................................238 Actions...........................................................................................................................238 Dump Memory...........................................................................................................
Actions...........................................................................................................................255 Replace.....................................................................................................................255 Set Locator.................................................................................................................255 6780 Switch Module........................................................................................................
Actions...........................................................................................................................262 ServerNet Cluster.................................................................................................................262 Attributes........................................................................................................................262 ServerNet Cluster.............................................................................................
Actions...........................................................................................................................269 Switch Logic Board...............................................................................................................269 Attributes........................................................................................................................269 Switch Logic Board.............................................................................................
Neighbor Switch PIC...................................................................................................276 Actions...........................................................................................................................276 Switch Port...........................................................................................................................276 Attributes............................................................................................................
What's New in This Guide Describes features available with OSM Service Connection version T0682 H02 ADL, including: • Support/requirement for Java 7. For configuration steps necessary to use OSM with Java 7, see Launching an OSM Service Connection and Enabling Java Next Generation Plug-in to Avoid OSM Memory Errors. Java 7 also requires Windows Server 2003 Hotfixes in order to use OSM T0682 H02 ADL (and later) on Windows Server 2003.
Also new for H06.27/J06.16, OSM Low-Level Link (T0633 G07 ABS) adds a “Select to change iLO Admin user's password” option in the Configure CLIM dialog box. This allows you to change this password without logging on to the iLO interface. If there is no Admin user ID yet – as may be the case with replacement CLIMs – this Low-Level Link action creates that Admin user ID and allows you to establish a password for it. At H06.26/J06.
• A new Place Local Node in Service action on the BladeCluster object, to be used when intentionally halting a system to prevent all other directly-connected nodes from dialing out an alarm as soon as SNETMON is stopped or the node is halted. • Support for analyzing the system board battery sensor in RX2620, RX2660, RX2800 i2, BL860c, and BL860c i2 servers at initial blade discovery and whenever the Save BMC Event Log is retrieved (the default interval is every 24 hours).
• Support for disk partitioning on both Hard Disk Drives (HDDs) and Solid State Disks (SDDs), including: ◦ The Start Disk, Start Volume, Stop Disk, and Get Logical Disk(s) actions on the SAS Disk object have been modified to work with partitioned disks. ◦ A Partition Number attribute has been added to the CLIM-Attached Disk object to indicate the partition number. • For G6 CLIMs, a new subcomponent InfiniBand HCA Card object.
At H06.20/J06.09, OSM Service Connection (T0682 H02 ACC) added support for: • NonStop Volume Level Encryption, which provides a simple and secure method for registering CLIMs with Enterprise Secure Key Managers. OSM support includes: ◦ A new guided procedure, launched from an action on the CLIMs (container) object, to help you Register CLIMs with Key Managers. ◦ A new action on individual CLIM objects to Show CLIM/Key Manager Registration Information.
At H06.19/J06.08, OSM Service Connection (T0682 H02 ABX) added: • New actions on the System object to Configure BladeCluster and Clear External Cluster Configuration. • Support for new actions on the Processor Blade (BladeSystem) and Blade Element objects to clear or retrieve the Forward Progress Log. • The Reboot action on the CLIM object has been enhanced, providing the option to perform a dump of diagnostic data before rebooting the CLIM.
to include support for J06.03 and the components, as displayed by the OSM Service Connection, of an HP Integrity NonStop BladeSystem, including: • HP BladeSystem c-Class Enclosure • CLuster I/O Module (CLIM) • SAS Disk Enclosure For more information, see: • NonStop BladeSystems Planning Guide • NonStop BladeSystems Hardware Installation Manual • CLuster I/O Module (CLIM) Installation and Support Guide • Common IP (CIP) Installation, Configuration, and Management Manual At H06.
At H06.07, the OSM Service Connection Suite was updated to T0682 H02 AAU to provide support for: • An improved module-level Redundant Power Scrub test. (Click the link or see softdoc for details.) • RoHS-compliant hardware. • Monitoring four Blade Element fans for Integrity NonStop NS1000 servers, five Blade Element fans for Integrity NonStop NS5000T and NS5000CG servers. Also new for H06.07 is the OSM System Inventory Tool.
About This Guide The OSM Service Connection User's Guide is available as online help within the OSM Service Connection, and in the NonStop Technical Library. From within the OSM Service Connection, you can: 40 • Access a JavaHelp online help interface to the OSM Service Connection User's Guide by selecting Help > Help Contents from the OSM menu bar.
Related Reading Sources of OSM-related information: • This manual, the OSM Service Connection User's Guide, is available in the NonStop Technical Library (NTL) and as online help from within the OSM Service Connection. It deals mostly with using the OSM Service Connection to monitor and perform actions on system and cluster resources.
1 Introducing OSM The OSM client components are installed on a PC workstation that serves as the system console. The OSM server components are installed on the NonStop server running the HP NonStop operating system. Server-Based Components OSM server-based components (including the OSM Service Connection and OSM Event Viewer applications) have been combined into a single product, T0682. For information on how to configure and start OSM server-based processes, see the OSM Configuration Guide.
OSM Guided Procedure OSM Action For Object Replace Fibre Channel Disk Module Replace (FCDM) component FCDM or subcomponent (Fibre Channel disk drive, FC-AL I/O module, EMU, power supply, and blower) Replace Processor Switch component Replace Processor Switch or subcomponent (ServerNet Switch Board, Maintenance PIC, ServerNet PIC, fan, and power supply) Replace Blade Element component Replace NonStop Blade Element or subcomponent(processor board, front panel display, memory board, reintegration boa
2 Preparing the OSM Environment To plan your network LAN configuration and connect your system console so it can communicate with your NonStop server through OSM client/server software, see the NonStop NS-Series Hardware Installation Manual (shipped with every new system; also available in the Hardware Service and Maintenance collection of NTL). The OSM Configuration Guide describes how to configure and start OSM server-side processes.
3 Configuring OSM Before using OSM applications to manage your system. • Configure the server using the OSM Low-Level Link (see Configuring the Server). • If using HP Insight Remote Support Advanced for remote support services, see Insight Remote Support Advanced for NonStop, located in the external NonStop Service Information collection of NTL. • Configure OSM to Avoid Java Memory Errors NOTE: It is possible to start and run a new server without performing OSM configuration.
Configuring the Server You must configure these server components using the OSM Low-Level Link: Use this dialog box To Network Configure unique MSP IP addresses for your primary and backup LANs. Startup Windows Define the workstations authorized to display the startup TACL prompt and receive the event messages that occur during a system load. MSP Users Define the users that are authorized to connect to the master service processors (MSPs) or maintenance entities (MEs) on your server.
For rack-integrated UPS units, OSM provides an orderly system shutdown in the event that a power failure exceeds the powerfail-delay time interval specified for your rack-integrated UPS. To configure this OSM power-fail support: • For an HP Integrity NonStop NS16000 server, you must use the Configure Power Source as UPS action for at least one processor switch power supply unit to tell OSM that a rack-integrated UPS is configured to provide backup power.
4 Starting the OSM Service Connection You can: • Launch an OSM Service Connection • OSM Service Connection Session Error Messages • Using OSM Bookmarks • Verify the OSM Service Connection State • Run Multiple Sessions Launching an OSM Service Connection NOTE: There are conditional requirements for using T0682 H02 ADL (and later), depending on how the Service Connection is being accessed: • Because it uses Java 7, Windows Server 2003 Hotfixes are required in order to use OSM T0682 H02 ADL (and lat
NOTE: When using Secure Sockets Layer (SSL) to establish a secure connection to the NonStop server, OSM checks that the server certificate that meets all requirements for establishing this trust relationship. If one or more of the requirements are not met, OSM displays a dialog box right after you submit logon credentials. This dialog box informs you that there is a problem with the OSM server certificate and lists the specific reason(s) for the problem.
You cannot run multiple sessions by: 50 • Reusing a browser window used for a previous OSM Service Connection session • Selecting File > New to open a new OSM session from within an existing session Starting the OSM Service Connection
5 Using the Management Window The OSM Management window appears after system discovery. It displays OSM features and information about your local system and ServerNet cluster. The Management window contains an OSM menu bar and these panes: Overview Displays a high-level view of system objects, such as internal fabrics, groups, and external devices (external disks and tapes), and of ServerNet Cluster objects, such as external fabrics, local nodes, and remote nodes.
Management Window Example Internet Explorer Menu Bar The Internet Explorer menu bar is not customized for the OSM application. For most OSM functions, use the OSM menu bar (located above the view pane) and the various panes within the Management window. Internet Explorer functions that you might use for OSM include • Access OSM bookmarks from the Internet Explorer Favorites menu. However, you must use the OSM Create Bookmark function in the Tools menu to create the bookmarks.
to a menu option under the Tools menu. This topic describes the options available under each OSM menu. CAUTION: Do not close the Management window when any OSM dialog box is open. You will lose your current service connection. Display Menu The Display menu contains the following items: Attributes Displays the Attributes dialog box for the selected object. See Using the Attributes Dialog Box to View Attributes.
the Logical Status view. If the icon turns yellow, select this Logical Status menu option to locate the problem and get details. While the Logical Status view cannot be customized, you can also use the Multi-Resource Action dialog box to create your own resource views; see Using Customized Resource Views. Event Viewer Launches the OSM Event Viewer in a separate window.
refers to the running of OSM incident analysis, which checks EMS event messages and creates alarms in OSM if certain conditions exist. Using the Physical View The Physical view is displayed in the view pane of the Management window. You can display the Physical view of either: • A ServerNet Cluster • A local system or its components When you select any resource in the Physical view, its attributes, alarms (if any), and actions are displayed in the details pane.
To display the Physical view of an enclosure: 1. In the tree or Overview pane, click a group. 2. From the View list, select Physical. Physical View of a Fabric The Physical view of a fabric provides an overview of the internal ServerNet X and Y fabrics and the processors and groups connected to them. You can also view a single fabric and the processor switches and IOAM enclosure connected to it. Clicking a resource within the Tree view outlines its location in blue in the Physical view.
Track ID The unique number assigned to every component. If you know a component's part number and tracking ID, you can find its exact location in the system. Part Number The part number assigned to the component. Use this part number to order a replacement component. Inventory View of a Local System The Inventory view of a local system displays a complete or partial list of resources in it, depending on the system resource you select in the tree pane.
Interpreting Icons and Color The OSM Service Connection uses different icons and colors to indicate a change from normal status in a group or resource in the Management window. The states are indicated as green (normal), yellow (warning), and red (critical). See Alarm Severity.
State icons are also shown in the Physical view of a cluster or system. Alarm Indicators If the object has at least one alarm, an alarm icon appears: In the tree pane On the alarms tab and detail In the Alarm Summary Alarm Severity Critical Immediate corrective action is required. A service-affecting fault occurred. For example, a resource might have become unavailable. Major Urgent corrective action is required. A service-affecting fault has developed.
Warning A potential or impending service-affecting fault was detected before any significant effects are evident. For example, retriable errors exceeded a threshold. Cleared This alarm is no longer in effect. Typically, alarms are cleared because the affected resource has been repaired or the fault condition no longer exists. Indeterminate The severity level cannot be determined.
6 Viewing Alarms When certain problem conditions exist on a system, OSM generates alarms on the objects in need of service or attention. Alarms can be viewed in these ways: • • Alarms associated with a specific resource: ◦ Right-click the object and select Alarms to display the Alarms dialog box. ◦ Click the Alarms Tab of the Details pane to view alarms for the selected object. A summary of alarms for the entire server or ServerNet cluster; see Viewing a Summary of Alarms.
Viewing the Alarms Dialog Box To reach this dialog box, either: • Right-click any object in the tree pane or view panes and select Alarms. • Highlight any object in the tree pane or view panes and select Alarms from the Display menu. The Alarms dialog box displays the alarms associated with a selected resource. You can select individual alarms for the resource and display detailed information and available repair actions or act on those alarms.
Click Save. In the Save As dialog box, specify a file name and folder and click Save. The information is saved as a text file. To reach this dialog box: In the Alarm dialog box or Alarm Summary dialog box, select an alarm and click Detail. Suppressing Alarms To stop known problems from propagating up and causing higher level object icons to indicate problem conditions within, you can choose to suppress a particular alarm type on a specific system resource.
7 Viewing Attributes Every resource has attributes associated with it. You can view the attributes of a resource in the details pane of the Management window, or you can display the Attributes dialog box, which is available from any view. To view attributes for a selected resource without opening the Attributes dialog box, see Using the Details Pane to View Attributes. For further information on viewing the Attributes dialog box, see Using the Attributes Dialog Box to View Attributes.
Select, then right-click a problem attribute in either the Attributes tab or Attributes dialog box and click either Permanent or Temporary suppression, as desired:. • If you select Permanent suppression and the same attribute value is generated again on this object at a later time, state propagation will not occur. • If you select Temporary suppression and the same attribute value is generated again on this object at a later time, state propagation will occur.
8 Performing Actions You can perform and monitor actions as follows: • Perform a specific action on a selected resource: Performing Actions on a Selected Resource. • Perform a specific action on several resources of the same type: Performing Actions on Multiple Resources of the Same Type. • Perform a firmware update on a specific resource: Performing Firmware Updates. • View a summary of actions in progress and recently completed: Viewing a Summary of Actions.
Behavior for the three Default Roles is as follows: • NonStop Super ID – No changes can be made to this default role, in terms of membership or privileges, nor can this role be deleted. • For the default roles Everyone and NonStop Super Group Users, cannot add or delete members, but you can change the privileges assigned to those roles. You can delete a selected role using the Delete Role button or restore them if they have been deleted by using the Restore Default Roles button.
in this dialog box. You can add members to the new role by clicking Add Member. Under Privileges, select the actions that can be performed by the members of this role. Any OSM actions not listed here are actions that cannot be restricted through the Access Control List functionality. Click Save Role to save the role and have it added to the list of available roles. You can delete members from a role by using the Delete Member button or delete a selected role by clicking Delete Role.
Viewing Detailed Information About an Action 1. 2. In the Action Status list, select the action whose details you want to view. Click Details to display the Action Detail dialog box. The Action Detail dialog box provides a description of the action, the resource acted on, and the action status. The detail also includes the cause, effect, and repair action for any failed action.
4. 5. Select the specific resources on which to perform the action: Select To Add all Move all resources in the available resources list to the selected resources list. (The Add all button is enabled only when no resource in the available resource list is highlighted.) Add Move a specific resource (selected by clicking it) from the available list to the selected list. Remove all Move all resources from the selected list back to the available list.
Viewing Action Details The Action Detail box provides a description of a selected action, the resource acted upon, and the action status. The detail also includes the cause, effect, and repair action for any failed action. To reach this dialog box: Do one of: • In the Action Status list of Action dialog box, select the desired action and click Details. • In the Action Status list of Multi-Resources Action dialog box, select the desired action and click Details.
6. Click Perform Action. As the firmware update is performed, its status appears to the left of the resource name in the selected resources list. A summary of the action progress is shown in the Progress status boxes. 7. To view a summary of the actions, click Action Summary. (For information on action details, see Viewing Action Details.) Launching Guided Procedures For a list of available guided procedures, see OSM Guided Procedures.
Monitored Service LAN Devices objects do not have a Set Physical Location action; however, the Rack Name and Offset values can be set by placement of the objects through the Physical Configuration Tool. For illustrated information on using the Physical Configuration Tool, see the OSM Configuration Guide.
9 Viewing Summary Reports You can view a: • Problem Summary • Summary of Actions • Summary of Alarms • Resource Summary Viewing a Problem Summary The Problem Summary lists all resources that are in a problem state. The report lists this information: • The name of the problem resource • The Service State (See possible values.) • The attribute group in which the problem occurs • The attributes in which the problem occurs To create the report: Select Summary > Problem.
The Alarm Summary dialog box provides this information about each alarm: • Alarm severity • Time and date the alarm occurred • Resource name • Description of the alarm, including probable cause and alarm type • Whether or not the alarm is suppressed • Whether the alarm is dialed out to your service provider (assuming your system console is configured to dial out) To display detailed information for an alarm: Highlight the alarm and click Detail.
10 Managing a System A system consists of all the hardware components, software, and firmware that are managed by a single operating system. Using the OSM applications, you can monitor and maintain your local server to check the status of all system components and to watch for indications of potential system problems. You can also perform OSM actions to resolve many system problems. For details about the resources that make up a system, see System Resources. Locating and Viewing System Resources 1. 2.
11 System Resources Using OSM, you can monitor and maintain these system resources: Alarm Panel FESA Processor Blade 4PSE Fiber (Blade Switch Port) Processor Components ATM Adapter Fibre Channel Router Processor Switch Module ATM Line FSAC SAC Battery G4SA SAS Card (CLIM) Blade Complex G4SA PIF SAS Disk Enclosure Blade Element G4SA SAC SAS Disk Enclosures Blade Element Firmware GESA SCSI Controller Blade System Board Group (IOAM, Fabric, or G16SE) ServerNet Interface Card (Blade)
FC Card (CLIM) Power Supply (IOAM) VIO FCSA FC-AL I/O Module Power Supply (Processor Switch) VIO G4SA FCDM Power Supply (SAS Disk Enclosure) VIO Logic Board FCDM Collection Power Supply and Fan (Telco SAS Disk VIO Module Enclosure) FCSA Power Supply (VIO) FCSA FSAC Processor (CLIM) 4PSE (4-Port ServerNet Extender) Used only in HP Integrity NonStop NS14000 or NonStop NS1000 systems containing IOAMs, 4PSEs provide ServerNet connectivity to the processors.
Set LED State Turns on or off the amber LED located on the 4PSE. The current state is indicated by the LED State attribute. Alarm Panel (Telco) For Telco systems only, this object can be displayed and monitored in OSM by using the Start Monitoring Alarm Panel action, located under the Monitored Service LAN Devices object. You can access its browser-based configuration interface through the Link to Web Interface action.
Actions Link to Web Interface Opens a Web interface that provides detailed device configuration and information for the alarm panel. Rediscover Causes OSM to refresh and reanalyze the object. Refresh refers to OSM updating the attribute values displayed in the OSM Service Connection interface. Reanalyze refers to the running of OSM incident analysis, which checks EMS event messages and creates alarms in OSM if certain conditions exist. Stop Monitoring Stops OSM from monitoring the alarm panel.
Automatic Dump State Indication of whether the ATM adapter software is automatically dumped to the specified dump file if the software abends abnormally. Enabled: The software is automatically copied. Disabled: The software is not automatically copied. Unknown:: The Automatic Dump state could not be read. Media Type The type of media or cable, such as single-mode fiber or coaxial cable, supported by the ATM CRU.
Test Verify Runs all the firmware diagnostic tests on the CRU. This test takes about three minutes to finish. The CRU must be in the Stopped state before you initiate the Test Verify action. ATM Line The Asynchronous Transfer Mode (ATM) line represents the logical link between the ATM CRU and the ATM network. There is one ATM line per ATM CRU. This Nonstop S-series component can be connected to a Nonstop NS-series system through an IOMF2 enclosure.
Battery The battery customer-replaceable unit (CRU), located in Nonstop S-series processor or I/O enclosures, is an assembly of 24 cells rated at 2.5 amp-hours per cell. The batteries are designed to handle occasional power failures that might occur at typical computer sites. Each processor or I/O enclosure contains two batteries. Location in OSM Tree: System > Group > Module > Battery Slot Location: In processor enclosures, battery CRUs are located in slots 23 and 28 (appearance side). Example: Battery (1.
Total Voltage Sensor Normal Minimum Value The minimum voltage that the battery should maintain is 42 volts. If the battery's Total Voltage falls below 42 volts, an alarm is generated. (If the Total Voltage falls below the Disconnect Voltage Limit of 39.6 volts, the battery is disconnected.) Lower Fatal Threshold The minimum voltage that the battery must maintain to continue operating is 39.6 volts. If the battery's Total Voltage falls below 39.6, the battery is disconnected.
Expected Processor Redundancy The expected redundancy for all the processors in the complex. Set using the Set Processor Expected Redundancy action. Values: Simplex, Duplex, Triplex NOTE: Displayed for NonStop NS14000 series and NS16000 series servers only. Group Number The Group Number for the Blade Complex. Actions These actions apply to NonStop NS14000 series and NS16000 series servers only. There are no actions under the Blade Complex object for any other NonStop servers.
• Two Blade Element Power Supply objects. • Fan Assembly objects to represent each fan in the Blade as follows: slots 16 through 19 for NS1000, slots 16 through 20 for NS5000, and slots 33 through 44 for NS3000AC, NS1200, and NS2000 series. • Memory Card objects. For NonStop NS2100, NS2200 series, NS2300, and NS2400 series servers, OSM displays: • Two Blade Element Power Supply objects. • Six Fan Assembly objects to represent each fan in the Blade slots 32 through 37. • Memory Card objects.
Disk Boot Firmware Running Version The version of the Disk Boot firmware currently running on the processor Blade Element. NOTE: Not applicable for NonStop NS14000 series and NS16000 series servers, where the firmware information is reported under the Blade Element Firmware object. Halted State Services Firmware Running The version of the HSS firmware currently running on the processor Blade Version Element.
Enable Blade Element Reintegration Available for NonStop NS14000 series and NS16000 series servers only, this action enables automatic reintegration of the processor elements on this Blade Element in case of failure. Firmware Update This action, displayed for most Integrity NonStop servers, launches a documented service procedure for updating the Blade Element firmware.
Retrieve Forward Progress Log Retrieves the Forward Progress Log (FPL), which is more detailed than the System Event Log. NOTE: This action can take up to an hour to complete. Save Extended Inventory Allows you to save a file containing an inventory of the Blade Element. Set LED State Available for NonStop NS14000 series and NS16000 series servers only, this action allows you to set the Blade Element front or rear (service side) amber LEDs to On or Off.
following Reset, and perform the Reset to start running the new (non-BMC) firmware. Then you can update the other image, which was the Running image but, following the Switch to Use Shadow... and Reset actions, is now the Shadow image.
Primitive State Firmware Running Version The version of the Primitive State firmware currently running on the processor Blade Element. Shadow Version The version of the Primitive State firmware currently designated as the Shadow image of the Blade Element firmware. Default File Name The full path name of the default Primitivate State firmware file on the server. Default File Version The version of the firmware to be used for a Primitive State firmware update.
Running Compare State The difference, if any, between the current Running image and default BMC firmware version. Values Shadow Compare State The difference, if any, between the current Shadow image and default BMC firmware version. Values PAL/SAL Firmware Running Version The version of the PAL/SAL firmware currently running on the processor Blade Element. Shadow Version The version of the PAL/SAL firmware currently designated as the Shadow image of the blade element firmware.
Location in OSM Tree: System > Group > FCDM Collection > FCDM > Blower Example: Blower (111.211.1.97) Attributes Blower Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values LED State Indicates whether or not the blower’s (amber) fault LED is blinking. Value: Blinking or Off Type The vendor hardware type. Device State The state of the component as known to the operating system on the server.
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Manufacturer Identifies the manufacturer of the component. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Power State Indication of whether the component is powered on. Values Track ID A unique serial number that identifies the component.
• FC Card • Hard Disk • InfiniBand HCA Card (G6 CLIMs only) • Motherboard (G6 and Gen8 CLIMs only) • NIC • PCI Riser • Power Supply • Processor • SAS Card • ServerNet Interface Card • Smart Array Controller (G6 and Gen8 CLIMs only) To update firmware on CLIM components, you can use the actions located on the individual component objects within the OSM Service Connection or the Down System CLIM Firmware Update Tool.
Registered with Key Managers This attribute applies only to supported storage CLIMs (G5 and later), and indicates whether or not – at the time of discovery – the CLIM had been successfully registered to the Key Manager or Key Manager Cluster using the Register CLIMs with Key Managers guided procedure. Storage Software Version The version of storage software running on the CLIM. Temperature Status Indicates whether or not the CLIM has exceeded its temperature threshold for proper operation.
iLO IPv4 Address The IPv4 address of the Integrated Lights Out (iLO) port on the CLIM. The IP address of the CLIM iLO is displayed only when SNMP is available; however, the iLO DNS Name attribute is displayed even when SNMP is not available. iLO Pulse Link State Possible values: Up or Down. Model The model number of the CLIM that was assigned in manufacturing. Part Number The part number of the CLIM that was assigned in manufacturing. Serial Number The serial number of the CLIM.
Default File Version The version of the firmware to be used for an iLO firmware update. Version The version of the firmware running on the iLO. ROM Version -- the version of the ROM firmware running on the CLIM. Compare State Indication of the differences, if any, between the current and default ROM firmware versions. Values Default File Name The name of the file to be used for an ROM firmware update. Default File Version The version of the firmware to be used for an ROM firmware update.
Replace Hard Drive Launches a guided procedure to make replacement of a CLIM hard disk drive more automated. This guided procedure can also be launched through the Replace action on the (CLIM) Hard Disk object, although CLIM subcomponents, such as the Hard Disk object will not be displayed by OSM if SNMP is not available. Restore CLIM Configuration Restores the CLIM configuration from a previously saved file at a user-specified or default location.
Attributes None. Actions Collect CLIM Logs This action finds and collects CLIM logs, saving them to a subvolume location on the NonStop system specified through the Set Location for CLIM Log Collection action. If no location is specified, a default location of $system.zservice will be used.
• CLIM Smart Array Controller • CLIM NIC • CLIM InfiniBand HCA • CLIM SAS Firmware • CLIM SAS BIOS • CLIM FC Firmware • CLIM FC BIOS • SAS Disk Enclosure (but not individual SAS disk) Firmware NOTE: The Down System CLIM Firmware Update Tool is installed on the NonStop system console as part of the OSM Console Tools product, T0634 G06 ABB and later. It requires SSH SPR T0801^ABA or later.
NOTE: This location is the alternate SYSnn on which you installed the SUT containing the new firmware to be used for the update. • The IP address of the NonStop system console to which the files will be transferred. • User name and password for the NSC. NOTE: This user must have the necessary OpenSSH access permissions, as described above. Click OK to proceed.
DIMM (CLIM) A subcomponent of the CLIM; details that vary according to CLIM type include: • For G2 and G5 CLIMs, there are eight DIMM slots that can be populated. • For G6 CLIMs, there are 18 DIMM slots that can be populated. Nine of those DIMM slots are associated with the processor installed in processor socket 1. The other nine DIMM slots are associated with the processor installed in processor socket 2. The location is identified in OSM by appending the processor number and slot to the DIMM name.
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Manufacturer Identifies the manufacturer of the component. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Power State Indication of whether the component is powered on. Values Track ID A unique serial number that identifies the component.
Backup Path Access State The accessibility of the backup path. Example: Inactive, Active Configured Controller Location The location of the backup disk path SCSI controller. Example: PMF.SAC-2.GRP-1.MOD-1.SLOT-55 SCSI Controller A number (1 or 2) that identifies the backup SCSI controller that manages the disk. Example: SCSI Controller (1.1.50.2) SCSI ID An identification number assigned to the device when configured. Primary Path Access State The accessibility of the primary path.
1. 2. 3. 4. 5. Locate and transfer the appropriate firmware source file to your server. Disk firmware versions vary by manufacturer and model number. The correct version for one disk drive might not work for others. Log on to the OSM Service Connection and use the Actions dialog box (to update one disk at a time) or the Multi-Resource Actions dialog box (to update multiple disks of the same type simultaneously). Stop the disk or disks that you want to update. Perform the Firmware Update action.
NOTE: With OSM Low-Level Link T0633 AAQ and later, you can also save system configuration files on the system console. Those saved configurations are not displayed as attributes values in the OSM Service Connection, but can be used during the system load operations in the Low-Level Link. For more information, see the OSM Low-Level Link online help. Start Backup Path Starts the backup path to this disk drive. When the Start action completes, the backup path is in the Started state.
Switch Process Pair Switches the primary and backup disk I/O processes. Switch to Backup Path Switches processing from the primary to the backup path. Switch to Primary Path Switches processing from the backup to the primary path. Test Verify Runs the power-on self-test for the disk and tests the internal circuitry of the drive. Validate Checksum Scans the user data area of a disk for sector checksum errors.
Media Size The total size (in kilobytes) of disk storage space. Partition Number The number of the partition on a partitioned disk. Physical Location The location of the physical disk that is mapped to this logical disk. Primary Path State The current state of the primary disk path. Values. Product ID A unique number that identifies the product. Backup Path Access State Indicates whether the disk is active or inactive. Configured CLIM The CLIM to which the backup path is configured.
Abort Disk Terminates operation of all paths for the disk. When the Abort action finishes, the paths are in a Hard Down state. You must use the Reset Disk action before you can start the paths again. Abort Primary Path Terminates operation of the primary path to the disk. When the Abort action finishes, the path is in the Stopped state. Clear Data Available only for SAS or SSD disks -- Erases all data on the disk but leaves the disk label intact.
Start Backup Path Starts the backup path to this disk drive. When the Start action completes, the backup path is in the started State. Start Disk Starts all paths to this disk drive. When the Start action completes, all paths are in the Started state. Start Primary Path Starts the primary path to this disk drive. When the Start action completes, the primary path is in the Started state. Start Volume Starts all paths for both the primary and mirror drives of this volume.
Attributes Disk (Fibre Channel) Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Device State The state of the component as known to the operating system on the server. LED State Indicates whether or not the disk drive’s (amber) fault LED is blinking. Value: Blinking or Off Port A Bypass State The state of the Port A Bypass. Possible values include: Bypass Disabled, Bypassed By Disk, Bypassed By User, Bypassed By EMU.
Primary Execution State The state of the primary I/O process. Values: Running, Stopped Primary Process ID The process ID of the primary I/O process. If the state of the primary I/O process is Stopped, this ID is not displayed. Example: 1,296 Disk Pair Name The name and location of the mirrored disk. Example: Disk $DATA00-M (1.1.2). Disk Pair Primary Path Access State Indicates whether the primary disk path is active or inactive.
Abort Primary Path Terminates operation of the primary path to the disk. When the Abort action finishes, the path is in a Hard Down state. You must use the Reset Primary Path action before you can start the path again. Blink LED Off Turns off the blinking of the disk drive’s (amber) fault LED. SCF Equivalent: SCF Control SAC $ZZSTO.#sac-name, deviceid(shelf,bay), LED OFF Blink LED On Causes the disk drive’s (amber) fault LED to start blinking. SCF Equivalent: SCF Control SAC $ZZSTO.
Responsive Test Verifies that the disk drive is installed and responding. Save as System Load Configuration Specifies, within OSM, this disk as an alternate system load volume. For NonStop BladeSystem NB54000c and NB56000c only, if the action passes and a valid core license file is present in $SYSTEM, OSM offers to copy the license file copied to each new alternate system disk. You can specify up to four such alternate system load configurations.
Stop Backup Path Terminates the backup path to the disk. When the Stop action finishes, the path is in a Down state. If the disk drive is currently in use, a dialog box warns you and asks whether or not you want to continue with the action. Stop Disk Terminates all paths for this disk drive. When the Stop action finishes, the paths are in a Down state. If the disk drive is currently in use, a dialog box warns you and asks whether or not you want to continue with the action.
Actions Firmware Update Updates the firmware running on the SAS disk drive. Get Logical Disk(s) Retrieves the names of the logical disks configured for the physical disk in the SAS disk enclosure. Replace Launches a documented service procedure to replace a disk drive in a SAS disk enclosure. Set LED State Sets the LED on the physical disk in the SAS disk enclosure to On or Off. Show SMARTSSD Wear Gauge This action is available for Solid State drives only.
E4SA (Ethernet 4 ServerNet Adapter) An adapter that connects the ServerNet connections inside a server to an Ethernet local area network (LAN). The Ethernet 4 ServerNet Adapter (E4SA) CRU contains two Ethernet ServerNet addressable controllers (SACs), each of which contains two Ethernet physical interfaces, for a total of four Ethernet ports on each E4SA CRU. This Nonstop S-series component can be connected to a Nonstop NS-series system through an IOMF2 enclosure.
Enable ServerNet Port Enables the specified ServerNet router port on this CRU. Perform this action only as directed by OSM alarm repair actions. Parameter: Port Number Start Starts the Ethernet 4 ServerNet Adapter (E4SA) CRU and the associated Ethernet ServerNet addressable controller (ESAC). The E4SA CRU and the ESAC must be in the Stopped state before you perform this action. During startup, the controller operational code is automatically loaded into the ESAC.
Enclosure The Enclosure object is displayed in the OSM Service Connection (J-series only) to represent a HP BladeSystem c-Class Enclosure in an HP Integrity NonStop BladeSystem. There can be one or two enclosures in each NonStop BladeSystem.
Aggregate Status This represents the status of the c7000 enclosure, as seen by the OA. Possible Values: Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity In Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved.
Delete the Power Source Configuration Deletes a previously configured Configured AC or UPS backup power source and sets the specified Configuration attribute value to Not Configured. You must be logged on as super.super to perform this action. Display Diagnostic Status Errors Displays all diagnostic status errors for the Enclosure. Launch the Onboard Administrator Launches the Onboard Administrator (OA) management page. Prepare Enclosure for Removal Prepares the enclosure for removal.
Logical Logical Device Number The logical device number used by the operating system to identify the disk. Example: 7 Backup Path State The current state of the backup disk path. Values. Media Size The total size (in kilobytes) of disk storage space. Active Path The path that is currently accessing the disk. Values: Primary, Backup, Mirror, Mirror Backup Primary Path State The current state of the primary disk path. Values.
Backup Execution State The state of the backup I/O process. Values: Running, Stopped Backup Process ID The process ID of the backup I/O process. If the state of the backup I/O process is Stopped, this ID is not displayed. Example: 1,285 Actions Abort Backup Path Terminates operation of the backup path to the disk. When the Abort action finishes, the path is in a Hard Down state. You must use the Reset Backup Path action before you can start the path again.
Start Volume Starts all paths for both the primary and mirror drives of this volume. Stop Backup Path Terminates operation of the backup path to the disk. When the Stop action finishes, the path is in a Down state. If the disk drive is currently in use, a dialog box warns you and asks whether or not you want to continue with the action. Stop Disk Terminates all paths for this disk drive. When the Stop action finishes, the paths are in a Down state.
Attributes External Disk Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Hardware Revision A code that identifies the generation of the component.
Backup Path SCSI ID An identification number assigned to the device when configured. SCSI Controller A number (1 or 2) that identifies the backup SCSI controller that manages the disk. Example: SCSI Controller (1.1.50.2) Access State The accessibility of the backup path. Values: Inactive, Active Configured Controller Location The location of the backup disk path SCSI controller. Example: IOMF2.SAC-2.GRP-1.MOD-1.
action completes or is cancelled, the disk drive is not usable until you restore the file system by using the SCF Alter Label command. The action prompts you to specify an optional process priority for the action. If not specified, the current default priority is used. Firmware Update Updates disk drive firmware. Reset Backup Path Places the backup path in a state from which it can be started. Reset Disk Places the disk in a state from which it can be started.
Stop Primary Path Terminates the primary path to the disk. When the Stop action finishes, the path is in a Down state. If the disk drive is currently in use, a dialog box warns you and asks whether or not you want to continue with the action. Stop Volume Terminates all paths for the primary and mirror drives of this volume. When the Stop action finishes, the paths are in a Down state. Switch to Backup Path Switches processing from the primary to the backup path.
Example: Fan (1.1.22) Attributes Fan Service State Displayed in the Attributes tab and Attributes dialog box only if attention or service is required. Values Manufacturer Identifies the manufacturer of the component. Power State Whether the component is powered on. Values Enabled State The current state of the fan as known to the operating system. Values Physical Logical Rotations Sensor Normal Minimum Value The minimum acceptable fan speed is 1800 RPM.
Physical Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. NOTE: series. Not displayed for NS2100, NS2200 series, NS2300, or NS2400 Logical Device State The state of the fan as reported by OSM. Possible values include OK,FAN_CRITICAL_FAULT, etc. Actions None Fan (CLIM) A subcomponent of the CLIM.
Attributes Physical LED State Indicates whether or not the fan’s amber LED is lit. This state is determined by the Set LED State action. Value: On or Off Logical Device State The state of the component as known to the operating system on the server. Values Actions Set LED State Turns on or off the amber LED located on the fan. The current state is indicated by the LED State attribute. Fan (Processor Switch) One of two FRUs that provide cooling for the components in a processor switch.
Attributes None. Actions Replace Launches a documented service procedure to replace a fan in a SAS disk enclosure. Fan (VIO) A component of VIO enclosures (represented in the OSM Service Connection as VIO modules) that circulates air into the enclosure to help maintain optimal temperature. There are two fans in each VIO enclosure. Attributes Physical LED State Indicates whether or not the fan’s amber LED is lit. This state is determined by the Set LED State action.
Logical Device State The state of the FC Card as known to the operating system on the server. Possible values include: OK, Degraded, Fault, Power Off. Node WWN The World Wide Name (WWN) assigned to the node. Port WWN The World Wide Name (WWN) assigned to the port. Compare State Indication of the differences, if any, between the current and default BIOS versions. Values Default File Name The name of the file to be used for a BIOS update.
Physical LED State Indicates whether or not the FC-AL I/O Module’s (amber) fault LED is blinking. Value: Blinking or Off Type The vendor hardware type. Device State The state of the component as known to the operating system on the server. Values Vendor Hardware Revision A code that identifies the generation of the component provided by its supplier. Logical Device Connection Configured Controller Location The location of the configured FCSA connected to the FC-AL I/O Module. Example: FCSA.FSAC-1.
Attributes FCDM Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Manufacturer Identifies the manufacturer of the component. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Serial Number The serial number of the component assigned to it by the supplier of the component. Type The vendor hardware type.
Path A Configured Controller Location The location of FCSA connected to the disk drive through Port A. Example: FCSA.FSAC-1.GRP-111.MOD-2.SLOT-1 Fibre Channel Controller Identifies the FCSA FSAC connected to the FCDM through Port A. Example: FCSA FSAC (111.2.1.1) Actions Blink All LEDs Off Turns off the blinking of the fault LEDs on the FCDM, disks, FC-AL I/O module, power supplies, and fans.
Verify Path B Access Verifies that Path B from the FCDM via FC-AL I/O module B to the FCSA FSAC is responding. FCDM Collection The OSM Service Connection displays all Fibre Channel disk modules (FCDMs) within FCDM Collection objects, whether or not they are daisy-chained. FCDMs that are daisy-chained together (up to four) are displayed within the same FCDM Collection object. If an FCDM Collection object contains only one FCDM, it is not daisy-chained.
OSM does not display FCSA attribute information until an associated disk process is configured and started. For more information, see the Fibre Channel ServerNet Adapter Installation and Support Guide. Location in OSM Tree: System > Group > IOAM Enclosure > IOAM > FCSA Example: FCSA (13.3.1) Attributes FCSA Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Hardware Revision A code that identifies the generation of the component.
Replace Launches an interactive action to assist with replacement of an FCSA. Note: This replacement procedure is intended for authorized service providers only. When initiated, OSM checks for any connected paths that do not have a backup and warns you of any connectivity loss that could result from continuing with the action. OSM also directs you to the online help for precautionary guidelines for handling the hardware.
7. Grasp the FCSA by its handle while supporting the bottom edge of the FCSA with the other hand and pull the FCSA the rest of the way out of the slot. NOTE: 8. The FCSA weighs approximately 7.25 pounds (3 kilograms). Place the FCSA on the antistatic mat. Installing the Replacement FCSA NOTE: Whenever you handle a FCSA, follow standard operating practices to avoid damage to the equipment.
c. Firmly push the FCSA to the rear of its slot, but do not force it. CAUTION: To avoid damaging the connector pins, apply equal pressure to both the top and bottom of the FCSA when pushing it into its slot. If you try to push the FCSA into its slot when the pins in either the FCSA or the midplane are damaged, you must replace both the FCSA and the enclosure. d. 6. 7. Press down and back on the ejector. The ejector will slide under the top lip of the frame and secure the adapter in place.
Actions Responsive Test Verifies that the FCSA FSAC is present and responding. (To pass the test, a disk using this FSAC must be configured and started.) FESA (Fast Ethernet ServerNet Adapter) An adapter that connects the ServerNet connections inside a server to a 10/100Base-TX local area network (LAN).
Start Starts the Fast Ethernet ServerNet adapter (FESA) and the associated Ethernet ServerNet addressable controller (SAC). The FESA and the SAC must be in the Stopped state before you perform this action. During startup, the controller operational code is automatically loaded into the SAC. When the Start action completes, both the FESA and the SAC are in the Started state.
World Wide Port Name The name of the fibre channel port that connects the router to the FCSA. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. DHCP Setting Indicates whether IP address assignment by DHCP (for this router) is enabled or disabled. IPv4 Address The IPv4 address of the router. Currently supported model: M8201. ROM Version The version of the ROM on the router.
Attributes FSAC Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Track ID The track ID of the switch logic board. Part Number The part number of the switch logic board. Hardware Revision The hardware revision of the switch logic board. CRU Type The type of CRU this SAC is connected to. Values: SSAC, FSAC, SCSI Configured Type The type of storage device supported by this Fiber SAC.
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Configured Type The configuration type of this resource.
or, in a VIO enclosure: System > Fabric Group 100 > Internal ServerNet Fabric > VIO Module > G4SA > G4SA SAC > G4SA PIF Example: G4SA PIF $ZZLAN.G4SA1.0.A Attributes G4SA PIF Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Configured Interface Type Displays the configured interface, as specified by the Alter Interface Type action. Logical Values: Copper, Fiber, or Autodetect.
Start Starts the G4SA PIF. The PIF must be in the Stopped state before you perform this action. When the Start action completes, the PIF is in the Started state. Stop Rather than automatically stopping the G4SA PIF (as the Abort action does), this action first warns you if the PIF is currently in use (and stops it only after you confirm). G4SA SAC A ServerNet addressable controller mounted on a G4SA (Gigabit Ethernet 4-port ServerNet adapter) or the functional equivalent on a VIO G4SA.
Owning Processor The processor to which the G4SA SAC is connected. Processor Access List The currently available processors that can access the resource. Example: 0,1,4,8,9 Version The version of the boot firmware for the SAC. Default File Name The name of the file to be used for a (boot) Firmware Update. Default File Version The version of the firmware to be used for a (boot) Firmware Update. Compare State The differences, if any, between the current and default boot firmware versions.
The Gigabit Ethernet ServerNet Adapter (GESA) CRU contains one Gigabit Ethernet ServerNet addressable controller (SAC), which contains one Ethernet physical interface (PIF), resulting in one Ethernet port on each GESA CRU. Location in OSM Tree: System > Group > Module > GESA Slot Location: GESA CRUs can be located in slots 51, 52, 53, and 54 in IOMF2 enclosures (service side). Example: GESA $ZZLAN.GESA0 (1.1.
Group (IOMF2 or VIO) This type of group object contains either a legacy Nonstop S-series IOMF2 enclosure or, for NS16000CG or NS5000 only, VIO Modules used to provide a Versatile Ethernet ServerNet enclosure with 4 (V4SE) or 8 (V8SE) Gigabit Ethernet ports. Location in OSM Tree: Under System Examples: When the group contains a legacy Nonstop S-series IOMF2 enclosure, it has a 2-digit number, such as Group 11-16, 21-26, etc.
Group (IOAM, Fabric, G16SE) Depending on system type and configuration, this Group object may be displayed in OSM to represent: • IOAM Group • Fabric Group • G16SE Group IOAM Group An IOAM Group contains an I/O Adapter Module enclosure and FCDM Collection objects, which contain Fibre Channel disk modules (FCDMs) that are connected to this IOAM enclosure.
Hard Disk (CLIM) A subcomponent of the CLIM. For G2 and G5 CLIMs, there is only one hard disk object, located in Bay 1. For G6 and Gen8 CLIMs, there are two hard disks, located in Bay 1 and Bay 2. Location in OSM Tree: System > CLIMs > CLIM > Hard Disk Attributes Hard Disk Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Firmware Firmware Version The version of the firmware running on the CLIM hard disk.
Logical Device State The state of the InfiniBand HCA card as known to the operating system on the server. Possible values include: OK and Fault. Node GUID A text string displaying a globally unique identifier (GUID) for each InfiniBand HCA card, as assigned by the channel adapter vendor. It is obtained through an SNMP call.
Example: Internal ServerNet Y Fabric Attributes None. Actions Group Connectivity ServerNet Path Test You can perform this action on either the Internal ServerNet X Fabric or the Internal ServerNet Y Fabric. The action tests the links between SPs and ServerNet Switch Board maintenance entities (MEs) that provide ServerNet communication between groups on the system.
IOAMs are initially configured using the Configure Module action in the OSM Low-Level Link, as described in the NonStop NS-Series Hardware Installation Manual (available in the Hardware Service and Maintenance collection of NTL). IOAM names in OSM include the group number and a module number of either 2 or 3. For example, IOAM 13.2 is located in group 13, module 2. The other IOAM in this IOAM group is IOAM 13.3.
Attributes IOAM Enclosure Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Physical Location The values displayed by these attributes are assigned through the Set Physical Location action. Rack Name A user-defined name assigned to identify the rack in which the IOAM enclosure is located. You can enter up to 15 alphanumeric characters.
With T0682 H02 AAN and later, you can also use the Physical Configuration Tool to set the Rack Name and Rack Offset values in a consistent manner throughout the system while you create a physical view of your modular racks.
Other Rail Voltage The voltage of the Other Rail, which connects the IOMF2 CRU to the other power supply in the enclosure (to provide power in the event of a problem with the Main Rail power supply). Other Rail Voltage After Fuse The current voltage on the Other Rail of the IOMF2 CRU, measured after the fuse. Rail Maximum Voltage The maximum voltage limit (60 volts) for the IOMF2 CRU. Rail Minimum Voltage The minimum voltage (39.6 volts) that must be available to power the IOMF2 CRU.
Replace Launches the Replace IOMF guided procedure, which provides step-by-step instructions for replacing the IOMF2 CRU. Storage ASIC Initialization Test Prompts the storage subsystem manager process ($ZZSTO) to initialize the storage ASIC in the CRU. If initialization fails, an alarm is generated. This action is triggered automatically when a new CRU is inserted while OSM is running or when an (SCF) STATUS ADAPTER command is issued.
Logical Processor The OSM Service Connection displays Logical Processor objects for both HP Integrity NonStop BladeSystems (J-series software) and Integrity NonStop NS-series servers (H-series software); what OSM displays depends on the type of system: • For Integrity NonStop BladeSystems, OSM displays a Logical Processor object for each processor blade physically present in the Enclosure.
Processor Blade Valid only for NonStop BladeSystems, this attribute maps the Logical Processor to the Processor Blade it represents. Processor Freeze State Indicates whether the processor freeze state is enabled or disabled. Processor State (from ME) The state of the Logical Processor as seen by the Maintenance Entity (ME) of the associated ServerNet Switch Board. Values Processor Type The NonStop server type.
Enable Processor Freeze Turns the Freeze Enable flag on this processor on. If the OSM Low-Level Link System Freeze attribute is set to Enabled, a freeze-enabled processor might freeze if either another freeze-enabled processor halts, or the (Low-Level Link) system-level Freeze action is performed. Halt Terminates all processes running on this processor. Halting a processor does not affect any other processors in the system. CAUTION: Halting a processor might result in unrecoverable loss of data.
Maintenance PIC Located in slot 1 of a processor switch in NonStop NS-series servers that contain processor switches. Attributes Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. LED State Indicates whether or not the power supply’s amber LED is lit. This state is determined by the Set LED State action. Value: On or Off Model Identifies the plug-in card type as being a Maintenance PIC.
Firmware Revision The version of the firmware running on the switch. IPv4 Address The IPv4 address of the switch. Lines Connected Lists the port numbers of ports on the switch that have lines connected. Lines Disconnected Lists the port numbers of ports on the switch that have been disconnected (since the OSM server has been running).
Attributes Memory Card Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component.
Location action. This attribute is displayed only if a value is specied through the action. Temperature Sensor Current Value The current temperature, in degrees Celsius (°C), inside the enclosure of the module. Actions Rediscover Causes OSM to refresh and reanalyze all components within the module. Use this action in situations such as: • OSM does not recognize a new CRU following a CRU replacement. • An alarm remains after the alarm condition has been fixed.
error in the system. By default, systems are configured with one SAP located in the CIA for the group 11 I/O enclosure. You might need to set the Alarm Panel Identifier if the system has multiple SAPs, you add equipment to a system, or you move equipment from one system to another. Monitored Service LAN Devices Contains Maintenance Switch, Fibre Channel Router, UPS, and (Telco) Alarm Panel objects that you have configured OSM to monitor through the actions on this object.
Attributes None. Actions Replace Launches a documented service procedure to replace a CLIM motherboard. NIC (CLIM) A subcomponent of the CLIM. For Gen8 CLIMs, there are three types of NIC cards, as identified by the Model and Part Number attributes.
Replace Launches a documented service procedure to replace a NIC in a CLIM. Optical Extender PIC These (optional) Optical Extender PICs are used only in HP Integrity NonStop systems that include VIO enclosures (represented in the OSM Service Connection as VIO modules). Optical Extender PICs can be used as follows: • Slot 2 – for additional processor connectivity (processors 4 through 7) on NS14000 series, NS1000, NS1200, NS2000 series, NS2100, NS2200 series, NS2300, and NS2400 series servers.
Actions Power Off Shuts off power to the Optical Extender PIC. Power On Restores power to the Optical Extender PIC. Replace Launches a service procedure describing how to replace an Optical Extender PIC. Set LED State Turns on or off the amber LED located on the Optical Extender PIC. The current state is indicated by the LED State attribute. PCI Riser A subcomponent of the CLIM. Only one PCI Riser can be installed in G2, G5, and Gen8 CLIMs; up to two PCI Risers can be installed in G6 CLIMs.
Logical Connector Number A unique number used to distinguish between plug-in cards on an MSEB CRU. Actions Clear Loopback Test Clears the loopback test on a plug-in card (PIC). This action clears both the internal loopback test initiated by the Internal Loopback Test action and the external loopback initiated by the guided procedure for troubleshooting a ServerNet fabric.
NOTE: itself.
Values: Last Open Successful, No Open Attempted, Bad Parameter, Lobe Failed, Signal Loss, Insertion Timeout, Ring Failure, Beaconing, Duplicate MAC, Request Failed, Remove Received Link Pulse State Valid only for E4SA PIFs. A value of Up confirms that the cable from the PIF to the LAN is connected and operational. A value of Down indicates a problem with LAN connectivity. Actions Abort Terminates operation of the PIF. When the Abort action finishes, the PIF is in the Stopped state.
Temperature Sensor Normal Minimum Value The minimum acceptable air intake temperature is 5 degrees Celsius. If the temperature falls below 5 degrees, an alarm is generated. Current Value The current temperature, in degrees Celsius (°C), inside the enclosure of the module. Normal Maximum Value The maximum acceptable air intake temperature is 50 degrees Celsius. If the temperature rises above 50 degrees, an alarm is generated. Actions None.
Actions Replace Launches an interactive action to guide you through replacement of a power supply CRU. This action is applicable for IOMF2 and most PMF enclosures. It is not applicable for S7000 PMF or IOMF CRUs (in which the power supply is not a customer-replaceable unit). The steps include: NOTE: In DC-powered Telco systems, instead of having power supply units in slots 31 and 32, there are actually 4 TICs (in positions A1, A2, B1, and B2).
2. • Handle with care -- the power supply weighs approximately 5.6 kilograms (14 pounds). • Follow these standard operating practices when replacing CRUs: ◦ Replace only one CRU at a time. Attempting to replace more than one hardware component at a time might cause serious system outages, processor halts, and connectivity problems. ◦ Remove all jewelry and metal accessories, such as rings, watches, and necklaces, before working with the equipment.
3. Lower the ejector on the power supply to its fully open position. This action disconnects the power supply from the power interface board (PIB) and the AC power cord directly behind it. 4. With one hand, grasp the handle of the power supply and slide the power supply partway out of the slot. Using your other hand to support the weight of the power supply, slide the power supply all the way out of the slot. 5.
Installing the Replacement Power Supply 1. Lower the ejector on the replacement power supply to its fully open position. 2. With one hand, grasp the handle of the power supply. Use your other hand to support the weight of the power supply. Then slowly push the power supply all the way into the empty slot. Raise the ejector on the replacement power supply to its fully closed position. This action connects the power supply to the power interface board (PIB) and the AC power cord directly behind it. 3.
Physical Device State The state of the Blade Element Power Supply, as known to the operating system on the server. Possible values include OK, Fault, Power Loss, and Power Supply Fan Fault. Manufacturer Identifies the manufacturer of the component. Displayed for NonStop NS14000 series and NS16000 series servers only. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts.
Attributes Power Supply Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values LED State Indicates whether or not the power supply’s (amber) fault LED is blinking. Value: Blinking or Off Type The vendor hardware type. AC Power State Whether the power source is On or Off. Device State The state of the component as known to the operating system on the server.
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Serial Number The serial number of the component assigned to it by the supplier of the component. Type The vendor hardware type. Device State The state of the component as known to the operating system on the server.
Delete the Power Source Configuration Sets the Configuration > Power Supply attribute value to Not Configured. You must be logged on as super.super to perform this action. Power Supply (Processor Switch) One of two FRUs that supply power for the components in a processor switch. Attributes Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. LED State Indicates whether or not the power supply’s amber LED is lit.
powerfail-delay time interval specified for your UPS. For more information on preparing for AC power-fail scenarios, see the NonStop NS16000 Series Planning Guide. For more information on using the POWERFAIL_DELAY_TIME command to specify the Power-Failure-to-Shutdown time interval, see the SCF Reference Manual for the Kernel Subsystem. Delete the Power Source Configuration Sets the Configuration > Power Supply attribute value to Not Configured. You must be logged on as super.super to perform this action.
Attributes VIO Power Supply Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Manufacturer Identifies the manufacturer of the component. Displayed for VIO power supplies in S-series VIO modules only. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Device State The state of the component as known to the operating system on the server.
NOTE: This action is not valid for a power supply unit in an S-series VIO Module. Delete the Power Source Configuration Sets the Configuration > Power Supply attribute value to Not Configured. You must be logged on as super.super to perform this action. NOTE: This action is not valid for a power supply unit in an S-series VIO Module. Replace Displays a service procedure describing how to replace a power supply in a VIO enclosure. Processor (CLIM) A subcomponent of the CLIM.
Attributes Processor Blade Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Product Name The product name of the component as assigned by the manufacturer. Replacement Part Number The replacement part number of the component.
NOTE: With T0682 AAN and later, OSM saves a copy of each Blade Element's BMC event log to a file in $system.zservice and clears the BMC event log daily between 1 and 2 a.m. The log file name is the format blMMMSDD, where MMM is Blade Element's module number, S is slot number, and DD is date of the month. Retrieve Forward Progress Log Retrieves the Forward Progress Log (FPL), which is more detailed than the System Event Log.
PE (A/B/C) Reintegration Progress Displayed only if a PE reintegration is in progress, this attribute displays the progress in terms of percentage complete. NOTE: Displayed for NonStop NS14000 series and NS16000 series servers only. PE (A/B/C) Reintegration Status Indicates the status of the PE reintegration process.
LSU Optics Adapter NOTE: only. These attributes are displayed for NonStop NS14000 series and NS16000 series servers Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Serial Number The serial number of the component assigned to it by the supplier of the component.
Set LED State Sets these LSU LEDs to On or Off: • Optics adapter amber LED • Logic Board amber LED • ServerNet X Link LED • ServerNet Y Link LED • Serial ZX1 I/O Link A LED • Serial ZX1 I/O Link B LED • Serial ZX1 I/O Link C LED Set Physical Location Allows you to assign these Physical Location attributes for the LSU: • Rack Name is a user-defined name for the rack containing the LSU. You can enter up to 15 alphanumeric characters.
Each processor switch module contains these components: • A ServerNet switch board, located in slot 14 • Two power supplies, located in slots 15 and 18 • Two fans, located in slots 16 and 17 • A maintenance PIC, located in slot 1 in the back of the processor switch • A cluster PIC, located in slot 2 in the back of the processor switch • A crosslink PIC, located in slot 3 in the back of the processor switch • I/O PICs, located in slots 4-9 in the back of the processor switch • Processor PICs,
refers to the running of OSM incident analysis, which checks EMS event messages and creates alarms in OSM if certain conditions exist. Replace Launches an OSM guided procedure with step-by-step instructions for replacing the processor switch chassis or subcomponents. Retrieve Network Connectivity Info Displays remote IP addresses stored in the IPAUTH file of the processor switch.
Slot Location: SACs are located on the CRUs that might be installed in slots 53 and 54 in processor enclosures (service side) or in slots 51, 52, 53, and 54 in I/O enclosures (service side). Example: E4SA SAC $ZZLAN.E4SA0.0 Attributes SAC Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Physical The Physical attributes are displayed only when the SAC is a subcomponent of a CCSA.
Firmware Version The version of the boot firmware for the SAC. Default File Name The name of the file to be used for a (boot) Firmware Update. Default File Version The version of the firmware to be used for a (boot) Firmware Update. Compare State The differences, if any, between the current and default boot firmware versions. Values Actions Abort Terminates operation of the ServerNet Adapter ServerNet addressable controller. When the Abort action finishes, the SAC is in the Stopped state.
Logical Connected Enclosures A list of the SAS Disk Enclosure(s) to which the SAS card is attached. Compare State Indication of the differences, if any, between the current and default BIOS versions. Values Default File Name The name of the file to be used for a BIOS update. Default File Version The version of the firmware to be used for a BIOS update. Version The version of the BIOS running on the SAS card.
Attributes SAS Disk Enclosure Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Manufacturer Identifies the manufacturer of the component. Model The model number of the SAS disk enclosure that was assigned in manufacturing. Serial Number The serial number of the SAS disk enclosure. Physical Connected SAS Card-1 SAS Card The name of one of the two SAS cards to which this SAS disk enclosure is connected.
Default File Version The version of the firmware to be used for a firmware update. Version The version of the firmware running on the SAS disk enclosure. Actions Firmware Update Updates the firmware on the SAS Disk Enclosure.
The remaining IDs are for the device on the SCSI bus. SCSI Bus Number The bus to which the device is attached: Bus 1 or 2: Internal device Bus 3: External device Actions Responsive Test Verifies that the component is installed and responding. ServerNet Interface Card (Blade) A processor switch plug-in card (PIC) used to provide internal ServerNet connections for the Blade.
Attributes ServerNet Interface Card Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Model The product name of the ServerNet interface card. Physical Actions Replace Launches a documented service procedure to replace a ServerNet interface card in a CLIM. ServerNet PIC A processor switch plug-in card (PIC) used for internal ServerNet connections. ServerNet PICs are installed in slots 2 through 13 of the processor switch.
Actions Enable ServerNet Port Enables the specified ServerNet port on this PIC. Perform this action only as directed by OSM alarm repair actions. Each PIC contains two to four ports. Parameter: Port Number Power Off Removes power to the PIC. When a crosslink PIC is powered off or removed, the loss of ServerNet cluster traffic on a single fabric is expected. Other nodes in the cluster continue to communicate over that fabric.
Attributes Logical Connector Type Values include: QSFP, POP4, SFP, Snap12 Link Status Displays the status of this port. Values: Disabled, Neighbor Check In Progress, Enabled Neighbor Check Status Displays the status of the port to which this port is connected.
ME FPGA Version The VPROC of the ME FPGA (Field Programmable Gate Array) image currently loaded on the switch. Default File Name The full path name of the default ME FPGA file on the server. Default File Version The version of the ME FPGA image in the default FPGA file. Compare State The differences, if any, between the current and default ME FPGA versions. Values ME Firmware Version The version of the ME firmware running on the switch.
Soft Reset Reinitializes the firmware without affecting the ServerNet Switch hardware or the routing tables. Synchronize FIR Files to Other Switches Synchronizes the FRU information record (FIR) files of the X and Y fabric ServerNet switches. The files will be synchronized from the switch on which this action is executed to the other switch.
Logical Time of Last Reset The date and time of the last hard or soft reset of the ServerNet Switch Board. Fabric Side This attribute is displayed only within the Multi-Resource Actions dialog box, to indicate whether the ServerNet Switch Board is on the X or Y fabric. ME FPGA Version The VPROC of the ME FPGA (Field Programmable Gate Array) image currently loaded on the switch logic board. Default File Name The full path name of the default ME FPGA file on the server.
ME Firmware Update Allows you to update the firmware file for the Maintenance Entity (ME) of the ServerNet Switch Board. Power Cycle Power cycles the ServerNet Switch Board. Replace Launches the guided procedure to replace a ServerNet switch board in an IOAM or processor switch. NOTE: For an HP Integrity NonStop NS14000 or NS1000 system, the Replace action launches a documented service procedure describing how to replace a ServerNet Switch Board unique to that type of system.
Master SP Indicates whether this service processor is the master service processor on the system: Indicates whether this service processor is the master service processor on the system. The value will always be False on a legacy IOMF2 SP in an Integrity NonStop NS-series server. Running Image Source Indicates whether the SP firmware was loaded from its own (local), the peer's, or the backup flash memory.
Actions Reset Causes the service processor (SP) to reload the service processor operating image from the FLASH PROM. If the CLCI and CNSL (console) sessions are running through an SP that is reset, the session windows stop responding, and you must switch to the other paired SP by specifying the appropriate IP addresses. When you reset a master service processor (MSP), any LAN client connections to that MSP are terminated and must be reconnected by the client.
Default File Version The version of the firmware to be used for a Smart Array Controller firmware update. Version The version of the Smart Array Controller firmware running on the CLIM. Actions Firmware Update Updates the firmware running on the Smart Array Controller. Upon completion, OSM offers to reboot the CLIM, in order for the CLIM to start using the updated firmware.
Storage ASIC Initialization Test Prompts the storage subsystem manager process ($ZZSTO) to initialize the storage ASIC in the CRU. If initialization fails, an alarm is generated. This action is triggered automatically when a new CRU is inserted while OSM is running or when an SCF STATUS ADAPTER command is issued. If a CRU is inserted while OSM is not running, perform this action after logging on to the OSM Service Connection. Test Verify Performs basic tests on the CRU.
SCSI Extender A pair of SCSI extenders (one SCSI-to-Fiber extender and one Fiber-to-SCSI extender) can be used to increase the distance between the host system and any of these devices to a maximum of 10 kilometers: • 9840 cartridge tape drive • T525x Super DLT tape drive • 5242 DAT72 tape drive (all models) • Virtual tape subsystems (all models) • N152x LTO tape drives (all models) SCSI-to-Fiber Converter A Fibre Channel (scsi to fiber) converter is used to connect the following tape drives: • C
Process Pair Configured Processors The 2 processors in which this I/O process is configured to run. Example: 0,1 Primary Execution State The state of the primary I/O process. Values: Running, Stopped Primary Process ID The process ID of the primary I/O process. If the state of the primary I/O process is Stopped, this ID is not displayed. Example: 1,296 Backup Execution State The state of the backup I/O process. Values: Running, Stopped Backup Process ID The process ID of the backup I/O process.
Example: SWAN2 $ZZWAN.#SWAN2 Attributes SWAN $ZZWAN Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Hardware Revision A code that identifies the generation of the component.
Primary Host Connection Host Connection Point If the primary path of this SWAN concentrator is connected to a CLIM, this attribute is the name of the primary CLIM. If the primary path of this SWAN concentrator is connected to a PIF, this attribute is the location of the SLSA adapter containing the primary PIF. Format:$ZZCIP.CLIM_Name, (Group, Module, Slot) Example:$ZZCIP.
Location in OSM Tree: System > SWAN Collection > Battery Example: Battery $ZZWAN.#SWAN2.BAT Attributes Battery $ZZWAN Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Charge Status The charge status of the SWAN 2 battery. Values: Charging, Critical (Discharging), Unknown Device State The state of the component as known to the operating system on the server. Values Logical Actions None.
Physical The Physical attributes are displayed for SWAN 2 CLIPs only. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components.
Test Primary Path Access Tests two-way access to the communications line interface processor (CLIP) using the primary address Test Verify Runs the power-on self-test for the CLIP. The FAULT LED on the CLIP flashes during the test. If the test passes, the FAULT LED goes off. If the test fails, the FAULT LED remains on continuously.
Attributes LAN LB $ZZWAN Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Hardware Revision A code that identifies the generation of the component.
Example: $ZZWAN.#D08XE5.1.DLC0 DLC Task State The state of the data link control (DLC) task associated with the line as known to the operating system. Values: Starting, Started, Stopped, Unknown, and Indeterminate (CLIP is inaccessible). Actions External Loopback Test Performs the external loopback firmware diagnostic test. Start DLC Task Starts the data link control (DLC) task associated with the SWAN Line. When the Start action completes, the task is in the Started State.
Verify Logical Configuration Verifies that the SWAN Path is properly configured. If not, an Incorrect Logical Configuration alarm is generated on the SWAN Path. SWAN (Power Supply) Each SWAN 2 CRU has two customer-replaceable power supply subcomponents. Location in OSM Tree: System > SWAN Collection > SWAN > Power Supply Example: Power Supply $ZZWAN.#SWAN2.PS2 Attributes Power Supply Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Logical Current Topology The maximum processor configuration for the service processor. Values Power Regulator Management Supported Displayed only for NonStop BladeSystems, this attribute will show a value of True for an NB54000 series BladeSystem running a NonStop RVU that supports HP Power Regulator management; in all other cases, the value will be False. Power Regulator Management Status Displayed only the value of the Power Regulator Management Supported attribute is True.
Connection). You can specify up to four such alternate system disks; each one is displayed in the system attributes (under a separate System Load Configuration heading), and can be selected from the Configuration menu of the System Load dialog box in the OSM Low-Level Link. These configurations can be deleted by the system-level Delete System Load Configuration action. NOTE: With OSM Low-Level Link T0633 AAQ and later, you can also save system configuration files on the system console.
Collect Diagnostic Data This action collects diagnostic data for your system. Upon performing the action, you are prompted to specify date and time parameters. Based on the date and time specified: • Diagnostic events are collected for a period of 12 hours (configurable through OSMCONF file) before and three hours after the specified date and time. • Diagnostic Data files, such as ZZAAxxxx, ZZSNxxxx, and ZZPSxxxx, are collected for a period of three hours starting from the specified date and time.
Two attributes under the Logical attributes heading on the System object, Power Regulator Management Supported and Power Regulator Management Status, indicate whether this feature is available and enabled. Insight Control power management is an HP SIM plug-in that can be installed after HP SIM is installed on the system console. Both HP SIM and Insight Control power management can be installed from HP Insight Control for NonStop DVD.
NOTE: The list of system types or configurations for which this action must be performed may grow as other hardware and/or memory configurations requiring blade software beyond the base versions required for NS16000 and NS14000 become available. Install Core License File Valid only for NonStop BladeSystem NB54000c and NB56000c, this action launches a guided procedure to install core license files.
After clicking "Yes" to three confirmation dialog boxes and OSM reports that the action has completed successfully, check the OSM event viewer session opened earlier to locate CMAP event 135 (CMAP started reinitialization) and a corresponding CMAP event 136 (CMAP completed reinitialization) for each logical processor running NSK. Reinitialization for each processor is complete when the CMAP event 136 appears.
For more information, see Insight Remote Support Advanced for NonStop, located in the Support and Service collection of NTL. Unsuppress Problem Incident Report Creation Removes suppression caused by the Suppress Problem Incident Report Creation action. While this suppression is automatically unsuppressed when the specified suppression time has been reached, you can choose to end the suppression immediately using this action.
Actions None. Tape Specifies a tape drive configured for a system. All tape drives are displayed under the Tape Collection object, whether they are attached through Fibre Channel ServerNet adapters in IOAM enclosures or through legacy NonStop S-series IOAM2 enclosures.
Physical Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. This is not the spare part number. Serial Number The serial number of the tape drive (where applicable). Process Pair Configured Processors The two processors in which this I/O process is configured to run. Example: 0,1 Primary Execution State The state of the primary I/O process.
CLIM Path Configured CLIM The CLIM to which the tape drive is configured. HBA Location Indicates the slot and port location for the HBA controller (either SAS or FC). LUN The logical unit number of the tape. Actions Responsive Test Verifies that the component is installed and responding. Start Puts the tape process in a state to accept regular I/O commands to the tape drive. When the Start action completes, the drive is in the Started state.
Test Verify Runs the power-on self-test for the tape drive. Additionally, runs tests to isolate problems involving the tape drive, SAC, or Common Base Board. The tape drive must be in the Stopped state to perform this action. TRSA (Token Ring ServerNet Adapter) A customer-replaceable unit (CRU) that connects the ServerNet connections inside a server to a Token Ring LAN. The TRSA CRU contains one Token Ring ServerNet addressable controller (TRSA SAC).
Stop Rather than automatically stopping the TRSA (as the Abort action does), this action first warns you if the TRSA is currently in use (and stops it only after you confirm). Unknown CRU If a service processor cannot identify a system resource, that resource is represented by an object in the tree pane. That object icon features a blue question mark.
Software Version Displays the version of the UPS software. UPS Location Displays the physical location of the UPS as set by the super-user in the Link to Web Interface action. VA Rating This is the apparent power rating of the UPS, expressed in Volt-Amperes. Example: 12000 VA Physical Location The values displayed by these attributes are assigned through the Physical Configuration Tool. Rack Name A user-defined name assigned to identify the rack in which the UPS is located.
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Flash Firmware Information about the version of the operational firmware located in the Flash memory of the FCSA.
VIO G4SA In an Integrity NonStop NS-series system containing VIO enclosures (represented in the OSM Service Connection as VIO modules), OSM displays a G4SA object to represent: • In slot 6, the Ethernet ports that provide the functional equivalent of a Gigabit 4-port Ethernet adapter. • In slot 7, an optional expansion VIO G4SA.
Actions Abort Terminates operation of the VIO G4SA and the associated Ethernet ServerNet addressable controller (SAC). When the Abort action finishes, the VIO G4SA and the SAC are in the Stopped state. Add This action is displayed in OSM only when a VIO G4SA is first inserted and not yet configured. Performing this action ensures that the Configured Type is set to G4SA. Delete Deconfigures the VIO G4SA, removing the associated G4SA SAC and PIF objects.
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. LED State Indicates whether the VIO logic board LED is on or off. Manufacturer Identifies the manufacturer of the component. Displayed for VIO logic board in S-series VIO modules only. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts.
Hard Reset Resets the VIO logic board hardware and the routing tables. ME FPGA Update Allows you to update the FPGA code file for the integrated maintenance entity (IME) of the VIO logic board. The firmware file for IME FPGA (SAM0789) is different from that of other MEs.
For more information, see the G16SE Service Provider Supplement for Integrity NonStop BladeSystems. Each VIO Module object, depending on the type of system and configuration, contains: • VIO FCSA in slot 1 -- OSM displays an FCSA object to represent the four built-in Fibre Channel ports that provide the functional equivalent of an FCSA. NOTE: • Valid for NS14000 series, NS1200, and NS1000 servers only. (Optional) Optical Extender PIC in slot 2 for additional processor connectivity (processors 4-7).
Physical Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. Track ID A unique serial number that identifies the component. Track IDs are used for tracking components. Physical Location The values displayed by these attributes are assigned through the Set Physical Location action.
With T0682 H02 AAN and later, you can also use the Physical Configuration Tool to set the Rack Name and Rack Offset values in a consistent manner throughout the system while you create a physical view of your modular racks. Synchronize FIR Files to Other Switches Synchronizes the FRU information record (FIR) files of the X and Y fabric processor switches. NOTE: This action is only valid from Group 100; it will fail on VIO Modules in NonStop BladeSystem NB54000c and NB56000c or S-series.
Compare State (Other) Value Meaning Same Current and default versions are the same. Up-rev The current version is newer than the default version. Down-rev The current version is older than the default version. Unknown Unable to compare files. Device State Value Meaning Aborting Processing is terminating. AC Power Loss The device is currently not powered by either AC or UPS. Defined State is defined by the NonStop OS. Degraded Performance is degraded.
Group Type A unique number in the system that identifies this group. Group Type is displayed in a window on the front door of the enclosure.
Powered On Meaning Redundant Power Problem There is a problem with the backup power supply for this component (as determined by the Redundant Power Scrub action). Unknown Power state of component is unknown. Processor State Value Meaning Dump in Progress Memory is being dumped from this processor. Submit memory dumps to the your service provider for problem analysis. Executing Diagnostics The processor is performing diagnostics.
Type System NSR-G S70000 NSR-T S72000 NSR-V S74000 NSR-X S76000 NSR-H S78000 NSR-Y S86000 NSR-Z S88000 NSE-A Integrity NonStop NS16000 server NSE-AB Integrity NonStop BladeSystem NB54000 NSE-AD Integrity NonStop NS2200 series server NSE-AE Integrity NonStop NS2100 server NSE-AF Integrity NonStop BladeSystem NB56000 NSE-AG Integrity NonStop NS2300 server NSE-AH Integrity NonStop NS2400 series server NSE-B Integrity NonStop NS1000 server NSE-D Integrity NonStop NS14000 server
Tape Types Product ID Meaning CT9840-1 9840 cartridge tape drive mounted in an L700 tape library CT9840-2 9840 cartridge tape drive mounted in a 9710 tape library CT9840-3 9840 cartridge tape drive mounted on HP NonStop S-series server CT9840-4 9840 cartridge tape drive mounted in a 9310 tape library CT9840FC-1 9840FC (Fibre Channel) cartridge tape drive mounted in an L700 tape library CT9840FC-3 9840FC (Fibre Channel) cartridge tape drive mounted on HP NonStop S-series server CT9840FC-4 9840
Product ID Meaning T5258ACL Super DLT tabletop with ACL T9490 STK 9490 cartridge drive VT5801 Virtual Tape Solution: Tributary Systems Inc. 2U VT5802 Virtual Tape Solution: Tributary Systems Inc. 7U VT5900-A Virtual Tape Solution: Tape Labs Inc. 7U VT5900-B Virtual Tape Solution: Tape Labs Inc. 7U VT5900-C Virtual Tape Solution: Tape Labs Inc. 7U VT5901 Virtual Tape Solution: Tape Labs Inc. 2U VT5902 Virtual Tape Solution: Tape Labs Inc.
12 Managing a ServerNet Cluster A ServerNet cluster is a collection of NonStop servers connected together using the ServerNet protocol. There are two generations of ServerNet clusters that utilize cluster switches for ServerNet cluster connectivity: • The first-generation ServerNet cluster is built around the HP NonStop Cluster Switch (model 6770) and can support up to 24 nodes. It is built using one of the star topologies (star, split-star, or tri-star).
In the View drop-down list, you can select different views of the ServerNet cluster: • The Physical view depicts the connections and resources within the ServerNet cluster. • The Inventory view lists the ServerNet cluster resources in tabular format. See also Using the Browser’s Find Feature. Monitoring a Cluster ServerNet cluster monitoring tasks include: • Viewing alarms for resources in a ServerNet cluster.
• Updating firmware and configuration for the 6770 cluster switch. Perform the Firmware Update and Configuration Update actions on the ServerNet II switch component. • Replacing components of a cluster switch using the Replace Switch guided procedure. To launch the guided procedure, navigate to the switch component and perform the Replace action. Performing actions on ServerNet cluster resources is similar to performing actions on resources within a server.
Updating ServerNet II Switch Configuration NOTE: You can change the configuration tag as part of the Update Configuration action. However, you normally do this only when you are changing to a different network topology for a ServerNet cluster. See Updating ServerNet Cluster Topology. To update ServerNet II Switch configuration: 1. In the tree pane of the OSM management window, expand the ServerNet Cluster resource and navigate to the Switch component of the Switch Module. 2.
External Slot Layer 11 12 13 Port Internal Router Port 2 5 5 1 3 7 2 4 7 3 1 7 4 2 7 1 2 8 2 1 8 3 4 8 4 3 8 1 1 9 2 2 9 3 3 9 4 4 9 Router Connections for Router Interconnect PICs External Slot Internal Router Port Slot 4 1 4 2 5 3 4 3 5 1 6 2 4 3 5 4 4 Slot 5 Router Connections in a Layered Topology 253
13 Cluster Resources A ServerNet cluster is built using one of several topologies. The resource objects displayed in the OSM Service Connection for a cluster differ depending on the topology of the ServerNet cluster. ServerNet clusters using one of the star topologies are built with the HP NonStop Cluster Switch (model 6770) and can support up to 24 nodes. ServerNet clusters using the layered topology are built around the HP NonStop ServerNet Switch (model 6780) and can support up to 64 nodes.
Attributes Switch Module Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Presence Whether the switch is installed and responding. Values: Present, Absent, and Unknown Locator User-assigned text that can be used to help identify the switch. The text is assigned by using the Set Locator action. Example: Switch On Left in 1205 Topology The network topology and ServerNet nodes supported by this 6770 switch.
Midplane Physical Primary AC Power State Whether the primary power source is On or Off. Backup AC Power State Whether the backup power source is On or Off. Part Number The part number of the switch module midplane. Presence Whether the switch module is installed and responding. Values: Present, Absent, and Unknown Track ID The track ID of the switch module midplane. Manufacturer Identifies the manufacturer of the component. Hardware Revision The hardware revision of the switch module midplane.
Responsive Test Tests the connectivity of the switch module from the local node. Set Locator Allows you to enter text to aid in locating or identifying the switch. This text is displayed as the Locator attribute. These ASCII characters cannot be used in the Set Locator field: =, +, &, or %. Also, copy and paste features do not work in this field. For more information, see Specifying a Cluster Switch Locator String. Parameter: Locator – Free-form text up to 64 characters long.
Attributes BladeCluster Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values BladeCluster Service ServerNet Cluster State The current state of the ServerNet Cluster subsystem on the local node. Values: Starting, Started, Stopping, Stopped, and Unknown SCF Equivalent: SCF STATUS SUBSYS $ZZSCL Logical Inter-Zone Distance Indicates whether the distance is Short-Haul or Long-Haul.
ServerNet Path Test on Y Fabric Runs a path test on the Y fabric, checking the local node's connection to the BladeCluster by testing the Y fabric between the local node and remote nodes. Set ServerNet Cluster State Starts or stops the ServerNet Cluster subsystem on the local node. Parameter: ServerNet Cluster State can be set to Stopped or Started.
Attributes Logical Expand Node Number The Expand node number of the local node. Value: 0 through 254 Node Name The Expand name of the local node. Node Position in the Zone The position of the local node in the zone. ServerNet Node Number The ServerNet node number of the local node. X Fabric Connection State The state of the connection from the local node to the remote node over the external ServerNet X fabric.
Y Fabric Connection #2 Port Name Identifies the Y2 port used for BladeCluster connectivity. X Fabric Connection #1 Port Name Identifies the X1 port used for BladeCluster connectivity. X Fabric Connection #2 Port Name Identifies the X2 port used for BladeCluster connectivity. Actions Generate ServerNet Statistics Generates an event containing the ServerNet statistics for the node.
Fabric Setting Whether the switch is configured for operation on the X fabric or the Y fabric. Values: X, Y, or Clear Presence Verification that the switch is installed and responding. Values: Present, Absent, Unknown Configuration Version The version of the configuration file currently loaded on the switch. Example: 1_5 Firmware Version The version of the firmware currently loaded on the switch. Example: 3_0_23 Actions None.
Backup Execution State The state of the backup SANMAN process. Values: Running, Stopped Backup Process ID The process ID of the backup SANMAN process. If the state of the backup SANMAN process is Stopped, this ID is not displayed. Example: 1,285 SNETMON Process Pair Primary Execution State The state of the primary SNETMON process. Values: Running, Stopped Primary Process ID The process ID of the primary SNETMON process. If the state of the primary SNETMON process is Stopped, this ID is not displayed.
ServerNet Local Node This object represents the system within a ServerNet cluster to which you are currently logged on. Location in OSM tree: Under the ServerNet Cluster Example: ServerNet Local Node \STARZ Attributes ServerNet Local Node Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Y Fabric Connection State The state of the connection from the local node to the remote node over the external ServerNet Y fabric.
Logical Y Fabric Connection State The state of the connection from the local node to the remote node over the external ServerNet Y fabric. Up: At least one of the processors on the local node can communicate with at least one processor on the remote node over the Y fabric. Down: No processor on the local node can communicate with any processor on the remote node over the Y fabric. Unknown: The state of the connection cannot be determined. Expand Node Number The Expand node number of the local node.
Attributes Switch Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values GUID A unique, read-only number stored in nonvolatile memory (SEEPROM) on a ServerNet II switch. The Globally Unique ID can be used programmatically to identify the switch. Fabric Setting Whether a switch is configured for operation on the X fabric or the Y fabric. Values: X, Y, or Clear Version The version of the firmware currently loaded on the switch.
SCF Equivalent: SCF ALTER SWITCH $ZZSMN, NEAREST { X | Y}, BLINK NONE Blink LED On Causes the LED to start blinking. SCF Equivalent: SCF ALTER SWITCH $ZZSMN, NEAREST { X | Y}, BLINK ALL Configuration Update This action updates the configuration for the ServerNet II switch component of the 6770 switch module. For more information, see Updating Cluster Switches. NOTE: If you are updating both firmware and configuration on the same cluster switch, you should always update the firmware first.
Attributes Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values LED State The state of the fault LED on the fan. Values: On, Off, Blinking Presence Whether the fan is installed and responding. Values: Present, Absent, Unknown Enabled State The initial state of the component at the time of discovery. Enabled: The component is operational.
Actions None. Switch Logic Board A circuit board that provides switching logic for the 6780 switch. The logic board connects to a panel on the front of the 6780 switch for operator and maintenance functions. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch Logic Board Example: Switch Logic Board (1020.1.14) Attributes Switch Logic Board Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Configuration Configuration Tag A parameter used by SCF and the guided procedures that allows SANMAN to select an appropriate switch configuration block (SCB) from the switch configuration library. The selected SCB is subsequently loaded on the specified switch. The configuration tag determines the position of the cluster switch in the topology and the ServerNet node numbers supported by the cluster switch.
FPGA Update Loads an FPGA code file from the local node to the switch logic board. For details, see the ServerNet Cluster 6780 Planning and Installation Guide. Optional Parameter: File Name—the name of the FPGA code file on the local node Syntax: $volume.subvolume Default value: $SYSTEM.SYSnn Hard Reset Hard resets the switch logic board. SCF Equivalent: RESET SWITCH, HARD Replace Invokes the Replace Switch Component guided procedure that helps to replace the switch logic board.
Logical Enabled State The initial state of the component at the time of discovery. Enabled: The component is operational. Disabled: The component is present but not operational. Device State Indication of whether the switch has a fault. Values: OK, Fault Actions Blink LED Off Turns off the blinking of the LEDs. Blink LED On Causes the LEDs to start blinking. Replace Invokes the Replace Switch Component guided procedure that helps to replace the switch PIC.
Disabled: The component is present but not operational. Device State Whether the power supply has a fault. Values: OK, Fault Actions Blink LED Off Turns off the blinking of the LEDs. Blink LED On Causes the LEDs to start blinking. Switch-to-Node PIC A plug-in card (PIC) on the 6770 switch module that connects to a ServerNet node. The last part of the name contains the port number where the PIC is located. Only the PICs in ports 0 through 7 of the switch are used for switch-to-node connections.
Actions Node Responsive Test Tests the connectivity on the external ServerNet fabric through this port. Switch Node Port On the 6780 switch, an external transceiver port that connects to a ServerNet node.These ports reside only on switch PICs in slots 6 through 9. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch PIC > Switch Port Example: Switch Port (1010.1.6.1) See also Router Connections for Switch Node Ports.
Transceiver Device State The initial state of the component at the time of discovery. Values: OK, Fault Transceiver Enabled State Whether the transceiver is enabled. Enabled: The component is operational. Disabled: The component is present but not operational. Fabric State The state of the external ServerNet fabric from the local node to the remote node connected via this port. Up: At least one of the processors on the local node can communicate with at least one processor on one of the remote nodes.
Unknown Presence Whether the PIC is installed and responding. Values: Present, Absent, Unknown Neighbor Switch PIC PIC Name The neighbor switch and PIC to which this PIC is connected. Example: Switch PIC $ZZSMN.X.1.8 (indicates that this PIC is connected to switch X1, PIC 8) Actions None. Switch Port An external transceiver port on a 6780 switch that connects to a 6780 switch in another zone or layer.
Connected to node Connected to switch with wrong numeric selector Connected to switch with invalid configuration version identifier Connected to wrong port Connected to different switch Connected to switch with incompatible configuration No response to Manage Port command from neighbor port Manage Port command not acknowledged (NACKed) from neighbor port Port enabled Invalid Unknown Current Speed The speed of the port in bits per second.
Logical Estimated Charge Remaining The percentage of charge remaining in the UPS batteries. Remaining Time The amount of time remaining (in minutes) that the UPS battery will provide power to the switch in the event that both the primary and backup rails lose power, or if the input voltage of the AC power source is not within the allowable range. Remaining Capacity Status The remaining capacity level in the UPS batteries.
Topology Supported Configuration Tags* OSM and Guided Procedures Display Value Split-star 0x10000 Max 16 nodes, nodes 1-8 (0x10000) 0x10001 Max 16 nodes, nodes 9-16 (0x10001) 0x10002 Max 24 nodes, nodes 1-8 (0x10002) 0x10003 Max 24 nodes, nodes 9-16 (0x10003) 0x10004 Max 24 nodes, nodes 17-24 (0x10004) Tri-star Port Connectivity Status Value Valid Only For Reset Link dead (Loss of optical signal) Link dead (Transceiver absent) No link alive Link alive, port disabled Link alive, port disable
14 Updating ServerNet Cluster Topology You can update a ServerNet cluster to support more nodes or to expand the geographical limits of the cluster. These topics provide guidance on the different types of topology updates: • To locate relevant information for your update, see Identifying Your Update Type. • If you need to add a node to a cluster without changing the topology, log on to the node using OSM, and perform the Add Node to ServerNet Cluster action.
These three methods are supported for updating to the split-star or tri-star topology: • Merging two star topologies to create a split-star topology • Merging a star topology with a split-star topology to create a tri-star topology • Merging three star topologies to create a tri-star topology The major steps in updating a topology are: 1. 2. 3. 4. 5. Review the planning information in the ServerNet Cluster Manual for your type of update.
11. Use OSM to monitor the connectivity on the X fabric for all the nodes and switches. Connectivity on the X fabric should be restored over time. Confirm that the original nodes of the cluster are visible. If necessary, resolve any connectivity problems by following the repair actions. 12. Disconnect any existing Y-fabric cables between the cluster switches. (If you are updating from a star topology, there are no existing cables between switches.) 13.
Cable Connections Between Star Groups Updating to the Split-Star Topology If you are updating to the split-star topology, connect the cables as follows: Cluster Switch Port Connects to Cluster Switch Port X1 8 X2 8 X1 9 X2 9 X1 10 X2 10 X1 11 X2 11 Y1 8 Y2 8 Y1 9 Y2 9 Y1 10 Y2 10 Y1 11 Y2 11 Updating to the Tri-Star Topology If you are updating to the tri-star topology, connect the cables as follows: Cluster Switch Port Connects to Cluster Switch Port X1 8 X2 10 X
Switch PIC Slot Port Connect to Switch PIC Slot Port X11/Y11 11 4 X12/Y12 11 4 X11/Y11 12 1 X13/Y13 12 1 X11/Y11 12 2 X13/Y13 12 2 X11/Y11 12 3 X13/Y13 12 3 X11/Y11 12 4 X13/Y13 12 4 X11/Y11 13 1 X14/Y14 13 1 X11/Y11 13 2 X14/Y14 13 2 X11/Y11 13 3 X14/Y14 13 3 X11/Y11 13 4 X14/Y14 13 4 X12/Y12 12 1 X14/Y14 12 1 X12/Y12 12 2 X14/Y14 12 2 X12/Y12 12 3 X14/Y14 12 3 X12/Y12 12 4 X14/Y14 12 4 X12/Y12 13 1 X13/Y13 13 1 X12/Y
Switch PIC Slot Port Connect to Switch PIC Slot Port X14 2 1 X24 2 2 X14 2 2 X24 2 1 X14 3 1 X24 3 2 X14 3 2 X24 3 1 Y Fabric Connections Between Two Zones This table lists the Y-fabric connections between two zones of a layered topology: Switch PIC Slot Port Connect to Switch PIC Slot Port Y11 2 1 Y21 2 2 Y11 2 2 Y21 2 1 Y11 3 1 Y21 3 2 Y11 3 2 Y21 3 1 Y12 2 1 Y22 2 2 Y12 2 2 Y22 2 1 Y12 3 1 Y22 3 2 Y12 3 2 Y22 3 1 Y13 2
Switch PIC Slot Port Connect to Switch PIC Slot Port X13 2 1 X23 2 2 X13 2 2 X33 2 1 X13 3 1 X23 3 2 X13 3 2 X33 3 1 X14 2 1 X24 2 2 X14 2 2 X34 2 1 X14 3 1 X24 3 2 X14 3 2 X34 3 1 X21 2 1 X31 2 2 X21 3 1 X31 3 2 X22 2 1 X32 2 2 X22 3 1 X32 3 2 X23 2 1 X33 2 2 X23 3 1 X33 3 2 X24 2 1 X34 2 2 X24 3 1 X34 3 2 Y Fabric Connections for Three Zones This table lists the Y-fabric connections for three zones of a l
Switch PIC Slot Port Connect to Switch PIC Slot Port Y21 3 1 Y31 3 2 Y22 2 1 Y32 2 2 Y22 3 1 Y32 3 2 Y23 2 1 Y33 2 2 Y23 3 1 Y33 3 2 Y24 2 1 Y34 2 2 Y24 3 1 Y34 3 2 Cable Connections in a Layered Topology 287
Index Symbols 4PSE, 78 actions, 78 attributes, 78 6770 Switch Module about, 254 actions, 255 attributes, 255 6780 Switch Module about, 255 actions, 256 attributes, 255 A AC Transfer Switch about, 257 actions, 257 attributes, 257 Access Control List, 66 actions automatically initiating, 68 controlling access, 66 detailed information about, 68 on multiple resources, 69 performing, 66 performing on a resource, 68 saving details, 71 stopping, 68 summary of, 74 viewing details, 71 Add Node to ServerNet Cluster,
CLIM-Attached Disks, 102 CLIMs, 133 CLIMs (container object), 99 Cluster about, 262 actions, 263 attributes, 262 cluster of Key Managers, cluster resources list of, 254 locating, 249 managing, 254 monitoring, 250 performing actions on, 250 viewing, 249 cluster switch specifying location, 251 cluster topology updating, 280 CMAP, reinitialize, 226 Collect CLIM Logs, 100 Collect CLIM Logs action, 98 Collect Diagnostic Data, 224 Common Communication ServerNet Adapter see CCSA CRU Compare HSS Firmware Versions,
about, 138 attributes, 138 FCSA about, 138 actions, 139, 235 attributes, 139, 234 removing and installing, 140 FCSA FSAC about, 142 actions, 143 attributes, 142 FESA about, 143 actions, 143 attributes, 143 Fiber, 144 Fiber ServerNet Addressable Controller see FSAC Fibre Channel Router about, 144 actions, 145 attributes, 144 firmware updating, 76 Firmware update Switch Logic Board, 270 firmware updates performing, 71 FPGA code update Switch Logic Board, 271 FSAC, 113 about, 145 actions, 146 attributes, 146
Logical Processor State, 162 M Maintenance PIC about, 165 actions, 165 attributes, 165 Maintenance Switch about, 165 actions, 166 attributes, 165 managing a system, 76 Memory Card about, 166 Module about, 167 actions, 168 attributes, 167 Monitored Service LAN Devices about, 169 actions, 169 Motherboard, 169 N NIC, 170 Node Connectivity ServerNet Path Test, 259 Node Responsive Test, 274, 275 NonStop Setup User Credentials, NSSuser, deleting, NSSuser, enter credentials, O Optical Extender PIC, 171 actions,
Read Core License File, 226 Rediscover System, 226 Rediscover System and ServerNet Cluster, 226 Redundancy State, 163 Register CLIMs with Key Managers (guided procedure), 102 register CLIMs, final step, Reinitialize Complex Manager, 226 Remote 6770 Switch about, 261 attributes, 261 Remote Node about, 264 actions, 265 attributes, 264 Replace, 257, 267, 271, 272, 278 Replacement Part Number, 190 Reset ServerNet Statistics, 258 Reset Statistics, 263 Responsive Test, 146 Restore CLIM Configuration action, 99 S
about, 219 actions, 220 attributes, 219 SWAN Path about, 220 actions, 220 attributes, 220 SWAN Power Supply see SWAN PS SWAN PS about, 221 actions, 221 attributes, 221 SWAN/SWAN2 CRU about, 213 actions, 215 attributes, 214 Switch Fan about, 267 actions, 268 attributes, 268 Switch Group about, 268 Switch Logic Board about, 269 actions, 270 attributes, 269 Switch Node Port about, 274 actions, 275 attributes, 274 Switch PIC about, 271 actions, 272 attributes, 271 Switch Port about, 276 attributes, 276 Switch P
VIO Logic Board about, 237 actions, 238 attributes, 237 VIO Module about, 239 actions, 241 VIO Power Supply actions, 186 W window printing, 51 X X Fabric Responsive Test, 261 X Fabric ServerNet State , 163 X.
15 Register CLIMs with Key Managers Guided Procedure Online Help Introduction The Register CLIMs with Key Managers Guided Procedure guides you through the process of registering storage CLIMs with a cluster of HP Enterprise Secure Key Managers (ESKMs) for the purpose of providing encryption on storage devices. Keys generated by the Key Managers help protect your storage data. NOTE: See the NonStop Volume Level Encryption Guide for steps that must be taken before performing this guided procedure.
All CLIMs to be registered must be selected and moved from the upper to the lower list using the Add or Add All buttons (the Ctrl key can be used to select multiple CLIMs). Remove or Remove All can be used to remove CLIMs from the list to be registered. Once all CLIMs to be registered have been moved to the lower list, click Continue to proceed to the next step of the guided procedure: Configuring a Key Manager Cluster.
You can define up to three tiers by providing the IPv4 addresses for Key Managers that are all members of the same Key Manager Cluster. At least two Key Managers should be specified in Tier 1. You are not required to enter Key Managers in Tier 2 or 3; however, you cannot skip over a tier. In order to enter Key Managers in Tier 3, you must also enter at least one in Tier 2. There is no maximum limit to the number of Key Managers defined in a tier.
Upon clicking the Check connectivity to all Key Managers button, the guided procedure checks the connectivity by attempting to log on to each Key Manager. The connectivity status for each Key Manager is reported in the column to the left of its IP address with a green check mark (for success) or a red "X" (for failure). Also, as each connection attempt is made, a running count of the passes and failures is reported in the Progress section of the dialog box.
In the top portion of the dialog box, the CLIM Client Group Name box displays the name ("NonStop") of the CLIM group created by the guided procedure (if not already created). Click Create User IDs/Passwords. The guided procedure then: • Verifies NSSuser logon information by attempting to logon to a Key Manager. If a logon failure occurs on the first Key Manager, the next Key Manager is attempted (and so on). If no Key Manager can be logged onto, an error message is displayed.
Using the Select the Local CA Dialog Box NOTE: The Select Local CA dialog box is displayed twice during the guided procedure if you choose to have your Client Certificates automatically created. To view the appropriate help topic when clicking the Help button on that dialog box: • If the text at the top of the dialog box is as pictured below, see Selecting the Local CA that Signed the Server Certificate.
Click Continue to proceed to the next step of the guided procedure: Selecting Certification Method and Creating Client Certificates. Selecting Certification Method and Creating Client Certificates Upon selecting the Local CA that signed the Server Certificate, the Server and Client Certificate dialog box is displayed.
• Creating Client Certificate Automatically – having the guided procedure create a client certificate for each CLIM automatically. • Using your own X.509 Certificate – whereby you supply information so that OSM can use an existing signed X.509 Certificate to each register CLIM. After making your selection, click Continue to proceed to the step of the procedure, depending on the option chosen.
Upon clicking Create CLIM Client Certificates, the guided procedure starts the process of creating the client certificates, including a private key and a cryptographically secure pass phrase for each of the CLIMs listed in the table. The selected Local CA will be used to validate the client certificate during the SSL handshake. As with other guided procedure operations, the status is reported for each CLIM and by a running total in the Progress section of the dialog box.
• The certificate must be added to the Default Trusted CA List in one of the Key Managers. For information on how to do this, see the NonStop Volume Level Encryption Guide. • OSM can only validate up to 128 bit certificates.
5. indicated by red italic text). You can correct the error and repeat the validity check, or go on to step 5 to complete the registration process for the CLIMs that did not fail the validity check. Click Continue to proceed to the final step of the guided procedure: Register CLIMs. CLIMs for which the validity check failed will be removed from the list of CLIMs to be registered; a pop-up dialog informs you of any such removals.
After each registration attempt, the success or failure for each CLIM is reported in the far left column (a green check mark indicates success, a red "X" indicates failure). The Progress section toward the bottom of the dialog box displays a running count of the passes and failures. Details for any error are available by clicking on the row of the CLIM reporting the error.
