RE: [nsp] Help, I need good 7206 Multichannel code!

From: Brian (signal@shreve.net)
Date: Tue Jan 29 2002 - 00:51:55 EST


On Tue, 29 Jan 2002, Marcus Keane wrote:

> Brian,
>
> What could have happened is that a network statement for area 0 was
> entered by mistake and then removed and the router hasn't completely
> "forgotten" about it. You can try "clear ip ospf process" or failing
> that a reload in order of relative disruption.

Marcus,

No these routers were reloaded to hell and back :) The problematic router
was running 12.0(7)XK2 code (mz-is image). It needed the XK line because
of some 1FE2W's in it, its a 3640.

Downgrading to 12.0(7)XK1 fixed the problem. I do appreciate you taking
the time in helping. I was getting so frustrated, I probably would not
have thought to check to see if the NSSA ASBR was mistaking itself for an
ABR/ASBR.

Brian

> Cheers,
> Marcus.
>
> -----Original Message-----
> From: Brian [mailto:signal@shreve.net]
> Sent: 29 January 2002 14:32
> To: Marcus Keane
> Cc: cisco-nsp@puck.nether.net
> Subject: RE: [nsp] Help, I need good 7206 Multichannel code!
>
>
>
>
> Marcus, that seems to be the case:
>
> marshall-gw#show ip ospf data
>
> OSPF Router with ID (207.254.193.52) (Process ID 10)
>
>
> Router Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum Link
> count
> 207.254.193.52 207.254.193.52 575 0x80000001 0xF8BE 0
>
> Router Link States (Area 10)
>
> Link ID ADV Router Age Seq# Checksum Link
> count
> 207.254.193.52 207.254.193.52 546 0x8000000B 0xE618 5
> 207.254.193.53 207.254.193.53 547 0x8000000A 0xFAD6 4
>
>
>
> the NSSA ASBR is 207.254.193.52, and it thinks its in area 0 and 10, but
>
> its an NSSA in area 10. There is nothing in the config to account for
> this.
>
> router ospf 10
> area 10 nssa
> redistribute connected subnets
> redistribute static subnets
> redistribute rip subnets
> passive-interface FastEthernet0/0
> passive-interface Serial1/0
> network 207.254.193.176 0.0.0.3 area 10
> network 207.254.193.180 0.0.0.3 area 10
> network 208.242.79.0 0.0.0.15 area 10
>
>
> Brian
>
>
> Brian
>
>
> On Tue, 29 Jan 2002, Marcus Keane wrote:
>
> > 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
> >
> >
>
> -----------------------------------------------
> 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