HP 2128-F ClusterPack V2.4 Tutorial - Page 161

How do I access the Clusterware Pro V5.1 Command Line Interface?

Page 161 highlights

z The username and password are the same as for any normal user account on the Management Server. References: z 3.7.6 How do I start and stop the Clusterware Pro V5.1 Web GUI? Back to Top 3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface? Before using the Clusterware Pro V5.1 CLI, you must set a number of environment variables. This must b done once in each shell before using any of the Clusterware Pro V5.1 commands. z For users of csh or tcsh % source /share/platform/clusterware/conf/cshrc.lsf z For users of sh or bash or ksh % . /share/platform/clusterware/conf/profile.lsf Back to Top 3.7.10 How can the Clusterware Pro V5.1 services be refreshed after changes to the configuration are made? The services only read the configuration file when they are started up or reconfigured. Any time a change made to the configuration, the services must either be restarted or reconfigured. Changes include, but are limited to: z adding or removing queues z changing existing queues z adding or removing nodes z reinstalling software (i.e. manager_config -F) Reconfiguring the Clusterware Pro V5.1 Services The Clusterware Pro V5.1 services can be reconfigured without stopping the daemons. This must be done the super user (i.e. root) and you must be able to run the 'rsh' command without providing a password. Th f" flag will force a reconfiguration, unless there are fatal errors. When reconfiguring the cluster, order is important: % lsadmin reconfig -f

  • 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

The username and password are the same as for any normal user account on the
Management Server.
References:
3.7.6 How do I start and stop the Clusterware Pro V5.1 Web GUI?
Back to Top
3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface?
Before using the Clusterware Pro V5.1 CLI, you must set a number of environment variables. This must b
done once in each shell before using any of the Clusterware Pro V5.1 commands.
For users of csh or tcsh
%
source /share/platform/clusterware/conf/cshrc.lsf
For users of sh or bash or ksh
%
. /share/platform/clusterware/conf/profile.lsf
Back to Top
3.7.10 How can the Clusterware Pro V5.1 services be refreshed after changes to the
configuration are made?
The services only read the configuration file when they are started up or reconfigured. Any time a change
made to the configuration, the services must either be restarted or reconfigured. Changes include, but are
limited to:
adding or removing queues
changing existing queues
adding or removing nodes
reinstalling software (i.e. manager_config -F)
Reconfiguring the Clusterware Pro V5.1 Services
The Clusterware Pro V5.1 services can be reconfigured without stopping the daemons. This must be done
the super user (i.e. root) and you must be able to run the 'rsh' command without providing a password. Th
f" flag will force a reconfiguration, unless there are fatal errors. When reconfiguring the cluster, order is
important:
%
lsadmin reconfig -f