topic ACE routing fails and networks not reachable in Network Security

ACE routing fails and networks not reachable

Shobith K — Tue, 12 Mar 2019 07:08:14 GMT

We have an ACE module on 6513 where in the rservers are hosted behind the ACE in routed mode. We are having an issue where in we lost connectivity to all servers behind the ACE from outside world. From the servers they were able to reach their gateway (ACE ip) but not the MSFC or any other external world ip's.

To fix this we failed over to backup context, it started working. But after some time the issue came on the secondary as well. Any thoughts on this issue. Has anyone faced this anywhere.

Rservers --->ACE --> MSFC--->External world

External world --> ACE VIP--> Rservers

There were no suspicious logs on MSFC or the ACE module. It was like the routing daemon on the ACE not doing its job and this issue becomes undetected for a failover.

I am running sw version Version A2(3.3) [build 3.0(0)A2(3.3)] on ACE 20 module.

When you failover is that to

Richard Bradfield — Thu, 14 Jan 2016 05:01:30 GMT

When you failover is that to a different ACE and 6513?

yes, it gets failed over to a

Shobith K — Thu, 14 Jan 2016 12:27:43 GMT

yes, it gets failed over to a different ACE on standby 6513

however the Layer 2 path will be still via primary 6513 onto secondary 6513 MSFC then secondary ACE.

Ok so the rservers are

Richard Bradfield — Thu, 14 Jan 2016 22:02:17 GMT

Ok so the rservers are physically connected to the primary 6513?

so when running secondary the path is

rserver> pri6513> sec6513> ACE

the 6513 just has the rserver vlan configured no L3 for it?

it does not look like an ACE problem as it is the same for both, but you could try upgrading the ACE to 4.2.3.

you could share the relevant 6513 and ACE configuration

a bit puzzling!