16 Replies Latest reply on Jan 3, 2013 12:25 PM by moulegend

    Configuring WAN Failover with Network Monitor

    moulegend New Member

      It was relayed to me that if our primary internet connection is using HDLC, Frame-Relay, or PPP, then I can simply use floating static routes instead of network monitoring to configure the failover.

       

      Our primary interface is PPP.

       

      It seems that the network monitoring may be easier to configure.  What information is available for setting up floating static routes as mentioned by noor previously?  I'm thinking it may just be the best practice to go ahead with the network monitoring fail over but wanted to get some information in regards to this. 

       

      Any help is greatly appreciated.

        • Re: Configuring WAN Failover with Network Monitor
          levi Employee

          moulegend:

           

          For HDLC, Frame Relay, and PPP interfaces, typically the floating static route is much easier to configure, and will take over as the primary default route if the physical interface goes down. 

           

          To configure a floating static route in the CLI use the following syntax:  ip route 0.0.0.0 0.0.0.0 <next hop IP address> <admin distance>.  For example, ip route 0.0.0.0 0.0.0.0 1.1.1.1 10.

           

          To configure a floating static route in the web interface navigate to the following: 

          Data > Route Table > Destination Address:  (0.0.0.0) > Destination Mask (0.0.0.0) > Gateway (Address <next hop IP address>) > Administrative Distance <value greater than 1> (typically 10) > Add

           

          Please, let me know if you have any questions.  I will be happy to help in any way I can.

           

          Levi

            • Re: Configuring WAN Failover with Network Monitor
              moulegend New Member

              Thanks for your response levi.  That seems pretty straight forward and simple and I'm assuming will work just the same as the network monitor in regards to fail over.  Just to make sure I'm reading that correct, I would use 0.0.0.0 for both the Destination address and Mask and then just include the next hop for the Gateway of my backup ISP correct?

               

              Also, in regards to my router configurations, up until this point I've done all the configurations on the Eth 0/2 port of the router since the Eth 0/1 port is in production.  What would be the simplest way to convert those configuration over.  I downloaded the configs as they are right now and thought I could just manually update that file before I upload it back but thought that might cause an error.  Worst case scenario, I'll just reconfigure eth 0/1 with everything needed, put in the floating static route and then plug the backup ISP in to Eth 0/2.

               

              Should be in business then.

               

              Thoughts?

              1 of 1 people found this helpful
              • Re: Configuring WAN Failover with Network Monitor
                moulegend New Member

                Hey Levi,

                 

                I wanted to first say thank you for everything over the past several weeks. We're in our new building and everything is up and operational.  I'm waiting for our NetVanta 150 piece to arrive and plan on hooking that up as soon as it arrives.

                 

                Our secondary fiber solution is just about in place and I'm reviewing back over my notes on configuring the Floating Static Route.  I flipped the configs that I had and then installed the networks so my Encapsulation and VLAN's are all setup on Eth 0/1 now.  My Eth 0/2 has an internal IP address assigned so I can access it.  I'm looking to add in the floating static route but want to make sure I understand it correctly.

                 

                The Destination Address would be my static IP given by the ISP along with the Mask and then the Gateway would be the next Hop IP which was given to me as well correct?  I'm assuming I plug the cat 6 cable from my secondary ISP Switch into my the 5305 Eth 0/2 port.  Is there any config I need to do on the Eth 0/2 port to make the floating static route work?  My Primary Line is PPP through Verizon, but I'll have to check on my Secondary line they are straight fiber and bringing a Cisco Switch to my location to tie in.  Your help is greatly appreciated.

                 

                James

                  • Re: Configuring WAN Failover with Network Monitor
                    levi Employee

                    moulegend:

                     

                    Based on the information you provided above, there are several configuration changes you would need to make to Ethernet 0/2 if you are going to use it as a backup/failover Internet port.  You will need to configure it with the IP address information the ISP provided you with, as well as setup the firewall so private IP addresses can be network address translated (NAT) to public IP addresses that can be routed over the Internet.  Furthermore, the route you described above is not correct for a default route, or a floating static default route.  For a default route, the router must determine if the incoming packet is destined for that router, one of the attached interfaces, or some other network. So the default route (defined by the static route command ip route 0.0.0.0 0.0.0.0 A.B.C.D where A.B.C.D. is the address of the far end router serving as the gateway for all unknown route packets) if configured, serves as the destination for packets that a route is not known for. it is also known as the gateway of last resort.  All traffic not matching a more specific static route will use the default / last resort route (such as Internet traffic).

                     

                    For the floating static route, the key aspect is the administrative distance.  You configure the static route, but have to add the administrative distance at the end so it only becomes the selected route if the primary route (with a lower administrative distance) drops out of the route table do to a failure.  For HDLC, Frame Relay, and PPP interfaces, typically the floating static route is much easier to configure, and will take over as the primary default route if the physical interface goes down.

                     

                    To configure a floating static route in the CLI use the following syntax: ip route 0.0.0.0 0.0.0.0 <next hop IP address> <admin distance>.  For example, ip route 0.0.0.0 0.0.0.0 1.1.1.1 10.

                     

                    To configure a floating static route in the web interface navigate to the following:

                    Data > Route Table > Destination Address:  (0.0.0.0) > Destination Mask (0.0.0.0) > Gateway (Address <next hop IP address>) > Administrative Distance <value greater than 1> (typically 10) > Add

                     

                    Therefore, in your application the "next hop IP address" would be the default-gateway IP address the ISP provided you out the "backup" connection.

                     

                    Levi