OSM User's Guide OSM User's Guide Legal Notice Abstract Product Version: HP OSM T0682AAA Version ID: 2004November09 The HP NonStop" Open System Management (OSM) software is a collection of client/server applications that provide troubleshooting, maintenance, and service tools for the HP NonStop S-series server. The OSM software also allows you to view and manage resources within a supported Expand network, such as an HP NonStop ServerNet Cluster.
❍ How to configure and start OSM server-side processes ● The NonStop System Console Installer Guide describes how to install OSM client-based components and other required system console software. (Installation of server-based components is covered in the softdoc for each product.
2. Preparing the OSM Environment Installing OSM Components System Console-Based Components Server-Based Components 3. Configuring OSM Configuring the Server Defining Users Configuring Service Provider Access Dial-out/Dial-in Unattended Site 4. Starting the OSM Service Connection Launching an OSM Service Connection Using OSM Bookmarks Verifying the OSM Service Connection State Running Multiple Sessions 5.
State Indicators Alarm Indicators Alarm Severity Using the Browser's Find Feature 6. Viewing Alarms Viewing the Alarms Tab Viewing Alarms for a Selected Resource Viewing Alarm Details Suppressing Alarms 7. Viewing Attributes Using the Details Pane to View Attributes Using the Attributes Dialog Box to View Attributes Suppressing Problem Attributes 8.
Viewing a Resource Summary 10. Managing a System Locating and Viewing System Resources Monitoring a System Performing Actions on a System Updating Firmware 11.
Actions External Disk Collection Attributes Actions Fan Attributes Actions FCSA Attributes Actions Removing and Installing a Fibre Channel ServerNet Adapter FCSA FSAC Attributes Actions FESA (Fast Ethernet ServerNet Adapter) CRU Attributes Actions FSAC (Fiber ServerNet Addressable Controller) Attributes Actions FXSA / FX2SA (ServerNet/FX / ServerNet/FX2) FRU Attributes Actions GESA (Gigabyte Ethernet ServerNet Adapter) CRU Attributes Actions G4SA Attributes Actions G4SA PIF Attributes Actions G4SA SAC
Attributes Actions Group Attributes Actions Internal ServerNet Fabric Attributes Actions IOAM (I/O Adapter Module) Attributes Actions IOAM Enclosure Attributes Actions IOAM Fan Attributes Actions IOAM Group Attributes Actions IOAM Power Supply Attributes IOMF (I/O Multifunction) CRU Attributes Actions IOMF2 (I/O Multifunction 2) CRU Attributes Actions LIF Attributes Actions Maintenance Switch Attributes
Actions MIOE (Ethernet Controller) Attributes Actions MIOE PIF Attributes Actions MIOE SAC Attributes Actions Module Attributes Actions Monitored Service LAN Devices Attributes Actions MSEB Attributes Actions PIC Attributes Actions PIF Attributes Actions PMCU Attributes Actions PMF (Processor Multifunction) CRU Attributes Actions PMF2 (Processor Multifunction 2) CRU Attributes
Actions Power Supply Attributes Actions Replacement Guidelines and Precautions Processor Attributes Actions SAC (ServerNet Addressable Controller) Attributes Actions SCSI Controller Attributes Actions SEB Attributes Actions ServerNet Switch Board Attributes Actions Service Processor (SP) Attributes Actions SNDA (ServerNet/DA) CRU Attributes Actions SSAC (SCSI SAC) Attributes Actions Storage Router Attributes Actions SWAN / SWAN2 CRU
Attributes Actions SWAN Battery Attributes Actions SWAN CLIP Attributes Actions SWAN Collection Attributes Actions SWAN FAN Attributes Actions SWAN LAN Logic Board (LANLB) Attributes Actions SWAN Line Attributes Actions SWAN Path Attributes Actions SWAN PS (Power Supply) Attributes Actions System Attributes Actions Tape Collection Attributes Actions Tape
Attributes Actions TRSA (Token Ring ServerNet Adapter) CRU Attributes Actions Unknown CRU Attributes Actions UPS (IOAM) Attributes Actions Common Attribute Values Battery Charge Status Compare State Device State Enabled State Group Type Path State Power State Processor State Processor Type Service State Tape Types Topology 12.
Router Connections for Ports Connecting to Other Switches Router Connections for Router Interconnect PICs 13.
Switch Group Attributes Actions Switch Logic Board Attributes Actions Switch PIC Attributes Actions Switch Power Supply Attributes Actions Switch-to-Node PIC Attributes Actions Switch Node Port Attributes Actions Switch-to-Switch PIC Attributes Actions Switch Port Attributes Actions UPS (6770 Switch Module) Attributes Actions Common Attribute Values Service State Fabric State Configuration Tag Port Connectivity Status 14.
Identifying Your Update Type Migrating to the Layered Topology Adding Layers or Zones to a Layered Topology Updating Star Topologies Software Requirements for Split-Star and Tri-Star Topologies Cable Connections Between Star Groups Updating to the Split-Star Topology Updating to the Tri-Star Topology Cable Connections in a Layered Topology Connections Between Layers Within a Switch Group X Fabric Connections Between Two Zones Y Fabric Connections Between Two Zones X Fabric Connections for Three Zones Y Fabr
Chapter 1. Introducing OSM Chapter 1. Introducing OSM What's New and Changed for This Version OSM Interfaces OSM Service Connection OSM Notification Director OSM Guided Procedures OSM Low-Level Link OSM Event Viewer What Changed From TSM to OSM New Look-and-Feel Functional Differences Between OSM and TSM The OSM client components are installed on a PC workstation that serves as the system console.
T0634 -- OSM Console Tools -- Start menu shortcuts and default home pages for easy access to the OSM Service Connection and OSM Event Viewer (browser-based OSM applications that are not installed on the system console). Caution: Only system consoles provided by HP are supported for use with the OSM applications. To preserve the integrity of software running on system consoles, do not install any software applications on your system consoles other than the preinstalled software.
Connection, are combined into a single product, T0682AAA. ● The OSM Service Connection has also been enhanced to reduce processor utilization and provide faster status updates. 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 S-series server. From the Management window, you can manage the resources of your server.
● Receives, displays, and allows you to take action on problem incident reports, periodic incident reports, software configuration incident reports, and test dial-out incident reports ● Configuration of remote access (dial-in) and remote notification (dial-out) information ● Configuration of dial-out point status for your system console ● Specification of the interval at which your OSM server generates periodic incident reports ● Authorization (automatically or manually) of incident reports to be d
TSM Guided Procedure Replace Power Supply Add Switch OSM Action Replace Upgrade Topology Troubleshoot ServerNet Fabric External Loopback Test For Object Each CRU ServerNet Cluster MSEB and IOMF2 ServerNet plug-in cards (PICs) Firmware Update and Configuration Switch Update Use the Multi-Resource Actions SWAN Fast Firmware Update dialog box to stop, update, and restart SWAN CLIP any or all CLIPs simultaneously.
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.
Functional Differences Between OSM and TSM To find familiar TSM Service Application functions that have been enhanced or otherwise changed in the OSM Service Connection: This TSM feature...
Performing the same TSM action The Multi-Resource Actions dialog box (available from the Display menu) on several objects allows you to initiate an action on any or all resources of the same type of the same type simultaneously. (individually) Rediscover is supported as an action on all system and some cluster objects. For most objects, Rediscover is available only in the shortcut menu. Rediscover menu Rediscover causes OSM to refresh and reanalyze the object and all subcomponents.
You can save a snapshot from the OSM Service Connection without having to change a configuration file setting as in TSM. Snapshots You can load and view a saved snapshot on any server running OSM server software. To load a snapshot, launch Internet Explorer and enter the URL of the system you are using to view the snapshot, followed by /snapshot/index.html. For example: http://star2.caclab.cpqcorp.net:9990/snapshot/index.html.
Chapter 2. Preparing the OSM Environment Chapter 2. Preparing the OSM Environment Installing OSM Components System Console-Based Components Server-Based Components To plan your network LAN configuration and connect your system console so it can communicate with your NonStop S-series 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 Guide.
Chapter 3. Configuring OSM Chapter 3. Configuring OSM Configuring the Server Defining Users Configuring Service Provider Access Dial-out/Dial-in Unattended Site 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.
Defining Users To use the OSM client and server software, you must define the users that have access to your server. OSM allows two types of users: MSP (Low-Level-Link) Users ● Can log on to the OSM Low-Level Link and connect to the MSP, allowing them to access a server even when the NonStop Kernel operating system is not running. ● Have full privileges and can perform serious actions such as loading the processor or starting the system.
Configuring Service Provider Access Use the OSM Notification Director to configure these service provider access components: If you want your system console to receive incident reports from your Incident reports 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.
Chapter 2. Preparing the OSM Environment Chapter 4.
Chapter 4. Starting the OSM Service Connection Chapter 4. Starting the OSM Service Connection Launching an OSM Service Connection Using OSM Bookmarks Verifying the OSM Service Connection State Running Multiple Sessions You can: ● Launch an OSM Service Connection ● Using OSM Bookmarks ● Verify the OSM Service Connection State ● Run Multiple Sessions Launching an OSM Service Connection 1.
want to access. 2. The first time you try to establish a service connection you are prompted Click here to download Java Runtime Environment. Select Open and install it according to the instructions. Then close the current browser, open a new browser, and repeat Step 1. Also, a dialog box appears, asking if you trust the signed applet distributed by Hewlett-Packard. You must select Yes or Always to establish a service connection.
For more information on LAN connectivity options and configuring more TCPIP stacks in the OSMCONF for additional fault tolerance, see the OSM Migration Guide. 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: ● 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 Chapter 3.
Chapter 5. Using the Management Window Chapter 5.
Tree Displays both system and cluster resources at the same time. Allows you to choose a view of the cluster or system: ● Select Physical from the view drop-down list to display a physical view. ● Select Inventory from the view drop-down list to display an inventory view. View Details The inventory view also contains a Save button. Provides Alarms and Attributes tabs to view specific information about the resource you selected in the overview, tree, or view pane.
Internet Explorer Menu Bar The standard Internet Explorer menu bar is not customized for, or fully compatible with, the OSM Service Connection. For most OSM functions, use the OSM toolbar and 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.
● You cannot use Internet Explorer's Add to Favorites menu option to create OSM bookmarks. For this functionality, see Create Bookmark on the OSM Tools menu. 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.
Indicates the current state of all OSM service connection processes. Each IP address listed is associated with a corresponding TCPIP stack Connection Status configured in the OSMCONF (OSM server configuration) file. You should have at least two connections with a status of UP for fault-tolerance. Displays a small dialog box containing a system icon, which changes color to indicate problems within the system.
Help Menu The Help menu contains: OSM online help Opens the OSM Service Connection help. Opens the About dialog box containing OSM product information, such as About OSM version number and trademarks. Using the Physical View The Physical view is displayed in the view pane of the Management window.
For more detail on items represented in the Physical view of a system, see the Physical view of an enclosure, the Inventory view, or the details pane. Procedure 5.2. To display the Physical view of a system: 1. In the tree or overview pane, select the system name. 2. From the View list, select Physical. Physical View of an Enclosure The Physical view of a group enclosure is similar to the way the group looks with the enclosure door open.
1. From the tree or overview pane, click ServerNet Cluster or System. 2. From the View list, select Inventory. Inventory View of a ServerNet Cluster The Inventory view of a ServerNet Cluster displays a complete or partial list of resources in the cluster, depending on the resource you select in the tree pane. The Inventory view of a ServerNet cluster displays: The logical name of a component in the cluster and the switch zone and Name fabric in which it is located.
Type Indication of the type of plug-in card, such as ECL or SSAC. Power State Indication of whether the component is powered on or off. Hardware Revision The hardware design revision, similar to a version number. The unique number assigned to every component. If you know a Track ID components part number and tracking ID, you can find its exact location in the system. The part number assigned to the component. Use this part number to Part Number order a replacement component.
State Indicators The color of system icon in the view pane shows the overall state of the system. A red or yellow icon displayed over a resource indicates that it requires service or operational intervention. Icons in the overview pane show the state of various resources. In the tree pane, a yellow arrow is displayed over a system, group, module, or parent object to indicate that one or more subcomponents require service or operational intervention.
On the alarms tab and detail In the Alarm Summary Alarm Severity Immediate corrective action is required. A service-affecting fault occurred. For example, a resource might have become unavailable. Urgent corrective action is required. A service-affecting fault has Major developed. For example, a resource might have lost fault tolerance. A fault exists that does not affect service. Corrective action should be taken to Minor prevent a more serious fault. For example, an unexpected path change occurred.
you want to find. 2. From the view pane drop-down list, select Inventory. If the Inventory view is already displayed, click one of its column headings to ensure that the view pane is active. 3. From the browser's Edit menu, select Find [on This Page].... 4. Type a resource name or an attribute value associated with the resource you want to find. 5. Click Find Next. If a resource with a matching value is found, the matching text is selected in the Inventory view. 6.
Chapter 6. Viewing Alarms Chapter 6. Viewing Alarms Viewing the Alarms Tab Viewing Alarms for a Selected Resource Viewing Alarm Details Suppressing Alarms Alarms can be viewed in these ways: ● On the Alarms tab of the Details pane: see Viewing the Alarms Tab. ● All alarms associated with a specific resource: see Viewing Alarms for a Selected Resource. ● A summary of alarms for the entire server or ServerNet cluster: see Viewing a Summary of Alarms.
Procedure 6.1. To view alarms: 1. In either the tree or view pane, click a resource. 2. In the details pane, click the Alarms tab to display the alarms for the selected resource. Procedure 6.2. To view alarm details: 1. Select Display>Alarms. 2. Click Detail on the Alarms screen. Viewing Alarms for a Selected Resource 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.
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.
Chapter 7. Viewing Attributes Chapter 7. Viewing Attributes Using the Details Pane to View Attributes Using the Attributes Dialog Box to View Attributes Suppressing Problem 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.
Procedure 7.2. To save the list of attributes: Click Save to display a Save dialog box. Procedure 7.3. To reach the attributes dialog box: Do one of: ● In the tree view, select a resource and select Display>Attributes. ● Right-click any resource and select Attributes from the menu that appears. ● In the physical view, right-click a resource and select Attributes from the menu that appears.
Chapter 8. Performing Actions Chapter 8.
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.) Procedure 8.1.
further refine the resource list. Procedure 8.4. To reach the Multi-Resource Actions dialog box: Do one of: ● Select Display>Multi-Resource Actions. ● In the Action dialog box, click Multi-Resources. Performing an Action 1. From the Resource Type drop-down list, select the type of resource on which to perform the action. (If you reach this dialog box from the Actions dialog box, the resource selected in the Actions dialog box appears in the Resource Type box.
As the action is performed, its status appears to the left of the resource name in the selected resources list. A summary of the action progress is shown in the Progress status boxes. 6. To view a summary of the actions, click Action Summary. (For information on action details, see Viewing Action Details.) Viewing Action Details The Action Detail box provides a description of a selected action, the resource acted upon, and the action status.
4. To further refine the resources on which to perform the firmware update, select a parameter from the Filter by drop-down list. Only resources in the available resources list with the specified characteristic are displayed. Some actions, such as SP Firmware Updates should not be performed on all SPs simultaneously. For these potentially disruptive actions, the Filter by menu forces you to choose between X-fabric or Y-fabric SPs.
Replace MSEB or SEB Replace Switch Component Replace MSEB SEB Replace ServerNet II Switch AC Transfer Switch UPS Switch Power Supply Switch Logic Board Switch Fan List of Available OSM Actions ServerNet Cluster Actions Resource Available Actions 6770 Switch Module Replace Set Locator 6780 Switch Module Blink All LEDs Off Blink All LEDs On Connect to UPS Replace Responsive Test Set Locator AC Transfer Switch Replace External ServerNet Fabric Node Connectivity ServerNet Path Test Rediscover Lo
ServerNet II Switch Blink LED Off Blink LED On Configuration Update Firmware Update Hard Reset Prepare to Replace Set Fabric Setting Soft Reset Switch Fan Blink LED Off Blink LED On Switch Logic Board Blink LED Off Blink LED On Configuration Update Dump Firmware Update FPGA Update Hard Reset Replace Soft Reset Switch PIC Blink LED Off Blink LED On Replace Switch Power Supply Blink LED Off Blink LED On Switch Node Port Node Responsive Test UPS Replace System Actions Resource Available Actions
CCSA Abort Start Stop Test Verify Disk Abort Backup Path Abort Disk Abort Primary Path Clear Data Firmware Update Power Off Power On Reset Backup Path Reset Disk Reset Primary Path Reset Volume Responsive Test Start Backup Path Start Disk Start Primary Path Start Volume Stop Backup Path Stop Disk Stop Primary Path Stop Volume Switch Process Pair Switch to Backup Path Switch to Primary Path Test Verify Validate Checksum E4SA Abort Disable ServerNet Port Enable ServerNet Port Start Stop
ESS Disk CRU External Disk Abort Backup Path Abort Disk Abort Primary Path Reset Backup Path Reset Disk Reset Primary Path Reset Volume Start Backup Path Start Disk Start Primary Path Start Volume Stop Backup Path Stop Disk Stop Primary Path Stop Volume Switch to Backup Path Switch to Backup Processor Switch to Primary Path Switch to Primary Processor Abort Backup Path Abort Disk Abort Primary Path Blink LED Off Blink LED On Clear Data Firmware Update Reset Backup Path Reset Disk Reset Primary Path Reset
Switch to Primary Path Test Verify Validate Checksum Fan Enable/Disable FESA Abort Start Stop FCSA Flash Boot Firmware Update Flash Firmware Update Replace Responsive Test Test Verify FCSA FSAC Responsive Test FSAC Responsive Test Test Verify FXSA / FX2SA Add LBU Delete LBU Dump Controller External Loopback Test Firmware Update Responsive Test Set FOX Cluster Number Set Left Transmitter Power Level Set Right Transmitter Power Level Start Stop Test Verify G4SA Abort Add Delete Power Off Reset St
G4SA SAC Abort Dump Firmware Update Responsive Test Start Stop Test Verify GESA Abort Start Stop Group Power Off Set Service LED State Internal ServerNet Fabric Group Connectivity ServerNet Path Test Start ServerNet Stop ServerNet IOMF Disable ServerNet Port Enable ServerNet Port Force Power Off Power Off Prepare to Power Off Replace Storage ASIC Initialization Test Test Verify IOAM (I/O Adapter Module) Read LCD Rediscover Set Locator Write LCD Line IOAM Enclosure Replace Enclosure or ServerNet
IOMF2 Disable ServerNet Port Enable ServerNet Port Force Power Off Power Off Prepare to Power Off Replace Storage ASIC Initialization Test Test Verify LIF Abort Delete Start Stop Maintenance Switch Link to Web Interface Rediscover Stop Monitoring MIOE Abort Start Stop MIOE PIF Abort Configure LIF Start Stop MIOE SAC Abort Responsive Test Start Stop Module Rediscover Redundant Power Scrub Monitored Service LAN Devices Start Monitoring Maintenance Switch Start Monitoring UPS MSEB Disable Serv
PIF Abort Configure LIF Start Stop PMF Disable ServerNet Port Enable ServerNet Port Force Power Off Power Off Prepare to Power Off Replace Storage ASIC Initialization Test Test Verify PMF2 Disable ServerNet Port Enable ServerNet Port Force Power Off Power Off Prepare to Power Off Replace Storage ASIC Initialization Test Test Verify Power Supply Replace Processor Disable Processor Freeze Halt Online Boot Millicode Firmware Update Reload Reset Responsive Test SAC Abort Firmware Update Responsive Te
ServerNet Switch Board Dump Memory Hard Reset ME FPGA Update ME Firmware Update Replace Set LED State Soft Reset Service Processor Processor Boot Millicode Firmware Update Reset Responsive Test SCSI Boot Code Firmware Update SP Firmware Update SNDA (ServerNet/DA) Replace Storage ASIC Initialization Test Test Verify SSAC (SCSI SAC) Responsive Test Storage Router Responsive Test SWAN / SWAN2 Start Stop Verify Logical Configuration SWAN CLIP Firmware Update Start Stop Test Backup Path Access Test
System Add Node to ServerNet Cluster Disable Advanced Storage Configuration Enable Advanced Storage Configuration Extend Problem Incident Report Suppression Time Rediscover System Rediscover System and ServerNet Cluster Suppress Problem Incident Report Creation Unsuppress Problem Incident Report Creation Tape Responsive Test Start Stop Switch Process Pair Test Extended Test Verify TRSA Abort Start Stop UPS (IOAM) Link to Web Interface Stop Monitoring Chapter 7. Viewing Attributes Chapter 9.
Chapter 9. Viewing Summary Reports Chapter 9. Viewing Summary Reports Viewing a Problem Summary Viewing a Summary of Actions Actions Not Displayed OSM Software-Triggered Actions Viewing Action Details Viewing a Summary of Alarms Viewing a Resource Summary You can view a: ● Problem Summary ● Summary of Actions ● Summary of Alarms ● Resource Summary Viewing a Problem Summary The Problem Summary lists all resources that are in a problem state.
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.
● Time and date the alarm occurred ● Resource name ● Description of the alarm, including probable cause and alarm type ● Whether the alarm is dialed out to your service provider (assuming your system console is configured to dial out) Procedure 9.3. To display detailed information for an alarm: Highlight the alarm and click Detail. Or right-click the alarm and select Detail from the menu that appears. See Viewing Alarm Details. Procedure 9.4.
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. Chapter 8. Performing Actions Chapter 10.
Chapter 10. Managing a System Chapter 10. Managing a System Locating and Viewing System Resources Monitoring a System Performing Actions on a System Updating Firmware 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.
● Checking for incident reports in the OSM Notification Director. The OSM Notification Director generates problem incident reports when critical changes occur to a resource on the system. ● Checking the OSM Event Viewer for events. The OSM Event Viewer displays events from EMS-formatted log files such as $0 and $ZLOG. ● Checking the internal X and Y fabrics to examine the systems connections between its groups.
Chapter 11. System Resources Chapter 11.
Attributes Actions Fan Attributes Actions FCSA Attributes Actions Removing and Installing a Fibre Channel ServerNet Adapter FCSA FSAC Attributes Actions FESA (Fast Ethernet ServerNet Adapter) CRU Attributes Actions FSAC (Fiber ServerNet Addressable Controller) Attributes Actions FXSA / FX2SA (ServerNet/FX / ServerNet/FX2) FRU Attributes Actions GESA (Gigabyte Ethernet ServerNet Adapter) CRU Attributes Actions G4SA Attributes Actions G4SA PIF Attributes Actions G4SA SAC Attributes Actions Group
Attributes Actions Internal ServerNet Fabric Attributes Actions IOAM (I/O Adapter Module) Attributes Actions IOAM Enclosure Attributes Actions IOAM Fan Attributes Actions IOAM Group Attributes Actions IOAM Power Supply Attributes IOMF (I/O Multifunction) CRU Attributes Actions IOMF2 (I/O Multifunction 2) CRU Attributes Actions LIF Attributes Actions Maintenance Switch Attributes Actions MIOE (Ethernet Controller) Attributes Actions
MIOE PIF Attributes Actions MIOE SAC Attributes Actions Module Attributes Actions Monitored Service LAN Devices Attributes Actions MSEB Attributes Actions PIC Attributes Actions PIF Attributes Actions PMCU Attributes Actions PMF (Processor Multifunction) CRU Attributes Actions PMF2 (Processor Multifunction 2) CRU Attributes Actions Power Supply Attributes Actions Replacement Guidelines and Precautions
Processor Attributes Actions SAC (ServerNet Addressable Controller) Attributes Actions SCSI Controller Attributes Actions SEB Attributes Actions ServerNet Switch Board Attributes Actions Service Processor (SP) Attributes Actions SNDA (ServerNet/DA) CRU Attributes Actions SSAC (SCSI SAC) Attributes Actions Storage Router Attributes Actions SWAN / SWAN2 CRU Attributes Actions SWAN Battery Attributes Actions SWAN CLIP
Attributes Actions SWAN Collection Attributes Actions SWAN FAN Attributes Actions SWAN LAN Logic Board (LANLB) Attributes Actions SWAN Line Attributes Actions SWAN Path Attributes Actions SWAN PS (Power Supply) Attributes Actions System Attributes Actions Tape Collection Attributes Actions Tape Attributes Actions TRSA (Token Ring ServerNet Adapter) CRU Attributes Actions Unknown CRU Attributes
Actions UPS (IOAM) Attributes Actions Common Attribute Values Battery Charge Status Compare State Device State Enabled State Group Type Path State Power State Processor State Processor Type Service State Tape Types Topology Using OSM, you can monitor and maintain these system resources: ATM Adapter CRU ATM Line IOAM IOAM Enclosure SCSI Controller SEB Battery IOAM Fan ServerNet Switch Board CCSA CRU Disk CRU E4SA CRU ESS Disk CRU IOAM Group IOAM Power Supply IOMF CRU IOMF2 CRU SSAC SNDA CRU Service P
G4SA FRU G4SA PIF PMCU PMF CRU G4SA SAC PMF2 CRU Group Power Supply Internal ServerNet Fabric Processor Tape Collection Tape Drive TRSA CRU Unknown CRU UPS (IOAM) SAC ATM3SA (ATM Adapter) CRU 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.
Indication of whether the ATM adapter software is automatically dumped to the specified dump file if the software abends abnormally. Automatic Dump State True: The software is automatically copied. False: The software is not automatically copied. Unknown: The Automatic Dump state could not be read. The type of media or cable, such as single-mode fiber or coaxial cable, supported by the ATM CRU. Indication of whether the ATM CRU firmware is automatically updated when the ATM CRU is started.
Responsive Test Verifies that the component is connected and responding. Start Starts the ATM CRU and the associated ATM line. The ATM CRU must be in the Stopped state before you perform this action. During startup, the controller operational code is automatically loaded into the ATM CRU. When the Start action finishes, the ATM CRU and the ATM line are in the Started state. Test Verify Runs all the firmware diagnostic tests on the CRU. This test takes about three minutes to finish.
Maximum Number of VCIs UNI Version Maximum Number of VPIs The maximum number of Virtual Circuit IDs (VCIs) that can be active for permanent virtual circuits. Value: 32 through 3072 The version of the User-Network Interface (UNI) supported by this ATM line. The maximum number of virtual path identifiers (VPIs) for permanent virtual circuits. Value: 0 through 256 ATM Address Registered The address that is registered for this ATM Line.
Service State Displayed in the Attributes tab and Attributes dialog box only if attention or service is required. Values Physical Power State Indication of whether the component is powered on. Values Logical The condition of the battery CRU. Fully Charged: The battery is fully charged. Charge State Charging: The battery is in the process of being charged. Critical: The battery needs recharging or replacement. Unknown: The battery is not responding, and its state cannot be determined.
The current combined voltage of both the upper and lower cells of the battery. Current Value If the Total Voltage falls below 42 volts, an alarm is generated. If the Total Voltage falls below the 39.6 volts, the battery is disconnected. Normal Maximum Value The maximum voltage that the battery can hold (60 volts). Actions Enable/Disable Prepares the battery to supply power when AC power is unavailable. The battery must be enabled to remain charged.
Logical The configuration type of this resource. Configured Type Device State Values: CCSA, E4SA, FESA, G4SA, GESA, TRSA, Unknown The state of the component as known to the NonStop Kernel operating system on the server. Values Actions Abort Terminates operation of the Common Communication ServerNet adapter (CCSA) CRU and its associated ServerNet addressable controller (SAC). When the Abort action finishes, the CCSA CRU and SAC are in the Stopped state.
Attributes Disk Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Physical Power State Indication of whether the component is powered on. Values The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component.
The name and location of the mirrored disk. Disk Pair Name Example: Disk $DATA00-M (1.1.2). Firmware Version The version of the firmware running on the disk. Backup Path SCSI ID SCSI Controller An identification number assigned to the device when configured. A number (1 or 2) that identifies the backup SCSI controller that manages the disk. Example: SCSI Controller (1.1.50.2) The accessibility of the backup path.
Abort Primary Path Terminates operation of the primary path to the disk. When the Abort action finishes, the path is in a Hard Down state. You must use the Reset Primary Path action before you can start the path again. Clear Data Erases all data on the disk but leaves the disk label intact. Clear Data does not erase the FIR data in the CE sector, the volume label, the boot sector, or the spare tracks table.
Reset Backup Path Places the backup path in a state from which it can be started. Reset Disk Places the disk in a state from which it can be started. This action might be necessary before starting a disk that has both paths in a Hard Down state; if a hardware error has occurred; if the disk was stopped with an Abort action; or if a Stop or Abort fails to put the disk into the Down state. If only one disk path is in a Hard Down state, you can use the Reset Primary Path or Reset Backup Path as appropriate.
Started state. This action fails if both paths to this disk are down and the mirrored disk is Up. For more information, see Start Disk. 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.
Validate Checksum Scans the user data area of a disk for sector checksum errors. If the action fails, the Action Details dialog box reports a sector checksum and suggests that you spare the sector only if you believe there is a drive media problem. To find additional information, use the OSM Event Viewer. Retrieve events using $ZLOG as the source criteria and RAL as the subsystem criteria, and look for Disk-sector-failure events (event number 7001).
Which, if any, ServerNet router ports on this CRU are disabled. OSM Disabled ServerNet Ports actions to disable or enable a ServerNet port are performed as directed by OSM alarm repair actions. The configuration type of this resource. Configured Type Values: CCSA, E4SA, FESA, G4SA, GESA, TRSA, Unknown The state of the component as known to the NonStop Kernel operating Device State 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.
Represents the actual presence of the FCSA FSAC containing the backup disk path SCSI controller. This attribute is displayed only if the physical FCSA FSAC is not present. A number that uniquely identifies the port through which the disk is connected. FSAC Port Name Primary Path Displays the configured location of the FCSA FSAC containing the Configured FSAC Location primary disk path SCSI controller. This attribute is displayed even if the physical FCSA FSAC is not present.
Terminates operation of the primary path to the disk. When the Abort action finishes, the path is in the Stopped state. Reset Backup Path Places the backup path in a state from which it can be started. Reset Disk Places the disk in a state from which it can be started.
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. Stop Volume Terminates all paths for the primary and mirror drives of this volume. When the Stop action finishes, the paths are in a Down state.
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.
Process Pair The fault-tolerance status of the disk environment. Redundancy Status Values: Fully Redundant, Redundancy Lost The processor number and PIN of the current backup disk I/O process. Backup Process ID Example: 1,269 The processor number and PIN of the current primary disk I/O process. Primary Process ID Example: 0,296 Disk Pair The name of the disk paired with this one.
Version The version of the firmware running on the disk. Actions Abort Backup Path Terminates operation of the backup path to the disk. When the Abort action finishes, the path is in a Hard Down state. You must use the Reset Backup Path action before you can start the path again. Abort Disk Terminates operation of the all paths for the disk. When the Abort action finishes, the paths are in a Hard Down state. You must use the Reset Disk action before you can start the paths again.
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. Responsive Test Verifies that the disk drive is installed and responding. Start Backup Path Starts the backup path to this disk drive. When the Start action completes, the backup path is in the started State. Start Disk Starts all paths to this disk drive. When the Start action completes, the all paths are in the Started state.
Stop Volume Terminates all paths for the primary and mirror drives of this volume. When the Stop action finishes, the paths are in a Down state. Switch Process Pair Switches the primary and backup disk I/O processes. Switch to Backup Path Switches processing from the primary to the backup path. Switch to Primary Path Switches processing from the backup to the primary path. Test Verify Runs the power-on self-test for the disk and tests the internal circuitry of the drive.
Attributes Disk Collection Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Actions None. 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.
The current fan speed, measured in rotations per minute (RPM). Current Value Alarms are generated if the speed of the fan falls below 1800 (minimum RPM) or rises above 5800 (maximum RPM). The maximum acceptable fan speed is 5800 RPM. If the speed rises Normal Maximum Value above 5800, an alarm is generated. Actions Enable/Disable Restores or stops power to the fan. After servicing the fan or its associated PMCU, perform the Enable action.
Part Number Track ID The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for tracking components. Flash Firmware Information about the version of the operational firmware located in the Flash memory of the FCSA. This firmware is not used in NonStop S-series systems as they do not support system load through the FCSA.
● Removing the FCSA ● Installing the Replacement FCSA Once you confirm that the FCSA has been replaced, OSM presents these options for bringing up the paths associated with this adapter: ● Bring up and balance. This option makes the -P (primary) and -M (mirror) paths active. ● Bring up only. This option starts the path only if the other path is already up. ● Leave down. Responsive Test Verifies that the FCSA is connected and responding. Test Verify Verifies basic functionality of the FCSA.
out of its slot to be unseated. If the adapter is not unseated far enough, a long connector pin in the midplane can still be engaged with the FCSA. This will make some software behave as though the FCSA is still in its slot, but broken. 6. Grasp the FCSA by its ejector in one hand and slowly pull the FCSA part way out of the slot. 7. Grasp the FCSA by its handle while supporting the bottom edge of the FCSA with the other hand and pull the FCSA the rest of the way out of the slot.
c. Set the FCSA down on an antistatic mat right side up with the ejector at the top. 4. Disconnect the grounding clip of your ESD wrist strap from the FCSA and connect it to any unpainted metal surface on the IOAM enclosure or on the rack in which the enclosure is installed. 5. Insert the FCSA: a. Using both hands, hold the FCSA so that its ejector is at the top. b. Insert the adapter into its slot in the enclosure. c. Firmly push the FCSA to the rear of its slot, but do not force it.
Note: The ports on the FCSA are numbered from top down when viewing 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). Attributes FCSA FSAC Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Logical A number (read from the hardware) that uniquely identifies each FCSA FSAC.
Attributes FESA Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Physical Power State Whether the component is powered on. Values The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component.
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 attention or service is required.
(FRUs) allow 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 processor or I/O enclosures (service side). Example: FX2SA (41.1.53) Attributes FX2SA Service State Displayed in the Attributes tab and Attributes dialog box only if attention or service is required. Values Physical Whether the component is powered on.
Indication of the current power level for the fiber-optic transmitter LED from the right direction: Low: The LED power for transmitting to the right direction is low, Right Transmitter Power Level suitable for shorter distances (less than 2 kilometers). High: The LED power for transmitting to the right direction is high, suitable for shorter distances (2 km to 4 km). Invalid: The LED power level to the right direction is unknown, possibly due to no response.
the ServerNet/FX or ServerNet/FX2 adapter. Dump Controller Writes the data from the memory of the ServerNet/FX or ServerNet/FX 2 adapter field-replaceable unit (FRU) to the file $SYSTEM.ZSERVICE.ZFOXDUMP. The ServerNet/FX FRU must be in the Stopped state to perform this action. External Loopback Test Performs the external loopback firmware diagnostic test.
Start Starts the ServerNet/FX or ServerNet/FX 2 adapter field-replaceable unit (FRU) that is in the Stopped state. During startup, the controller operational code is automatically loaded into the FRU. When the Start action completes, the FRU is in the Started state. 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.
A unique serial number that identifies the component. Track IDs are used for tracking components. A code that identifies the generation of the component. Hardware revision Hardware Revision codes are used for tracking components. Track ID Logical The configuration type of this resource. Configured Type Device State Values: CCSA, E4SA, FESA, G4SA, GESA, TRSA, Unknown The state of the component as known to the NonStop Kernel operating system on the server.
Location in OSM Tree: System > Group > IOAM Enclosure > IOAM > G4SA Example: G4SA $ZZLAN.G4SA1 (13.3.2) Attributes G4SA Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Physical Hardware Revision Part Number Track ID A code that identifies the generation of the component. Hardware revision codes are used for tracking components. The part number of the component that was assigned in manufacturing.
Physically powers off the G4SA. Reset Places the G4SA in a state from which it can be started. Start Starts the G4SA and the associated G4SA SAC. The G4SA and the SAC must be in the Stopped state before you perform this action. 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).
Hardware MAC Address The media access control (MAC) address of the PIF hardware. Displays the actual interface that is physically present. Interface Type Link Pulse State Maximum Speed Values: Copper, Fiber, and Unknown (if nothing is plugged in) A value of Up confirms that the cable from the PIF to the LAN is connected and operational. A value of Down indicates a problem with LAN connectivity. The maximum transmission rate for the ServerNet addressable controller.
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 attention or service is required.
Owning Processor The processor to which the G4SA SAC is connected. The currently available processors that can access the resource. Processor Access List Example: 0,1,4,8,9 Firmware Version Default File Name The version of the boot firmware for the SAC. 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. The differences, if any, between the current and default boot firmware Compare State versions.
Group A group contains all the components that are serviced by a pair of service processors (SPs). For S7x00, S7x000, and S86000 servers, an enclosure contains one group, and a group contains one module. Location in OSM Tree: Under System Example: Group 1 Attributes Group Service State Displayed in the Attributes tab and Attributes dialog box only if attention or service is required. Values Logical Indication of whether the service LED is on or off.
Turns the service light-emitting diode (LED) on or off for this group. Use this action to mark an enclosure to make it easily locatable for service. Parameter: Service LED State on: turns LED on off: turns LED off Internal ServerNet Fabric The system has two internal ServerNet fabric objects, the Internal_SvNet_X_Fabric and the Internal_SvNet_Y_Fabric, that give you a quick synopsis of the state of the two ServerNet fabric paths.
IOAM 13.2 is located in group 13, module 2. The other IOAM in this IOAM group is IOAM 13.3. Each IOAM contains: ● A ServerNet Switch Board ● Two IOAM Power Supplies ● Two IOAM Fans ● Up to five FCSA or G4SAs Note: If for any reason a ServerNet switch board is not present in a module, the fans, power supplies, and adapters in that module will not appear in OSM. Location in OSM Tree: System > Group > IOAM Enclosure > IOAM Example: IOAM 13.
Write LCD Line Allows you to edit the text displayed by the IOAMs LCD. You can modify lines 9 through 15 with this action. IOAM Enclosure An enclosure that contains two I/O Adapter Modules. Location in OSM Tree: System > Group > IOAM Enclosure Example: IOAM Enclosure 13 Attributes Logical Rack Name An arbitrary name assigned through the Set Rack Name and Offset action.
Attributes Physical Indicates whether or not the fans amber LED is lit. This state is determined by the Set LED State LED State action. Value: On or Off Logical The state of the component as known to the NonStop Kernel operating system on the Device State server. Values Actions Set LED State Turns on or off the amber LED located on the fan. The current state is indicated by the LED State attribute. IOAM Group A logical entity that represents a physical I/O Adapter Module enclosure.
IOAM Power Supply 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 see the CSSI web site. 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.
Slot Location: IOMF CRUs are located in slots 50 and 55 in I/O enclosures (service side). Example: IOMF (2.1.50) Attributes IOMF Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Physical Whether the component is powered on. Values The part number of the component that was assigned in manufacturing. Use Part Number part numbers for identifying and ordering parts. A unique serial number that identifies the component.
Actions Disable ServerNet Port Disables the specified ServerNet router 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 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.
becomes primary ● Disables the battery Replace Launches the Replace IOMF guided procedure, which provides step-by-step instructions for replacing the IOMF 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.
The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component. Hardware revision Hardware Revision codes are used for tracking components. Part Number Logical Fan Voltage The current voltage of the Fan CRU.
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. Parameter: Port Number Force Power Off This action is not supported for this CRU type. See the Prepare to Power Off action. Power Off This action is not supported for this CRU type.
CRU. If initialization fails, an alarm is generated. This action is triggered automatically when a new CRU is inserted while OSM is running or when an (SCF) STATUS ADAPTER command is issued. If a CRU is inserted while OSM is not running, perform this action after logging on to the OSM Service Connection. Test Verify Performs basic tests on the CRU. You can perform this action when the CRU is online.
Starts the LIF. Stop Rather than automatically stopping the LIF (as the Abort action does), this action first warns you if the LIF is currently in use (and stops it only after you confirm). Maintenance Switch An Ethernet switch that allows the OSM console to communicate with the Maintenance Entity (ME) in the ServerNet switch board.
Rediscover Causes OSM to refresh and reanalyze the object. Refresh refers to OSM updating the attribute values displayed in the OSM Service Connection interface. Reanalyze refers to the running of OSM incident analysis, which checks EMS event messages and creates alarms in OSM if certain conditions exist. Stop Monitoring Stops OSM from monitoring the maintenance switch. MIOE (Ethernet Controller) A component of PMF and PMF2 CRUs located in Group 1 only.
action completes, the MIOE is in the Started state. Stop Rather than automatically stopping the MIOE (as the Abort action does), this action first warns you if the MIOE is currently in use (and stops it only after you confirm). 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.
Stop Rather than automatically stopping the MIOE 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). 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.
Loads the controller operational code and starts the MIOE SAC. When the Start action finishes, the MIOE SAC is in the Started state. Stop Rather than automatically stopping the MIOE SAC (as the Abort action does), this action first warns you if the SAC is currently in use (and stops it only after you confirm). Module A set of components that share a common hardware interconnection, such as a backplane. Each enclosure of a system contains one or more modules.
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 OSM to start monitoring the maintenance switch. Start Monitoring UPS Causes OSM to start monitoring the UPS.
The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component. Hardware revision Hardware Revision codes are used for tracking components. Part Number Logical Which, if any, ServerNet router ports on this CRU are disabled.
Attributes PIC Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Physical Indication of the type of plug-in card. Type Values: NNA, Serial Copper, ECL, Long-Haul Fiber, Short-Haul Fiber Logical Connector Number A unique number used to distinguish between plug-in cards on an MSEB CRU. Actions Clear Loopback Test Clears the loopback test on a plug-in card (PIC).
Caution: Do not use the external loopback test on a PIC that you believe is operating normally. Doing so shuts down ServerNet traffic through the PIC for the duration of the test (several minutes). The action isolates the MSEB port occupied by the PIC, preventing the port from sending or receiving ServerNet traffic. ServerNet traffic resumes when the test is finished. Do not use the external loopback test if alarms are present on the peer fabric (the fabric opposite the PIC you intend to test).
Attributes PIF Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Logical Current Configured Speed The transmission rate for the ServerNet addressable controller. The transmission mode for the ServerNet addressable controller. Duplex Mode Values: Half Duplex, Full Duplex, Unknown Network MAC Address The media access control (MAC) address of the PIF network. The maximum transmission rate for the ServerNet addressable controller.
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.
Normal Maximum Value The maximum acceptable air intake temperature is 50 degrees Celsius. If the temperature rises above 50 degrees, an alarm is generated. Actions None.
Fan Voltage The current voltage of the Fan CRU. The voltage of the Main Rail, which supplies power to the CRU from its Main Rail Voltage own power supply This attribute indicates which, if any, ServerNet router ports on this CRU Disabled ServerNet Ports are disabled. OSM actions to disable or enable a ServerNet port are performed as directed by OSM alarm repair actions. The voltage of the SCSI-Y path, the path configured for mirrored disks on SCSI-Y Voltage a system.
are done by the Prepare to Power Off and Power Off actions. However, these steps are taken: ● If the SP on this PMF CRU is designated as Active (Primary), resets the SP so the peer SP becomes primary instead ● Disables the battery ● Halts the processor on this PMF CRU Power Off Upon successful completion of the Prepare to Power Off action, you can use the Power Off action to turn off power to the PMF2 CRU and all components.
● Disables the battery. ● Halts the processor on this PMF2 CRU. 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.
Power State Whether the component is powered on. Values The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component. Hardware revision Hardware Revision codes are used for tracking components. Part Number Logical Fan Voltage The current voltage of the Fan CRU.
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. Parameter: Port Number Force Power Off This action is not supported for this CRU type. See the Prepare to Power Off action. Power Off This action is not supported for this CRU type.
Launches the Replace PMF guided procedure, which provides step-by-step instructions for replacing the PMF2 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.
The state of the power supply CRU as known to the NonStop Kernel operating system Power State on the server. Values Logical Enabled State The initial state of the power supply component at the time of discovery. Values The state of the component as known to the NonStop Kernel operating system on the Device State server. Values Actions Replace Launches an interactive action to guide you through replacement of a power supply CRU. This action is valid for IOMF2 and most PMF enclosures.
● Before handling any CRU, obtain an electrostatic discharge (ESD) protection kit. Follow the directions on the kit for replacing a CRU to prevent damage to system components. ● Power cords might contain faulty connectors that, when touched, vibrated, or flexed, can cause intermittent power or the loss of a processor. ● Before replacing a power supply, visually check the power cord without touching the power cord.
3. Lower the ejector on the power supply to its fully open position. This action disconnects the power supply from the power interface board (PIB) and the AC power cord directly behind it.
4. With one hand, grasp the handle of the power supply and slide the power supply partway out of the slot. 5. Using your other hand to support the weight of the power supply, slide the power supply all the way 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. 3. 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. The green power-on LED above the replacement power supply should now be lit.
Processor A processor or central processing unit (CPU) in the server. The 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.
Whether the processors and service processors have been initialized after the most recent power-on. Initialized True: Processors and service processors have been initialized. False: Processors and service processors have not been initialized. The octal halt code emitted by the processor that halted. 0: No halt has occurred. Halt Code %53: System freeze occurred. %74: Software fault occurred. For details, see Lites Register.
systems running G06.11 or earlier. The related attributes and action are not displayed for processors on which this action is not supported. Default File Name Running Version The name of the file to be used for the Boot Millicode firmware update. The version of the Boot Millicode currently running on the processor. The version of the firmware to be used for the Boot Millicode firmware Default File Version update. The differences, if any, between the running and default firmware versions.
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.
Indicates whether the SAC boot firmware is automatically reloaded if it terminates abnormally: Automatic Boot State Enabled: The boot firmware is automatically reloaded. Disabled: The boot firmware is not automatically reloaded. Unknown: Automatic Boot state could not be read. Whether the SAC software is automatically dumped to the specified dump file if the software abends abnormally: Automatic Dump State Enabled: The software is automatically copied to a dump file.
Runs an online test that verifies the SAC is integrated with the LAN subsystem, is owned, and is in the Started state. Start Loads the controller operational code and starts the ServerNet addressable controller. The SAC must be in the Stopped state before you perform this action. When the Start action completes, the SAC is in the Started state. Test Verify Runs the power-on self-test for the SAC component of the CRU.
The bus to which the device is attached: SCSI Bus Number Bus 1 or 2: Internal device Bus 3: External device Actions Responsive Test Verifies that the component is installed and responding. 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.
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. Parameter: Port Number Replace Launches the Replace SEB guided procedure, which provides step-by-step instructions for replacing the SEB CRU.
A unique serial number that identifies the component. Track IDs are used for tracking components. A code that identifies the generation of the component. Hardware revision Hardware Revision codes are used for tracking components. Track ID Logical Time of Last Reset The date and time of the last processor soft reset. ME FPGA The VPROC of the ME FPGA (Field Programmable Gate Array) image currently loaded on the switch logic board.
Replace Launches a guided procedure, which provides step-by-step instructions for replacing the ServerNet Switch Board. Set LED State Turns the ServerNet Switch Board LED on or off. Soft Reset Performs a soft reset of the ServerNet switch board. Service Processor (SP) The service processor (SP) controls environmental and maintenance functions and acts as the master of the serial maintenance bus (SMB).
IP Address Current Topology The IP address of the service processor. The maximum processor configuration for the service processor. Values The state of the service processor: Active (Primary): This is the master service processor and is available. Active (Secondary): This is the not master service processor, but it is available. Device State Firmware Update Mode: An SP firmware update is in progress. In Test: Temporary state during power-on self-test. Initializing: Temporary state during startup.
Compare State The differences, if any, between the current and default firmware versions. Values Actions Processor Boot Millicode Firmware Update Updates the Processor Boot Millicode firmware for a single service processor (SP). Available only for SPs on PMF and PMF2 CRUs. Optional Parameter: File Namethe name of the Processor Boot Millicode firmware file on the local node. Syntax: $volume.subvolume Default value: $SYSTEM.
Syntax: $volume.subvolume Default value: $SYSTEM.SYSnn SNDA (ServerNet/DA) CRU 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.
Storage ASIC Initialization Test Prompts the storage subsystem manager process ($ZZSTO) to initialize the storage ASIC in the CRU. If initialization fails, an alarm is generated. This action is triggered automatically when a new CRU is inserted while OSM is running or when an SCF STATUS ADAPTER command is issued. If a CRU is inserted while OSM is not running, perform this action after logging on to the OSM Service Connection. Test Verify Performs basic tests on the CRU.
Logical The type of device supported by this SAC. Configured Type Values: Disk, Tape, SCSI Controller, Not Configured, Unknown Actions Responsive Test Verifies that the component is connected and responding. Storage Router This object represents one of these resources: SCSI Extender.
Attributes Storage Router Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Logical The type of router. Router Type Logical Device Number Values: SCSI Extender or SCSI-to-Fiber Converter The number assigned to the router by the file system. Whether the resource is communicating to the host system.
The number that identifies the SCSI controller that manages the storage router. SCSI Controller If this attribute is missing, it is because the SCSI Controller has been removed from the system. Example: SSAC (1.1.50.3) Actions Responsive Test Verifies that the resource is configured and responding.
Attributes SWAN $ZZWAN Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Physical The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component.
The name of the subnet on the primary TCP/IP process that supports the SWAN concentrator. Primary Subnet Name Format: TCPIP process name.subnet name Example: $ZTCP1.#SN1 The name of the subnet on the alternate TCP/IP process that supports the SWAN concentrator. Alternate Subnet Name Format: TCPIP process name.subnet name Example: $ZTCP3.#SN1 The primary gateway IP address configured for the SWAN Primary Gateway IP Address concentrator. Example: 192.168.10.
Example: Battery $ZZWAN.#SWAN2.BAT Attributes Battery $ZZWAN Service State Displayed in the Attributes tab and Attributes dialog box only if attention or service is required. Values Logical The charge status of the SWAN 2 battery. Charge Status Values: Charging, Critical (Discharging), Unknown The state of the component as known to the NonStop Kernel operating system on the Device State server. Values Actions None.
Device State The state of the component as known to the NonStop Kernel operating system on the server. Values Physical The part number of the component that was assigned in manufacturing. Use part numbers for identifying and ordering parts. A unique serial number that identifies the component. Track IDs are used for Track ID tracking components. A code that identifies the generation of the component. Hardware revision Hardware Revision codes are used for tracking components.
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 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 Displayed in the Attributes tab and Attributes dialog box only if attention or service is Service State required. Values Logical The state of the component as known to the NonStop Kernel operating system on the Device State server. Values Actions None.
Hardware Revision A code that identifies the generation of the component. Hardware revision codes are used for tracking components. Logical The status of the Ethernet link. Link State Values: Up, Down, Not Available The duplex mode of the connection between the logic board and the router. Duplex Mode Values: Half Duplex, Full Duplex, Not Available The maximum speed of the connection between the logic board and the router.
The state of the data link control (DLC) task associated with the line as known to DLC Task State the NonStop Kernel operating system. Values: Started, Stopped, Unknown The name of the WAN device associated with the line. Device Name Example: $TP6S1 If no device is configured, "FREE" is shown. Actions External Loopback Test Performs the external loopback firmware diagnostic test. Start DLC Task Starts the data link control (DLC) task associated with the SWAN Line.
The state of the SWAN Path as known to the NonStop Kernel operating system. Path State Values: Started, Stopped Actions Start Starts the SWAN Path. When the Start action completes, the SWAN Path is in the Started state. Stop Terminates operation of the SWAN Path. When the Stop action completes, the SWAN Path is in the Stopped state. Verify Logical Configuration Verifies that the SWAN Path is properly configured. If not, an Incorrect Logical Configuration alarm is generated on the SWAN Path.
Device State The state of the component as known to the NonStop Kernel operating system on the server. Values Actions None. 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).
The release version update of the NonStop Kernel operating system that is running on the server. Version Example: G06.19 Other values that might be displayed for Operating System Version are Not Running and Halted. System Services Indicates whether or not the system has been configured to allow advanced storage configurations. This feature is enabled/disabled using the Enable and Disable Advanced Storage Configuration actions.
The date and time the creation ability was suppressed. Time of Suppression Duration of Suppression This attribute is shown only if the Problem Incident Report Creation State value is Suppressed. How long the suppression will last (in minutes). The default value is 40 minutes. You can extend he time using the Extend Problem Incident Report Suppression Time action. This attribute is shown only if the Problem Incident Report Creation State value is Suppressed.
Enable Automatic Data Collection Changes the Automatic Data Collection State attribute value to Enabled, thus enabling automatic collection of data for failed system resources, provided the data collection volume, as specified by the Set Data Collection Volume action, is available. Supported resources include PMF, IOMF, SEB/MSEB, Battery, Fan, Power, Disk, Tape, SNDA, FXSA, and SWAN. To disable automatic collection of data, use the Disable Automatic Data Collection action.
you can choose to end the suppression immediately using this 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.
The availability of the tape: Ready: Tape is loaded. Ready Status Not Ready: No tape is loaded. Unknown: Tape status cannot be determined. Logical Device Number The number assigned to the drive by the file system. The type of tape drive. Values. Tape Type Product ID The tape drive product identification. The accessibility of the tape drive through the tape process. Device State Values: Up, Down, Hard Down Firmware version The version of the firmware.
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. When the Stop action completes, the tape drive is in the Stopped state. Note that Stop is a logical command and does not affect the hardware.
TRSA (Token Ring ServerNet Adapter) CRU 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.
Start Starts the TRSA CRU and the associated Token Ring SAC. The TRSA CRU must be in the Stopped state before you perform this action. During startup, the controller operational code is automatically loaded into the TRSA SAC. When the Start action completes, both the TRSA CRU and the Token Ring SAC are in the Started state. Stop Rather than automatically stopping the TRSA (as the Abort action does), this action first warns you if the TRSA is currently in use (and stops it only after you confirm).
Attributes UPS (IOAM) Indicates the current status of the UPS battery. Possible values are Normal and On Battery. OSM displays a yellow alarm if the UPS goes On Battery (or starts drawing power from the battery). This alarm goes away when the UPS stops drawing power from the battery. OSM displays a red alarm when the battery power is low. Device Status Indicates whether the UPS is up or down.
Stop Monitoring Stops OSM from monitoring the UPS. Common Attribute Values Battery Charge Status Value Absent Charged Charging Meaning The battery is not installed. The battery is fully charged The battery is in the process of being charged. The battery cannot supply power and cannot be charged, possibly because the Disable Disabled Battery action has been performed. You should disable a battery before removal. Discharged The battery needs recharging or replacement.
Stopping Unknown OK Processing is being terminated. Component is not responding. Component is accessible. Enabled State Value Meaning The component is present but not operational, possibly because the Disable action was Disabled performed. Enabled The component is operational. A problem was detected. The component might be functioning below standard or not Fault responding. Inspect the component. Off The component is not functional. On The component is functional.
Format Hard Down Inaccessible Revival Special Mount Unknown Up Disk format in progress. The disk volume or disk path was put in this state by an OSM Abort actionor an SCF ABORT command, or it is physically inaccessible because of a hardware error. In SCF, the equivalent state is STOPPED, substate HARDDOWN. Disk cannot be accessed. A mirrored disk is being updated. Only maintenance-type I/O operations can be performed on the disk. The disk might not be responding. The disk path is logically accessible.
The processor is primed for a memory dump using ServerNet. Submit memory dumps to your service provider for problem analysis. Primed for ServerNet Load The processor is primed for system load using ServerNet. Processor Hung The processor has stopped responding. Reload In Progress The system is reloading. Running NSK The processor is executing the NonStop Kernel operating system. This processor is dumping memory over ServerNet.
Tape Types Product ID CT9840-1 CT9840-2 CT9840-3 CT9840-4 CT9840FC-1 CT9840FC-3 CT9840FC-4 CT9841FC-1 CT9841FC-4 N1521A N1524A N1525A T5142 T5142ACL T515 (7-9) T517x T519x T5242 T5242ACL T5242-2SE T5257 T5257ACL T5259 T5258ACL T9490 VT5801 VT5900A VT5900B VT5900C VT5901 VT5902 Meaning 9840 cartridge tape drive mounted in an L700 tape library 9840 cartridge tape drive mounted in a 9710 tape library 9840 cartridge tape drive mounted on a NonStop S-series server 9840 cartridge tape drive mounted in a 9310 tap
Tetra 8 The system configuration is set to support a maximum of 8 processors. Tetra 16 The system configuration is set to support a maximum of 16 processors. Unknown Topology information cannot be determined. Chapter 10. Managing a System Chapter 12.
Chapter 12. Managing a ServerNet Cluster Chapter 12.
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. In the tree pane, select the resource. 2. 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.
Navigate to the ServerNet Cluster resource and check the value of the ServerNet Cluster State attribute. ● Monitoring the Expand-over-ServerNet lines. Navigate to a Remote ServerNet Node resource and check the value of the Line LDEV State attribute. This value indicates the state of the line between the local node and the selected remote node. Repeat this action for all remote nodes in the cluster.
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 Procedure 12.1. To specify the switch location: 1.
To update ServerNet II switch firmware: 1. In the tree pane of the OSM management window, expand the ServerNet Cluster resource and navigate to the switch component of the switch module. 2. Right-click the Switch component and select Attributes. In the Firmware section, check the value of the Compare State attribute. If it is Down-rev, continue with this procedure. 3. Right-click the Switch component and select Actions. The Actions dialog box appears. 4.
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. If you use OSM to manage a cluster with one of the star topologies, see the next paragraphs for differences between OSM and TSM. Some Cluster Resources Are Represented Differently in OSM. The OSM representation of the 6770 cluster switch used in the star topologies is more complete than the TSM representation.
Router Connections in a Layered Topology Router Connections for Switch Node Ports External Slot Port Internal Router 6 1 1 2 1 7 1 2 2 2 8 1 3 2 3 9 1 4 2 4 Port 0 1 0 1 0 1 0 1 Router Connections for Ports Connecting to Other Switches External Slot Port Internal Router Zone 2 1 5 2 5 3 1 5 2 5 Layer 11 1 3 2 4 3 1 4 2 12 1 2 2 1 3 4 4 3 13 1 1 2 2 3 3 4 4 Port 6 7 8 5 7 7 7 7 8 8 8 8 9 9 9 9 Router Connections for Router Interconnect PICs External Slot Internal Router Port Slot 4 1 4
Slot 5 2 3 3 1 2 3 4 Chapter 11. System Resources 5 4 5 6 4 5 4 Chapter 13.
Chapter 13. Cluster Resources Chapter 13.
Switch Fan Attributes Actions Switch Group Attributes Actions Switch Logic Board Attributes Actions Switch PIC Attributes Actions Switch Power Supply Attributes Actions Switch-to-Node PIC Attributes Actions Switch Node Port Attributes Actions Switch-to-Switch PIC Attributes Actions Switch Port Attributes Actions UPS (6770 Switch Module) Attributes Actions Common Attribute Values Service State
Fabric State Configuration Tag Port Connectivity Status 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.
Attributes Switch Module Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Logical Whether the switch is installed and responding. Presence Locator Values: Present, Absent, and Unknown User-assigned text that can be used to help identify the switch. The text is assigned by using the Set Locator action. Example: Switch On Left in 1205 The network topology and ServerNet nodes supported by this 6770 switch.
The subcomponents of the 6780 switch module are the Switch Logic Board, Switch PICs, Switch Ports, Switch Power Supply, and Switch Fan. Location in OSM tree: External ServerNet Fabric > Switch Group > Switch Module Example: Switch Module $ZZSMN.Y21 (1021.1) [The 6780 switch module on the Y fabric of zone 2, occupying layer 1] Attributes Switch Module Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required.
The current temperature, in degrees Celsius (°C), inside the enclosure of the module. The maximum acceptable air intake temperature is 65 degrees Normal Maximum Value Celsius. If the temperature rises above 65 degrees, an alarm is generated. Current Value Actions Blink All LEDs Off Turns off the blinking of the fault LEDs on the switch logic board, PICs, power supplies and fans.
Example: Switch On Left in 1205 SCF Equivalent: SCF ALTER SWITCH $ZZSMN, FABRIC { X | Y }, ZONE { 1 | 2 | 3 }, LAYER { 1 | 2 | 3 | 4 }, LOCATOR string 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 Group > Switch Module > AC Transfer Switch Example: AC Transfer Switch $ZSMN.
Cluster. Example: External ServerNet X Fabric Attributes External ServerNet X Fabric Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Logical The number of nodes that are currently connected to the ServerNet cluster Number of Nodes on this fabric, including the local node to which you are currently logged on. The connectivity state between processors on the local node and processors on remote nodes for this fabric.
that switch. Location in OSM tree: External ServerNet Fabric > Remote Switch The last part of the switch name indicates the fabric and position of the switch in the topology. Example: Remote Switch $ZZSMN.X2 Attributes Remote Switch Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required.
ServerNet Cluster A ServerNet cluster is a collection of NonStop S-series 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 Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required.
SNETMON Process Pair The fault-tolerance status of the SNETMON Process Pair. Redundancy Status Values: Fully Redundant, Redundancy Lost The processor number and PIN of the backup SNETMON process Backup/Process ID ($ZZSCL) running on the local node. The processor number and PIN of the primary SNETMON process Primary/Process ID ($ZZSCL) running on the local node. Actions Rediscover Causes OSM to refresh and reanalyze the object and all subcomponents.
Launches an interactive action that guides you in updating the network topology of a ServerNet cluster. You are prompted to temporarily disable dial-out alarms during the update process. For more information, see Updating ServerNet Cluster Topology. ServerNet Local Node This object represents the system within a ServerNet cluster to which you are currently logged on.
The state of the connection from the local node to the remote node over the external ServerNet X fabric. Up: At least one of the processors on the local node can communicate with at least one processor on a remote node over the X Fabric Connection State X fabric. Down: No processor on the local node can communicate with any processor on the remote node over the X fabric. Unknown: The state of the connection cannot be determined.
The state of the connection from the local node to the remote node over the external ServerNet Y fabric. Up: At least one of the processors on the local node can communicate with at least one processor on the remote node over Y Fabric Connection State the Y fabric. Down: No processor on the local node can communicate with any processor on the remote node over the Y fabric. Unknown: The state of the connection cannot be determined. The Expand node number of the local node.
The state of the Expand-over-ServerNet line configured from the Remote Line LDEV State remote node to the local node. Values: Up, Down, Unknown Actions Generate ServerNet Statistics Generates an event containing the ServerNet statistics from the local node to the remote node. ServerNet II Switch The component of the 6770 switch module that provides routing for the cluster over an external ServerNet fabric.
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 Configuration Configuration Tag Version A parameter used by SCF and the guided procedures that allows SANMAN to select an appropriate switch configuration block (SCB) from the M6770CL switch configuration library. The selected SCB is subsequently loaded on the specified switch.
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. For more information, see the ServerNet Cluster Manual. Optional Parameter: File name of the configuration file.
SCF Equivalent: SCF RESET SWITCH $ZZSMN, NEAREST { X | Y }, SOFT 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 Switch Fan Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Physical Whether the fan is installed and responding.
Causes the fault LED to blink on and off. 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.
Attributes Switch Logic Board Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Physical Part Number The part number of the switch logic board. The state of the fault LED on the switch logic board. Fault LED State Values: On, Off, On and Blinking, Off and Blinking Track ID The track ID of the switch logic board. Hardware Revision The hardware revision of the switch logic board. Logical The reason for last reset operation.
Compare State The differences, if any, between the current and default firmware versions. Values Configuration Configuration Tag A parameter used by SCF and the guided procedures that allows SANMAN to select an appropriate switch configuration block (SCB) from the switch configuration library. The selected SCB is subsequently loaded on the specified switch. The configuration tag determines the position of the cluster switch in the topology and the ServerNet node numbers supported by the cluster switch.
Planning and Installation Guide. Optional Parameter: File Namethe name of the configuration file on the local node Syntax: $volume.subvolume Default value: $SYSTEM.SYSnn Dump Copies a memory image from a 6780 switch to a specified file on the local system. Firmware Update Loads a firmware file from the local node to the switch logic board. For details, see the ServerNet Cluster 6780 Planning and Installation Guide. Optional Parameter: File Namethe name of the firmware file on the local node Syntax: $volume.
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.
Actions Blink LED Off Turns off the blinking of the LEDs. Blink LED On Causes the LEDs to blink on and off. Replace Invokes the Replace Switch Component guided procedure that helps to replace the switch PIC. 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.
The initial state of the component at the time of discovery. Enabled State Enabled: The component is operational. Disabled: The component is present but not operational. Whether the power supply has a fault. Device State Values: OK, Fault Actions Blink LED Off Turns off the blinking of the LEDs. Blink LED On Causes the LEDs to blink on and off. Switch-to-Node PIC A plug-in card (PIC) on the 6770 switch module that connects to a ServerNet node.
The state of connectivity between the switch and the node to which this PIC connects. Values: Connected Not Connected Connectivity Status Connected to Switch With Wrong Fabric Connected to Node Connected to Wrong Port Connected to Different Switch Connected to Switch With Wrong Configuration Unknown Whether the PIC is installed and responding. Presence Values: Present, Absent, Unknown The state of the external ServerNet fabric from the local node to the Fabric State remote node connected via this port.
Attributes Switch Node Port Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Transceiver Physical The type of transceiver. Type Example: 9/125 Micron SMF Part Number The vendor part number of the transceiver. Serial Number The vendor serial number of the transceiver. Hardware Revision The vendor hardware revision of the transceiver. Logical The status of the port.
Current Speed The speed of the port in bits per second. The initial state of the component at the time of discovery. Transceiver Device State Values: OK, Fault Whether the transceiver is enabled. Transceiver Enabled State Enabled: The component is operational. Disabled: The component is present but not operational. The state of the external ServerNet fabric from the local node to the remote node connected via this port.
Attributes Switch PIC Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Logical The state of connectivity between the switch and the node to which this PIC connects. Values: Connected Not Connected Connectivity Status Connected to Switch With Wrong Fabric Connected to Node Connected to Wrong Port Connected to Different Switch Connected to Switch With Wrong Configuration Unknown Whether the PIC is installed and responding.
PIC > Switch Port Example: Switch Port (1010.1.13.4) See also Router Connections for Ports Connecting to Other Switches. Attributes Switch Port Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Transceiver Physical The type of transceiver. Type Example: 50/125 - 62.5/125 Micron MMF Part Number The vendor part number of the transceiver. Serial Number The vendor serial number of the transceiver.
Current Speed Manage Port command not acknowledged (NACKed) from neighbor port Port enabled Invalid Unknown The speed of the port in bits per second. The initial state of the component at the time of discovery. Transceiver Device State Values: OK, Fault Whether the transceiver is enabled. Transceiver Enabled State Enabled: The component is operational. Disabled: The component is present but not operational. Neighbor Switch Port The name of the port to which this port is connected. Format: Port (Group.
Displayed in the Attributes tab and Attributes dialog box only if attention or Service State service is required. Values Physical The VA rating (volts multiplied by amps) and the firmware version of the UPS. CRU Type Example: UPS 1440 VA FW -0039 Part Number The part number of the UPS. Logical Estimated Charge Remaining The percentage of charge remaining in the UPS batteries.
The resource requires service. This condition generates an alarm, and the component that requires service is colored red in the tree pane and in the Physical and ServerNet views of the view pane. Service Required Fabric State Value Up Down Meaning At least one of the processors on the local node can communicate with at least one processor on one of the remote nodes. No processor on the local node can communicate with a processor on any remote node. This value is the default.
Link alive, port disabled, neighbor check in progress Link alive, port disabled, neighbor check complete Link alive, port disabled, neighbor check failed (Not connected) Link alive, port disabled, neighbor check failed (Connected to switch) Link alive, port disabled, neighbor check failed (Connected to node) Link alive, port disabled, neighbor check failed (Connected to switch with invalid configuration version identifier) Link alive, port disabled, neighbor check failed (Connected to switch with incompatib
Chapter 14. Updating ServerNet Cluster Topology Chapter 14.
● 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.
These three methods are supported for updating to the split-star or tri-star topology: ● Merging two star topologies to create a split-star topology ● Merging a star topology with a split-star topology to create a tri-star topology ● Merging three star topologies to create a tri-star topology The major steps in updating a topology are: 1. Review the planning information in the ServerNet Cluster Manual for your type of update.
configuration tags for the switches in one star topology to support node numbers 9 through 16. Change the configuration tags for the switches in another star topology to support node numbers 17 through 24. (The remaining star topology should already use node numbers 1 through 8.) Note: Changing the configuration tag requires a hard reset of the switches, resulting in a temporary disruption of ServerNet connectivity.
ServerNet Cluster Manual. 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.
X1 Y1 Y1 Y1 Y1 11 8 9 10 11 X2 Y2 Y2 Y2 Y2 11 8 9 10 11 Updating to the Tri-Star Topology If you are updating to the tri-star topology, connect the cables as follows: Cluster Switch X1 X1 X1 X1 X2 X2 Y1 Y1 Y1 Y1 Y2 Y2 Port Connects to Cluster Switch 8 X2 9 X2 10 X3 11 X3 8 X3 9 X3 8 Y2 9 Y2 10 Y3 11 Y3 8 Y3 9 Y3 Port 10 11 8 9 10 11 10 11 8 9 10 11 Cable Connections in a Layered Topology Connections Between Layers Within a Switch Group This table lists the connections between layers within a switch g
X11/Y11 X11/Y11 X11/Y11 X12/Y12 X12/Y12 X12/Y12 X12/Y12 X12/Y12 X12/Y12 X12/Y12 X12/Y12 X13/Y13 X13/Y13 X13/Y13 X13/Y13 13 13 13 12 12 12 12 13 13 13 13 11 11 11 11 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 X14/Y14 X14/Y14 X14/Y14 X14/Y14 X14/Y14 X14/Y14 X14/Y14 X13/Y13 X13/Y13 X13/Y13 X13/Y13 X14/Y14 X14/Y14 X14/Y14 X14/Y14 13 13 13 12 12 12 12 13 13 13 13 11 11 11 11 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 X Fabric Connections Between Two Zones This table lists the X-fabric connections between two zones of a layered topo
Y Fabric Connections Between Two Zones This table lists the Y-fabric connections between two zones of a layered topology: Switch PIC Slot Port Connect to Switch PIC Slot Port Y11 2 1 Y21 2 2 Y11 2 2 Y21 2 1 Y11 3 1 Y21 3 2 Y11 3 2 Y21 3 1 Y12 2 1 Y22 2 2 Y12 2 2 Y22 2 1 Y12 3 1 Y22 3 2 Y12 3 2 Y22 3 1 Y13 2 1 Y23 2 2 Y13 2 2 Y23 2 1 Y13 3 1 Y23 3 2 Y13 3 2 Y23 3 1 Y14 2 1 Y24 2 2 Y14 2 2 Y24 2 1 Y14 3 1 Y24 3 2 Y14 3 2 Y24 3 1 X Fabric Connections for Three Zones This table lists the X-fabric connections f
X14 X14 X14 X21 X21 X22 X22 X23 X23 X24 X24 2 3 3 2 3 2 3 2 3 2 3 2 1 2 1 1 1 1 1 1 1 1 X34 X24 X34 X31 X31 X32 X32 X33 X33 X34 X34 2 3 3 2 3 2 3 2 3 2 3 1 2 1 2 2 2 2 2 2 2 2 Y Fabric Connections for Three Zones This table lists the Y-fabric connections for three zones of a layered topology: Switch PIC Slot Port Connect to Switch PIC Slot Port Y11 2 1 Y21 2 2 Y11 2 2 Y31 2 1 Y11 3 1 Y21 3 2 Y11 3 2 Y31 3 1 Y12 2 1 Y22 2 2 Y12 2 2 Y32 2 1 Y12 3 1 Y22 3 2 Y12 3 2 Y32 3 1 Y13 2 1 Y23 2 2 Y13 2 2 Y33 2 1
Y24 Y24 2 3 1 1 Chapter 13.
Glossary Glossary AB CD E FGHI J KL M NOP QRS T U VWX YZ A action An operation, such as a diagnostic test, that can be performed on a selected resource. Use the Actions dialog box to display and perform actions. Examples Load (action on a selected processor) Up (action on a selected disk) 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.
See also event message and incident report appearance side The side of a system group enclosure that has a door and contains disk CRUs and PMCU FRUs. The appearance side is the side opposite the service side. asynchronous A mode of serial-data transmission in which characters are sent at random and the transmission is not synchronized with a separate clock signal. That is, there is no timing relationship between the end of one character and the start of the next.
board A frame on which computer circuitry is mounted. Same as logic board. boot A synonym for load. bus A system or subsystem data path that provides serial or parallel interconnection for multiple modules or components. Examples of buses are the serial maintenance buses (SMBs) and the small computer system interface (SCSI) buses. C client A software process, hardware device, or combination of the two that requests services from a server.
The topological cluster switch position within a cluster switch group. Each cluster switch group can contain up to four layers, numbered 1 to 4 from bottom to top. A cluster switch layer consists of a pair of cluster switches (X and Y) and provides connections for up to eight ServerNet nodes. Layers within a group are interconnected by intragroup cables. When all four layers are present, the intragroup cables are configured as a vertical tetrahedron. See also cluster switch layer number.
before you can proceed. customer-replaceable unit (CRU) A server component that can be removed and installed by customers with minimal training. CRUs are considered to be a subset of field-replaceable units (FRUs). D darksite A location where no operator is working on site and the only access to the LAN is from a centralized monitoring station through a modem connected to a routing workstation. Darksite is a synonym for unattended site.
A device that stores data on a disk and provides random access to addressable locations on the disk. There are two types of disk drives: ● On magnetic drives, access is provided by magnetic read/write heads. ● On optical drives, access is provided by a low-intensity laser beam. disk volume A logical disk drive. A volume can be one or two physical drives. In NonStop S-series servers, volumes have names that begin with a dollar sign ($), such as $DATA.
ports. Event Management Service (EMS) A Distributed Systems Management (DSM) product that is used to provide event collection, event logging, and event distribution facilities. EMS provides different event descriptions for interactive and programmatic interfaces, lets an operator or an application select specific event-message data, and allows for flexible distribution of event messages within a system or network.
A single-ported ServerNet adapter that supports 100-megabit/second (Mbps) or 10-Mbps Ethernet data transfer rates on an HP NonStop" S-series server. The 3863 FESA installs directly into an available I/O port. Fiber Optic Extension (FOX) Refers to two products, FOX II and ServerNet/FX, which allow you to create high-speed (up to 4 megabytes/second) networks of as many as 14 systems connected by dual fiber-optic cables.
processors. In a NonStop S-series server, there is one group in a system enclosure, and each group consists of a single module. See also enclosure, module, customer-replaceable unit (CRU), and field-replaceable unit (FRU). guided procedure A software tool that assists you in performing complex configuration or replacement tasks on an NonStop S-series server. OSM guided procedures are launched through actions in the OSM Service Connection. Guided procedures include Replace PMF, IOMF, SNDA, SEB, or MSEB.
logic board, a midplane, plug-in cards, power supplies, and fans. See also HP NonStop Cluster Switch (model 6770). I incident report (IR) A report sent by the OSM software on the server to the OSM Notification Director on the OSM system console. Incident reports notify you of changes that could directly affect the availability of resources, changes in hardware configuration, and changes in software configuration.
See also ServerNet addressable controller (SAC). I/O multifunction (IOMF) CRU A customer-replaceable unit (CRU) that connects an I/O enclosure to a processor enclosure through a ServerNet cable and supplies power to the components within the IOMF CRU as well as redundantly to the disk drives, SCSI terminators, and ServerNet adapters in that enclosure.
(model 6780). The layered topology can scale by adding cluster switch layers or zones. The layered topology supports up to four layers and three zones. See also star topology. light-emitting diode (LED) A semiconductor device that emits light from its surface. LEDs are used as indicator lights on CRUs and FRUs in NonStop S-series servers. line The specific hardware path over which data is transmitted or received.
logical interface (LIF) A process that allows an application or another process to communicate with data communications hardware. logical name An attribute of a resource that is either assigned to the I/O process associated with the resource during configuration using the Subsystem Control Facility (SCF) or that represents the type of resource or its location. When you are logged on to the OSM Service Connection, you can use the logical name to locate a resource.
nodes). The overview pane does not appear in the OSM Low-Level Link. The top pane is the view pane. It might contain a Physical view or an Inventory view. You can select the type of view from the Display menu or the toolbar. The lower pane is the details pane. It displays the specific information about the selected resource. Click a tab to select the type of information to display in the details pane.
drive can continue operations. Each drive has the same volume name, but the name has a suffix to show which drive is the primary (-P) and which is the mirror (-M). See also volume. modular ServerNet expansion board (MSEB) A ServerNet expansion board (SEB) that uses plug-in cards (PICs) to provide a choice of connection media for routing ServerNet packets. module A set of components sharing a common hardware interconnection, such as a backplane.
Examples of logical names: ● $DATA04-P is the logical name of the disk CRU located in group 1, module 1, slot 13. ● PMF.SCSI-3.GRP-1.MOD-1.SLOT-50 is the logical name of the third SCSI bus on the PMF CRU located in group 1, module 1, slot 50. Examples of service processor (SP) logical names: ● SCSICRU.GRP-1.MOD-1.SLOT-3 is the SP logical name of the disk CRU located in group 1, module 1, slot 3. ● PMF.SCSI-3.GRP-1.MOD-1.
A component of the OSM software that lets you set up criteria to view log files in several ways, enabling you to rapidly assess service problems. The OSM Event Viewer is launched from within the OSM Low-Level Link and the OSM Service Connection. OSM Low-Level Link A component of the OSM software that enables you to communicate with a server when the NonStop Kernel operating system is not running, as long as both the server and the workstation have power.
A pair of service processors (X and Y) in a service processor (SP) domain. See also master service processor (MSP) and expansion service processor (ESP). pending incident report An incident report that has never been delivered to your service provider, either because delivery to both the primary and the backup sites was unsuccessful or because the incident report was generated at an unattended site. See also periodic incident report, problem incident report, and software configuration incident report.
port A physical connector to which a cable can be attached. The system transmits and receives data or requests through ports on ServerNet adapters and processor multifunction (PMF) CRUs. A port is also called a connector. power domain A set of customer-replaceable units (CRUs) and field-replaceable units (FRUs) that share a set of power rails. See also serial maintenance bus (SMB) domain.
cluster. A problem incident report is generated when changes occur that could directly affect the availability of resources. Problem incident reports include the system configuration file and might include other attachments, such as alarm logs and processor diagnostic information. See also periodic incident report. processor A functional unit of a computer that reads program instructions, moves data between processor memory and the input/output controllers, and performs arithmetic operations.
refresh An action that updates the attribute values displayed in the OSM Service Connection interface. See also reanalyze. remote access A form of remote support. Remote access, or dial-in, allows a remote service provider to dial in to your server to diagnose hardware and software problems. Remote access and remote notification are not available in countries where the modem provided by HP is not certified.
S SANMAN Abbreviation for the external system area network manager process. A NonStop Kernel process that provides management access to the external ServerNet fabrics. SCSI plug-in card A plug-in card (PIC) for the 6760 ServerNet device adapter (ServerNet/DA) that uses a small computer system interface (SCSI) interface to connect devices to an NonStop S-series system. See also plug-in card (PIC).
A customer-replaceable unit (CRU) that connects peripheral devices to the system through a ServerNet bus interface. 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.
distinction between the two is not required. ServerNet wide area network (SWAN) 2 concentrator An HP data communications peripheral that provides connectivity to an HP NonStop" S-series server. The SWAN 2 concentrator supports both synchronous and asynchronous data over RS-232, RS-449, X.21, and V.35 electrical and physical interfaces. The SWAN 2 concentrator is the next-generation SWAN concentrator and has 12 WAN ports.
1. A person trained and qualified to service field-replaceable units (FRUs) associated with a NonStop S-series server. 2. An organization, such as the Global Customer Support Center (GCSC), that helps you resolve problems with your server or ServerNet cluster. OSM allows you to utilize the help of a service provider by configuring OSM to support remote notification and remote access.
source One of two selection types for filtering OSM status messages. These category types are supported: SNMP OSM encountered an SNMP protocol error. The OSM client or server application encountered an error while SP Interface performing an OSM operation. System The OSM operation failed due to a system error. The user specified an incorrect value for the requested operation. Check the User specified value and retry the operation.
Subsystem Control Facility (SCF) An interactive interface for configuring, controlling, and collecting information from its subsystems. super group The group of user IDs that have group number 255. This group has special privileges. Many NonStop Kernel operating system utilities contain commands or functions that can be executed only by a member of the super group. super ID A privileged user in the NonStop Kernel operating system environment who can read, write, execute, and purge all files on the system.
A condition encountered by the server while performing a command or other operation that causes the command or operation to fail. system image tape (SIT) The tape used when a processor is loaded from tape in an emergency situation. The SIT, which is generated by the SYSGENR program and copied to tape by the BACKUP program, contains a minimum set of software needed to bring up and run the system. The SIT contains tape boot, disk boot, and NonStop Kernel operating system images.
tetrahedral topology. tetrahedral topology A topology of NonStop S-series servers in which the ServerNet connections between the processor enclosures form a tetrahedron. 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.
The star groups are joined by two-lane links. The tri-star topology supports up to 24 nodes. See also split-star topology, star topology, and layered topology. two-lane link The two single-mode fiber-optic (SMF) ServerNet cables that connect the HP NonStop Cluster Switches on the same external fabric (for example, X1, X2, and X3) in a tri-star topology.
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.
See also fabric. Y Y fabric The Y side of the internal or external ServerNet fabrics. See also fabric. Z No entries at this time. Chapter 14.
© Copyright 2004 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 vendors standard commercial license. The information contained herein is subject to change without notice.
OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.