Cneonction and nnCoection in HTTP Response Headers

You may receive Cneonction or nnCoection HTTP Reponse Header even if you are not using Keep-Alive on you member servers. Some loadbalancers rewrites http response headers.So you can see
nnCoection : Close
instead of
Connection : Close
Your WebServer is returning the response header Connection: close but loadbalancer rewrites it to nnCoection: close because you have keep-alive enabled on your loadbalancer and the loadbalancer want to keep connection so it replaces Connection header.

The case I met on Netscaler MPX appliance, you should disable Client Keep Alive on your service or Service Group. So, LB will never send Connection response to clients.
Otherwise, you have to rewrite nnCoection ..
nncoection

Netscaler VIP Realtime traffic usage

I googled everywhere, checked documents and cant reach any information how to measure how much traffic is passing through loadbalancer individual VIPs.

So my solutions is to measure RX/TX bytes/s via SNMP. To accomplish it follow the steps below.

Requirement
An SNMP browser ( I used Ireasoning MIB Browser )
Netscaler SNMPv2 MIBs ( you may download it from your Netscaler appliance )

I assume that your appliance SNMP enabled and functioning normally.

Load the MIB you downloaded from netscaler and enter the SNMP settings. Navigate to nsVserverGroup with MIB browser and send SNMP walk.

mib

You have get the names starting with vsvrName on the left side. Select your favorite VIP :)

Now lets take the first line in out example. Full OID will be like below

.1.3.6.1.4.1.5951.4.1.3.1.1.1.5.67.101.98.105.116

so crop the vsvrName part and you will have you unique OID for your VIP

.1.3.6.1.4.1.5951.4.1.3.1.1.1.    5.67.101.98.105.116 < this is out VIP

Now, we have to put RX or TX rate OID in front of 5.67.101.98.105.116
. Let’s find the RX

check the list below and find the lines starting with vsvrRxBytesRate. You may check any value you want because we want to learn what OID is representing vsvrRxBytesRate

mib2

so as you can see .1.3.6.1.4.1.5951.4.1.3.1.1.44.16.79.68.67.95.65.112.112.95.83.77.84.80.95.49.48.49 is whole OID and .1.3.6.1.4.1.5951.4.1.3.1.1.44. is representing the vsvrRxBytesRate

Now if you combine both OID you will get the RX bytes/s of that VIP. But this is not a gauge, it is a value.. It may not as good as traffic counter but the best you can do is that :)

.1.3.6.1.4.1.5951.4.1.3.1.1.44.5.67.101.98.105.116

After you had the value multiply with 8 to get the bits value and divide it to 1024 to get kbits/s..

Also there are lots of other OID pick as you want using this method.