HP NonStop BladeCluster Solution Manual HP Part Number: 604082-004 Published: November 2012 Edition: H06.14 and subsequent H-series RVUs and J06.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document.....................................................................................7 Supported Release Version Updates (RVUs)..................................................................................7 Intended Audience....................................................................................................................7 New and Changed Information for the 604082–004 Edition.........................................................7 Document Organization....
Processor Switch Cable Connections for BladeCluster/NonStop NS16000 Series Solution Topology...............................................................................................................................49 Example of a Two-Node BladeCluster/NonStop NS16000 Series Solution................................51 ServerNet Switch and Processor Switch Cable Connections for BladeCluster/Mixed System Solution Topology......................................................................................
Starting Starting Starting Starting Starting Starting the ServerNet Cluster Subsystem...................................................................................81 the External ServerNet Fabric.......................................................................................81 SANMAN.................................................................................................................81 MSGMON.............................................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Example of the BladeCluster/BladeSystem Solution Topology.................................................13 Example of the BladeCluster/NonStop NS16000 Series Solution Topology..............................13 Example of the BladeCluster/Mixed System Solution Topology...............................................14 Example of the BladeCluster/6700 Series Solution Topology.................................................
About This Document This guide describes the HP NonStop™ BladeCluster Solution and how to install and migrate HP Integrity NonStop BladeSystems and NonStop NS16000 series systems to the topology as well as migrating from or clustering with 6770/6780 ServerNet clusters. Supported Release Version Updates (RVUs) This publication supports the H06.14 and all subsequent H-series RVUs and J06.04 and all subsequent J-series RVUs until otherwise indicated in a replacement publication.
Document Organization Section Contents BladeCluster Solution Overview (page 12) Introduces the BladeCluster Solution product. It describes concepts that are essential to understanding the operation of a BladeCluster and its software and hardware requirements. Installation and Migration Tasks (page 28) Describes the steps to install an initial BladeCluster topology or to migrate a NonStop BladeSystem or NonStop NS16000 series to the topology.
file-name Computer Type Computer type letters indicate: • C and Open System Services (OSS) keywords, commands, and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: Use the cextdecs.h header file. • Text displayed by the computer. For example: Last Logon: 14 May 2006, 08:02:23 • A listing of computer code.
… Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]… - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown.
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.
1 BladeCluster Solution Overview The BladeCluster Solution is comprised of network topologies that interconnect NonStop BladeSystems and NonStop NS16000 series systems as nodes, which can also cluster with 6770/ 6780 ServerNet clusters. These interconnected nodes use ServerNet to pass information from node–to–node functioning as one large processing entity. WARNING! All procedures in this manual must be performed by authorized service providers.
BladeCluster/BladeSystem Solution The BladeCluster/BladeSystem Solution topology is comprised of a zone populated with BladeSystem nodes. There can be one to eight BladeSystem nodes in this topology. Figure 1 Example of the BladeCluster/BladeSystem Solution Topology For more information about the connections for this topology, refer to “ServerNet Switch Connections” (page 43).
BladeCluster/Mixed System Solution The BladeCluster/Mixed System Solution topology is comprised of a zone populated with NonStop BladeSystems and NonStop NS16000 series nodes. There can be one to four nodes of either system type and up to 8 nodes in this topology. When there are more than five nodes, node 1 and nodes 6–8 must be occupied by a NonStop BladeSystem. Table 1 ServerNet Node Positions in a Single Zone ServerNet Node 1 If 5 or Less Nodes are in the Zone, the System is a...
BladeCluster/6700 Series Solution NOTE: NonStop NS14000 series can only connect to 6780 ServerNet clusters. The BladeCluster/6700 Series Solution topology is comprised of a zone populated with NonStop BladeSystems or NonStop NS16000 series nodes that provide connectivity to NonStop S-Series and NS14000 series systems via a 6700 series ServerNet Cluster (either a 6770 or 6780 cluster switch).
BladeCluster/Multi-Zone Solution The BladeCluster/Multizone Solution offers short-haul and long-haul multi-zone topologies comprised of multiple BladeCluster zones (up to 3 zones) interconnected as clusters of nodes (up to 24 nodes). Each zone-to-zone connection is a ServerNet multi-lane link comprised of ServerNet 3 links (unless configured for ServerNet 2 in interzone distances greater than 25 km) and each zone can contain a different number of nodes.
NOTE: For a list of supported DWDMs, contact your HP representative. For information about connecting these multi-zone topologies, refer to “Connections to BladeCluster/Multi-Zone Solution Topologies” (page 63). Multi-Zone Configuration Options There are two BladeCluster/Multi-zone configuration options: • The first option is a fault-tolerant, high-availability configuration. The high-availability configuration option splits the anchor node's inter-zone connections between two c7000 enclosures.
Hardware Overview Depending on your BladeCluster topology, standard hardware for BladeCluster can include: • “ServerNet Switch for BladeCluster” (page 18) • “Processor Switch (P-Switch) for BladeCluster ” (page 19) • “Advanced Cluster Hub (ACH)” (page 20) • “Dense Wavelength Division Multiplexer (DWDM) ” (page 20) NOTE: For 6700 series cluster switches, refer to “Hardware Requirements for BladeCluster/6700 Series Solution” (page 56).
NOTE: • BladeCluster Ports (13-18) ◦ • You cannot use ports 11 and 12 at the same time. Each BladeCluster port supports four transmit/receive fiber pairs. However, one transmit/receive fiber pair in each of ports 16 and 18 is not used. Fiber (1-4) Processor Switch (P-Switch) for BladeCluster No external switches are required by the BladeCluster topologies that include NonStop NS16000 series systems. Instead, external routing is handled by the processor switches within each NonStop NS16000 series node.
Advanced Cluster Hub (ACH) NOTE: OSM refers to the Advanced Cluster Hub as a patch panel. An Advanced Cluster Hub (ACH) is used to connect NonStop NS16000 series processor switches and BladeSystem ServerNet switches in a BladeCluster topology. Using the ACH reduces the number of cable connections per fabric. All cables from the p-switches or ServerNet switches in a node are bundled together using Multifiber Termination Push-on (MTP) cables that are then connected to the ACH.
Expand and Message-System Traffic In a BladeCluster, message-system traffic flows directly between processors by way of the message system but under the control of Expand. The Expand product has an option called Expand-over-ServerNet. This option provides high performance inter-application communication with minimal processor cost. The illustration below diagrams this message-system traffic.
Software Requirements for the Current Release of BladeCluster NOTE: If your topology includes nodes that only connect to 6700 series fabrics and not to BladeCluster fabrics, these software requirements do not apply. Instead, follow the “Software Requirements for BladeCluster/6700 Series Solution” (page 57) for these nodes. All of the required software shown in this table is for the current version of BladeCluster and it is included in the J06.12 and H06.23 RVUs. This software can be installed on H06.14/J06.
Migrating from Previous Releases of the BladeCluster Solution If you are migrating from a previous release of the BladeCluster Solution, install the SPRs in the table above and follow the installation instructions in each SPR's softdoc to install the SPRs on the nodes. All of these SPRs can be installed without a system load.
BladeCluster Software (H06.21 and J06.10 RVUs) All of the required software shown in this table is included in the H06.21 and J06.10 RVUs and can be installed on H06.14/J06.04 and later RVUs without requiring a system load. Table 4 Software Requirements for BladeClusters (H06.21 and J06.
BladeCluster Software (H06.20 and J06.09 RVUs) All of the required software shown in this table is included in the H06.20 and J06.09 RVUs and can be installed on H06.14/J06.04 and later RVUs without requiring a system load. Table 5 Software Requirements for BladeClusters (H06.20 and J06.
BladeCluster Software (H06.19 and J06.08 RVUs) All of the required software shown in this table is included in the H06.19 and J06.08 RVUs and can be installed on H06.14/J06.04 and later RVUs without requiring a system load. Table 6 Software Requirements for BladeClusters (H06.19 and J06.
BladeCluster Software (J06.07 RVU) All of the required software shown in this table is included in the J06.07 RVU and can be installed on J06.04 and later RVUs without requiring a system load. Table 7 Software Requirements for BladeCluster (J06.
2 Installation and Migration Tasks Use this chapter to plan your BladeCluster topology and to migrate, install, and configure the nodes in the topology. All required steps are detailed in the “Checklist of Installation and Migration Tasks — Tasks 1 through 8” (page 28).
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Installation/Migration Tasks TIP: This step is only required for multi-zone topologies. Skip this step if you are configuring a single-zone BladeCluster. For more information, see...
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Installation/Migration Tasks For more information, see... If the BladeCluster zone requires installation of the ACHs, only a service provider can install the hubs on the rack rails. Service providers, for ACH information refer to “Advanced Cluster Hubs (ACHs)” (page 38).
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Installation/Migration Tasks For more information, see... Check that all nodes participating in the BladeCluster topology have the Expand-over-ServerNet profile (T0509H01^AAH).
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) d) If you adding a single-zone BladeCluster and do not plan to add zones to this configuration in the future, skip these bulleted steps and proceed to substep “e” following.
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Task 6: Configure and Start Subsystem Processes and Expand Lines and Verify ServerNet Cluster Connectivity Installation/Migration Tasks Action or Command Run the ZSCCONF TACL macro (located in $SYSTEM.ZSUPPORT) to configure and start the $ZZSCL (SNETMON) and $ZIMnn (MSGMON) processes processes in the node. Refer to Starting and Stopping ServerNet Cluster Processes and Subsystems (page 80).
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) • BladeSystem ServerNet switches or NonStop NS16000 series processor switches that meet the hardware requirements for BladeCluster connectivity can remain connected to the 6700 series ServerNet cluster. For more information about hardware requirements, refer to “Hardware Overview” (page 18).
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Migration Only Tasks Command or Action If $ZZSCL is running, abort (but do not delete) the process. SCF ABORT PROCESS $ZZKRN.#ZZSCL Check if the $ZIMnn (MSGMON) processes are SCF STATUS PROCESS $ZZKRN.#MSGMON running in each node that is being migrated from a 6700 series ServerNet Cluster to a BladeCluster Solution topology. If the $ZIMnn processes are running, abort (but do SCF ABORT PROCESS $ZZKRN.
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Upgrade Tasks Command or Action... On each node that will be connected to the Notify end users before terminating applications. BladeCluster Solution topology: stop all applications that use Expand-over-ServerNet lines to communicate with other nodes.
Table 8 Checklist of Installation and Migration Tasks — Tasks 1 through 8 (continued) Upgrade Tasks Command or Action... Complete Tasks 3, 4, and 6 for each BladeSystem Refer to: or NS16000 series node that will be connected to • Task 3: Perform the Add Node to ServerNet Cluster the BladeCluster Solution topology.
3 Advanced Cluster Hubs (ACHs) NOTE: OSM refers to the Advanced Cluster Hub as a patch panel. This chapter describes the Advanced Cluster Hub (ACH) which is used to connect processor switches and ServerNet switches in a BladeCluster topology. Advanced Cluster Hub (ACH) Description The ACH is used to connect the processor switches and ServerNet switches in each node within the zone along one fabric as described in “Connections to the Advanced Cluster Hubs” (page 43).
• Contains a cable management system that includes cable management cartridges for securing the MTP-4LC or MTP-MTP fiber cables. • Two ACHs are required per zone: one each for the X and Y fabrics. Width Length Height Dimensions in cm in cm in cm Advanced Cluster Hub1 17.4 44.1 26.8 68 3.3 8.4 1 An ACH weighs 16 pounds (7.2 kilograms).
Figure 7 Example of Advanced Cluster Hubs (ACHs) in a NonStop BladeSystem Figure 8 Example of Advanced Cluster Hubs in a NonStop NS16000 Series 40 Advanced Cluster Hubs (ACHs)
Cable Management Procedure for the ACH The cable management system for the ACH consists of a cable management tray attached to the rear side of the ACH. The tray has 10 cable management cartridges used to secure the MTP fiber cables. At each side of the tray, a vertical radius guide (VRG) routes the cables up or down the rack while maintaining a minimum bend radius. Perform this procedure for each ACH in the BladeCluster zone. On the back of each ACH: NOTE: 1. 2. 3. 4.
Figure 10 (page 42) shows two cables routed in opposite directions. One cable is routed around the right side of the center radius control and then directed to the left side of the rack. The other cable is routed around the left side of the center radius control and then directed to the right side of the rack. Figure 10 Cables Routed Around Center Radius Control 7. 8. 9. 42 Route the cables out of the assembly through the vertical radius guide (VRG).
4 Connections to the Advanced Cluster Hubs CAUTION: All connections must be done under the guidance of the Add Node to ServerNet Cluster guided procedure. Wait until the procedure prompts you to make the connections. If you are adding a node to a BladeCluster/6700 Series Solution, you must make all connections to both types of clusters before continuing with the procedure. For the 6700 series ServerNet Cluster connections, see Chapter 5 (page 56).
This illustration shows the connections on a ServerNet switch to an Advanced Cluster Hub. Figure 11 ServerNet Switch for BladeCluster Connectivity Width Depth Height Dimensions in cm in cm in cm ServerNet Switch1 15.3 38.8 10.75 27.3 1.1 2.7 1 A ServerNet switch weighs six pounds (2.7 kilograms). For c7000 enclosure specifications, see the NonStop BladeSystem Planning Guide. Before Cabling the ServerNet Switches in a Single-Zone Topology 1. 2. 3.
Before Cabling the ServerNet Switches in a Multi-Zone Topology 1. 2. For each zone of the multi-zone topology, verify that a pair of ACHs (one for each external fabric) is installed for the BladeCluster. One pair of ACHs supports up to eight nodes per zone. For installation instructions, see “Advanced Cluster Hubs (ACHs)”.
ServerNet Switch Cable Connections for BladeCluster/BladeSystem Solution Topology This table and illustration on next page show the port connections between the ServerNet switches and the ACH. A pair of ACHs is installed for each BladeCluster and supports up to 8 nodes. One ACH supports the X fabric, the other the Y fabric. The port numbering on each ACH is identical.
Figure 12 ServerNet Switch to ACH Connections Example of a Two-Node BladeCluster This illustration shows an example of the ServerNet switch to ACH connections for a two-node BladeCluster.
Processor Switch Connections This section describes the processor switch hardware, physical dimensions, and connections from the processor switch to the ACH. Processor Switch Hardware Description The processor switch, or p-switch, provides the first level of ServerNet fabric interconnect for the Integrity NonStop NS16000 series nodes in a BladeCluster.
Before Cabling the Processor Switches • Verify that a pair of ACHs (one for each external fabric) is installed for the BladeCluster. One pair of ACHs supports up to five NonStop NS16000 series nodes. For installation instructions, see “Advanced Cluster Hubs (ACHs)”. • Verify that the processor switches in group.module locations 100.2 and 100.3 of the NonStop NS16000 series node that is being added to the BladeCluster have quad MMF PICs installed in slots 7 and 9.
Table 10 Processor Switch to ACH Connections (BladeCluster/NonStop NS16000 Series Solution) (continued) ServerNet Node Number 3 4 5 1 50 Processor Switch1 Slot PIC Port Connects to...
Example of a Two-Node BladeCluster/NonStop NS16000 Series Solution Figure 14 (page 51) shows an example of the processor switch to ACH connections for a two-node BladeCluster/NonStop NS16000 Series Solution.
ServerNet Switch and Processor Switch Cable Connections for BladeCluster/Mixed System Solution Topology Table 11 (page 52) shows the port connections between the ServerNet switches (for BladeSystem nodes) and the p-switches (for NS16000 series nodes) and the shared ACH in the BladeCluster/Mixed System Solution topology. One pair of ACHs is installed for each BladeCluster and supports up to eight nodes. One ACH supports the X fabric, and the other ACH supports the Y fabric.
Table 11 ServerNet Switch/Processor Switch to ACH Connections (BladeCluster/Mixed System Solution Topology) (continued) ServerNet Node Number If Node is a... 3 NS16000 series BladeSystem 4 NS16000 series BladeSystem 5 NS16000 series Processor Switch1 ServerNet Switch2 Slot PIC Port Connects to... LC Connects Connector to ACH Port Port Connects to...
Table 11 ServerNet Switch/Processor Switch to ACH Connections (BladeCluster/Mixed System Solution Topology) (continued) ServerNet Node Number If Node is a... BladeSystem 6 7 8 54 BladeSystem only BladeSystem only BladeSystem only Processor Switch1 ServerNet Switch2 Slot PIC Port Connects to... LC Connects Connector to ACH Port Port Connects to...
Example of a Four-Node BladeCluster/Mixed System Solution Figure 15 (page 55) shows an example of the ServerNet switch and processor switch to ACH connections for a four-node BladeCluster that has two BladeSystem nodes and two NonStop NS16000 series nodes. NOTE: You use MTP-4LC cables for connections between the Advanced Cluster Hub and the p-switch. A single MTP connector at one end connects to the Advanced Cluster Hub. Four LC connectors at the other end (labeled 1 through 4) connect to the p-switch.
5 Connections to NonStop 6700 Series ServerNet Clusters CAUTION: All connections must be done under the guidance of the Add Node To ServerNet Cluster guided procedure. Wait until the procedure prompts you to make the connections. If you are adding a node to a BladeCluster/6700 Series Solution, you must make all connections to both types of clusters before continuing with the procedure. For the connections to the Advanced Cluster Hubs, see Chapter 4 (page 43).
for the star topologies (star, split-star, and tri-star); 6780 switches are used for the layered topology. For more information about 6700 series cluster switch hardware requirements or topologies, refer to “Related Documentation for 6700 Series ServerNet Clusters” (page 57). Software Requirements for BladeCluster/6700 Series Solution Software requirements for the BladeCluster/6700 Series Solution depend on your BladeCluster topology: Software Requirements1 Applies to...
It is possible that certain nodes connected to the 6770 ServerNet Cluster fabrics might not (or cannot) be connected to the BladeCluster fabrics. For example, consider a BladeCluster/6770 topology with: • BladeSystems and NS16000 series nodes connected to both the X1 and Y1 6770 ServerNet cluster switches and BladeCluster zone 1. • S-series nodes connected to the X2 and Y2 6770 ServerNet cluster switches. S-series nodes cannot connect directly to the BladeCluster fabrics.
Connecting BladeSystem Nodes to a BladeCluster/6770 Solution 1. 2. 3. Before connecting the cables, make sure the cables are labeled at both ends, indicating the applicable connections for: node, ServerNet fabric, 6770 cluster switch name (for example, X1), cluster switch PIC slot number (for example, 6), and cluster switch PIC port (for example, 1). Connect the cable from the X-fabric 6770 ServerNet cluster switch (X1) to port 12 of the ServerNet switch port in Group 100, module 2, slot 5.
When configuring a multi-zone BladeCluster/6780 topology, nodes connected to a particular BladeCluster zone must be assigned the same ServerNet node numbers on both the BladeCluster and 6780 ServerNet Cluster fabrics: Table 14 ServerNet Node Numbers in a Multi-Zone BladeCluster/6780 Topology 6780 ServerNet Cluster Switches ServerNet Node Numbers Assigned by the BladeCluster Zone with Matching ServerNet 6780 Switches Node Numbers X11 and Y11 1 to 8 1 X21 and Y21 9 to 16 2 X12 and Y12 17 to 24 3 X2
Figure 17 Example of a BladeCluster/Multi-Zone Long-Haul Topology Clustered with a 6780 ServerNet Cluster BladeCluster Node Connections to the BladeCluster/6780 Solution CAUTION: All connections must be done under the guidance of the Add Node to ServerNet Cluster guided procedure. Wait until the procedure prompts you to make the connections. If you are adding a node to a BladeCluster/6700 Series Solution, you must make all connections to both types of clusters before continuing with the procedure.
BladeCluster Node Interconnects to 6780 Cluster Nodes Via Connecting to... the PIC in the range 1–2 must be available for connecting one cable (SMF-LC) per fabric. Connecting BladeSystem Nodes to a BladeCluster/6780 Solution 1. 2. Connect the cable from the X-fabric 6780 ServerNet cluster switch (X11) to port 11 (MMF) or port 12 (SMF) of the ServerNet switch in Group 100, module 2, slot 5.
6 Connections to BladeCluster/Multi-Zone Solution Topologies CAUTION: All connections must be done under the guidance of the Add Node to ServerNet Cluster guided procedure. Wait until the procedure prompts you to make the connections to the anchor nodes. NOTE: The maximum overall distance between non-anchor nodes in different zones is 125 meters + 65 kilometers + 125 meters = 65,250 meters (40.54 miles).
BladeCluster Inter-zone Speed Attributes The SCF ALTER SUBSYS $ZZSCL and SCF INFO SUBSYS $ZZSCL commands support new BladeCluster inter-zone speed attributes BCZ1Z2SPEED, BCZ1Z3SPEED, and BCZ2Z3SPEED.
BladeCluster Connections for the Short-Haul Multi-Zone Topology (2 Zones) To participate in a BladeCluster/Multizone Solution with the short-haul option for two zones, both ServerNet switches in a BladeSystem anchor node must have port 13 (labeled VA) and port 14 (labeled VB) available in slots 5 and 7. For an illustration of these ServerNet switch ports and faceplate labels, see “ServerNet Switch for BladeCluster” (page 18).
BladeCluster Connections for the Short-Haul Multi-Zone Topology (3 Zones) To participate in a BladeCluster/Multizone Solution with the short-haul option for three zones, both ServerNet switches in a BladeSystem anchor node must have port 13 (labeled VA) and port 14 (labeled VB) available in slots 5 and 7. For an illustration of these ServerNet switch ports and faceplate labels, see “ServerNet Switch for BladeCluster” (page 18).
BladeCluster Connections for the Long-Haul Multi-Zone Topology (2 Zones) To participate in a BladeCluster/Multizone Solution using one of the long-distance options—25 kilometers (km), 50 km, or 65 km—both ServerNet switches in a BladeSystem anchor node must have port 13 (labeled VA) available in slots 5 and 7. For an illustration of this ServerNet switch port and faceplate label, see “ServerNet Switch for BladeCluster” (page 18).
BladeCluster Connections for the Long-Haul Multi-Zone Topology (3 Zones) To participate in a BladeCluster/Multizone Solution using one of the long-distance options—25 kilometers (km), 50 km, or 65 km—both ServerNet switches in a BladeSystem anchor node must have port 13 (labeled VA) available in slots 5 and 7. For an illustration of this ServerNet switch port and faceplate label, see “ServerNet Switch for BladeCluster” (page 18).
Interzone Long-Haul Connections (3 Zones) From ServerNet Nodes (MTP to 4LC) To DWDM Max. Distance From DWDM (SMF customer-supplied cable) To DWDM Max. Distance Zone 1: DWDM Zone 2: DWDM Zone 2: DWDM Zone 3: DWDM Zone 3: DWDM Zone 1: DWDM Determined by the Long-Haul option you selected and is either: 25 km, 50 km, or 65 km. After connecting the cables, wait for the node to appear under the BladeCluster object in the OSM Service Connection.
7 Checking Operations This chapter provides procedures to check the operations of the BladeCluster.
Checking That Automatic Line-Handler Generation is Enabled Use one of these methods to determine if the automatic line-handler generation is enabled in the nodes: • Check for the presence of $ZZKRN.#OSM-CONFLH-RD. If it is present, the automatic line-handler configuration is enabled. • Check the status of the routing distributor ($ZOLHD). If this process is running (but in a STOPPED state), automatic line-handler configuration is enabled.
5. Check that the processes are started: STATUS PROCESS $ZZKRN.#MSGMON STATUS PROCESS $ZZKRN.#ZZSMN STATUS PROCESS $ZZKRN.#ZZSCL 6. If either process is not started, refer to Starting and Stopping ServerNet Cluster Processes and Subsystems (page 80).
Hardware Prod Type is the hardware product type for the modules that connect the node to the BladeCluster fabrics. Cluster Topo Type is the cluster topology type for the modules that connect the node to the BladeCluster fabrics. BladeCluster indicates if the local node is configured for connectivity to a BladeCluster. BladeCluster/67x0 indicates if the local node is configured for connectivity to a combined BladeCluster/6770 or BladeCluster/6780 topology.
Checking the Operation of the Expand Processes and Lines $NCP and $ZEXP must be running before you add a node to a BladeCluster topology. The Expand-over-ServerNet line-handler processes and lines are configured and started after the node is added. Checking $NCP and $ZEXP Perform this procedure before connecting the fiber-optic cable from a ServerNet switch in a BladeSystem node to an Advanced Cluster Hub (ACH). Process TACL Name Required SCF Symbolic Name Expand manager $ZEXP $ZZKRN.
3. Check that the path is started: STATUS PATH $SC035, DETAIL 4. For additional information about the lines: INFO PROCESS $NCP, NETMAP For more information, refer to the Expand Configuration and Management Manual. 5. If a line is STOPPED, NOT READY, or not in a STARTED state, check that the remote node is up, and then start the line.
8 Changing the BladeCluster Topology CAUTION: Only authorized service providers can perform the installation and replacement procedures described in this manual.
Performing an RVU Upgrade on a Node This procedure describes the steps for an RVU upgrade in a node connected to any ServerNet Cluster topology (such as a BladeCluster Solution, ServerNet Cluster 6770, ServerNet Cluster 6780, or a combination of these cluster topologies). TIP: Besides the RVU upgrade itself, this procedure: • Minimizes EMS error messages on other nodes connected to the same ServerNet Cluster.
NOTE: It might take a few minutes for the node that received the RVU upgrade to restore ServerNet Cluster connectivity to all other nodes. a. b. The STATUS SUBNET $ZZSCL command also shows the state of the Expand-over-ServerNet lines to/from the node receiving the RVU upgrade. The Expand-over-ServerNet lines should restart automatically if the OSM Automatic Line Handler generation feature is enabled as described in “Checking That Automatic Line-Handler Generation is Enabled” (page 71).
and 2, which increases the aggregate bandwidth between these zones. For more information, refer to: • “BladeCluster Connections for the Short-Haul Multi-Zone Topology (2 Zones)” (page 65) • “BladeCluster Connections for the Short-Haul Multi-Zone Topology (3 Zones)” (page 66) • “BladeCluster Connections for the Long-Haul Multi-Zone Topology (2 Zones)” (page 67) • “BladeCluster Connections for the Long-Haul Multi-Zone Topology (3 Zones)” (page 68) 10.
9 Starting and Stopping ServerNet Cluster Processes and Subsystems When the ServerNet cluster subsystem is stopped, the BladeSystem node informs other nodes that it is leaving the BladeCluster. Stopping the ServerNet cluster subsystem destroys interprocessor connectivity between the node that receives the command and all other nodes over both external fabrics. The ServerNet cluster monitor process $ZZSCL itself does not stop but remains an active process.
3. 4. Shut down or reroute traffic for any applications using the Expand-over-ServerNet connections between the affected node and the rest of the BladeCluster. If your applications might be affected and adequate alternate Expand lines are not available, shut down all applications that depend on the Expand-over-ServerNet line-handler processes. For each Expand-over-ServerNet line on the affected node, stop the Expand-over-ServerNet lines to other nodes.
If $ZZKRN.#ZZSMN is configured but not started, use SCF to start it. This command starts a copy of SANMAN on every available processor on the node. At an SCF prompt: START PROCESS $ZZKRN.#ZZSMN Starting MSGMON If $ZZKRN.#MSGMON is configured but not started, use SCF to start it. This command starts a copy of MSGMON on every available processor on the node. At an SCF prompt: START PROCESS $ZZKRN.#MSGMON Starting SNETMON If $ZZKRN.#ZZSCL is configured but not started, use SCF to start it.
10 Troubleshooting This chapter provides procedures to troubleshoot and recover from basic problems that might occur when installing, changing, or migrating to a BladeCluster topology and includes these topics: • “Using OSM to Suppress BladeCluster Alarms” (page 83) • “Restoring Connectivity to a Node ” (page 83) • “Switching the SNETMON Primary and Backup Processes” (page 84) • “Starting Required Processes and Subsystems” (page 84) • “Fallback Procedures” (page 84) Using OSM to Suppress BladeClus
Switching the SNETMON Primary and Backup Processes When the SNETMON backup process becomes the new primary, it queries all processors in the node to find the state of ServerNet connections to all other nodes. If it finds any connections that are down, it initiates a sequence to bring the connections to an online state.
A Cables Cable Types, Connectors, Lengths, and Product IDs Available cables and their lengths are: Cable Type Connectors Length (meters) Length (feet) Product ID MMF LC-LC .24 .79 N.A. MMF MTP-MTP 1.5 5 M8925–01 5 16 M8925–05 10 33 M8925–10 30 98 M8925–30 50 164 M8925–50 80 262 M8925–80 100 328 M8925100 125 410 M8925125 2.5 8 M8941–02 3.
Table 16 BladeCluster Interconnections — Cable Length Restrictions (continued) Connection Type: Cable Type Connectors Max.
B Configuring MSGMON, SANMAN, and SNETMON CAUTION: You should neither configure nor start the $ZZSMN (SANMAN) process unless the BladeCluster will be connected to a 6700 series ServerNet cluster. The SANMAN process supports 6770 or 6780 ServerNet cluster switches and is not useful unless these switches are present. This appendix provides an example of how to configure MSGMON, SANMAN, and SNETMON as generic processes in the system configuration database.
6. Start the $ZZSMN process if needed: START PROCESS $ZZKRN.#ZZSMN 7. Check that the SCF state of the $ZIMnn processes are in the STARTED state: STATUS PROCESS $ZZKRN.#MSGMON 8. Start the $ZIMnn processes if needed: START PROCESS $ZZKRN.#MSGMON 9. Check that the ServerNet cluster subsystem is in the STARTED state: STATUS SUBSYS $ZZSCL 10.
Configure SANMAN CAUTION: You should neither configure nor start the $ZZSMN (SANMAN) process unless the BladeCluster will be connected to a 6700 series ServerNet cluster. The SANMAN process supports 6770 or 6780 ServerNet cluster switches and is not useful unless these switches are present. The ServerNet SAN manager process (SANMAN) must be configured: • To be persistent. It should be configured to be started at all times. • To have the process name $ZZSMN. You must set the NAME attribute to $ZZSMN.
Start MSGMON, SANMAN, and SNETMON CAUTION: You should neither configure nor start the $ZZSMN (SANMAN) process unless the BladeCluster will be connected to a 6700 series ServerNet cluster. The SANMAN process supports 6770 or 6780 ServerNet cluster switches and is not useful unless these switches are present. NOTE: When $ZZKRN.#MSGMON is started, it is normal to receive error messages indicating that one or more processes did not start due to CPU down.
C Expand Lines Form To complete the form: 1. Use the OSM Service Connection to identify the system name and Expand node number of the affected node. 2. Record the system name. 3. For the affected node, list the Expand-over-ServerNet lines to all other nodes. 4. For each other node, list the Expand-over-ServerNet lines to the affected node. On the affected Expand node... On all other Expand nodes..
D Safety Requirements for Service Providers Safety Requirements When you handle a FRU, follow standard operating practices and use electrostatic discharge (ESD) protection to minimize any potential damage to yourself and the equipment. See “Using ESD Protection” (page 93) NOTE: The Advanced Cluster Hub is a passive component and does not require ESD protection. Standard Operating Practices 92 • Obtain an ESD protection kit and follow the directions that come with the kit.
Using ESD Protection Safety Requirements 93
Safety and Compliance This section contains three types of required safety and compliance statements: • Regulatory compliance • Waste Electrical and Electronic Equipment (WEEE) • Safety Regulatory Compliance Statements The following 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.
Taiwan (BSMI) Compliance Japan (VCCI) Compliance This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take corrective actions. European Union Notice Products with the CE Marking comply with both the EMC Directive (2004/108/EC) and the Low Voltage Directive (2006/95/EC) issued by the Commission of the European Community.
Ukraine Addendum to User Documentation Україна Додаток до документації користувача: Обладнання відповідає вимогам Технічного регламенту щодо обмеження використання деяких небезпечних речовин в електричному та електронному обладнанні, затвердженого постановою Кабінету Міністрів України від 3 грудня 2008 № 1057 Збережіть цей документ разом із документацією користувача для цього виробу Laser Compliance This product may be provided with an optical storage device (that is, CD or DVD drive) and/or fiber optic tr
IMPORTANT: TOUS LES RECIPIENTS SONT DESTINES UNIQUEMENT A UN USAGE INTERNE. VORSICHT: ALLE STECKDOSEN DIENEN NUR DEM INTERNEN GEBRAUCH. HIGH LEAKAGE CURRENT To reduce the risk of electric shock due to high leakage currents, a reliable grounded (earthed) connection should be checked before servicing the power distribution unit (PDU).
Safety and Compliance
Index Symbols 6770/6780 ServerNet Clusters clustering with BladeCluster topology, 15 connecting to BladeCluster, 56 hardware requirements, 56 software requirements, 57 A Advanced Cluster Hub (ACH), 20 cable management procedure, 41 dimensions, 39 hardware description, 38 illustrations, 39 rack location, 38 B BladeCluster 6700 series hardware requirements, 56 adding a node to the topology, 76 cables, 85 changing the topology, 76 characteristics, 12 checking operations, 70 checking the external fabric for a
BladeCluster/6700 Series topology, 15 BladeCluster/BladeSystem topology, 8-nodes, 13 BladeCluster/Mixed System topology, 8-nodes, 14 BladeCluster/NS16000 topology, 5-nodes, 13 illustration of a four-node BladeCluster/Mixed System topology, 55 illustration of a two-node BladeSystem topology, 47 Expand blank form for recording stopped lines, 91 checking operation of Expand processes and lines, 74 checking the status of line-handler processes, 74 message system traffic, 21 starting Expand-Over-ServerNet Line-H
ServerNet switches before cabling tasks in a multi-zone topology, 45 before cabling tasks in a single-zone topology, 44 cable connections to Advanced Cluster Hubs, 46 dimensions, 44 enclosure location, 43 for BladeCluster, 18 hardware description, 43 ports, 43 service procedure for replacing, 79 ServerNet switches in c7000 BladeCluster, 18 SNETMON, 71 configuring, 87 Software BladeCluster, 20 Software requirements for current release of BladeCluster, 22 Specifications Advanced Cluster Hub (ACH) dimensions,
