From: Earl Aboytes (earl@xxxxxxxxxxxx)
Date: Fri Aug 25 2000 - 11:37:28 GMT-3
The trick here is to not put the loopback into any area. Use a redistribute
connected and use a restrictive route-map. Then you can use the
summary-address command.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Earl Aboytes CCIE #6097
Senior Technical Consultant
GTE Managed Solutions
805-381-8817
earl.aboytes@verizon.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]
Sent: Friday, August 25, 2000 8:24 AM
To: Simon Baxter; CCIE Group Study (E-mail)
Subject: RE: 2nd attempt at a question!!
I forgot, you could also put them into there own area and
summarize into area 0 as whatever mask you choose. 'Area 5 range 120.1.1.0.0
255.255.0.0' would take a loop of 120.1.1.1 /32 and advertise it to other
areas as 120.1.0.0 /16.
-----Original Message-----
From: nobody@groupstudy.com
[mailto:nobody@groupstudy.com] On Behalf Of Simon Baxter
Sent: Friday, August 25, 2000 9:51 AM
To: CCIE Group Study (E-mail)
Subject: 2nd attempt at a question!!
I'm doing a test lab which has asked me if there's
any way to advertise routes to loopback interfaces as anything but /32
routes.
I can't see any way around this :
Link connected to: a Stub Network
(Link ID) Network/subnet number: 130.130.33.1
(Link Data) Network Mask: 255.255.255.255
Number of TOS metrics: 0
TOS 0 Metrics: 1
R4#sh ip os int lo0
Loopback0 is up, line protocol is up
Internet Address 130.130.33.1/24, Area 0.0.0.0
Process ID 10, Router ID 130.130.33.1, Network
Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
R4#
No matter what I do, it always stays as "Loopback
interface is treated as a stub Host"
Is this a trick question???
I'm losing WAY too much sleep over it..
Simon
winmail.dat
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:30 GMT-3