Forum Discussion

faziz_252121's avatar
faziz_252121
Icon for Nimbostratus rankNimbostratus
Mar 01, 2016

BIG-IP VM Connectivity

Hi

 

I have LAB with 3 web server VMs, & BIG-IP LTM running on VMware Workstation

 

BIG-IP:

 

Network adapter 2 connect to vmnet 4 :172.16.10.1 -External BIG-IP : 172.16.10.100-,

 

Network adapter 3 connect to vmnet 2 :10.10.10.1 -Internal BIG-IP : 10.10.10.100-,

 

My problem is I cant ping from webserver-10.10.10.0/24- to BIG-IP external interface 172.16.10.100?

 

@I am new on BIG-IP, so the help from BIG-IP Eng. will be highly appreciated.

 

Thanks

 

application delivery
LTM

3 Replies

Sort By
  • Nath's avatar
    Nath
    Icon for Cirrostratus rankCirrostratus
    Mar 01, 2016
    Hi Faziz, Why you need to ping the 172.16.10.x subnet?
  • faziz_252121's avatar
    faziz_252121
    Icon for Nimbostratus rankNimbostratus
    Mar 01, 2016
    Actually, i have BIG-IP with two interfaces, external: 172.16.10.100 connect to my pc:172.16.10.1 and internal interface: 10.10.10.100 connect to two servers: 10.10.10.1 & 10.10.10.2, when choice Source Address Translation: None; on virtual server, and trying to browse vServer ip: 172.16.10.100 traffic not forward to to back-end server; but when i switch Source Address Translation to Auto Map browse the traffic forward to back-end server; so i think the issue is when i use None in Source Address Translation the traffic come as 172.16.10.1 but back-end server can't reach this subnet.
  • Daniel_Epperson's avatar
    Daniel_Epperson
    Icon for Employee rankEmployee
    Mar 03, 2016

    For inbound connections, that is, connections initiated by a client node, SNATs ensure that server nodes always send responses back through the BIG-IP system, when the servers default route would not normally do so. See the Manual Chapter: Configuring SNATs for more details.