bigip snat automap

You created a forwarder virtual server for your servers behind the bigip appliance to access the internet, your server could not get a respond back. You troubleshoot the problem and found that:

  1. Default route is configured in the bigip.
  2. You cannot ping the next hop gateway specified in the default route.
  3. You could not determine if this is the cause of routing because the next hop router is not in your governance.

To troubleshoot the problem you can try using SNAT automap. SNAT automap will translate the address in this sequence:

  1. floating self ip of the egress vlan.
  2. floating self ip of a different vlan.
  3. non-floating self ip of an egress vlan.
  4. non-floating selfip of a different vlan.

snat-automap.png

After you have turned on the SNAT automap your server is able to get external updates

apt-get1.png

Now you can conclude that it is highly possible that the next hop router does not have a route back to your server.

snat1

what this means is that your server’s traffic is being translated into the floating self ip address of vlan internet, and the firewall thought that the incoming request is from a directly connected route.

 

 

This entry was posted in F5, General stuffs and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s