Having trouble with LANE - can someone identify this cause code?

Having trouble with LANE - can someone identify this cause code?

Post by Brad Benso » Fri, 25 Oct 1996 04:00:00



Can you let us know what problems indicate that the LANE code is
picky?  We're very interested in fixing interoperability problems.

Brad

Quote:

> The Cisco Lane code is a little picky, it would be nice to know what it
> tries to ask from the switches/LANE servers. We had a case where some other
> devices worked, but Ciscos could not join the LANE, even if
> the LANE servers were at the nearest switch.

> When we removed a typo from a static IISP route (which had nothing to
> do with this LANE) the Ciscos were suddenly able to join the lane again..

> VesA

 
 
 

Having trouble with LANE - can someone identify this cause code?

Post by Brad Benso » Fri, 25 Oct 1996 04:00:00


Ditto.  Can you send the config?  It appears that the LES is on the
same box, so you might also turn on the server debug...

> Having just went thru something similar, it would help to
> include the ATM config lines from the Cat5 and the 7507.
> Which is the LECs and which is the server-bus....

> /darrel

> ==============================================================================

> > Date: Thu, 17 Oct 1996 15:59:24 -0700 (PDT)


> > Subject: Having trouble with LANE - can someone identify this cause code?

> > For some reason which I'm just not seeing, I'm unable to get an ELAN working
> > between a Cat5k and 7507.  Running with debugging turned on gave me the
> > following:

> >    LEC ATM1/0.10: sending LISTEN
> >    LEC ATM1/0.10:   listen on      39.000000000000000000000000.00602F066C20.0A
> >    LEC ATM1/0.10: received LISTEN
> >    LEC ATM1/0.10: sending SETUP
> >    LEC ATM1/0.10:   callid         0x60EB713C
> >    LEC ATM1/0.10:   called party   39.000000000000000000000000.00602F066C23.00
> >    LEC ATM1/0.10:   calling_party  39.000000000000000000000000.00602F066C20.0A
> >    LEC ATM1/0.10: received CONNECT
> >    LEC ATM1/0.10:   callid         0x60EB713C
> >    LEC ATM1/0.10:   vcd            634
> >    LEC ATM1/0.10: sending RELEASE
> >    LEC ATM1/0.10:   callid         0x60EB713C
> >    LEC ATM1/0.10:   cause code     31
> >    LEC ATM1/0.10: received RELEASE_COMPLETE
> >    LEC ATM1/0.10:   callid         0x60EB713C
> >    LEC ATM1/0.10:   cause code     31
> >    LEC ATM1/0.10: sending SETUP
> >    LEC ATM1/0.10:   callid         0x60EAA550
> >    LEC ATM1/0.10:   called party   39.000000000000000000000000.00602F066C21.10
> >    LEC ATM1/0.10:   calling_party  39.000000000000000000000000.00602F066C20.0A
> >    LEC ATM1/0.10: received RELEASE
> >    LEC ATM1/0.10:   callid         0x60EAA550
> > >  LEC ATM1/0.10:   cause code     1
> >    LEC ATM1/0.10: sending RELEASE_COMPLETE
> >    LEC ATM1/0.10:   callid         0x60EAA550
> >    LEC ATM1/0.10:   cause code     31
> >    LEC ATM1/0.10: sending CANCEL
> >    LEC ATM1/0.10:   ATM address    39.000000000000000000000000.00602F066C20.0A
> >    LEC ATM1/0.10: received CANCEL

> > I've place a '>' to the left of the line in which I'm interested.  Can someone
> > tell me what the meaning of that cause code is?

> > I've got several other ELANs working just fine, but this one refuses to
> > cooperate.

> > Thanks in advance,
> > mb


 
 
 

Having trouble with LANE - can someone identify this cause code?

Post by Petri Heleniu » Tue, 29 Oct 1996 04:00:00


Quote:Vesa Halkka writes:

 > The Cisco Lane code is a little picky, it would be nice to know what it
 > tries to ask from the switches/LANE servers. We had a case where some other
 > devices worked, but Ciscos could not join the LANE, even if
 > the LANE servers were at the nearest switch.
 >
 > When we removed a typo from a static IISP route (which had nothing to
 > do with this LANE) the Ciscos were suddenly able to join the lane again..
 >
The Cisco LANE code has had it setbacks but with current form, not
counting it's continuing instability on some platforms, it's one of
the better conformant to the specification. It's not to the letter
though, as is nobody else I know of.

Pete

 
 
 

Having trouble with LANE - can someone identify this cause code?

Post by Darrel Beach - Cisco System » Tue, 29 Oct 1996 04:00:00


Unless of course the NSAP address of the LECS or the LES/BUS of
any emulated LANS was prefixed by the IISP prefix with the
typo....


> Date: Thu, 24 Oct 1996 10:54:02 -0700 (PDT)



> Subject: Re: Having trouble with LANE - can someone identify this cause code?

> Can you let us know what problems indicate that the LANE code is
> picky?  We're very interested in fixing interoperability problems.

> Brad

> > The Cisco Lane code is a little picky, it would be nice to know what it
> > tries to ask from the switches/LANE servers. We had a case where some other
> > devices worked, but Ciscos could not join the LANE, even if
> > the LANE servers were at the nearest switch.

> > When we removed a typo from a static IISP route (which had nothing to
> > do with this LANE) the Ciscos were suddenly able to join the lane again..

> > VesA