Forum Discussion

Sinan_WANG's avatar
Sinan_WANG
Icon for Nimbostratus rankNimbostratus
Nov 25, 2014

linerate version2.5 virtual ip status UP but "no associated system interface. Routed traffic only."

Hi all,

 

when i configed a linerate for LB. But there is WARNING: virtual-ip vipweb1 has ARP reply disabled until the IP address is configured on a system interface.

 

This is my config:

 

interface em0 mtu 1500 ip address dhcp ip address 10.10.10.254 255.255.255.0 ! interface em1 mtu 1500 ip address 192.168.2.254 255.255.255.0 ! interface em2 mtu 1500 ip address 10.10.20.254 255.255.255.0 ! ip route 0.0.0.0/0 192.168.2.2 ! ssl profile self-signed attach certificate self-signed attach key self-signed ! virtual-ip base vipbase_web1 service http keepalive-timeout 5 admin-status online ! virtual-ip vipweb1 ip 192.168.2.100 80 base vipbase_web1 virtual-ip vipweb2 ip 192.168.2.101 80 base vipbase_web1

 

How can i resolve it?

 

thanks

 

linerate

4 Replies

Sort By
  • Madhu_Rajagopal's avatar
    Madhu_Rajagopal
    Icon for Employee rankEmployee
    Nov 25, 2014

    It appears from the config you have provided that you don't have 'the ip-address of virtual-ip 'vipweb1' matching to any of your data interfaces like em0, em1, or em2. Seeing that vipweb1 has an ip-address on the same subnet as you have or vipweb1 virtual-ip, you need to change your configuration to so that virtual-ip vipweb1 should have the same ip-address as em1:

    virtual-ip vipweb1
ip 192.168.2.254 80    <------ line changed
base vipbase_web1

    You can find more information on this warning in the product documentation for LineRate of the virtual-ip as a note. Please let us know if this was helpful. Look forward to your reply.

  • Sinan_WANG's avatar
    Sinan_WANG
    Icon for Nimbostratus rankNimbostratus
    Nov 25, 2014

    Hi Rajagopal,

     

    I changed my config and it worked! Thanks for your reply.

     

    In linerate it should use the interface ip address for virtual server ip.

     

    But in F5 LTM it could uses ip address on the same subnet of the interface ip address.

     

    I should change my mind to use linerate.

     

    • Johnny_Schmidt_'s avatar
      Johnny_Schmidt_
      Historic F5 Account
      Nov 25, 2014
      Yes, exactly, the BIG-IP LTM behavior is very different from LineRate with respect to virtual address traffic handling configuration. In LineRate, an Interface address + VirtualIP + VirtualServer together define the reverse-proxy data path from a client to the LineRate system (with a Real Server configuration attached to a VirtualServer defining the back-end of the proxy). You might think of this as Layer2/3 + Layer3/4 + Layer4+ components of the application proxy: the interface (Layer2) configurations allows the network to resolve the L2 MAC address for the IP address (Layer3); the VirtualIP attaches an L3 network address and L4 port of socket to a VirtualServer. Also note that ICMP behavior may be different than you expect. See http://docs.lineratesystems.com/093Release_2.5/100Getting_Started_Guide/100LineRate_OverviewICMP for specifics. Hope that helps!
  • Madhu_Rajagopal's avatar
    Madhu_Rajagopal
    Icon for Employee rankEmployee
    Dec 02, 2014

    Hi Sinan, I am pleased to know that your problem was resolved. Although this is a documented aspect of LineRate, we may still need to improve our documentation. On that note, I am interested in knowing what documentation you were following in setting up your LineRate. Further, I am curious about LineRate's application in your network. Do share that with us if you can. Look forward to hearing from you.

     

    Regards Madhu