[c-nsp] eigrp questions

[Geoffrey Pendery]

The HSRP address is only virtual, but the 6509 should also have an
actual address on VLAN 2, different from the HSRP address.  It is
probably the .2 or .3 you're seeing in the routing tables.  Issue a
"show int VLAN2" on the 6500 to see its actual address.

HSRP is generally used to provide redundant gateway for host machines
which can't peer with the routing protocol - that .1 address is for
static routes or default gateway settings on servers and workstations,
not for EIGRP.

If you connect the router to both 6509s and run EIGRP, the default
behavior will probably be what you see now - two equal cost routes,
both 6509s.
If you want to force it to use only the first one, then switch to the
second in the event of a failure, you can modify the delay value on
the interfaces, causing EIGRP to prefer one over the other.  This
could have implications in the rest of your EIGRP domain though, as
this delay information will be advertised to others.  If you want to
establish the preference only for this router, or only for particular
routes, you could use floating statics, or even a single static route
to the HSRP address.  Which approach is better depends on more details
in your network.


-Geoff


On Thu, Mar 5, 2009 at 11:50 AM, Leslie Meade <lmeade at signal.ca> wrote:
> I have two 6509's with sup 32 running HRSP and ether channel links
> between them.
>
> On Vlan2 I have two routers, one that handles T1 and the other DMVPN.
>
> All devices have eigrp running. Vlan 2 is my routed network to these
> devices. The HRSP ip on the 6509 is 10.1.2.1
>
>
>
> On my both of my routers that are only connected to one 6509, when I do
> a sh ip route eigrp 100 I get the following.
>
>
>
>  D       10.1.32.0/24 [90/3072] via 10.1.2.3, 1w5d, GigabitEthernet0/0
>
>                                     [90/3072] via 10.1.2.2, 1w5d,
> GigabitEthernet0/0
>
> D EX    10.1.204.0/24 [170/3072] via 10.1.2.3, 1w5d, GigabitEthernet0/0
>
>                                         [170/3072] via 10.1.2.2, 1w5d,
> GigabitEthernet0/0
>
> D EX 192.168.0.0/16 [170/3072] via 10.1.2.3, 1w5d, GigabitEthernet0/0
>
>                                        [170/3072] via 10.1.2.2, 1w5d,
> GigabitEthernet0/0
>
>
>
> vfs-core-r1#sh ip route 10.1.1.6
>
> Routing entry for 10.1.1.0/24
>
>  Known via "eigrp 100", distance 90, metric 3072, type internal
>
>  Redistributing via eigrp 100
>
>  Last update from 10.1.2.2 on GigabitEthernet0/0, 1w5d ago
>
>  Routing Descriptor Blocks:
>
>  * 10.1.2.3, from 10.1.2.3, 1w5d ago, via GigabitEthernet0/0
>
>      Route metric is 3072, traffic share count is 1
>
>      Total delay is 20 microseconds, minimum bandwidth is 1000000 Kbit
>
>      Reliability 255/255, minimum MTU 1500 bytes
>
>      Loading 1/255, Hops 1
>
>    10.1.2.2, from 10.1.2.2, 1w5d ago, via GigabitEthernet0/0
>
>      Route metric is 3072, traffic share count is 1
>
>      Total delay is 20 microseconds, minimum bandwidth is 1000000 Kbit
>
>      Reliability 255/255, minimum MTU 1500 bytes
>
>      Loading 11/255, Hops 1
>
>
>
> My question is how do I change the weighting on the eigrp so that
> 10.1.2.1 is the preferred, then .2 then .3.
>
> The easy answer is to remove the eigrp from the 2nd 6509, but there is a
> move to plug them into the other 6509 for redundancy.
>
>
>
>
>
> Leslie
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>