We have a primary 10Meg fiber connection with a backup ADSL connection for redundancy
Standalone sites are smaller. These locations do not usually have as much network traffic and therefore do not need the capacity that the fiber connection provides. As such, these sites use ADSL as their primary connection and have a dedicated internet connection for when they fail over.
Our fiber network 192.168.10.0/24 connects each of the full centres to head office and all routes are identified via EIGRP. When one or more of these sites goes down, EIGRP identifies the ADSL network as the best route to the store as the fiber route disappears from EIGRP.
Our ADSL network is 192.168.11.0/24. This network designed required us to have a default gateway of 192.168.11.100 ( which is a third party system and don't have access) that routes all traffic to the appropriate destination via EIGRP. This network also depends on EIGRP for getting traffic from head office to each site.
The problem that we are facing is that EIGRP is changing the route on a fairly regular basis, switching between sending the traffic directly to head office via the ADSL network and sending the traffic to another location via the ADSL network and then to head office via that locations fiber network. I believe that because this traffic is taking different routes to head office than they are taking back to the location. Anybody has any idea how can I can configure my remote sites to make sure it doesn't take different path to reach head office.
Do you have the option enabled to log EIGRP neighbor changes? If not, I would suggest that you do enable this option.
After the option is enabled I would suggest that you look on the routers both for the head end and for the remote and see whether there are any log messages about neighbor changes. If neighbor relationship is going down and then back up this would explain the difference in how traffic is being routed.
I am confused. The original post talked about running EIGRP on networks 192.168.10.0 and on 192.168.11.0 The output in this post is showing EIGRP neighbors up and down in 192.168.1.0. So what is the relationship between 192.168.1.0 and the other 2 networks?
The EIGRP output here shows neighbors failing because of holding time expired. Holding time expired indicates that the router stopped receiving Hello messages from the neighbor. Since there are no time stamps in the log output we can not tell how frequently this is happening. But not receiving Hello messages could very well be caused by packets being dropped on the link connected to the interface. What is FastEth0/1 connected to?
One way to test this would be to run a ping with lots of packets to one of the neighbors in the output and to look for how many time there is no response to the ping.
If you increase the hold timer it would slow down the incidence of flaps. That may help with the symptoms but it does not address the underlying problem.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...