Your organization has simply added R3 router to the present community. However at present no routing updates are being exchanged between R3 and the community. All different connectivity, together with Web entry are working correctly.
The duty is to establish the fault(s) and proper the router configuration to supply full connectivity between the routers.
All passwords on all routers are set to cisco.
IP addresses are listed within the chart beneath.
Reply and clarification
We should always verify the configuration of the brand new added router first as a result of it doesn’t operate correctly whereas others work properly. From the command line interface of R3 router, enter the present running-config command
From the output above, we all know that this router was wrongly configured with an autonomous quantity (AS) of twenty-two. When the AS numbers amongst routers are mismatched, no adjacency is fashioned.
(It’s best to verify the AS numbers on different routers for certain)
To unravel this drawback, we merely re-configure router R3 with the next instructions:
R3>allow (you must enter [email protected] as its password right here) R3#configure terminal R3(config)#no router eigrp 22 R3(config)#router eigrp 212 R3(config-router)#community 192.168.60.0 R3(config-router)#community 192.168.77.0 R3(config-router)#no auto-summary R3(config-router)#finish R3#copy running-config startup-config
Verify R1 router with the present running-config command:
Discover that it’s lacking a definition to the community R3. Due to this fact now we have so as to add it in order that it might acknowledge R3 router
R1>allow (you must enter cisco as its password right here) R1#configure terminal R1(config)#router eigrp 212 R1(config-router)#community 192.168.77.0 R1(config-router)#finish R1#copy running-config startup-config
Now the entire community will work properly. It’s best to verify once more with ping command from router R3 to different routers!
Perhaps on this EIGRP Sim you will note the “passive-interface …” command someplace in R1 configuration. If the hyperlink between R1 to R2; or R1 to R3; or R1 to R4) routers has the “passive interface” then now we have to take away it with the “no passive-interface …” command as a result of it prevents EIGRP replace from being despatched on that interface. But when the “passive interface” is utilized to the hyperlink between R1 and ISP router like this:
router eigrp 212
then we simply go away it. Don’t use the “no passive-interface s1/0” on R1 as a result of the hyperlink between R1 & ISP doesn’t want EIGRP to run on it. A static route from R1 to ISP & “ip default-network” command in R1 are right so that each one the routers (R1, R2, R3, R4) can entry the Web.
(Notice: The “ip default-network” command in R1 will promote the static route of R1 (to go to the Web) to different routers (R2,R3,R4) in order that they’ll entry the Web too). Within the examination you will note these traces in R1 configuration:
ip default-network 220.127.116.11
ip route 0.0.0.0 0.0.0.0 18.104.22.168
If you wish to study extra about “ip default-network” command please learn: http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094374.shtml
I learn current feedback and realized that you will note the “passive-interface” within the hyperlink between R1 & ISP router so simply go away it.
Notice: Additionally some readers confuse about if we should always use the wildcard masks on the “community” statements underneath EIGRP course of or not. For instance ought to we use:
router eigrp 212
community 192.168.77.0 0.0.0.3
The reply is: we are able to use wildcard masks or not, it doesn’t matter. Not having a wildcard masks doesn’t make the routes conflicting. The “community …” command in EIGRP (and OSPF, RIP) doesn’t means “promote this community” however means “If I has interface(s) belongs to this community please activate EIGRP on that interface. Due to this fact if you don’t use wildcard masks EIGRP will activate EIGRP on all interfaces that belongs to the community you specify within the “community …” command.
It’s best to solely use wildcard masks on EIGRP when you have 2 or extra interfaces that belong to the identical main networks however you don’t need to run EIGRP on all of them. For instance in case your router has 2 interfaces whose IP addresses are 192.168.30.1/28 and 192.168.30.17/28 however you solely need to run EIGRP on the primary interface, you’ll be able to sort “community 192.168.30.0 0.0.0.15” underneath EIGRP course of.