HP 1032 ClusterPack V2.4 Tutorial - Page 34

Background, clnetworks, Overview, Details

Page 34 highlights

Background This tool is the driver that installs and configures appropriate components on every Compute Node. z Registers Compute Nodes with HP Systems Insight Manager or SCM on the Management Server. z Pushes agent components to all Compute Nodes. z Sets up each Compute Node as NTP client, NIS client, and NFS client. z Starts necessary agents in each of the Compute Nodes. z Modifies configuration files on all Compute Nodes to enable auto-startup of agents after reboots. z Allows for the configuration of additional networks with clnetworks z Prints a PASS diagnostic message if all configuration steps are successful. clnetworks Each Compute Node is known to the Management Server through the IP address and specified to manager_config. These interfaces are collectively known as the Cluster Network. This term can be somewhat confusing when a cluster consists of both private nodes and public nodes. This is possible, for example, when an initial set of Compute Nodes is created on a private network and then additional nodes outside the private network are added using -a. The IP address of each Compute Node known by the Management Server makes up the Cluster Network. ClusterPack includes a utility to configure additional networks on all of the Compute Nodes. These networks, like the Cluster Network, refer to a logical collection of interfaces/IP addresses and not to a physical network. However, they must share a common netmask. The concept of a network is defined as: z A name (for reference only) z A subset of the nodes in the cluster z A network interface for each node in the subset z An IP address for each interface z A name extension that is added to the hostname of each machine and associated with each host's interface. z A netmask To define additional networks, use the command clnetworks. This tool is also called from compute_confi clnetworks provides a text-based interface for selecting nodes, network interfaces and IP addresses. It gui the user through the creation of a network. It is also possible to modify an existing network. When you ha finished creating or updating networks, clnetworks will ensure that each interface specified is configured correctly and ensure the proper entries in each host's /etc/hosts file. Overview The compute_config program will register the nodes with various programs. Details

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173

Background
This tool is the driver that installs and configures appropriate components on every Compute Node.
Registers Compute Nodes with HP Systems Insight Manager or SCM on the Management
Server.
Pushes agent components to all Compute Nodes.
Sets up each Compute Node as NTP client, NIS client, and NFS client.
Starts necessary agents in each of the Compute Nodes.
Modifies configuration files on all Compute Nodes to enable auto-startup of agents after
reboots.
Allows for the configuration of additional networks with clnetworks
Prints a PASS diagnostic message if all configuration steps are successful.
clnetworks
Each Compute Node is known to the Management Server through the IP address and specified to
manager_config. These interfaces are collectively known as the Cluster Network. This term can be
somewhat confusing when a cluster consists of both private nodes and public nodes. This is possible, for
example, when an initial set of Compute Nodes is created on a private network and then additional nodes
outside the private network are added using -a. The IP address of each Compute Node known by the
Management Server makes up the Cluster Network.
ClusterPack includes a utility to configure additional networks on all of the Compute Nodes. These
networks, like the Cluster Network, refer to a logical collection of interfaces/IP addresses and not to a
physical network. However, they must share a common netmask. The concept of a network is defined as:
A name (for reference only)
A subset of the nodes in the cluster
A network interface for each node in the subset
An IP address for each interface
A name extension that is added to the hostname of each machine and associated with each
host's interface.
A netmask
To define additional networks, use the command clnetworks. This tool is also called from compute_confi
clnetworks provides a text-based interface for selecting nodes, network interfaces and IP addresses. It gui
the user through the creation of a network. It is also possible to modify an existing network. When you ha
finished creating or updating networks, clnetworks will ensure that each interface specified is configured
correctly and ensure the proper entries in each host's /etc/hosts file.
Overview
The compute_config program will register the nodes with various programs.
Details