Tags |
|
|
Links |
|
|
Added for You - Cisco CCNA / CCNP Certification Exam Tutorial: Troubleshooting EIGRP
Career motivation is a great thing to have and if you do not have it, you should work on getting it. You need motivation to get what you want in life and to have the best career that you can have. If you think that you are lacking in motivation, you need to work on it. There are a few tips that will help you get to where you need to be in your career motivation skills. There are a few simple things that you can do to make it a little easier to get where you
The adjacency goes down, and the router's kind enough to tell you that it's the result of the metrics changing. We'll also see that message on R4, but just in case you don't see it, debug eigrp packet will indicate the K-value mismatch as well.
R4#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK)
3w2d: EIGRP: Received HELLO on Ethernet0 nbr 172.12.23.2
3w2d: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
3w2d: K-value mismatch
3w2d: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is down:K-value mismatc
Even if you’re counting on rising property values to eventually make a profit on an investment property, it’s far more desirable to have a positive cash flow each month. If you’re losing money on a property every month, it may not take long until your future profits will have been lost. Owning investment property is much more enjoyable if you’re making money along the way.Here are a couple of ideas for keeping your investment property cash flow in the b
Most adjacency issues are easily resolved - mistyped IP address, bad wildcard mask in the neighbor statement, mistyped EIGRP AS number, and so forth. You know the AS number has to match, but always double-check that. Next, check the wildcard mask to make sure the correct interfaces are EIGRP-enabled. In the following example, we've configured three loopbacks on R2 and want to advertise all three loopbacks via EIGRP, but R4 only sees one.
R2(config)#int loopback1
R2(config-if)#ip address 10.1.1.1 255.255.255.0
R2(config-if)#int loopback2
R2(config-if)#ip address 10.1.2.1 255.255.255.0
R2(config-if)#int loopback3
R2(config-if)#ip address 10.1.3.1 255.255.255.0
R2(config-if)#router eigrp 100
R2(config-router)#no auto
R2(config-router)#network 10.1.1.0 0.0.0.255
R2(config-router)#network 172.12.23.0 0.0.0.255
R4#show ip route eigrp
10.0.0.0/24 is subnetted, 1 subnets
D 10.1.1.0 [90/409600] via 172.12.23.2, 00:00:25, Ethernet0
We know it's not an adjacency issue, because R4 has to have an adjacency to get the route. Perhaps the config on R2 is the problem.
R2(config-if)#router eigrp 100
R2(config-router)#no auto
R2(config-router)#network 10.1.1.0 0.0.0.255
R2(config-router)#network 172.12.23.0 0.0.0.255
The only one of the three networks that matches that network statement is 10.1.1.0 /24. As a result, the networks 10.1.2.0 /24 and 10.1.3.0 /24 will not be advertised.
We could use a network statement with 10.1.0.0 0.0.255.255 to successfully advertise the loopbacks, but by breaking the three networks down into binary, we can see that the three networks have the first 22 bits in common. Therefore, a better wildcard mask to use is 0.0.3.255.
R2(config-router)#no network 10.1.1.0 0.0.0.255
R2(config-router)#network 10.1.0.0 0.0.3.255
R4#show ip route eigrp
10.0.0.0/24 is subnetted, 3 subnets
D 10.1.3.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.2.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.1.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
Another factor that must match between potential EIGRP neighbors is the K-metrics, or metric weights. Let's change the EIGRP metric weights on R2 and watch the effect on its adjacency with R4.
R2(config)#router eigrp 100
R2(config-router)#metric weights 0 1 2 3 4 5 ?
03:33:18: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: metric changed
03:33:20: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: K-value mismatch
The adjacency goes down, and the router's kind enough to tell you that it's the result of the metrics changing. We'll also see that message on R4, but just in case you don't see it, debug eigrp packet will indicate the K-value mismatch as well.
R4#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK)
3w2d: EIGRP: Received HELLO on Ethernet0 nbr 172.12.23.2
3w2d: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
3w2d: K-value mismatch
3w2d: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is down:K-value mismatch
Merchants, particularly those who work through affiliate network, do a reasonable due diligence evaluation of affiliate or publisher sites to make sure they have a reasonable chance of leading to incremental sales, and don’t have the obvious potential to hurt their brand or reputation.For merchants, it’s a numbers game. They need to be sure that they’re receiving value from all their affiliates. A partnership with an affiliate costs the affiliate noth
R2(config-if)#int loopback2
R2(config-if)#ip address 10.1.2.1 255.255.255.0
R2(config-if)#int loopback3
R2(config-if)#ip address 10.1.3.1 255.255.255.0
R2(config-if)#router eigrp 100
R2(config-router)#no auto
R2(config-router)#network 10.1.1.0 0.0.0.255
R2(config-router)#network 172.12.23.0 0.0.0.255
R4#show ip route eigrp
10.0.0.0/24 is subnetted, 1 subnets
D 10.1.1.0 [90/409600] via 172.12.23.2, 00:00:25, Ethernet0
We know it's not an adjacency issue, because R4 has to have an adjacency to get the route. Perhaps the config on R2 is the problem.
R2(config-if)#router eigrp 100
R2(config-router)#no auto
R2(config-router)#network 10.1.1.0 0.0.0.255
R2(config-router)#network 172.12.23.0 0.0.0.255
The only one of the three networks that matches that network statement is 10.1.1.0 /24. As a result, the networks 10.1.2.0 /24 and 10.1.3.0 /24 will not be advertised.
We could use a network statement with 10.1.0.0 0.0.255.255 to successfully advertise the loopbacks, but by breaking the three networks down into binary, we can see that the three networks have the first 22 bits in common. Therefore, a better wildcard mask to use is 0.0.3.255.
R2(config-router)#no network 10.1.1.0 0.0.0.255
R2(config-router)#network 10.1.0.0 0.0.3.255
R4#show ip route eigrp
10.0.0.0/24 is subnetted, 3 subnets
D 10.1.3.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.2.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.1.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
Another factor that must match between potential EIGRP neighbors is the K-metrics, or metric weights. Let's change the EIGRP metric weights on R2 and watch the effect on its adjacency with R4.
R2(config)#router eigrp 100
R2(config-router)#metric weights 0 1 2 3 4 5 ?
03:33:18: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: metric changed
03:33:20: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: K-value mismatch
The adjacency goes down, and the router's kind enough to tell you that it's the result of the metrics changing. We'll also see that message on R4, but just in case you don't see it, debug eigrp packet will indicate the K-value mismatch as well.
R4#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK)
3w2d: EIGRP: Received HELLO on Ethernet0 nbr 172.12.23.2
3w2d: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
3w2d: K-value mismatch
3w2d: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is down:K-value mismatc
The plan in your head seems so simple: bid on keywords on pay-per-click (PPC) engines then watch your business skyrocket. Some marketers do achieve instant success. However, many are losing money because they’ve got gaping holes in their PPC strategy. Don’t overlook the basics.Search engines such as Yahoo! and Google allow you to bid on keywords and drive visitors to your web site for a per-click fee. The Yahoo! Sponsored Search program has a $30 non-r
R2(config-router)#no auto
R2(config-router)#network 10.1.1.0 0.0.0.255
R2(config-router)#network 172.12.23.0 0.0.0.255
The only one of the three networks that matches that network statement is 10.1.1.0 /24. As a result, the networks 10.1.2.0 /24 and 10.1.3.0 /24 will not be advertised.
We could use a network statement with 10.1.0.0 0.0.255.255 to successfully advertise the loopbacks, but by breaking the three networks down into binary, we can see that the three networks have the first 22 bits in common. Therefore, a better wildcard mask to use is 0.0.3.255.
R2(config-router)#no network 10.1.1.0 0.0.0.255
R2(config-router)#network 10.1.0.0 0.0.3.255
R4#show ip route eigrp
10.0.0.0/24 is subnetted, 3 subnets
D 10.1.3.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.2.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.1.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
Another factor that must match between potential EIGRP neighbors is the K-metrics, or metric weights. Let's change the EIGRP metric weights on R2 and watch the effect on its adjacency with R4.
R2(config)#router eigrp 100
R2(config-router)#metric weights 0 1 2 3 4 5 ?
03:33:18: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: metric changed
03:33:20: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: K-value mismatch
The adjacency goes down, and the router's kind enough to tell you that it's the result of the metrics changing. We'll also see that message on R4, but just in case you don't see it, debug eigrp packet will indicate the K-value mismatch as well.
R4#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK)
3w2d: EIGRP: Received HELLO on Ethernet0 nbr 172.12.23.2
3w2d: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
3w2d: K-value mismatch
3w2d: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is down:K-value mismatc
Have you ever read an article and felt a powerful contact with the writer? Just as if that person REALLY understood you and was speaking right to you?It doesn’t often happen with an article. Even less often with a sales letter. But when it does, you find yourself pulling out your credit card.If you can write your copy from a perspective where you can see it from the point of view of the reader, you have an advantage over 99 percent of people w
R4#show ip route eigrp
10.0.0.0/24 is subnetted, 3 subnets
D 10.1.3.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.2.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
D 10.1.1.0 [90/409600] via 172.12.23.2, 00:00:36, Ethernet0
Another factor that must match between potential EIGRP neighbors is the K-metrics, or metric weights. Let's change the EIGRP metric weights on R2 and watch the effect on its adjacency with R4.
R2(config)#router eigrp 100
R2(config-router)#metric weights 0 1 2 3 4 5 ?
03:33:18: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: metric changed
03:33:20: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.4 (Ethernet0) is down: K-value mismatch
The adjacency goes down, and the router's kind enough to tell you that it's the result of the metrics changing. We'll also see that message on R4, but just in case you don't see it, debug eigrp packet will indicate the K-value mismatch as well.
R4#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK)
3w2d: EIGRP: Received HELLO on Ethernet0 nbr 172.12.23.2
3w2d: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
3w2d: K-value mismatch
3w2d: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is down:K-value mismatc
Trying to run a successful online business can be more than just time consuming, it can be financially consuming as well. Wouldn't it be nice to have all of your virtual tools in one toolbox to run your internet empire?For the serious minded netpreneur, certain tools are a must but how to get them affordably without wasting time and valuable resources is a dilemma. Personally, I believe that there are five major areas that need to be dealt with when t
The adjacency goes down, and the router's kind enough to tell you that it's the result of the metrics changing. We'll also see that message on R4, but just in case you don't see it, debug eigrp packet will indicate the K-value mismatch as well.
R4#debug eigrp packet
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK)
3w2d: EIGRP: Received HELLO on Ethernet0 nbr 172.12.23.2
3w2d: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0
3w2d: K-value mismatch
3w2d: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is down:K-value mismatch
The changed K-values will also appear in the running configuration. This is one time when you don't have to depend on debugs to know what the problem is - the router's going to scream at you until you fix it!
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.added4u.com/article/171068/added4u-Cisco-CCNA--CCNP-Certification-Exam-Tutorial--Troubleshooting-EIGRP.html">Cisco CCNA / CCNP Certification Exam Tutorial: Troubleshooting EIGRP</a>
BB link (for phorums):
[url=http://www.added4u.com/article/171068/added4u-Cisco-CCNA--CCNP-Certification-Exam-Tutorial--Troubleshooting-EIGRP.html]Cisco CCNA / CCNP Certification Exam Tutorial: Troubleshooting EIGRP[/url]
Related Articles:
Electronic Check Conversion: Points to Consider
Is Life After Bankruptcy That Bad?
Fast Personal Cash Loans – Instant Finance For Emergency
Bookmark it:
|