VMware VLM3-ENG-CP User Guide - Page 177

Reviewing Additional Fencing Operations, To change the switch for fencing

Page 177 highlights

Appendix C Network Fencing CAUTION Do not connect the virtual switches that Lab Manager creates to an external network. Lab Manager needs these virtual switches for deploying fenced configurations. Reviewing Additional Fencing Operations If you need to view current fencing options or change the switch that Lab Manager uses for fencing, follow these instructions (instead of uninstalling and reinstalling the Managed Server agent software). For more information on switches, see the VMware Infrastructure 3 documentation. NOTE Undeploy the virtual machines before changing the switch for fencing or adjusting the number of fences. To change the switch for fencing 1 Log in as root. 2 From the command line, type: > lm-fencecfg 3 Select a different network switch for virtual machines. To view current fencing options 1 Log in as root. 2 From the command line, type: > cat /etc/labmanager/agentconf.xml The HostNic field contains the bridge device and the VNetCount field contains the number of fences. To adjust the number of fences 1 Log in as root. 2 From the command line, change the number of fences. Usage: > lm-fencecfg --numFenced NUM_FENCES For example, update the number of fences to 30: > lm-fencecfg --numFenced 30 VMware, Inc. 177

  • 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
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

VMware, Inc.
177
Appendix C
Network Fencing
Reviewing Additional Fencing Operations
If you need to view current fencing options or change the switch that Lab Manager uses
for fencing, follow these instructions (instead of uninstalling and reinstalling the
Managed Server agent software).
For more information on switches, see the VMware Infrastructure 3 documentation.
To change the switch for fencing
1
Log in as root.
2
From the command line, type:
>
lm-fencecfg
3
Select a different network switch for virtual machines.
To view current fencing options
1
Log in as root.
2
From the command line, type:
>
cat /etc/labmanager/agentconf.xml
The
HostNic
field contains the bridge device and the
VNetCount
field contains the
number of fences.
To adjust the number of fences
1
Log in as root.
2
From the command line, change the number of fences. Usage:
>
lm-fencecfg --numFenced NUM_FENCES
For example, update the number of fences to 30:
>
lm-fencecfg --numFenced 30
C
AUTION
Do not connect the virtual switches that Lab Manager creates to an
external network. Lab Manager needs these virtual switches for
deploying fenced configurations.
N
OTE
Undeploy the virtual machines before changing the switch for fencing or
adjusting the number of fences.