From: Scott Morris (swm@emanon.com)
Date: Thu Oct 27 2005 - 01:17:37 GMT-3
I'm not sure where you're trying to go with this...
You can have other neighbors just fine, but the thing you posted talked
about over the NBMA network...
"ensure that R1 does not accept any EIGRP packets on the NBMA Interface"
So I understand where you were going with the distance 255 as that would
kill any routes the other side would give you. Or the distribute-list
gateway someone else mentioned. But what are you trying to do with the K
values? I'm not getting it.
K values are meant to change how you (and all neighbors) calculate metrics.
Everyone must be the same. If you aren't, the router complains about it and
won't peer.
??
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Victor Cappuccio
Sent: Wednesday, October 26, 2005 11:06 PM
Cc: 'Cisco certification'
Subject: Re: is this acceptable?
Hello,
But I'm receiving the routes, now I know after thinking real hard in the Why
of the IE lab Wording, I understand that my solution is not bad, but if I
have any other trusted neighbors that I should receive routes, I'm going to
have an administrative pain in a growing organization.
Rack1R6#show ip route eigrp
D 200.0.0.0/24 [90/5620069] via 54.1.6.254, 01:39:12, Serial0/0
191.1.0.0/16 is variably subnetted, 15 subnets, 3 masks
D 191.1.4.0/24 [90/867251276] via 191.1.46.4, 01:07:29, Tunnel0
D 191.1.0.0/16 is a summary, 01:07:33, Null0
54.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D 54.0.0.0/8 is a summary, 01:07:33, Null0
D 200.0.1.0/24 [90/5620069] via 54.1.6.254, 01:39:12, Serial0/0
D 200.0.2.0/24 [90/5620069] via 54.1.6.254, 01:39:12, Serial0/0
D 200.0.3.0/24 [90/5620069] via 54.1.6.254, 01:39:12, Serial0/0
Rack1R6#show ip eigrp neighbors
IP-EIGRP neighbors for process 10
H Address Interface Hold Uptime SRTT RTO Q
Seq Type
(sec) (ms) Cnt Num
1 191.1.46.4 Tu0 12 01:07:42 144 5000 0
10 ****************************** TRUSTED NEIGHBOR..
0 54.1.6.254 Se0/0 13 01:39:24 32 200 0
5
Rack1R6#show run | b eigrp 10
router eigrp 10
network 54.0.0.0
network 191.1.46.0 0.0.0.255
metric weights 0 3 1 1 1 0
auto-summary
Scott Morris wrote:
>IMHO, the key would be "accept any packets". In your method, you
>aren't accepting any ROUTES, but you do have an EIGRP neighbor
>relationship and therefore are getting packets.
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>Victor Cappuccio
>Sent: Wednesday, October 26, 2005 8:18 PM
>To: Cisco certification
>Subject: is this acceptable?
>
>Hello All,
>
>If I have a EIGRP neighbor relationship between 2 Routers in a NBMA
>Network in AS 10, and the wording indicates that In order to prevent
>routing issues over this Network, ensure that R1 does not accept any
>EIGRP packets on the NBMA Interface
>
>Ok the topology is like this
>
>R1 --| NBMA |-- R2
>
>I think that a valid solution could be:
>
>Rack1R1#show run | be router eigrp
>router eigrp 10
>network 54.0.0.0
>metric weights 0 3 1 1 1 0
>distance 90 54.1.6.254 0.0.0.0
>! Where 54.1.6.254 is Router 2
>distance 255 0.0.0.0 255.255.255.255
>! Deny every thing to be installed in the Rtable.
>no auto-summary
>
>The solution that appers in the WB (IE Lab 5 Tasks 5.23-5.25.-I'm not
>saying that is wrong)
>
>access-list 102 permit eigrp host 54.1.6.254 any access-list 102 deny
>eigrp any any access-list 102 permit ip any any log
>
>interface Serial0/0
>ip address 54.1.6.6 255.255.255.0
>ip access-group 102 in
>
>So my question now if the First method is acceptable?
>Regards
>Victor.
>
>--
>Victor Cappuccio
>cvictor@protokolgroup.com
>.O.
>..O
>OOO
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
-- Victor Cappuccio cvictor@protokolgroup.com .O. ..O OOO
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:54 GMT-3