RE: ISDN over DLSW

From: Hunt Lee (huntl@webcentral.com.au)
Date: Tue Dec 31 2002 - 02:06:18 GMT-3

Next message: Janto Cin: "BGP and RIP route"
Previous message: Larry Yurdin: "dlsw timer command"
Maybe in reply to: Hunt Lee: "ISDN over DLSW"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Thanks for that =) I wonder why did Cisco uses "Promiscious" keyword on
the backup peer (Tanius)? Could it be possible that the CCO example is
wrong?

http://www.cisco.com/en/US/tech/tk331/tk336/technologies_tech_note09186a0080
093ecb.shtml

Regards,
Hunt Lee

-----Original Message-----
From: Janto Cin [mailto:jantocin@datacomm.co.id]
Sent: Tuesday, 31 December 2002 2:54 PM
To: Hunt Lee
Subject: RE: ISDN over DLSW

Passive keyword on Tanius local peer prevent Tanius to make a connection
but it allow Tat to make connection if its primary down (due to
backup-peer command on Tat).
Promiscious keyword on Tanius local peer allow any peer to make
connection to Tanius without to define remote-peer on Tanius (usually
use on peer on demand type of circuit such as border and group peers).
Just remember to always put 'passive' on backup peer.
Apoligize if I could not desribe it clearly.
Perhaps other in the mailing list can help further.

Kind Regards,
Janto

-----Original Message-----
From: Hunt Lee [mailto:huntl@webcentral.com.au]
Sent: Tuesday, December 31, 2002 11:31 AM
To: 'Janto Cin'
Subject: RE: ISDN over DLSW

I have just tried this, and "passive" keyword on Tanius works!!!

Can you please tell me why "passive" keyword works while "promiscious"
won't work???

Thanks in advance,

Best Regards,
Hunt Lee

-----Original Message-----
From: Janto Cin [mailto:jantocin@datacomm.co.id]
Sent: Tuesday, 31 December 2002 12:49 PM
To: Hunt Lee
Subject: RE: ISDN over DLSW

To prevent Tanius established DLSW connection to Tat use 'passive'
rather than 'promiscious'. Correct me if I'm wrong.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Hunt Lee
Sent: Tuesday, December 31, 2002 9:40 AM
To: 'Tony Schaffran'; ccielab@groupstudy.com; 'Joe Chang'
Subject: RE: ISDN over DLSW

Hello Tony + Joe & for those who is interested...

To make it more confusing, I realized that I don't even have any ISDN
connection, but the DLSW peers' status is "Connect" (the last ISDN
connection (4hours ago) was before I configured ISDN when I haven't
define DLSW as the only interesting traffic).

Tat#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts TCP
uptime
TCP 3.3.3.3 CONNECT 3 15 conf 0 0 0
04:25:50
TCP 2.2.2.2 DISCONN 0 0 conf 0 0 -
-
Total number of connected peers: 1
Total number of connections: 1

Tat#sh isdn active
------------------------------------------------------------------------

---- ---- ISDN ACTIVE CALLS ------------------------------------------------------------------------ ---- ---- Call Calling Called Remote Seconds Seconds Seconds Charges Type Number Number Name Used Left Idle Units/Currency ------------------------------------------------------------------------ ---- ---- ------------------------------------------------------------------------ ---- ----

N.B:- The "promiscuous" keyword is used at Tanius to prevent it from making a connection to Tat when the primary link is up.

Tat#

Here are the configs for the 3 routers:-

-RTA = Tat

Tat#sh run Building configuration...

Current configuration : 1632 bytes ! version 12.2 no service single-slot-reload-enable service timestamps debug datetime msec show-timezone service timestamps log datetime msec show-timezone no service password-encryption ! hostname Tat ! logging rate-limit console 10 except errors ! username Tanius password 0 cisco123 ip subnet-zero no ip finger ! no ip dhcp-client network-discovery isdn switch-type basic-net3 ! ! dlsw local-peer peer-id 1.1.1.1 keepalive 0 dlsw remote-peer 0 tcp 2.2.2.2 timeout 90 dlsw remote-peer 0 tcp 3.3.3.3 backup-peer 2.2.2.2 timeout 90 dlsw bridge-group 1 ! ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! interface Ethernet0 no ip address ip ospf message-digest-key 1 md5 cisco ip ospf hello-interval 30 bridge-group 1 ! interface Serial0 ip address 10.1.1.2 255.255.255.0 no fair-queue clockrate 64000 ! interface Serial1 ip address 10.64.3.162 255.255.255.240 no fair-queue ! interface BRI0 ip address 10.2.2.2 255.255.255.0 encapsulation ppp dialer map ip 10.2.2.1 name Tanius broadcast 2222 dialer-group 1 isdn switch-type basic-net3 cdapi buffers regular 0 cdapi buffers raw 0 cdapi buffers large 0 ppp authentication chap ! router eigrp 1 network 1.0.0.0 network 10.0.0.0 no auto-summary no eigrp log-neighbor-changes ! ip kerberos source-interface any ip classless ip route 3.3.3.3 255.255.255.255 10.2.2.1 150 ip http server ! access-list 101 deny eigrp any any access-list 101 permit tcp any eq 2065 any access-list 101 permit tcp any any eq 2065 dialer-list 1 protocol ip list 101 ! bridge 1 protocol ieee ! line con 0 transport input none line aux 0 line vty 0 4 login ! end

Tat#

============================

-RTB = Diplodocus

Diplodocus#sh run Building configuration...

