Hello friend welcome to my video
We practice with a small example like above
This video explains how to configure The Cisco ASA to use redundant or backup internet connections
Cisco ASA uses static route tracking to allow devices to use redundant or redundant internet connections
In order to achieve this redundancy the a side Associates a static route with a monitoring Target that you define
The service level agreement operation monitors the target with periodic icmp Echo requests
If an echo reply is not received then the object is considered down
and the associated route is removed from the routing table.
A previously configured backup route is used in place of the route that is removed
While the backup route is in use, the SLA monitor operation continues its attempts to reach the monitoring target.
Once the target is available again, the first route is replaced in the routing table,
and the backup route is removed
Enter this command in order to track a static route.
This is the static route to be installed in the routing table while the tracked object is reachable
The value after the keyword "track" is a tracking ID you specify.
The interface attached to the Secondary ISP.
"backup" was chosen here, but any name can be assigned
The administrative distance of the backup route must be greater than the administrative distance of the tracked route.
If the primary gateway is unreachable,
that route is removed and the backup route is installed in the routing table instead of the tracked route
Nat configuration for outside and backup
Configure a new monitoring process with the ID 123
Specify the monitoring protocol and the target Network object whose availability the tracking process monitors
Specify the number of packets to be sent with each poll
In this example
It is 3
Specify the rate at which the monitor process repeats
In this example it is 10 seconds
Schedule the monitoring process
In this case the lifetime of the process is specified to be forever
The process is scheduled to begin at the time this command is entered
As configured, this command allows the monitoring configuration specified above to determine how often the testing occurs
However, you can schedule this monitoring process to begin in the future and to only occur at specified times
Associate a tracked static route with the SLA monitoring process
The track ID corresponds to the track ID given to the static route to monitor
123 is the ID of the SLA process defined above
Now if the primary ISP fails the secondary becomes active automatically
As always if you found this post useful then subscribe to my YouTube channel
Help me 500 thousand subscribers