Re: doubt on dlsw and isdn

From: Donny MATEO (donny.mateo@sg.ca-indosuez.com)
Date: Fri Oct 04 2002 - 06:56:16 GMT-3


what about keepalive 0 ?

Donny

                      Le Dinh An
                      <anld@ispco.com.v To: Svuillaume8@aol.com
                      n> cc: bpjain@cisco.com, brian@5g.net,
                      ccielab@groupstudy.com
                      Sent by: Subject: Re: doubt on dlsw and isdn
                      nobody@groupstudy
                      .com

                      04-10-2002 14:18
                      Please respond to
                      Le Dinh An

Hi,

I'm using dlsw dynamic peer as you've mentioned. It seems to work but I
don't know how come the Dialer0 is brought up whenever inactivity
timeout occurs? If I set the inactivity period to 2 mins, which equals
to the idle timer of the DDR, the link is brought up right after being
shutdown!

Please help!

Thanks,

An.

01:42:44: %DIALER-6-UNBIND: Interface Async65 unbound from profile Dialer0
01:42:46: %LINK-5-CHANGED: Interface Async65, changed state to reset
01:42:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async65,
changed state to down
01:42:51: %LINK-3-UPDOWN: Interface Async65, changed state to downDLSw:
closing conn for dynamic peer 15.0.0.1(2065); no llc
01:45:44: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:ADMIN-CLOSE
CONNECTION state:CONNECT
01:45:44: DLSw: dtp_action_b() close connection for peer 15.0.0.1(2065)
01:45:44: DLSw: aborting tcp connection for peer 15.0.0.1(11016)
01:45:44: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:CONNECT->DISCONN

01:45:47: %LINK-3-UPDOWN: Interface Async65, changed state to up
01:45:47: %DIALER-6-BIND: Interface Async65 bound to profile Dialer0
01:45:48: DLSw: Packet for disconnected dynamic peer 15.0.0.1
01:45:48: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:ADMIN-OPEN
CONNECTION state:DISCONN
01:45:48: DLSw: dtp_action_a() attempting to connect peer 15.0.0.1(2065)
01:45:48: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:DISCONN->WAIT_WR

01:45:48: DLSw: Async Open Callback 15.0.0.1(2065) -> 11063
01:45:48: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:TCP-WR PIPE
OPENED state:WAIT_WR
01:45:48: DLSw: dtp_action_f() start read open timer for peer
15.0.0.1(2065)
01:45:48: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_WR->WAIT_RD

01:45:48: DLSw: dlsw_tcpd_fini() for peer 15.0.0.1(2065)
01:45:48: DLSw: tcp fini closing connection for peer 15.0.0.1(2065)
01:45:48: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:ADMIN-CLOSE
CONNECTION state:WAIT_RD
01:45:48: DLSw: dtp_action_b() close connection for peer 15.0.0.1(2065)
01:45:48: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_RD->DISCONN

01:45:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async65,
changed state to up
01:45:55: DLSw: Packet for disconnected dynamic peer 15.0.0.1
01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:ADMIN-OPEN
CONNECTION state:DISCONN
01:45:55: DLSw: dtp_action_a() attempting to connect peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:DISCONN->WAIT_WR

01:45:55: DLSw: frame failed (2) to be sent to peer 15.0.0.1(2065)
01:45:55: DLSw: frame failed (2) to be sent to peer 15.0.0.1(2065)
01:45:55: DLSw: Async Open Callback 15.0.0.1(2065) -> 11064
01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:TCP-WR PIPE
OPENED state:WAIT_WR
01:45:55: DLSw: dtp_action_f() start read open timer for peer
15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_WR->WAIT_RD

01:45:55: DLSw: passive open 15.0.0.1(11017) -> 2065
01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:TCP-RD PIPE
OPENED state:WAIT_RD
01:45:55: DLSw: dtp_action_g() read pipe opened for peer 15.0.0.1(2065)
01:45:55: DLSw: CapExId Msg sent to peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_RD->WAIT_CAP

