Partial failover cannot be accessed from some subnets.

[lchuakc]

I have a cloud connect subscription with Replication VM located in the DR site. Back in 2023 I used to be able to perform partial failover of one single VM and it will use the NEA applicance to connect to the DR side and I am able to ping the fail-over VM in the remote site from the VPN subnet, lan, server and wireless subnets.

Recently I have done a partial failover test and I am only able to ping from the server subnet but unable to ping from the VPN, lan and wireless subnets.

Vendor told me there are issues on my end? I am just trying to get a closure on what is causing the issues? I do not have any network changes on my end. But vendor is saying my site is the issue so I have to resolve it on my end.

Does anyone know what could be causing it? Service provider side network blocking my other subnets? Thanks

[lchuakc]

Nobody knows what is happening? Thanks

[tyler.jurgens]

The NEA appliances stretches your Layer 2 broadcast domain over to the providers side. If you have simply failed over one VM and can still ping it from the same subnet, then whatever is handling the routing from the other subnets seems to be blocking the traffic, and at that point it should still be the router on your side. If you fail multiple VMs over, each in a different VLAN then the NEA would handle the routing.

I would start by verifying you can ping the server when it is not failed over. After that, fail it over and check your own router and see if you can detect any blocked traffic.

Also, double check you have all your networks configured to be available on the provider side. You can read up more on the NEA here:
https://vccbook.io/2.Architecture/2.10- ... ances.html