
;; cert (the first 4 bytes of the MD5 hash in least significant byte order).
;; The hash can be obtained with the command: openssl x509 -noout -in cert.pem
-hash
CApath = C:\Program Files (x86)\VMware\VCM\Tools\sTunnel\certs
;; Some debugging stuff useful for troubleshooting
;debug = 7
;output = stunnel.log
;; verify = level
;; level 1 - verify peer certificate if present
;; level 2 - verify peer certificate
;; level 3 - verify peer with locally installed certificate
;; default - no verify
verify = 3
;; limit connections to certain ciphers
ciphers = AES128-SHA:DES-CBC3-SHA :@STRENGTH
;; asm_hostname_or_ip_address must be replaced with the correct value for the
OS Provisioning Server
[fsrepo]
accept = 127.0.0.1:21307
connect = asm_hostname_or_ip_address:40607
4. Update the accept and connect values in the [fsrepo] section.
Value Action
accept = 21307
Update to accept = 127.0.0.1:21307
connect = asm_hostname_or_ip_
address:40607
Update to the hostname or the IP address of the OS
Provisioning Server
5. Run the commands from the Stunnel directory to register and start the Stunnel service.
cd c:\Program Files (x86)\VMware\VCM\Tools\sTunnel
stunnel –install
net start stunnel
What to do next
Verify that the communication between the OS Provisioning server and the VCMCollector is properly
configured. See "Confirm Stunnel Configuration" on page 42.
Confirm Stunnel Configuration
You must confirm that Stunnel communication between the OS Provisioning server and the VCM
Collector is configured and active before provisioning machines.
vCenter Configuration Manager Installation and Getting Started Guide
42 VMware, Inc.
Commenti su questo manuale