From: Fred Ingham (fingham@cox.net)
Date: Thu Aug 07 2003 - 15:56:12 GMT-3
!!!!
FYI: the error messages:
> 01:14:43: DLSw: Recv CapExNegRsp Msg from peer 153.1.103.1(2065)
> 01:14:43: DLSw: offest: 0x23, reason: 0x8
.
.
> 01:14:46: DLSw: Recv CapExNegRsp Msg from peer 153.1.104.1(2065)
> 01:14:46: DLSw: offest: 0x23, reason: 0x8
indicate that there was problem with the capabilities exchange,
specifically,
that the length of the control vector is invalid. The offset of 0x23 points
to the first vector after the supported sap controlled vector. This is a
good
indication of an IOS problem as you verified. And that the problem was
on r1. The receiver of a negative response is the one that takes down the
connection.
Debug output is good but confusing since there is little documentation
on details.
Cheers, Fred
----- Original Message -----
From: "Jason Cash" <cash2001@swbell.net>
To: <ccielab@groupstudy.com>
Sent: Wednesday, August 06, 2003 11:49 AM
Subject: DLSW border peers with only 1 group?
> Can you have a border group with only 1 group? For some reason, I cannot
> establish DLSW peers in this scenario:
>
> R1(s0)---(s0/0)R3
> |
> (s0)R4
>
> Pretty simple setup, but it just won't happen. Here are the configs:
>
> R1
> dlsw local-peer peer-id 153.1.101.1 group 10 border
> dlsw remote-peer 0 tcp 153.1.103.1 cost 1
> dlsw remote-peer 0 tcp 153.1.104.1 cost 5
> dlsw bridge-group 1
> bridge 1 protocol ieee
>
> R3
> dlsw local-peer peer-id 153.1.103.1 group 10 promiscuous
> dlsw bridge-group 1
> interface FastEthernet0/0
> bridge-group 1
> bridge 1 protocol ieee
>
> R4:
> dlsw local-peer peer-id 153.1.104.1 group 10 promiscuous
> dlsw bridge-group 1
> interface Ethernet0
> bridge-group 1
> bridge 1 protocol ieee
>
> r1#sh dlsw peer
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> TCP 153.1.103.1 DISCONN 0 0 conf 0 0 -
> -
> TCP 153.1.104.1 DISCONN 0 0 conf 0 0 -
> -
> Total number of connected peers: 0
> Total number of connections: 0
>
> When I debug DLSW peers, I get undecipherable output:
>
> r1#deb dlsw peer
> DLSw peer debugging is on
> r1#
> 01:14:42: DLSw: START-TPFSM (peer 153.1.103.1(2065)): event:ADMIN-OPEN
> CONNECTION state:DISCONN
> 01:14:42: DLSw: dtp_action_a() attempting to connect peer
153.1.103.1(2065)
> 01:14:42: DLSw: END-TPFSM (peer 153.1.103.1(2065)): state:DISCONN->WAIT_WR
>
> 01:14:42: DLSw: Async Open Callback 153.1.103.1(2065) -> 11088
> 01:14:42: DLSw: START-TPFSM (peer 153.1.103.1(2065)): event:TCP-WR PIPE
> OPENED state:WAIT_WR
> 01:14:42: DLSw: dtp_action_f() start read open timer for peer
> 153.1.103.1(2065)
> 01:14:42: DLSw: END-TPFSM (peer 153.1.103.1(2065)): state:WAIT_WR->WAIT_RD
>
> 01:14:42: DLSw: passive open 153.1.103.1(11051) -> 2065
> 01:14:42: DLSw: START-TPFSM (peer 153.1.103.1(2065)): event:TCP-RD PIPE
> OPENED state:WAIT_RD
> 01:14:42: DLSw: dtp_action_g() read pipe opened for peer 153.1.103.1(2065)
> 01:14:42: DLSw: CapExId Msg sent to peer 153.1.103.1(2065)
> 01:14:42: DLSw: END-TPFSM (peer 153.1.103.1(2065)):
state:WAIT_RD->WAIT_CAP
>
> 01:14:43: DLSw: START-TPFSM (peer 153.1.103.1(2065)): event:SSP-CAP MSG
RCVD
> state:WAIT_CAP
> 01:14:43: DLSw: dtp_action_j() cap msg rcvd from peer 153.1.103.1(2065)
> 01:14:43: DLSw: Recv CapExNegRsp Msg from peer 153.1.103.1(2065)
> 01:14:43: DLSw: offest: 0x23, reason: 0x8
> 01:14:43: DLSw: END-TPFSM (peer 153.1.103.1(2065)):
state:WAIT_CAP->WAIT_CAP
>
> 01:14:43: DLSw: Processing delayed event:ADMIN-CLOSE CONNECTION - prev
> state:WAIT_CAP
> 01:14:43: DLSw: START-TPFSM (peer 153.1.103.1(2065)): event:ADMIN-CLOSE
> CONNECTION state:WAIT_CAP
> 01:14:43: DLSw: dtp_action_b() close connection for peer 153.1.103.1(2065)
> 01:14:43: DLSw: aborting tcp connection for peer 153.1.103.1(2065)
> 01:14:43: DLSw: aborting tcp connection for peer 153.1.103.1(11051)
> 01:14:43: DLSw: END-TPFSM (peer 153.1.103.1(2065)):
state:WAIT_CAP->DISCONN
>
> 01:14:45: DLSw: START-TPFSM (peer 153.1.104.1(2065)): event:ADMIN-OPEN
> CONNECTION state:DISCONN
> 01:14:45: DLSw: dtp_action_a() attempting to connect peer
153.1.104.1(2065)
> 01:14:45: DLSw: END-TPFSM (peer 153.1.104.1(2065)): state:DISCONN->WAIT_WR
>
> 01:14:45: DLSw: Async Open Callback 153.1.104.1(2065) -> 11089
> 01:14:45: DLSw: START-TPFSM (peer 153.1.104.1(2065)): event:TCP-WR PIPE
> OPENED state:WAIT_WR
> 01:14:45: DLSw: dtp_action_f() start read open timer for peer
> 153.1.104.1(2065)
> 01:14:45: DLSw: END-TPFSM (peer 153.1.104.1(2065)): state:WAIT_WR->WAIT_RD
>
> 01:14:46: DLSw: passive open 153.1.104.1(11039) -> 2065
> 01:14:46: DLSw: START-TPFSM (peer 153.1.104.1(2065)): event:TCP-RD PIPE
> OPENED state:WAIT_RD
> 01:14:46: DLSw: dtp_action_g() read pipe opened for peer 153.1.104.1(2065)
> 01:14:46: DLSw: CapExId Msg sent to peer 153.1.104.1(2065)
> 01:14:46: DLSw: END-TPFSM (peer 153.1.104.1(2065)):
state:WAIT_RD->WAIT_CAP
>
> 01:14:46: DLSw: START-TPFSM (peer 153.1.104.1(2065)): event:SSP-CAP MSG
RCVD
> state:WAIT_CAP
> 01:14:46: DLSw: dtp_action_j() cap msg rcvd from peer 153.1.104.1(2065)
> 01:14:46: DLSw: Recv CapExNegRsp Msg from peer 153.1.104.1(2065)
> 01:14:46: DLSw: offest: 0x23, reason: 0x8
> 01:14:46: DLSw: END-TPFSM (peer 153.1.104.1(2065)):
state:WAIT_CAP->WAIT_CAP
>
> 01:14:46: DLSw: Processing delayed event:ADMIN-CLOSE CONNECTION - prev
> state:WAIT_CAP
> 01:14:46: DLSw: START-TPFSM (peer 153.1.104.1(2065)): event:ADMIN-CLOSE
> CONNECTION state:WAIT_CAP
> 01:14:46: DLSw: dtp_action_b() close connection for peer 153.1.104.1(2065)
> 01:14:46: DLSw: aborting tcp connection for peer 153.1.104.1(2065)
> 01:14:46: DLSw: aborting tcp connection for peer 153.1.104.1(11039)
> 01:14:46: DLSw: END-TPFSM (peer 153.1.104.1(2065)):
state:WAIT_CAP->DISCONN
>
>
> _______________________________________________________________________
> You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:55 GMT-3