VMware VLM3-ENG-CP User Guide - Page 173

C-1., Configuration A Without Fencing and Configuration B With Fencing

Page 173 highlights

Appendix C Network Fencing Figure C-1. Configuration A (Without Fencing) and Configuration B (With Fencing) Managed Server system 1 192.10608:5.00.:156:00:00:01 IIPMAC VM1 configuration a Managed Server system 2 192.10608:5.00.:256:00:00:02 192.10608:5.00.:156:00:00:01 192.10608:5.00.:256:00:00:02 IIPMAC IIPMAC IIPMAC VM2 VM1 VM2 fenced network configuration b VR (fenced) client machine legend IIP EIP VR network EIP 192.168.0.4 EIP 192.168.0.3 connection fenced connection internal IP address external IP address for fenced configurations virtual router Fencing a configuration does not require any changes to its virtual machines. Within a fenced configuration, virtual machines continue to use preassigned IP addresses to communicate with each other. For more information on IP address allocation in fenced configurations, see "Understanding IP Address Management" on page 139. VMware, Inc. 173

  • 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.
173
Appendix C
Network Fencing
Figure C-1.
Configuration A (Without Fencing) and Configuration B (With Fencing)
Fencing a configuration does not require any changes to its virtual machines. Within a
fenced configuration, virtual machines continue to use preassigned IP addresses to
communicate with each other. For more information on IP address allocation in fenced
configurations, see
“Understanding IP Address Management”
on page 139.
fenced
network
Managed Server system 2
Managed Server system 1
client machine
configuration a
configuration b
(fenced)
network
legend
connection
fenced connection
IIP
internal IP address
EIP
external IP address for fenced configurations
VR
virtual router
EIP
192.168.0.4
EIP
192.168.0.3
IIP
192.168.0.1
MAC
00:50:56:00:00:01
IIP
192.168.0.2
MAC
00:50:56:00:00:02
VM1
VM2
IIP
192.168.0.1
MAC
00:50:56:00:00:01
IIP
192.168.0.2
MAC
00:50:56:00:00:02
VM1
VM2
VR