From: Nick Shah (nshah@connect.com.au)
Date: Tue Sep 03 2002 - 23:25:25 GMT-3
Chris
Surprisingly enough (surprised me anyway), I labbed up ur scenario
(redistributing Connected routes) and only when I put the loopback0 of the
router into the nssa area(the router on which the redistribution is taking
place), could I get a forwarding address of non-zero, and could also get the
LSA 7's converted to LSA's 5. I always thought that the 'next-hop' should be
the O/IA, but in this case I found it different.
I will be reading up on it more tonight..
Nick
----- Original Message -----
From: "Chris Larson" <clarson52@comcast.net>
To: "Peter van Oene" <pvo@usermail.com>; "Khalid Siddiq"
<khalid@sys.net.pk>; <ccielab@groupstudy.com>
Sent: Wednesday, September 04, 2002 11:42 AM
Subject: Re: NSSA and type 7 LSA's -same problem. Configs incl.
> The only reason that I know that this would happen is if the router were
> both ASBR and ABR and R2 is not. Also, an earlier post had mentioned
> reacability. I have taken the config off for now, but I remeber that
subnet
> being an O route.
>
>
> ----- Original Message -----
> From: "Peter van Oene" <pvo@usermail.com>
> To: "Khalid Siddiq" <khalid@sys.net.pk>; <ccielab@groupstudy.com>
> Sent: Tuesday, September 03, 2002 6:42 PM
> Subject: RE: NSSA and type 7 LSA's -same problem. Configs incl.
>
>
> > I agree that this could be an issue. However, lack of reachability to
the
> > forwarding address shouldn't prevent the LSA from appearing in the
> > LSDB. The fact that is doesn't, in addition to the fact that a type 4
> > isn't announce by the translating NSSA ABR leads me to believe that the
> ABR
> > isn't translating this type 7. This is further evidenced by the P-Bit
> > clear setting on these particular LSAs. I think the question is why is
> the
> > ASBR setting the P bit clear.
> >
> > At 02:56 PM 9/3/2002 +0500, Khalid Siddiq wrote:
> > >I think,their is issue with the reachability of Forwarding address, for
> > >the conversion of type 7 to type 5 LSA, the forwarding address
> 150.50.17.1
> > >should be know via OSPF O or IA route.
> > >Please Check the route of 150.50.17.1 on nssa abr and let me know if
this
> > >reslove the issue.
> > >regards,
> > >khalid
> > >
> > >-----Original Message-----
> > >From: Peter van Oene [mailto:pvo@usermail.com]
> > >Sent: Tuesday, September 03, 2002 12:11 AM
> > >To: ccielab@groupstudy.com
> > >Subject: RE: NSSA and type 7 LSA's -same problem. Configs incl.
> > >
> > >
> > >Quick clarification. A type 3 default will take precedence over a type
7
> > >default, not more specific type 7's. In this situation, so long as the
> > >p-bit is set, and the forwarding address isn't 0.0.0.0, the 7's should
be
> > >translated. For whatever reason, the ASBR's in this case are creating
> type
> > >7's with the p bit clear (this is the new default btw) I am not aware
of
> > >an option to control p-bit setting and there must be some other
> > >characteristic at work here that is non obvious.
> > >
> > >At 02:44 PM 9/2/2002 -0400, Peter van Oene wrote:
> > > >Hey guys,
> > > >
> > > >I think you are both setting the area up as totally stubby which may
be
> > > >injecting a type 3 default. With a type 3 default, IIRC, this route
> will
> > > >be preferred over all more specific type 7's. With this in place, it
> > > >could be that the NSSA ASBR sees this and sets the P-bit. I am fuzzy
on
> > > >this behavior and will look it up in more detail, but try pulling out
> the
> > > >no-summary and see what happens. Specifically, look at the type 7's
in
> > > >detail on the NSSA ABR and see if type 7/5 translation (ie P-bit) is
> set
> > > >to translate.
> > > >
> > > >Pete
> > > >
> > > >
> > > >At 01:00 PM 9/2/2002 -0500, Keith Steller wrote:
> > > >>http://www.cisco.com/warp/public/104/ospfdb8.html
> > > >>
> > > >>What I want to see is the type 5 E1 route like in the example above.
> Thats
> > > >>my problem.
> > > >>
> > > >>Thanks,
> > > >>
> > > >>Keith
> > > >>
> > > >>-----Original Message-----
> > > >>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
Of
> > > >>Chris Larson
> > > >>Sent: Monday, September 02, 2002 12:07 PM
> > > >>To: Landon Fitts; Keith Steller; ccielab@groupstudy.com
> > > >>Subject: Re: NSSA and type 7 LSA's -same problem. Configs incl.
> > > >>
> > > >>
> > > >>I am having a similiar issue with the same topo and config. Only the
> IP
> > > >>addresses are different and I am redistributing connected not rip.
> > > >>
> > > >>The type 7 to the ABR is fine, but the ABR is not translating the
7's
> into
> > > >>5's for the rest of the OSPF domain.
> > > >>
> > > >>
> > > >> redistributeConnected ------>R1(area 3
> > > nssa)-----area3-----R2(area 3
> > > >>nssa ABR)----------area0------------
> > > >>
> > > >>R1 is ASBR in area 3. R2 is ABR and has connection to area 0. R5 is
in
> area
> > > >>0 and does not have type 5 generated from R2.
> > > >>
> > > >>
> > > >>R2#sh ip ospf dat ext
> > > >>
> > > >> OSPF Router with ID (200.0.0.2) (Process ID 1)
> > > >>
> > > >>
> > > >> Type-5 AS External Link States
> > > >>
> > > >> Routing Bit Set on this LSA
> > > >> LS age: 1905
> > > >> Options: (No TOS-capability, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 150.50.4.0 (External Network Number )
> > > >> Advertising Router: 200.0.0.8
> > > >> LS Seq Number: 80000053
> > > >> Checksum: 0xD7D8
> > > >> Length: 36
> > > >> Network Mask: /24
> > > >> Metric Type: 2 (Larger than any link state path)
> > > >> TOS: 0
> > > >> Metric: 20
> > > >> Forward Address: 0.0.0.0
> > > >> External Route Tag: 0
> > > >>
> > > >>This is from a different area
> > > >>
> > > >>None of the other routers see any type 5's being generated from R2.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>R2#sh ip ospf dat nssa-external
> > > >>
> > > >> OSPF Router with ID (200.0.0.2) (Process ID 1)
> > > >>
> > > >>
> > > >> Type-7 AS External Link States (Area 3)
> > > >>
> > > >> LS age: 127
> > > >> Options: (No TOS-capability, No Type 7/5 translation, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 0.0.0.0 (External Network Number )
> > > >> Advertising Router: 200.0.0.2
> > > >> LS Seq Number: 80000002
> > > >> Checksum: 0xEFF5
> > > >> Length: 36
> > > >> Network Mask: /0
> > > >> Metric Type: 2 (Larger than any link state path)
> > > >> TOS: 0
> > > >> Metric: 1
> > > >> Forward Address: 0.0.0.0
> > > >> External Route Tag: 0
> > > >>
> > > >> LS age: 1810
> > > >> Options: (No TOS-capability, No Type 7/5 translation, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 150.50.17.0 (External Network Number )
> > > >> Advertising Router: 200.0.0.1
> > > >> LS Seq Number: 80000002
> > > >> Checksum: 0x346B
> > > >> Length: 36
> > > >> Network Mask: /24
> > > >> Metric Type: 1 (Comparable directly to link state metric)
> > > >> TOS: 0
> > > >> Metric: 20
> > > >> Forward Address: 150.50.17.1
> > > >> External Route Tag: 0
> > > >>
> > > >> LS age: 1813
> > > >> Options: (No TOS-capability, No Type 7/5 translation, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 150.50.18.0 (External Network Number )
> > > >> Advertising Router: 200.0.0.1
> > > >> LS Seq Number: 80000002
> > > >> Checksum: 0x2975
> > > >> Length: 36
> > > >> Network Mask: /24
> > > >> Metric Type: 1 (Comparable directly to link state metric)
> > > >> TOS: 0
> > > >> Metric: 20
> > > >> Forward Address: 150.50.17.1
> > > >> External Route Tag: 0
> > > >>
> > > >> Routing Bit Set on this LSA
> > > >> LS age: 1557
> > > >> Options: (No TOS-capability, No Type 7/5 translation, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 150.50.200.0 (External Network Number )
> > > >> Advertising Router: 200.0.0.1
> > > >> LS Seq Number: 80000004
> > > >> Checksum: 0x3CAC
> > > >> Length: 36
> > > >> Network Mask: /22
> > > >> Metric Type: 1 (Comparable directly to link state metric)
> > > >> TOS: 0
> > > >> Metric: 20
> > > >> Forward Address: 150.50.17.1
> > > >> External Route Tag: 0
> > > >>
> > > >> Routing Bit Set on this LSA
> > > >> LS age: 1821
> > > >> Options: (No TOS-capability, No Type 7/5 translation, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 200.0.0.1 (External Network Number )
> > > >> Advertising Router: 200.0.0.1
> > > >> LS Seq Number: 80000002
> > > >> Checksum: 0xB3FB
> > > >> Length: 36
> > > >> Network Mask: /32
> > > >> Metric Type: 1 (Comparable directly to link state metric)
> > > >> TOS: 0
> > > >> Metric: 20
> > > >> Forward Address: 150.50.17.1
> > > >> External Route Tag: 0
> > > >>
> > > >>
> > > >>R5#sh ip ospf dat external
> > > >>
> > > >> OSPF Router with ID (200.0.0.5) (Process ID 1)
> > > >>
> > > >>
> > > >> Type-5 AS External Link States
> > > >>
> > > >> Routing Bit Set on this LSA
> > > >> LS age: 60
> > > >> Options: (No TOS-capability, DC)
> > > >> LS Type: AS External Link
> > > >> Link State ID: 150.50.4.0 (External Network Number )
> > > >> Advertising Router: 200.0.0.8
> > > >> LS Seq Number: 80000054
> > > >> Checksum: 0xD5D9
> > > >> Length: 36
> > > >> Network Mask: /24
> > > >> Metric Type: 2 (Larger than any link state path)
> > > >> TOS: 0
> > > >> Metric: 20
> > > >> Forward Address: 0.0.0.0
> > > >> External Route Tag: 0
> > > >>
> > > >>
> > > >>CONFIGS::
> > > >>
> > > >>
> > > >>hostname R1
> > > >>!
> > > >>netbios access-list host nofile deny FIL*
> > > >>!
> > > >>no ip subnet-zero
> > > >>no ip domain-lookup
> > > >>ipx routing 0001.0001.0001
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>interface Loopback0
> > > >> ip address 200.0.0.1 255.255.255.255
> > > >> no ip directed-broadcast
> > > >>!
> > > >>interface Ethernet0
> > > >> ip address 150.50.200.1 255.255.255.0
> > > >> ip helper-address 1.1.1.1
> > > >> ip helper-address 1.1.1.2
> > > >> no ip directed-broadcast
> > > >> no keepalive
> > > >>!
> > > >>interface Ethernet1
> > > >> ip address 150.50.17.1 255.255.255.0
> > > >> no ip directed-broadcast
> > > >> ipx network 12
> > > >> ipx netbios input-access-filter host nofile
> > > >>!
> > > >>interface Serial0
> > > >> no ip address
> > > >> no ip directed-broadcast
> > > >> no ip mroute-cache
> > > >> shutdown
> > > >> no fair-queue
> > > >>!
> > > >>interface Serial1
> > > >> no ip address
> > > >> no ip directed-broadcast
> > > >> shutdown
> > > >>!
> > > >>interface Virtual-TokenRing0
> > > >> ip address 150.50.18.1 255.255.255.0
> > > >> no ip directed-broadcast
> > > >> ip ospf network point-to-point
> > > >> ring-speed 16
> > > >>!
> > > >>router ospf 1
> > > >> area 3 nssa
> > > >> summary-address 150.50.200.0 255.255.252.0
> > > >> redistribute connected metric-type 1 subnets
> > > >> network 150.50.17.0 0.0.0.255 area 3
> > > >> network 150.50.18.0 0.0.0.255 area 3
> > > >>!
> > > >>ip nat translation timeout never
> > > >>ip nat translation tcp-timeout never
> > > >>ip nat translation udp-timeout never
> > > >>ip nat translation finrst-timeout never
> > > >>ip nat translation syn-timeout never
> > > >>ip nat translation dns-timeout never
> > > >>ip nat translation icmp-timeout never
> > > >>ip classless
> > > >>!
> > > >>access-list 5 permit 200.0.0.1
> > > >>access-list 5 permit 150.50.200.0 0.0.0.255
> > > >>access-list 1001 deny FFFFFFFF 0
> > > >>route-map conn permit 10
> > > >> match ip address 5
> > > >>!
> > > >>route-map conn deny 20
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>ipx router eigrp 1
> > > >> network 12
> > > >>!
> > > >>!
> > > >>ipx router rip
> > > >> no network all
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>line con 0
> > > >> logging synchronous
> > > >> transport input none
> > > >>line aux 0
> > > >>line vty 0 4
> > > >> login
> > > >>!
> > > >>end
> > > >>
> > > >>
> > > >>
> > > >>hostname R2
> > > >>!
> > > >>!
> > > >>memory-size iomem 20
> > > >>ip subnet-zero
> > > >>no ip domain-lookup
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>interface Loopback0
> > > >> ip address 200.0.0.2 255.255.255.255
> > > >> no ip directed-broadcast
> > > >>!
> > > >>interface FastEthernet0/0
> > > >> ip address 150.50.17.2 255.255.255.0
> > > >> no ip directed-broadcast
> > > >>!
> > > >>interface Serial0/0
> > > >> no ip address
> > > >> no ip directed-broadcast
> > > >> encapsulation frame-relay
> > > >> no ip mroute-cache
> > > >> no fair-queue
> > > >> clockrate 56000
> > > >> frame-relay traffic-shaping
> > > >> frame-relay class classmap
> > > >>!
> > > >>interface Serial0/0.1 point-to-point
> > > >> ip address 150.50.24.2 255.255.255.0
> > > >> no ip directed-broadcast
> > > >> ip ospf network point-to-multipoint
> > > >> frame-relay interface-dlci 104
> > > >>!
> > > >>interface Serial0/0.2 multipoint
> > > >> ip address 150.50.100.2 255.255.255.224
> > > >> no ip directed-broadcast
> > > >> ip ospf message-digest-key 1 md5 cisco
> > > >> ip ospf network non-broadcast
> > > >> frame-relay map ip 150.50.100.5 105 broadcast
> > > >> frame-relay map ip 150.50.100.6 106 broadcast
> > > >>!
> > > >>interface BRI0/0
> > > >> no ip address
> > > >> no ip directed-broadcast
> > > >> shutdown
> > > >>!
> > > >>router ospf 1
> > > >> network 150.50.17.0 0.0.0.255 area 3
> > > >> network 150.50.24.0 0.0.0.255 area 1
> > > >> network 150.50.100.0 0.0.0.31 area 0
> > > >> network 200.0.0.2 0.0.0.0 area 100
> > > >> neighbor 150.50.100.5
> > > >> neighbor 150.50.100.6
> > > >> area 0 authentication message-digest
> > > >> area 1 stub no-summary
> > > >> area 3 nssa default-information-originate
> > > >>!
> > > >>ip classless
> > > >>no ip http server
> > > >>!
> > > >>!
> > > >>map-class frame-relay classmap
> > > >> frame-relay cir 58000
> > > >> no frame-relay adaptive-shaping
> > > >>!
> > > >>!
> > > >>line con 0
> > > >> transport input none
> > > >>line aux 0
> > > >>line vty 0 4
> > > >> login
> > > >>!
> > > >>no scheduler allocate
> > > >>end
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>hostname R5
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>ip subnet-zero
> > > >>no ip domain-lookup
> > > >>!
> > > >>cns event-service server
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>!
> > > >>interface Loopback0
> > > >> ip address 200.0.0.5 255.255.255.255
> > > >> no ip directed-broadcast
> > > >>!
> > > >>interface Ethernet0
> > > >> ip address 150.50.7.5 255.255.255.128
> > > >> no ip directed-broadcast
> > > >> ip ospf message-digest-key 1 md5 cisco
> > > >>!
> > > >>interface Serial0
> > > >> ip address 150.50.100.5 255.255.255.224
> > > >> no ip directed-broadcast
> > > >> encapsulation frame-relay
> > > >> ip ospf message-digest-key 1 md5 cisco
> > > >> ip ospf priority 0
> > > >> no ip mroute-cache
> > > >> frame-relay map ip 150.50.100.2 501 broadcast
> > > >> frame-relay map ip 150.50.100.6 501 broadcast
> > > >> frame-relay lmi-type cisco
> > > >>!
> > > >>interface Serial1
> > > >> no ip address
> > > >> no ip directed-broadcast
> > > >> shutdown
> > > >>!
> > > >>router ospf 1
> > > >> area 0 authentication message-digest
> > > >> network 150.50.7.0 0.0.0.127 area 0
> > > >> network 150.50.100.0 0.0.0.31 area 0
> > > >> network 200.0.0.5 0.0.0.0 area 100
> > > >>!
> > > >>ip classless
> > > >>no ip http server
> > > >>!
> > > >>!
> > > >>!
> > > >>line con 0
> > > >> transport input none
> > > >>line aux 0
> > > >>line vty 0 4
> > > >>!
> > > >>end
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>----- Original Message -----
> > > >>From: "Landon Fitts" <l.fitts@mindspring.com>
> > > >>To: "Keith Steller" <ksteller@attbi.com>; <ccielab@groupstudy.com>
> > > >>Sent: Monday, September 02, 2002 12:25 PM
> > > >>Subject: Re: NSSA and type 7 LSA's
> > > >>
> > > >>
> > > >> > Keith.
> > > >> >
> > > >> > This is correct behavior. The ASBR that is part of the NSSA
sends
> > > the RIP
> > > >> > routes as LSA type 7 (N2/N1), but the ABR sends those LSAs out as
> type 5
> > > >> > (E2/E1) into the backbone. The type 7 LSAs are only distributed
> within
> > > >>the
> > > >> > NSSA area.
> > > >> >
> > > >> > Landon
> > > >> >
> > > >> > ----- Original Message -----
> > > >> > From: "Keith Steller" <ksteller@attbi.com>
> > > >> > To: <ccielab@groupstudy.com>
> > > >> > Sent: Monday, September 02, 2002 11:26 AM
> > > >> > Subject: NSSA and type 7 LSA's
> > > >> >
> > > >> >
> > > >> > > Hello All-
> > > >> > >
> > > >> > > I have a question for someone. I have an NSSA configured to
allow
> > > >> > > redistibution of a few RIP routes into the OSPF net. I have
> everything
> > > >> > > working fine except for one thing. I can see the RIP routes,
> > > denoted by
> > > >> > the
> > > >> > > N2 in the routing table on the ABR where the "Area X NSSA" is
> > > >>configured.
> > > >> > I
> > > >> > > dont see those type 7 routes being advertised to other routers
in
> the
> > > >>OSPF
> > > >> > > network though. I'm wondering if that's correct behavior. I can
> get
> > > >> > > connectivity to the RIP net (146.10.18.x) when I add the
"default
> > > >> > > information originate always" on the ABR with the NSSA, as he
can
> see
> > > >>the
> > > >> > > RIP routes from there. With that configured, everyone sends
> packets to
> > > >>him
> > > >> > > when they dont have a route available. Shouldnt the NSSA allow
> the RIP
> > > >> > > network to be advrtised to all routers in the OSPF network? I
> attached
> > > >>the
> > > >> > > configs below. R1 is the ASBR with RIP and OSPF. R2 is the
other
> > > end of
> > > >> > the
> > > >> > > NSSA ABR (connected to Area 0), and R5 is also on th backbone
on
> > > area 0.
> > > >> > >
> > > >> > > Thanks for the assistance,
> > > >> > >
> > > >> > > Keith
> > > >> > >
> > > >> > > R1
> > > >> > > !
> > > >> > > router ospf 100
> > > >> > > redistribute rip subnets
> > > >> > > passive-interface TokenRing0
> > > >> > > network 146.10.11.0 0.0.0.255 area 11
> > > >> > > network 146.10.21.0 0.0.0.3 area 21
> > > >> > > default-metric 5
> > > >> > > area 11 range 146.10.11.0 255.255.255.0
> > > >> > > area 21 nssa
> > > >> > > !
> > > >> > > router rip
> > > >> > > version 1
> > > >> > > redistribute ospf 100 metric 10
> > > >> > > passive-interface Loopback100
> > > >> > > passive-interface Serial1
> > > >> > > network 146.10.0.0
> > > >> > > neighbor 146.10.18.8
> > > >> > > !
> > > >> > > 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, * -
> > > candidate
> > > >> > > default
> > > >> > > U - per-user static route, o - ODR
> > > >> > >
> > > >> > > Gateway of last resort is 146.10.21.2 to network 0.0.0.0
> > > >> > >
> > > >> > > 146.10.0.0/16 is variably subnetted, 6 subnets, 2 masks
> > > >> > > C 146.10.18.0/24 is directly connected, TokenRing0
> > > >> > > C 146.10.21.0/30 is directly connected, Serial1
> > > >> > > C 146.10.11.0/24 is directly connected, Loopback100
> > > >> > > R 146.10.88.0/24 [120/1] via 146.10.18.8, 00:00:17,
> TokenRing0
> > > >> > > R 146.10.78.0/24 [120/1] via 146.10.18.8, 00:00:17,
> TokenRing0
> > > >> > > C 146.10.118.0/24 is directly connected, Loopback200
> > > >> > > O*IA 0.0.0.0/0 [110/65] via 146.10.21.2, 00:12:41, Serial1
> > > >> > > r1#
> > > >> > > ***************************************
> > > >> > > R2
> > > >> > > !
> > > >> > > router ospf 100
> > > >> > > network 146.10.10.0 0.0.0.255 area 0
> > > >> > > network 146.10.21.0 0.0.0.3 area 21
> > > >> > > network 146.10.22.0 0.0.0.255 area 22
> > > >> > > neighbor 146.10.10.6 priority 1
> > > >> > > neighbor 146.10.10.5 priority 5
> > > >> > > default-information originate always
> > > >> > > area 21 nssa default-information-originate no-summary
> > > >> > > area 22 range 146.10.22.0 255.255.255.0
> > > >> > > !
> > > >> > >
> > > >> > > r2#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, * -
> > > candidate
> > > >> > > default
> > > >> > > U - per-user static route, o - ODR
> > > >> > >
> > > >> > > Gateway of last resort is not set
> > > >> > >
> > > >> > > 146.10.0.0/16 is variably subnetted, 12 subnets, 3 masks
> > > >> > > C 146.10.24.0/24 is directly connected, Serial0.1
> > > >> > > O N2 146.10.18.0/24 [110/5] via 146.10.21.1, 00:14:30,
Serial1
> > > >> > > C 146.10.21.0/30 is directly connected, Serial1
> > > >> > > C 146.10.22.0/24 is directly connected, Loopback100
> > > >> > > C 146.10.10.0/24 is directly connected, Serial0
> > > >> > > O N2 146.10.11.0/24 [110/5] via 146.10.21.1, 00:14:30,
Serial1
> > > >> > > O IA 146.10.57.0/25 [110/74] via 146.10.10.6, 00:14:30,
> Serial0
> > > >> > > [110/74] via 146.10.10.5, 00:14:30,
> Serial0
> > > >> > > O IA 146.10.55.0/24 [110/65] via 146.10.10.5, 00:14:30,
> Serial0
> > > >> > > O N2 146.10.88.0/24 [110/5] via 146.10.21.1, 00:14:30,
Serial1
> > > >> > > O N2 146.10.78.0/24 [110/5] via 146.10.21.1, 00:14:30,
Serial1
> > > >> > > O IA 146.10.66.0/24 [110/65] via 146.10.10.6, 00:14:30,
> Serial0
> > > >> > > O N2 146.10.118.0/24 [110/5] via 146.10.21.1, 00:14:30,
> Serial1
> > > >> > > r2#
> > > >> > > Type-7 AS External Link States (Area 21)
> > > >> > >
> > > >> > > Link ID ADV Router Age Seq# Checksum
> Tag
> > > >> > > 146.10.11.0 146.10.118.1 445 0x80000002 0xF944
0
> > > >> > > 146.10.18.0 146.10.118.1 445 0x80000002 0xAC8A
0
> > > >> > > 146.10.21.0 146.10.118.1 445 0x80000002 0x79BD
0
> > > >> > > 146.10.78.0 146.10.118.1 445 0x80000002 0x16E4
0
> > > >> > > 146.10.88.0 146.10.118.1 445 0x80000002 0xA749
0
> > > >> > > 146.10.118.0 146.10.118.1 445 0x80000002 0x5C76
0
> > > >> > > ****************************************************
> > > >> > > R5
> > > >> > > !
> > > >> > > router ospf 100
> > > >> > > network 146.10.10.0 0.0.0.255 area 0
> > > >> > > network 146.10.55.0 0.0.0.255 area 55
> > > >> > > network 146.10.57.0 0.0.0.127 area 57
> > > >> > > neighbor 146.10.10.2 priority 10
> > > >> > > area 55 range 146.10.55.0 255.255.255.0
> > > >> > > !
> > > >> > > r5#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, * -
> > > candidate
> > > >> > > default
> > > >> > > U - per-user static route, o - ODR
> > > >> > >
> > > >> > > Gateway of last resort is 146.10.10.2 to network 0.0.0.0
> > > >> > >
> > > >> > > 146.10.0.0/16 is variably subnetted, 6 subnets, 3 masks
> > > >> > > O IA 146.10.21.0/30 [110/128] via 146.10.10.2, 00:16:28,
> > > Serial0.501
> > > >> > > O IA 146.10.22.0/24 [110/65] via 146.10.10.2, 00:16:28,
> Serial0.501
> > > >> > > C 146.10.10.0/24 is directly connected, Serial0.501
> > > >> > > C 146.10.57.0/25 is directly connected, Ethernet0
> > > >> > > C 146.10.55.0/24 is directly connected, Loopback55
> > > >> > > O IA 146.10.66.0/24 [110/65] via 146.10.10.6, 00:16:28,
> Serial0.501
> > > >> > > 146.100.0.0/24 is subnetted, 1 subnets
> > > >> > > C 146.100.55.0 is directly connected, Loopback100
> > > >> > > O*E2 0.0.0.0/0 [110/1] via 146.10.10.2, 00:16:21, Serial0.501
> > > >> > > r5#
> > > >> > >
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:43 GMT-3