Re: Summarization problem

From: Donny MATEO (donny.mateo@sg.ca-indosuez.com)
Date: Sun Sep 15 2002 - 05:45:38 GMT-3


Hi Hunt,
I did this once. Use a summary-address command on R2. Ok, the guide said u can only do that on ASBR,
but I found it to be working on this particular scenario (haven't tried on other). After that check
that only the summarized route is sent to R1. Let me know what you got.
Best Regards
Donny

                                                                                                                                       
                      Hunt Lee
                      <ciscoforme3@yaho To: ccielab@groupstudy.com
                      o.com.au> cc:
                      Sent by: Subject: Summarization problem
                      nobody@groupstudy
                      .com
                                                                                                                                       
                                                                                                                                       
                      15-09-2002 14:01
                      Please respond to
                      Hunt Lee
                                                                                                                                       
                                                                                                                                       

ALL,

I just got a weird one. I dunno if it's IOS related or not, anyway,
here's the topology.

R1 -- OSPF (Area 0) -- R2 -- OSPF (Area 3 NSSA) --- R3 --- EIGRP -- R4

I have 3 EIGRP networks that are being injected into R3 from R4
(20.2.0.0/16, 20.3.0.0/16 & 20.4.0.0/16), and I can see them all at R2
as O N2 routes. I want to summarzie them before they are injected into
Area 0. So I use the "area 3 range" command at R2 (NSSA ABR & Area 0
ABR)

router ospf 1
 log-adjacency-changes
 area 3 nssa
 area 3 range 20.0.0.0 255.248.0.0
 network 172.16.1.0 0.0.0.255 area 3
 network 192.168.1.0 0.0.0.255 area 0

But then when I checked the Routing Table at R1, all those 20.x.0.0
routes still appears as their own routes, and the summary route
(20.0.0.0/13) aren't even there.

R1#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route

Gateway of last resort is not set

     20.0.0.0/16 is subnetted, 3 subnets
O E2 20.4.0.0 [110/20] via 192.168.1.1, 00:49:03, Serial0
O E2 20.2.0.0 [110/20] via 192.168.1.1, 00:49:03, Serial0
O E2 20.3.0.0 [110/20] via 192.168.1.1, 00:49:03, Serial0
     5.0.0.0/24 is subnetted, 1 subnets
O E2 5.5.5.0 [110/20] via 192.168.1.1, 00:49:03, Serial0
     172.16.0.0/24 is subnetted, 1 subnets
O IA 172.16.1.0 [110/128] via 192.168.1.1, 00:49:26, Serial0
     10.0.0.0/30 is subnetted, 1 subnets
O E2 10.1.1.4 [110/20] via 192.168.1.1, 00:49:27, Serial0
     11.0.0.0/32 is subnetted, 1 subnets
C 11.1.1.1 is directly connected, Loopback0
C 192.168.1.0/24 is directly connected, Serial0
R1#

Another funny stuff I found is when I used "show ip ospf" on R2, it has
a "passive advertise" that I haven't seen before. Does it mean
anything?

R2#sh ip ospf
 Routing Process "ospf 1" with ID 1.1.1.1
 Supports only single TOS(TOS0) routes
 Supports opaque LSA
 It is an area border and autonomous system boundary router
 Redistributing External Routes from,
 SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
 Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
 Number of external LSA 5. Checksum Sum 0x38D59
 Number of opaque AS LSA 0. Checksum Sum 0x0
 Number of DCbitless external and opaque AS LSA 0
 Number of DoNotAge external and opaque AS LSA 0
 Number of areas in this router is 2. 1 normal 0 stub 1 nssa
 External flood list length 0
    Area BACKBONE(0)
        Number of interfaces in this area is 1
        Area has no authentication
        SPF algorithm executed 7 times
        Area ranges are
        Number of LSA 3. Checksum Sum 0xBED7
        Number of opaque link LSA 0. Checksum Sum 0x0
        Number of DCbitless LSA 0
        Number of indication LSA 0
        Number of DoNotAge LSA 0
        Flood list length 0
    Area 3
        Number of interfaces in this area is 1
        It is a NSSA area
        Perform type-7/type-5 LSA translation
        Area has no authentication
        SPF algorithm executed 9 times
        Area ranges are
           20.0.0.0/13 Passive Advertise <--- what does this mean?
        Number of LSA 8. Checksum Sum 0x42B10
        Number of opaque link LSA 0. Checksum Sum 0x0
        Number of DCbitless LSA 0
        Number of indication LSA 0
        Number of DoNotAge LSA 0
        Flood list length 0

R2#

thx
Hunt

http://mobile.yahoo.com.au - Yahoo! Messenger for SMS
- Always be connected to your Messenger Friends

This message is for information purposes only and its content
should not be construed as an offer, or solicitation of an offer,
to buy or sell any banking or financial instruments or services
and no representation or warranty is given in respect of its
accuracy, completeness or fairness. The material is subject
to change without notice. You should take your own independent
tax, legal and other professional advice in respect of the content
of this message. This message may contain confidential or
legally privileged material and may not be copied, redistributed
or published (in whole or in part) without our prior written consent.
This email may have been intercepted, partially destroyed,
arrive late, incomplete or contain viruses and no liability is
accepted by any member of the Credit Agricole Indosuez group
as a result. If you are not the intended recipient of this message,
please immediately notify the sender and delete this message
from your computer.



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:52 GMT-3