From: McClure, Allen (Allen.McClure@Tricon-Yum.Com)
Date: Wed Oct 16 2002 - 14:17:47 GMT-3
Try it without the group statements on your peers and see what happens.
You shouldn't need them for this requirement.
Allen McClure
MCSE, CCNP, CCDP
YUM! Brands, Inc.
Sr. Network Analyst
NEW E-Mail - mailto:allen.mcclure@yum.com
972-338-7494
-----Original Message-----
From: Larson, Chris [mailto:CLarson@usaid.gov]
Sent: Wednesday, October 16, 2002 11:04 AM
To: 'ccielab@groupstudy.com'
Subject: DLSW problem
I am running netbui only on my 2 workstations. They have ethernet and
token cards.
I can get TR to TR dlsw connectivity and see all shares in nethood. I
can get Ether to Ether dlsw connectivity and see all shares in nethood.
I can get Ether to TR in the same router using SR\TLB and DLSW and see
all shares in nethood.
I cannot get ether to tokenring on seperate routers to work. I can debug
and see that the remote sends NETBIOS_NAME_RECOGNIZED in a response to
the NETBIOS_NAME_QUEURY. It appears as if a circuit is established but
the Windows comes up with an error about the net ebing busy.
Below is the debug output from R1 as well as the pertinent config.
Notice R8 is doing both SR\TLB for the local ether to tr as well as
DLSW+ for the remote ethernet on R1.
R1 config:
dlsw local-peer peer-id 150.50.1.1 group 5 promiscuous
dlsw remote-peer 0 tcp 150.50.5.5
dlsw bridge-group 1
!
interface Ethernet0
ip address 150.50.10.1 255.255.255.0
no ip directed-broadcast
bridge-group 1
!
!
!
bridge 1 protocol ieee
!
R8 config:
hostname R8
!
logging rate-limit console 10 except errors
!
ip subnet-zero
no ip finger
no ip domain-lookup
!
cns event-service server
!
!
!
source-bridge ring-group 100
source-bridge transparent 100 1 1 1
dlsw local-peer peer-id 150.50.8.8 group 7 promiscuous
dlsw remote-peer 0 tcp 150.50.7.7
dlsw bridge-group 1
!
!
interface Loopback0
ip address 150.50.8.8 255.255.255.0
!
interface Ethernet0
description Backbone #2
ip address 150.50.80.8 255.255.255.0
no keepalive
bridge-group 1
!
interface TokenRing0
description Ring 2
ip address 150.50.88.8 255.255.255.0
ring-speed 16
source-bridge 200 1 100
source-bridge spanning
!
!
bridge 1 protocol ieee
bridge 1 bitswap-layer3-addresses
Here is the debug on R1. Peers can ping each other just fine.
R1 debug:
1d22h: DLSw: Recv border to member packet from peer 150.50.5.5(2065)
1d22h: %DLSWC-3-RECVSSP: SSP OP = 18( NBNQ ) -explorer from peer
150.50.8.8(2065)
1d22h: DISP Sent : CLSI Msg : UDATA_STN.Req dlen: 90
1d22h: DLSW Received-ctlQ : CLSI Msg : UDATA_STN.Ind dlen: 79
1d22h: CSM: Received CLSI Msg : UDATA_STN.Ind dlen: 79 from DLSw Port0
1d22h: CSM: smac 000a.4fee.dfb6, dmac 0000.f6e6.4468, ssap F0, dsap F0
1d22h: CSM: Received frame type NETBIOS NAME_RECOGNIZED from
000a.4fee.dfb6, DL0
1d22h: DLSw: passive open 150.50.8.8(11030) -> 2065
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:TCP-RD PIPE
OPENED state:DISCONN
1d22h: DLSw: dtp_action_c() opening write pipe for peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:DISCONN->WWR_RDOP
1d22h: DLSw: Async Open Callback 150.50.8.8(2065) -> 11018
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:TCP-WR PIPE
OPENED state:WWR_RDOP
1d22h: DLSw: dtp_action_i() write pipe opened for peer 150.50.8.8(2065)
1d22h: DLSw: CapExId Msg sent to peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:WWR_RDOP->WAIT_CAP
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:SSP-CAP MSG RCVD
state:WAIT_CAP
1d22h: DLSw: dtp_action_j() cap msg rcvd from peer 150.50.8.8(2065)
1d22h: DLSw: Recv CapExId Msg from peer 150.50.8.8(2065)
1d22h: DLSw: received fhpr capex from peer 150.50.8.8(2065): support:
false,
fst-prio: false
1d22h: DLSw: Pos CapExResp sent to peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:WAIT_CAP->WAIT_CAP
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:SSP-CAP MSG RCVD
state:WAIT_CAP
1d22h: DLSw: dtp_action_j() cap msg rcvd from peer 150.50.8.8(2065)
1d22h: DLSw: Recv CapExPosRsp Msg from peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:WAIT_CAP->WAIT_CAP
1d22h: DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev
state:WAIT_CAP
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:SSP-CAP
EXCHANGED state:WAIT_CAP
1d22h: DLSw: dtp_action_k() cap xchged for peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:WAIT_CAP->PCONN_WT
1d22h: DLSw: dlsw_tcpd_fini() for peer 150.50.8.8(2065)
1d22h: DLSw: dlsw_tcpd_fini() closing write pipe for peer 150.50.8.8
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:TCP-CLOSE WR
PIPE state:PCONN_WT
1d22h: DLSw: dtp_action_l() close write pipe for peer 150.50.8.8(2065)
1d22h: DLSw: closing write pipe tcp connection for peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:PCONN_WT->PCONN_WT
1d22h: DLSw: Processing delayed event:TCP-PEER CONNECTED - prev
state:PCONN_WT
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:TCP-PEER
CONNECTED state:PCONN_WT
1d22h: DLSw: dtp_action_m() peer connected for peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:PCONN_WT->CONNECT
1d22h: %DLSWC-3-RECVSSP: SSP OP = 3( CUR ) from peer 150.50.8.8(2065)
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:CORE-ADD CIRCUIT
state:CONNECT
1d22h: DLSw: dtp_action_u(), peer add circuit for peer 150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:CONNECT->CONNECT
1d22h: DLSw: START-FSM (1593835539): event:WAN-CUR state:DISCONNECTED
1d22h: DLSw: core: dlsw_action_c()
1d22h: DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 114
1d22h: DLSw: END-FSM (1593835539): state:DISCONNECTED->REMOTE_RESOLVE
1d22h: DLSW Received-ctlQ : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 114
1d22h: DLSw: START-FSM (1593835539): event:DLC-ReqOpnStn.Cnf
state:REMOTE_RESOLVE
1d22h: DLSw: core: dlsw_action_d()
1d22h: CORE: Setting lf : bits 8 : size 1500
1d22h: DLSw: 1593835539 sent RWO
1d22h: DLSw: 1593835539 sent FCI 80 on ICR - s:0 so:0 r:20 ro:1
1d22h: %DLSWC-3-SENDSSP: SSP OP = 4( ICR ) to peer 150.50.8.8(2065)
success
1d22h: DLSw: END-FSM (1593835539): state:REMOTE_RESOLVE->CKT_PENDING
1d22h: %DLSWC-3-RECVSSP: SSP OP = 5( ACK ) from peer 150.50.8.8(2065)
1d22h: DLSw: 1593835539 recv FCI 0 - s:0 so:0 r:20 ro:1
1d22h: DLSw: 1593835539 recv RWO
1d22h: DLSw: START-FSM (1593835539): event:WAN-ACK state:CKT_PENDING
1d22h: DLSw: core: dlsw_action_x()
1d22h: DLSw: END-FSM (1593835539): state:CKT_PENDING->CKT_ESTABLISHED
1d22h: %DLSWC-3-RECVSSP: SSP OP = 8( CONQ ) from peer 150.50.8.8(2065)
1d22h: DLSw: 1593835539 recv FCA on CONQ - s:20 so:1 r:20 ro:0
1d22h: DLSw: START-FSM (1593835539): event:WAN-CONQ
state:CKT_ESTABLISHED
1d22h: DLSw: core: dlsw_action_i()
1d22h: DISP Sent : CLSI Msg : CONNECT.Req dlen: 16
1d22h: DLSw: END-FSM (1593835539):
state:CKT_ESTABLISHED->CONTACT_PENDING
1d22h: DLSW Received-ctlQ : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 28
1d22h: DLSw: START-FSM (1593835539): event:DLC-Connect.Cnf
state:CONTACT_PENDING
1d22h: DLSw: core: dlsw_action_j()
1d22h: DLSw: 1593835539 sent FCA on CONR
1d22h: %DLSWC-3-SENDSSP: SSP OP = 9( CONR ) to peer 150.50.8.8(2065)
success
1d22h: DISP Sent : CLSI Msg : FLOW.Req dlen: 0
1d22h: DLSw: END-FSM (1593835539): state:CONTACT_PENDING->CONNECTED
1d22h: %DLSWC-3-RECVSSP: SSP OP = 10( INFO ) from peer 150.50.8.8(2065)
1d22h: DLSw: 1593835539 decr r - s:20 so:0 r:19 ro:0
1d22h: DLSw: START-FSM (1593835539): event:WAN-INFO state:CONNECTED
1d22h: DLSw: core: dlsw_action_m()
1d22h: DISP Sent : CLSI Msg : DATA.Req dlen: 34
1d22h: DLSw: END-FSM (1593835539): state:CONNECTED->CONNECTED
1d22h: DLSw: START-TPFSM (peer 150.50.5.5(2065)): event:DLX-KEEPALIVE
REQ state:CONNECT
1d22h: DLSw: dtp_action_q() keepalive request from peer 150.50.5.5(2065)
1d22h: DLSw: Keepalive Response sent to peer 150.50.5.5(2065))
1d22h: DLSw: END-TPFSM (peer 150.50.5.5(2065)): state:CONNECT->CONNECT
1d22h: %DLSWC-3-RECVSSP: SSP OP = 14( HLTQ ) from peer 150.50.8.8(2065)
1d22h: DLSw: START-FSM (1593835539): event:WAN-HLTQ state:CONNECTED
1d22h: DLSw: core: dlsw_action_o()
1d22h: DISP Sent : CLSI Msg : DISCONNECT.Req dlen: 4
1d22h: DLSw: END-FSM (1593835539): state:CONNECTED->HALT_PENDING
1d22h: DLSW Received-ctlQ : CLSI Msg : DISCONNECT.Cfm CLS_OK dlen: 8
1d22h: DLSw: START-FSM (1593835539): event:DLC-Disc.Cnf
state:HALT_PENDING
1d22h: DLSw: core: dlsw_action_p()
1d22h: %DLSWC-3-SENDSSP: SSP OP = 15( HLTR ) to peer 150.50.8.8(2065)
success
1d22h: DISP Sent : CLSI Msg : CLOSE_STN.Req dlen: 4
1d22h: DLSw: END-FSM (1593835539): state:HALT_PENDING->CLOSE_PEND
1d22h: DLSW Received-ctlQ : CLSI Msg : CLOSE_STN.Cfm CLS_OK dlen: 8
1d22h: DLSw: START-FSM (1593835539): event:DLC-CloseStn.Cnf
state:CLOSE_PEND
1d22h: DLSw: core: dlsw_action_y()
1d22h: DLSw: 1593835539 to dead queue
1d22h: DLSw: START-TPFSM (peer 150.50.8.8(2065)): event:CORE-DELETE
CIRCUIT state:CONNECT
1d22h: DLSw: dtp_action_v(), peer delete circuit for peer
150.50.8.8(2065)
1d22h: DLSw: END-TPFSM (peer 150.50.8.8(2065)): state:CONNECT->CONNECT
1d22h: DLSw: END-FSM (1593835539): state:CLOSE_PEND->DISCONNECTED
Christopher Larson - CNE, MCP+I, CCNP + Security
Open Systems Sciences Corp.
USAID Information Resources Management (contractor)
202 712 4559
clarson@usaid.gov
This communication is confidential and may be legally privileged. If you are not the intended recipient, (i) please do not read or disclose to others, (ii) please notify the sender by reply mail, and (iii) please delete this communication from your system. Failure to follow this process may be unlawful. Thank you for your cooperation.
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:48 GMT-3