Guest

Preview Tool

Cisco Bug: CSCtf13593 - snmp trap is inconsistent when real-rserver states changes due to probe

Last Modified

Nov 01, 2010

Products (1)

  • Cisco ACE 4700 Series Application Control Engine Appliances

Known Affected Releases

3.0(0)A4(0.99.17)

Description (partial)

Symptom:

Question about whether the correct trap is being sent when a real server comes back operational after a probe-failure or arp-failure.

Conditions:
Traps are sent when a real server in a serverfarm flaps, e.g probe-failure and back operational. When the probe-failure is detected the cesRealServerStateChangeRev1 is sent as mentioned in the A2(2.3) release note. But when the real becomes operational again, the probe succeeds, we see cesRealServerStateUpRev1. The release note states the cesRealServerStateUpRev1 results from user intervention, i.e. inservice. It does not state it will happen when the real is operational again. Hence the question about correct behavior.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.