01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:SSP-CAP MSG
RCVD state:WAIT_CAP
01:45:55: DLSw: dtp_action_j() cap msg rcvd from peer 15.0.0.1(2065)
01:45:55: DLSw: Recv CapExPosRsp Msg from peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_CAP->WAIT_CAP

01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:SSP-CAP MSG
RCVD state:WAIT_CAP
01:45:55: DLSw: dtp_action_j() cap msg rcvd from peer 15.0.0.1(2065)
01:45:55: DLSw: Recv CapExId Msg from peer 15.0.0.1(2065)
01:45:55: DLSw: Unknown CV E1 with length 3 from peer 15.0.0.1(2065)
01:45:55: DLSw: Unknown CV E2 with length 4 from peer 15.0.0.1(2065)
01:45:55: DLSw: Unknown CV E3 with length 8 from peer 15.0.0.1(2065)
01:45:55: DLSw: Pos CapExResp sent to peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_CAP->WAIT_CAP

01:45:55: DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev
state:WAIT_CAP
01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:SSP-CAP
EXCHANGED state:WAIT_CAP
01:45:55: DLSw: dtp_action_k() cap xchged for peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:WAIT_CAP->PCONN_WT

01:45:55: DLSw: dlsw_tcpd_fini() for peer 15.0.0.1(2065)
01:45:55: DLSw: dlsw_tcpd_fini() closing write pipe for peer 15.0.0.1
01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:TCP-CLOSE WR
PIPE state:PCONN_WT
01:45:55: DLSw: dtp_action_l() close write pipe for peer 15.0.0.1(2065)
01:45:55: DLSw: closing write pipe tcp connection for peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:PCONN_WT->PCONN_WT

01:45:55: DLSw: Processing delayed event:TCP-PEER CONNECTED - prev
state:PCONN_WT
01:45:55: DLSw: START-TPFSM (peer 15.0.0.1(2065)): event:TCP-PEER
CONNECTED state:PCONN_WT
01:45:55: DLSw: dtp_action_m() peer connected for peer 15.0.0.1(2065)
01:45:55: DLSw: END-TPFSM (peer 15.0.0.1(2065)): state:PCONN_WT->CONNECT

Svuillaume8@aol.com wrote:

>In my opinion the timeout value are necesserary,
>
>dlsw remote peer 0 tcp 1.1.1.1 dynamique inactivity 2 keepalive 0 timeout 300
>
>the other side
>
>dlsw local-peer peer-id 2.2.2.2 promiscuous
>dlsw prom keepalive 0
>
>And a tips: Don't forget netbios-keepalive filter if you are using netbeui!!!!!!!!

This message is for information purposes only and its content
should not be construed as an offer, or solicitation of an offer,
to buy or sell any banking or financial instruments or services
and no representation or warranty is given in respect of its
accuracy, completeness or fairness. The material is subject
to change without notice. You should take your own independent
tax, legal and other professional advice in respect of the content
of this message. This message may contain confidential or
legally privileged material and may not be copied, redistributed
or published (in whole or in part) without our prior written consent.
This email may have been intercepted, partially destroyed,
arrive late, incomplete or contain viruses and no liability is
accepted by any member of the Credit Agricole Indosuez group
as a result. If you are not the intended recipient of this message,
please immediately notify the sender and delete this message
from your computer.

This message is for information purposes only and its content
should not be construed as an offer, or solicitation of an offer,
to buy or sell any banking or financial instruments or services
and no representation or warranty is given in respect of its
accuracy, completeness or fairness. The material is subject
to change without notice. You should take your own independent
tax, legal and other professional advice in respect of the content
of this message. This message may contain confidential or
legally privileged material and may not be copied, redistributed
or published (in whole or in part) without our prior written consent.
This email may have been intercepted, partially destroyed,
arrive late, incomplete or contain viruses and no liability is
accepted by any member of the Credit Agricole Indosuez group
as a result. If you are not the intended recipient of this message,
please immediately notify the sender and delete this message
from your computer.



This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:38 GMT-3