How to see which NetScaler VIP is consuming your bandwidth
When you see throughput peaks on your NetScaler (Citrix ADC), the key question is simple: which virtual server (VIP) is generating the load?
Whether you are troubleshooting spikes, investigating potential abuse, or analysing long‑term usage trends, nsconmsg and the newnslog files give you precise historical and real‑time visibility at VIP level.
Step 1 – Find the right newnslog file
If you want to analyse historical throughput for a specific date and time, start by locating the correct newnslog file for that period.
root@ns# cd /var/nslog
root@ns# ls -lh
Identify the newnslog archive that matches the day and time you want to investigate, for example newnslog.88.tar.gz.
In this example, we want to investigate peaks on 06.11 at 11:15:42, so newnslog.88.tar.gz is the relevant file. This is what the example would look like (output shortened):
-rw-r--r-- 1 root wheel 23605923 Oct 18 16:46 newnslog.63.tar.gz
-rw-r--r-- 1 root wheel 22303719 Oct 19 11:46 newnslog.64.tar.gz
...
-rw-r--r-- 1 root wheel 20296679 Nov 6 07:46 newnslog.87.tar.gz
-rw-r--r-- 1 root wheel 24487432 Nov 7 00:46 newnslog.88.tar.gz
-rw-r--r-- 1 root wheel 24319876 Nov 7 19:46 newnslog.89.tar.gz
...
-rw-r--r-- 1 root wheel 19579009 Nov 11 16:46 newnslog.94.tar.gz
Step 2 – Check for throughput peaks
To check if throughput exceeded a specific threshold (for example 90 Mbps), run:
root@ns# nsconmsg -K newnslog.88.tar.gz -g mbits -d past -s disptime=1 -s ratecount=90 | more
newnslog.88/
newnslog.88/newnslog.ppe.0
Displaying performance information
NetScaler V20 Performance Data
NetScaler NS13.1: Build 49.15.nc, Date: Sep 20 2023, 23:22:03 (64-bit)
reltime: milliseconds between two records Mon Nov 6 11:15:42 2023
Index rtime totalcount-val delta rate/sec symbol-name&device-no&time
0 7010 8948176 1455 207 allnic_tot_rx_mbits Mon Nov 6 11:15:42 2023
1 0 9564174 1460 208 allnic_tot_tx_mbits Mon Nov 6 11:15:42 2023
2 0 8948176 1455 207 nic_tot_rx_mbits interface(0/1) Mon Nov 6 11:15:42 2023
3 0 9564174 1460 208 nic_tot_tx_mbits interface(0/1) Mon Nov 6 11:15:42 2023
...
12 7010 9162442 668 95 allnic_tot_rx_mbits Mon Nov 6 21:02:40 2023
13 0 9796649 667 95 allnic_tot_tx_mbits Mon Nov 6 21:02:40 2023
14 0 9162442 668 95 nic_tot_rx_mbits interface(0/1) Mon Nov 6 21:02:40 2023
15 0 9796649 667 95 nic_tot_tx_mbits interface(0/1) Mon Nov 6 21:02:40 2023
If you are running a VPX 1000 with a normal baseline around 500 Mbps, you might increase the threshold instead:
root@ns# nsconmsg -K newnslog.88.tar.gz -g mbits -d past -s disptime=1 -s ratecount=550 | more
This lets you detect meaningful spikes relative to your environment (output shortened above).
The output shows timestamps where total throughput exceeded the threshold.
What the parameters do
-K newnslog.88.tar.gz– read from the selected log archive.-g mbits– display throughput in Mbps.-d past– analyse historical data.-s disptime=1– include timestamps.-s ratecount=90– only show entries above 90 Mbps.
Step 3 – Identify which VIP consumed the traffic
Once you know the exact time of the spike, the next step is to find which VIP (or backend service) is responsible. To do this use:
root@ns# nsconmsg -K /var/nslog/newnslog.88 -s ConLb=3 -d oldconmsg -s time=06Nov2023:11:15:42 | more
...
VIP(192.0.2.50:443:UP:LEASTCONNS): Hits(66711, 0/sec) PHits(0) Mbps(200.77) Pers(OFF) Err(0) SO(0) LConn_Best
Pkt(20412/sec, 1149 bytes) actSvc(1) DefPol(NONE) override(0) newlyUP(0)
Conn: Clt(3, 0/sec, OE[3]) Svr(3) SQ(Total: 0) OnVserver: 0 OnServices: 0)
slimit_SO: (Sothreshold: 0 [Ex: 0] Consumed: [Ex: 0 Borrowed: 0 TotActiveConn: 3] Available: 0)
S(192.0.2.60:8080:UP) Hits(66711, 0/sec, P[0, 0/sec]) ATr(3:3) Mbps(209.94) BWlmt(0 kbits) RspTime(0.00 ms) Load(0)
...
Output shortened: in this capture the virtual server itself was running at 200.77 Mbps, with its backend service reporting 209.94 Mbps for the same interval.
Explanation
-s ConLb=3– show load‑balancing virtual server statistics.-d oldconmsg– dump historical connection messages.-s time=...– filter on the exact timestamp of the spike.
The output includes:
- VIP name.
- Backend services.
- Throughput in Mbps.
- Connections per second.
- Response times.
You now have a clear view of which virtual server was driving the load at that moment.
Step 4 – Filter VIPs by traffic range with grep
In busy environments, there may be many VIPs in the output.
You can narrow down the list by filtering on a throughput range using grep.
Example – show VIPs between 100.00 and 999.99 Mbps:
root@ns# nsconmsg -K /var/nslog/newnslog.88 -s ConLb=3 -d oldconmsg | grep "Mbps([0-9][0-9][0-9].[0-9][0-9])"
This regex returns VIPs with throughput between 100 and 999 Mbps.
Step 5 – Use the current log instead of an archive
To analyse the active newnslog instead of an archived file, drop the archive path and filter the ConLb output directly — for example between 10.00 and 99.99 Mbps:
root@ns# nsconmsg -K /var/nslog/newnslog -s ConLb=3 -d oldconmsg | grep "Mbps([0-9][0-9].[0-9][0-9])"
Adjust the [0-9] expressions in the pattern to match the range you care about, for example two or three digits before the decimal.
Step 6 – Search for a specific throughput value
Sometimes monitoring tools give you an exact Mbps value from an alert (for example 161.47 Mbps).
You can search directly for that value in the ConLb output:
root@ns# nsconmsg -K /var/nslog/newnslog -s ConLb=3 -d oldconmsg | grep "Mbps(161.47)"
S(192.0.2.17:8080:UP) Hits(38163816, 12/sec, P[38110108, 12/sec]) ATr(118:118) Mbps(161.47) BWlmt(0 kbits) RspTime(59.31 ms) Load(0) LConn_Idx: (C:0; V:0,I:1, B:0, X:118, SI:0)
This makes it easy to correlate NetScaler logs with external monitoring alerts that report specific values or security events.
Step 7 – What to do once you know the VIP
After identifying the virtual server responsible for the spike:
- Validate whether the traffic is expected (backup jobs, batch processes, maintenance windows).
- Check backend service health and performance.
- Look for unusual connection patterns or sudden growth in client IPs.
- Validate against security monitoring tools: Cross‑check with your security monitoring and WAF logs.
- Investigate potential DDoS, scraping or abusive behaviour if the pattern looks suspicious.
Why this method works so well
Using nsconmsg with newnslog archives gives you precise, timestamped visibility into historical NetScaler throughput and VIP‑level consumption.
With a few targeted commands you can:
- Detect and confirm traffic spikes.
- Pinpoint exactly which VIP generated the load.
- Filter by throughput ranges or specific Mbps values.
- Quickly distinguish between normal high‑load events and potential performance or security incidents.
For busy Citrix ADC / NetScaler environments, this approach is fast, reliable and invaluable when you are troubleshooting performance or security incidents on NetScaler environments.
Need more expert advice? Book a meeting with one of our experts.
