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

genseek_32178's avatar
genseek_32178
Icon for Nimbostratus rankNimbostratus
Jan 09, 2012

Basic Setup of F5

Hi,

 

 

I want to setup a new F5 box in my network. Before, i do that i want to understand how it can actually be configured in Routed and Bridge mode.

 

 

I would really appreciate if someone can guide me on this.

 

 

F5 is connected to AGG pair A, with upstream device as Access Router and downstream device as L2 TOR switches connecting servers, as below.

 

 

Core

 

|

 

Access Router

 

|

 

|

 

F5---Trunk----Agg Switch - A

 

|

 

|

 

L2Hst TOR Switch

 

| |

 

| |

 

Server1 Server2

 

 

I want to start with Routed mode configuration using tmsh.

 

 

TH-genseek

 

 

 

38 Replies

  • i did ping from pc to virtual server address. tcpdump was run on bigip.

     

     

    the tcpdump output above shows icmp echo request reached bigip and bigip replied with icmp echo reply.
  • but i'm not able to ping the VIP from within F5 itself.

     

     

    Do you see any reason why this could happen? I mean usual reasons.
  • i have no idea yet.

     

     

    is there any special in the virtual server configuration?
  • In the below, VS configuration, can you tell me what is the purpose of the cmd - vlans q_mps_r_10.221.256.0_27 enable ?

     

     

    What it does, when it is mapped to a VS? Is it a normal configuration to map vlans to Virtual servers just like pools, profiles etc?

     

     

    virtual wlireports_df_wlxbici_80_vs {

     

    pool wlireports_df_wlxbici_80_pl

     

    destination 10.221.256.254:http

     

    ip protocol tcp

     

    profiles fastl4_default_gns_pr {}

     

    vlans q_mps_r_10.221.256.0_27 enable
  • what is the purpose of the cmd - vlans q_mps_r_10.221.256.0_27 enable ? the virtual server is enabled on q_mps_r_10.221.256.0_27 vlan only. that means if traffic has to come from that vlan to hit the virtual server.

    What it does, when it is mapped to a VS? Is it a normal configuration to map vlans to Virtual servers just like pools, profiles etc?that is fine. it might have some scenario which we do not want virtual server to be listening on every vlan.

    can you try this command and see if arp is enabled or not?

    b virtual address 10.221.256.254 list all

    this is mine.

    [root@ve1023:Active] config  b virtual address 172.28.19.79 list all
    virtual address 172.28.19.79 {
       enable
       limit 0
       arp enable
       route advertisement disable
       mask 255.255.255.255
       floating enable
       unit 1
       server any
       partition Common
    }
    
  • Arp is enabled.

     

     

    Actually, in the below configuration, the cmd - vlans q_mps_r_10.221.256.0_27 enable is not there, instead it is as below.

     

     

    virtual wlireports_df_wlxbici_80_vs {

     

    pool wlireports_df_wlxbici_80_pl

     

    destination 10.221.256.254:http

     

    ip protocol tcp

     

    profiles fastl4_default_gns_pr {}

     

    vlans q_mps_r_172.20.500-24 enable

     

    vlans q_mps_r_203.36.134.0_192 enable

     

     

    So, inbound traffic is coming on VIP,10.221.256.254. But the corresponding vlan, vlans q_mps_r_10.221.256.0_27 enable, is not mapped to the VS.

     

     

    Could this be the reason? If yes, why?

     

     

  • i do not think so. virtual server is on port 80 but the problem we are taking is icmp (vlan on virtual server should not matter).

     

     

    10.221.256.254 should be pingable anyway.