check it out, and hope it helps...
passive stops the hellos from being sent and kills the neighborship...
but the network command adds that interface IP into the routing process...
you also have redistributed connected which sends the IP into the routing
information base of the routing process but it is not a part of the
configured routing process, and will show up at EX route on neighbor (see
the output of the neighbor i put in using an R2 i setup hanging off F0/0)
see output below and look for Routing for Networks:
R1#sh ip protocols
Routing Protocol is "eigrp 2004"
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: connected, eigrp 2004
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
150.100.24.0/24
150.100.40.0/23
200.0.0.4/32
Passive Interface(s):
FastEthernet0/0
FastEthernet0/1
Serial0/1
Loopback0
VoIP-Null0
Routing Information Sources:
now take out the network statement for loopback0 200.0.0.4/32:
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#router eigrp 2004
R1(config-router)#no network 200.0.0.4 0.0.0.0
R1(config-router)#do sh ip protocols
Routing Protocol is "eigrp 2004"
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: connected, eigrp 2004
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
150.100.24.0/24
150.100.40.0/23
Passive Interface(s):
FastEthernet0/0
FastEthernet0/1
Serial0/1
Loopback0
VoIP-Null0
Routing Information Sources:
Gateway Distance Last Update
Distance: internal 90 external 170
NEIGHBOR R2 with redistributed connected:
R2#sh ip route
200.0.0.0/32 is subnetted, 1 subnets
D EX 200.0.0.4 [170/409600] via 150.100.40.4, 00:00:06, FastEthernet0/0
150.100.0.0/24 is subnetted, 2 subnets
C 150.100.40.0 is directly connected, FastEthernet0/0
D 150.100.41.0 [90/307200] via 150.100.40.4, 00:00:06, FastEthernet0/0
NEIGHBOR R2 with network command for loopback0 200.0.0.4:
R2#sh ip route
200.0.0.0/32 is subnetted, 1 subnets
D 200.0.0.4 [90/409600] via 150.100.40.4, 00:00:07, FastEthernet0/0
150.100.0.0/24 is subnetted, 2 subnets
C 150.100.40.0 is directly connected, FastEthernet0/0
D 150.100.41.0 [90/307200] via 150.100.40.4, 00:04:57, FastEthernet0/0
--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
On Sun, Aug 1, 2010 at 9:36 PM, Jay McMickle <[email protected]> wrote:
> While working on WB1, Lab 9.7, EIGRP, I'm wondering why we should list
> networks that the intereface has be put into EIGRP passive mode?
>
> Passive mode disables the EIGRP neighbor process, and the network statement
> specifies which interface to enable the EIGRP process. So, why list the
> other networks with network statements if their interface has been marked as
> passive?
>
> !
> interface Loopback0
> ip address 200.0.0.4 255.255.255.255
> !
> interface FastEthernet0/0
> ip address 150.100.40.4 255.255.255.0
> duplex auto
> speed auto
> !
> interface FastEthernet0/1
> ip address 150.100.41.4 255.255.255.0
> duplex auto
> speed auto
> !
> interface Serial0/0/0
> bandwidth 64
> ip address 150.100.24.4 255.255.255.0
> encapsulation frame-relay
> no fair-queue
> frame-relay lmi-type cisco
> !
> router eigrp 2004
> passive def
> no passive-interface s0/0/0
> no auto-summary
> redistribute connected
> network 150.100.24.0 0.0.0.255
> network 200.0.0.4 0.0.0.0
> network 150.100.40.0 0.0.1.255
>
>
> Regards,
> Jay McMickle- CCNP, CCSP, MCSE
>
>
>
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
