Redundant Internet 3.1.1
Redundant Internet 3.1.1
Redundant Internet 3.1.1
This document describes the steps to configure a dual ISP configuration for a Branch office. In
this scenario an office is connected to two ISPs and redundancy for outbound connectivity is
desired. This configuration uses a combination of static routing, policy based forwarding (PBF),
and destination interface based source NAT translation. This solution provides automatic
outbound Internet redundancy without the need for BGP routing protocol between ISPs.
The static default route will be configured to point to the backup ISP. A PBF rule with path
monitoring will be used to route traffic out to the primary ISP. If the path monitor finds the
primary PBF path is no longer available, traffic will automatically begin flowing over the backup
static default route.
Two source NAT rules will be configured to make sure the outbound traffic is source translated
to the correct IP address depending on the egress interface (primary or backup).
Prerequisites
• PANOS 3.1.1 and above
2. Configure a static default route within your Virtual Router to you backup ISP
4. Configure Path Monitoring on the PBF rule so it will only be active as long as the next
hop (or some other IP beyond the next hop) is available. You can use the default monitor
profile or configure a new one. If you leave the Target IP address blank the next-hop will
be monitored.
set rulebase pbf rules rule1 action forward monitor profile default
set rulebase pbf rules rule1 action forward monitor disable-if-
unreachable yes
6. Don’t forget your security policy to allow the outbound traffic and commit your
configuration.
1. Start a continuous ping out to the Internet. Do a “show session id xxx” to see the details
of the ping session. While the primary link is available the session should be showing the
PBF rule active and the primary Internet link being used. Also, the correct source NAT
address should be displayed.
admin@PA-2050> show session all
-------------------------------------------------------------------------------
ID/vsys application state type flag src[sport]/zone/proto (translated IP[port])
dst[dport]/zone (translated IP[port]
-------------------------------------------------------------------------------
session 39
c2s flow:
source: 10.1.1.100[Trust]
dst: 4.2.2.2
sport: 1 dport: 1
proto: 1 dir: c2s
state: INIT type: FLOW
ipver: 4
src-user: unknown
dst-user: unknown
PBF rule: rule1(1)
s2c flow:
source: 4.2.2.2[Untrust]
dst: 192.0.2.1
sport: 1 dport: 1
proto: 1 dir: s2c
state: INIT type: FLOW
ipver: 4
src-user: unknown
dst-user: unknown
start time : Tue Mar 16 07:08:22 2010
timeout : 6 sec
total byte count : 148
layer7 packet count : 2
vsys : vsys1
application : ping
rule : rule1
session to be logged at end : yes
session in session ager : no
session sync'ed from HA peer : no
address/port translation : source
nat-rule : Primary(vsys1)
layer7 processing : enabled
URL filtering enabled : no
ingress interface : ethernet1/3
egress interface : ethernet1/1
session QoS rule : default (class 4)
Rule: rule1(1)
State: Active
Action: Forward
Egress IF: ethernet1/1
NextHop: 192.0.2.2
Monitor IP: 192.0.2.2
Rule Status: UP
Monitor: Action:Fail-Over, Interval:3, Threshold:5
Stats: KA sent:194, KA got:177, Packet Matched:65915
-------------------------------------------------------------------------------
ID/vsys application state type flag src[sport]/zone/proto (translated IP[port])
dst[dport]/zone (translated IP[port]
-------------------------------------------------------------------------------
session 257
c2s flow:
source: 10.1.1.100[Trust]
dst: 4.2.2.2
sport: 1 dport: 200
proto: 1 dir: c2s
state: INIT type: FLOW
ipver: 4
src-user: unknown
dst-user: unknown Notice no PBF rule listed here
s2c flow:
source: 4.2.2.2[Untrust]
dst: 192.0.2.253
sport: 200 dport: 1
proto: 1 dir: s2c
state: INIT type: FLOW
ipver: 4
src-user: unknown
dst-user: unknown
start time : Tue Mar 16 07:13:37 2010
timeout : 6 sec
total byte count : 74
layer7 packet count : 1
vsys : vsys1
application : ping
rule : rule1
session to be logged at end : yes
session in session ager : no
session sync'ed from HA peer : no
address/port translation : source
nat-rule : Backup(vsys1)
layer7 processing : enabled
URL filtering enabled : no
ingress interface : ethernet1/3
egress interface : ethernet1/2
session QoS rule : default (class 4)