From: Arun Arumuganainar (aarumuga@hotmail.com)
Date: Tue Jul 12 2005 - 11:48:48 GMT-3
Hi Bill ,
Yes I confirmed this in my lab . Both netmask and inverse mask are the same
!!!
As an alternate we can use this following technique !!! Not sure this will
be a correct approach .
Use distribute prefix list to filter out fa0/0 interface prefixes . I had
the following trace from my router .
===========================================
Topology
~~~~~~~~
E0---R1(S1)----(S1)R2
R1-E0 : 10.1.2.1/24 R1-S1 : 10.1.1.1/24
R1's Config :
~~~~~~~~~
router eigrp 10
network 10.0.0.0
distribute-list prefix test out
auto-summary
!
ip prefix-list test seq 5 deny 10.1.2.0/24
ip prefix-list test seq 10 permit any
================================================
R2 - Eigrp Topology
~~~~~~~~~~~~~~
router2#sh ip eigrp topology
IP-EIGRP Topology Table for AS(10)/ID(10.1.1.2)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 10.1.1.0/24, 1 successors, FD is 2169856
via Connected, Serial1
router2#
=============================================
Important Configuration Notes :
~~~~~~~~~~~~~~~~~~~~~~
1) I have assumed E0 has not been connected to any other router . In case
there another router connected to E0 then R1 will form adjacencies with that
router.In case you wanted to prevent it from happening configure and apply
an access list on e0 to filter out EIGRP hellos .
2) Use only prefix list or extended accesslists in this scenario . Simple
access list ( ACL 1 till 99 ) is a strict no-no here . It will not filter
out properly in this scenario .
Thanks and Regards
Arun
----- Original Message -----
From: "Schulz, Dave" <DSchulz@dpsciences.com>
To: <Bill.McKenzie@bisys.com>; "Arun Arumuganainar " <aarumuga@hotmail.com>
Cc: <ccielab@groupstudy.com>; <nobody@groupstudy.com>; "Spyros Kranis "
<skranis@algosystems.gr>
Sent: Tuesday, July 12, 2005 6:27 PM
Subject: RE: EIGRP Network Statements....excluding interfaces
> That is correct, Bill.
>
> -----Original Message-----
> From: Bill.McKenzie@bisys.com
> To: Arun Arumuganainar
> Cc: ccielab@groupstudy.com; Schulz, Dave; nobody@groupstudy.com; Spyros
Kranis
> Sent: 7/12/2005 8:53 AM
> Subject: Re: EIGRP Network Statements....excluding interfaces
>
> I believe Dave was saying that the requirement was not to use the
> inverse
> mask statement. Please correct me if I'm wrong.
>
>
> Bill
>
> "Exceeding Client Expectations"
>
>
>
>
> "Arun
>
> Arumuganainar"
>
> <aarumuga@hotmail
> To
> .com> "Schulz, Dave"
>
> Sent by: <DSchulz@dpsciences.com>, "Spyros
>
> nobody@groupstudy Kranis "
> <skranis@algosystems.gr>,
> .com <ccielab@groupstudy.com>
>
>
> cc
>
>
> 07/12/2005 08:45
> Subject
> AM Re: EIGRP Network
>
> Statements....excluding
> interfaces
>
>
> Please respond to
>
> "Arun
>
> Arumuganainar"
>
> <aarumuga@hotmail
>
> .com>
>
>
>
>
>
>
>
>
>
> Hi Dave
>
> EIGRP supports both netmask and inverse mask statements .
>
> For example, you could use network 10.1.1.0 255.255.255.252 or network
> 10.1.1.0 0.0.0.3
>
> If inverse mask is not allowed I think you can use net mask format (
> network
> 10.1.1.0 255.255.255.252 )
>
> Hope this helps.
>
> Thanks and Regards
> Arun
>
> ----- Original Message -----
> From: "Schulz, Dave" <DSchulz@dpsciences.com>
> To: "Spyros Kranis " <skranis@algosystems.gr>; <ccielab@groupstudy.com>
> Sent: Tuesday, July 12, 2005 5:55 PM
> Subject: RE: EIGRP Network Statements....excluding interfaces
>
>
> > This is good...however, you specified the inverse mask in the network
> > statement. Is there way to do this without the inverse mask and not
> exclued
> > the Fa0/0?
> >
> > Dave
> >
> > -----Original Message-----
> > From: Spyros Kranis
> > To: Schulz, Dave; ccielab@groupstudy.com
> > Sent: 7/12/2005 8:13 AM
> > Subject: RE: EIGRP Network Statements....excluding interfaces
> >
> > Dave,
> > I think that you can issue the following that I labed it now:
> > Note that I added to lo interfaces from 10.x.x.x network and
> > Enable the eigrp protocol on one of them.
> >
> >
> > R9#c
> > Enter configuration commands, one per line. End with CNTL/Z.
> > R9(config)#int lo 99
> > R9(config-if)#ip address 10.1.1.1 255.255.255.0
> > R9(config-if)#int lo 100
> > R9(config-if)#ip address 10.2.2.2 255.255.255.0
> > R9(config-if)#^Z
> > R9#c
> > Enter configuration commands, one per line. End with CNTL/Z.
> > R9(config)#router ei 1
> > R9(config-router)#no auto-summary
> > R9(config-router)#network 10.1.1.1 0.0.0.0
> > R9(config-router)#^Z
> > R9#sh ip pro
> > *Jul 12 12:00:21.774: %SYS-5-CONFIG_I: Configured from console by
> > console
> > R9#sh ip pro
> > R9#sh ip protocols
> > Routing Protocol is "eigrp 1"
> > Outgoing update filter list for all interfaces is not set
> > Incoming update filter list for all interfaces is not set
> > Default networks flagged in outgoing updates
> > Default networks accepted from incoming updates
> > EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
> > EIGRP maximum hopcount 100
> > EIGRP maximum metric variance 1
> > Redistributing: eigrp 1
> > Automatic network summarization is not in effect
> > Maximum path: 4
> > Routing for Networks:
> > 10.1.1.1/32
> > Routing Information Sources:
> > Gateway Distance Last Update
> > Distance: internal 90 external 170
> >
> > R9#
> >
> > HTH
> >
> > Skra
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Schulz, Dave
> > Sent: Tuesday, July 12, 2005 3:05 PM
> > To: ccielab@groupstudy.com
> > Subject: EIGRP Network Statements....excluding interfaces
> >
> > Team -
> >
> > Is there a way to do this....
> >
> > R1 has two interfaces with 130.10.12.1/24 (BRI0) and 130.10.10.1/24
> > (Fa0/0).
> > The BRI needs to be added to EIGRP, but not Fa0/0. You cannot specify
> > an
> > inverse mask under EIGRP. How is this accomplished? (the goal is to
> > "show
> > ip
> > eigrp topology" to only have the 130.10.12.0 in the table. Possible?
> >
> > I was first thinking using the passive-interface for Fa0/0, but this
> > still
> > allows the Fa0/0 in the topology for eigrp. Or, using a redistribute
> > connected with a route map and only allowing the BRI. The issue is
> here
> > if
> > you
> > do "network 130.10.12.1", eigrp always defaults to 130.10.0.0 and
> > includes
> > both interfaces in the topology. Hmmmmm.
> >
> > Dave
> >
> >
> _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:29 GMT-3