Surebackup "Route network traffic between vNICs" not routing traffic between vNICs

[darren_flatman]

Configured Virtual lab with Proxy appliance

Proxy appliance has a static IP

Powered on appliance and test ping - success

Created application group for 4 VMs

3 application servers + 1 DC

3 Application servers are on Prod network VLAN 511

DC is on Prod network VLAN 506

Created two isolated networks,

Vlab VLAN 511 and Vlab VLAN 506

The IP for isolated Vlab VLAN 511 is the default gateway for the 3 app servers

The IP for Vlab VLAN 506 is the default gateway for the DC

The 3 app server are on the network 10.2.23.0/16

The DC is on 10.2.6.0/24

Route Network traffic between vNICs is enabled

I ran the job, all VMs powered on no issues, nothing flagged in the logs

Connected to DC and tried to ping one of the app servers - failed

From DC tried to ping default gateway (isolated network IP) - success

From DC tried to ping IP for App server default gate - success

From App server tried to ping DC - failed

From App server tried to ping default gateway - success

From App server tried to ping DC default gateway success

From App server tried to ping another App server - success

Looks like the Proxy appliance is not routing traffic between the vNICs

Am I missing a step somewhere? It does not look like the traffic is getting router from one network to the other

[PetrM]

Hi Darren,

There are many different reasons why ping may be failed. I don't think we can effectively troubleshoot this technical issue over the forum posts, I would run Wireshark on DC and App server and tcpdump on the proxy appliance to define a node where packets are lost. You should ask our support engineers to carry out all necessary tests and analyze debug logs, I'm pretty sure they will find out the root cause soon. Also, please share a support case ID for our reference.

Thanks!

[darren_flatman]

Thanks will try your suggestion
Case ID #05966403

[Andreas Neufert]

Just one idea. Windows Firewall has a "Router"/DNS/Network identification functionality. If you change the router and potentially the DNS (as you do when starting the vlab), then the System would detect the network as "unknown" and the "Public" network rule in the windows firewall might apply. I would check the ICMP rules (PING uses ICMP) and open it up temporary when you have bootet the VM in the lab. Then try to ping again and see if you get answers through the routing of the vLAB. From there you can go.

Another thing that could prevent PING from working is if you have set the Subnet mask wrong (at VLAB configuration or at the VMs). Please careful check it.

I would as well check IP addresses (ipconfig -all) on the vlab bootet systems if they got the right IPs.

[doktornotor]

Just to add to the above, you can check the network profile with Get-NetConnectionProfile via PS. If it shows Public in NetworkCategory, the traffic will pretty likelly be blocked.