Jump to content
Welcome to our new Citrix community!

Monitor Probes failed, how to investigate failure reason


Raza Mir

Recommended Posts

Hi,

 

I am new to NetScaler. I have setup a CUSTOMLOAD monitor to monitor the server CPU.

I am getting Prob fails as below. Server is configured with correct Community, I like to know the exact reason that why SNMP monitor is failing.  Please advise how I can findout the failure reason.

e.g. is loadbalancer able to talk with server via snmp or not, or some other specific reason.

Same SNMP monitor is working for other servers.

 

show servicegroup ServiceGroupName-1

'#'#'#'#'#'

1) Monitor Name: tcp-vlan100  State: ENABLED  Weight: 1       Passive: 0
 2) Monitor Name: Prob-CPU    State: ENABLED  Weight: 1       Passive: 0


        1)    10.10.10.x:80       State: UP       Server Name: Serv1  Server ID: None Weight: 1
                Last state change was at Wed Apr 29 10:00:36 2020
                Time since last state change: 0 days, 02:59:28.710

                Monitor Name: tcp-vlan100        State: UP       Passive: 0
                Probes: 235481  Failed [Total: 959 Current: 0]
                Last response: Success - TCP syn+ack received.
                Response Time: 2000 millisec
                Monitor Name: Prob-CPU       State: DOWN     Passive: 0
                Probes: 7760    Failed [Total: 7759 Current: 7759]
                Last response: Failure - Probe failed.
                Response Time: 0 millisec

 

 

LB1> sh monitor Prob-CPU
1)   Name.......:Prob-CPU  Type......:      LOAD State....:   ENABLED        Network profile:A_VLAN100
Standard parameters:
  Interval.........:           15 sec   Retries...........:                3
  Response timeout.:           10 sec   Down time.........:           30 sec
  Reverse..........:               NO   Transparent.......:               NO
  Secure...........:   Not applicable

  LRTM.............:         DISABLED
  Action...........:   Not applicable   Deviation.........:            0 sec
  Destination IP...:    Bound service
  Destination port.:              161
  Iptunnel.........:               NO
  TOS..............:               NO
  SNMP Alert Retries:               0     Success Retries..:                1
  Failure Retries..:                0
Special parameters:
  Community : ABC12345
  Version : V1
  Bound Metric table : local , Prob-CPU

        Prob-CPU Metric Table binding:
                METRICNAME                          Weight     Threshold
                CPU_1                                   10     100

                CPU_2                                   10     100
                CPU_3                                   10     100
                CPU_4                                   10     100
                CPU_5                                   10     100
                CPU_6                                   10     100
 Done
 

 

 

 

Link to comment
Share on other sites

I would do a network trace, on server side to see, if the ADC is able to connect. You could also do a trace on ADC to see, if SNMP replies arrive.

 

It seems like you did everything right, as these monitors worked fine for other servers. I guess, you already know, they use NSIP as a source (not SNIP)

 

Greetings

 

Johannes Norz

Link to comment
Share on other sites

On 4/29/2020 at 3:46 PM, Johannes Norz said:

I would do a network trace, on server side to see, if the ADC is able to connect. You could also do a trace on ADC to see, if SNMP replies arrive.

 

It seems like you did everything right, as these monitors worked fine for other servers. I guess, you already know, they use NSIP as a source (not SNIP)

 

Greetings

 

Johannes Norz

Thanks for reply.  Its SNMP(udp 161) traffic from ADC to server, kindly advice the options for network trace, as telnet is for tcp.

Is there any log file that I can check to identify that why CUTOMLOAD monitor SNMP communication is not happening or more details about Probe failure.

 

Thanks,

Link to comment
Share on other sites

1 hour ago, Raza Mir said:

Thanks for reply.  Its SNMP(udp 161) traffic from ADC to server, kindly advice the options for network trace, as telnet is for tcp.

Is there any log file that I can check to identify that why CUTOMLOAD monitor SNMP communication is not happening or more details about Probe failure.

 

Thanks,

I have noticed below warning message as well. i.e. Service contributing to RR . Please advice that what does this means?

sh vserver  vServiceName-1
''''''''''
Bound Service Groups:
1)      Group Name: ServiceGroupName-1

                1) ServiceGroupName-1 (10.10.10.x:80) - HTTP State: UP     Weight: 1
                        Warning: Service contributing to RR
                2) ServiceGroupName-1 (10.10.10.x:80) - HTTP State: UP     Weight: 1
                        Warning: Service contributing to RR

Link to comment
Share on other sites

3 hours ago, Raza Mir said:

Thanks for reply.  Its SNMP(udp 161) traffic from ADC to server, kindly advice the options for network trace, as telnet is for tcp.

 

Thanks,

you may start a trace either from GUI (system -> diagnostics, start a new trace, under Technical support tools, or from command line start nstrace

 

Greetings


Johannes Norz

CTA, CCI, CCE-N

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...