VMware VC-VLM4-C User Guide - Page 58

Allow Out, Block In and Out,

Page 58 highlights

Lab Manager User's Guide  Allow Out - Virtual machines in a fenced configuration can initiate communication with machines outside the fence and can receive messages back on the same connection. Machines outside the fence cannot initiate communication to virtual machines inside the fenced configuration. This option is useful when virtual machines need to obtain data or execute code outside the fence (such as with Web services or databases) but do not want to receive messages that might disrupt testing. Figure 7-3. Allow Out Fencing Mode ESX Server host VM1 fenced network VR configuration physical network  Block In and Out - Network traffic does not travel across the fence. Virtual machines in a fenced configuration cannot communicate with machines outside of the fence, and machines outside the fence cannot communicate with virtual machines in the fenced configuration. When you deploy a fenced configuration with this option, Lab Manager does not create a virtual router or assign external IP addresses. Figure 7-4. Block In and Out Fencing Mode ESX Server host VM1 fenced network configuration physical network 58 VMware, Inc.

  • 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

Lab Manager User’s Guide
58
VMware, Inc.
Allow Out
– Virtual machines in a fenced configuration can initiate communication with machines
outside the fence and can receive messages back on the same connection. Machines outside the fence
cannot initiate communication to virtual machines inside the fenced configuration.
This option is useful when virtual machines need to obtain data or execute code outside the fence (such as
with Web services or databases) but do not want to receive messages that might disrupt testing.
Figure 7-3.
Allow Out Fencing Mode
Block In and Out
– Network traffic does not travel across the fence. Virtual machines in a fenced
configuration cannot communicate with machines outside of the fence, and machines outside the fence
cannot communicate with virtual machines in the fenced configuration. When you deploy a fenced
configuration with this option, Lab Manager does not create a virtual router or assign external
IP addresses.
Figure 7-4.
Block In and Out Fencing Mode
fenced
network
ESX Server host
configuration
physical network
VM1
VR
fenced
network
configuration
physical network
VM1
ESX Server host