NHLD: Application options dedicated for specific link

A10 Networks Support Forum Forums Thunder and AX Series NHLD: Application options dedicated for specific link

Tagged: 

This topic contains 2 replies, has 3 voices, and was last updated by avatar Oscar Aguilar 4 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #6852
    avatar
    netcrawler
    Member

    Hi Team:

    Setup:Next Hop Load Distributor
    Just want to ask, Is it possible to dedicate a specific application to use a specific ISP link? For ex. Skype traffic, all of the traffic from a skype client will only use ISP 1 link. Is this possible? if yes, how can we implement this.

    Looking forward to hearing from you soon.

    Regards,
    Evea

    #10612
    avatar
    baburkhan
    Member

    Hello Evea,

    We do support Next Hop Load Distribution on A10. For your example scenario, you can deploy it as follows:

    1- Assign your application, e.g. Skype, a custom port to use, OTHER than 80 and 443 (which are the defaults)

    2- Enable allow promiscuous VIP command on your client side interfaces only.

    3- Set up Real Servers with wildcard ports 0 TCP, 0 UDP, 0 Others and that custom port number you chose (lets say 8080). For 8080 TCP, make sure you assign the IP address of the link intended for use by Skype e.g. ISP 1.

    4- Configure a service group for the links (real servers). If the real server configurations for the links have both TCP and UDP ports, configure a service group for TCP and another service group for UDP.

    5- Set up a wildcard VIP (0.0.0.0) on your device. Inside, have wildcard Virtual Ports 0 TCP, 0 UDP, 0 Others and the custom 8080 TCP.

    Thanks,
    Babur

    #12562

    Adding my 5 cents to Babur answer,

    6.- Create and associate to the wilcard VIP the aflex script that is going to match skype client source IP, so he will be always sent through the same link: Begin—

    when CLIENT_ACCEPTED {
    	switch [IP::client_addr] {
    	10.1.1.14 { node 1.1.1.1 }
    	10.1.1.121 { node 2.2.2.2 }
    	10.1.2.0/24 { node 1.1.1.1 }
    	10.1.3.0/24 { node 2.2.2.2 }
    	}
    }

    —End
    And if you wan to do it based on destination not origin:
    Begin—

    when CLIENT_ACCEPTED {
    	switch [IP::local_addr] {
    	8.8.8.8 { node 1.1.1.1 }
    	8.8.4.4 { node 2.2.2.2 }
    	}
    }

    —End
    where 1.1.1.1 would be router or link 1 and 2.2.2.2 would be router or link 2

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Comments are closed.