I tried serial back-to-back instead of frame relay, but got same result, the
show ip ospf nei resulted the same as yours.
Instead of assigning ip directly to s0 and s1, I put on loopback 1 and 2,
then on s0 and s1, do ip unumber loopback 1 and 2 (although for ospf, it's
not supposed to put one end unnumbered but the other end not), and I got the
result!!! Tow O*N2 entries.
I also tried the following senario:
R1(ASBR)
| (Area 0)
|
R2(ABR)
/ \ (Area 1)
/ \
R3 R4
\ /
\ /
R5
With normal configuration, I only can see one O*N2 entry on R5, but with ip
unnumbered with serail ports on R2, I can see both O*N2 0.0.0.0/0 using R3
and R4.
I am really confused. With regular ospf area, stubby, totally stubby, it
works fine, just doesn't like the NSSA.
I checked RFC 2328, the differece between unnumbered and ip assigned
point-to point is the Link Data info in LSA, is that which causes the problem?
Chuck, thank you very much for you help, BTW, can you give me your IOS
version? (Hopefully I am not tired yet of another try)
Wei
----- Original Message -----
From: "The Long and Winding Road"
To:
Sent: Friday, January 03, 2003 11:30 PM
Subject: Re: revisited: OSPF stub/stub no-summary O*IA routing table
[7:60278]
> ""Wei Zhu"" wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Hi Chuck,
> > I tried point-to-point instead of frame relay and still could not get
> > through.(Everything is fine except nssa)
> > In my understanding, the External type LSA (E1 or E2) will flood
> everywhere,
> > while for NSSA area, it change from type 5 to type 7.
>
> I'm not sure, but I believe that for routes INTO an NSSA, type 5's are
> blocked, not changed to type 7. The ABR will change type 7's to type 5's
OUT
> of the NSSA ( into the rest of OSPF ) yeah - looking at the RFC, that's
what
> it states - external type-5's are not imported into the NSSA
>
>
> When I tried "show ip
> > ospf database external" on R2, I could see the LSA with forward address
> > 0.0.0.0, but on R5, the forward address changed to 192.168.1.33(or
> > 192.168.1.17). How did this happen? I think that's the reason why I only
> can
> > see on O*N2 entry insteady of 2. I am using 2500 serial routers.
> >
>
> For this experiment, I used 2500 routers as well.
>
> when you do the show ip ospf neighbors, do you see neighbor relationships
> over both links?
>
> Router_8#o nei
>
> Neighbor ID Pri State Dead Time Address Interface
> 222.222.222.9 1 FULL/ - 00:00:36 192.168.1.34 Serial1
> 222.222.222.9 1 FULL/ - 00:00:36 192.168.1.18 Serial0
> Router_8#
>
> the relevant results from my show ip ospf database:
>
> Router 9 ( area border router )
>
> Router_9#o data
>
> OSPF Router with ID (222.222.222.9) (Process ID 200)
>
> Router Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum Link count
> 222.222.222.9 222.222.222.9 1595 0x80000011 0xAF01 1
> 222.222.222.10 222.222.222.10 1873 0x8000000E 0x941F 1
>
> Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 10.1.1.1 222.222.222.10 1873 0x8000000D 0xE14C
>
> Summary Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 192.168.1.16 222.222.222.9 595 0x80000010 0x1BC1
> 192.168.1.32 222.222.222.9 595 0x80000010 0x7A52
> 192.168.1.48 222.222.222.9 1595 0x8000000C 0xEBD3
> 192.168.1.64 222.222.222.9 1595 0x8000000C 0x4B64
>
> Router Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum Link count
> 222.222.222.8 222.222.222.8 1468 0x80000013 0x6FB2 6
> 222.222.222.9 222.222.222.9 1598 0x8000001A 0x2E31 4
>
> Summary Net Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum
> 10.1.0.0 222.222.222.9 1598 0x80000010 0xCBA1
>
> Type-7 AS External Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum Tag
> 0.0.0.0 222.222.222.9 1598 0x8000000C 0xDB25 0
>
> Type-5 AS External Link States
>
> Link ID ADV Router Age Seq# Checksum Tag
> 172.16.10.0 222.222.222.10 627 0x8000000E 0xB86D 0
> 172.16.11.0 222.222.222.10 627 0x8000000E 0xAD77 0
> Router_9#
>
> AND from router 8 ( the router that is NSSA only )
>
> Router_8#o data
>
> OSPF Router with ID (222.222.222.8) (Process ID 200)
>
> Router Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum Link count
> 222.222.222.8 222.222.222.8 1666 0x80000013 0x6FB2 6
> 222.222.222.9 222.222.222.9 1795 0x8000001A 0x2E31 4
>
> Summary Net Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum
> 10.1.0.0 222.222.222.9 1795 0x80000010 0xCBA1
>
> Type-7 AS External Link States (Area 1)
>
> Link ID ADV Router Age Seq# Checksum Tag
> 0.0.0.0 222.222.222.9 1795 0x8000000C 0xDB25 0
> Router_8#
>
> As I said, I can't duplicate the problem. I keep coming back to a frame
> relay issue 9 but for the life of my I can't see why. are the subinterfaces
> point-to-point? ) or artifact.
>
> have you blown away the config, reloaded, then started from scratch? hate
to
> suggest the microsoft answer, but I am at a loss.
>
> HTH
>
> Chuck
>
>
> > Thanks
> > Wei
> > ----- Original Message -----
> > From: "The Long and Winding Road"
> > To:
> > Sent: Friday, January 03, 2003 4:59 PM
> > Subject: revisited: OSPF stub/stub no-summary O*IA routing table entry
> > [7:60242]
> >
> >
> > > hope you don't mind me bringing this back public. I saw no other
> responses
> > > and I was curious so I've done some further research based on your
> > > configuration. The major difference in my setup and yours is frame
> relay. I
> > > am using two point-to-point serial links. too complicated for me to
tear
> > > down my current setup to emulate your frame.
> > >
> > > methodology:
> > >
> > > 1) set everything up as best I can based on your configurations. At
this
> > > point, just plain old ordinary OSPF areas.
> > >
> > > C 222.222.222.8 is directly connected, Loopback1001
> > > 172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
> > > O E2 172.16.10.0/24 [110/20] via 192.168.1.18, 00:04:47, Serial0
> > > [110/20] via 192.168.1.34, 00:04:47, Serial1
> > > O E2 172.16.11.0/24 [110/20] via 192.168.1.18, 00:04:47, Serial0
> > > [110/20] via 192.168.1.34, 00:04:47, Serial1
> > > 10.0.0.0/16 is subnetted, 1 subnets
> > > O IA 10.1.0.0 [110/74] via 192.168.1.34, 00:04:48, Serial1
> > > [110/74] via 192.168.1.18, 00:04:48, Serial0
> > > 192.168.1.0/28 is subnetted, 4 subnets
> > > C 192.168.1.64 is directly connected, Loopback2
> > > C 192.168.1.32 is directly connected, Serial1
> > > C 192.168.1.48 is directly connected, Loopback1
> > > C 192.168.1.16 is directly connected, Serial0
> > > Router_8#
> > >
> > > as you can see, all routes are shown as reachable via both of the
serial
> > > ports.
> > >
> > > 2) turn area 1 into a stub area:
> > >
> > > 10.0.0.0/16 is subnetted, 1 subnets
> > > O IA 10.1.0.0 [110/74] via 192.168.1.34, 00:01:50, Serial1
> > > [110/74] via 192.168.1.18, 00:01:50, Serial0
> > > 192.168.1.0/28 is subnetted, 4 subnets
> > > C 192.168.1.64 is directly connected, Loopback2
> > > C 192.168.1.32 is directly connected, Serial1
> > > C 192.168.1.48 is directly connected, Loopback1
> > > C 192.168.1.16 is directly connected, Serial0
> > > O*IA 0.0.0.0/0 [110/65] via 192.168.1.34, 00:01:51, Serial1
> > > [110/65] via 192.168.1.18, 00:01:51, Serial0
> > > Router_8#
> > >
> > > exactly as expected. the two external routes in the 172 range are not
> > passed
> > > into the stub area.
> > >
> > > 3) turn area 1 into a totally subby area ( love that term! I can still
> hear
> > > my ACRC instructor intoning it just like a Valley Girl )
> > >
> > > show ip ospf
> > >
> > > Area 1
> > > Number of interfaces in this area is 2
> > > It is a stub area, no summary LSA in this area
> > > generates stub default route with cost 1
> > >
> > > 192.168.1.0/28 is subnetted, 4 subnets
> > > C 192.168.1.64 is directly connected, Loopback2
> > > C 192.168.1.32 is directly connected, Serial1
> > > C 192.168.1.48 is directly connected, Loopback1
> > > C 192.168.1.16 is directly connected, Serial0
> > > O*IA 0.0.0.0/0 [110/65] via 192.168.1.34, 00:01:01, Serial1
> > > [110/65] via 192.168.1.18, 00:01:01, Serial0
> > > Router_8#
> > >
> > > again - everything is as expected
> > >
> > > 4) change from totally stubby to NSSA ( kinda sorta stubby :-> )
> > >
> > > router ospf 200
> > > log-adjacency-changes
> > > area 1 nssa
> > > network 10.0.0.0 0.255.255.255 area 0
> > > network 192.168.1.0 0.0.0.255 area 1
> > > !
> > >
> > > 10.0.0.0/16 is subnetted, 1 subnets
> > > O IA 10.1.0.0 [110/74] via 192.168.1.34, 00:00:25, Serial1
> > > [110/74] via 192.168.1.18, 00:00:25, Serial0
> > > 192.168.1.0/28 is subnetted, 4 subnets
> > > C 192.168.1.64 is directly connected, Loopback2
> > > C 192.168.1.32 is directly connected, Serial1
> > > C 192.168.1.48 is directly connected, Loopback1
> > > C 192.168.1.16 is directly connected, Serial0
> > > Router_8#
> > >
> > > again - completely as expected. the inter-area route in the 10. network
> is
> > > seen, but the two external routes in the 172 network are not seen.
> > >
> > > 5) tweak the NSSA
> > >
> > > router ospf 200
> > > log-adjacency-changes
> > > area 1 nssa default-information-originate
> > > network 10.0.0.0 0.255.255.255 area 0
> > > network 192.168.1.0 0.0.0.255 area 1
> > > !
> > >
> > > 10.0.0.0/16 is subnetted, 1 subnets
> > > O IA 10.1.0.0 [110/74] via 192.168.1.34, 00:00:01, Serial1
> > > [110/74] via 192.168.1.18, 00:00:01, Serial0
> > > 192.168.1.0/28 is subnetted, 4 subnets
> > > C 192.168.1.64 is directly connected, Loopback2
> > > C 192.168.1.32 is directly connected, Serial1
> > > C 192.168.1.48 is directly connected, Loopback1
> > > C 192.168.1.16 is directly connected, Serial0
> > > O*N2 0.0.0.0/0 [110/1] via 192.168.1.34, 00:00:02, Serial1
> > > [110/1] via 192.168.1.18, 00:00:02, Serial0
> > > Router_8#
> > >
> > >
> > > as you can see, step by step, I get the expected result every time.
> > >
> > > variables - things that differ in my setup -
> > >
> > > 1) point-to-point serial links instead of frame relay
> > >
> > > 2) secondary address in the ethernet port of the area 1 router - R8 in
> my
> > > case, R3 in your case. I use loopbacks instead.
> > >
> > > So - I am unable to duplicate your problem in my setup. you don't
> indicate
> > > the configurations of the interfaces, but I am now thinking something
in
> > > your frame relay setup. I did not see anything resembling this problem
> in
> > > the TAC bug database. Not that I read all of them :->
> > >
> > > I don't have a solution, but I certainly admire the problem.
> > >
> > > Chuck
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Wei Zhu"
> > > To: "The Long and Winding Road"
> > > Sent: Thursday, 02 January, 2003 7:48 PM
> > > Subject: Re: OSPF stub/stub no-summary O*IA routing table entry
> [7:60088]
> > >
> > >
> > > > Thank you Chuck. Finally it worked with totally stubby, but this time
> the
> > > nssa didn't work, I tried several times, upgraded IOS to 12.2.13. Here
I
> > > gave some brief configuration, the interface configuration are all
> > > frame-relay subinterface point-to point .
> > > >
> > > > The router configuration on R1:
> > > > router ospf 200
> > > > log-adjacency-changes
> > > > redistribute connected subnets route-map passext
> > > > network 10.0.0.0 0.255.255.255 area 0
> > > > !
> > > > ip classless
> > > > no ip http server
> > > > !
> > > > access-list 1 permit 172.16.10.0
> > > > access-list 1 permit 172.16.11.0
> > > > route-map passext permit 10
> > > > match ip address 1
> > > >
> > > > The router configuration on R2:
> > > > router ospf 200
> > > > log-adjacency-changes
> > > > area 1 nssa default-information-originate
> > > > network 10.0.0.0 0.255.255.255 area 0
> > > > network 192.168.1.0 0.0.0.255 area 1
> > > >
> > > > The router configuration on R3:
> > > > router ospf 200
> > > > log-adjacency-changes
> > > > area 1 nssa
> > > > network 192.168.1.0 0.0.0.255 area 1
> > > >
> > > > The show ip route on R3:
> > > > Gateway of last resort is 192.168.1.33 to network 0.0.0.0
> > > >
> > > > 10.0.0.0/24 is subnetted, 2 subnets
> > > > O IA 10.2.2.0 [110/4686] via 192.168.1.33, 00:00:01, Serial0.312
> > > > [110/4686] via 192.168.1.17, 00:00:01, Serial0.302
> > > > O IA 10.1.1.0 [110/3124] via 192.168.1.33, 00:00:01, Serial0.312
> > > > [110/3124] via 192.168.1.17, 00:00:01, Serial0.302
> > > > 192.168.1.0/28 is subnetted, 4 subnets
> > > > C 192.168.1.64 is directly connected, Ethernet0
> > > > C 192.168.1.32 is directly connected, Serial0.312
> > > > O 192.168.1.48 [110/1572] via 192.168.1.66, 00:00:01, Ethernet0
> > > > C 192.168.1.16 is directly connected, Serial0.302
> > > > O*N2 0.0.0.0/0 [110/1] via 192.168.1.33, 00:00:01, Serial0.312
> > > >
> > > > Thanks
> > > > Wei
> > > >
> > > > ----- Original Message -----
> > > > From: "The Long and Winding Road"
> > > > To:
> > > > Sent: Wednesday, January 01, 2003 10:12 PM
> > > > Subject: Re: OSPF stub/stub no-summary O*IA routing table entry
> [7:60088]
> > > >
> > > >
> > > > > ""Wei Zhu"" wrote in message
> > > > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > > > > The Router connections are as following, R1 has 1 frame relay
> circuit
> > > to
> > > > > R2,
> > > > > > R2 has 2 frame relay circuits to R3, R2 is the ABR, R1 in Area 0,
> and
> > > R3
> > > > > in
> > > > > > area 1.
> > > > > > R1
> > > > > > /
> > > > > > /
> > > > > > R2
> > > > > > / /
> > > > > > / /
> > > > > > R3
> > > > > > On R1, there is a redistribute entry. The two ip address on R2 to
> R3
> > > side
> > > > > > are 192.168.1.33/28, 192.168.1.17/28. The IOS is 12.2(1d).
> > > > > > When enable area 1 as a stub area, the O* IA entry on R3:
> > > > > > O*IA 0.0.0.0/0 [110/1563] via 192.168.1.33
> > > > > > 0.0.0.0/0 [110/1563] via 192.168.1.17
> > > > > > When enable area 1 as a totally stub area, the O* IA entry on R3:
> > > > > > O*IA 0.0.0.0/0 [110/1563] via 192.168.1.33 (the 192.168.1.17
entry
> > > > > > disappeared)
> > > > > >
> > > > > > It seems that in totally stub area(stub no-summary), the default
> > > traffic
> > > > > > cannot be load balanced between the two circuits.
> > > > > > Can anyone explain this?
> > > > >
> > > > >
> > > > > sorry - can't duplicate your results. in my test bed, everything
> > > operated
> > > > > precisely as expected. 12.1.5T10 and 12.2.1D on the roputers in
> > > question.
> > > > >
> > > > > might want to check your configs again. depending on what you have
> been
> > > > > doing, a phenomenon known as artifact can distort results. Reload
> > helps.
> > > > >
> > > > > otherwise, if you can document, pass along your configs, and I can
> try
> > > doing
> > > > > things exactly the way you do them.
> > > > >
> > > > > HTH
> > > > >
> > > > > Chuck
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Thanks
> > > > > > Wei
> > > [EMAIL PROTECTED]><J<~7iYB'z; )I(
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=60293&t=60293
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
