From: fningham@xxxxxxx
Date: Tue Jun 18 2002 - 17:39:06 GMT-3
Craig: I changed the bridge number on all but the
bridge number here is not relevant, any number between
1-15 should work. I thought I saw bridge 14 on one of
your R6 displays (sh sou). I had the bridge numbers
different on R2/R4 so the RIF wouldn't be the same.
If you are seeing the packet on a sniffer but the
name/MAC isn't appearing in the local cache and doesn't
show in a deb dlsw then I suspect there is a problem
with the PC or the router connecting to the local ring.
On the router you can enter a "show lnm station" and
you should see a list of ring stations. (This command
is for the IBM Lan Net Manager and will show all
stations on the ring and their ring function.) You
should see the router MAC, usually as active monitor,
and the PC. Are you using a MAU or a TR switch? If
you don't see both on both ends then troubleshoot ring
connectivity.
Could be the IOS but I have used anything above 11.0
with minimal problems. I assume you have the right
feature set on all routers since the peers are
connected.
Configs look good but I'd put an lf 1500 on the
R6/R4/R2 local and remote peer statements for good
practices.
I'll send a separate e-mail for an off-line discussion.
> Thanks. I can't figure this one out. Questions:
> 1) Did you intend on changing the bridge #'s on the token interfaces to 14
> on all. I tried it, it didn't work. I changed them back to 2 on R6, and
> 14 on R4, R2. ?
>
> 2) Could it be the IOS version I'm running. The sniffer see's the NetBios
> Name query coming from the PC. The DLSW peer is connected. But, DLSW
> Debug doesn't show the name query packet come into the router.
>
> Latest config's and IOS ver's attached.
> Thank you kindly,
> -Craig.
>
>
> >R6: source-bridge ring-group 999
> > dlsw local-peer peer-id 135.2.66.66
> > dlsw remote-peer 0 tcp 135.2.24.4
> > dlsw remote-peer 0 tcp 135.2.24.2
> >
> > int tok 1/1/0
> > ring speed 16
> > source-bridge 200 2 999
> > source-bridge spanning
> >
> >R2: source-bridge ring-group 999
> > dlsw local-peer peer-id 135.2.24.2 prom
> >
> > int tok 0
> > ip add 135.2.24.2 255.255.255.0
> > ring 16
> > source-bridge 100 14 999
> > source-bridge spanning
> >
> >R4: source-bridge ring-group 999
> > dlsw local-peer peer-id 135.2.24.4 prom
> >
> > int tok 0
> > ip add 135.2.24.4 255.255.255.0
> > ring 16
> > source-bridge 100 14 999
> > source-bridge spanning
>
>
> At 05:16 PM 6/18/2002 +0000, fningham@att.net wrote:
> >Craig: Your configs were deleted but they could be:
> >
> >R6: source-bridge ring-group 999
> > dlsw local-peer peer-id <r6 address>
> > dlsw remote-peer 0 tcp 135.2.24.4
> > dlsw remote-peer 0 tcp 135.2.24.2
> >
> > int tok 1/1/0
> > ring speed 16
> > source-bridge 200 14 999
> > source-bridge spanning
> >
> >R2: source-bridge ring-group 999
> > dlsw local-peer peer-id 135.2.24.2 prom
> >
> > int tok 0
> > ip add 135.2.24.2 255.255.255.0
> > ring 16
> > source-bridge 100 1 999
> > source-bridge spanning
> >
> >R4: source-bridge ring-group 999
> > dlsw local-peer peer-id 135.2.24.4 prom
> >
> > int tok 0
> > ip add 135.2.24.4 255.255.255.0
> > ring 16
> > source-bridge 100 14 999
> > source-bridge spanning
> >
> >If your PC's are set up correctly with NetBIOS,
> >a "find", or "net view" command should put the PC name
> >and MAC address in the local reachability cache. If
> >it's not there, on either end, troubleshoot PC config.
> >You can do a deb dlsw and see if there is a NB packet
> >received from the PC with a dest MAC of
> >0xc000.0000.0080. This is the name-query packet sent
> >by the PC.
> >
> >If the PC is in the local reachability cache but not in
> >the remote reachability cache, troubleshoot IP
> >connectivity between peers.
> >
> >If your still having troubles, e-mail you configs and
> >the output from sh sou, and sh dlsw rea on R6, R4, and
> >R2.
> >
> >HTH, Fred
> > > The following in my network. Attached are config files and sh
> > > commands. The DLSW peer's connect ok, but the netbios traffic never
> > > propagates, and the 'show dlsw reach' is empty. I also noticed that with
> > > 'show source' the TCP Peername not set message. Is this the problem. I
> > > thought DLSW+ was to allow connect without peernames, especially over
> > token
> > > ring.
> > > Thank you kindly for your help,
> > > -Craig.
> > >
> > > [Win 2000 PC] netbios
> > > |
> > > (tokenring 200, Brdg 2)
> > > R6
> > > /\
> > > / \
> > > frame / \ ethernet
> > > / \
> > > R4 R2
> > > \ /
> > > \ /
> > > \ /
> > > (tokenring 100, brdg 14)
> > > |
> > > [Win 95 pc] netbios
> > >
> > >
> > > ex:
> > > end
> > >
> > > r6#sh dl pe
> > > Peers: state pkts_rx pkts_tx type drops ckts
> > > TCP uptime
> > > TCP 135.2.24.4 CONNECT 97 97 conf 0 0 0
> > > 00:47:31
> > > TCP 135.2.24.2 CONNECT 96 96 conf 0 0 0
> > > 00:47:16
> > > Total number of connected peers: 2
> > > Total number of connections: 2
> > >
> > > r6#
> > >
> > > r6#sh sour
> > >
> > > Local Interfaces: receive transmit
> > > srn bn trn r p s n max
> > hops cnt cnt drops
> > > To1/1/0 200 14 999 * b 7 7 7 18 0 14
> > >
> > > Global RSRB Parameters:
> > > TCP Queue Length maximum: 100
> > >
> > > Ring Group 999:
> > > No TCP peername set, TCP transport disabled
> > > Maximum output TCP queue length, per peer: 100
> > > Rings:
> > > bn: 14 rn: 200 local ma: 400b.3d1e.1f14 TokenRing1/1/0 fwd:
0
> > >
> > > Explorers: ------- input ------- ------- output -------
> > > spanning all-rings total spanning all-rings tota
l
> > > To1/1/0 0 3 3 0 0 0
> > >
> > > Explorer fastswitching enabled
> > > Local switched: 17 flushed 0 max Bps 38400
> > >
> > > rings inputs bursts throttles output
> > drops
> > > To1/1/0 17 0 0
> > 0
> > >
> > > r6#
> > >
> > > [GroupStudy.com removed an attachment of type application/zip which had
> > a name
> > > of dlsw+.zip"; x-mac-type="705A4950"; x-mac-creator="705A4950]
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:37 GMT-3