OSM Service Connection User's Guide 527274-028 Part number: 527274-028 Published July 2008
Legal Notice © Copyright 2008 Hewlett-Packard Development Company L.P. 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....................................................................................25 About This Guide..................................................................................................27 Related Reading..................................................................................................29 1 Introducing OSM OSM Interfaces...............................................................................................................................
Windows Menu.......................................................................................................................................55 Help Menu.............................................................................................................................................55 Rediscover Shortcut Menu Item...............................................................................................................55 Using the Physical View...........................................
Viewing a Resource Summary....................................................................................................................85 10 Managing a System Locating and Viewing System Resources....................................................................................................88 Monitoring a System..................................................................................................................................89 Performing Actions on a System.......................
Disk..................................................................................................................................................101 Physical............................................................................................................................................101 Logical..............................................................................................................................................101 Process Pair.........................................
Responsive Test................................................................................................................................107 Spin Down........................................................................................................................................107 Spin Up............................................................................................................................................107 Start Backup Path................................................
Stop Primary Path.............................................................................................................................114 Stop Volume......................................................................................................................................114 Switch Process Pair...........................................................................................................................114 Switch to Backup Path..................................................
Fan (VIO)................................................................................................................................................123 Attributes.............................................................................................................................................123 Physical............................................................................................................................................123 Logical.........................................
Responsive Test................................................................................................................................131 FESA (Fast Ethernet ServerNet Adapter)...................................................................................................132 Attributes.............................................................................................................................................132 FESA.................................................................
G4SA SAC..............................................................................................................................................140 Attributes.............................................................................................................................................140 G4SA SAC........................................................................................................................................140 Logical................................................
Logical..............................................................................................................................................148 Storage ASIC....................................................................................................................................148 Actions.................................................................................................................................................148 Disable ServerNet Port.................................
Stop.................................................................................................................................................155 MIOE SAC...............................................................................................................................................156 Attributes.............................................................................................................................................156 MIOE SAC.........................................
Configure LIF....................................................................................................................................164 Start.................................................................................................................................................165 Stop.................................................................................................................................................165 PMCU....................................................
Power Supply (IOAM)...............................................................................................................................177 Attributes.............................................................................................................................................177 IOAM Power Supply..........................................................................................................................177 Physical........................................................
Attributes.............................................................................................................................................186 Logical..............................................................................................................................................186 Actions.................................................................................................................................................186 ServerNet Switch Board..........................
Attributes.............................................................................................................................................195 SWAN $ZZWAN................................................................................................................................195 Physical............................................................................................................................................195 Logical.......................................................
Attributes.............................................................................................................................................205 Power Supply....................................................................................................................................205 Physical............................................................................................................................................205 Logical..................................................
UPS.................................................................................................................................................214 Physical............................................................................................................................................214 Actions.................................................................................................................................................214 Link to Web Interface...............................
Synchronize FIR Files........................................................................................................................222 Write LCD Line..................................................................................................................................222 Common Attribute Values.........................................................................................................................223 Battery Charge Status..................................................
External ServerNet X Fabric...............................................................................................................244 Logical..............................................................................................................................................244 Actions.................................................................................................................................................244 Node Connectivity ServerNet Path Test........................
Switch Group...........................................................................................................................................253 Attributes.............................................................................................................................................253 Switch Group....................................................................................................................................253 Logical...............................................
Neighbor Switch PIC.........................................................................................................................261 Actions.................................................................................................................................................261 Switch Port..............................................................................................................................................262 Attributes.............................................
What's New in This Guide OSM Service Connection Suite version T0682G07 ABJ replaces ABM. For a complete list of new features, fixes, and known problems, see the T0682 softdoc. For the latest OSM configuration options, see the OSM Migration and Configuration Guide Recent OSM History OSM Service Connection Suite was updated to T0682G07 AAM to support using a V4SE or V8SE, which OSM displays under the VIO module object, as a replacement for a GESA on NonStop S-series servers. At G06.
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: • Get context-sensitive help by selecting a system resource object, action, or OSM management window area and pressing the F1 key. Help is also available from dialog box Help button.
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. • The NonStop S-Series Hardware Installation and FastPath Guide describes how to connect and configure a system console for use with OSM software.
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 Migration and Configuration Guide.
OSM Interfaces OSM Service Connection The OSM Service Connection is the primary OSM management component. You use the OSM Service Connection to log on and establish a connection with a NonStop server. From the Management window, you can manage the resources of your server. If your server is part of a ServerNet cluster, you can also manage cluster resources.
OSM Guided Procedure OSM Action Add Node to ServerNet Cluster (formerly Add Node to ServerNet Cluster Configure ServerNet Node) For Object System * Should be performed only by a trained service provider. NOTE: You must be logged on as a super-group user to perform OSM guided procedures. You can minimize the OSM Service Connection Management window, but must not close it.
What Changed From TSM to OSM New Look-and-Feel This section describes how the appearance of the OSM Service Connection is different from that of the TSM Service Application. • Tree pane tabs have been replaced by a view of both the system and the cluster in the tree pane. • A view pane drop-down list lets you select either a Physical or Inventory view. • The system-level physical view no longer allows you to change icon sizes.
This TSM feature... Is now performed by this OSM feature... Using the tree pane tabs to switch from system to cluster view Both system and cluster objects now appear in the tree pane at the same time. Monitoring system and cluster health by checking the system and cluster icons located on the tree pane tabs Icons indicating the health of the cluster and system appears in the overview pane.
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 S-Series Hardware Installation and FastPath Guide. To migrate from TSM to OSM, see the OSM Migration and Configuration Guide. This guide also describes how to configure and start OSM server-side processes. The NonStop System Console Installer CD includes the client software required for OSM use.
Installing OSM Components System Console-Based Components The NonStop System Console Installer Guide, available in NTL and provided in hard copy with the NonStop System Console Installer CD, describes how to install the OSM client components and other required HP and third-party software. Server-Based Components Installation of server-based OSM components is documented in the T0682 softdoc.
Using OSM in Conjunction with HP SIM HP Systems Insight Manager (SIM), which provides infrastructure management for all HP servers and storage, now supports the NonStop platform via a Web-Based Enterprise Management (WBEM) provided by OSM. HP SIM is capable of discovering NonStop systems, displaying and forwarding alarms generated by OSM, and collecting system and device data.
3 Configuring OSM Before using OSM applications to manage your system: • Configure the server using the OSM Low-Level Link. • Configure service provider access using the OSM Notification Director. • Configure the OSM Notification Director during OSM installation to run as a Windows Service, which allows it to run without requiring a Windows logon. For more information, see Installing OSM Components. 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.
Configuring Service Provider Access Use the OSM Notification Director to configure these service provider access components: Incident reports If you want your system console to receive incident reports from your server, use the Preferences tab in the System Configuration dialog box to designate the system console as either a primary or backup dial-out point.
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 45
Launching an OSM Service Connection 1. To initiate an OSM Service Connection session, either: • Open a new Internet Explorer browser window (but not from within a current browser window). In the Internet Explorer Address box, enter a system URL: http://system_IP_address:9990 (example: http://155.155.155.155:9990) http://system_host_name:9990 (example: http://himaxb.cac.cpqcorp.
OSM Service Connection Session Error Messages Server Undiscovered An OSM Service Connection session cannot be established until system discovery is complete. Close the browser session that generated the "Server Undiscovered" message, wait until discovery is complete and then establish a new OSM Service Connection session. Server Down An OSM Service Connection session cannot be established.
Using OSM Bookmarks To create OSM bookmarks, either: • If you have an existing TSM system list, the default home page launched by using the Start menu shortcut for the OSM Service Connection (and also for the OSM Event Viewer) automatically converts the TSM system list to bookmarks for accessing the systems through OSM (provided those systems are now running OSM server software).
Verifying the OSM Service Connection State Select Connection Status from the Summary menu. The Connection Status dialog box indicates the current state of all service connection processes. Each IP address listed is associated with a TCP/IP stack configured in the OSMCONF (OSM server configuration) file. OSM runs as a process pair for fault tolerance, which means the configuration file has two stacks configured by default.
Running Multiple Sessions You can run multiple sessions by: Using either of the methods described in Launching an OSM Service Connection 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 Management window appears after system discovery. It displays information about your local system and ServerNet cluster. The Management window contains 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. Tree Displays both system and cluster resources at the same time.
Management Window Example 52 Using the Management Window
Internet Explorer Menu Bar The Internet Explorer menu bar is not customized for the OSM application. For most OSM functions, use the OSM toolbar (located just 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. • Print the browser frame with focus.
OSM Toolbar Features and Menu Options In conjunction with the Management window, the OSM toolbar provides access to all OSM functions. Except for the Log On and Log Off buttons, all items on the OSM toolbar contain menus. 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.
Reload Configuration Settings Initiates the process of reloading your OSM server configuration settings. Select Reload Configuration Settings to put into effect any changes made to your OSMCONF file. A dialog will instruct you which OSM processes must be restarted for the reload to be complete. Create Bookmark Creates an entry in your Internet Explorer Favorites list for the system you are currently logged on to.
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. If the status of a resource is abnormal, a red or yellow triangle appears over it. For more information, see Interpreting Icons and Color.
Using the Inventory View The Inventory view contains a list of resources and select attributes. It is located in the view pane of the Management window. You can display an Inventory view of a ServerNet Cluster or a local system. You can select a resource in the Inventory view and display its attributes or alarms (if any) or perform actions on it. If an alarm is outstanding for the selected resource, a bell icon appears on the Alarms tab in the details pane when you select the resource.
Using Shortcut Menus The shortcut menu is available for all selectable system and cluster resources. These resources include the overview pane, tree pane, and the Physical and Inventory views in the View pane, as well as dialog boxes with selectable resources. To display a shortcut menu, right-click a resource. The shortcut menu for all resources contains these choices: Attributes brings up the Attributes dialog box for that resource. Alarms brings up the Alarms dialog box for that resource.
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 Indicators The color of the System Status icon in the view pane indicates the overall state of the system.
On the alarms tab and detail In the Alarm Summary Alarm Severity 60 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. For example, a resource might have lost fault tolerance. Minor A fault exists that does not affect service. Corrective action should be taken to prevent a more serious fault.
Using the Browser's Find Feature You can use your browser's Find feature to search the local system or ServerNet cluster for a resource. This feature is especially useful on large systems or clusters. To find a resource: 1. 2. 3. 4. 5. 6. In the tree pane, select System or ServerNet Cluster, depending on the type of resource you want to find. From the view pane drop-down list, select Inventory.
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 Tab The details pane displays attribute and alarm information about a selected resource, depending on which tab you select. If there are any alarms for a selected resource, a bell icon appears on the Alarms tab. The Alarms tab provides this information about the selected alarm: • Alarm severity The Severity column contains a colored icon corresponding to the severity of the alarm. Red icons represent Critical and Major 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.
Viewing Alarm Details The Alarm Detail dialog box provides this information about the selected alarm: • Name of the resource associated with the alarm • Whether the alarm is dialed out to your service provider (assuming your system console is configured to dial out) • Time and date the alarm occurred • Alarm type and severity • Probable cause and description of the alarm • Repair actions To save alarm detail and repair information: Click Save.
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. To suppress an alarm: Right-click an alarm in either the Alarms tab, Alarms dialog box, or the Alarm Summary dialog box and select Suppress. (In the Alarms dialog box or the Alarm Summary dialog box, you can also highlight the alarm and click the Suppress button.). To undo the alarm suppression, select Unsuppress.
Deleting Alarms To delete an alarm, right-click the alarm in either the Alarms tab, Alarms dialog box, or the Alarm Summary dialog box and select Delete. (In the Alarms dialog box or the Alarm Summary dialog box, you can also highlight the alarm and click the Delete button.
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.
Using the Details Pane to View Attributes The details pane displays information about a selected resource. The type of information displayed depends on which tab is selected in the details pane: 1. 2. 70 In either the tree pane or the view pane, select a resource. In the details pane, click the Attributes tab to display the attributes for the selected resource.
Using the Attributes Dialog Box to View Attributes The Attributes dialog box displays the attributes associated with a selected resource and allows you to display the actions that you can perform. Any problematic attribute that might require attention is preceded by a colored icon. Yellow indicates a warning, and red indicates a critical state. To show actions for a resource: Click Show Actions to display the Actions dialog box for the resource.
Suppressing Problem Attributes 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 problem attribute. Problem attributes are those displaying yellow or red flags next to the attribute name. To suppress a problem attribute: Right-click a problem attribute in either the Attributes tab or Attributes dialog box and select Suppress. To undo the attribute suppression, select Unsuppress.
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.
Performing Actions on a Selected Resource Use the Actions dialog box to perform actions on a selected resource in the server or ServerNet cluster. Actions for the selected resource appear in the Available Actions list. For a description of a particular action, highlight the action and press the F1 key. A history of actions performed on the resources within the last eight hours appears in the Action Status list. (Eight hours is the default, which is configurable.) To reach the Actions dialog box: 1.
Performing Actions on Multiple Resources of the Same Type Use the Multi-Resource Actions dialog box to perform an action on a group of resources of the same type. The dialog box allows you to select the resource type. All resources of that type appear in an available resources list, and actions for the selected resource type appear in the Action drop-down menu.You can select an action and then select specific resources on which to perform the action.
Selecting a Saved Resource View 1. 2. From the Display menu on the OSM toolbar, select Resource Views and then the name of the previously saved resource view you want to view. (Within the Multi-Resource Actions dialog box, you can also select a previously saved resource view from the Configuration list.) The Multi-Resource Actions dialog box is displayed. Only the resources specified in the saved resource view appear under Resource Types. Deleting a Resource View 1. 2. 3.
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.
Performing Firmware Updates To update down-rev firmware for a specific resource, use one of the actions available for that resource. Performing a Firmware Update 1. 2. 3. 4. Select Display>Multi-Resource Actions. From the Resource Type drop-down list, select the type of resource on which to perform the firmware update. All resources of the selected type appear in the available resources list. From the Action drop-down menu, select the action to perform.
Launching Guided Procedures For a list of available guided procedures, see OSM Guided Procedures.
9 Viewing Summary Reports You can view a: • Problem Summary • Summary of Actions • Summary of Alarms • Resource Summary 81
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.
Viewing a Summary of Actions The Action Status Summary displays a summary of all actions in progress and actions that have taken place in past 24 hours. Information for each action includes resource name, action name, action status, and progress of the action. You can also view detailed information about each action. Actions Not Displayed The Rediscover action is not reported in the Action Summary dialog box.
Viewing a Summary of Alarms The Alarm Summary displays a list of alarms in the server or ServerNet cluster. The dialog box allows you select individual alarms for the resource and display detailed information and repair actions that you can perform to correct them. You can use the Alarms dialog box to view the alarms for a single resource, as described in Viewing the Alarms Dialog Box.
Viewing a Resource Summary Use the Multi-Resource Actions dialog box to build a summary of any collection of resources of the same type: 1. Select Display>Multi-Resource Actions. 2. From the Resource Type list, select a resource to display all resources of that type. 3. To perform an action on any of the resources, see Performing Actions on Multiple Resources of the Same Type.
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. 88 Expand the system resource in the tree pane to see its resources. In the View drop-down menu, you can select different views of the system: • The Physical view depicts the resources within the system. • The Inventory view lists the resources within the system in tabular format.
Monitoring a System System monitoring tasks include: • Viewing alarms for resources in the system. Look for alarm bell icons and red and yellow triangle icons. These icons appear in the Management window and Alarm dialog box identifying which resources need operator attention or some other type of service. See Viewing a Summary of Alarms. • Viewing the attributes of a selected resource in the system.
Performing Actions on a System With System selected in the tree pane drop-down list, you can access and perform actions on resources within a system. To perform an action on a system, select System in the tree pane and then navigate to the system resource on which you want to perform an action. See Performing Actions.
Updating Firmware You can update firmware for many resources, including the service processor, selected resources, and the cluster switch. See Performing Firmware Updates.
11 System Resources Using OSM, you can monitor and maintain these system resources: ATM Adapter G4SA SAC SCSI Controller ATM Line Group (I/O or Processor Enclosure) SEB Battery Group (IOAM) ServerNet Switch Board Blower (FCDM) Internal ServerNet Fabric SSAC CCSA IOAM SNDA Disk IOAM Enclosure Service Processor Disk (Fibre Channel) IOMF Storage Router E4SA IOMF2 SWAN / SWAN2 EMU LIF SWAN Battery ESS Disk Maintenance Switch SWAN CLIP ESS Disk Collection MIOE SWAN Collection Ext
ATM3SA (ATM Adapter) A customer-replaceable unit (CRU) that connects the ServerNet SAN inside a server to an Asynchronous Transfer Mode (ATM) network through a logical connection known as an ATM line. Each ATM CRU contains one ATM line. Slot Location: ATM CRUs can be located in slots 53 and 54 in processor enclosures (service side) or in slots 51, 52, 53, and 54 in IOMF or IOMF2 enclosures (service side). Example: ATM3SA (12.1.
Default Firmware Filename The name of the file to be used for a firmware update. Default Firmware File Version The version of the firmware to be used for a firmware update. Compare State Indication of the differences, if any, between the current and default firmware versions. Values Actions Abort Terminates operation of the ATM CRU and the associated ATM line. When the Abort action finishes, the ATM CRU and the ATM line are in the Stopped state. Firmware Update Updates the ATM adapter firmware.
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. Location in OSM Tree: System > Group > Module > ATM3SA > Line Example: Line $ATM (1.1.54) Attributes Line $ATM Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Logical Maximum Number of VPCs The maximum number of virtual path connections (VPCs).
Battery The battery customer-replaceable unit (CRU), located in Nonstop S-series 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 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.1.
Actions Enable/Disable Prepares the battery to supply power when AC power is unavailable. The battery must be enabled to remain charged.
Blower (FCDM) A subcomponent of an FCDM. There are two blowers in each FCDM. Each blower is mounted on a power supply and cools the enclosure by circulating air through the enclosure and the elements. The rate at which air moves (the air flow) determines the amount of cooling and is a function of blower speed (rpm). These blowers, under the control of the EMU or the associated power supply, can operate at multiple speeds.
CCSA (Common Communication ServerNet Adapter) An adapter that allows PCI-based communications devices to connect to a server. A CCSA CRU can hold up to four CCSA ServerNet addressable controllers (SACs) with four ports each, providing up to 16 links per adapter. Location in OSM Tree: System > Group > Module > CCSA Example: CCSA $ZZLAN.CCSA1 (2.1.53) Attributes CCSA Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Disk An internal 3.5-inch hard disk drive. Each disk drive connects to one of two SCSI buses on either a (PMF), IOMF) or an IOMF2 CRU. Disk CRUs can be located in slots 01 through 08 and slots 11 through 18 in processor and I/O enclosures (appearance side). SCSI terminators are in slots 09, 10, 19 and 20, for a total of 16 available disk slots. Location in OSM Tree: System > Group > Module > Disk Example: Disk $SYSTEM-P (1.1.
Firmware Version The version of the firmware running on the disk. 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.
NOTE: Contrary to the generic dialog text, for disk firmware you must specify the firmware source file path (established in Step 1). Because disk firmware versions vary, OSM does not use a default file name. If you do not specify a valid file path, the action fails. 6. 7. Enter the firmware source file path (established in Step 1) and click OK. Restart the disk or disks. Power Off Removes power to the disk drive. Power On Restores power to the disk drive.
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. 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.
Disk (Fibre Channel) A Fibre Channel disk that resides in a Fibre Channel disk module (FCDM). Location in OSM Tree: System > Group > FCDM Collection > FCDM > Disk Example: Disk (111.211.1.3) 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 Physical Device State The state of the component as known to the operating system on the server.
Disk Pair Disk Pair Name The name and location of the mirrored disk. Example: Disk $DATA00-M (1.1.2). Primary Path Access State Indicates whether the primary disk path is active or inactive. Configured FSAC Location Displays the configured location of the FCSA FSAC containing the primary disk path controller. This attribute is displayed even if the physical FCSA FSAC is not present. Example: FCSA.SAC-1.GRP-111.MOD-2.SLOT-2 FSAC Identifies the primary FCSA that manages the disk.
Disable Drive Bypass Opens up the specified port or ports (A and/or B) on the disk drive for use. Enable Drive Bypass Shuts down the specified port or ports (A and/or B) on the disk drive. Firmware Update Updates firmware for the Fibre Channel disk drive. This action can be performed only when both Primary and Backup paths are in the Down state. Replace Displays the procedure for replacing the disk. Reset Backup Path Places the backup path in a state from which it can be started.
Start Volume Starts all paths for both the primary and mirror drives of this volume unless they are in a Hard Down state. Disk paths in a Hard Down state require a reset action first (either Reset Disk, Reset Primary Path, or Reset Backup Path as appropriate). 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.
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.
Stop Rather than automatically stopping the E4SA (as the Abort action does), this action first warns you if the E4SA is currently in use (and stops it only after you confirm).
EMU The Environmental Monitoring Unit (EMU) is a subcomponent of a FCDM. Location in OSM Tree: System > Group > FCDM Collection > FCDM > EMU Example: EMU (111.211.1.99) Attributes EMU Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Type The vendor hardware type. Device State The state of the component as known to the operating system on the server.
ESS Disk Enterprise Storage System disk drive. ESS disks are visible in the tree pane and in the Inventory view of the Management window. In the tree pane, expand the ESS Disk Collection object to see the individual ESS disk drives. In the Inventory view, each ESS disk drive is listed on a separate line. ESS disk drives are not visible in the Physical view. ESS disks connect to your system through FCSAs in I/O Adapter Module enclosures.
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.
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. 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.
ESS Disk Collection Contains all ESS Disks that are connected to the system. Location in OSM Tree: Under System Example: ESS Disk Collection Attributes None.
External Disk An external disk drive that connects to a system through the ServerNet/DA CRU. The External Disk CRU is housed in an 8-slot disk enclosure that is physically connected to a Fiber SAC (ServerNet addressable controller) mounted on the ServerNet/DA CRU. External disks are visible in the tree pane and in the Inventory view of the Management window. In the tree pane, expand the External Disk Collection to see the individual external disk drives.
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.
Reset Disk Places the disk in a state from which it can be started. This action might be necessary if the disk was in a STOPPED state, substate HARDDOWN; a hardware error has occurred; the disk was stopped with an ABORT command; or a STOP or ABORT fails to put the disk into the STOPPED state, substate DOWN. Reset Primary Path Places the primary path in a state from which it can be started. Reset Volume Places the volume in a state from which it can be started.
You can perform the Validate Checksum action while the disk drive is in use.
External Disk Collection When one or more external disks are connected to a system, an External Disk Collection object appears in both the tree pane and the overview pane of the OSM Service Connection. In both panes, this object displays an alarm or yellow icon if alarms or degraded conditions exist on any of the individual external disks contained within. You can expand the External Disk Collection icon in the tree pane (but not in the overview pane) to select and monitor individual external disks.
Fan A component that circulates air into the enclosure to help maintain optimal temperature. Each system enclosure contains two fans, and each fan is connected to one processor multifunction ( PMF) CRU. Location in OSM Tree: System > Group > Module > Fan Slot Location: Fan CRUs are located in slots 25 and 26 on the appearance side of processor enclosures.
Fan (IOAM) An IOAM component that circulates air into the enclosure to help maintain optimal temperature. There are two fans in each IOAM, for a total of four in each IO enclosure. NOTE: If a ServerNet switch board is not present, the IOAM fans will not appear in OSM. For information on how to replace an individual IOAM Fan, see Replacing a Fan in an IOAM Enclosure in the Support and Service > Service Procedures > IOAM Hardware Servicing collection in NTL.
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. Value: On or Off Manufacturer Identifies the manufacturer of the component. Displayed for VIO fans in S-series VIO modules only.
FC-AL I/O Module Subcomponent of a FCDM. There are two FC-AL I/O modules in each FCDM. These modules are the interface between the FCDM elements and the host controller. They route data to and from the drives using loop A and loop B. Location in OSM Tree: System > Group > FCDM Collection > FCDM > FC-AL I/O Module Example: FC-AL I/O Module (111.211.1.93) Attributes FC-AL I/O Module Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
FCDM Fibre Channel disk modules (FCDMs), formerly known as Disk Drive Enclosures, are located in the OSM Service Connection tree pane hierarchy under FCDM Collection objects. (See FCDM Collection for more information on where they appear in the tree hierarchy.) Each FCDM contains: • Up to 14 Fibre Channel disk drives • Two FC-AL I/O Modules • Two Power Supplies • Two Blowers • One EMU Location in OSM Tree: System > Group > FCDM Collection > FCDM Example: FCDM (111.211.
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. Blink All LEDs On Causes the fault LEDs on the FCDM, disks, FC-AL I/O module, power supplies, and fans to blink. Disable All Drive Bypass Opens up the specified port or ports (A and/or B) on all disk drives in the FCDM for use.
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. Other FCDMs that are not daisy-chained appear under separate in FCDM Collection objects.
FCSA Fibre Channel ServerNet adapter. The FCSA object always displays two FCSA FSACs, regardless of whether they are both physically present. At least one must be present to perform FCSA firmware updates. The FCSA FSAC attributes Node Name and Port Name indicate the presence of FCSA FSACs and attached disks. Unlike many other adapters, the ports on the FCSA are numbered from top down when viewing the FCSA installed in a rack.
Flash Firmware Update Updates the operational firmware in Flash memory of the FCSA. NOTE: This firmware is not used on NonStop S-series systems, as system load through an FCSA is not supported on S-series. Replace Launches an interactive action to assist with replacement of an FCSA. Note: This replacement procedure is intended for authorized service providers only.
Installing the Replacement FCSA NOTE: Whenever you handle a FCSA, follow standard operating practices to avoid damage to the equipment. Review the standard operating practices documented in the Fibre Channel ServerNet Adapter Installation and Support Guide. 1. Unpack and inspect the FCSA: a. Put on an ESD wrist strap and attach the grounding clip to the antistatic mat. b. Place the package containing the FCSA on the antistatic mat. c. Open the packing container and remove the FCSA. CAUTION: d.
FCSA FSAC A Fibre Channel SAC (ServerNet addressable controller) is one of two fiber-optic plug-in cards mounted on an FCSA (Fibre Channel ServerNet adapter). Location in OSM Tree: System > Group > IOAM Enclosure > IOAM > FCSA > FCSA FSAC Example: FCSA FSAC (100.2.1.1) NOTE: The ports on a Fibre Channel ServerNet adapter are numbered from top down when you view the FCSA installed in a rack. Thus, FCSA FSAC 1 is attached to the upper port (port 1), FCSA FSAC 2 is attached to the lower port (port 2).
FESA (Fast Ethernet ServerNet Adapter) An adapter that connects the ServerNet connections inside a server to a 10/100Base-TX local area network (LAN). The Fast Ethernet ServerNet adapter (FESA) CRU contains one Fast Ethernet ServerNet addressable controller (SAC), which contains one Ethernet physical interface, that corresponds to the one Ethernet port on each FESA CRU.
FSAC (Fiber ServerNet Addressable Controller) The Fiber SAC (ServerNet addressable controller) is a fiber-optic plug-in card mounted on the ServerNet/DA CRU. External storage devices are physically connected to the Fiber SACs. There can be up to four Fiber SACs on each ServerNet/DA CRU. Location in OSM Tree: System > Group > Module > SNDA > FSAC Example: FSAC (11.1.53.1) Attributes FSAC Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
FXSA / FX2SA (ServerNet/FX / ServerNet/FX2) The ServerNet/FX adapter (FXSA) and ServerNet/FX 2 adapter (FX2SA) field-replaceable units (FRUs) allow NonStop S-series servers to communicate with NonStop K-series servers using a fiber-optic ring. Location in OSM Tree: System > Group > Module > FX2SA Slot Location: FXSA and FX2SA FRUs can be installed in slots 51 through 54 in PMF or IOMF enclosures (service side).
Firmware Version The VPROC of the firmware currently loaded on the FRU. Default File Name The name of the file to be used for a firmware update. Default File Version The version of the firmware to be used for a firmware update . Compare State The differences, if any, between the current and default firmware versions. Values Actions Add LBU Configures a ServerNet/FX or ServerNet/FX2 adapter as an LBU. An LBU is the SCF logical equivalent for the adapter.
Stop Stops the ServerNet/FX or ServerNet/FX 2 adapter field-replaceable unit (FRU) that is in the Started state. When the Stop action completes, the FRU is in the Stopped state. Test Verify Runs all the firmware diagnostic tests on the ServerNet/FX or ServerNet/FX 2 adapter field-replaceable unit (FRU). This test takes about 10 minutes to complete. You must use the Stop action to place the FRU in the Stopped state before you initiate the Test Verify action.
G4SA The M8800 Gigabit Ethernet 4-port ServerNet adapter (G4SA) provides Gigabit connectivity between NonStop servers and Ethernet LANs. G4SAs are installed in slots 1 through 5 of an I/O Adapter Module (IOAM). Each G4SA contains one G4SA SAC, which contains up to four G4SA PIFs, resulting in four Ethernet ports on each G4SA. For more information about the G4SA, including diagrams to identify specific ports, see the Gigabit Ethernet 4-Port Adapter Installation and Support Guide.
Stop Rather than automatically stopping the G4SA (as the Abort action does), this action first warns you if the G4SA is currently in use (and stops it only after you confirm).
G4SA PIF Physical interface (PIF) objects represent each of the four ports on a G4SA through which LAN connections are made. Each G4SA PIF has an associated LIF object. Location in OSM Tree: System > Group > IOAM Enclosure > IOAM > 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.
G4SA SAC A ServerNet addressable controller mounted on a G4SA (Gigabit Ethernet 4-port ServerNet adapter). Each G4SA SAC contains up to four G4SA PIFs, which correspond to the four Ethernet ports on each G4SA. Location in OSM Tree: System > Group > IOAM Enclosure > IOAM > G4SA > G4SA SAC Example: G4SA SAC $ZZLAN.G4SA1.0 Attributes G4SA SAC Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Dump Copies a memory image from a G4SA SAC to a file on the local system. The file will be the last (highest numbered) file of the chain started with the file specified in the Dump File Name attribute of the SAC. CAUTION: The SAC and PIFs will be unavailable while the SAC is being dumped. Firmware Update Updates the boot firmware for the G4SA SAC. Responsive Test Runs an online test that verifies the SAC is integrated with the LAN subsystem, is owned, and is in the Started state.
GESA (Gigabyte Ethernet ServerNet Adapter) An adapter that connects the ServerNet connections inside a server to an Ethernet local area network (LAN). The Gigabit Ethernet ServerNet adapter is similar to the Fast Ethernet ServerNet adapter but offers enhanced performance. 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.
Group (I/O or Processor Enclosure) A group contains all the components that are serviced by a pair of service processors (SPs). For Nonstop S-Series servers, an enclosure contains one group, and a group contains one module. 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) 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. If an FCDM is connected to FCSAs located in different IOAM enclosures (for increased fault tolerance), OSM displays the FCDM Collection in the lower-numbered group. Numbering of IOAM groups starts at 11.
Internal ServerNet Fabric The system has two internal ServerNet fabric objects, the Internal ServerNet X Fabric and the Internal ServerNet Y Fabric. Location in OSM Tree: Under System Example: Internal ServerNet Y Fabric Attributes Internal ServerNet Y Fabric Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
IOAM (I/O Adapter Module) A modular I/O adapter module. There are two IOAMs in each IOAM Enclosure. Each IOAM contains: • A ServerNet Switch Board • Two IOAM Power Supplies • Two IOAM Fans • Up to five FCSA or G4SAs 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 Enclosure An enclosure that contains two I/O Adapter Modules. Location in OSM Tree: System > Group > IOAM Enclosure Example: IOAM Enclosure 13 Attributes IOAM Enclosure Service State 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 eight alphanumeric characters.
IOMF (I/O Multifunction) Each I/O multifunction (IOMF) CRU contains these components: • A service processor (SP) • A power supply • Three SCSI controllers Location in OSM Tree: System > Group > Module > IOMF Slot Location: IOMF CRUs are located in slots 50 and 55 in I/O enclosures (service side). Example: IOMF (2.1.50) Attributes IOMF Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
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 Force Power Off Use this action to power off the CRU and all of its subcomponents only if the Prepare to Power Off or Power Off actions fail. The Force Power Off does not perform the other precautionary checks that are done by the Prepare to Power Off and Power Off actions.
IOMF2 (I/O Multifunction 2) Each I/O multifunction 2 (IOMF2) CRU in a NonStop server contains these components: • A service processor (SP) • Two internal SCSI controllers • One external SSAC • A ServerNet plug-in card (PIC), which provides connectivity to internal ServerNet fabrics Location in OSM Tree: System > Group > Module > IOMF2 Slot Location: IOMF2 CRUs are located in slots 50 and 55 of Nonstop S-series I/O enclosures (service side). Example: IOMF2 (1.1.
Storage ASIC Initialization State The status of the storage ASIC in the CRU. Values: Initialized, Uninitialized, Unknown Actions Disable ServerNet Port Disables the specified ServerNet port on this CRU. Perform this action only as directed by OSM alarm repair actions. Parameter: Port Number Enable ServerNet Port Enables the specified ServerNet port on this CRU. Perform this action only as directed by OSM alarm repair actions.
LIF The logical interface, associated with a physical interface (PIF), used by an Ethernet controller port or a ServerNet adapter port. Location in OSM Tree: For an Ethernet controller port LIF: System > Group > Module > PMF2 > MIOE > MIOE SAC > MIOE PIF > LIF For a ServerNet adapter port LIF: System > Group > Module > adapter > SAC > PIF > LIF Example: LIF $ZZLAN.LAN01A Attributes LIF Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Maintenance Switch An Ethernet switch that allows the OSM console to communicate with the Maintenance Entity (ME) in the ServerNet switch board. Location in OSM Tree: System > Monitored Service LAN Devices > Maintenance Switch Example: Maintenance Switch SRSLAN Attributes Maintenance Switch Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
MIOE (Ethernet Controller) A component of PMF and PMF2 CRUs located in Group 1 only. Provides connectivity between the service processor and the dedicated service LAN (for OSM). Each MIOE represents a single Ethernet port, known as a Physical Interface (PIF) object. Each PIF is associated with a service processor (SP) in Group 1. Location in OSM Tree: System > Group > Module > PMF2 > MIOE Slot Location: Located on PMF CRUs in slots 50 and 55 of processor enclosures in Group 1 Example: MIOE $ZZLAN.
MIOE PIF The physical interface through which the MIOE is logically connected to the system. Location in OSM Tree: System > Group > Module > PMF2 > MIOE >MIOE SAC > MIOE PIF Example: MIOE PIF $ZZLAN.MIOE0.0.A Attributes MIOE PIF 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.
MIOE SAC The MIOE ServerNet addressable controller (MIOE SAC) is a LAN controller that is a component of the MIOE. Each MIOE contains one MIOE SAC, which contains one Ethernet port, known as a physical interface (PIF) object. Location in OSM Tree:System > Group > Module > PMF2 > MIOE > MIOE SAC Example:MIOE SAC $ZZLAN.MIOE0.0 Attributes MIOE SAC Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Module A set of components that share a common hardware interconnection, such as a backplane. This object applies only to Nonstop S-series processor and I/O enclosures, in which each enclosure contains contains one group, and a group contains only one module. The module is considered a subcomponent of the group. IOAM enclosures contain two I/O adapter modules. Example: Module 2.
Set Physical Location Allows you to assign these Physical Location attributes for the module: • Rack Name is a user-defined name for the rack containing the module. You can enter up to eight alphanumeric characters. • Rack Offset allows you to display a numerical value representing the location of the module within the rack. A valid integer (from 1 to 42) must be specified when performing the Set Physical Location action, or the action will fail.
Monitored Service LAN Devices Contains Maintenance Switch and UPS objects that you have configured OSM to monitor through the actions on this object. Location in OSM Tree: System > Monitored Service LAN Devices Attributes None. Actions Start Monitoring Maintenance Switch Causes the OSM Service Connection to display and start monitoring the maintenance switch.
MSEB Modular ServerNet expansion boards (MSEBs) allow processors in one enclosure to communicate with processors in other nodes of a ServerNet cluster on one fabric. MSEBs contain ServerNet plug-in cards (PICs), which provide ServerNet connectivity by means of fiber-optic cables. Each node in a ServerNet cluster must have two MSEBs for fault tolerance, one for connectivity to a switch on the X fabric and the other for connectivity to a switch on the Y fabric.
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). An Optical Extender PIC can be used in slot 2 (NS14000 series, NS1200, or NS1000 only) for additional processor connectivity (processors 4 through 7), slot 3 (NS5000 only) for NonStop S-series connectivity, and in slot 5 (Integrity NonStop NS14000 series only) for ServerNet cluster connectivity.
PIC A replaceable component of MSEB or IOMF2 CRUs that provides connectivity to internal* ServerNet fabrics. * In port 6 of the MSEBs located in slot 51 and 52 of group 01 only, NNA-type ServerNet PICs can be used to provide connectivity to external ServerNet fabrics. Location in OSM Tree: System > Group > Module > IOMF2 > PIC Example: PIC (1.1.52.1) Attributes PIC Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Internal Loopback Test Tests the circuitry of a plug-in card (PIC) installed in an MSEB to determine if ServerNet traffic can pass through the PIC. CAUTION: Do not perform this test on a PIC that is operating normally because it will shut down ServerNet traffic through the PIC. Also, do not perform this test on an NNA-type ServerNet PIC because the test will fail even if nothing is wrong with the NNA PIC. NOTE: This test fails if no device is attached to the PIC even if nothing is wrong with the PIC itself.
PIF Physical interface (PIF) objects are the ports on these resources through which LAN connections are made: • Ethernet ServerNet addressable controllers (E4SA SACs) • Fast Ethernet ServerNet addressable controller (FESA SACs) • Gigabit Ethernet ServerNet addressable controllers (GESA SACs) • Common Controller ServerNet addressable controllers (CCSA SACs) • Token Ring ServerNet addressable controllers (TRSA SACs) Location in OSM Tree: System > Group > Module > CRU > SAC > PIF Example: TRSA PIF $Z
Start Starts the CRU's 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 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).
PMCU The power monitor and control unit (PMCU) controls and monitors the battery connection to the DC power distribution buses. Along with the service processor, the PMCU diagnoses the condition of the batteries, fans, and power supplies and regulates the voltage supplied to the fans. Location in OSM Tree: System > Group > Module > PMCU Slot Location: PMCUs are located in slots 21 and 22 of Nonstop S-series processor or I/O enclosures (appearance side). Example: PMCU (1.1.
PMF (Processor Multifunction) Each processor multifunction (PMF) CRU in a NonStop server contains these components: • A processor and memory board (PMB), which contains a processor • A power supply (S7000 only) • A service processor (SP) • Three SCSI controllers • And for PMFs in Group 1 only, an MIOE (Ethernet controller) to provide connectivity between the service processor and the dedicated service LAN (for OSM).
Storage ASIC Initialization State The status of the storage ASIC in the CRU. Values: Initialized, Uninitialized, Unknown Actions Disable ServerNet Port Disables the specified ServerNet port on this CRU. Perform this action only as directed by OSM alarm repair actions. Parameter: Port Number Enable ServerNet Port Enables the specified ServerNet port on this CRU. Perform this action only as directed by OSM alarm repair actions.
Replace Launches the Replace PMF guided procedure, which provides step-by-step instructions for replacing the PMF 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.
PMF2 (Processor Multifunction 2) Each processor multifunction 2 (PMF2) CRU in a NonStop server contains these components: • A processor and memory board (PMB), which contains a processor • A service processor (SP) • Two internal SCSI controllers • One external SSAC • And for PMF2s in Group 1 only, an MIOE (Ethernet controller) to provide connectivity between the service processor and the dedicated service LAN (for OSM).
Storage ASIC Initialization State The status of the storage ASIC in the CRU. Values: Initialized, Uninitialized, Unknown Actions Disable ServerNet Port Disables the specified ServerNet port on this CRU. Perform this action only as directed by OSM alarm repair actions. Parameter: Port Number Enable ServerNet Port Enables the specified ServerNet port on this CRU. Perform this action only as directed by OSM alarm repair actions.
Power Supply The power supply converts standard AC line voltage and distributes DC power to all components in its power domain. The power supply is: • A component of all the IOMF CRUs and PMF CRUs in NonStop S7000 servers • A separate CRU for enclosures containing IOMF2, PMF2, or PMF CRUs in NonStop S7400 or later servers ▲ In DC-powered Telco systems, the power supply units displayed in slots 31 and 32 of the OSM GUI represent up to 4 Telco Isolating Converters (TICs) in positions A1, A2, B1, and B2.
OSM alarm appears on a power supply in either slot 31 or 32, consult your wiring diagram and the NonStop S-Series Central Office Server Installation and Service Guide before replacing a power supply component. 1. 2. 3. Preparing to replace the power supply CRU -- The action directs you to the Replacement Guidelines and Precautions help topic for guidelines and precautionary steps to observe before and during the CRU replacement.
enclosure. For an illustration of an IOMF2 CRU, see the NonStop S-Series Hardware Installation and FastPath Guide. 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. 5. With one hand, grasp the handle of the power supply and slide the power supply partway out of the slot.
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.
Power Supply (FCDM) Subcomponent of a FCDM. There are two power supplies in each FCDM. Location in OSM Tree: System > Group > FCDM Collection > FCDM > Power Supply Example: Power Supply (111.211.1.95) 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.
Power Supply (IOAM) Supplies power to the IOAM. There are two IOAM power supply units in each IOAM. For information on how to replace an individual Power Supply, see the Support and Service > Service Procedures collection in NTL. NOTE: If a ServerNet switch board is not present, the IOAM power supplies will not appear in OSM. Location in OSM Tree: System > Group > IOAM Enclosure > IOAM > Power Supply Example: Power Supply (13.2.
Power Supply (VIO) Provides power to the VIO enclosure (represented in the OSM Service Connection as VIO module). There are two VIO power supplies in each VIO enclosure. 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.
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 A processor or central processing unit (CPU). In Nonstop S-series servers, a Processor is a component of the processor multifunction (PMF) customer-replaceable unit (CRU). Each processor enclosure in a NonStop S-series server contains two PMF CRUs and therefore two processors. Location in OSM Tree: System > Group > Module > PMF2 > Processor Slot Location: Processors are located on the PMF CRUs in slots 50 and 55 on the service side of processor enclosures.
Hardware Freeze Flag Whether the processor has been frozen by a hardware error: True: A hardware error in this processor caused it to freeze. (Disregard the Halt Code and Lites Register values.) False: This processor has not experienced a freeze caused by a hardware error. Unknown: Hardware freeze state could not be read. Online Boot Millicode Firmware Online Boot Millicode Firmware Update is not supported for processors in S7000 PMF CRUs or on systems running G06.11 or earlier.
SAC (ServerNet Addressable Controller) A LAN controller that is a component of one of these CRUs: CRU SACs in CRU PIFs in SAC CCSA 4 4 E4SA 2 2 FESA 1 1 GESA 1 1 TRSA 1 1 Location in OSM Tree: System > Group > Module > CRU > SAC 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.
SAC Type Displayed for CCSA SACs only, displays the type of CCSA SAC (for example: SS7TE3A). 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.
SCSI Controller A controller that manages devices using the Small Computer System Interface (SCSI) protocol. This SCSI controller is a component of Processor Multifunction (PMF) CRUs and I/O Multifunction (IOMF) CRUs. Location in OSM Tree: System > Group > Module > PMF2 > SCSI Controller Slot Location: SCSI controllers are located on PMF CRUs in slots 50 and 55 of processor enclosures and on IOMF CRUs in slots 50 and 55 of I/O enclosures. Example: SCSI Controller (1.1.55.
SEB The ServerNet expansion boards (SEBs) and cables allow processors in one enclosure to communicate with processors in another enclosure. Each SEB CRU provides either the ServerNet X fabric or the ServerNet Y fabric for a group. Location in OSM Tree: System > Group > Module > SEB Slot Location: SEBs must be located in slots 51 and 52 of processor enclosures (service side). Example: SEB (1.1.
ServerNet Port In OSM, this object represents ports on: • ServerNet PICs located within Processor Switches • ServerNet Switch Boards located within IOAM Enclosures • 4-Port ServerNet Extenders (4PSEs) located only in HP Integrity NonStop NonStop NS14000 or NonStop NS1000 systems containing IOAMs • VIO Logic Board located in systems containing VIO enclosures.
ServerNet Switch Board A component of the IOAM, the ServerNet Switch Board provides ServerNet connectivity between processors, ServerNet adapters, and attached hardware devices. OSM software communicates with an internal part of the switch known as the Maintenance Entity (ME) by a connection established through the Maintenance Switch. Location in OSM Tree: In an IOAM: System > Group > IOAM Enclosure > IOAM > ServerNet Switch Board Example: ServerNet Switch Board (11.2.
The filename convention is ZMmmmssn, where: mmm = group number ss = module number n = version number (incremented for subsequent versions of the same ZMmmmss snapshot files) Example: ZM100023: snapshot file taken of ServerNet Switch Board in group 100, module 02, version number 3. Enable Memory Snapshot Creates a snapshot of the ServerNet Switch Board's logic board memory. Perform Dump Memory to dump this snapshot to a file in $SYSTEM.ZSERVICE.
Service Processor (SP) The service processor (SP) controls environmental and maintenance functions and acts as the master of the serial maintenance bus (SMB). The service processor is a physical component of PMF, PMF2, IOMF, and IOMF2) CRUs. Location in OSM Tree: System > Group > Module > PMF2 > SP Slot Location: Service processors are located on the PMF CRUs and IOMF CRUs in slots 50 and 55 of processor and I/O enclosures (service side). Example: SP (1.1.
Compare State The differences, if any, between the current and default firmware versions. Values Processor Boot Millicode Firmware These attributes are displayed only for SPs located in PMF or PMF2 CRUs; not for those in IOMF or IOMF2 CRUs. Version The version of the firmware on the processor on the same PMF CRU with this service processor. Default File Name The name of the file to be used for the Processor Boot Millicode firmware update.
SNDA (ServerNet/DA) The ServerNet/DA CRU (customer-replaceable unit) is an adapter that allows external storage devices to be connected to servers. The external storage devices are physically connected to either Fiber SACs (FSAC) or SCSI SACs (SSAC) mounted on the ServerNet/DA CRU. Location in OSM Tree: System > Group > Module > SNDA Slot Location: ServerNet/DA CRUs can be located in slots 53 and 54 in processor enclosures (service side) or in slots 51, 52, 53, and 54 in I/O enclosures (service side).
SSAC (SCSI SAC) The SCSI SAC (ServerNet addressable controller) is a SCSI plug-in card mounted on these devices: • Processor multifunction 2 (PMF2) CRU (external SCSI controller, SAC 3) • I/O multifunction (IOMF2) 2 CRU (external SCSI controller, SAC 3) • ServerNet/DA CRU (There can be up to four SCSI SACs on each ServerNet/DA CRU.) SCSI SACs are used for connecting external SCSI devices such as tape drives. Location in OSM Tree: System > Group > Module > IOMF2 > SSAC Example: SSAC (1.1.50.
Storage Router This object represents one of these resources: 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
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. If the state of the backup I/O process is Stopped, this ID is not displayed. Example: 1,285 SCSI Interface SCSI ID An identification number assigned to the device when configured.
SWAN / SWAN2 The ServerNet wide area network (SWAN) concentrator CRU is an external communications device that connects to a system through dual Ethernet ports. It supports both synchronous and asynchronous protocols over a variety of electrical interfaces. The SWAN CRU object displayed by OSM can be either a SWAN or SWAN 2 CRU. To distinguish between them, look at their subcomponents.
Primary Subnet Name The name of the subnet on the primary TCP/IP process that supports the SWAN concentrator. Format: TCPIP process name.subnet name Example: $ZTCP1.#SN1 Alternate Subnet Name The name of the subnet on the alternate TCP/IP process that supports the SWAN concentrator. Format: TCPIP process name.subnet name Example: $ZTCP3.#SN1 Primary Gateway IP Address The primary gateway IP address configured for the SWAN concentrator. Example: 192.168.10.
SWAN Battery A subcomponent of the SWAN 2 CRU that provides backup power for 30 seconds in the event of a power outage. 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.
SWAN CLIP A communications line interface processor (CLIP) is a component of a SWAN or SWAN 2 CRU. The CLIP provides a link-level protocol and a software interface to the host. Each SWAN concentrator contains up to three CLIPs, and each CLIP has two WAN Lines and two SWAN Paths. Each SWAN 2 CRU contains up to six SWAN 2 CLIPs, and each CLIP has two WAN Lines and two SWAN Paths. Location in OSM Tree: System > SWAN Collection > SWAN > CLIP Slot Location: CLIPs are external to the enclosures.
Test Backup Path Access Tests two-way access to the communications line interface processor (CLIP) using the alternate address. Test Basic Online Runs an online test to determine if the CLIP is functional, and checks that both the access paths are available. Test Full Path Access Tests two-way access to the communications line interface processor (CLIP) using both the primary and alternate addresses.
SWAN Collection When one or more SWAN or SWAN 2 concentrator CRUs are connected to a system, a SWAN Collection object appears in both the tree pane and the overview pane of the OSM Service Connection. In both panes, this object displays an alarm or yellow icon if alarms or degraded conditions exist on any of the individual SWAN CRUs contained within.You can expand the SWAN Collection icon in the tree pane (but not in the overview pane) to select and monitor individual SWAN CRUs and their subcomponents.
SWAN FAN Each SWAN 2 CRU has two customer-replaceable fan subcomponents. Location in OSM Tree: System > SWAN Collection > SWAN > Fan Example: Fan $ZZWAN.#SWAN2.FAN1 Attributes Fan $ZZWAN 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. Values Logical Actions None.
SWAN LAN Logic Board (LANLB) Each SWAN 2 CRU has two customer-replaceable LAN logic board subcomponents. Location in OSM Tree: System > SWAN Collection > SWAN > LANLB Example: LAN LB $ZZWAN.#SWAN2.LAN1 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.
SWAN Line A subcomponent of SWAN CLIPs and SWAN 2 CLIPs. Every CLIP has two lines, which represent the ports on the CLIP. Location in OSM Tree: System > SWAN Collection > SWAN > CLIP > Line Example: Line $ZZWAN.#SWAN2.1.0 Attributes Line $ZZWAN Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Device Name The name of the WAN device associated with the line. Example: $TP6S1 Logical If no device is configured, "FREE" is shown.
SWAN Path A subcomponent of SWAN CLIPs and SWAN 2 CLIPs. Every CLIP has two paths, path A and path B. These paths represent the two Ethernet interfaces on the SWAN concentrator. Location in OSM Tree: System > SWAN Collection > SWAN > CLIP > Path Example: PATH $ZZWAN.#SWAN2.1.B Attributes PATH $ZZWAN Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values MAC Address The media access control (MAC) address of 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. Values Part Number The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts.
System A system is made up of all the hardware components, software, and firmware that are managed by a single operating system. Internal hardware components are housed in enclosures and are arranged in groups, modules, and slots. User-replaceable components are known as customer-replaceable units (CRUs). Components that must be replaced by your service provider are known as field-replaceable units (FRUs). Both CRUs and FRUs can contain subcomponents.
Incident Report Configuration Problem Incident Report Creation State Indicates whether or not OSM's ability to create Problem Incident Reports has been suppressed. This suppression is accomplished by the Suppress Problem Incident Report Creation action and is desirable to stop dial-out of known problems, such as those that may occur during CRU replacements. Values: Suppressed, Unsuppressed Reason for Suppression Why the creation ability was suppressed, displayed as free form text.
Set Data Collection Volume Used to specify a volume in which automatic or manual data collection will take place. The volume should be something other than $SYSTEM to avoid the possibility of filling that volume with collected data. The Diagnostic Data Collection Volume attribute displays the currently specified volume. How long the files are retained in this volume before being automatically deleted is determined by the Set Days to Persist for Diagnostic Data action.
Tape Collection When one or more tape drives are connected to a system, a Tape Collection object appears in both the tree pane and the overview pane of the OSM Service Connection. In both panes, this object displays an alarm or yellow icon if alarms or degraded conditions exist on any of the individual tape devices contained within. You can expand the Tape Collection icon in the tree pane (but not in the overview pane) to select and monitor individual tape devices.
Tape Specifies a tape drive configured for a system. Location in OSM Tree: System > Tape Collection > Tape Drive Slot Location: Most tape drives can be connected physically through a cable connected to the MFC SCSI port on the IOMF CRU or a SCSI SAC (available on a ServerNet/DA CRU, a PMF2 CRU, or an IOMF2 CRU). The CT9840/CT9840FC/CT9841FC cartridge tape drives must be connected to a SCSI SAC on either a ServerNet/DA CRU, a PMF2 CRU, or an IOMF2 CRU.
Configured Controller Location The location of the SCSI controller. Example: IOMF2.SAC-3.GRP-1.MOD-1.SLOT-55 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. Note that Start is a logical command and does not affect the hardware. Stop Puts the tape process in a state to disallow regular I/O commands to the tape drive.
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). Location in OSM Tree: System > Group > Module > TRSA Slot Location: TRSA CRUs can be located 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: TRSA $ZZLAN.TRSA0 (1.1.
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. Location in OSM Tree: System > Group > Module > Unknown CRU Attributes Unknown CRU Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Power State Whether the component is powered on. Values Physical Actions None.
UPS Uninterruptible power supply (UPS) unit that provides backup power for IOAM enclosures. NOTE: OSM supports SNMP card versions up to and including v3.20. Location in OSM Tree: System > Monitored Service LAN Devices > UPS Example: UPS SDUPS Attributes UPS Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Battery Status Indicates the current status of the UPS battery. Possible values are Normal and On Battery.
VIO FCSA In a system containing VIO enclosures (represented in the OSM Service Connection as VIO modules), OSM displays an FCSA object to represent: • In slot 1, the four built-in Fibre Channel ports that provide the functional equivalent of a Fibre Channel ServerNet adapter. • In slot 7, an optional expansion VIO FCSA. NOTE: VIO FCSA is not a subcomponent of VIO modules in S-series servers. OSM does not display VIO FCSA attribute information until an associated disk process is configured and started.
Flash Firmware Update Updates the operational firmware in Flash memory of the VIO FCSA. Replace This action fails when trying to replace an FCSA in a VIO enclosure. The repair action text points you to the Support and Service collection of NTL for a documented service procedure describing how to replace a VIO FCSA. Responsive Test Verifies that the VIO FCSA is connected and responding. Test Verify Verifies basic functionality of the VIO 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.
Replace Displays a service procedure describing how to replace a VIO G4SA in a VIO enclosure. Reset Places the VIO G4SA in a state from which it can be started. Start Starts the VIO G4SA and the associated G4SA SAC. The VIO G4SA and the SAC must be in the Stopped state before you perform this action. Stop Rather than automatically stopping the VIO G4SA (as the Abort action does), this action first warns you if the VIO G4SA is currently in use (and stops it only after you confirm).
VIO Logic Board Component of a VIO enclosure (represented in the OSM Service Connection as VIO module), the VIO logic board provides ServerNet connectivity between processors, ServerNet adapters, and attached hardware devices. Each VIO logic board contains five ports. Ports 1 through 4 providing connectivity to processors 0 through 3. Port 5 represents the crosslink connectivity to the VIO enclosure on the opposite fabric.
mmm = group number ss = module number n = version number (incremented for subsequent versions of the same ZMmmmss snapshot files) Example: ZM100023: snapshot file taken of VIO logic board in group 100, module 02, version number 3. Enable Memory Snapshot Creates a snapshot of the VIO logic board's memory. Perform Dump Memory to dump this snapshot to a file in $SYSTEM.ZSERVICE. Hard Reset Resets the VIO logic board hardware and the routing tables.
VIO Module The OSM Service Connection displays a VIO Module object to represent: • In Integrity NonStop NS14000 series, NS1200, NS1000, and NS3000AC servers, VIO enclosures, which take the place of an IOAM enclosure. There are two VIO enclosures in each system. The VIO Module objects are located under the Fabric Group objects, with VIO Module 2 under the Internal ServerNet X Fabric and VIO Module 3 under the Internal ServerNet Y Fabric.
Physical Location The values displayed by these attributes are assigned through the Set Physical Location action. NOTE: These attributes are not displayed for a VIO Module providing V4SE or V8SE connectivity (NS16000CG or NS5000). Rack Name A user-defined name assigned to identify the rack in which the VIO enclosure is located. You can enter up to eight alphanumeric characters. Rack Offset A number (from 1 to 42) assigned to describe the location of the VIO enclosure within the rack.
Common Attribute Values Battery Charge Status Value Meaning Absent The battery is not installed. Charged The battery is fully charged Charging The battery is in the process of being charged. Disabled The battery cannot supply power and cannot be charged, possibly because the Disable Battery action has been performed. You should disable a battery before removal. Discharged The battery needs recharging or replacement. Discharging The system is currently drawing power from the battery.
Enabled State Value Meaning Disabled The component is present but not operational, possibly because the Disable action was performed. Enabled The component is operational. Fault A problem was detected. The component might be functioning below standard or not responding. Inspect the component. Off The component is not functional. On The component is functional. Unknown State is unknown; component might not be responding. Group Type A unique number in the system that identifies this group.
Powered On Meaning Off Component is powered off. Possible Redundant Power Problem There might be a problem with the backup power supply for this component. (The Redundant Power Scrub action could not determine the exact cause of the problem.) 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.
Type System NSR-V S74000 NSR-X S76000 NSR-H S78000 NSR-Y S86000 NSR-Z S88000 NSE-A Integrity NonStop NS16000 server NSE-B Integrity NonStop NS1000 server NSE-D Integrity NonStop NS14000 server NSE-I Integrity NonStop NonStop NS5000T or NS5000CG server NSE-K Integrity NonStop NS3000AC server NSE-M Integrity NonStop BladeSystem NSE-Q Integrity NonStop NS1200 server NSE-S Integrity NonStop NS14200 server NSE-T Integrity NonStop NS16200 server Service State Value Meaning OK The
Product ID Meaning M8503 HP Ultrium 960 LTO Fibre Channel Tape Drive in L700 tape library M8504 HP Ultrium 960 LTO Fibre Channel Tape Drive in mid-range tape library M8505 HP Ultrium 960 LTO Fibre Channel Tape Drive - table top N1521A LTO in tape library N1522A LTO in mid-range tape library N1524A LTO with ACL installed in tape enclosure N1525A LTO with ACL - table top model N1526A HP Ultrium 460 LTO Fibre Channel Tape Drive - rack mount N1527A HP Ultrium 460 LTO Fibre Channel Tape Drive
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: • 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).
Locating and Viewing Cluster Resources To locate resources in a ServerNet cluster, expand the ServerNet Cluster resource in the tree pane to see the resources and connections in the cluster. To view more information about a particular resource: 1. 2. In the tree pane, select the resource. In the details pane: • Click the Attributes tab to see attributes for the resource. • Click the Alarms tab to see if there are alarms for the resource.
Monitoring a Cluster ServerNet cluster monitoring tasks include: • Viewing alarms for resources in a ServerNet cluster. This task is similar to viewing alarms for resources within a server, except that you must first select the ServerNet Cluster in the tree pane and then navigate to the cluster resource you want to view. See Viewing a Summary of Alarms. • Viewing attributes for resources in a ServerNet cluster. This task is similar to viewing attributes for resources within a server.
Performing Actions on Cluster Resources Some of the actions you can perform on resources within a ServerNet cluster include: • Testing ServerNet cluster connectivity. Perform the Node Connectivity ServerNet Path Test for the external ServerNet fabrics, the Node Responsive Test for the 6780 switch node port, and the Responsive Test for the 6780 switch module. • Starting and stopping the ServerNet cluster subsystem ($ZZSCL). Perform the Set ServerNet Cluster State action on the ServerNet Cluster resource.
Specifying a Cluster Switch Locator String The Set Locator action allows you to specify a text string to indicate the physical location of a cluster switch. This information, which appears in the Locator attribute for the cluster switch, assists in locating the switch when maintenance is required. The maximum length for the text string (including spaces) is: • 64 characters for the 6780 switch • 32 characters for the 6770 switch To specify the switch location: 1. 2. 3. 4. 5. 6. 7. 8. 9.
Updating Cluster Switches To update the firmware, configuration, and FPGA images for the switch logic board in a 6780 switch module, see the ServerNet Cluster 6780 Planning and Installation Guide. Use these procedures to update firmware and configuration on the ServerNet II Switch component of a 6770 switch module. When performing these updates: • Update firmware before updating the configuration. • Do not perform concurrent Firmware Update actions on the same ServerNet II switch.
Managing One of the Star Topologies With OSM OSM supports all topologies of a ServerNet cluster: the star topologies (star, split-star, and tri-star) and the newer layered topology. Differences Between OSM and TSM If you use OSM to manage a cluster with one of the star topologies, see the next paragraphs for differences between OSM and TSM.
Router Connections in a Layered Topology Router Connections for Switch Node Ports External Slot Port Internal Router Port 6 1 1 0 2 1 1 1 2 0 2 2 1 1 3 0 2 3 1 1 4 0 2 4 1 7 8 9 Router Connections for Ports Connecting to Other Switches Zone External Slot Port Internal Router Port 2 1 5 6 2 5 7 1 5 8 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 3 Layer 11 12 13 Router Connections for Ro
External Slot Internal Router Port 4 4 Router Connections in a Layered Topology 237
13 Cluster Resources A ServerNet cluster is built using one of several topologies. The hardware resources in 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.
6770 Switch Module A hardware assembly that provides connectivity for multiple nodes of a ServerNet cluster. The 6770 switch module is used in star, split-star, and tri-star topologies. The subcomponents of the 6770 switch module are the ServerNet II Switch, the AC Transfer Switch, and the Uninterruptible Power Supply (UPS). Location in OSM tree: Under the External ServerNet Fabric (X and Y) objects. Example: SwitchModule $ZZSMN.
6780 Switch Module A hardware component that provides connectivity for multiple nodes of a second-generation ServerNet cluster using the layered topology. As part of the layered topology, the 6780 switch module comprises one cluster switch layer within a cluster switch group. The 6780 switch connects to the nodes through fiber-optic cables that connect to modular ServerNet expansion boards (MSEBs) on each node.
SCF Equivalent: ALTER SWITCH, BLINK ALL Connect to UPS Starts a new Internet Explorer window and loads the default HTTP home page provided by the UPS vendor. Parameter: IP Address (the IP address of the UPS) Replace Invokes the Replace Switch Component guided procedure that helps to replace the switch module. 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.
AC Transfer Switch A component of a 6770 switch module that automatically switches to a backup AC power source if the primary source fails. Location in OSM tree: External ServerNet Fabric > Switch Module > AC Transfer Switch Example: AC Transfer Switch $ZSMN.X1 Attributes AC Transfer Switch Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK. Values Backup Rail Power State The state (On or Off) of the backup power source for the switch.
External ServerNet Fabric This object represents a collection of switches and ServerNet links that connect the local node to other nodes in a ServerNet cluster. Location in OSM tree:The External ServerNet Fabrics (X and Y) are under the ServerNet Cluster. Example:External ServerNet X Fabric Attributes External ServerNet X Fabric Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Remote 6770 Switch The nodes connected directly to one switch see the other switches as remote switches. Although local and remote switches are the same from a hardware standpoint, less information and no actions are available for the remote switch. To perform actions or get additional information on a remote switch, establish a service connection from one of the nodes that connects directly to that switch.
ServerNet Cluster A ServerNet cluster is a collection of NonStop servers connected together that function as a single processing unit. Servers within a ServerNet cluster pass information to each other using the ServerNet protocol. Location in OSM tree: Located at the top level. See also Managing a ServerNet Cluster. Attributes ServerNet Cluster Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Actions Rediscover Causes OSM to refresh and reanalyze the object and all subcomponents. 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. Reset ServerNet Statistics Resets the ServerNet statistical counters to zero for all processors in the system.
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.
ServerNet Remote Node This object represents any system within a ServerNet cluster that is not the local node. Remote nodes are visible when the ServerNet Cluster view is selected. Location in OSM tree: Under the ServerNet Cluster Example: ServerNet Remote Node \MOON2 Attributes ServerNet Remote Node Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
ServerNet II Switch The component of the 6770 switch module that provides routing for the cluster over an external ServerNet fabric. The ServerNet II switch connects to the nodes through fiber-optic cables that connect to plug-in cards (PICs) located on modular ServerNet expansion boards (MSEBs) on each node. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch Example: Switch $ZZSMN.
Blink LED On Causes the LED to blink on and off. 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. In some circumstances, updating both firmware and configuration is not necessary.
Switch Fan A component that circulates air into the enclosure to help maintain optimal temperature. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch Fan Example: Fan (1020.1.16) 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.
Switch Group A collection of up to four 6780 switches connected together, typically mounted in a rack, that reside on one fabric of a cluster switch zone. The switch group is identified by a four-digit number. The first two digits (10) distinguish a switch group from a group within a NonStop S-series server.
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.
Compare State The differences, if any, between the current and default configuration files. Values Version The VPROC of the FPGA (field programmable gate array) image currently loaded on the switch logic board. Default File Name The full path name of the default FPGA file on the server. Default File Version The version of the FPGA image in the default FPGA file. Compare State The differences, if any, between the current and default FPGA versions.
Switch PIC A card in the 6780 switch that plugs into the switch logic board. Most switch PICs (except for maintenance PICs and router interconnect PICs) are populated with transceivers that enable connections to the different nodes, layers, and zones of the cluster. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch PIC Example: Switch PIC $ZZSMN.Y11.13 (1011.1.13) See also Router Connections for Router Interconnect PICs.
Switch Power Supply A component in the switch modules that converts standard AC line voltage and distributes DC power to all components in the module. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch Power Supply Example: Power Supply (1010.1.18) Attributes Power Supply 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 power supply.
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. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch > Switch PIC Example: Switch PIC $ZZSMN.X2.
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. Attributes Switch Node Port Service State Displayed in the Attributes tab and Attributes dialog box only if the value is something other than OK.
Neighbor ServerNet Node Node Number The ServerNet node number of the neighbor node. Node Name The name of the neighbor node. Actions Node Responsive Test Tests the connectivity on the external ServerNet fabric from the local node to the remote node connected via this port.
Switch-to-Switch PIC A plug-in card (PIC) on the 6770 switch module that connects to another switch on the same fabric. The last part of the name contains the port number where the PIC is located. Only the PICs in ports 8 through 11 of the switch are used for switch-to-switch connections. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch > Switch PIC Example: Switch PIC $ZZSMN.Y3.
Switch Port An external transceiver port on a 6780 switch that connects to a 6780 switch in another zone or layer. These ports reside only on switch PICs in slots 2 and 3 (for zone connections) and 11 through 13 (for layer connections). Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module > Switch PIC > Switch Port Example: Switch Port (1010.1.13.4) See also Router Connections for Ports Connecting to Other Switches.
Neighbor Switch Port Switch Port The name of the port to which this port is connected. Format: Port (Group.Module.Slot.Port) where: Group can be 1010, 1020, 1030, 1011, 1021 or 1031. Module can be 1, 2, 3 or 4. Slot can be 2, 3, 11, 12 or 13. Port can be 1, 2, 3 or 4. Actions None.
UPS (6770 Switch Module) The uninterruptible power supply (UPS) is a component of a 6770 switch module that provides two hours of power if both the primary and backup AC power sources fail. Location in OSM tree:External ServerNet Fabric > Switch Group > Switch Module > UPS Example:UPS $ZZSMN.X1 Attributes UPS 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 UPS.
Common Attribute Values Service State This attribute appears in the list of attributes only when attention or service is required. Value Meaning OK The object is functioning properly. This value appears only in the Problem Summary dialog box. Attention Required The resource requires operator attention. This condition sometimes generates an alarm, and the component that requires attention is colored yellow in the tree pane and in the Physical and ServerNet views of the view pane.
Value Valid Only For Link alive, port disabled, neighbor check failed (Connected Zone-to-Zone Interconnect and Layer-to-Layer Interconnect ports to node) Link alive, port disabled, neighbor check failed (Connected Zone-to-Zone Interconnect and Layer-to-Layer Interconnect ports to switch with invalid configuration version identifier) Link alive, port disabled, neighbor check failed (Connected Zone-to-Zone Interconnect and Layer-to-Layer Interconnect ports to switch with incompatible configuration Link aliv
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.
Identifying Your Update Type These topics describe different ways to update a ServerNet cluster. Click the appropriate link for your type of update. • Migrating to the Layered Topology describes how to migrate a cluster from one of the star topologies to the layered topology. • Adding Zones or Layers to a Layered Topology describes how to add zones or layers to a cluster already using the layered topology.
Migrating to the Layered Topology The layered topology requires HP NonStop ServerNet Switches (model 6780). To migrate a ServerNet cluster from one of the star topologies to the layered topology, you must have on hand enough 6780 switches and ServerNet cables to support your cluster. You need at least two switches (one for each external fabric) for every eight nodes.
Adding Layers or Zones to a Layered Topology You can expand an existing ServerNet cluster that uses the layered topology by adding layers or zones. For complete instructions for adding layers or zones, see the ServerNet Cluster 6780 Planning and Installation Guide.
Updating Star Topologies Follow this procedure only if you plan to use OSM to merge clusters to create a split-star or tri-star topology. NOTE: Do not use this procedure unless you have the OSM package running on all nodes of the cluster. Instead, use the TSM Add Switch guided procedure as described in the ServerNet Cluster Manual to perform the update.
14. 15. 16. Use OSM to monitor the connectivity on the Y fabric for all the nodes and switches. Connectivity on the Y fabric should be restored over time. Confirm that the nodes from the original clusters are visible. If any nodes are not visible to the cluster, perform the Add Node to ServerNet Cluster action on the nodes that are not visible to the cluster. If there are no connectivity problems, perform the Rediscover action on the ServerNet Cluster resource. OSM is now configured to dial out alarms.
Software Requirements for Split-Star and Tri-Star Topologies Any node that will participate in a ServerNet cluster must have Expand (T9057) software, which is delivered on the site update tape (SUT). In addition, the Expand/ServerNet Profile (T0569) is required for clustering. If you order the optional Expand/ServerNet Profile component, it is delivered on the SUT.
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
Cable Connections in a Layered Topology Connections Between Layers Within a Switch Group This table lists the connections between layers within a switch group: Switch PIC Slot Port Connect to Switch PIC Slot Port X11/Y11 11 1 X12/Y12 11 1 X11/Y11 11 2 X12/Y12 11 2 X11/Y11 11 3 X12/Y12 11 3 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/Y
Switch PIC Slot Port Connect to Switch PIC Slot Port X13 2 1 X23 2 2 X13 2 2 X23 2 1 X13 3 1 X23 3 2 X13 3 2 X23 3 1 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
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 Y23 2 1 Y33 2 2 Y23 3 1 Y33 3 2 Y24 2 1 Y34 2 2 Y24 3 1 Y34 3 2 278 Updating ServerNet Cluster Topology
Glossary A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z A AC transfer switch A component of a NonStop™ Cluster Switch (model 6770) that provides access to dual AC power sources and the ability to switch between the two sources if one fails. The AC transfer switch draws power from its primary power source as long as it is available. If the primary source fails, the AC transfer switch is switched to draw power from the secondary power source.
backup processor A processor running the HP NonStop™ operating system that communicates with the primary processor, allowing the processors to remain independent. A component failure in one processor has no effect on any other processor. blower A variable speed airflow device that pulls air into an enclosure or element. It usually pulls air in from the front and exhausts the heated air out the rear. board A frame on which computer circuitry is mounted. Same as logic board. boot A synonym for load.
complex programmable logic device (CPLD) Provides the LSU or Blade Element with power-on reset sequencing, configuration loading prior to complete system startup, a watchdog timer, and monitoring of the health of the FPGAs. connection A logical link established between the OSM client software on the system console and the OSM server software on a NonStop server after a logon sequence has been performed. There are two types of connections: service connection and low-level link.
E EMU (Environmental Monitoring Unit) An element which monitors the status of an enclosure, including the power, air temperature, and blower status. The EMU detects problems and displays and reports these conditions to a user and the controller. In some cases, the EMU implements corrective action. enclosure A single sheet-metal structure and its enclosed set of system components.
Fibre Channel ServerNet adapter (FCSA) A ServerNet adapter that transmits data between an HP NonStop™ server and Fibre Channel storage devices. This ServerNet adapter is installed in an IOAM enclosure. Field-programmable gate array (FPGA) A programmable integrated circuit that can be customized to perform specific functions. field-replaceable unit (FRU) A unit that can be replaced in the field only by qualified personnel trained by HP and cannot be replaced by customers.
hard reset An action performed on an HP NonStop™ Cluster Switch (model 6770) and HP NonStop™ ServerNet Switch (model 6780) that reinitializes the router-2 ASIC within the switch, disrupting the routing of ServerNet messages through the switch for several minutes. When the hard reset is finished, the paths are restored automatically. hardware error freeze (HEF) A lock-step error that has caused a processor to freeze.
initial discovery Discovery of a NonStop server with which the or the OSM Service Connection has had no prior contact and for which it has no locally saved information. See also discovery. internal ServerNet X or Y fabric The fabrics that link ServerNet devices within an HP NonStop™ server. internal ServerNet fabrics The fabrics that link ServerNet devices within an HP NonStop™ server.
logic board (LB) A printed wiring assembly (PWA) on which computer circuits (chips and wiring) are mounted. One type of logic board is a processor and memory board (PMB). Another type is a multifunction I/O board (MFIOB). logical device number A number that identifies a particular I/O device in the system. Logical device numbers are assigned to physical I/O devices. logical interface (LIF) A process that allows an application or another process to communicate with data communications hardware.
master service processor (MSP) A type of service processor (SP) pair that provides the basic service processor functions as well as centralized system functions such as a console port, a modem port for remote support functions, and system-load control. The OSM system console communicates directly with the MSPs on the server. The enclosure containing processors 0 and 1 contains the MSP pair. Media Interface Connector (MIC) A type of head on a fiber-optic cable that has locking wings on the sides.
N name For the OSM software, the name attribute is determined by the connection type. When you use the service connection, the logical name is used. When you use the low-level link, the service processor (SP) logical name is used. Examples of logical names: • $DATA04-P is the logical name of the disk CRU located in group 1, module 1, slot 13. • IOMF2.SCSI-3.GRP-1.MOD-1.SLOT-50 is the logical name of the third SCSI bus on the IOMF2 CRU located in group 1, module 1, slot 50.
default configuration settings, as listed in the OSMINI file. For more information, see the OSM Migration and Configuration Guide. P PAL firmware The Processor Abstraction Layer is firmware that directly handles all aborts and initialization and platform management interrupts. part number A unique number assigned to a product. The part number can be used for ordering purposes. path The route between a processor and a subsystem.
to the group identification switches and service LEDs. There are two PMCUs in each group, one for each of the two DC power distribution buses. power supply In system enclosures without power shelves, the component that converts standard AC line voltage into the DC voltages needed by the group components in the enclosure.
Remote access and remote notification are not available in countries where the modem provided by HP is not certified. In these countries, you cannot use OSM to dial out to or accept dial-in communications from a service provider. See also remote notification. remote notification Remote notification, or dial-out, allows OSM to notify a service provider, such as the Global Customer Support Center (GCSC), of pending hardware and software problems.
ServerNet addressable controller (SAC) A controller that is uniquely addressable within one or more ServerNet address domains (SADs) through the node ID and address fields in a request packet. A SAC is typically implemented on some portion of a processor multifunction (PMF) customer-replaceable unit (CRU), an I/O multifunction (IOMF) CRU, or a ServerNet adapter.
service processor (SP) event messages A notification generated by the master service processors (MSPs) on the NonStop server. The OSM Notification Director can gather SP event messages directly from the MSPs, allowing SP event messages to be received when the NonStop operating system is not running. service provider 1. 2. A person trained and qualified to service field-replaceable units (FRUs) associated with a NonStop server.
network. Outside that network, the subnetworks appear as part of a single network. The terms subnetwork and subnet are used interchangeably. subnetwork address An extension of the internet protocol (IP) addressing scheme that allows a site to use a single IP address for multiple physical networks.
tetrahedron A solid bounded by four triangular faces. In ServerNet context, a tetrahedron is four processors interconnected by ServerNet links so as to form a conceptual tetrahedron. Each processor therefore has a direct connection to the other three processors. See tetrahedral topology. Token-Ring ServerNet adapter (TRSA) A ServerNet adapter that provides a single line from a NonStop S-series server to a token-ring network, allowing the server to act as a station on the ring.
vertical tetrahedron • Support for dial-in on a system console • Recommended repair actions associated with alarms A topology of NonStop S-series servers in which the ServerNet connections between the layers of a cluster switch group form a tetrahedron See also tetrahedron, tetrahedral topology, and cluster switch layer. view One of several representations of the server or ServerNet cluster that appear in the view pane of the Management window. See also Inventory view and Physical view.
Index Symbols 6770 Switch Module about, 240 actions, 240 attributes, 240 6780 Switch Module about, 241 actions, 241 attributes, 241 A AC Power State, 176 AC Transfer Switch about, 243 actions, 243 attributes, 243 Access State, 102, 106, 112, 117 actions automatically initiating, 74 detailed information about, 74 on multiple resources, 75 performing, 73 performing on a resource, 74 saving details, 77 stopping, 74 summary of, 83 viewing details, 77 Active Path, 101 Adapter State, 195 Adapter Type, 195 Add No
managing, 239 monitoring, 231 performing actions on, 232 viewing, 230 cluster switch specifying location, 233 cluster topology updating, 267 Collect Diagnostic Data, 207 Common Communication ServerNet Adapter (see CCSA CRU) Communication State, 193 Compare State, 95, 128, 135, 140, 181, 183, 187, 189– 190, 198, 250, 254–255 Compare State values, 223 Configuration Tag, 245, 250, 254, 265 Configuration Update, 251, 255 Configuration Version, 245 Configured Controller Location, 102, 124–125, 127, 193, 211 Conf
Fan about, 121 actions, 121 attributes, 121 for IOAM, 122 for VIO module, 123 Fan Voltage, 148, 150, 167, 170 Fast Ethernet ServerNet Adapter about, 132 FC-AL I/O Module about, 124 actions, 124 attributes, 124 FCDM about, 125 actions, 126 attributes, 125 FCDM Collection about, 127 attributes, 127 FCSA about, 128 actions, 128, 215 attributes, 128, 215 removing and installing, 129 FCSA FSAC about, 131 actions, 131 attributes, 131 FESA about, 132 actions, 132 attributes, 132 Fiber ServerNet Addressable Control
about, 147 actions, 147 attributes, 147 IOAM Fan actions, 122 attributes, 122 IOMF CRU about, 148 actions, 148 attributes, 148 IOMF2 CRU about, 150 actions, 151 attributes, 150 IP Address, 153, 189, 204, 214 L Last Reset Type, 254 LED State, 99, 124 Left Squelch Detected, 134 Left Transmitter Power Level, 134 LIF about, 152 actions, 152 attributes, 152 LIF State, 152 Line LDEV, 249 Line LDEV Name, 249 Line LDEV State, 249 Lines Connected, 153 Lines Disconnected, 153 Link Pulse State, 139, 164 Link State, 2
Path State values, 224 Physical Transmission Type, 94 PIC about, 162 actions, 162 attributes, 162 PIC Model, 256 PIF about, 164 actions, 164 attributes, 164 PMCU about, 166 attributes, 166 PMF about, 167 actions, 168 attributes, 167 PMF2 about, 170 actions, 171 attributes, 170 Port A Bypass State, 105 Port A World Wide Name, 105 Port B Bypass State, 105 Port B World Wide Name, 105 Port Connectivity Status, 259, 262 Port Connectivity Status values, 265 Port Name, 112, 131 Position ID, 250 Power State, 94, 97
actions, 184 attributes, 184 SCSI Extender, 193 SCSI ID, 102 SCSI SAC (see SSAC) SCSI-to-Fiber Converter, 193 SCSI-X Voltage, 148, 150, 167, 170 SCSI-Y Voltage, 148, 150, 167, 170 SEB about, 185 actions, 185 attributes, 185 Secondary Processor Cache Size, 180 Serial Number, 105 ServerNet cluster, 246 cluster actions, 247 cluster attributes, 246 external fabric, 244 internal fabric, 145 Local Node, 248 Local Node actions, 248 Local Node attributes, 248 Remote Node, 249 Remote Node actions, 249 Remote Node at
about, 253 Switch Logic Board about, 254 actions, 255 attributes, 254 Switch Node Port about, 259 actions, 260 attributes, 259 Switch PIC about, 256 actions, 256 attributes, 256 Switch Port about, 262 attributes, 262 Switch Power Supply about, 257 actions, 257 attributes, 257 Switch SANMAN Process Pair, 247 Switch SNETMON Process Pair, 247 Switch-to-Node PIC about, 258 attributes, 258 Switch-to-Switch PIC about, 261 attributes, 261 System about, 206 actions, 207 attributes, 206 system locating resources, 88
actions, 217 attributes, 217 VIO Logic Board about, 219 actions, 219 attributes, 219 VIO Module about, 221 VIO Power Supply actions, 178 W window printing, 51 World Wide Name, 105 X X Fabric Connection State, 249 Y Y Fabric Connection State, 249 304 Index
