Re: unidentified snap frame from catalyst keeping up isdn betweendlsw peers

From: David FAHED (dfahed@xxxxxxxxxxxx)
Date: Fri Jan 19 2001 - 20:10:25 GMT-3


   
Try to disable CDP on the interface

"Connary, Julie Ann" wrote:

> Hi,
>
> can anyone tell me what these snap frames originating from a catalyst and
> going between my DLSW peers are:
>
> 01:58:53: CSM: Received CLSI Msg : UDATA_STN.Ind dlen: 70 from DLSw Port0
> 01:58:53: CSM: smac 0006.f418.e71d, dmac 8000.3033.3333, ssap AA, dsap AA
> 01:58:53: BR0 DDR: ip (s=170.100.3.1, d=170.100.25.2), 170 bytes, outgoing
> inter
> esting (ip PERMIT)
> 01:58:53: DLSW Received-ctlQ : CLSI Msg : UDATA_STN.Ind dlen: 112
>
> They are definitely SNAP frames and the are being sourced from the Catalyst
> I am using
> to setup ethernet vlans in my test networks.
>
> Are these Bridge BPDU's?
>
> Can they be safely filtered?
>
> I am doing some ddr testing for dlsw and I have determined that:
>
> 1. you need to do dlsw netbios-keepalive-filter on both peers on either
> side of the isdn link
> 2. you need to set the keepalive to 0 and the timeout to 90 on your remote
> peers.
>
> This will keep your link quiet, your netbios connection up and when other
> interesting traffic between the DLSW peers
> comes along, correctly invoke the isdn line.
>
> However these pesky snap packets are in the way. I notice that all my
> peers see the catalysts in their reachability
> cache's.
>
> Julie Ann
> ------------------------------------------------------------------------
> Julie Ann Connary
> | | Network Consulting Engineer
> ||| ||| Federal Support Program
> .|||||. .|||||. 13635 Dulles Technology Drive,
> Herndon VA 20171
> .:|||||||||:.:|||||||||:. Pager: 1-888-642-0551
> c i s c o S y s t e m s Email: jconnary@cisco.com
>
> ------------------------------------------------------------------------
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:36 GMT-3