i work with an ISP and which have configured eigrp on some of their core routers though it is working normally, i have the following issues always reported to the console and am wondering what to do to correct it. i need expert idears.
the console message
MainRouter# *May 6 12:15:31.444: IP-EIGRP(Default-IP-Routing-Table:18): Neighbor 188.8.131.52 not on common subnet for GigabitEthernet0/1
MainRouter# *May 6 12:15:42.468: IP-EIGRP(Default-IP-Routing-Table:18): Neighbor 184.108.40.206 not on common subnet for GigabitEthernet0/1
asside that am wondering how to make the eigrp routes more preferable than our wirless canopy system which we are using as alternate to the routed network aside changing the bandwith of the eigrp interfaces.
please note that on the routers only the canopy network has been configured with a static route with an administrative distance of 150. thanks.
If your routes are statically set at 150, what does the preferred route look like in the routing table? EIGRP has an AD of 90, so 150 would be less preferred than that, which should mean that your eigrp routes will be preferred over the statics.
the second issue with the routes is that the eigrp table converges well with the eigrp routes prefered over the radio canopy link but without the " ip route 0.0.0.0 0.0.0.0 220.127.116.11 150 ", which is the only static route, connectivity goes down.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...