For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

ReynaldoQ_14206's avatar
ReynaldoQ_14206
Icon for Nimbostratus rankNimbostratus
Feb 20, 2014

Vlan n a Layer 2 device

After configuring a new VLAN on a Layer 2 LTM, I setup a virtual server with an ip from this new vlan. I still can not telnet to this virtual server but can telnet to the pool members. Is the self ip has to do with this? Do I have to creat a self ip for this new vlan.

 

I am new to this. Please advise.

 

Thanks.

 

5 Replies

  • Can you post your virtual server config? Are you attempting a telnet on the port the virtual server is configured on?

     

  • Hi Cory,

     

    Yes I am attempting a telnet on the port the virtual server is configured on.

     

    ltm pool pl_bxb-www.mdgtools_80 { members { 10.196.36.55:80 { session monitor-enabled } 10.196.36.56:80 { session monitor-enabled } } monitor http_php5_test partition common }

     

    ltm virtual vs_bxb-www.mdgtools_80 { destination 10.196.36.126 ip-protocol tcp mask 255.255.255.255 partition common pool pl_bxb-www.mdgtools_80 profiles { fastL4 { } } }

     

  • If you run a tcpdump on the F5, do you see the port 80 traffic arriving from your client?

     

  • ltm virtual vs_bxb-www.mdgtools_80 { destination 10.196.36.126 ip-protocol tcp mask 255.255.255.255 partition common pool pl_bxb-www.mdgtools_80 profiles { fastL4 { } } }

     

    have you tried snat automap under virtual server configuration?

     

  • Sorry nitass for not getting back to you sooner. The virtual server is now reachable. All it took was to uncheck the Address Translation and Port Translation checkbox in the setup.

     

    Thanks for the help though.