Current configuration : 976 bytes ! version 12.2 service timestamps debug datetime msec show-timezone service timestamps log datetime msec show-timezone no service password-encryption ! hostname Diplodocus ! logging buffered 4096 debugging ! ip subnet-zero ! ! ! ip audit notify log ip audit po max-events 100 ! call rsvp-sync ! ! ! ! ! ! ! dlsw local-peer peer-id 2.2.2.2 dlsw remote-peer 0 tcp 1.1.1.1 dlsw bridge-group 1 ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 shutdown ! interface FastEthernet0/0 no ip address speed 10 half-duplex bridge-group 1 ! interface Serial0/0 no ip address ! interface Serial0/1 ip address 10.1.1.1 255.255.255.0 ! router eigrp 1 network 2.0.0.0 network 10.0.0.0 no auto-summary no eigrp log-neighbor-changes ! ip classless ip http server ! access-list 1 deny 10.1.70.0 0.0.0.255 access-list 1 permit any access-list 202 permit 0x0000 0x0D0D ! bridge 1 protocol ieee ! dial-peer cor custom ! ! ! ! ! line con 0 line aux 0 line vty 0 4 login ! end

Diplodocus#

===========================================

-RTC = Tanius

Tanius#sh run Building configuration...

Current configuration : 1257 bytes ! version 12.2 service timestamps debug datetime msec show-timezone service timestamps log datetime msec show-timezone no service password-encryption ! hostname Tanius ! ! username RTB password 0 isdn username Tat password 0 cisco123 ip subnet-zero ! isdn switch-type basic-net3 ! ! dlsw local-peer peer-id 3.3.3.3 keepalive 0 promiscuous dlsw remote-peer 0 tcp 1.1.1.1 timeout 90 dlsw bridge-group 1 ! interface Loopback0 ip address 3.3.3.3 255.255.255.255 ! interface Ethernet0 no ip address bridge-group 1 ! interface Serial0 no ip address ! interface Serial1 no ip address shutdown ! interface BRI0 ip address 10.2.2.1 255.255.255.0 encapsulation ppp dialer enable-timeout 2 dialer map ip 10.2.2.2 name Tat broadcast 1111 dialer-group 1 isdn switch-type basic-net3 ppp authentication chap ! router eigrp 1 network 3.0.0.0 network 10.0.0.0 no auto-summary ! ip classless ip route 1.1.1.1 255.255.255.255 10.2.2.2 150 ip http server ! ! map-class dialer ClassA dialer idle-timeout 60 dialer fast-idle 5 access-list 101 deny eigrp any any access-list 101 permit tcp any eq 2065 any access-list 101 permit tcp any any eq 2065 dialer-list 1 protocol ip list 101 ! bridge 1 protocol ieee ! line con 0 line aux 0 line vty 0 4 login ! end

Tanius#

-----Original Message----- From: Tony Schaffran [mailto:tschaffran@cconlinelabs.com] Sent: Tuesday, 31 December 2002 5:06 AM To: Hunt Lee; ccielab@groupstudy.com Subject: Re: ISDN over DLSW

To answer your second question, without seeing your entire configs, those two keywords should not have any affect on your isdn config. The keepalive 0 is just to keep the keepalives from keeping the isdn up if there is no traffic and the timeout 90 is just the amount of time required to bring up the isdn in the event of primary link failure.

Like you already stated, Solie has a pretty good description.

Tony Schaffran Network Analyst CCNP, CCNA, CCDA, NNCSS, NNCDS, CNE, MCSE

CCOnlineLabs.com http://www.cconlinelabs.com

----- Original Message ----- From: "Hunt Lee" <ciscoforme3@yahoo.com.au> To: <ccielab@groupstudy.com> Sent: Monday, December 30, 2002 7:38 AM Subject: ISDN over DLSW

> Hi Group, > > I am very very confused about DLSW over ISDN. I tried to simulate the

> CCO example > at:- > > http://www.cisco.com/en/US/customer/tech/tk331/tk336/technologies_tech_n ote0 9186a0080093ecb.shtml > > Firstly, by following the example exactly, I managed to get everything

> to work. > However, according to Solie (p923), & I have also read up lots of GroupStudy posts, > in order for ISDN to work with DLSW, one would need these keywords on > both ISDN > routers:- > > keeplive 0 on Local-peer statement > Timeout 90 on Remote-peer statement > > Yet on this CCO e.g., neither of these are used. Why???? > > Second Question, to make matter worse, after I have tried to put these

> two keywords > on the 2 ISDN routers, RTA don't even dial to RTC anymore... > > Any ideas would be greatly appreciated. > > On RTA - Tatiasaurus (Loopback int - 1.1.1.1 for simplicity) > > dlsw local-peer peer-id 1.1.1.1 keepalive 0 > dlsw remote-peer 0 tcp 2.2.2.2 timeout 90 > dlsw remote-peer 0 tcp 3.3.3.3 backup-peer 2.2.2.2 timeout 90 dlsw > bridge-group 1 > > > RTB - Diplodocus (Loopback int - 2.2.2.2) > > dlsw local-peer peer-id 2.2.2.2 > dlsw remote-peer 0 tcp 1.1.1.1 > dlsw bridge-group 1 > > RTC - Tanius (Loopback int - 3.3.3.3) > > dlsw local-peer peer-id 3.3.3.3 keepalive 0 promiscuous > dlsw remote-peer 0 tcp 1.1.1.1 timeout 90 > dlsw bridge-group 1 > > > Thanks. > > H. > > http://movies.yahoo.com.au - Yahoo! Movies > - What's on at your local cinema? > . . -----Original Message----- From: Tony Schaffran [mailto:tschaffran@cconlinelabs.com] Sent: Tuesday, 31 December 2002 5:06 AM To: Hunt Lee; ccielab@groupstudy.com Subject: Re: ISDN over DLSW