From: Brian Burke (burkebri@acworthcablenet.net)
Date: Sat Mar 08 2003 - 16:49:38 GMT-3
Scott, Gery,
I just created the scenario and see that it works ok. I think Scott's
recommendations are the best way to go.
Brgds,
Brian
----- Original Message -----
From: "Scott M. Livingston" <scottl@sprinthosting.net>
To: "'Gery Pang'" <pang_gery@yahoo.com.hk>
Cc: "'OhioHondo'" <ohiohondo@columbus.rr.com>; "'ccielab'"
<ccielab@groupstudy.com>
Sent: Saturday, March 08, 2003 12:58 PM
Subject: RE: OSPF NSSA help please!
> Maybe someone else, but nothing is jumping out at me right now. If I
> were you I would do the following - you probably have already done
> number 1.
>
> 1. Bounce the OSPF PID on all the routers.
> 2. Rebuild it step by step.
> 3. I need to go back and either set this up and or do a dig on NSSA
> behavior. It all looks good to me.
>
> Thanks,
> scott
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Gery Pang
> Sent: Saturday, March 08, 2003 9:26 AM
> To: Scott M. Livingston
> Cc: OhioHondo; ccielab
> Subject: Re: OSPF NSSA help please!
>
> Sorry for not including the config for last mail.
>
>
> R3-------R5--------R4--------R6
>
> R3 and R5 : Area 0
> R5 and R4: Area 45 (nssa)
> R4 and R6: eigrp
>
> My problem is R3 cannot get the eigrp routes from nssa area.
>
> The followings are the related config and router table.
>
> R4
>
> interface Serial0.1 multipoint
> descrition interface to R5
> ip address 172.16.45.4 255.255.255.0
>
> interface Serial0.2 multipoint
> descrition interface to R6
> ip address 172.16.46.4 255.255.255.0
>
> router eigrp 10
> redistribute ospf 10
> network 172.16.46.0 0.0.0.255
> default-metric 1544 100 255 1 1500
> no auto-summary
> !
> router ospf 10
> router-id 172.16.4.4
> area 45 nssa
> redistribute eigrp 10 subnets
> network 172.16.4.4 0.0.0.0 area 45
> network 172.16.45.4 0.0.0.0 area 45
> neighbor 172.16.45.5 priority 1
>
> The related routes of R4:
>
> O IA 172.16.35.0 [110/65] via 172.16.45.5, 00:10:55, Serial0.1
> C 172.16.45.0 is directly connected, Serial0.1
> C 172.16.46.0 is directly connected, Serial0.2
> C 172.16.40.0 is directly connected, Loopback10
> C 172.16.4.0 is directly connected, Loopback0
> O 172.16.5.0 [110/65] via 172.16.45.5, 00:10:55, Serial0.1
> D 172.16.6.0 [90/2297856] via 172.16.46.6, 01:02:22, Serial0.2
> O IA 172.16.3.0 [110/66] via 172.16.45.5, 00:10:55, Serial0.1
> 172.60.0.0/24 is subnetted, 1 subnets
> D 172.60.61.0 [90/2297856] via 172.16.46.6, 01:02:28, Serial0.2
>
>
> R5
>
> interface Loopback0
> ip address 172.16.5.5 255.255.255.0
> ip ospf network point-to-point
>
> interface Serial0/0
> description interface to R4
> ip address 172.16.45.5 255.255.255.0
> encapsulation frame-relay
> no arp frame-relay
> frame-relay map ip 172.16.45.4 411 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
>
> interface FastEthernet0/0
> description interface to R3
> ip address 172.16.35.5 255.255.255.0
> duplex auto
> speed auto
>
>
> router ospf 10
> router-id 172.16.5.5
> log-adjacency-changes
> area 45 nssa
> network 172.16.5.5 0.0.0.0 area 45
> network 172.16.45.5 0.0.0.0 area 45
> network 172.16.51.0 0.0.0.255 area 50
> network 172.16.35.5 0.0.0.0 area 0
>
> The related routes of R5: (these routes are missing in R3)
>
> O N2 172.16.6.0/24 [110/20] via 172.16.45.4, 00:01:06, Serial0/0
> O N2 172.16.46.0/24 [110/20] via 172.16.45.4, 00:01:06, Serial0/0
> O N2 172.60.61.0 [110/20] via 172.16.45.4, 00:01:07, Serial0/0
> O N2 172.60.61.16 [110/20] via 172.16.45.4, 00:01:07, Serial0/0
>
> R5#sh ip ospf neig
>
> Neighbor ID Pri State Dead Time Address
> Interface
> 172.16.3.3 1 FULL/DR 00:00:35 172.16.35.3
> FastEthernet0/0
> 172.16.4.4 1 FULL/BDR 00:01:45 172.16.45.4
> Serial0/0
>
>
>
> R3
>
> interface Loopback0
> ip address 172.16.3.3 255.255.255.0
> ip ospf network point-to-point
>
> interface Ethernet0
> description interface to R5
> ip address 172.16.35.3 255.255.255.0
>
>
> router ospf 10
> router-id 172.16.3.3
> network 172.16.3.3 0.0.0.0 area 0
> network 172.16.35.3 0.0.0.0 area 0
>
> R3#sh ip ospf neig
>
> Neighbor ID Pri State Dead Time Address
> Interface
> 172.16.5.5 1 FULL/DR 00:00:32 172.16.35.5
> Ethernet0
>
>
> R3#sh ip ospf data
>
> OSPF Router with ID (172.16.3.3) (Process ID 10)
>
>
> Router Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum Link
> count
> 172.16.3.3 172.16.3.3 88 0x80000013 0xD88D 2
> 172.16.5.5 172.16.5.5 94 0x80000016 0x2C06 1
>
> Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 172.16.35.5 172.16.5.5 95 0x80000001 0x735
>
> Summary Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 172.16.4.0 172.16.5.5 444 0x80000001 0x90E3
> 172.16.5.0 172.16.5.5 611 0x8000000F 0xE6BE
> 172.16.45.0 172.16.5.5 449 0x80000015 0x999E
> 172.16.51.0 172.16.5.5 611 0x8000000B 0x98F1
> 172.16.51.16 172.16.5.5 611 0x8000000B 0xF782
> 172.16.51.32 172.16.5.5 611 0x8000000B 0x5713
> 172.16.51.48 172.16.5.5 613 0x8000000B 0xB6A3
>
> Type-5 AS External Link States
>
> Link ID ADV Router Age Seq# Checksum Tag
> 172.10.10.0 172.16.3.3 96 0x80000009 0x1AEB 34
> 172.16.1.0 172.16.3.3 96 0x80000009 0x35D3 34
> 172.16.13.0 172.16.3.3 91 0x8000000E 0xFE08 0
> 192.168.10.0 172.16.3.3 96 0x80000009 0x4B17 34
> 192.168.10.16 172.16.3.3 96 0x80000009 0xAAA7 34
> 192.168.11.0 172.16.3.3 96 0x80000009 0xDF91 34
> 192.168.11.96 172.16.3.3 96 0x80000009 0x1CF4 34
> 192.168.12.0 172.16.3.3 96 0x80000009 0x7DD6 34
> 192.168.13.0 172.16.3.3 96 0x80000009 0x84CB 34
> R3#
>
>
>
> ----- Original Message -----
> From: "Scott M. Livingston" <scottl@sprinthosting.net>
> To: "'Gery Pang'" <pang_gery@yahoo.com.hk>
> Sent: Saturday, March 08, 2003 10:17 PM
> Subject: RE: OSPF NSSA help please!
>
>
> > Gery,
> >
> > Maybe not for others, but for me it's hard to figure this one out w/o
> > seeing the configs and tables.
> >
> > 1. So you know for sure your neighbors are up between R3 and R5? Sorry
> > to ask, but it would be easy to overlook.
> >
> > 2. There isn't any sort of OSPF config between R4 and R6 is there?
> It's
> > just EIGRP right?
> >
> > Seems like I had this happen to me before, but I don't remember what
> it
> > was. I set this up this morning just to make sure and I can't find a
> > problem.
> >
> > Thanks,
> > scott
> >
> >
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Gery Pang
> > Sent: Saturday, March 08, 2003 2:44 AM
> > To: ccielab
> > Subject: OSPF NSSA help please!
> >
> > Hi Group,
> >
> > R3-------R5--------R4--------R6
> >
> > R3 and R5 : Area 0
> > R5 and R4: Area 45 (nssa)
> > R4 and R6: eigrp
> >
> > The problem is R3 cannot see the routes of the eigrp domain.
> > R5 has the routes as Type 7 LSA but these routes are not appear
> > R3's ospf database as Type 5.
> >
> > I have only type "area 45 nssa" in both R4 and R5, and no access list
> > is present.
> >
> > Please help!
> >
> > Thank you very much.
> >
> > Gery
>
> _________________________________________________________
> 'Z*:E:6F(.e/*(`)!A%*>F%k(=('u'J6T)!A'A3L,u(Twins)...
> 9L$d-:$b>w9aAn BIRing3#1o
> http://ringtone.yahoo.com.hk
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:35 GMT-3