ACE Active and Standby

[philip-devos]

I'm seeing a potential problem with the current ACE design, which is configured as one-arm.

What I’ve discovered is that the standby ACE show hit counts with the service policy as well as connections. According to what I understand, to maintain state between the ACE’s, both share connection and therefore not a concern.

What I see as a potential problem is:

• The network sniff also revealed TCP retransmission between the RSERVER and the standby ACE
• All probes fails on standby

According to my understanding is that the RSERVER should not try to make a connection to the standby.

I will appreciate if someone can shed some light on this.

Philip

[Cesar Roque]

Hi Philip

What si the status of the rserver in the standby ACE?  It is OPERATIONAL or OUTOFSERVICE?

---------------------
Cesar R
ANS Team

[philip-devos]

The rservers on the standby ACE are all in operational state.

state                : OPERATIONAL (by default, unverified)

[philip-devos]

Interesting observation that I want to add.

The standby ACE, when it is in FSM_FT_STATE_STANDBY_HOT mode, show that the probes are failing, service-policy state is out of service and no curr or hit counts.

But, when in FSM_FT_STATE_STANDBY_COLD, the probes is working fine, state IN-SRVC, no current connections