VMware VLM3-ENG-CP User Guide - Page 176

Processor Type Incompatibility, Viewing Virtual Switches for Fences

Get VMware VLM3-ENG-CP - Lab Manager - PC PDF manuals and user guides View all VMware VLM3-ENG-CP manuals
Add to My Manuals
Save this manual to your list of manuals

Page 176 highlights

VMware® Lab Manager User's Guide This option is useful in these circumstances: „ You are testing software viruses that need to remain isolated from the network. „ You are testing a client‐server application in isolation. Processor Type Incompatibility Deploying a configuration in fenced mode hosts all the virtual machines on a single Managed Server system. You must have a Managed Server system connected to the storage server where the templates that serve as the basis of this configuration reside on. The Managed Server system must have sufficient resources, such as memory, slots, and fences. If you deploy a configuration, perform an operation which saves the state of the configuration (for example, suspend or capture to library), and redeploy the configuration with fencing (which requires hosting all virtual machines on the same physical machine), a situation could come up where the only Managed Server systems available are ones with incompatible processor types. The captured memory expects a particular processor type. To address this situation, deploy the configuration without fencing, undeploy it without saving the memory state (use the Turn Off deployment setting in the User Preferences page or the Undeploy ‐ Discard State mouseover menu), and redeploy the configuration. If deploying a configuration without fencing is not an option, reset the MAC address of each virtual machine to remove the saved state, and redeploy the configuration. See "Changing IP or MAC Addresses" on page 34. Viewing Virtual Switches for Fences You can use the VI Client in the ESX Server system to see the "LMNetwork" virtual switches or networks that Lab Manager creates for each fence. To view virtual switches for fences 1 Navigate to the Configuration tab of the VI Client. 2 Click the Networking link in the Hardware list to view virtual switches (for example, "LMNetwork001"). See the VMware Infrastructure 3 documentation for details on using VI Client. 176 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
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
VMware® Lab Manager User’s Guide
176
VMware, Inc.
This option is useful in these circumstances:
You are testing software viruses that need to remain isolated from the
network.
You are testing a client
‐
server application in isolation.
Processor Type Incompatibility
Deploying a configuration in fenced mode hosts all the virtual machines on a single
Managed Server system. You must have a Managed Server system connected to the
storage server where the templates that serve as the basis of this configuration reside
on. The Managed Server system must have sufficient resources, such as memory, slots,
and fences.
If you deploy a configuration, perform an operation which saves the state of the
configuration (for example, suspend or capture to library), and redeploy the
configuration with fencing (which requires hosting all virtual machines on the same
physical machine), a situation could come up where the only Managed Server systems
available are ones with incompatible processor types. The captured memory expects a
particular processor type.
To address this situation, deploy the configuration without fencing, undeploy it
without saving the memory state (use the
Turn Off
deployment setting in the User
Preferences page or the
Undeploy
‐
Discard State
mouseover menu), and redeploy the
configuration.
If deploying a configuration without fencing is not an option, reset the MAC address of
each virtual machine to remove the saved state, and redeploy the configuration. See
“Changing IP or MAC Addresses”
on page 34.
Viewing Virtual Switches for Fences
You can use the VI Client in the ESX Server system to see the “LMNetwork<n>” virtual
switches or networks that Lab Manager creates for each fence.
To view virtual switches for fences
1
Navigate to the
Configuration
tab of the VI Client.
2
Click the
Networking
link in the
Hardware
list to view virtual switches (for
example, “LMNetwork001”).
See the VMware Infrastructure 3 documentation for details on using VI Client.