From: Church, Chuck (cchurch@xxxxxxxx)
Date: Fri Mar 08 2002 - 21:57:00 GMT-3
That's a good idea. It seems the 2500's token ring interfaces default to
about 4kb MTU at 16mbit, but 2600's and up default to 16kb at 16mbit. OSPF
will give you lots of 'too many retransmissions' errors. We discovered this
in NMC-1. Either set the MTU, or use 4 mbit speed. It's possible DLSW
doesn't like it either.
Chuck Church
CCIE #8776, MCNE, MCSE
Sr. Network Engineer
Magnacom Technologies
140 N. Rt. 303
Valley Cottage, NY 10989
845-267-4000
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
John Mistichelli
Sent: Friday, March 08, 2002 7:17 PM
To: Bob Sinclair
Cc: ccielab@groupstudy.com
Subject: RE: DLSW Troubleshooting
Just a thought...
Try lowering the MTU on To1/0.
-----Original Message-----
From: Bob Sinclair [mailto:bsin@erols.com]
Sent: Friday, March 08, 2002 7:14 PM
To: jmistichelli@yahoo.com
Cc: ccielab@groupstudy.com
Subject: Re: DLSW Troubleshooting
Yes. I am running NetBEUI. The two other PCs can netview just fine. When
I switch the PCs to different routers, it pretty much seems clear that the
problem is with the router, not the PCs. Relevant portions of he config
below:
!
source-bridge ring-group 100
dlsw local-peer peer-id 148.6.6.6
dlsw remote-peer 0 tcp 148.6.3.3 lf 1500
dlsw remote-peer 0 tcp 148.6.4.4 lf 1500
!
!interface TokenRing1/0
mtu 4464
no ip address
ring-speed 16
source-bridge 2 1 100
source-bridge spanning
!
R6#sh dlsw peers
Peers: state pkts_rx pkts_tx type drops ckts TCP
uptime
TCP 148.6.3.3 CONNECT 560 477 conf 0 0 0
03:17:58
TCP 148.6.4.4 CONNECT 499 492 conf 0 0 0
03:17:47
Total number of connected peers: 2
Total number of connections: 2
R6#
The only thing different about this router I can see is that it is a 3620.
Have had DLSW running fine on it before. Have tried various mtu settings.
Rebooted it.
----- Original Message -----
From: "John Mistichelli" <jmistichelli@yahoo.com>
To: "Bob Sinclair" <bsin@erols.com>; <ccielab@groupstudy.com>
Sent: Friday, March 08, 2002 7:06 PM
Subject: RE: DLSW Troubleshooting
> Just a REAL basic question for you...
>
> Are you running NetBEUI on these PCs?
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Bob Sinclair
> Sent: Friday, March 08, 2002 6:22 PM
> To: ccielab@groupstudy.com
> Subject: DLSW Troubleshooting
>
>
> DLSW Experts:
>
> I have three routers, fully meshed with tcp remote peer statements. All
are
> showing two connected peers. DLSW capabilities shows all three are aware
of
> the PC's behind the other routers, and the local pc. Yet, the PC behind
R6,
> on a token ring segment, cannot reach others or be reached. Even though
the
> other peers know it is there (reachability). Have switched PC's so I
know
> that is not the issue. There are no filters. Below are output of debugs.
> Testing is by net view \\ on the pc's. Whenever the PC behind R6 tries
to
> contact another, it gets "network path not found". Same when others try
to
> reach it. Other two peers can reach each other fine. Bottom line, other
> peers see it as reachable, but can't contact it.
>
>
> Below is debug when another peer tries to reach this one. 148.6.4.4 is the
> peer address of the peer trying to reach this one.
>
> R6#
> R6#
> 02:17:21: %DLSWC-3-RECVSSP: SSP OP = 18( NBNQ ) -explorer from peer
> 148.6.4.4(2065)
> R6#
> 02:17:21: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:21: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> R6#
> 02:17:23: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:23: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:24: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:24: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> R6#
> 02:17:24: %DLSWC-3-RECVSSP: SSP OP = 18( NBNQ ) -explorer from peer
> 148.6.4.4(2065)
> R6#
> 02:17:25: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:25: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:26: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:26: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> R6#
> 02:17:27: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:17:27: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
>
>
>
>
> Below is debug when this one tries to reach another. 148.6.3.3 is the
peer
> router of the pc name I am trying to reach.
>
>
> R6#
> R6#
> 02:18:27: DLSW Received-ctlQ : CLSI Msg : UDATA_STN.Ind dlen: 84
> 02:18:27: %DLSWC-3-RECVSSP: SSP OP = 19( NBNR ) -explorer from peer
> 148.6.3.3(2065)
> 02:18:27: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:18:27: DLSW Received-ctlQ : CLSI Msg : UDATA_STN.Ind dlen: 84
> 02:18:27: %DLSWC-3-RECVSSP: SSP OP = 19( NBNR ) -explorer from peer
> 148.6.3.3(2065)
> R6#
> 02:18:27: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> 02:18:28: DLSW Received-ctlQ : CLSI Msg : UDATA_STN.Ind dlen: 84
> 02:18:28: %DLSWC-3-RECVSSP: SSP OP = 19( NBNR ) -explorer from peer
> 148.6.3.3(2065)
> R6#
> 02:18:28: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
> R6#
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:57 GMT-3