beautypg.com

12 managing a servernet cluster, Bladecluster solution, Locating and viewing cluster resources – HP Integrity NonStop J-Series User Manual

Page 261: Bladecluster

background image

12 Managing a ServerNet Cluster

A ServerNet cluster is a collection of NonStop servers connected together using the ServerNet
protocol. There are two generations of ServerNet clusters that utilize cluster switches for ServerNet
cluster connectivity:

The first-generation ServerNet cluster is built around the HP NonStop Cluster Switch (model
6770) and can support up to 24 nodes. It is built using one of the

star topologies

(star, split-star,

or tri-star).

For information about ServerNet clusters built with the star topologies, see the ServerNet
Cluster Manual
, the ServerNet Cluster 6770 Hardware Installation and Support Guide, and
the ServerNet Cluster Supplement for NS-Series Servers.

The second-generation ServerNet cluster is built around the HP NonStop ServerNet Switch
(model 6780) and can support up to 64 nodes. It is built using a

layered topology

.

For information about ServerNet clusters built with the layered topology, see the ServerNet
Cluster 6780 Planning and Installation Guide
, the ServerNet Cluster 6780 Operations Guide,
and the ServerNet Cluster Supplement for NS-Series Servers.

HP NonStop

BladeCluster Solution

offers a topology, for NonStop BladeSystems and NS16000

series servers only, that requires no additional cluster switches for ServerNet cluster connectivity.

Using the OSM Service Connection, you can monitor and maintain the ServerNet cluster resources.
The hardware resources in a cluster differ depending on the topology of the ServerNet cluster. For
details about the resources that make up each type of ServerNet cluster, see

Cluster Resources

.

BladeCluster Solution

A clustering topology for HP Integrity NonStop BladeSystems and Integrity NonStop NS16000
series servers only that provides connectivity directly through the ServerNet switches in the Blade
enclosure or P-switches, without the need for additional cluster switches.

To configure a system as a member of a BladeCluster, use the

Add Node to ServerNet Cluster

action, located under the System object. Once configured through the guided procedure, the OSM
Service Connection displays a

BladeCluster

object in the tree pane (instead of a ServerNet Cluster

object, as with other ServerNet Cluster topologies), at the same level as the System object. Under
the BladeCluster object, OSM displays a

Node

object for every member of the BladeCluster. The

system to which the OSM session is logged on is represented by a Local Node object; all other
member systems are represented by a Remote Node object.

For H06.23/J06.12 and later, BladeCluster enhancements include support for additional long
distance options of 50 kilometers and 65 kilometers maximum between zones in a BladeCluster
topology. For more information, see the BladeCluster Solution Manual.

Locating and Viewing Cluster Resources

To locate resources in a ServerNet cluster, expand the ServerNet Cluster resource in the tree pane
to see the resources and connections in the cluster.

To view more information about a particular resource:

1.

In the tree pane, select the resource.

2.

In the details pane:

Click the Attributes tab to see attributes for the resource.

Click the Alarms tab to see if there are alarms for the resource.

In the View drop-down list, you can select different views of the ServerNet cluster:

The Physical view depicts the connections and resources within the ServerNet cluster.

The Inventory view lists the ServerNet cluster resources in tabular format.

BladeCluster Solution

261

This manual is related to the following products: