[f-nsp] ServerIron XL hard coded ICMP limit

Drew Weaver drew.weaver at thenap.com
Sat Feb 19 14:12:37 EST 2011


Howdy again,

I hate replying to my own messages but I have made progress =)

It seems that the pings are failing when the health checks are running.

Are healthcks really resource intensive?

(especially ones like this):

healthck node-ssl tcp
  dest-ip 222.222.222.222
  port ssl
  protocol ssl
  protocol ssl url "GET /test/gif.gif"
  protocol ssl use-complete
  l7-check

I noticed that with the above configuration that pings to the switch fail quite regularly.

If I add 'interval 30' to the configuration it seems like pings only fail once every 30 seconds.

The goal is to not have it fail at all..

Anyone seen this before, know how to fix it?

Thanks,
-Drew


From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Drew Weaver
Sent: Thursday, February 17, 2011 11:41 AM
To: foundry-nsp
Subject: [f-nsp] ServerIron XL hard coded ICMP limit

Does anyone know if there is a hard coded ICMP limit in a serveriron XL for both packets directed at the system and passed through it?

I am having the weirdest issues where ping monitoring a serveriron XL and anything directly connected to the serveriron xl gets messed up even though there is no real reason why on the network.

It is not configured (by me) to have any sort of rate-limit.

Anyone have any thoughts?

-Drew





More information about the foundry-nsp mailing list