Troubleshooting web browsing performance issue can be very time-consuming because it can be affected by several factors, such as DNS, web server performance, URL Rating server connection, and LDAP query.
The connectivity test tool helps the IWSVA administrators to easily identify the areas that take a long time to produce results, or the areas where failures are encountered.
To use the Connectivity Test tool:
- Log in to IWSVA shell as root.
- Go to the usr/iwss/connectivity_test directory and execute the following command:
./connectivitytest.sh
This command produces output like below:
=============== DNS Server Connectivity Test ===============
From ('10.13.9.215', 53)
CNAME: www3.l.google.com
IP: 209.85.148.100
IP: 209.85.148.101
IP: 209.85.148.102
IP: 209.85.148.113
IP: 209.85.148.138
IP: 209.85.148.139
Time : 2 ms
From ('145.253.2.11', 53)
CNAME: www3.l.google.com
IP: 209.85.148.113
IP: 209.85.148.138
IP: 209.85.148.139
IP: 209.85.148.100
IP: 209.85.148.101
IP: 209.85.148.102
Time : 28 ms
=============== URL Query Test ===============
URL: http://www.google.com/
Version: 11
Reason: Found
Status: 302
Time : 41 ms
URL: http://www.google.com/
Version: 11
Reason: Found
Status: 302
Time : 66 ms
=============== TMUFE Server Connectivity Test ===============
The URL is : http://www.google.com/
The rating WRS score is : 81
Time : 381 ms
The URL is : http://www.google.com
The rating WRS score is : 81
Time : 44 ms
=============== LDAP Server Connectivity Test ===============
kinit(v5): Cannot resolve network address for KDC in realm EUCT.LOCAL while getting initial credentials
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Local error (-2)
additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Unknown code krb5 195)
Time : 9 ms
=============== Done ================