Latency While Accessing NetScaler Gateway Page

Latency While Accessing NetScaler Gateway Page

book

Article ID: CTX229253

calendar_today

Updated On:

Description

Latency during opening Gateway page or login page.

Resolution

  • Always take the traces when the traffic is going through NetScaler and bypassing NetScaler going directly to the backend server and compare both and check the time frame and difference between the responses. Capture IP address details.
  • Always try to access the services directly and check if the latency is still there.
  • Try to create TCP profile and verify if that makes any difference 
  • Check relevant counters if there any unusual spikes in any of CPU, PE tight loops, memory, traffic, SSL card activity at that time using nsconmsg and graphs.
  • Check if there is SurgeQ buildup using nsconmsg
      
nsconmsg101 -K newnslog -g  si_cur_surgeCnt -g si_cur_ConnOpenEst -g si_cur_ConnEstablished -s disptime=1 -d current
 
27486       0             4020          171    24 si_cur_ConnOpenEst server_svc_cfg_NSSVC_HTTP_10.65.41.210:9898(searcher186-HTTP_9898tcp) Wed Nov 12 23:44:38 2014
28020       0              680         320       45 si_cur_surgeCnt server_svc_cfg_NSSVC_HTTP_10.65.41.210:9898(searcher186-HTTP_9898tcp) Wed Nov 12 23:44:38 2014
33663       0              3280       142    19 si_cur_ConnEstablished server_svc_cfg_NSSVC_HTTP_10.65.41.210:9898(searcher186-HTTP_9898tcp) Wed Nov 12 23:44:38 2014 \
  • Check if the backend server is overloaded and responding slowly based on response time, SQ buildup from nsconmsg ConLb output
 
nsconmsg101 -K var/nslog/newnslog -s ConLb=2  -s disptime=1 -d oldconmsg
  
VIP(10.65.84.5:80:UP:LEASTCONNS): Hits(428837884, 0/sec) Mbps(0.00) Pers(OFF) Err(0) SO(0) LConn_BestIdx: 0
Pkt(0/sec, 0 bytes) actSvc(47) DefPol(NONE) override(0) newlyUP(0)
Conn: Clt(0, 0/sec, OE[0]) Svr(0) SQ(Total: 0 OnVserver: 0 OnServices: 0)
slimit_SO: (Sothreshhold: 0 [Ex: 0]  Consumed: [Ex: 0 Borrowed: 0 TotActiveConn: 0] Available: 0
   
S(10.65.41.120:9898:UP) Hits(11217655, 0/sec, P[0, 0/sec]) ATr(0:0) Mbps(0.90) BWlmt(0 kbits) RspTime(1233.55 ms)        Load(0) LConn_Idx: (C:0; V:0,I:1)
           
Other: Pkt(96/sec, 1055 bytes) Wt(1) Wt(Reverse Polarity)(10000)
Conn: CSvr(6, 1/sec) MCSvr(0) OE(3980) E(2800) RP(2) SQ(1020)
slimit_maxClient: (MaxClt: 0 [Ex: 0]  Consumed: [Ex: 0 Borrowed: 0 TotActiveConn: 2] Available: 0)
newlyUP_mode: NO, Pending: 0, update: 0x0, incr_time: 0x0, incr_count: 0
  • Check for TCP profile settings and TCP latency related counters
  • Check offline analysis output for any high latency counters
  • Analyze the nstrace capture to find latency on the client as well on server side based on RTT, packet loss, retransmissions, congestion etc
  • Check for packet discards at NIC Level.