From: Zeng Puyang (zbridge98@xxxxxxxxx)
Date: Tue May 15 2001 - 06:19:03 GMT-3
Hi, group
I try this, it works find. The lsa7 tranlate to lsa5 on R8.
But when I want to try config the R7 to let the lsa7 can't be tranlate to lsa5,
then it won't be seen out of nssa. The only command I remenber is 'summ x.y.z
.0 255.255.255.0 no-adv', then the lsa7 disappeared on R7.
What should I do to set 'No Type7/5 translation', if it's not a ABR?
Thanks
Zeng
----- Original Message -----
From: "perez claude-vincent" <claude_vincent@yahoo.com>
To: "Lachlan Kidd" <lkidd@netstarnetworks.com>; "Wei Man" <mandraw1@yahoo.com>;
<ccielab@groupstudy.com>
Sent: Tuesday, May 15, 2001 4:17 PM
Subject: RE: NSSA and Virtual Link Again
> Yes. the nssa asbr cannot be an abr otherwise there
> will be no translation.
>
> vincent
> --- Lachlan Kidd <lkidd@netstarnetworks.com> wrote:
> > Hi Wei,
> > Not sure if Vincents suggestion helped but your
> > problem is
> > > LS age: 1771
> > > Options: (No TOS-capability, No Type
> > 7/5<-----This means that no
> > translation will take place
> > > translation, DC)
> > The last time I tried this, the same thing happened.
> > To fix it I removed the
> > OSPF process from the ASBR, re-applied it and the
> > Database entries had 'Type
> > 7/5 translation' next to them. Everything started to
> > work.
> > I think this is related to the fact that a router in
> > an NSSA cannot be an
> > ABR and an ASBR. When you set up the underlying OSPF
> > infrastructure, at some
> > point the ASBR believes it is an ASBR and an ABR at
> > the same time. Hence the
> > LSA's get marked this way. Be removing the process
> > and re-applying it the
> > router gets it's view of the world re-established. I
> > am running 12.0(7)T
> > This is only from limited observation, so if anyone
> > else out there has found
> > otherwise, please let me know.
> > Regards,
> > Lachlan
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com
> > [mailto:nobody@groupstudy.com]On Behalf Of
> > perez claude-vincent
> > Sent: Tuesday, 15 May 2001 5:27:PM
> > To: Wei Man; lkidd@netstarnetworks.com;
> > ccielab@groupstudy.com
> > Subject: RE: NSSA and Virtual Link Again
> >
> >
> > Wei,
> >
> > Please take these commands out of your ospf
> > configuration on your R7:
> >
> > area 55 range 170.150.7.0 255.255.255.0
> > area 55 range 170.150.78.0 255.255.255.0
> >
> > Vincent
> >
> >
> > --- Wei Man <mandraw1@yahoo.com> wrote:
> > > Here it is
> > >
> > >
> > > R7#sh ip ospf database nssa
> > >
> > > OSPF Router with ID (217.1.7.1) (Process ID
> > > 10)
> > >
> > >
> > > Type-7 AS External Link States
> > (Area
> > > 55)
> > >
> > > LS age: 1771
> > > 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: 217.1.8.1
> > > LS Seq Number: 80000001
> > > Checksum: 0x1EAF
> > > 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: 869
> > > Options: (No TOS-capability, No Type 7/5
> > > translation, DC)
> > > LS Type: AS External Link
> > > Link State ID: 160.60.60.0 (External Network
> > > Number
> > > )
> > > Advertising Router: 217.1.7.1
> > > LS Seq Number: 80000005
> > > Checksum: 0xD9F8
> > > Length: 36
> > > Network Mask: /22
> > > Metric Type: 1 (Comparable directly to
> > link
> > > state metric)
> > > TOS: 0
> > > Metric: 20
> > > Forward Address: 170.150.7.7
> > > External Route Tag: 0
> > >
> > > R7#
> > > Csc2511-R3#8
> > > [Resuming connection 8 to Csc2620 ... ]
> > >
> > >
> > >
> > > R8>en
> > > R8#sh ip ospf da
> > > R8#sh ip ospf database nssa
> > >
> > > OSPF Router with ID (217.1.8.1) (Process ID
> > > 10)
> > >
> > >
> > > Type-7 AS External Link States
> > (Area
> > > 55)
> > >
> > > LS age: 1781
> > > 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: 217.1.8.1
> > > LS Seq Number: 80000001
> > > Checksum: 0x1EAF
> > > 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
> > >
> > > Routing Bit Set on this LSA
> > > LS age: 881
> > > Options: (No TOS-capability, No Type 7/5
> > > translation, DC)
> > > LS Type: AS External Link
> > > Link State ID: 160.60.60.0 (External Network
> > > Number
> > > )
> > > Advertising Router: 217.1.7.1
> > > LS Seq Number: 80000005
> > > Checksum: 0xD9F8
> > > Length: 36
> > > Network Mask: /22
> > > Metric Type: 1 (Comparable directly to
> > link
> > > state metric)
> > > TOS: 0
> > > Metric: 20
> > > Forward Address: 170.150.7.7
> > > External Route Tag: 0
> > >
> > > R8#
> > >
> > >
> > >
> > > --- Lachlan Kidd <lkidd@netstarnetworks.com>
> > wrote:
> > > > Hi Wei,
> > > > Can you post a 'show ip ospf data nssa' from
> > > r7/r8.
> > > > It may help explain
> > > > what is going on
> > > > Regards,
> > > > Lachlan
> > > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com
> > > > [mailto:nobody@groupstudy.com]On Behalf Of
> > > > Wei Man
> > > > Sent: Tuesday, 15 May 2001 3:10:PM
> > > > To: ccielab@groupstudy.com
> > > > Subject: NSSA and Virtual Link Again
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I am running into problem that Type 7 LSA does
> > not
> > > > converted to Type 5 LSA, any idea how to fix
> > this
> > > ?
> > > >
> > > >
> > > > here is diagram
> > > >
> > > > R5 (Area 0 with
> > Authentication)
> > > > |
> > > > | Area 5
> > > > |
> > > > R7--------R8
> > > > Link between R7 and R8 is in Area 55
> >
> === message truncated ===
>
>
> =====
>
> Vincent
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:41 GMT-3