From: graham@cisco-engineer.com
Date: Thu Apr 19 2007 - 16:52:08 ART
Zack,
Thanks that makes more sense now, it's the way it was worded had me confused
on the matter and the EIGRP packets made it worse, interestingly I have seen
the same with OSPF packets been sent out and interface not included in the
network statement, which was as a result of a leak from a malformed GRE
Tunnel (TAC case was opened but never resolved).
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Zack
(Doc)
Sent: 19 April 2007 20:37
To: ccielab@groupstudy.com
Subject: Re: Passive-Interface Command (EIGRP)
I'm not sure why you saw EIGRP packets on the hub, but the two DocCD
entries are not mutually exclusive, and they are both correct.
The first is simply is saying the EIGRP routing updates and hello
messages will not be sent out that interface. Making it impossible to
form an adjacency.
The second link is saying that while that interface is passive, it's
"disabled" for EIGRP, but EIGRP will still learn the route of that
interface (the network corresponding to it's IP address) and advertise
it into EIGRP.
On 4/19/07, graham@cisco-engineer.com <graham@cisco-engineer.com> wrote:
> Group,
>
>
>
> I am getting some conflicting info from the Doc-CD on the
Passive-interface
> command;
>
>
>
> http://www.cisco.com/univercd
>
<http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/hirp_
> r/rte_eih.htm#wp1000250>
> /cc/td/doc/product/software/ios124/124cr/hirp_r/rte_eih.htm#wp1000250
>
>
>
> The link above states
>
>
>
> Configuring the passive-interface command suppresses all incoming and
> outgoing routing updates and hello messages. EIGRP neighbor adjacencies
> cannot be established or maintained over an interface that is configured
as
> passive. "
>
>
>
> Yet this link;
>
>
>
> http://www.cisco.com/univercd
>
<http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/hirp_
> r/rte_pih.htm#wp1124419>
> /cc/td/doc/product/software/ios124/124cr/hirp_r/rte_pih.htm#wp1124419
>
>
>
> "Enhanced Interior Gateway Routing Protocol (EIGRP) is disabled on an
> interface that is configured as passive although it advertises the route.
"
>
>
>
> Perhaps its me being silly, I always believed the first quote was correct
> for EIGRP, and looking at Debugs on a network would make it true, but then
I
> decided to hub and "ethereal/wireshark" the packets outgoing and saw IP
> protocol 88 being sent (EIGRP)
>
>
>
> Does someone have an authoritative answer on this one?
>
>
>
>
>
> Thanks
>
>
>
> Graham
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:36 ART