Cisco ISP Failover IP SLA Configuration Example

Cisco ISP Failover IP SLA Configuration Example

On some Cisco routers there is the command IP SLA and on other routers it is IP SLA MONITOR. Without going into the reasons for the differences including IOS features and versions, this post will focus and show a working example of IP SLA. To view a similar post containing IP SLA MONITOR please visit the following link:

IP SLA Monitor Example for Fail-over Survivability of ISP .

That post will contain a similar configuration example to the following that uses the ip sla monitor configuration to accomplish the same task of redundancy/failover of an ISP link. Also similar to this post is that the primary interface or ISP for a custom application is a T! and the redundant or fail-over ISP is a DSL.

Configure ASA to allow traceroute responses

Below is a configuration example for IS SLA (no monitor in the command line interface): Cisco IP SLA example configuration (not IP SLA MONITOR) also uses a track list and Boolean operator condition. This was a working configuration so the IP addresses have been modified. The remote office this configuration was used for has a T1 connection to the internet (a "legacy" T1) and a DSL directly attached to the router. The interface for the T1 was 0/3/0:0.1 and the DSL was GigabitEthernet 0/1. they wanted a custom application to use the T1 exclusively but in case there was a T1 internet access failure, they wanted to utilize the DSL as a failover. The custom application was critical to the business. The idea was simple, if the T1 fails, use the DSL for the custom application to connect to an online database source and server. 

There are some other mitigating factors that made this IP SLA configuration a little more challenging but I will not go into it at this time. It is not relevant actually to the commands used. The relevance came in to play in regards to what interfaces were to be used for sourcing the icmp ping used in the ip sla monitor. It is also the reason the line-code tracker in combination with the boolean operator and track list. There are two tracker objects in a tracker list. The list uses a boolean AND, track 10 ip sla 20 reachability --> a ping to a target ip address for which there is ONLY a single static route to use the T1 track 11 interface Serial0/1/0:0 line-protocol --> Interface status track 20 list boolean and --> boolean AND, two both conditions have to be met , almost seems redundant but TAC did this on another remote office router object 10 --> tracker 10 shown above object 11 --> tracker 11 shown above ip route 4.2.2.2 255.255.255.255 192.168.1.11 track 20 --> tracked main route ip route 4.2.2.2 255.255.255.255 192.168.1.1 100 --> alternate route is used if T1 is down ip sla 20 --> referenced in tracker 10 type echo protocol ipIcmpEcho 8.8.8.8 source-interface GigabitEthernet0/0 --> had to use the interface as source, using the ip address did not work. This is the "inside" interface . Yes, I know "inside" is more (another bug, perhaps) , there is a static route that says anny traffic for 8.8.8.8 use the T1 interface. so if there is a problem with the T1 the pings will time out. timeout 1000 --> max ping reply time allowed in milliseconds threshold 2 tag 20 frequency 5 --> status is checked every five seconds ip sla monitor schedule 20 life forever start-time now --> scheduler for monitor 20

Cisco IP SLA Example for ISP failover

Some Cisco routers have IP SLA without the command option of monitor and other Cisco routers have IP SLA MONITOR. The configurations vary slightly, just enough to throw you off just a little. Another simple article (or post) on a tech support for computers, servers, and routers blog site. It describes an example of how IP SLA was used for redundancy and how fears of asynchronous routing were dismissed. From what I have seen and found, support for ip sla monitor started at about the 12.3 release of Cisco's IOS for routers. The two connections or paths to a destination or the internet as it is most often used for, don't even have to be directly connected to the router.

  

Enhance your Support Services with Software for Online Desktop Support. 

 

An inexpensive cost-effective remote desktop software for screen sharing online. Check out and try for free 4RemoteSupport's online desktop support software . Even if you have other software for managing remote desktops such as MSP RMM, not all software works all the time and 4RemoteSupport.com allows unlimited connections and is useful to get that first connection to a remote desktop or laptop system to add your RMM software like Nable, Datto, or Kaseya for example. 

Reset CISCO 5505 ASA to Factory Default

Reset CISCO 5505 ASA to Factory Default

Enhance your Support Services with Online Desktop Support Software. 

You’ll need to use the Console Port to perform this procedure. Hook up the blue console cable to your DB 9 PIN serial port. Plug the other end into ‘Console’ port on the ASA 5505. The console port looks like a network jack. It’s above the USB ports and is surrounded with a blue color matching the console cable itself and says console right next to the port. Use hyper-terminal, click Start, Programs, Accessories, Communications, HyperTerminal, create a connection on Com1 using the terminal settings: 

    - Bits per second: 9600 

    - Data bits: 8 

    - Parity: None 

    - Stop bits: 1 

    - Flow control: None 

 After you open your connection through hyper-term, press enter a couple times. You should get a prompt similar to the following: ‘ciscoasa>’, or ‘nameofyourdevice>’ type ‘ena’ which is the abbreviation for "enable" to go to enable mode. Enter the password, or just press enter if there is no password set. type ‘config t’ type ‘config factory-default’ hit spacebar when the ‘more’ is displayed to get the next page of output. You want to get back to the prompt that looks like: ‘ciscoasa(config)#’ type ‘reload save-config noconfirm’ Make sure that the outside line is plugged into port zero, and your pc is plugged into any of the ports 1-7. The Cisco ASA has been reset to factory settings. DHCP is enabled on the Cisco device, and it’s internal IP address is now 192.168.1.1! Configure RDP Port Forwarding on a Cisco ASA 5505

Enhance your Support Services with Software for Online Desktop Support. 

Access servers, desktop, networks switches and even firewalls remotely on the web.  

Fix Error 1603 when you install QuickBooks Desktop

There are many causes to application not behaving as expected, there are of course networking errors. Networking connects devices all across the Internet and in immediate space around you.  Database issues are also caused by networking problems. there are occasion where applications that use databases simply don't install. The cause can be network or a simple compatibility not fully addressed by the software vendor, or the applications release was for up to a specific OS build number. An update on the client device has also been the cause of many application installation issues. A recent encounter with Intuit QuickBooks installation lead me to a solution not present in Intuit's Knowledgebase or forum support. The application installation error code was 1603. QuickBooks error 1603 is not uncommon, but the process to work around it as presented by Intuit support for QuickBooks error 1603 didn't solve it. Many were repetitive, understandable as to why, as that was the common process for solving multiple installation issues but was not successful for me. Those steps to resolve including downloading from Intuit an additional software troubleshooting component didn't resolve the QuickBooks desktop installation issue. In fact, the Intuit installation troubleshooting software also displayed an error. A unique discovery of a work around to QuickBooks error 1603 was found here. 

 

Configure RDP Port Forwarding on a Cisco ASA 5505

http://remotesupportsoftware.blogspot.com/2008/10/configure-rdp-port-forwarding-on-cisco.html - Configure RDP Port Forwarding on a Cisco ASA 5505 . This is a good simple code example of adding a port forwarding rule to a Cisco ASA 5500 series (in this case it was a Cisco ASA 5505) but it won;t differ much with other versions.

read more | digg story