RE: EIGRP and secondary IP Addresses

From: Dennis J. Hartmann (dennisjhartmann@hotmail.com)
Date: Tue Sep 13 2005 - 14:01:44 GMT-3


        I re-configured this in the lab and like Ralph is mentioning, it's
working. Error was on my side.

        Does anyone have a summary of the issues/workarounds of peering to
secondary addresses with various routing protocols? I believe the fix is by
using a common bridge-group and applying an IP address to the BVI interface,
but I'm not 100% on this.

Sincerely,
 
Dennis J. Hartmann
 

-----Original Message-----
From: Ralph [mailto:Mandela@myrealbox.com]
Sent: Monday, September 12, 2005 11:29 PM
To: dennisjhartmann@hotmail.com
Cc: ccielab@groupstudy.com
Subject: Re: EIGRP and secondary IP Addresses

Dennis,

Here is a sample config, when I try to advertise a secondary address into
eigrp using network statements.

R3:
interface Loopback2
 ip address 148.6.11.11 255.255.255.0 secondary ip address 150.6.33.33
255.255.255.0 !

R5: (from sh ip route)
D 148.6.11.0/24 [90/2297856] via 148.6.35.3, 00:05:31, Serial0/0

R5#PING 148.6.11.11

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 148.6.11.11, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms

I observed that on loopbacks and ethernet interfaces eigrp is able to
advertise secondary addresses fine, but on NBMA interfaces, you have to
disable split-horizon to advertise the secondary address.

Regards
Ralph

-----Original Message-----
From: "Dennis J. Hartmann" <dennisjhartmann@hotmail.com>
To: <ccielab@groupstudy.com>
Date: Mon, 12 Sep 2005 22:09:13 -0400
Subject: EIGRP and secondary IP Addresses

    My understanding is that EIGRP can not have a neighbor relationship
and/or advertise a secondary IP Address on an interface. I tested this by
trying to advertise a secondary IP Address on a Loopback interface trying
both the network command and trying to do a redistribute connected with a
route-map that matched on the Loopback interface only. Neither method
worked. In this type of scenario, I believe one would be forced into using
the auto-summary option in the EIGRP routing protocol process OR use the ip
summary-address command on an interface. Opinons and/or comments
welcome.....
 

Sincerely,

 

Dennis J. Hartmann



This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:15 GMT-3