1.1 Application Scenario
The company has two WAN connections for sharing outbound internet traffic . WAN1 uses a static IP address, and WAN2 uses a PPPoE connection. Since WAN1 ISP is also the company's VOIP provider, the network administrator wants VoIP traffic primarily sent out over WAN1. In case WAN1 is down, the VoIP can still go out over WAN2 PPPoE connection. The network administrator also wants HTTP traffic sent over WAN2 PPPoE connection primarily. In case WAN2 PPPoE is down, LAN users can still surf internet over WAN1. For all other types of traffic, administrator needs the WAN connection to share the outbound traffic load, performing load balancing.
1.2 Configuration Guide
Goal to achieve:
1) VoIP traffic goes out primarily through WAN1. In case WAN1 is down, it will go out via WAN2 PPPoE connection.
2) HTTP traffic goes out primarily through WAN2 PPPoE connection. In case WAN2 PPPoE is down, it will go out via WAN1.
3) All other traffic goes out via WAN trunk performing Load balancing with Least Load Balancing algorithm.
USG configuration:
Step 1. Configure a PPPoE account on WAN2 interface.
(1) Go to CONFIGURATION > Object > ISP Account, add a PPPoE account:
(2) Go to CONFIGURATION > Network > Interface > PPP, add a new PPP interface, which is based on WAN2 interface,
Step-2: Go to CONFIGURATION > Network>Interface>Trunk. Add WAN Trunks.
(1) Add WAN trunks for VoIP traffic - Set WAN1 as Active mode, while setting WAN_ppp as Passive mode.
(2) Add WAN trunk for HTTP traffic- Set WAN2_ppp as Active mode, while setting WAN1 as Passive mode.
(3) Use SYSTEM_DEFAULT_WAN_TRUNK to perform load balancing for all other traffic.
Step-3. Go to CONFIGURATION > Network > Routing > Policy Route, add policy routes for VoIP and HTTP traffic.
(1) Add a policy route for VoIP traffic:
Source: LAN1_subnet
Destination: Any
Service: SIP
Next Hop: select the newly created WAN trunk WAN_Trunk_VoIP
Please note that to make sure this policy route applies to all VoIP traffic, including both the SIP signaling and RTP (voice data), we need to enable SIP ALG.
Go to CONFIGURATION > Network > ALG, enable SIP ALG.
(2) Add a policy route for HTTP traffic:
Source: LAN1_subnet
Destination: Any
Service: HTTP
Next Hop: select the newly created WAN trunk WAN_Trunk_HTTP.
(3) For all other traffic, use SYSTEM_DEFAULT_WAN_TRUNK to perform load balancing. Go to CONFIGURATION >Network> Interface >Trunk. Click on Show Advance Settings.
Make sure Default SNAT is enabled. Select SYSTEM_DEFAULT_WAN_TRUNK in Default Selection.
The company has two WAN connections for sharing outbound internet traffic . WAN1 uses a static IP address, and WAN2 uses a PPPoE connection. Since WAN1 ISP is also the company's VOIP provider, the network administrator wants VoIP traffic primarily sent out over WAN1. In case WAN1 is down, the VoIP can still go out over WAN2 PPPoE connection. The network administrator also wants HTTP traffic sent over WAN2 PPPoE connection primarily. In case WAN2 PPPoE is down, LAN users can still surf internet over WAN1. For all other types of traffic, administrator needs the WAN connection to share the outbound traffic load, performing load balancing.
1.2 Configuration Guide
Goal to achieve:
1) VoIP traffic goes out primarily through WAN1. In case WAN1 is down, it will go out via WAN2 PPPoE connection.
2) HTTP traffic goes out primarily through WAN2 PPPoE connection. In case WAN2 PPPoE is down, it will go out via WAN1.
3) All other traffic goes out via WAN trunk performing Load balancing with Least Load Balancing algorithm.
USG configuration:
Step 1. Configure a PPPoE account on WAN2 interface.
(1) Go to CONFIGURATION > Object > ISP Account, add a PPPoE account:
(2) Go to CONFIGURATION > Network > Interface > PPP, add a new PPP interface, which is based on WAN2 interface,
Step-2: Go to CONFIGURATION > Network>Interface>Trunk. Add WAN Trunks.
(1) Add WAN trunks for VoIP traffic - Set WAN1 as Active mode, while setting WAN_ppp as Passive mode.
(3) Use SYSTEM_DEFAULT_WAN_TRUNK to perform load balancing for all other traffic.
Step-3. Go to CONFIGURATION > Network > Routing > Policy Route, add policy routes for VoIP and HTTP traffic.
(1) Add a policy route for VoIP traffic:
Source: LAN1_subnet
Destination: Any
Service: SIP
Next Hop: select the newly created WAN trunk WAN_Trunk_VoIP
Please note that to make sure this policy route applies to all VoIP traffic, including both the SIP signaling and RTP (voice data), we need to enable SIP ALG.
Go to CONFIGURATION > Network > ALG, enable SIP ALG.
(2) Add a policy route for HTTP traffic:
Source: LAN1_subnet
Destination: Any
Service: HTTP
Next Hop: select the newly created WAN trunk WAN_Trunk_HTTP.
(3) For all other traffic, use SYSTEM_DEFAULT_WAN_TRUNK to perform load balancing. Go to CONFIGURATION >Network> Interface >Trunk. Click on Show Advance Settings.
Make sure Default SNAT is enabled. Select SYSTEM_DEFAULT_WAN_TRUNK in Default Selection.
Hello,
ReplyDeleteWe are doing VoIP wholesales routes business.
We are looking A-Z CLI & Non CLI traffic.
Aggressive rates with premium quality CLI/NON CLI routes.
India CLI, Bangladesh CLI/Non CLI, Pakistan CLI/Non CLI & A-z CLI/Non CLI.
Premium quality with good status routes.
A-Z CLI & Non CLI very low rates with working routes.
We are interest to do long term business with you, if you are interested then please contact.
E-Mail : voiphaariz@gmail.com
Skype : voiphaariz
Mobile : +919747434994
WhatsApp : +919747434994