From: John Koehl (jfkoehl@xxxxxxxxxxxxxxxxx)
Date: Wed Oct 04 2000 - 10:18:04 GMT-3
   
Clear ip ospf process would work but you may want to try clear ip ospf
redistribute on the ABR first.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Eddie
Parra
Sent: Wednesday, October 04, 2000 3:40 AM
To: Wu,Jiang
Cc: ccielab@groupstudy.com
Subject: RE: OSPF NSSA External LSA
"clear ip ospf process" is a very handy command.  I don't remember which
document it was on CCO.  I think I did a search for "configuring OSPF".
Have you tried to just do this on the ABR to see if it works at all?  My lab
is apart right now.  When I put it back together I'll try it.
-Eddie
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Wu,Jiang
Sent: Wednesday, October 04, 2000 2:44 AM
To: Eddie Parra
Cc: ccielab@groupstudy.com
Subject: Re: OSPF NSSA External LSA
Eddie,
I updated some of my routers' IOS to 12.0(13) GD. I am glad I can use "clear
ip ospf process" to erase the OSPF database now. The problem while type 5
LSAs can be seen in OSPF database and those routes cannot be added into
routing table is solved by cleaning the database.
But the original problem still exists. Type 7 LSAs are still type 7 on ABR.
I try to use summary  or area range statements but they have no influence.
Would you please tell me which document did you find to say I must use the
summary command to enable the type 7 to 5 translation?
Thanks,
-Wu
----- Original Message -----
From: Eddie Parra <eparra@cisco.com>
To: Wu,Jiang <wujiang@bj163.com>
Cc: <ccielab@groupstudy.com>
Sent: Wednesday, October 04, 2000 12:14 AM
Subject: RE: OSPF NSSA External LSA
> Try using 11.2(x) GD or 12.x(x) GD.  Have you also tried to use summary
> statements on the ABR?  Try that...
>
> -Eddie
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Wu,Jiang
> Sent: Tuesday, October 03, 2000 4:06 AM
> To: eparra@cisco.com
> Cc: ccielab@groupstudy.com
> Subject: Re: OSPF NSSA External LSA
>
>
> Eddie,
>
> Do Not Age! I do remember it this time.
> On the ABRs, there are some type 5 LSAs and they have been advertised to
the
> backbone. I found them on a backbone router. But what amaze me is I cannot
> see them in the routing table!
> However, these type 5 LSAs are all advertised by ABRs (ADV Router in ospf
> database) and the link IDs are just a subset of those of type 7. All type
7
> LSAs are still type 7 on the ABRs. How can it happen?
> I use three versions of IOS. If any one of them has some problem, could
this
> happen? My IOS versions are:
> ABR1: IOS (tm) C2600 Software (C2600-JS56I-M), Version 11.3(11a)T1,
> ABR2: IOS (tm) C2600 Software (C2600-JOS56I-M), Version 12.0(3)T3,
> NSSA ASBR: IOS (tm) L3 Switch/Router Software (CAT2948G-IN-M), Version
> 12.0(7)WX5(15a)
>
> -Wu
>
> ----- Original Message -----
> From: Eddie Parra
> To: Wu,Jiang
> Cc: ccielab@groupstudy.com
> Sent: Tuesday, October 03, 2000 11:52 AM
> Subject: RE: OSPF NSSA External LSA
>
>
> Wu,
>
>      DNA stands for "Do Not Age".  You must be using a OSPF demand circuit
> somewhere.  If you look on your router where you are doing the
redistribute
> you will see your LSA's as type 7.  But once it gets to the ABR it will
> convert them to type 5's.  Try using the summary command on the ABR.  I
read
> two different Cisco docs that said two different things about the summary
> command when doing this.  One said you must use the summary command to
> enable the type 7 to 5 translation, and another said you didn't have to?
If
> your ABR has them as type 5's and is not advertising them, you might want
to
> change the IOS.  You might have a software problem.
>
> -Eddie
>
> -----Original Message-----
> From: Wu,Jiang [mailto:wujiang@bj163.com]
> Sent: Monday, October 02, 2000 11:06 PM
> To: Eddie Parra
> Cc: ccielab@groupstudy.com
> Subject: Re: OSPF NSSA External LSA
>
>
> Eddie,
> I have tried it, but it did not work. Unless I use explicit redistribution
> on NSSA ABR, those routes cannot be seen on other routers outside the
NSSA.
> Also I can't see any output as type 7 LSA's as type 5 LSA's. May it be
> caused by my somewhat complex topology?
> Another question, could you (or anyone else) tell me what the DNA means in
> the following output?
>
> r5#sh ip o d
>
>        OSPF Router with ID (172.31.5.5) (Process ID 100)
>
>
>                 Router Link States (Area 0)
>
> Link ID         ADV Router      Age         Seq#       Checksum Link count
> 172.31.2.2      172.31.2.2      401         0x80000006 0xFC6F   4
> 172.31.3.3      172.31.3.3      7     (DNA) 0x80000002 0x4BBF   3
> 172.31.5.5      172.31.5.5      51          0x80000004 0x85B4   2
>
>                 Summary Net Link States (Area 0)
>
> Link ID         ADV Router      Age         Seq#       Checksum
> 172.16.30.0     172.31.3.3      2     (DNA) 0x80000003 0xE69D
> 172.16.30.0     172.31.5.5      1954        0x80000004 0xD4A9
> 172.16.56.0     172.31.3.3      2     (DNA) 0x80000001 0xC3AA
> 172.16.56.0     172.31.5.5      937         0x80000005 0x3D33
> 172.16.56.4     172.31.3.3      2     (DNA) 0x80000001 0x9BCE
> 172.16.56.4     172.31.5.5      1954        0x80000002 0x1B54
> 172.31.2.2      172.31.2.2      402         0x80000003 0x694
>
>                 Router Link States (Area 3)
>
> Link ID         ADV Router      Age         Seq#       Checksum Link count
> 172.31.3.3      172.31.3.3      387         0x80000004 0xEDCD   1
> 172.31.5.5      172.31.5.5      53          0x80000008 0x683C   3
> 172.31.6.6      172.31.6.6      1     (DNA) 0x8000000D 0xCEF0   4
>
>                 Net Link States (Area 3)
>
> Link ID         ADV Router      Age         Seq#       Checksum
> 172.16.30.6     172.31.6.6      58          0x80000003 0x319E
> 172.16.56.2     172.31.6.6      944         0x80000003 0x5E5A
>
>                 Summary Net Link States (Area 3)
>
> Link ID         ADV Router      Age         Seq#       Checksum
> 172.16.15.4     172.31.3.3      389         0x80000003 0xE28F
> 172.16.15.4     172.31.5.5      1956        0x80000002 0x68F6
> 172.16.235.0    172.31.3.3      389         0x80000003 0x506A
> 172.16.235.0    172.31.5.5      1183        0x80000002 0x255E
> 172.31.2.2      172.31.3.3      389         0x80000003 0xED80
> 172.31.2.2      172.31.5.5      1956        0x80000002 0x245B
>
>                 Type-7 AS External Link States (Area 3)
>
> Link ID         ADV Router      Age         Seq#       Checksum Tag
> 170.170.10.0    172.31.6.6      1058        0x80000004 0x4E9D   0
> 170.170.11.0    172.31.6.6      1058        0x80000004 0x43A7   0
> 170.170.12.0    172.31.6.6      1058        0x80000004 0x38B1   0
> 172.16.15.0     172.31.6.6      59          0x80000003 0xA980   0
> 172.16.15.4     172.31.3.3      390         0x80000003 0xE12    0
> 172.16.30.0     172.31.3.3      390         0x80000003 0xA26F   0
> 172.16.30.0     172.31.6.6      60          0x80000006 0x383F   0
> 172.16.56.0     172.31.6.6      1     (DNA) 0x80000001 0x1154   0
> 172.16.56.4     172.31.6.6      60          0x80000006 0xDE7D   0
> 172.16.235.0    172.31.3.3      390         0x80000003 0xCA79   0
> 172.16.235.0    172.31.6.6      60          0x80000003 0x3E0C   0
> 172.16.235.2    172.31.6.6      1     (DNA) 0x80000006 0x2421   0
> 172.16.235.3    172.31.6.6      1     (DNA) 0x80000006 0x1A2A   0
> 172.17.22.0     172.31.6.6      60          0x80000006 0x84F9   0
> 172.17.40.0     172.31.6.6      60          0x80000006 0xBDAE   0
> 172.31.1.1      172.31.6.6      60          0x80000003 0x978D   0
> 172.31.3.3      172.31.3.3      391         0x80000003 0xF921   0
> 172.31.4.4      172.31.6.6      1059        0x80000004 0xD89E   0
> 172.31.5.5      172.31.6.6      60          0x80000003 0x43D9   0
> 172.31.6.6      172.31.6.6      60          0x80000007 0x4E2B   0
> 192.168.0.0     172.31.6.6      1     (DNA) 0x80000008 0x2B59   0
> 192.168.1.0     172.31.6.6      1     (DNA) 0x80000008 0x2063   0
>
>                 Type-5 AS External Link States
>
> Link ID         ADV Router      Age         Seq#       Checksum Tag
> 170.170.10.0    172.31.5.5      25          0x80000001 0xF505   0
> 170.170.11.0    172.31.5.5      25          0x80000001 0xEA0F   0
> 170.170.12.0    172.31.5.5      25          0x80000001 0xDF19   0
> 172.16.15.4     172.31.3.3      6     (DNA) 0x80000001 0x50B1   0
> 172.16.30.0     172.31.3.3      6     (DNA) 0x80000001 0xE40F   0
> 172.16.235.0    172.31.3.3      6     (DNA) 0x80000001 0xD19    0
> 172.31.3.3      172.31.3.3      6     (DNA) 0x80000001 0x3CC0   0
> 172.31.4.4      172.31.5.5      25          0x80000001 0x8006   0
> 172.31.6.6      172.31.5.5      25          0x80000001 0xFB8F   0
> 192.168.0.0     172.31.5.5      33          0x80000001 0xDABC   0
> 192.168.1.0     172.31.5.5      33          0x80000001 0xCFC6   0
> r5#
>
> ----- Original Message -----
> From: Eddie Parra
> To: Wu,Jiang ; ccielab@groupstudy.com
> Sent: Monday, October 02, 2000 11:09 PM
> Subject: RE: OSPF NSSA External LSA
>
>
> A OSPF NSSA does this by default when you are redistributing.  Certain CCO
> docs will tell you to use the summary command to control/enable this
> process, but it is not required.  You might have some problems with
certain
> revisions of code.  To make sure things are working do a "show ip ospf
> database" and you should see the type 7 LSA's as type 5 LSA's.
>
> -Eddie
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Wu,Jiang
> Sent: Monday, October 02, 2000 5:47 AM
> To: ccielab@groupstudy.com
> Subject: OSPF NSSA External LSA
>
>
> I want to set the P-bit in type 7 LSA so that it can be translated into a
> type 5 LSA and flooded throughout the other areas. But I have not found
the
> command(s). Could anyone please tell me how to do that?
>
> Thanks,
> Jiang
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:24 GMT-3