Yes, you are right, the P bit should be set in this case. Can you
confirm by looking at its router LSA that the originating router doesn't
think it's an ABR for some reason...?
Marcus.
-----Original Message-----
From: Brian [mailto:signal@shreve.net]
Sent: 29 January 2002 13:33
To: Marcus Keane
Cc: cisco-nsp@puck.nether.net
Subject: RE: [nsp] Help, I need good 7206 Multichannel code!
On Tue, 29 Jan 2002, Marcus Keane wrote:
> Brian, is this LSA originated by the ABR/ASBR or from an ASBR inside
> the NSSA? The RFC specifies that LSA originated by an ASBR that is
> also an ABR must clear the P-bit to prevent the LSA from translated by
> another ABR.
The LSA is originated from an ASBR inside the NSSA. It is not
originated
on the ABR/ASBR, so my understanding is the P-bit should be set. I
believe this is possibly a bug.
Brian
> Cheers,
> Marcus.
>
> -----Original Message-----
> From: Brian [mailto:signal@shreve.net]
> Sent: 29 January 2002 13:04
> To: cisco-nsp@puck.nether.net
> Subject: Re: [nsp] Help, I need good 7206 Multichannel code!
>
>
>
> More info to add to this. Basically the P-bit is not being set, and so
> the Type 7 -> Type 5 translation is not taking place:
>
> cygnus#show ip ospf database nssa-external 207.254.220.224
>
> OSPF Router with ID (207.254.193.53) (Process ID 10)
>
> Type-7 AS External Link States (Area 10)
>
> Routing Bit Set on this LSA
> LS age: 94
> Options: (No TOS-capability, No Type 7/5 translation, DC)
> LS Type: AS External Link
> Link State ID: 207.254.220.224 (External Network Number )
> Advertising Router: marshall-gw.shreve.net
> LS Seq Number: 80000001
> Checksum: 0x7FC0
> Length: 36
> Network Mask: /29
> Metric Type: 2 (Larger than any link state path)
> TOS: 0
> Metric: 20
> Forward Address: 208.242.79.1
> External Route Tag: 0
>
>
> This router is an ASBR (since its redistributing some
> statics/connected of its own), and its an ABR for the NSSA (area 10).
> If anyone can shed further light on why the P-bit may not be being
> set, and how I could change that behavior, that would be great. I am
> currently approaching this as if it were a bug, and playing IOS
> roulette.
>
> Brian
>
>
>
> On Mon, 28 Jan 2002, Brian wrote:
>
> >
> >
> > I have been battling a problem on a 7206 all day, and I am stressing
> > over it. 7206 with a PA-MC-2T3+. I tried 12.0(19)S1 and 12.0(7)XE1
> > and both are showing the same problems. Type 7 LSA's are not being
> > translated to Type 5 LSA's for redistribution in the backbone.
> >
> > To run a Multichannel interface, CCO says you need at least 12.0(1)S
> > or 12.0(2)XE2.
> >
> > I have an NSSA on this 7206 (area 10). The 7206 is an ABR between
> > area 10 and 0. The NSSA is configured correctly, the 7206 is
getting
> > all the Type 7 LSA's. The braindead 7206 is announcing Type 5 LSA's
> > for other parts of ospf (such as redistributed statics, connected,
> > etc). But its not doign the 7->5 conversion for routes learned from
> > the NSSA.
> >
> > If anyone is using a Multichannel interface, on a 7206, and has a
> > NSSA
>
> > hanging off it, and can tell me the code they are using, I would
> > really appreciate it.
> >
> > Even if someone just knows of a train that works pretty good on a
> > 7200
>
> > that supports Multichannel, I would try it.
> >
> > Brian
> >
> > -----------------------------------------------
> > Brian Feeny, CCIE #8036 e: signal@shreve.net
> > Network Engineer p: 318.222.2638x109
> > ShreveNet Inc. f: 318.221.6612
> >
> >
>
> -----------------------------------------------
> Brian Feeny, CCIE #8036 e: signal@shreve.net
> Network Engineer p: 318.222.2638x109
> ShreveNet Inc. f: 318.221.6612
>
>
-----------------------------------------------
Brian Feeny, CCIE #8036 e: signal@shreve.net
Network Engineer p: 318.222.2638x109
ShreveNet Inc. f: 318.221.6612
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:30 EDT