Testing the View Servers
One of the best methods to test and make sure the servers are working is test run the following command from a client machin.
echo -en "GET /view/ HTTP/1.1\r\nHost: example.server.com\r\nConnection: Close\r\n\r\n" | nc 10.133.84.120 80
Success will return the following:
HTTP/1.1 200 OK
cache-control: no-cache
Content-Length: 1268
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: JSESSIONID=16692AA68187DB39E1D5B69F3CBFCD6E; Path=/
Content-Type: text/html;charset=UTF-8
pragma: no-cache
Connection: close
Vary: Accept-Encoding
VMware View Portal
If you are testing against HTTPS (443) servers it’s best to use openssl like this.
openssl s_client -crlf -connect 10.133.84.52:443
Success will return something like this:
CONNECTED(00000003)
depth=0 /O=VMware, Inc./OU=VMware View default certifcate/CN=view5-
con1.view5.tc.f5net.com
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 /O=VMware, Inc./OU=VMware View default certifcate/CN=view5-
con1.view5.tc.f5net.com
verify error:num=21:unable to verify the first certificate
verify return:1
---
Certificate chain
0 s:/O=VMware, Inc./OU=VMware View default certifcate/CN=view5-
con1.view5.tc.f5net.com
i:/O=VMware, Inc./OU=VMware View default certifcate/CN=view5-
con1.view5.tc.f5net.com
---
Once you get this you’ll use the same string we used before.
GET / HTTP/1.1\r\nHost: view.view.tc.f5net.com\r\nConnection: Close\r\n\r\n
Success will return something like this:
HTTP/1.1 200 OK
cache-control: no-cache
Content-Length: 1268
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: JSESSIONID=36941E985BCD22421591BD52FA6CA0BC; Path=/; Secure;
HttpOnly
Content-Type: text/html;charset=UTF-8
pragma: no-cache
VMware View Portal
In the end your monitor would look like this:
GET /view/ HTTP/1.1\r\nHost: HOSTFQDN\r\nConnection: Close\r\n\r\n
and you would expect a response string of
VMware View Portal
Nimbostratus