Seen a few emails flying around the other day about how to add a remote Syslog server to the vCD cell once it has been installed. This has caught out a few people in the past couple of months. Follow the documentation and edit the syslog section in /opt/vmware/cloud-director/etc/responses.properties then re-run the configuration. Add your Syslog server to the audit.syslog.host line in /opt/vmware/cloud-director/etc/global.properties Restart the vCD Cell [service vmware-vcd restart] This will then configure vCD for using a remote syslog server. Please note: This is only required if you have an already installed or pre-configured vCD cell. For all fresh installations follow the guidelines in the installation guide.
Tag Archives | VMware Posts
An interesting topic came up the other day between some of us in the cloud team, regarding whether Ephemeral Ports should be continued to be used with vCD deployments. A colleague of mine Aidan Dalgleish (Senior Consultant, VMware TS Cloud Practice) kindly documented our discussions and wrote up the decisions. He can be found on LinkedIn. Background The topic of Portgroup binding was discussed and Ephemeral binding was selected as the preferred option for vCD created Portgroups for some of the following reasons: * Due to the dynamic nature of vCloud Director it is often difficult to define how many devices will be connected to a given Portgroup * Easy to code as there is no requirement to monitor and dynamically adjust the number of ports configured on the Portgroup as with Static/Dynamic * Very flexible due to their being no requirement to define a number of ports and hence […]
Last week a customer asked the question why the VMware HCL listed products that are certified with one version update but not the other. For example, the HCL shows HP BL620c G7 lists on ESXi4U2 but NOT ESXi4U1. The HCL Small Print: The detailed lists show actual vendor devices that are either physically tested or are similar to the devices tested by VMware or VMware partners. VMware provides support only for the devices that are listed in this document. What this translates to in the real world is that often the HCL exposes the time aspect of updating compatibility. If the server was released after a version of vSphere then it will not be listed for the previous versions, even though it may perform correctly.