Azure No Arp

Reply
Highlighted
L5 Sessionator

Azure No Arp

Hey All,

 

I'm coming across a weird issue here.

 

We have two subents in Azure. Let's call them Subnet1 and Subnet2

 

Subnet1 has a UDR to point traffic to the internal interface of the firewall.

 

This works, we see the traffic come into the firewall. We don't see any return traffic from the server in subnet 2. There is a static route pointing to the azure fabric .1 address.

 

When I do a flow basic, the firewall is unable to send the traffic to the gateway (azure .1 address) because there is no ARP.

 

Route found, interface ethernet1/2, zone 2, nexthop 10.38.225.1

Resolve ARP for IP 10.38.225.1 on interface ethernet1/2

ARP pending

Packet dropped, no ARP

 

HELP!


Accepted Solutions
Highlighted
L5 Sessionator

Found out the issue.. the static routes on the firewall were pointing to each .1 address of the subnet rather than the .1 address of the address range assigned to the VNET

View solution in original post


All Replies
Highlighted
L4 Transporter

Do you have a corresponding route in subnet 2 pointing to the firewall for subnet 1?  If you do not, azure will assymetrically return the traffic directly to the server rather than return routing through the firewall due to the VNET route.

Highlighted
L5 Sessionator

Hi @jmeurer 

 

Thanks for your input. Yes the UDR for subent 2 is there.

 

Any other ideas?

 

Thanks,

Luke.

Highlighted
L4 Transporter

I assume the firewall has corresponding routes for both subnets pointing to the first IP of the internal subnet the firewall is attached two.

 

Also, check to ensure the interface has IP Forwarding enabled on the azure side.  If you do need to change this setting.  Reboot the firewall.  I have seen it not apply until after reboot.

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface#enable-or-d...

 

From there, double check your NSGs.

 

Since this intrazone traffic, it should be allowed, but you may not be logging it due to the inherent rule.  Override logging on intrazone, it may give you some further information in the Monitor.

Highlighted
L5 Sessionator

Hey @jmeurer 

 

Firewall routes exist and are correct.

 

IP forwarding enabled on all interfaces. I've also rebooted the firewall.

 

nSGs are all allowed.

 

I've done logging on the policies but just show "bytes received: 0"

 

I've tried with a NAT rule to source NAT and not, makes no difference.

Highlighted
L4 Transporter

You have hit all of the usual culprits.  Time to get a TAC case open.

Highlighted
L4 Transporter

Is Subnet 2 a gateway subnet?

Highlighted
L5 Sessionator

Hey @dmaynard 

 

Nope! It's not a gateway subnet.

Highlighted
L5 Sessionator

Found out the issue.. the static routes on the firewall were pointing to each .1 address of the subnet rather than the .1 address of the address range assigned to the VNET

View solution in original post

Highlighted
L4 Transporter

Can you elaborate little bit ?  you are saying you pointed static route on Palo Alto to VNET  .1 IP ? and not first IP in subnet of interface of firewall for example eth2 ?

SD-WAN | Cloud Networking | PCNSE | ICSI CNSS | MCNA | | CCNP | CCSA | SPSP | SPSX | F5-101 | CCIE-SEC-Attempted
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!