Forum Discussion

VinS_66475's avatar
VinS_66475
Icon for Nimbostratus rankNimbostratus
May 22, 2009

Pb reconize ports

I've install a Vlan (internal) on an interface (1.1).

 

Configure a self ip (10.1.4.115) to this vlan (internal) ... But the f5 don't detect any machine (10.1.4.125 ; 10.1.4.116 ; 10.1.4.108) in this network.

 

 

In a second part, i've not configure a self ip but a route (10.1.4.0/24) to this Vlan (internal). But : same result.

 

 

These machines (10.1.4.125 ; 10.1.4.116 ; 10.1.4.108) are inaccessible by the f5, and inaccesible too by the managment port and less more by an another vlan (external) in the interface (1.3) on another network (10.1.5.0/24).
config
design
  • The_Bhattman's avatar
    The_Bhattman
    Icon for Nimbostratus rankNimbostratus
    May 22, 2009
    Assuming that the machines are hooked into a switch that are on the same VLAN as the one plugged into as the F5, did you check to see if the servers could ping each other?

     

     

    CB

     

  • L4L7_53191's avatar
    L4L7_53191
    Icon for Nimbostratus rankNimbostratus
    May 22, 2009
    Did you rule out an IP collision with the 10.1.4.115 address? If you've configured a self-ip on 10.1.4.0/24 and you can't see any of the L2 adjacent systems it sounds to me like you may have had some arp confusion. I say this because I noticed that you've got a system on an adjacent IP address (.116).

     

     

    It may be helpful to see what is going on arp-wise, so try running "tcpdump -ni internal arp" with your self-ip configured.

     

     

    -Matt
  • VinS_66475's avatar
    VinS_66475
    Icon for Nimbostratus rankNimbostratus
    May 22, 2009
    First, thanks for your's responses.

     

     

    cmbhatt, mine machines (10.1.4.125 and 10.1.4.116) are virtual machine in a vmware esxi server (10.1.4.108) and directely hooked in the interface 1.1

     

    If i connect these on my machine, all machines ping alls

     

    And the VLAN are only declared in the f5, but all machine connected in this interface are on the same network.

     

     

    L4L7, i've not create any rule ... i must it ?

     

    I've not use arp, only self-ip. Adjacent ip cause issues ?

     

    I've try running, as you have said, "tcpdump -ni internal arp", but it doesn't work. The single running "tcpdump" doesn't work too ...

     

     

    Thanks for your's help !

     

    Neophyse
  • The_Bhattman's avatar
    The_Bhattman
    Icon for Nimbostratus rankNimbostratus
    May 22, 2009
    When you do a tcpdump you need to know which interface to sniff. You might have not named 10.1.4.0/24 segment as "inside" so try "tcpdump -ni 1.1 arp". Then do a couple of pings to the hosts to generate the arp messages.

     

     

    CB