VMware VS4-ENT-PL-A Setup Guide - Page 23

Providing Sufficient Space for System Logging, Required Ports for vCenter Server - client windows 8

Page 23 highlights

Chapter 2 System Requirements Providing Sufficient Space for System Logging ESXi 5.x uses a new log infrastructure. If your host is deployed with Auto Deploy, or if you set up a log directory separate from the default location in a scratch directory on the VMFS volume, you might need to change your current log size and rotation settings to ensure that enough space for system logging exists. All vSphere components use this infrastructure. The default values for log capacity in this infrastructure vary, depending on the amount of storage available and on how you have configured system logging. Hosts that are deployed with Auto Deploy store logs on a RAM disk, which means that the amount of space available for logs is small. If your host is deployed with Auto Deploy, reconfigure your log storage in one of the following ways: n Redirect logs over the network to a remote collector. n Redirect logs to a NAS or NFS store. You might also want to reconfigure log sizing and rotations for hosts that are installed to disk, if you redirect logs to nondefault storage, such as a NAS or NFS store. You do not need to reconfigure log storage for ESXi hosts that use the default configuration, which stores logs in a scratch directory on the VMFS volume. For these hosts, ESXi 5.x autoconfigures logs to best suit your installation, and provides enough space to accommodate log messages. Table 2‑11. Recommended Minimum Size and Rotation Configuration for hostd, vpxa, and fdm Logs. Number of Rotations to Log Maximum Log File Size Preserve Minimum Disk Space Required Management Agent 10240KB 10 (hostd) VirtualCenter Agent 5120KB 10 (vpxa) vSphere HA agent (Fault 5120KB 10 Domain Manager, fdm) 100MB 50MB 50MB For information about setting up a remote log server, see "Configure Syslog on ESXi Hosts," on page 262 and "Install or Upgrade vSphere Syslog Collector," on page 108. Required Ports for vCenter Server The VMware vCenter Server system must be able to send data to every managed host and receive data from every vSphere Web Client. To enable migration and provisioning activities between managed hosts, the source and destination hosts must be able to receive data from each other. For information about ports required for the vCenter Server Appliance, see "Required Ports for the vCenter Server Appliance," on page 25. VMware uses designated ports for communication. Additionally, the managed hosts monitor designated ports for data from the vCenter Server system. If a firewall exists between any of these elements and Windows firewall service is in use, the installer opens the ports during the installation. For custom firewalls, you must manually open the required ports. If you have a firewall between two managed hosts and you want to perform source or target activities, such as migration or cloning, you must configure a means for the managed hosts to receive data. NOTE In Microsoft Windows Server 2008, a firewall is enabled by default. VMware, Inc. 23

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276

Providing Sufficient Space for System Logging
ESXi 5.x uses a new log infrastructure. If your host is deployed with Auto Deploy, or if you set up a log
directory separate from the default location in a scratch directory on the VMFS volume, you might need to
change your current log size and rotation settings to ensure that enough space for system logging exists.
All vSphere components use this infrastructure. The default values for log capacity in this infrastructure
vary, depending on the amount of storage available and on how you have configured system logging. Hosts
that are deployed with Auto Deploy store logs on a RAM disk, which means that the amount of space
available for logs is small.
If your host is deployed with Auto Deploy, reconfigure your log storage in one of the following ways:
n
Redirect logs over the network to a remote collector.
n
Redirect logs to a NAS or NFS store.
You might also want to reconfigure log sizing and rotations for hosts that are installed to disk, if you
redirect logs to nondefault storage, such as a NAS or NFS store.
You do not need to reconfigure log storage for ESXi hosts that use the default configuration, which stores
logs in a scratch directory on the VMFS volume. For these hosts, ESXi 5.x autoconfigures logs to best suit
your installation, and provides enough space to accommodate log messages.
Table 2
11.
Recommended Minimum Size and Rotation Configuration for hostd, vpxa, and fdm Logs.
Log
Maximum Log File Size
Number of Rotations to
Preserve
Minimum Disk Space Required
Management Agent
(hostd)
10240KB
10
100MB
VirtualCenter Agent
(vpxa)
5120KB
10
50MB
vSphere HA agent (Fault
Domain Manager, fdm)
5120KB
10
50MB
For information about setting up a remote log server, see
“Configure Syslog on ESXi Hosts,”
on page 262
and
“Install or Upgrade vSphere Syslog Collector,”
on page 108.
Required Ports for vCenter Server
The VMware vCenter Server system must be able to send data to every managed host and receive data from
every vSphere Web Client. To enable migration and provisioning activities between managed hosts, the
source and destination hosts must be able to receive data from each other.
For information about ports required for the vCenter Server Appliance, see
“Required Ports for the vCenter
Server Appliance,”
on page 25.
VMware uses designated ports for communication. Additionally, the managed hosts monitor designated
ports for data from the vCenter Server system. If a firewall exists between any of these elements and
Windows firewall service is in use, the installer opens the ports during the installation. For custom firewalls,
you must manually open the required ports. If you have a firewall between two managed hosts and you
want to perform source or target activities, such as migration or cloning, you must configure a means for the
managed hosts to receive data.
N
OTE
In Microsoft Windows Server 2008, a firewall is enabled by default.
Chapter 2 System Requirements
VMware, Inc.
23