HP NonStop S-Series System Expansion and Reduction Guide Abstract This guide describes how to expand or reduce an HP NonStop™ S-series system by adding or removing enclosures. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports G06.24 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
Document History Part Number Product Version Published 522465-002 N.A. May 2002 522465-003 N.A. August 2002 522465-004 N.A. May 2003 522465-005 N.A. September 2003 522465-006 N.A. September 2004 522465-009 N.A.
HP NonStop S-Series System Expansion and Reduction Guide Glossary Index Figures What’s New in This Guide ix Guide Information ix New and Changed Information Tables x About This Guide xi Who Should Read This Guide xi Section Abstracts xii Where to Get More Information xiii Notation Conventions xv 1.
3. Planning System Reduction Contents Block Structures 2-2 Supported Block Structures 2-3 Examples of Block Structures 2-4 Choosing Which Block Structure to Use 2-8 Example of Choosing a Block Structure 2-8 Enclosures From Another System 2-14 3.
. Reducing a System Offline Contents 8. Prepare Enclosures for Removal 4-11 8.1 Disable Batteries in the Enclosure 4-11 8.2 Halt Both Processors in a Processore Enclosure 4-11 8.3 Disable ServerNet Ports in Y-fabric MSEBs (or SEBs) 4-12 8.4 Remove Cables from Disabled ServerNet Ports on Y-fabric 4-13 8.5 Power Off Enclosure 4-14 8.6 Disable ServerNet Ports in X-fabric MSEBS 4-15 8.7 Remove Cables from Disabled ServerNet Ports on X-fabric 4-16 8.8 Reenable Disabled ServerNet Ports on both fabrics 4-16 8.
Contents 6. Expanding a System Online 8. Change Group Number of Enclosure to 01 6-16 9. Power On Enclosure 6-17 10. Verify Connection Between System Console and Enclosure 6-18 10.1 Verify Connection to ServerNet X Fabric 6-18 10.2 Verify Connection to ServerNet Y Fabric 6-18 11. Configure System Console and Enclosure 6-19 11.1 Check and Upgrade OSM and TSM Client Software If Necessary 6-19 11.2 Enter Enclosure IP Addresses 6-19 12. Verify SP Firmware Is Compatible 6-20 12.
. Troubleshooting Contents 7.
B. ServerNet Cabling Contents Stop the OSM or TSM Low-Level Link A-8 Start a Startup TACL Session A-9 Start the OSM or TSM Low-Level Link A-9 Start the OSM Service Connection or TSM Service Application A-9 B. ServerNet Cabling C. Checklists and Worksheets D.
Contents Table 4-4. Table 6-1. Table 6-2. Table 6-3. Table B-1. Table B-2. Table D-1.
Contents HP NonStop S-Series System Expansion and Reduction Guide—522465-009 viii
What’s New in This Guide Guide Information HP NonStop S-Series System Expansion and Reduction Guide Abstract This guide describes how to expand or reduce an HP NonStop™ S-series system by adding or removing enclosures. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports G06.24 and all subsequent G-series RVUs until otherwise indicated by its replacement publication.
New and Changed Information What’s New in This Guide New and Changed Information These changes have been made to this version of the manual: Section Section 4, Reducing a System Online Change • • Appendix B, ServerNet Cabling • Connections between router ports and the ServerNet cable connectors on SEBs and MSEBs have been added to 8.
About This Guide This guide describes how to expand or reduce a NonStop S-series system by adding or removing enclosures. This guide does not describe operations information for ServerNet clusters. For information regarding the installation, configuration, and management of HP NonStop ServerNet cluster hardware and software, see the ServerNet Cluster Manual and the ServerNet Cluster 6780 Planning and Installation Guide.
Section Abstracts About This Guide Section Abstracts Section Title Abstract 1 The Resizing Process This section gives background information necessary to understand system resizing. 2 Planning System Expansion This section defines the concept of blocks and describes how to use the worksheets in this guide to plan the orderly addition of enclosures. 3 Planning System Reduction This section defines the concept of a donor system and describes how to plan the orderly removal of enclosures.
About This Guide Where to Get More Information Where to Get More Information Manuals For abstracts of the NonStop S-series manuals, see the NonStop S-Series Planning and Configuration Guide. CSSI Web The CSSI Web provides procedures, part numbers, troubleshooting tips, and tools for servicing NonStop S-series systems. A link to the CSSI web can be found in the left navigation area of the NTL home page.
About This Guide Guided Replacement Procedures Guided Replacement Procedures This guide refers to the guided replacement procedures. These automated tools guide you step by step through replacing many customer-replaceable units (CRUs). Guided procedures are part of the HP Open Systems Management (OSM) package and the Compaq TSM package. OSM is the system management tool of choice for HP NonStop S-series systems.
About This Guide Notation Conventions Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
About This Guide Notation for Messages Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.
1 The Resizing Process This section gives background information necessary to understand system resizing.
The Resizing Process Prerequisites Prerequisites To resize a NonStop S-series system online: You must be familiar with: The system you are planning to resize must be: • • • • • • OSM or TSM software package HP NonStop Kernel operating system Subsystem Control Facility (SCF) NonStop S-series system Fully functional Currently running the following software and firmware if you are planning to reduce the system online: ° ° ° The system you are planning to resize must have: G06.
The Resizing Process Planning for Resizing For planning purposes, an IOAM enclosure is equivalent to an S-series I/O enclosure. In Section 2, Planning System Expansion, examples of blocks using I/O enclosures also apply to IOAM enclosures. However, IOAM enclosures may only be able to occupy certain positions in the topology. See you service provider for details. IOAM enclosures are physically different from I/O enclosures and contain different components with different slot numbering.
The Resizing Process Should You Install a New RVU? number of processors in the system after expansion. Your system probably contains only the correct number of MSEBs and MSEB PICs for its current configuration. Before you expand your system, be sure you have the appropriate number of MSEBs and MSEB PICs.
The Resizing Process Topology Topology The topology of your system is the basic structure of your system. Your system can be configured for either of two topologies: Tetra 8 or Tetra 16. Each topology has advantages, depending on how you use your system and how you plan to resize it in the future. Note. It is important to decide ahead of time which system topology you want in your resized system because topologies cannot be changed online.
The Resizing Process Impact on Users Benefits of Different Topologies The benefits of Tetra 8 topology are: • • ServerNet adapters can be put in slots that in Tetra 16 topology are reserved for SEBs and MSEBs. If your current needs are satisfied by a Tetra 8 topology, you do not have to purchase the extra hardware that a Tetra 16 topology requires. The benefits of Tetra 16 topology are: • You are not limited to the Tetra 8 maximums of eight processors and two I/O enclosures per processor enclosure.
The Resizing Process System Configuration Because the communication between and among enclosures is the basis of how your system operates, you should understand the principles of system communication: For Information About See Communication paths in your system NonStop S-Series Planning and Configuration Guide System Configuration To resize your system safely, you must know how every device in your system is configured.
The Resizing Process Site Planning The procedures in this guide assume the use of one system console. Site Planning The physical layout of your site affects how easy it is to service and operate your system.
The Resizing Process • Other Issues Emergency power-off (EPO) cables (required by some countries) For Information About See Principles of cabling enclosures NonStop S-Series Planning and Configuration Guide How to place enclosures so that cabling is easiest NonStop S-Series Planning and Configuration Guide Attaching and removing cables NonStop S-Series Hardware Installation and FastPath Guide Other Issues Because every system is different, this guide cannot predict every planning issue.
The Resizing Process HP NonStop S-Series System Expansion and Reduction Guide—522465-009 1-10 Other Issues
2 Planning System Expansion This section defines the concept of blocks and describes how to use the worksheets in this guide to plan the orderly addition of enclosures.
Planning System Expansion • Rules for Creating a Block Two or more I/O enclosures without a processor enclosure. This unit is not a block because if more than one I/O enclosure is in a block, the I/O enclosures must be attached to a processor enclosure. You can think of a block as a subcomponent of your system, or part of a corner of a tetrahedron as described in the NonStop S-Series Planning and Configuration Guide.
Supported Block Structures Planning System Expansion The most useful way to structure the blocks for your system varies depending on your needs and the configuration of your system: For Information About The basic considerations of system topology and how it affects the number of enclosures your system contains How your needs dictate system topology Points to consider when choosing block structure See • • • • NonStop S-Series Planning and Configuration Guide Choosing a Topology on page 1-5 Benefits of
Examples of Block Structures Planning System Expansion Examples of Block Structures If you want to add two processor enclosures and two I/O enclosures to your system, you can combine them into four, three, or two blocks. Note. In the examples in this section, an I/O enclosure could instead be an IOAM enclosure. An IOAM enclosure is considered a group and can take the place of an I/O enclosure in the topology.
Examples of Block Structures Planning System Expansion Three Blocks Your system can accept combinations of enclosures as well as single enclosures: • • • One I/O enclosure becomes one block. You add this block to a processor enclosure that already exists on the system. One processor enclosure becomes one block. One processor enclosure supports one I/O enclosure. This combination becomes one block. Figure 2-2 illustrates how four enclosures can become three blocks : Figure 2-2.
Examples of Block Structures Planning System Expansion Two Blocks (Two Structures) Your system can accept combinations of enclosures as well as single enclosures. Furthermore, these combinations can be different sizes. Structure 1 • • One processor enclosure becomes one block. One processor enclosure supports two I/O enclosures. This combination becomes one block. Figure 2-3 illustrates how four enclosures can become two blocks of different sizes: Figure 2-3.
Examples of Block Structures Planning System Expansion Structure 2 • • One processor enclosure supports one I/O enclosure.This combination becomes one block. The other processor enclosure supports the other I/O enclosure. This combination becomes one block. Figure 2-4 illustrates how four enclosures can become two identical blocks: Figure 2-4.
Planning System Expansion Choosing Which Block Structure to Use Choosing Which Block Structure to Use Because there are so many different ways to combine enclosures into blocks, plan ahead of time which block structures will best meet your needs.
Example of Choosing a Block Structure Planning System Expansion Example Step 1: Copy Worksheets for Your System If you have a Tetra 16 system, locate and copy Worksheets 5 and 6 from Appendix C, Checklists and Worksheets. This figure shows an example of Worksheet 5, copied and ready to map your current system: Worksheet 5 Added Blocks — Tetra 16 Topology, X Fabric Shade in the enclosures, ports, and slot numbers that are in use in your current configuration.
Example of Choosing a Block Structure Planning System Expansion Example Step 2: Eliminate Unsupported Enclosures Consult your service provider about how many I/O enclosures are supported for the RVU running on your system. This example assumes that you are reconfiguring a NonStop Sxx000 system that supports 36 I/O enclosures, so you mark off the unsupported I/O enclosures as shown.
Example of Choosing a Block Structure Planning System Expansion Example Step 3: Shade In Existing System Enclosures Shade in the enclosures your system actually contains now. This example system contains groups 01 through 04, each with three I/O enclosures, and group 05 with two I/O enclosures. Shade in those enclosures to see the space left in your topology, and the possible block structures that fit.
Example of Choosing a Block Structure Planning System Expansion Example Step 4: Choose the Block Structure The previous step shows that each existing processor enclosure can support two more I/O enclosures. You also can add three processor enclosures for groups 06, 07, and 08, each of which can support four I/O enclosures. In this example, you will add two processor enclosures and five I/O enclosures. You must now decide how to build those enclosures into blocks.
Example of Choosing a Block Structure Planning System Expansion Example Step 5: Add Blocks to Worksheets On your copy of Worksheet 5, confirm that your system will accept the block structures you have planned. Highlight the spaces in which you intend to install the blocks. Worksheet 5 Added Blocks — Tetra 16 Topology, X Fabric Shade in the enclosures, ports, and slot numbers that are in use in your current configuration. You can now see the available locations and group numbers for added enclosures.
Enclosures From Another System Planning System Expansion Because you have decided to add these blocks in the places shown, the blocks will be assigned the following group numbers when you attach the blocks to your system: Block Structure Group Numbers One I/O enclosure 14 One I/O enclosure 24 One I/O enclosure 34 One processor enclosure attached to one I/O enclosure 06, 61 One processor enclosure attached to one I/O enclosure 07, 71 Enclosures From Another System To expand a system online when
3 Planning System Reduction This section defines the concept of a donor system and describes how to plan the orderly removal of enclosures.
Considerations Planning System Reduction Considerations Before you remove any enclosures, answer the following questions about the donor system: Topic Page Are Both ServerNet Fabrics Up? 3-2 Can an Enclosure Be Removed Easily? 3-2 Remove All Enclosures at Once or One at a Time? 3-3 Is the Enclosure Providing Critical Resources? 3-4 Is the Enclosure an IOAM Enclosure? 3-5 Are Both ServerNet Fabrics Up? For online reduction to succeed, both ServerNet fabrics in the system must be fully operation
Planning System Reduction Remove All Enclosures at Once or One at a Time? Remove All Enclosures at Once or One at a Time? The two methods of removing enclosures each have advantages and disadvantages. If you are removing only one enclosure, there is no difference in these methods. Removing All Enclosures At Once Procedure 1. Route all applications and processes away from all enclosures to be removed. 2. Delete all the enclosures from the system configuration at once. 3.
Is the Enclosure Providing Critical Resources? Planning System Reduction Is the Enclosure Providing Critical Resources? Information about critical resources is system-specific. Therefore, consult your system analyst and service provider to determine the actions most appropriate for your system.
Planning System Reduction • Is the Enclosure an IOAM Enclosure? Processes and communication paths not started that might need a device For more information, see Determining Communication Paths on page 3-6. Is the Enclosure an IOAM Enclosure? If you are planning to remove an OAM enclosure from your system, the enclosure must be removed by a service provider trained by HP. See Expansion With IOAM Enclosures on page 1-2.
Determining Communication Paths Planning System Reduction Determining Communication Paths You must determine the direct and indirect communication paths within your donor system so that you know which enclosures to prepare for online reduction. To trace the ServerNet connections among enclosures, see Worksheets 9, 10, and 11 in Appendix C.
Example Using the ServerNet Worksheets Planning System Reduction 1. Choose and Copy the Appropriate Worksheets If the system topology is … Copy these worksheets from Appendix C Tetra 8 ServerNet Worksheet 9 Tetra 16 ServerNet Worksheets 10 and 11 This figure shows Worksheets 10 and 11 for a Tetra 16 system. Worksheet 11 ServerNet Communication Pathways: Tetra 16 Topology, Y Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration.
Planning System Reduction Example Using the ServerNet Worksheets 2. Highlight Your Present System Configuration Using a highlighter on a copy of Worksheet 9 or Worksheets 10 and 11, shade in all the ports, slots, and enclosures your current system contains.
Example Using the ServerNet Worksheets Planning System Reduction Configured portions of the system are shaded, while unconfigured portions of the system are white: Worksheet 10 ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Example Using the ServerNet Worksheets Planning System Reduction 3. Black Out the Enclosures to Be Removed With a marker, darken the enclosures you want to remove. This example worksheet shows a Tetra 16 system in which group 02 will be removed: Worksheet 10 ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove.
Planning System Reduction Example Using the ServerNet Worksheets 4. Trace Communication Paths to Each Enclosure Removing an enclosure removes communication paths within your system. In this step, you determine what communication paths will be removed from your system: 1. Starting from the central “X” in the tetrahedral topology for the system, trace all ServerNet cables to the ServerNet expansion boards (SEBs) or modular SEBs (MSEBs) in the processor enclosures. 2.
Example Using the ServerNet Worksheets Planning System Reduction Worksheet 10 ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Example Using the ServerNet Worksheets Planning System Reduction 5. Circle the Affected Enclosures After you have traced all possible communication paths, you can see the enclosures that will be affected by enclosure removal. Circle those enclosures. You must prepare to remove these parts of your system. Caution. If your tracing of communication paths is incomplete or incorrect, the procedure you follow in Section 4, Reducing a System Online, might remove more enclosures than you intended.
Example Using the ServerNet Worksheets Planning System Reduction Worksheet 10 ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Planning System Reduction Example Using the ServerNet Worksheets 6. List Affected Enclosures in Reverse Numerical Order The following example worksheet shows that you list the enclosures you must prepare for removal.
Example Using the ServerNet Worksheets Planning System Reduction Physically remove the enclosures from your system in this order. For more information, see Order of Removal on page 3-17. Worksheet 10 ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Planning System Reduction Order of Removal Order of Removal After you have prepared your system, power off and remove enclosures starting with the largest enclosure number. Proceed in decreasing numerical order by enclosure number, and end with the smallest enclosure number. For example, if you remove group 02, you affect the associated I/O enclosure groups 21, 22, 23, 24, and 25. You also affect group 06 and its associated I/O enclosure groups 61, 62, 63, 64, 65, and 66.
Planning System Reduction HP NonStop S-Series System Expansion and Reduction Guide—522465-009 3- 18 The Next Step
4 Reducing a System Online This section describes the procedure for removing enclosures from a system online, either to reduce a system or to expand a target system. Note. You must perform each step as documented, in the order shown. You should also read and understand the discussions and concepts in Section 3, Planning System Reduction, before reducing a system online. Step Page 1. Prepare the Donor System for Reduction 4-2 2. Record Information About the Donor System 4-4 3.
Reducing a System Online 1. Prepare the Donor System for Reduction 1. Prepare the Donor System for Reduction 1.1 Prepare Worksheets 1. From Appendix C, make copies of Worksheet 1 and Worksheets 2.1 through 2.8 (referred to hereafter as Worksheets 2.n). If the system contains any IOAM enclosures, also make copies of Worksheet 2.1a. 2. Circle the words Donor System at the top of each worksheet. 3. Make one copy of Worksheet 8 in Appendix C for each enclosure you will remove.
1.3 Save the Current Donor System Configuration Reducing a System Online TSM Software If you are reducing your system online, you must be running both the G06.04 or later RVU and a compatible version of the TSM package. If you are running an earlier RVU than G06.04, you must reduce the system offline, as described in Section 5, Reducing a System Offline. Step Action Use This Procedure Record Information Here 1. Record the current OSM or TSM version.
2. Record Information About the Donor System Reducing a System Online 2. Record Information About the Donor System Before you physically remove enclosures from your donor system, you must record information about those enclosures on the worksheets in Appendix C. You determine this information by using a system console. 2.1 Record Basic Information Continue filling out worksheets for the donor system, as follows: Step Action Result 1. On the OSM or TSM Low-Level Link tool bar, click System Discovery.
Reducing a System Online 2.2 Determine IP Addresses and Firmware Versions 2.2 Determine IP Addresses and Firmware Versions Perform this step twice for each enclosure you are removing from the donor system: • • • Once for the PMF CRU or IOMF CRU in slot 50 Once for the PMF CRU or IOMF CRU in slot 55 For an IOAM enclosure, once for each ServerNet Switch Board Step Action Result 1. In the tree pane, located on the left side of the window, expand the icon for the system.
Reducing a System Online 2.3 Label Enclosures 2.3 Label Enclosures You must identify each enclosure you plan to remove before you remove it from the donor system. Use copies of the completed worksheets as labels: 1. Make a copy of the Worksheets from 2.1 through 2.8 that you filled out for the donor system packet. If IOAM enclosures are involved, make a copy of Worksheet 2.1a. 2. To each enclosure you are removing from the donor system, tape a copy of the worksheet that describes that enclosure. 3.
Reducing a System Online 4. Inventory Enclosures to Be Removed 4. Inventory Enclosures to Be Removed Before you remove enclosures from your system, inventory each enclosure to identify its devices, communication paths, and subsystems. Record this information on Worksheet 8: Step Action Result 1. In the tree pane in the OSM Service Connection or TSM Service Application, expand the icon of the highest-numbered enclosure you will remove. The tree pane displays the devices in the enclosure. 2.
5. Prepare and Stop Devices and Processes Reducing a System Online 5. Prepare and Stop Devices and Processes Because you must maintain access to the system after you have stopped or moved all devices, processes, and their communication paths, the TACL process you use for the following steps should run in group 01. For this reason, use the startup TACL process for system reduction. Step Action 1.
6. Ensure Devices and Processes Are Stopped Reducing a System Online 6. Ensure Devices and Processes Are Stopped Step Action Result 1. In the tree pane of the OSM Service Connection or TSM Service Application, expand the enclosure and the module of the enclosure that contains the stopped devices, including internal disks. The tree pane displays the devices in the enclosure. 2. Make sure all icons are fully expanded. The tree pane displays all devices in the enclosure. 3.
Reducing a System Online 7.2 Ensure That Devices Are Deleted 7.2 Ensure That Devices Are Deleted From the OSM Service Connection or TSM Service Application, confirm that all devices have been deleted from the enclosure: • • In the tree pane, all deleted internal disks should be listed as Unknown Disk CRU. The Attributes tab should show other devices as Not Configured.
Reducing a System Online 8. Prepare Enclosures for Removal 8. Prepare Enclosures for Removal 8.1 Disable Batteries in the Enclosure This procedure prepares an enclosure for power off by disabling its battery packs. Step Action 1. In the tree pane of OSM or TSM, expand the group and module of the enclosure you want to remove so you can see the batteries. 2. Right click the battery in slot 23 and select Actions. 3. In OSM Select Enable/Disable. In TSM select Disable Battery. Click Perform Action. 4.
Reducing a System Online 8.3 Disable ServerNet Ports in Y-fabric MSEBs (or SEBs) 8.3 Disable ServerNet Ports in Y-fabric MSEBs (or SEBs) This procedure disables the Y-fabric ServerNet ports in processor enclosures that are connected to the enclosure you are removing. Note. Consult the topology diagrams in the planning worksheets to determine which ServerNet ports need to be disabled.
8.4 Remove Cables from Disabled ServerNet Ports on Y-fabric Reducing a System Online Table 4-2. Router Port Connections to MSEBs Router Port Connects to MSEB 0 Cable connector 6 1 Cable connector 5 2 Cable connector 4 3 Cable connector 3 4 Cable connector 2 5 Cable connector 1 8.4 Remove Cables from Disabled ServerNet Ports on Y-fabric Looking at an enclosure you are removing, you can see where all the ServerNet cables attach. Therefore, removing that end of the ServerNet cables is simple.
8.5 Power Off Enclosure Reducing a System Online 8.5 Power Off Enclosure Ensure that all processors in the enclosures to be removed have been prepared and halted, if applicable, before powering off the enclosures: Step Action Result 1. From the OSM Service Connection or TSM Service Application, select the Display menu. Right-click the enclosure you want to power off. A dialog box appears. 2. Select Actions. A dialog box appears. 3. Select Power Off. 4. Select Perform Action. 5.
Reducing a System Online 8.6 Disable ServerNet Ports in X-fabric MSEBS 8.6 Disable ServerNet Ports in X-fabric MSEBS This procedure disables the X-fabric ServerNet ports in processor enclosures that are connected to the enclosure you are removing. Note. Consult the topology diagrams in the planning worksheets to determine which ServerNet ports need to be disabled.
8.7 Remove Cables from Disabled ServerNet Ports on X-fabric Reducing a System Online Table 4-4. Router Port Connections to MSEBs Router Port Connects to MSEB 0 Cable connector 6 1 Cable connector 5 2 Cable connector 4 3 Cable connector 3 4 Cable connector 2 5 Cable connector 1 8.7 Remove Cables from Disabled ServerNet Ports on X-fabric Looking at an enclosure you are removing, you can see where all the ServerNet cables attach. Therefore, removing that end of the ServerNet cables is simple.
Reducing a System Online 8.8 Reenable Disabled ServerNet Ports on both fabrics Step Action 1. In the tree pane of OSM or TSM, navigate to the processor enclosure to which the removed enclosure was connected. Expand the group and module so you can see the MSEBs (or SEBs). 2. Right click the Y-fabric MSEB and select Actions. 3. Select Enable ServerNet (Router) Port and click Perform Action. 4. Follow the screen prompts to disable the appropriate ServerNet port. 5.
Reducing a System Online 8.9 Verify Enclosures Are Removed From System Configuration 8.9 Verify Enclosures Are Removed From System Configuration The icons of the enclosures disappear from the display in the OSM Service Connection or TSM Service Application, but you need to confirm that the enclosures have been removed from the system configuration: Step Action Result 1. Log off of the OSM or TSM LowLevel Link Application and then log back on.
Reducing a System Online 9. Finish the Reduction 9. Finish the Reduction 9.1 Save New Donor System Configuration Now that you have altered the donor system’s configuration, save its current configuration. 1. At a TACL prompt, start SCF and enter the SAVE CONFIGURATION command: >SCF -> SAVE CONFIGURATION xx.yy where xx.yy is a configuration number in the range 00.00 through 99.99 that is both: • • Not already in use Not the configuration number you used in Step 1.
10. Remove Other Cables From Powered-Off Enclosures Reducing a System Online 10. Remove Other Cables From Powered-Off Enclosures You must remove the remaining cables between the donor system and the powered-off enclosures. For Information About See The other cables you need to remove Cabling on page 1-8 Procedures for removing cables NonStop S-Series Hardware Installation and FastPath Guide Cables for an IOAM enclosure Modular I/O Installation and Configuration Guide 11.
5 Reducing a System Offline This section describes the procedure for removing enclosures offline. Reducing a system offline is removing enclosures from a donor system after you have shut down the entire system. You can do this on any RVU. For systems running an RVU earlier than G06.04, this is the only way to reduce a system. The procedure for reducing your system offline is: Step As Described In Page 1. 1. Prepare the Donor System for Reduction 4-2 2.
Reducing a System Offline HP NonStop S-Series System Expansion and Reduction Guide—522465-009 5 -2
6 Expanding a System Online This section describes the procedure for adding enclosures online to expand a system. You must perform each step as documented in the order shown. If you do not, system expansion could fail with unpredictable results. Step Page On the Target System: 1. Prepare Target System for Expansion 6-4 2. Record Information About Target System 6-6 3. Prepare Target System for Addition of Block 6-9 4. Save Current Target System Configuration 6-10 5.
Expanding a System Online Preparation for Online Expansion Preparation for Online Expansion Preparation for online expansion depends on where you get the enclosures with which you will be expanding your system. If the enclosures come from another system: Step For more information 1. Ensure that the system you are expanding contains an adequate number of MSEBs and MSEB PICs. Does Your System Have Enough MSEBs and MSEB PICs? on page 1-3 2. Plan the procedure of removing enclosures from another system.
Expanding a System Online Preparation for Online Expansion Cautions. • • You can expand your system only if it already contains an adequate number of MSEBs and MSEB PICs to support the increased number of processors after expansion. You can expand your system online only if it is running G06.00 or later with a compatible TSM package or G06.08 or later with a compatible OSM or TSM package. For information about the OSM package and other requirements for migrating to OSM, see the OSM Migration Guide.
1. Prepare Target System for Expansion Expanding a System Online 1. Prepare Target System for Expansion This procedure assumes that both ServerNet fabrics in your system are fully operational. If any ServerNet alarms have been generated, you must eliminate those problems before you expand your system online. Adding blocks must not conflict with the operations of your system. Therefore, you must prepare both the blocks you are adding and the target system you are expanding. For... See...
1. Prepare Target System for Expansion Expanding a System Online Table 6-2. Preparatory Steps Step Action Reason 1. If necessary, upgrade the OSM or TSM client software to a compatible version on all system consoles used in the resizing process. For online resizing to succeed, every system console involved must run identical versions of the OSM or TSM package. To determine which product versions of the OSM package are compatible with your system, see the OSM Migration Guide.
2. Record Information About Target System Expanding a System Online 2. Record Information About Target System Before you physically add enclosures to your target system, you must record information about the target system on worksheets in Appendix C. You determine this information with a system console.
Expanding a System Online 2.3 Record Information About Other Processors 2.3 Record Information About Other Processors Perform this step twice for each enclosure in the target system: • • • Once for the PMF CRU or IOMF CRU in slot 50 Once for the PMF CRU or IOMF CRU in slot 55 For an IOAM enclosure, once for each ServerNet Switch Board Step Action Result 1. In the tree pane, located on the left side of the window, expand the icon for the system. The tree pane displays all the enclosures. 2.
2.4 Record Service Connection IP Addresses Expanding a System Online 2.4 Record Service Connection IP Addresses Perform this step once for each enclosure in the target system. Step Action Result 1. In the OSM or TSM Low-Level Link window, select File. A menu appears. 2. Select Edit System List …. The Edit Systems List dialog box appears, containing the name of the target system. (You might have to scroll down to find it.) 3. Highlight the name of the target system. 4. Click Modify.
3. Prepare Target System for Addition of Block Expanding a System Online 3. Prepare Target System for Addition of Block On the target system, start a TACL session and log on as a super-group user. 3.1 Record Current SYSnn Subvolume 1. At the TACL prompt: > STATUS *, TERM, PROG 2. Record the SYSnn subvolume on Worksheet 1. 3.2 Check Storage Automatic Configuration and Autostart It is recommended that you start an SCF log file to track all configuration changes made during the system expansion. 1.
Expanding a System Online 4. Save Current Target System Configuration 4. Save Current Target System Configuration Before you alter your target system’s configuration, save its current configuration for fallback purposes: 1. At the SCF prompt, enter the SAVE CONFIGURATION command: -> SAVE CONFIGURATION xx.yy where xx.yy is a configuration number in the range 00.00 through 99.99 that is not already in use. If you specify a number that is already in use, you receive this message: Configuration file $SYSTEM.
Expanding a System Online 5. Copy SP Firmware File From the Target System to the System Console 5. Copy SP Firmware File From the Target System to the System Console In this step, you shift your activities from the target system to the block you will add. If you have a system console to move from the target system to that block, this step indicates when to move the system console.
5.2 Identify IP Address for FTP Session Expanding a System Online A display such as the following can take a few moments to appear: ->INFO SUBNET $*.* TCPIP Info SUBNET \TROLL.$ZTC00.* Name Devicename #LOOP0 #SN1 \NOSYS.$NOIOP \TROLL.LAN670A *IPADDRESS 127.0.0.1 172.17.116.175 TYPE *SUBNETMASK SuName LOOP-BACK %HFF000000 ETHERNET %HFFFFFF00 QIO *R OFF N ON N TCPIP Info SUBNET \TROLL.$ZTC20.* Name Devicename #LOOP0 #SN1 \NOSYS.$NOIOP \TROLL.LAN020A *IPADDRESS 127.0.0.1 172.17.116.
Expanding a System Online 5.3 Copy SP Firmware File From Target System 5.3 Copy SP Firmware File From Target System On the system console attached to the target system: 1. Select Start > Programs > Command Prompt 2. Create a directory for the SP firmware file on the target system console: C:\>md \spcode9 3. Switch to that directory: C:\>cd \spcode9 4. Start an FTP session a. Start > Programs > Command Prompt b. Enter ftp and the IP address obtained from Step 5.
6. Finish Gathering Information Expanding a System Online 6. Finish Gathering Information At this stage, you treat and configure each enclosure separately. Before you configure an enclosure into a block, you must supply its IP information. IP information for an enclosure is recorded on different worksheets, depending on whether the enclosure came directly from the factory or from a donor system. Note.
Expanding a System Online 7. Connect a System Console to the Enclosure 7. Connect a System Console to the Enclosure Caution. Before you perform this step, ensure that: • • The enclosure is powered off. The system console that you will connect to the enclosure is running a version of the OSM or TSM client software that is compatible with your RVU and TSM server software.
8. Change Group Number of Enclosure to 01 Expanding a System Online 8. Change Group Number of Enclosure to 01 Before you configure an enclosure into a block, you must temporarily change the enclosure’s group number to 01. Note. To change the group number of IOAM enclosures, your service provider uses the Configure Module action in the OSM Low-Level Link Application. Change I/O enclosure numbers with the group ID switches. These switches are shown in Figure 6-2.
Expanding a System Online 9. Power On Enclosure 9. Power On Enclosure Power on this enclosure by plugging the AC power cords for the enclosure into the AC power source. Caution. After an enclosure has been plugged into an AC power source once, unplugging and then replugging its AC power cord powers on the enclosure prematurely. Therefore, do not unplug and replug any AC power cords.
10. Verify Connection Between System Console and Enclosure Expanding a System Online 10. Verify Connection Between System Console and Enclosure In this step, you check whether the system console and enclosure you have connected are communicating. 10.1 Verify Connection to ServerNet X Fabric Open a Command Prompt window on the system console and enter the following command using the low-level link IP address of group 01, slot 50, from Worksheet 2.
11. Configure System Console and Enclosure Expanding a System Online 11. Configure System Console and Enclosure This step ensures that the system console attached to this enclosure contains the correct software and that this enclosure contains the correct IP addresses. 11.1 Check and Upgrade OSM and TSM Client Software If Necessary You must check to see whether the system console attached to this enclosure is running the appropriate OSM or TSM client software.
12. Verify SP Firmware Is Compatible Expanding a System Online 12. Verify SP Firmware Is Compatible This step checks whether the SP firmware on the enclosure is compatible with the SP firmware on the target system. Note. This step does not apply to IOAM enclosures. 12.1 Determine SP Firmware Version for Enclosure How you perform this step depends on where you got the enclosure: • If this enclosure was shipped directly from the factory: Step Action Result 1.
Expanding a System Online 13. Update SP Firmware in Enclosure If Necessary 13. Update SP Firmware in Enclosure If Necessary Note. For IOAM enclosures, your service provider must verify that the ME firmware and the ME FPGA is the latest version. Updating the ME firmware and ME FPGA is described in the Modular I/O Installation and Configuration Guide. You might be able to skip this step: If SP Firmware Versions Are … Then … Identical on the enclosure to be added and the target system Skip this step.
Expanding a System Online 14. Configure Topology of Enclosure If Necessary Step Action Result (page 2 of 2) 13. Click Refresh after approximately one minute. If the correct version of the SP firmware is displayed in the Service Processor (SPs) list, the update is successful. 14. Click Close. 15. When the update and reset finish successfully, repeat this procedure, starting with Step 2, for the SP in slot 55 of this enclosure. 14.
15. Power Off Enclosure Expanding a System Online This possibility of recabling and reconfiguring means that you must pay careful attention to Worksheets 3 and 4 for the Tetra 8 topology or Worksheets 5 and 6 for the Tetra 16 topology. 15. Power Off Enclosure You must power off the enclosure before connecting it to the target system. Step Action Result 1. From the OSM or TSM Low-Level Link, select the Display menu. A menu appears. 2. Select Actions. A menu appears. 3. Select Power Off. 4.
17. Assemble Enclosures Into a Block Expanding a System Online Step Page (page 2 of 2) 13. Update SP Firmware in Enclosure If Necessary 6-21 14. Configure Topology of Enclosure If Necessary 6-22 15. Power Off Enclosure 6-23 17. Assemble Enclosures Into a Block Skip this step if you are creating a block that contains only one enclosure: If You Are Creating … Then … A block consisting of only one enclosure Skip this step and go to Step 18.
17.1 Cable Enclosures Together Expanding a System Online Figure 6-3.
17.2 Verify ServerNet Cabling Expanding a System Online 4. Connect the system console to the block. You performed these procedures for each of the enclosures you have prepared. Now you perform these procedures for the entire block. Step Page 7. Connect a System Console to the Enclosure 6-15 9. Power On Enclosure 6-17 Start the OSM or TSM Low-Level Link A-9 10. Verify Connection Between System Console and Enclosure 6-18 17.
Expanding a System Online 18. Change Group Numbers of Block to Fit Target System 18. Change Group Numbers of Block to Fit Target System In Step 8. Change Group Number of Enclosure to 01 on page 6-16, you temporarily changed the group numbers of each enclosure in the block to configure them. Now that you are adding the block to the target system, you must change those temporary group numbers to working group numbers appropriate for the target system: 1.
20. Power On Added Block Expanding a System Online Figure 6-4. Disconnecting Ethernet Cable VST114.vsd 20. Power On Added Block On each PMF CRU or IOMF CRU in the added block, press and hold the power-on button for two seconds before releasing it. The location of the power-on button is shown in Figure 6-5 on page 6-29. Pressing the power-on button on one PMF CRU or IOMF CRU causes the other PMF CRU or IOMF CRU in the same enclosure to power on as well.
21. Cable Block to Target System Expanding a System Online After applying power to the enclosures, if the LEDs on a PMF CRU or IOMF CRU remain unlit, see CRU Does Not Start on page 7-6. Figure 6-5. PMF/IOMF CRU Power On Button Status LEDs System Enclosure (Service Side) POWER ON Power-On Button VST108.vsd 21. Cable Block to Target System Cautions. After the AC power cord on the target system or any enclosure in the block is connected to an AC power source, do not unplug and replug it.
Expanding a System Online 21.2 Connect ServerNet Cables Between Block and Target System 21.2 Connect ServerNet Cables Between Block and Target System Caution. When you attach the block to the target system, you must attach all ServerNet cables correctly the first time. All ServerNet cabling connections appear in Appendix B, ServerNet Cabling, and on Worksheets 3, 4, 5, and 6 in Appendix C. You might have to recable the block from the configuration you gave it in Step 17.
22. Verify Resized Target System Expanding a System Online 22. Verify Resized Target System In this step, you run two validation checks on the resized target system. 22.1 Verify That Added Enclosures Appear in System Configuration If the system console attached to the target system is running the OSM or TSM LowLevel Link: Step Action Result 1. Log off of the OSM or TSM Low-Level Link. These actions synchronize the OSM or TSM Low-Level Link with the resized system. 2. Log back on. 3.
Expanding a System Online 22.2 Check Configuration of All CRUs 22.2 Check Configuration of All CRUs In this step, check whether the CRUs in the target system were configured correctly and whether they passed their power-on self-tests (POSTs). 1. Start a TACL session and log on as a super-group user. 2. Start SCF and enter this command: ->STATUS ADAPTER $ZZSTO.* The command returns listings for all storage adapters in the target system. The following example shows what a partial display might look like.
Expanding a System Online 23a. Update Firmware and Code in Block (Using TSM) 23a. Update Firmware and Code in Block (Using TSM) Do this step even if you performed 13. Update SP Firmware in Enclosure If Necessary. For each PMF CRU or IOMF CRU in each enclosure you added, check (and update if necessary) the SP firmware, processor boot code, and SCSI boot code: Step Action Result 1. In the TSM Service Application, select Display. A menu appears. 2. Select Single SP Firmware Update.
Expanding a System Online Step 23a. Update Firmware and Code in Block (Using TSM) Action Result b. Click Perform action. The Update Action Summary dialog box appears. c. When the Status line lists the action as Completed, click Close. The Update Action Summary dialog box disappears. 6. Examine the State Box for the SP Firmware. • • Skip to Step 15 if both of the following conditions are true: • • The state box is OK You performed 13. Update SP Firmware in Enclosure If Necessary.
Expanding a System Online 23b. Update Firmware and Code in Block (Using OSM) 23b. Update Firmware and Code in Block (Using OSM) Do this step even if you performed 13. Update SP Firmware in Enclosure If Necessary. Note. For IOAM enclosures, your service provider must verify that the ME firmware and the ME FPGA is the latest version. Updating the ME firmware and ME FPGA is described in the Modular I/O Installation and Configuration Guide.
Expanding a System Online Step 23b. Update Firmware and Code in Block (Using OSM) Action Result 1. Launch and log on to the OSM Low-Level Link. 2. Click Processor Status. 3. Click to select the processor you want to update. 4. From the Processor Actions list, select Hard Reset and then click Perform action. 5. When the status line lists the action as Completed, click Close. The Processor Status dialog box appears.
24. Reload Processors in Block If Necessary Expanding a System Online 24. Reload Processors in Block If Necessary Skip this step if the added block does not contain a processor enclosure. If the Added Block Contains … Then … One I/O enclosure and no processor enclosures Skip this step. Go to 25. Verify Operations in Added Block on page 6-38. A processor enclosure, with or without I/O enclosures Perform this step. Note.
25. Verify Operations in Added Block Expanding a System Online 25. Verify Operations in Added Block This step ensures that all enclosures in the added block are operating normally: Step Action Result 1. Log on to the OSM Service Connection or TSM Service Application. The Management window appears. 2. In the tree pane, click the appropriate icons to view each enclosure in the added block. All added enclosures and their components should be displayed.
7 Troubleshooting This section gives troubleshooting information to solve problems encountered during system expansion or reduction. Note. For problems with components in an IOAM enclosure, your service provider should see the Modular I/O Installation and Configuration Guide.
Troubleshooting Symptoms and Problems Symptoms and Problems AC Power Cord Was Unplugged or Replugged Cause You unplugged the enclosure’s AC power cords from the power source and then plugged them back in. This might have occurred during Step 9. Power On Enclosure on page 6-17 or Step 20. Power On Added Block on page 6-28. Recovery 1. Unplug the AC power cords of the affected block or enclosure. 2. Unplug the battery packs from the power monitor and control unit (PMCU) in the affected block or enclosure.
Troubleshooting Added Enclosure Does Not Power On Added Enclosure Does Not Power On Not all enclosures in the added block powered on after you pressed the power-on button, possibly from Step 9. Power On Enclosure on page 6-17. Cause and Recovery Cause Recovery AC power cords are unplugged. See AC Power Cord Was Unplugged or Replugged on page 7-2. Power-on cables are disconnected. Figure 7-1 shows the location of the power-on cables.
Troubleshooting Added Enclosure Is Not Recognized by the Target System Added Enclosure Is Not Recognized by the Target System The OSM or TSM applications on the target system do not show the enclosure you just added. This problem might occur during Step 22.1 Verify That Added Enclosures Appear in System Configuration on page 6-31. Cause and Recovery Cause Recovery Topology problem. 1. Unplug the AC power cords of the affected block or enclosure. 2.
Troubleshooting Amber LEDs Remain Lit Amber LEDs Remain Lit Green LEDs should remain lit on powered-on enclosures. However, if an amber LED remains lit, see POST Fails on page 7-9. Neither CRU Starts See Added Enclosure Is Not Recognized by the Target System on page 7-4. Cannot See Enclosure in OSM or TSM See Added Enclosure Is Not Recognized by the Target System on page 7-4. Configuration File Already Exists When you are updating the system configuration database during one of these steps: • • • 9.
Troubleshooting CRU Does Not Start CRU Does Not Start In Step 9. Power On Enclosure on page 6-17, when you press the power-on button on one PMF CRU or IOMF CRU, the other PMF CRU or IOMF CRU in the same enclosure does not power on. Cause The PMF CRUs or IOMF CRUs in a single enclosure might not be seated correctly. Recovery 1. Unseat the affected CRU and wait one minute. 2. Reseat the CRU and reattach the AC power cord within 25 seconds. The CRU performs a POST.
Troubleshooting Ping Command Does Not Work Ping Command Does Not Work The ping command on the system console (entered during Step 10. Verify Connection Between System Console and Enclosure on page 6-18) returns the message “Destination host unreachable” or “Request timed out.” Cause You cannot connect to the block or enclosure you are configuring because: • • • There is a disconnect somewhere in the Ethernet cables.
Troubleshooting Ping Command Does Not Work 4. If these values differ, change the IP address of the system console: a. b. c. d. e. f. g. h. Click Start > Settings > Control Panel. Double-click the Network icon. Click the Protocols tab. Select TCP/IP Protocol. Click Properties. In the dialog box, click the IP Address tab. If necessary, click Specify an IP address. Change the IP Address, Subnet Mask, and Default Gateway fields: • • • i. j.
Troubleshooting POST Fails POST Fails The power-on self-test (POST) fails for one or more PMF CRUs or IOMF CRUs. This situation might occur when you perform these steps: • • • 9. Power On Enclosure on page 6-17 20. Power On Added Block on page 6-28 22.2 Check Configuration of All CRUs on page 6-32. Note. When POST fails before the added block is connected to the target system, the LEDs are available but not the event messages.
Troubleshooting RELOAD Command Does Not Work RELOAD Command Does Not Work Not all processors in the system come up in response to a TACL RELOAD command, as might happen during Step Skip this step if the added block does not contain a processor enclosure. on page 6-37. Cause The ServerNet X fabric might be down. Recovery 1. Enter this command and check for any status other than UP. > SCF STATUS SERVERNET $ZSNET 2. Start any down fabrics: > SCF START SERVERNET $ZSNET.X.* > SCF START SERVERNET $ZSNET.Y.
Troubleshooting ServerNet Fabrics Are Down Recovery 1. 2. 3. 4. 5. Disconnect ServerNet cables between the target system and the affected block. Unplug the AC power cords of the affected block. Unplug the battery packs in the affected block. Replug battery packs in the affected block. Begin the resizing process again at 20. Power On Added Block on page 6-28. ServerNet Fabrics Are Down One or more ServerNet fabrics might be down.
Troubleshooting Code 316 Returned During Logon Code 316 Returned During Logon While trying to log on to the OSM or TSM Low-Level Link during Step 12.1 Determine SP Firmware Version for Enclosure on page 6-20, you get a code 316 error message on the status bar at the bottom of the OSM or TSM window.
Troubleshooting Storage Automatic Configuration Does Not Work Storage Automatic Configuration Does Not Work The AUTOCONFIG option of the SCF ALTER command does not automatically configure all internal disk drives in an enclosure. An AUTOCONFIG command failure has three possible causes, each with its own recovery procedure. Note. If AUTOCONFIG fails for any reason, you must configure all disk drives in the enclosure manually with the SCF ADD DISK command.
Troubleshooting Topology Does Not Appear Topology Does Not Appear The OSM or TSM Low-Level Link is unable to report the topology value. You might get this result during Step 2.1 Record Basic Information on page 4-4 or Step 2.2 Record Information About the Master Service Processor on page 6-6. Cause The topology value continues to display as Retrieving Data. Recovery While still in the OSM or TSM Low-Level Link, from the Display menu, select Refresh.
Troubleshooting Service Processor Subsystem Event Messages Service Processor Subsystem Event Messages The symbolic name of each of these events begins with ZSPR-EVT: Event Number Name (ZSPR-EVT) Description 110 -CRU-INSERTION-OK CRU insertion passed preliminary self tests. 111 -CRU-INSERTION-FAILED CRU insertion failed preliminary self tests. 112 -CRU-REMOVED CRU was removed. 501 -CRU-SNETCFG-STARTED ServerNet configuration started for unit.
Troubleshooting Storage Subsystem Event Messages Storage Subsystem Event Messages The symbolic name of each of these events begins with ZSTO-EVT: Event Number Name (ZSTO-EVT) Description (page 1 of 2) 1026 -ADAPTER-AUTO-FAILED Autoconfiguration of an adapter failed. This event is usually preceded by storage subsystem event 1025 (failed to access $ZCNF). 1027 -ADAPTER-AUTO-RETRY Waiting for a resource that is blocking autoconfiguration of an adapter.
Troubleshooting Storage Subsystem Event Messages Event Number Name (ZSTO-EVT) Description (page 2 of 2) 1045 -CRU-CONFIG-FAILED Autoconfiguration of CRU failed. This event contains information describing the reason for failure. 1046 -CRU-ACCESS-ERROR Storage subsystem manager process did not obtain information for CRU. 1047 -CRU-RECONFIG CRU configuration has been changed. 1048 -CONFIG-DEFERRED CRU configuration deferred.
Troubleshooting Storage Subsystem Event Messages HP NonStop S-Series System Expansion and Reduction Guide—522465-009 7- 18
A Common System Operations This appendix describes how to perform common operations involved in resizing your system.
Determine the Processor Type Common System Operations Determine the Processor Type You can use either the OSM or TSM Low-Level Link or the OSM Service Connection or TSM Service Application to determine the processor type of the NonStop S-series server that you are logged on to. The software does not display the server model number, but you can use the Part Number or Processor Name attributes to infer the server model number. Determine the Processor Type Using the OSM or TSM Low-Level Link Step 1.
Common System Operations Determine the Processor Type Using the OSM Service Connection or TSM Service Application Determine the Processor Type Using the OSM Service Connection or TSM Service Application Step 1. Action • • Result In OSM, select Start> Programs>HP OSM>OSM Service Connection. In TSM, select Start> Programs>Compaq TSM>TSM Service Application. 2. Log on to the OSM Service Connection or TSM Service Application. 3. From the tree pane: a. Double-click the group number for the enclosure.
Determine the ServerNet Fabric Status Common System Operations Determine the ServerNet Fabric Status You use the OSM Service Connection, TSM Service Application, or SCF to determine the status of ServerNet fabrics. Check the ServerNet Fabric Status Using the OSM Service Connection or TSM Service Application This procedure is supported by OSM and TSM version 2000A or later and can be used on both processor enclosures and I/O enclosures. Step Action Result 1.
Common System Operations Check ServerNet Fabric Status Using SCF (Processor Enclosures Only) Check ServerNet Fabric Status Using SCF (Processor Enclosures Only) The following example shows how to use the SCF STATUS SERVERNET $ZSNET command to check the ServerNet communications among processors and provide an example of the display that might result. This command shows whether two processors can communicate over a specific fabric.
Check ServerNet Fabric Status Using SCF (Processor Enclosures Only) Common System Operations $SYSTEM STARTUP 1> scf SCF - T9082G02 - (16OCT98) (25SEP98) - 02/22/1999 13:37:32 System \ALPHA5 Copyright Tandem Computers Incorporated 1986 - 1998 (Invoking \ALPHA5.$SYSTEM.STARTUP.
Common System Operations Determine the Product Versions of the OSM Client Software Determine the Product Versions of the OSM Client Software To determine the version of the OSM Low-Level Link: Step Action Result 1. Select Start>Programs>HP OSM and start OSM Low-Level Link. The OSM Low-Level Link logon dialog box appears. 2. Either log on or close the logon dialog box. 3. From the Help menu, Select About HP OSM. The product version of the OSM Low-Level Link appears. 4. Click Close.
Move the System Console Common System Operations Move the System Console Step Action 1. Power off the system console. 2. Use Step 19.2 Disconnect System Console on page 6-27 to disconnect the system console’s Ethernet cables from the enclosure, block, or system you have stopped working with. 3. Physically move the system console to its new location. Both the system console that you will connect to the enclosure and the enclosure itself must be offline (and therefore isolated).
Start a Startup TACL Session Common System Operations Start a Startup TACL Session Only one startup TACL session can be running at one time on a system. If another user on your system is already using the startup TACL connection, you receive a message that a duplicate session cannot be established. The startup TACL session is usually started on the system console. Step Action Result 1. From the OSM or TSM Low-Level Link menu bar, select File. A menu appears. 2. Select Start Terminal Emulator.
Common System Operations Start the OSM Service Connection or TSM Service Application HP NonStop S-Series System Expansion and Reduction Guide—522465-009 A -10
B ServerNet Cabling This appendix shows diagrams of all ServerNet cable connections. It also includes examples of how you can map these diagrams to actual NonStop S-series enclosures.
Example: Correlation Between Cabling Diagram and One Enclosure with SEBs PMF CRU SEB slot 51 slot 50 SEB slot 52 SEB slot 53 SEB slot 54 PMF CRU slot 55 5 PM Grou 4 PMF F p0 5 Group 6 SEB 50 SEB 0 2 5 1 51 SE 02 1 SEB 2 B 5 53 3 3 6 5 4 3 2 1 Connector 6 Connector 5 Connector 4 Connector 3 Connector 2 Connector 1 NonStopTM processor enclosure with power shelf, service side Table B-1.
Example: Correlation Between Cabling Diagram and One Enclosure with MSEBS PMF CRU SEB slot 51 slot 50 SEB slot 52 SEB slot 53 SEB slot 54 5 Grou PM 4 PMF p0 F 5 Group 6 SEB 50 SEB 2 0 5 1 51 02 SE 1 SEB 2 B 5 53 3 3 6 5 4 3 2 1 PMF CRU slot 55 Connector 6 Connector 5 Connector 4 Connector 3 Connector 2 Connector 1 NonStopTM processor enclosure with power shelf, service side Table B-2.
Example: Correlation Between Cabling Diagram and Two Enclosures 5 4 6 1 2 3 SEB 51 6 5 PMF 50 Group 02 SEB 53 4 3 2 1 50 SEB 53 Connector 5 Group 25 IOMF IOMF CRU slot 50 NonStopTM processor enclosure with power shelf, service side ServerNet cable NonStopTM I/O enclosure without power shelf, service side VST112.
NonStop S-Series System — Tetra 8 Topology, X Fabric Group 01 Group 04 PMF 50 PMF 50 Group 11 IOMF Group 12 IOMF Group 22 IOMF Group 21 IOMF 50 50 50 50 5 4 SEB 6 51 1 2 3 5 4 6 SEB 1 51 2 3 3 2 SEB 1 51 6 4 5 3 2 1 SEB 6 51 4 5 50 Group 41 IOMF 50 Group 42 IOMF 50 Group 32 IOMF PMF 50 PMF 50 Group 02 Group 03 50 Group 31 IOMF VST303.
NonStop S-Series System — Tetra 8 Topology, Y Fabric Group 01 Group 04 PMF 55 PMF 55 Group 11 IOMF Group 12 IOMF Group 22 IOMF Group 21 IOMF 55 55 55 55 5 4 SEB 6 52 1 2 3 5 4 6 SEB 1 52 2 3 3 2 SEB 1 52 6 4 5 3 2 1 SEB 6 52 4 5 55 Group 41 IOMF 55 Group 42 IOMF 55 Group 32 IOMF PMF 55 PMF 55 Group 02 Group 03 55 Group 31 IOMF VST304.
NonStop S-Series System — Tetra 16 Topology, X Fabric Group Group Group 53 51 52 IOMF IOMF IOMF Group 54 IOMF Group Group 64 63 IOMF IOMF Group 62 IOMF Group 61 IOMF 50 50 50 50 50 1 PMF 50 2 Group 3 SEB 05 4 51 5 SEB 53 6 1 2 3 4 5 6 50 50 6 5 Group SEB 4 01 51 1 2 SEB 53 3 1 2 3 4 5 6 PMF 50 Group 55 IOMF 50 Group 56 50 IOMF 50 1 PMF 50 2 Group 3 SEB 06 4 51 5 SEB 53 6 6 5 4 3 2 1 6 PMF 50 5 Group 4 SEB 02 1 51 2 SEB 53 3 6 5 4 3 2 1 50 Group 65 IOMF 50 Group 66 IOMF Group 57 IOMF 5
NonStop S-Series System — Tetra 16 Topology, Y Fabric Group 51 IOMF Group Group 52 53 IOMF IOMF 55 55 1 2 Group SEB 3 05 52 4 5 SEB 54 6 1 2 3 4 5 6 55 Group 54 IOMF Group 64 IOMF 55 55 Group Group 62 63 IOMF IOMF 55 55 Group 61 IOMF 55 1 PMF 55 2 Group 3 SEB 06 4 52 5 SEB 54 6 6 5 4 3 2 1 PMF 55 6 5 SEB 4 1 52 2 SEB 54 3 1 2 3 4 5 6 PMF 55 Group 55 55 IOMF Group 01 Group 56 55 IOMF 6 PMF 55 5 Group 4 SEB 02 1 52 2 SEB 54 3 6 5 4 3 2 1 55 Group 65 IOMF 55 Group 66 IOMF Group 57 55 IOMF
C Checklists and Worksheets This appendix contains checklists and worksheets for planning system resizing. Note. These worksheets show the maximum number of I/O enclosures. Your service provider can tell you the number of I/O enclosures supported by the RVU on your system. Note. The diagrams in this guide identify all ServerNet expansion boards as SEBs. Your system might have or require modular ServerNet expansion boards (MSEBs) in the slots designated for SEBs. SEBs and MSEBs are functionally equivalent.
Sheet Title Purpose Worksheet 9 ServerNet Worksheet: Tetra 8 Topology, X and Y Fabrics Trace paths of ServerNet communication among enclosures Worksheet 10 ServerNet Worksheet: Tetra 16 Topology, X Fabric Worksheet 11 ServerNet Worksheet: Tetra 16 Topology, Y Fabric
Checklist: Tools and Supplies TM Short Phillips screwdriver NonStop S-series system console Small slotted screwdriver NonStop S-series System Console Installer CD-ROM 3/16” hex socket driver Three (3) Ethernet cables 3/4” or 9/16” open-end wrench One or more TM NonStop S-series system enclosures Antistatic mat Ethernet hub Safety glasses SEBs, MSEBs, adapters, and other components you will need for your resized system TM Scissors or cutter Tape Flashlight Pointed object such as a straighten
Checklist: Preliminary Procedures Ensure that all system consoles you will use to resize your system are running the appropriate version of OSM or TSM client software. If you are expanding your system, install enough MSEBs to accommodate the number of enclosures the system will contain after expansion. Copy all worksheets and staple them together. 1 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.
(circle one)Target System / Donor System Worksheet 1 OSM, TSM, System, and Firmware Information OSM Product Version See the OSM User's Guide and the NonStop System Console Installer Guide for instructions on how to obtain this information. TSM Product Version on the System Consoles If your system consoles are not running the correct TSM client software for your RVU, upgrade the consoles with the appropriate NonStop System Console Installer CD-ROM.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System For IOAM Enclosures Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
(circle one)Target System / Donor System Worksheet 2.
Worksheet 3 Added Blocks: Tetra 8 Topology, X Fabric Shade in the enclosures, ports, and slot numbers that are in use in your current configuration. You can now see the available locations and group numbers for added enclosures. With a highlighter or a pen of a different color, circle where you will add the enclosures.
Worksheet 4 Added Blocks: Tetra 8 Topology, Y Fabric Shade in the enclosures, ports, and slot numbers that are in use in your current configuration. You can now see the available locations and group numbers for added enclosures. With a highlighter or a pen of a different color, circle where you will add the enclosures.
Worksheet 5 Added Blocks: Tetra 16 Topology, X Fabric Shade in the enclosures, ports, and slot numbers that are in use in your current configuration. You can now see the available locations and group numbers for added enclosures. With a highlighter or a pen of a different color, circle where you will add the enclosures.
Worksheet 6 Added Blocks: Tetra 16 Topology, Y Fabric Shade in the enclosures, ports, and slot numbers that are in use in your current configuration. You can now see the available locations and group numbers for added enclosures. With a highlighter or a pen of a different color, circle where you will add the enclosures.
Worksheet 7 Block to Be Added If your block contains more enclosures than you can record on this sheet, copy this sheet and continue recording on that copy. Fill in the “1 of ____ pages” blank to the right. 1 of ___ pages If you are adding a block made of enclosures from another system, do not use this sheet. Copy Worksheets 2.1 through 2.8 and circle “Donor System” at the top instead.
Worksheet 8 Reduction: Hardware Inventory, Group #__________ Device Type Device Name Slot Device Type Device Name Slot (circle one) DISK _______________________ 1 DISK _______________________ 2 DISK _______________________ 3 DISK _______________________ 4 DISK _______________________ 5 DISK _______________________ 6 DISK _______________________ 7 DISK _______________________ 8 DISK _______________________ 11 TAPE DRIVE _______________________ 50 DISK _______________________ 12
Worksheet 8a Reduction: Hardware Inventory, IOAM Enclosure, Group #__________ Module 2 Device Type Device Name Module 3 Slot ServerNet _______________________ 14 Switch Board Device Type Device Name Slot G4SA _______________________ 1 Device Type Device Name Slot G4SA _______________________ 2 Device Type Device Name Slot G4SA _______________________ 3 Device Type Device Name Slot G4SA _______________________ 4 Device Type Device Name Slot (circle one) FCSA Device Type Device Nam
ServerNet Worksheet: Tetra 8 Topology, X and Y Fabrics Worksheet 9 With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the enclosure you plan to remove.
Worksheet 10 ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box. Then, on the worksheet for the Y fabric, black out the PMF CRU in slot 55 in the corresponding enclosure to indicate that this PMF CRU will lose access to the X fabric as well.
Worksheet 11 ServerNet Communication Pathways: Tetra 16 Topology, Y Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box. Then, on the worksheet for the X fabric, black out the PMF CRU in slot 50 in the corresponding enclosure to indicate that this PMF CRU will lose access to the Y fabric as well.
D Stopping Devices and Processes This appendix gives examples of identifying devices and processes before you move or stop them. As stated in Step 5. Prepare and Stop Devices and Processes on page 4-8, you need to identify all devices and processes before you can stop or move them. This important step in system reduction must be done successfully if the donor system is to continue to function well after the enclosures have been physically removed.
Prepare and Stop Internal Disk Drives Stopping Devices and Processes Table D-1. References and Examples (page 2 of 2) Example on Page Device Subsystem Manual ServerNet/FX adapter FOX ServerNet/FX Adapter Configuration and Management Manual -- 6760 ServerNet device adapter Storage 6760 ServerNet/DA Manual -- ServerNet wide-area network concentrator (SWAN) WAN WAN Subsystem Configuration and Management Manual -- Prepare and Stop Internal Disk Drives In Step 4.
Stop Internal Disk Drives Stopping Devices and Processes The following procedure identifies the active processes that are currently using an internal disk. This procedure might not generate a complete list of dependent processes. Step Action Result 1. At the TACL prompt, enter this command for each disk volume listed on Worksheet 8: You receive a list of processes that currently have files open on the specified disk. > FUP LISTOPENS diskname.*.
Stop Internal Disk Drives Stopping Devices and Processes 3. Verify that the disk drives have been stopped by entering this SCF command for each PMF CRU or IOMF CRU in each enclosure to be removed: -> STATUS ADAPTER $ZZSTO.#device.group.module.slot, DETAIL For example, for the IOMF CRU in slot 55 of I/O enclosure group 71: -> STATUS ADAPTER $ZZSTO.#IOMF.GRP-71.MOD-1.SLOT-55, DETAIL For the PMF CRU in slot 50 of processor enclosure group 07: -> STATUS ADAPTER $ZZSTO.#PMF.GRP-7.MOD-1.
Stopping Devices and Processes Delete Internal Disk Drives STARTED. Do not proceed with system reduction until all devices in the enclosure you are removing are listed as STOPPED. Repeat this procedure to stop internal disk drives for each internal disk drive in each enclosure to be removed.
Prepare and Stop an E4SA Stopping Devices and Processes Prepare and Stop an E4SA The next examples show how to stop an Ethernet 4 ServerNet adapter (E4SA). These examples: • • • • Use SCF unless otherwise noted Show part of the removal of group 02 from system \TROLL Show an E4SA that was configured to use only Expand-over-IP. Are only examples and might not be appropriate for your system Note.
Prepare and Stop an E4SA Stopping Devices and Processes This example screen shows all open associations of the TCP/IP $ZTC20 process to other processes. For example, $ZTN20, the Telserv process, appears in boldface. -> LISTOPENS PROCESS $ZTC20 TCPIP Listopens PROCESS \TROLL.
Stop the E4SA Adapter Stopping Devices and Processes This example screen shows the TACL commands you can use to trace processes started from a TCP/IP session. The processes highlighted in bold type might be affected by the removal of this E4SA. TACL> STATUS *, TERM $ZTN20.#PTCZA3G Process Pri PFR %WT Userid Program file $Z02F 7,20 169 005 255,255 SYSTEM.SYS00.TACL Hometerm $ZTN20.#PTCZA3G Process Pri PFR %WT $Z02F 6,45 168 P 000 Hometerm $ZTN20.#PTCZA3Y Userid 255,255 Program file SYSTEM.SYS00.
Stopping Devices and Processes Delete the E4SA Adapter Delete the E4SA Adapter You can use these SCF commands to delete the #E4SA20A adapter along with its associated LIFs, PIFs, and SACs from the system configuration. 5-> 6-> 7-> 8-> 9-> DELETE LIF $ZZLAN.LAN020A DELETE LIF $ZZLAN.LAN020B DELETE LIF $ZZLAN.LAN021A DELETE LIF $ZZLAN.LAN021B DELETE ADAPTER $ZZLAN.
Stopping Devices and Processes Delete the E4SA Adapter HP NonStop S-Series System Expansion and Reduction Guide—522465-009 D-10
Safety and Compliance Regulatory Compliance Statements The following warning and regulatory compliance statements apply to the products documented by this manual. FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Safety and Compliance Regulatory Compliance Statements Korea MIC Compliance Taiwan (BSMI) Compliance Japan (VCCI) Compliance This is a Class A product based on the standard or the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case the user may be required to take corrective actions.
Safety and Compliance Regulatory Compliance Statements DECLARATION OF CONFORMITY Supplier Name: HP COMPUTER CORPORATION Supplier Address: HP Computer Corporation, NonStop Enterprise Division 10333 Vallco Parkway Cupertino, CA 95014 USA Represented in the EU By: Hewlett Packard EMEA GmbH P.O.
Safety and Compliance Consumer Safety Statements Consumer Safety Statements Customer Installation and Servicing of Equipment The following statements pertain to safety issues regarding customer installation and servicing of equipment described in this manual. • • Keep door closed for normal operation. Batteries must be disposed of in compliance with local ordinances. Caution.
Safety and Compliance Consignes de sécurité à l'intention du client Consignes de sécurité à l'intention du client Installation et entretien du système par le client Les consignes de sécurité qui suivent concernent l'installation et l'entretien par le client du système décrit dans le présent manuel. • • Garder la porte fermée pendant le fonctionnement normal du système. Jeter les piles usagées conformément au règlement local en vigueur. Attention.
Safety and Compliance Verbraucher-Sicherheitsangaben Verbraucher-Sicherheitsangaben Geräteinstallation und -wartung durch den Kunden Die folgenden Angaben betreffen Sicherheitsfragen in Hinsicht auf die Geräteinstallation und -wartung durch den Kunden, wie sie in diesem Handbuch beschrieben werden. • • Tür für normalen Betrieb geschlossen lassen. Batterien müssen in Übereinstimmung mit örtlichen Vorschriften beseitigt werden. Vorsicht.
Safety and Compliance Declaraciones sobre la seguridad del consumidor Declaraciones sobre la seguridad del consumidor Instalación y servicio al equipo por el consumidor Las siguientes declaraciones tienen que ver con aspectos de seguridad relacionados con la instalación y servicio al equipo por el consumidor, y que se describen en este manual. • • Mantenga la puerta cerrada durante la operación normal del equipo. Las baterías (pilas) deben desecharse cumpliendo con los reglamentos locales. Precaución.
Safety and Compliance Forbrugersikkerhedsmeddelelser Forbrugersikkerhedsmeddelelser Installation og service af udstyr der udføres af kunden De følgende meddelelser vedrører sikkerheden angående installation og service af udstyr, der udføres af kunden, som beskrives i denne brugerhåndbog. • • Hold lugen lukket under normal drift. Batterierne skal kasseres i overensstemmelse med lokale vedtægter.
Safety and Compliance Veiligheidsinstructies voor de consument Veiligheidsinstructies voor de consument Installatie en onderhoud van apparatuur door de klant De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de klant van de in deze handleiding beschreven apparatuur. • • Houd bij normaal bedrijf de deur gesloten. Batterijen moeten overeenkomstig de plaatselijke voorschriften worden weggegooid. Opgelet.
Safety and Compliance Käyttöturvaa koskevia huomautuksia Käyttöturvaa koskevia huomautuksia Asiakkaan suorittama laiteasennus ja huolto Seuraavat huomautukset koskevat turvallisuusnäkökohtia, jotka asiakkaan täytyy ottaa huomioon tässä käsikirjassa kuvattuja laiteasennuksia ja huoltotoimenpiteitä suoritettaessa. • • Kansi täytyy pitää suljettuna normaalin käytön aikana. Paristot täytyy hävittää paikallisten säädösten mukaisesti. Varoitus.
Safety and Compliance Veiligheidsinstructies voor de consument Veiligheidsinstructies voor de consument Installatie en onderhoud van apparatuur door de klant De volgende veiligheidsinstructies betreffen de installatie en het onderhoud door de klant van de in deze handleiding beschreven apparatuur. • • Houd bij normaal bedrijf de deur gesloten. Batterijen moeten overeenkomstig de plaatselijke voorschriften worden weggegooid. Opgelet.
Safety and Compliance Misure precauzionali per i clienti Misure precauzionali per i clienti Installazione e manutenzione del sistema da parte del cliente Le seguenti misure precauzionali riguardano l’installazione e la manutenzione da parte del cliente del sistema descritto nel presente manuale. • • Mantenere la porta chiusa durante il funzionamento normale del sistema. Lo smaltimento delle batterie usate deve essere effettuato secondo la normativa locale. Avvertenza.
Safety and Compliance Informações de segurança para os consumidores Informações de segurança para os consumidores Instalação e manutenção do equipamento pelo cliente As seguintes informações se referem a questões de segurança relacionadas à instalação e manutenção, pelo cliente, do equipamento descrito neste manual. • • Para garantir o funcionamento normal, mantenha a porta fechada. As pilhas usadas devem ser descartadas de acordo com as leis locais. Cuidado.
Safety and Compliance Informações de segurança para os consumidores Informações de segurança para os consumidores Instalação e manutenção do equipamento pelo cliente As seguintes informações referem-se a questões de segurança relacionadas à instalação e manutenção, pelo cliente, do equipamento descrito neste manual. • • Para garantir o funcionamento normal, mantenha a porta fechada. As pilhas usadas devem ser descartadas de acordo com as leis locais. Cuidado.
Safety and Compliance Meddelanden beträffande konsumentsäkerhet Meddelanden beträffande konsumentsäkerhet Kundutförd installation och service De följande meddelandena beskriver säkerhetsföreskrifter för kundutförd installation och service av utrustning som beskrivs i denna manual: • • Dörren skall vara stängd under normal drift. Batterier måste kasseras i enlighet med lokala förordningar.
Safety and Compliance Kundutförd installation och service S7400/ S7600/ Sxx000 HP NonStop S-Series System Expansion and Reduction Guide—522465-009 Statements-16
Safety and Compliance Kundutförd installation och service S7400/ S7600/ Sxx000 HP NonStop S-Series System Expansion and Reduction Guide—522465-009 Statements-17
Safety and Compliance Kundutförd installation och service S7400/ S7600/ Sxx000 HP NonStop S-Series System Expansion and Reduction Guide—522465-009 Statements-18
Glossary 3-phase. Describes a single power source with three output phases (A, B, and C). The phase difference between any two of the three phases or currents is 120 degrees. 3860 ATM 3 ServerNet adapter (ATM3SA). See ATM 3 ServerNet adapter (ATM3SA). 3861 Ethernet 4 ServerNet adapter (E4SA). See Ethernet 4 ServerNet adapter (E4SA). 3862 Token-Ring ServerNet adapter (TRSA). See Token-Ring ServerNet adapter (TRSA). 3863 Fast Ethernet ServerNet adapter (FESA). See Fast Ethernet ServerNet adapter (FESA).
Glossary absolute pathname absolute pathname. An Open System Services (OSS) pathname that begins with a slash (/) character and is resolved beginning with the root directory. Contrast with relative pathname. AC. See alternating current (AC). accelerated mode. The operational environment in which Accelerator-generated RISC instructions execute. See also TNS mode and TNS/R native mode. accelerated object code. The RISC instructions that result from processing a TNS object file with the Accelerator program.
Glossary ADAPTER object type types of cable that can connect any of the six 50-pin WAN ports to one of the supported electrical interfaces (RS-232, RS-449, X.21, or V.35). ADAPTER object type. The Subsystem Control Facility (SCF) object type for all adapters attached to your system. address space. The memory locations to which a process has access. ADE. See application development environment (ADE). adjacent SP.
Glossary application binary interface (ABI) The appearance side is opposite the service side. System enclosures are typically arranged so that the appearance side is the most visible side. See also service side. application binary interface (ABI). The conventions used to call functions and access global or external data. application development environment (ADE). A set of methods and tools that are used throughout the lifecycle of an application project to design, code, and manage that project.
Glossary ASSIGN ASSIGN. An HP Tandem Advanced Command Language (TACL) command you can use to associate a file name with a logical file of a program or to assign a physical device to logical entities that an application uses. assign message. Within Subsystem Control Facility (SCF), a message created by SCF for each ASSIGN command. A new process must request its assign message following receipt of the startup message.
Glossary authentication attributes authentication attributes. Security attributes of a process that do not change unless a successful reauthentication occurs or the super ID changes them. For Open System Services (OSS) processes, the authentication attributes include the login name, real user ID, real group ID, authentication system (node name), and group list. authorization attributes.
Glossary backout backout. The Distributed Systems Management/Software Configuration Manager (DSM/SCM) action of making the last configuration applied to the target system inaccessible and replacing it with the previous configuration. backplane. A board that has connectors, on one or both sides of the board, into which circuit board assemblies plug. Backplanes are located behind card cages. BACKUP. A utility for the HP NonStop™ servers that creates a backup copy of one or more disk files on magnetic tape.
Glossary block block. A grouping of one or more system enclosures that an HP NonStop™ S-series system recognizes and supports as one unit. A block can consist of either one processor enclosure, one I/O enclosure, or one processor enclosure with one or more I/O enclosures attached. blocked signal. A programmatic signal that is currently in the pending signal mask of a process and, when generated, is not delivered to the process because of the signal mask setting. Some signals cannot be blocked.
Glossary branch circuit branch circuit. The circuit conductors located between the equipment receptacles and the final overcurrent device in a power distribution panel (PDP) that protect the circuits. branded product. A software product that is licensed by X/Open to carry the X/Open or UNIX trademark. branding process. The activities that lead to the acceptance of a product by X/Open in accordance with its Trade Mark Licence Agreement. break condition.
Glossary cache (cache memory) support. The cable support also contains the group and module ID labels and the rear group service light-emitting diode (LED). cache (cache memory). A small, fast memory holding recently accessed data designed to speed up subsequent access to the same data. Cache memory is built from faster memory chips than main memory, and it is most often used with process or main memory but also used in network data transfer to maintain a local copy of data. cached bindings.
Glossary CE CE. Customer engineer. See service provider. cell. See storage pool. central processing unit (CPU). Historically, the main data processing unit of a computer. The HP NonStop™ servers have multiple cooperating processors rather than a single CPU. See also processor. Challenge Handshake Authentication Protocol (CHAP). An Internet-standard protocol for verifying encrypted passwords. CHAP is a security protocol that is implemented using Point-to-Point Protocol (PPP).
Glossary CIIN CIIN. A command file in the SYSnn subvolume that is read and executed by the startup HP Tandem Advanced Command Language (TACL) process after system load if the CIIN file is specified in the CONFTEXT file and enabled in the OSM or TSM Low-Level Link. circuit breaker. A device designed to open and close a circuit by nonautomatic means and to open the circuit automatically on a predetermined overcurrent without damage to itself. CISC. See complex instruction-set computing (CISC).
Glossary CLIP CLIP. See communications line interface processor (CLIP). cluster. (1) A collection of servers, or nodes, that can function either independently or collectively as a processing unit. See also ServerNet cluster. (2) A term used to describe a system in a Fiber Optic Extension (FOX) ring. More specifically, a FOX cluster is a collection of processors and I/O devices functioning as a logical group. In FOX nomenclature, the term is synonymous with system or node. cluster number.
Glossary CMI CMI. See Communications Management Interface (CMI). code segment. A segment that contains executable instructions of a program or library to be executed plus related information. Code segments can be executed and also accessed as read-only data but not written to by an application program. These readonly and execute-only segments are efficiently shared among simultaneous executions of that program or library. Therefore, they are read from disk but are never written back to disk.
Glossary communications line communications line. A two-way link consisting of processing equipment, I/O devices, protocol conventions, and cables that connect a computer to other computers. communications line interface processor (CLIP). The major programmable device within the ServerNet wide area network (SWAN) concentrator, providing link-level protocol and a software interface to the host. The CLIP stores and implements specific communications protocols. Communications Management Interface (CMI).
Glossary Compaq TSM Service Application Compaq TSM Service Application. A component of the Compaq TSM client software. The TSM Service Application enables you to communicate with an HP NonStop™ S-series server when the HP NonStop Kernel operating system is running. When the operating system is not running, communication must take place using the TSM Low-Level Link. See also Compaq TSM Low-Level Link. compiler extended-data segment.
Glossary CONFIG file CONFIG file. In G-series release version updates (RVUs), the current system configuration database file, which is stored on the $SYSTEM. ZSYSCONF subvolume. See also configuration file. configuration. (1) The arrangement of enclosures, system components, and peripheral devices into a working unit. (2) The definition or alteration of characteristics of an object. configuration file.
Glossary conformance document conformance document. An implementor’s document that must accompany software claiming conformance with a POSIX standard. The document specifies the behavior or other aspect of the software when the standard describes a behavior or aspect as implementation-defined. conformance statement questionnaire (CSQ). A document that identifies how a product implements X/Open Specifications as defined in XPG Component/Profile Definitions. A CSQ exists for each branded product.
Glossary connectivity representation of the connectivity among components within an enclosure. See also Physical view. connectivity. The ability of a system to transfer information between itself and a system from another vendor. Other vendors use the term connectivity to mean hardware compatibility. See also interoperability. connector. See port. console message. See operator message. contiguous ground.
Glossary core file core file. See saveabend file. correctable memory error (CME). An error caused by incorrect data at a particular memory location. The cause of the error is such that the error is automatically corrected by the system. Contrast with uncorrectable memory error (UCME). COUP. See Configuration Utility Program (COUP). CPU. See central processing unit (CPU). cpu, pin.
Glossary customer-installable system customer-installable system. A system that does not require specially trained service providers to install. customer-replaceable unit (CRU). A unit that can be replaced in the field either by customers or by qualified personnel trained by HP.
Glossary dBm dBm. Decibels as referenced to a milliwatt. A unit of measure that establishes 0 dBm equal to 1 milliwatt. A negative value represents a decrease in power, and a positive value represents an increase in power. See also decibel (dB). DC. See direct current (DC). DCE. See data communications equipment (DCE). DCF. See dynamic configuration file (DCF). DCT. See destination control table (DCT). DC power cable.
Glossary destination ServerNet ID (DID) destination ServerNet ID (DID). A field in the ServerNet packet header indicating the intended destination for the packet. detailed report. A complete listing of status or configuration information provided by the Subsystem Control Facility (SCF) STATUS or INFO command when you use the DETAIL option. Contrast with summary report. device. A computer peripheral or an object that appears to an application as such. See also terminal. DHCP.
Glossary directory tree directory tree. A hierarchy of directories. In the Open System Services (OSS) environment, directories are connected to each other in a branching hierarchical fashion such that only one path exists between any two directories (if no backtracking occurs). disconnecting means. A device, group of devices, or other means by which the conductors of a circuit can be disconnected from their source of supply. discovery.
Glossary DLC DLC. See data link control (DLC). DNS. See Domain Name System (DNS). DNS server. A server that resolves hostnames to Internet protocol (IP) address mapping queries. These queries originate from either client computers, which are known as resolvers, or other Domain Name System (DNS) servers, which accounts for the distributed nature of DNS. See also Network Information Service (NIS). domain. (1) In the Internet, a part of the naming hierarchy.
Glossary downward compatibility downward compatibility. The ability of a requester to operate with a server of an earlier revision level. In this case, the requester is downward-compatible with the server, and the server is upward-compatible with the requester. Contrast with upward compatibility. drive. See disk drive or tape drive. dropout. A voltage loss of very short duration (that is, milliseconds). DSC. See Dynamic System Configuration (DSC). DSM. See Distributed Systems Management (DSM). DSM/SCM.
Glossary dynamic-link library (DLL) gathered from a server through the process of discovery. Contrast with static information. dynamic-link library (DLL). A collection of procedures whose code and data can be loaded and executed at any virtual memory address, with run-time resolution of links to and from the main program and other independent libraries. The same DLL can be used by more than one process. Each process gets its own copy of DLL static data. Contrast with shared run-time library (SRL).
Glossary effective group ID effective group ID. An attribute of an Open System Services (OSS) process that is used to determine permissions such as the file access allowed for the process. The effective group ID of a process is a group ID that contributes to the group access privileges of that process. The effective group ID of a process might be used to set the group ID of files created by that process. The effective group ID can be changed while the process runs. effective user ID.
Glossary EMI removes power from all computer equipment in the room. The EPO connectors prevent the batteries from powering the server after power is removed. EPO capabilities are required in the United States when a server is installed in a computer room designed to comply with the special construction and fire protection provisions of the United States’ national electrical code (or at other sites as required by local regulations.) EMI. See electromagnetic interference (EMI). emitter-coupled logic (ECL).
Glossary endian endian. Denotes the significance of byte 0 in a multibyte structure such as a word. NonStop servers are big-endian, where the most significant bit is contained in byte 0. Intel systems and HP AlphaServer OpenVMS and HP AlphaServer Tru64 UNIX systems are little-endian, where the least significant bit is contained in byte 0. environmental parameters. Subsystem Control Facility (SCF) session parameters set by default or by using various SCF commands.
Glossary Ethernet Ethernet. A local area network (LAN) that uses the carrier sense multiple access with collision detection (CSMA/CD) access method on a bus topology and is the basis for the IEEE 802.3 standard. Ethernet 4 ServerNet adapter (E4SA). A ServerNet adapter for Ethernet local area networks (LANs) that contains four Ethernet ports. Ethernet hub. A multiport repeater typically supporting 10Base-T cabling. Most hubs are connectors for 8 or 12 cables. Also referred to as a concentrator.
Glossary Expand-over-ServerNet line-handler process device number as its Expand-over-ServerNet line-handler process. However, the line does not have the same states as the line-handler process. Expand-over-ServerNet line-handler process. An Expand line-handler process that uses the NETNAM protocol to access the Network Access Method (NAM) interface provided by the ServerNet cluster monitor process, $ZZSCL. The Expand-over-ServerNet linehandler process handles incoming and outgoing Expand messages.
Glossary external routing external routing. The routing of packets over the external ServerNet fabrics; that is, between systems (or nodes) in a ServerNet cluster. See also internal routing. external ServerNet fabrics. The fabrics that link systems in a ServerNet cluster. See also internal ServerNet fabrics. external ServerNet X or Y fabric. The X or Y fabric that links systems in a ServerNet cluster. See also internal ServerNet X or Y fabric. external system area network manager process (SANMAN).
Glossary FCSA FCSA. See Fibre Channel ServerNet adapter (FCSA). FC switch. See Fibre Channel switch (FC switch). FDC. See flexible disk configuration (FDC). feature-test macro. In C and C++ programs, a symbol that, if defined in a program’s source code, includes specific other symbols from a header within that program’s source code and makes those symbols visible. feeder circuit.
Glossary field field. In a structured programming language, an addressable entry within a data structure. The term field is sometimes used to mean member. field-programmable gate array (FPGA). A programmable integrated circuit that can be customized to perform specific functions. field-replaceable unit (FRU). A unit that can be replaced in the field only by qualified personnel trained by HP and cannot be replaced by customers.
Glossary file mode file mode. For an Open System Services (OSS) process, a field in the stat structure for a specific file that describes the type and characteristics of the file and contains the access permission bits for the file. file mode creation mask. A mask associated with an Open System Services (OSS) process and used when the process creates a file. Bits set in this mask are cleared in the access permission bits for the file. filename.
Glossary file system file system. In the Open System Services (OSS) environment, a collection of files and file attributes. A file system provides the namespace for the file serial numbers that uniquely identify its files. Open System Services provides a file system (see also ISO/IEC IS 9945-1:1990 [ANSI/IEEE Std. 1003.1-1990], Clause 2.2.2.38); the Guardian application program interface (API) provides a file system; and OSS Network File System (NFS) provides a file system.
Glossary FIRINIT FIRINIT. A diagnostic task used to update the communications line interface processor (CLIP) FRU information record (FIR) that is kept in the ServerNet wide area network (SWAN) concentrator CLIP flash memory. FIRMUP. A diagnostic task used to update the copy of the Portable Silicon Operating System (pSOS) system product embedded kernel that is kept in the ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP) flash memory. firmware.
Glossary four-lane link four-lane link. The four single-mode fiber-optic (SMF) ServerNet cables that connect the two HP NonStop™ Cluster Switches on the same external fabric (for example, X1 and X2) in a split-star topology. FOX. See Fiber Optic Extension (FOX). FOXMON. See FOX monitor process. FOX monitor process. The Fiber Optic Extension (FOX) monitor process for the ServerNet/FX adapter subsystem. The process name is $ZZFOX. FOX ring.
Glossary GB GB. See gigabyte (GB). GCSC. See Global Customer Support Center (GCSC). general-purpose register (GPR). One of a small number of undedicated high-speed memory locations in a processor. generic process. A process created and managed by the Kernel subsystem; also known as a system-managed process. A common characteristic of a generic process is persistence. GESA. See Gigabit Ethernet ServerNet adapter (GESA). G4SA. See Gigabit Ethernet 4-Port ServerNet adapter (G4SA).
Glossary globalized globalized. The import-control characteristic of a loadfile that allows it to import symbols from any loadfile in the loadList of the program with which it is loaded. When those loadfiles offer multiple definitions of the same symbol, those loadfiles are searched in loadList sequence and the first definition found takes precedence. See also searchList. globally unique ID (GUID).
Glossary group ID group ID. The nonnegative integer used to identify a group of users of an HP NonStop™ network node. Each user of a node is a member of at least one group. When the identity of a group is associated with an Open System Services (OSS) process, a group ID value is referred to as one of: • • • • Real group ID Effective group ID Supplementary group ID Saved-set group ID group list.
Glossary hard link server version T7945AAX (shipped with G06.13) or later, use the appropriate guided procedure. hard link. In the Open System Services (OSS) file system, the relationship between two directory entries for the same file. A hard link acts as an additional pointer to a file. A hard link cannot be used to point to a file in another fileset. Contrast with symbolic link. hard reset.
Glossary HP NonStop™ Cluster Switch (model 6770) HP NonStop™ Cluster Switch (model 6770). An assembly that routes ServerNet messages across an external fabric of a ServerNet cluster. The cluster switch consists of a ServerNet II Switch, an uninterruptible power supply (UPS), and AC transfer switch, and it can be packaged in a switch enclosure or in a 19-inch rack. The cluster switch is used with star, split-star, and tri-star topologies. See also HP NonStop™ ServerNet Switch (model 6780).
Glossary HP NonStop™ S7800 server HP NonStop™ S7800 server. A model of the HP NonStop S-series server that provides a midrange upgrade option from a NonStop S7600 server or earlier midrange NonStop S-series server. HP NonStop™ S70000 server. See HP NonStop™ Sxx000 server. HP NonStop™ S72000 server. See HP NonStop™ Sxx000 server. HP NonStop™ S74000 server. See HP NonStop™ Sxx000 server. HP NonStop™ S76000 server. See HP NonStop™ Sxx000 server. HP NonStop™ S86000 server. See HP NonStop™ Sxx000 server.
Glossary HP NonStop™ System RISC Model V processor (NSR-V processor) HP NonStop™ System RISC Model V processor (NSR-V processor). The model designation for the TNS/R processor used in the HP NonStop S74000 server. HP NonStop™ System RISC Model W processor (NSR-W processor). The model designation for the TNS/R processor used in the HP NonStop S7000 server. HP NonStop™ System RISC Model X processor (NSR-X processor). The model designation for the TNS/R processor used in the HP NonStop S76000 server.
Glossary HP Tandem Failure Data System (TFDS) tasks or provide a consistent user interface across independently programmed applications. HP Tandem Failure Data System (TFDS). A diagnostic tool that is a component of the HP NonStop™ Kernel operating system. The TFDS tool isolates software problems and provides automatic processor-failure data collection, diagnosis, and recovery services. HP Transaction Application Language (TAL).
Glossary impedance impedance. The total opposition (that is, resistance and reactance) a circuit provides to the flow of alternating current at a given frequency. implementation-defined. Not specified by a standard. A correct value or behavior that is implementation-defined can vary from system to system and therefore might represent a feature or facility that cannot be ported. implicit library.
Glossary incremental discovery incremental discovery. Discovery of an HP NonStop™ S-series server when the OSM or TSM client software has locally saved information but where configuration changes have been made on the server since that information was saved. indicator lights. Two light-emitting diodes (LEDs) on a customer-replaceable unit (CRU) that indicate the status of the unit. The red or amber indicator light is lit when the unit is not working properly.
Glossary INSPSNAP INSPSNAP. The program that provides a process snapshot file for the Inspect subsystem. installation subvolume (ISV). A subvolume containing files that perform a specific function during the installation process, such as organizing documentation in a specific location, providing the components of the HP NonStop™ Kernel operating system image (OSIMAGE), and containing files that are used after the installation process. installer.
Glossary Internet control message protocol (ICMP) physical network, an Internet address consists of a network portion and a host portion. See also IP address. Internet control message protocol (ICMP). A maintenance protocol in the Transmission Control Protocol/Internet Protocol (TCP/IP) suite that is required in every TCP/IP implementation. The ICMP allows two nodes on an IP network to share IP status and error information.
Glossary I/O controller I/O controller. The hardware logic that controls computer I/O operations for a particular set of devices, such as disks, tapes, terminals, or communications lines. See also ServerNet addressable controller (SAC). I/O enclosure. An HP NonStop™ S-series system enclosure containing one module, which includes ServerNet adapters, disk drives, components related to the ServerNet fabrics, and components related to electrical power and cooling for the enclosure.
Glossary IPC IPC. See interprocessor communications (IPC). IPU. See instruction processing unit (IPU). ISO. International Organization for Standardization. ISO is an international body that drafts, discusses, proposes, and specifies standards for network protocols. ISO is best known for its seven-layer reference model that describes the conceptual organization of protocols. ISO is sometimes called the International Standards Organization.
Glossary KB KB. See kilobyte (KB). Kernel subsystem. In G-series release version updates (RVUs), the subsystem for configuration and management of the Subsystem Control Facility (SCF) subsystem managers that are generic processes, some system attributes, and the ServerNet X and Y fabrics. Kernel subsystem manager process. The generic process that starts and manages other generic processes, some system attributes, and the ServerNet X and Y fabrics in G-series release version updates (RVUs).
Glossary • layer number The loader binds a symbol in a DLL to the first definition it finds on the program’s loadList, and this is not the first definition that was encountered on the linker searchList. For localized loadfiles, the linker and loader searchLists are the same, so late binding does not occur. layer number. See cluster switch layer number. layered topology. The network topology for ServerNet clusters using the HP NonStop™ ServerNet Switch (model 6780).
Glossary LIC system can also retain the bindings as modified when a loadfile is loaded and associate a LIC with those cached bindings, so that they can be reused when the same file is again loaded in an equivalent environment. (See cached bindings.) LIC. See library import characterization (LIC). LIF. See logical interface (LIF). light-emitting diode (LED). A semiconductor device that emits light from its surface. Indicator lights are composed of LEDs. See also indicator lights. line.
Glossary Linux Linux. Linus Torvald’s version of the UNIX operating system. See also http://www.linux.org. listener. The process or server that is notified by the message system that a message from some other process or server is being delivered. LIU. See line interface unit (LIU). LMU. See logical memory unit (LMU). load. (1) To transfer the HP NonStop™ Kernel operating system image or a program from disk into a computer’s memory so that the operating system or program can run.
Glossary localization localization. The process of adapting computer interfaces, data, and documentation to the culturally accepted way of presenting information in the culture. Sometimes referred to as L10N, derived from the 10 letters between the initial L and the final N of the word localization. localized.
Glossary logical segment MS8. An LMU must have memory units installed either in all of its slots or in none of its slots. See also memory unit. logical segment. A single data area consisting of one or more consecutive 128-kilobyte unitary segments that is dynamically allocated by a process. The two types of logical segments are selectable segments and flat segments. See also selectable segment and flat segment. logic board (LB). (1) See cluster switch logic board.
Glossary main service entrance (PMF) customer-replaceable unit (CRU) and is cleared when the system is powered off. main service entrance. The enclosure containing connection panels and switchgear, located at the point where the utility power lines enter the building. Maintenance Interface. See Archive and Database Maintenance Interface. maintenance switch. The Ethernet switch that links the maintenance entities in various modular components to the HP NonStop™ Open System Management (OSM) Interface.
Glossary memory-exact point memory-exact point. A potential breakpoint location within an accelerated object file at which the values in memory (but not necessarily the values in registers) are the same as they would be if the object file were running in TNS interpreted mode or on a TNS system. Most source statement boundaries are memory-exact points. Complex statements might contain several such points: at each function call, privileged instruction, and embedded assignment.
Glossary MMF PIC Each byte of data written to the primary drive is also written to the mirror drive. If the primary drive fails, the mirror drive can continue operations. See also volume. MMF PIC. See multimode fiber-optic (MMF) plug-in card (PIC). MMF ServerNet cable. See multimode fiber-optic (MMF) ServerNet cable. mode. The set of attributes that specify the type and access permissions for a file. See also file mode. modular cabinet.
Glossary multifunction I/O board (MFIOB) multifunction I/O board (MFIOB). A ServerNet adapter that contains ServerNet addressable controllers (SACs) for SCSI and Ethernet; a service processor; ServerNet links to the processor, to the two ServerNet adapter slots, and to one of the ServerNet expansion board (SEB) slots; and connections to the serial maintenance bus (SMB), which connects components within an enclosure to the service processor. multilane link.
Glossary native system library native system library. Synonym for implicit library. $NCP. The process name of the network control process. NEC. National Electrical Code. network. Two or more computer systems (nodes) connected so that they can exchange information and share resources. See also Expand network, wide area network (WAN), and local area network (LAN). Network Access Method (NAM).
Glossary node node. (1) A uniquely identified computer system connected to one or more other computer systems in a network. See also Expand node and ServerNet node. (2) An endpoint in a ServerNet fabric, such as a processor or ServerNet addressable controller (SAC). node number. A number used to identify a member system in a network. The node number is usually unique for each system in the network. See also node and ServerNet node number. node-numbering agent (NNA).
Glossary noninteractive mode noninteractive mode. A mode of operation that usually involves a command file (an EDIT file that contains a series of commands). Contrast with interactive mode. nonlinear load. Electrical load for which the instantaneous current is not proportional to the instantaneous voltage. Consequently, the local impedance varies with the voltage. nonsensitive command.
Glossary NSR-E processor NSR-E processor. See HP NonStop™ System RISC Model E processor (NSR-E processor). NSR-G processor. See HP NonStop™ System RISC Model G processor (NSR-G processor). NSR-T processor. See HP NonStop™ System RISC Model T processor (NSR-T processor). NSR-V processor. See HP NonStop™ System RISC Model V processor (NSR-V processor). NSR-W processor. See HP NonStop™ System RISC Model W processor (NSR-W processor). NSR-X processor.
Glossary object type object type. The category of Subsystem Control Facility (SCF) objects to which a specific SCF object belongs. For example, a specific disk has the object type DISK, and a specific terminal can have the object type SU. Each subsystem has a set of object types for the objects it manages. obsolescent. An indication that a feature or facility exists for compatibility with older versions or drafts of a standard.
Glossary open propagation open propagation. In the Open System Services (OSS) file system, the set of events and outcomes that occur when an open file description is inherited by a child process in the same processor as its parent process. Contrast with open migration. Open SCSI. A subsystem that provides the hardware and software for a SCSI-2 open interface that runs on HP NonStop™ S-series servers and to which developers can attach small computer system interface (SCSI) devices. open system.
Glossary operational environment operational environment. The conditions under which your system performs. These conditions include the devices and communications lines that are made active and the system and application processes that are started at system startup. operator. (1) A symbol, such as an arithmetic or conditional operator, that performs a specific operation on operands. (2) In Network Control Language (NCL), a lexical element used for working on terms in expressions.
Glossary OSIMAGE OSIMAGE. A file built during system generation that contains the complete image of the HP NonStop™ Kernel operating system that runs in each processor in the system. OSM. See HP NonStop™ Open System Management (OSM) Interface. OSM Event Viewer. OSM replacement for the TSM Event Viewer. OSM Low-Level Link. OSM replacement for the TSM Low-Level Link. OSM Notification Director. OSM replacement for the TSM Notification Director. OSM Service Connection.
Glossary packet packet. A block of information that contains fields for addressing, sequencing information, possible priority indicators, and a portion of a message or an entire message. See also ServerNet packet. page. See memory page. Parallel Library TCP/IP. An HP product that provides increased performance and scalability over conventional Transmission Control Protocol/Internet Protocol (TCP/IP).
Glossary path prefix path prefix. In the Open System Services (OSS) environment, a pathname with an optional final slash (/) character that refers to a directory. PDC. See phase-loss detector/contactor (PDC). PDP. See power distribution panel (PDP). PDU. See computer-room power center (CRPC) and power distribution unit (PDU). peak load current. The maximum instantaneous load over a designated interval of time. PEEK. A utility program that reports statistics on resource use in a processor.
Glossary persistence manager process persistence manager process. The $ZPM process that is started and managed by the $ZCNF configuration utility process and that starts generic processes in G-series release version updates (RVUs) and manages their persistence. persistent configuration. A configuration that remains the same from one system load to another. persistent process. A process that must always be either waiting, ready, or executing.
Glossary ping ping. A utility used to verify connections to one or more remote hosts. The ping utility uses the Internet control message protocol (ICMP) echo request and echo reply packets to determine whether a particular IP system on a network is functional. The ping utility is useful for diagnosing IP network or router failures. pipe.
Glossary POOL object type information over point-to-point links. OSM and TSM use PPP to provide TCP/IP communication over a dial-up connection. POOL object type. The Subsystem Control Facility (SCF) object type for storage pool storage pools. port. (1) A data channel that connects to other devices or computers. (2) A connector to which a cable can be attached.
Glossary POSIX POSIX. The Portable Operating System Interface, as defined by the Institute of Electrical and Electronics Engineers (IEEE) and the American National Standards Institute (ANSI). Each POSIX interface is separately defined in a numbered ANSI/IEEE standard or draft standard. The application program interface (API), known as POSIX.1, has become ISO/IEC IS 9945-1:1990. power distribution panel (PDP).
Glossary power shelf of the batteries, fans, and power supplies; to regulate the voltage supplied to the fans; and to provide the interface to the group ID switches and service light-emitting diodes (LEDs). A group contains two PMCUs, one for each of the two DC power distribution buses. power shelf.
Glossary private dynamic-link library (private DLL) operating system. The primary processor is the processor that has direct control over the SAC. Contrast with backup processor. private dynamic-link library (private DLL). See ordinary dynamic-link library (ordinary DLL). problem incident report. A type of incident report that reports a problem in the server. A problem incident report is generated when changes occur on the server that could directly affect the availability of system resources.
Glossary process-pair list (PPL) process-pair list (PPL). A table that contains one entry for each process or process pair associated with a named resource. For some devices, a single PPL entry is associated with multiple named resource list (NRL) entries. For process pairs, a single PPL entry describes both members of the pair. processor.
Glossary product module (PM) product module (PM). The part of the Subsystem Control Facility (SCF) subsystem that is responsible for subsystem-specific command processing. profile. Default values used by the Distributed Systems Management/Software Configuration Manager (DSM/SCM) when processing requests. The three types of profiles are the Configuration Manager profile, the system profile, and the target profile. PROFILE object type.
Glossary R2 R2. See ServerNet router 2. raceway. An enclosed channel used to hold wires, cables, or busbars. Most raceways have removable tops to facilitate the installation or removal of their contents. rack. A structure that houses a chassis, power shelf, and other system components. The HP NonStop™ S-series server is designed to be mounted in an industry-standard 19-inch rack or a NonStop S-series frame. See also frame. radio frequency interference (RFI).
Glossary reference page recorded by the linker as a DLL is built. It affects only localized clients of the DLL. This feature allows a symbol to be moved from one DLL to another without relinking clients of the original DLL. Reexporting is transitive; that is, if A reexports B and B reexports C, then A reexports C. Reexported libraries can reexport other libraries to form a succession of reexported libraries of arbitrary length. reference page.
Glossary remote interprocessor communication (RIPC) console and access your HP NonStop™ S-series server to diagnose hardware and software problems. See also remote notification. remote interprocessor communication (RIPC). The exchange of messages between processors in different systems or nodes. remote mount. A mount used by a Network File System (NFS) client to attach part of the local NFS file hierarchy to a point within the client’s remote file hierarchy.
Glossary remote system remote system. An active ServerNet node to which the local system has active external ServerNet paths. Contrast with local system. request packet. A ServerNet packet sent from one ServerNet device to another, requesting either a read action or a write action on the part of the receiving device. In the case of a write request, the packet contains the data to be written.
Glossary rld library rld library. A library that loads position-independent code (PIC) programs and their associated dynamic-link libraries (DLLs). The rld library also provides the dlopen(), dlclose(), dlresultcode(), dlsys(), and dlerror() functions. rms. See root mean square (rms). robot. A media-changer device that transfers a tape cartridge to a tape drive for use and then returns the cartridge to the storage cell. root. See root fileset and root directory. See also super ID. root directory.
Glossary run-time linker run-time linker. See linker. run-time loader. See loader. RVU. See release version update (RVU). S700 server. See HP NonStop™ S700 server. S7000 server. See HP NonStop™ S7000 server. S7400 server. See HP NonStop™ S7400 server. S7600 server. See HP NonStop™ S7600 server. S7800 server. See HP NonStop™ S7800 server. S70000 server. See HP NonStop™ Sxx000 server. S72000 server. See HP NonStop™ Sxx000 server. S74000 server. See HP NonStop™ Sxx000 server. S76000 server.
Glossary save file save file. A file created through the Inspect or Debug product. A save file contains enough information about a running process at a given time to restart the process at the same point in its execution. A save file contains an image of the process, data for the process, and the status of the process at the time the save file was created. A save file can be created through an Inspect SAVE command at any time.
Glossary searchList searchList. For each loadfile, a list that is constructed and used by the linker and loader to tell them which libraries to examine, and in which order, to locate symbol definitions needed by that loadfile. The linker and loader construct the loadfile’s searchList in accordance with that loadfile’s import control, which is set at link time by the loadfile’s programmer. A loadfile’s searchList is unaffected by the import control of any other loadfile. SEB.
Glossary serial communications controller (SCC) derived power sources include standby power generator, uninterruptible power supply (UPS), isolation transformer, and computer-room power center (CRPC). serial communications controller (SCC). A type of communications controller. Each quad-integrated communications controller (QUICC) has four SCCs to handle the two Ethernet ports and the two wide area network (WAN) ports. serial copper.
Glossary ServerNet II ServerNet II. The second-generation ServerNet network. ServerNet II architecture is backward-compatible with ServerNet I architecture, and it features 125 (or 50) megabytes/second speed, 12-port ServerNet routers, 8b/9b and 8b/10b (serializer ready) encoding, and a 512-byte maximum packet size. See also ServerNet I. ServerNet adapter. A component that connects peripheral devices to the rest of the system through a ServerNet bus interface (SBI).
Glossary ServerNet cluster subsystem ServerNet cluster subsystem. The subsystem managed by the ServerNet cluster monitor process (SNETMON). The subsystem name is SCL. The subsystem number is 218. The subsystem identifier is ZSCL. ServerNet/DA. See ServerNet device adapter (ServerNet/DA). ServerNet device. Interface logic that is associated with a specific hardware unit, such as a processor or I/O adapter, and that provides the interface to the ServerNet communications network.
Glossary ServerNet ID ServerNet ID. A unique identifier for an addressable unit on a ServerNet communications network. A unit can have multiple ServerNet node IDs. This ID is used for routing. Each packet has a source ServerNet node ID and a destination ServerNet node ID. A pair of processors operating in duplex mode share one ServerNet node ID. ServerNet LAN Systems Access (SLSA) subsystem.
Glossary ServerNet router 1 crossbar switch, able to switch any of its input ports to any of its output ports. A ServerNet router in an HP NonStop™ S-series server has either six router ports (see ServerNet router 1) or twelve router ports (see ServerNet router 2). ServerNet router 1. A model of ServerNet router that, in an HP NonStop™ S-series server, has a total of six input and six output ports. See also ServerNet router 2. ServerNet router 2.
Glossary service equipment server. A service connection can be used to communicate with the server only when the HP NonStop™ Kernel operating system is running. A service connection provides a comprehensive service and maintenance picture of the server and is used to perform most service management tasks. See also low-level link. service equipment. The necessary equipment, usually consisting of circuit breakers and their accessories, that is located near the entrance point of supply conductors.
Glossary set-user-ID program set-user-ID program. In the Open System Services (OSS) environment, a program file that has the S_ISUID bit set in its file mode. shared memory. An interprocess communication mechanism that allows two or more processes to share a given region of memory. Shared Millicode Library. An intrinsic library containing privileged or TNS-derived millicode routines used by many native-compiled programs and by emulated TNS programs.
Glossary signal mask signal mask. The set of signals that are currently blocked from delivery to a specific process. signal reference grid. A series of conductors, constructed of pure or composite metals (for example, copper) with good surface conductivity. A superior signal reference grid is installed on the subfloor of a computer room and connected to the raised-floor structure to establish constant and equal potential for all equipment in the computer room that is connected to it.
Glossary skin effect skin effect. The tendency of higher frequency signals to flow on the outside surface, or skin, of a conductor instead of through the entire cross-section of the conductor. The result is less total conductor area available for carrying current and an increase in the resistance of the conductor at that high signal frequency. slot. A physical, labeled space for a customer-replaceable unit (CRU) or field-replaceable unit (FRU) that is part of a module. A module contains one or more slots.
Glossary SNDA Inspect and Inspect can be used to debug snapshots, but the Inspect product refers to a snapshot a save file. SNDA. See ServerNet device adapter (ServerNet/DA). SNETMON. See ServerNet cluster monitor process (SNETMON). SNMP. See Simple Network Management Protocol (SNMP). SNMP task. A task that runs in each ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP) as part of the WAN architecture.
Glossary spooler links. Introduced with the G06.12 release version update (RVU), the split-star topology supports up to 16 nodes. See also star topology, tri-star topology, and layered topology. spooler. The collection of files and processes that manages the printers and print jobs on the system. SPR. See software product revision (SPR). SP Tool Application. A PC-based software application that you can use to request information from the master service processors (MSPs) in an HP NonStop™ S-series server.
Glossary star topology star topology. A network topology in which all nodes are connected to a central hub (HP NonStop™ Cluster Switch). Each node has its own connection to the network, so a break in the connection does not affect other nodes in the network. In a ServerNet cluster, a star topology requires one cluster switch for each external fabric and can support up to eight nodes. See also split-star topology, tri-star topology, and layered topology. startup file.
Glossary strictly conforming POSIX.1 application strictly conforming POSIX.1 application. An application that requires only the facilities described in ISO/IEC IS 9945-1:1990 and the applicable computer language standards. Such an application must accept any behavior or value described in ISO/IEC IS 9945-1:1990 as unspecified or implementation-defined and, for symbolic constants, accept any value permitted by ISO/IEC IS 9945-1:1990. structured view of the user ID.
Glossary Subsystem Control Facility (SCF) Each subsystem has a manager through which applications can request services by issuing commands defined by that subsystem. See also subsystem manager. Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and collecting information from a subsystem and its objects. SCF enables you to configure and reconfigure devices, processes, and some system variables while your HP NonStop™ S-series server is online.
Glossary super time factors (STFs) The super ID has the set of special permissions called appropriate privileges. In the Guardian environment, the structured view of the super ID, which is (255, 255), is most commonly used. In the Open System Services (OSS) environment, the scalar view of the super ID, which is 65535, is most commonly used. super time factors (STFs).
Glossary switch logic board switch logic board. See cluster switch logic board. switch mode power supply. A computer power supply that uses a pulse-width modulation switching inverter and nonlinear current draw characteristics. Switch-mode power supplies are widely used because of their small size and efficiency. switch rack. See cluster switch rack. switch zone. See cluster switch zone. switched connect. Connection to the Enterprise Storage System (ESS) through a Fibre Channel switch (FC switch). symbol.
Glossary System Code (SC) System Code (SC). See TNS code space. system code. A logically distinct part of the HP NonStop™ Kernel operating system that consists of operating-system procedures shared by all processors. system configuration database. The database file on the $SYSTEM.ZSYSCONF subvolume that contains configuration information for all system objects that can be configured by the Subsystem Control Facility (SCF).
Glossary system interrupt vector (SIV) system interrupt vector (SIV). An HP NonStop™ Kernel operating system data structure that contains the addresses of interrupt handlers, parameters passed to interrupt handlers by special interrupt microcode, and other interrupt processing information. System Library (SL). See TNS code space. system library. A logically distinct part of the HP NonStop™ Kernel operating system that consists of user-callable library procedures and kernel procedures. system load.
Glossary system resource model (SRM) system resource model (SRM). A collection of C++ objects that model the diagnostic and serviceability state behavior of the system resources discovered and managed by the Compaq TSM package. The SRM has these attributes: Generic process name $ZZKRN.#TSM-SRM Process name $ZTSM Program file name $SYSTEM.SYSnn.SRM system serial number. A unique identifier, typically five or six alphanumeric characters, assigned to an HP NonStop™ S-series server when it is built.
Glossary TCP TCP. See Transmission Control Protocol (TCP). TCP/IP. See Transmission Control Protocol/Internet Protocol (TCP/IP). TEMPLI. The Event Management Service (EMS) template installation program that merges template object files from specified subsystems and produces resident and nonresident template files. terabyte (TB). A unit of measurement equal to 1,099,511,627,776 bytes (1024 gigabytes). See also gigabyte (GB), kilobyte (KB), and megabyte (MB). terminal.
Glossary three point fall of potential measurement method three point fall of potential measurement method. The measurement of a grounding electrode (such as a ground rod) where ground resistance is measured with respect to two other points. The ratio of the measurements determines the resistance of the grounding electrode. TIM. See HP NonStop™ Technical Library (NTL). time factor (TF). A number assigned to a line, path, or route to indicate its efficiency in transporting data.
Glossary TNS object file TNS object file. The object file created by a TNS compiler. The file contains TNS instructions and other information needed to construct the code spaces and the initial data for a TNS process. TNS process. A process initiated by executing a TNS or accelerated object file. A TNS process, whether accelerated or not, uses TNS register and stack conventions. Contrast with TNS/R native process. TNS shared run-time library (TNS SRL).
Glossary Token-Ring ServerNet adapter (TRSA) Services (OSS) environments. TNS/R native SRLs can be either public or private. A TNS/R native process can have multiple public SRLs but only one private SRL. Token-Ring ServerNet adapter (TRSA). A ServerNet adapter that provides a single line from an HP NonStop™ S-series server to a token-ring network, allowing the server to act as a station on the ring.
Glossary Trivial File Transfer Protocol (TFTP) G06.14 release version update (RVU), the tri-star topology supports up to 24 nodes. See also split-star topology, star topology, and layered topology. Trivial File Transfer Protocol (TFTP). A protocol defined by Request for Comments (RFC) 1350. TFTP is used as a data link control (DLC) and diagnostic task. TRSA. See Token-Ring ServerNet adapter (TRSA). TSM. See Compaq TSM. TSM client software. See Compaq TSM client software. TSM Event Viewer.
Glossary undefined undefined. Pertaining to the use of an incorrect value for data or the incorrect behavior of a program for which the ISO/IEC IS 9945-1:1990 standard imposes no portability requirements. undervoltage. A negative change in the amplitude of the voltage. unicode. A 2-octet (2-byte) character code designed to represent more alphabetic and graphic characters than allowed by the ASCII character set.
Glossary user ID user ID. The unique identification of a user within a node. In the Guardian environment, the term user ID usually means the structured view of the HP NonStop™ Kernel user ID. In the Open System Services (OSS) environment, the term user ID usually means the scalar view of the HP NonStop™ Kernel user ID—a number called the UID. User Library (UL). See TNS code space. user library.
Glossary WAN shared driver WAN shared driver. A driver, provided as part of the wide area network (WAN) subsystem, that provides a simplified interface to HP NonStop™ TCP/IP for use by I/O processes. The shared driver interface is similar to that provided by DOIOPLEASE on earlier systems. WAN subsystem. See wide area network (WAN) subsystem. WAN subsystem manager process.
Glossary WORM WORM. See write once, read many (WORM). wormhole routing. A technique for reducing network latency in a router. Packet bytes are immediately switched to the appropriate output port as soon as they arrive rather than accumulated in a buffer until an entire packet is received. Contrast with store and forward routing. write once, read many (WORM). A media storage class in which data, once written, cannot be erased or overwritten. WWN. See worldwide name (WWN). WWN zones.
Glossary $ZCNF $ZCNF. The name of the configuration utility process. zero-signal reference. A connecting point, bus, or conductor used as one side of a signal circuit. Such a reference object might or might not necessarily be designated as a ground. Sometimes referred to as a common circuit. $ZEXP. The name of the Expand manager process. $ZMnn. The name of the QIO monitor process in processor nn. $ZNET. The name of the Subsystem Control Point (SCP) management process. zombie process.
Glossary $ZZSCL $ZZSCL. The name of the ServerNet cluster monitor process (SNETMON). $ZZSMN. The name of the external system area network manager process (SANMAN). $ZZSTO. The name of the storage subsystem manager process. $ZZWAN. The name of the wide area network (WAN) subsystem manager process.
Glossary $ZZWAN G-Series Common Glossary Glossary- 120
Index A C ABORT command ADAPTER D-8 LIF D-8 PROCESS D-8 AC power cords caution 6-3 planning 1-8 plugging in 6-17 troubleshooting 7-2 ADD DISK 7-13 Adding enclosures offline 4-18 online 6-1/6-38 ALTER command AUTOCONFIG 7-13 SUBSYS 6-9 AUTOCONFIG 6-9, 7-13 AUTOSTART 6-9 Availability planning 1-6 Cables 1-8 See also AC power cords, Ethernet cables, Power-on cables, ServerNet cables DC power 1-8 EPO 1-9 Cautions AC power cords 6-3 KMSF 4-1, 6-3 online expansion 6-3 online reduction 4-1 resources 3-4 ServerN
Index E Deleting (continued) LIFs D-9 PIFs D-9 processes 4-9/4-10, D-3 SACs D-9 DHCP server 6-14 Disabling batteries 4-11 Disks not automatically configured 7-13 stopping D-2/D-5 Documentation, manual abstracts -xv Donor system deleting devices and processes 4-9 description 3-1, 4-2 preparation 4-2/4-18 saving configuration 4-17 worksheet packet 4-2 worksheets C-1 E E4SA See also ServerNet adapter connections 4-7 processes 4-7 removing D-6 stopping D-6/D-8 subsystems D-1 Emergency power-off (EPO) cables
Index F Expanding a system cautions 6-3 offline 4-18 online 6-1/6-38 planning 2-1/2-14 preparation 6-4/6-5 FTP (continued) start session 6-13 target system 6-12 FUP LISTOPENS D-3 tracing processes D-3, D-8 F G Fabrics See ServerNet fabrics FCSA 1-2 fibre-channel cables 1-8 File Transfer Protocol (FTP) See FTP File Utility Program (FUP) See FUP Firmware processor donor system 4-5, 6-7 verifying 6-37 SCSI controller donor system 4-5, 6-7 SP compatibility 6-20, 6-37 copying 6-11/6-13 donor system 4-5, 6-
Index K IP addresses See also Low-level link IP addresses already exist 7-6 configuring 6-19 default 6-14 FTP 6-11 MSP 6-14 overwriting 6-19 service connection 6-8 troubleshooting 7-6 IP Addresses for IOAM 6-14 I/O multifunction (IOMF) CRUs See IOMF CRUs K Kernel-Managed Swap Facility (KMSF) See KMSF swap space KMSF swap space caution 4-1, 6-3 planning 3-4 stopping disks D-2 target system 6-37 L LEDs IOMF CRUs 6-17 PMF CRUs 6-17 power-on 6-17, 6-28 troubleshooting 7-5 Light-emitting diodes (LEDs) See LE
Index P Online system expansion performing 6-1/6-38 planning 2-1/2-14 system reduction performing 4-1/4-18 planning 3-1/3-17 Open Systems Management (OSM) guided replacement procedures and -xvi low-level link 5-1 preparing for expansion and 6-4 required RVU 1-4, 4-1, 4-2, 6-3 Service Connection 3-4 checking enclosure status with 4-13 determining fabric status with 4-6 ensuring device deletion with 4-10 maintaining connections for 4-17 removing cables with 4-12, 4-14 updating firmware 6-35 OSM console tool
Index R Processor See also Firmware reloading 6-37 troubleshooting 7-10 Processor multifunction (PMF) CRUs See PMF CRUs R Recabling 6-22 Reducing a system See Removing enclosures Reloading processors does not work 7-10 in added block 6-37 Removing disk D-2 E4SA D-6 enclosures considerations 3-2 description 4-1/4-18 ease 3-2 methods 3-3 offline 5-1 planning 3-1 sequence 3-17 Request timed out 7-10 Resizing See also Expanding a system, Removing enclosures planning 1-3 prerequisites 1-2 S SAVE CONFIGURATIO
Index S ServerNet cables attaching 6-29/6-30 labeling 6-5 planning 1-8 recabling 6-22 removing 4-18 verifying 6-26 ServerNet expansion board (SEB) See SEB ServerNet fabrics caution 6-3 cross-cabled 7-10 preparing 4-6 status 4-6 verifying 6-18 ServerNet switch board IP addresses 4-5, 6-14 ME firmware 4-5, 6-7 ME FPGA 4-5, 6-7 ServerNet topology See Topology ServerNet wide area network (SWAN) concentrator See SWAN concentrator ServerNet worksheets example 3-6/3-17 list C-1 Service connection IP addresses 6-
Index T System serial number donor system 4-4 target system 6-6 System time, setting 5-1 System type donor system 4-4 target system 6-6 T TACL adding block 6-9 CLCI connection 4-17 commands RELOAD 6-37, 7-10 STATUS 4-8, 6-9, D-8 configuration of CRUs 6-32 does not start 7-12 IP addresses 6-11 process lists D-3 processor reload 6-37 save configuration 4-3 startup 4-8, 4-17, 7-12, A-9 system reduction 4-8 Tandem Advanced Command Language (TACL) See TACL Tape drives 4-7 Target system description 6-6 saving
Index W W Worksheets 2.1a 4-2, 4-6 2.
Index Z HP NonStop S-Series System Expansion and Reduction Guide—522465-009 Index-10
