From: Derek Fage (DerekF@xxxxxxxxxxx)
Date: Thu Jul 08 1999 - 17:43:10 GMT-3
Ron,
DLSW+ will automatically translate between ethernet and T/R. You only need
to configure SR/TLB with DLSW+ if you have ethernet and T/R on the same
router.
Unfortunately, I've blown away my configs as I'm working on something else
now.
Derek...
> -----Original Message-----
> From: Ron Trunk [SMTP:rtrunk@xatlantic.com]
> Sent: 08 July 1999 21:15
> To: Derek Fage; 'Ben Rife'
> Cc: ccielab@groupstudy.com
> Subject: Re: DLSW+
>
> Let me make another attempt at it:
> Your hub has an ethernet interface, and your spoke is running token-ring.
> So what you really want to run is SR/TLB on the hub router. I think the
> reason DLSW is complaining is because you don't have SR/TLB configured
> correctly.
> Just for kicks, remove all the source-route bridging and bridge-group
> statements from both routers (just DLSW by itself) and see if they
> connect.
>
> I hope at least I'm leading you down the right path...
> Ron
>
> -----Original Message-----
> From: Derek Fage <DerekF@itexjsy.com>
> To: 'Ben Rife' <brife@bignet.net>; Derek Fage <DerekF@itexjsy.com>
> Cc: ccielab@groupstudy.com <ccielab@groupstudy.com>
> Date: Thursday, July 08, 1999 3:49 PM
> Subject: RE: DLSW+
>
>
> >Ben,
> >
> >You've got me there !
> >
> >It looks as if the peers get to the stage where they are exchanging
> >capability messages, and there are problems there. You could do a 'show
> dlsw
> >capabilities' on both routers and compare them.
> >
> >One other thing I would do is to add 'lf 1500' on the remote-peer
> statements
> >that point to the router with the ethernet interface to set the largest
> >frame size correctly.
> >
> >Sorry I conldn't be more help, but hopefully somebody may come up with
> some
> >more answers for you.
> >
> >Good luck in the lab !
> >
> >Derek...
> >
> >> -----Original Message-----
> >> From: Ben Rife [SMTP:brife@bignet.net]
> >> Sent: 08 July 1999 20:33
> >> To: Derek Fage
> >> Cc: ccielab@groupstudy.com
> >> Subject: Re: DLSW+
> >>
> >> 5 days left....
> >>
> >> I tried to ping the peer address from each host, I have connectivity.
> >>
> >> Here's the "debug dlsw peer" of the peer that won't connect:
> >>
> >> Dopey#debug dlsw peer
> >> DLSw peer debugging is on
> >> Dopey#
> >> Dopey#
> >> DLSw: START-TPFSM (peer 170.100.6.3(2065)): event:ADMIN-OPEN CONNECTION
> >> state:DI
> >> SCONN
> >> DLSw: dtp_action_a() attempting to connect peer 170.100.6.3(2065)
> >> DLSw: END-TPFSM (peer 170.100.6.3(2065)): state:DISCONN->WAIT_WR
> >>
> >> DLSw: Async Open Callback 170.100.6.3(2065) -> 11138
> >> DLSw: START-TPFSM (peer 170.100.6.3(2065)): event:TCP-WR PIPE OPENED
> >> state:WAIT_
> >> WR
> >> DLSw: dtp_action_f() start read open timer for peer 170.100.6.3(2065)
> >> DLSw: END-TPFSM (peer 170.100.6.3(2065)): state:WAIT_WR->WAIT_RD
> >>
> >> DLSw: passive open 170.100.6.3(11131) -> 2065
> >> DLSw: START-TPFSM (peer 170.100.6.3(2065)): event:TCP-RD PIPE OPENED
> >> state:WAIT_
> >> RD
> >> DLSw: dtp_action_g() read pipe opened for peer 170.100.6.3(2065)
> >> DLSw: CapExId Msg sent to peer 170.100.6.3(2065)
> >> DLSw: END-TPFSM (peer 170.100.6.3(2065)): state:WAIT_RD->WAIT_CAP
> >>
> >> DLSw: START-TPFSM (peer 170.100.6.3(2065)): event:SSP-CAP MSG RCVD
> >> state:WAIT_CA
> >> P
> >> DLSw: dtp_action_j() cap msg rcvd from peer 170.100.6.3(2065)
> >> DLSw: Recv CapExId Msg from peer 170.100.6.3(2065)
> >> DLSw: Unknown CV DC with length 6 from peer 170.100.6.3(2065)
> >> DLSw: Unknown CV DD with length 3 from peer 170.100.6.3(2065)
> >> DLSw: Unknown CV DF with length 3 from peer 170.100.6.3(2065)
> >> DLSw: Unknown CV E1 with length 3 from peer 170.100.6.3(2065)
> >>
> >>
> >>
> >>
> >>
> >>
> >> Here is the configs of the two peers:
> >>
> >>
> >> SPOKE
> >> source-bridge ring-group 2000
> >> dlsw local-peer peer-id 170.100.5.2
> >> dlsw remote-peer 0 tcp 170.100.6.3
> >>
> >>
> >> HUB
> >> source-bridge ring-group 2000
> >> dlsw local-peer peer-id 170.100.6.3
> >> dlsw remote-peer 0 tcp 170.100.6.1
> >> dlsw remote-peer 0 tcp 170.100.5.2
> >> dlsw bridge-group 1
> >>
> >>
> >>
> >> Thanks,
> >>
> >> Ben
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:41 GMT-3