From: Chad Marsh (chad@xxxxxx)
Date: Thu May 18 2000 - 12:31:32 GMT-3
Hey Joe, I don't know if you can do backup and snapshot on the same ISDN
interface, however, you CAN do snapshot with a dialer profile, using rotory
groups.
Here is a thread from the groupstudy archives when I was playing with this
stuff:
----------------------------------------------------------------------------
----Subject: Re: More Dialer stuff From: Chad Marsh <chad@xxxxxx> Date: Wed, 29 Sep 1999 01:28:25 -0700 References: <37F1A20A.7F835B11@wa.net> <37F1AA14.69406B81@cisco.com> <37F1BCAE.FA992883@wa.net>
---------------------------------------------------------------------------- ----
Correction, after further study, it appears the mutually exclusive commands on the dialer interface are 'dialer remote-name' and 'dialer map'. If you set a remote name, you can no longer use 'dialer map'(which is required for snapshot), you can only set a dialer string. But, if you do specify a 'dialer remote-name' first, you cannot enter 'dialer in-band', you get that error '%Remove the dialer profile first' You can enter 'dialer in-band', then enter 'dialer remote-name', but at that point you can't enter dialer maps, so I guess that doesn't do any good anyway.
So what exactly does 'dialer in-band' do anyway? CCO says: dialer in-band To specify that dial-on-demand routing (DDR) is to be supported, use the dialer in-band interface configuration command. To disable DDR for the interface, use the no form of this command.
But that doesn't make any sense, I can setup DDR with dialer profiles using dialer pools, and without using 'dialer in-band' and it works just fine.
Chad Marsh
> > It appears that the 'dialer in-band' and 'dialer remote-name' commands > are mutually exclusive on the Dialer interface. > I have this working with rotary-groups, not sure if it would work with > dialer pools, maybe I'll try that next. > But the bottom line is that it DOES work. > I just got it working, here are some relevant outputs and portions of > the configs: > > Chad Marsh > > R5#sho snap > Dialer1 is up, line protocol is upSnapshot client > Options: dialer support > Length of active period: 5 minutes > Length of quiet period: 8 minutes > Length of retry period: 8 minutes > For dialer address 1 > Current state: active, remaining/exchange time: 4/2 minutes > Connected dialer interface: > BRI0:1 > Updates received this cycle: ip > > R6#sho snap > Dialer1 is up, line protocol is upSnapshot server > Options: dialer support > Length of active period: 5 minutes > For ip address: 172.16.1.5 > Current state: active, remaining time: 3 minutes > Connected dialer interface: > BRI0:1 > > R5#sh ru > Building configuration... > > Current configuration: > ! > hostname R5 > ! > ! > username R6 password 0 ccie > isdn switch-type basic-dms100 > ! > interface Loopback0 > ip address 10.5.1.1 255.255.255.0 > ! > interface BRI0 > no ip address > encapsulation ppp > isdn spid1 20649906240101 4990624 > isdn spid2 20649906250101 4990625 > dialer rotary-group 1 > no cdp enable > ! > interface Dialer1 > ip address 172.16.1.5 255.255.255.0 > encapsulation ppp > dialer in-band > dialer in-band > dialer map snapshot 1 4990622 > dialer map ip 172.16.1.6 name R6 broadcast 4990622 > dialer-group 1 > snapshot client 5 8 dialer > no cdp enable > ppp authentication chap > ! > router rip > network 10.0.0.0 > network 172.16.0.0 > ! > ip classless > ! > dialer-list 1 protocol ip permit > ! > R5# > > R6#sho run > Building configuration... > > Current configuration: > ! > hostname R6 > ! > ! > username R5 password 0 ccie > isdn switch-type basic-dms100 > ! > interface Loopback0 > ip address 20.6.1.1 255.255.255.0 > ! > interface BRI0 > no ip address > encapsulation ppp > isdn spid1 20649906220101 4990622 > isdn spid2 20649906230101 4990623 > dialer rotary-group 1 > no cdp enable > ! > interface Dialer1 > ip address 172.16.1.6 255.255.255.0 > encapsulation ppp > dialer in-band > dialer idle-timeout 30 > dialer map ip 172.16.1.5 name R5 broadcast 4990624 > dialer-group 1 > snapshot server 5 dialer > no cdp enable > ppp authentication chap > ! > router rip > network 10.0.0.0 > network 172.16.0.0 > ! > ip classless > ! > dialer-list 1 protocol ip permit > ! > R6#
----- Original Message ----- From: "Joe Martin" <jmartin@gte.net> To: "Earl Aboytes" <earl@linkline.com>; "JZ" <jzhang0427a@yahoo.com>; <ccielab@groupstudy.com> Sent: Tuesday, May 16, 2000 11:28 PM Subject: Re: ISDN: Snapshot + Backup w/ profiles ?
> I've spoke with several people, plus I played with this a bit. You can't do > snapshot on a dialer profile interface, only DDR. So, you can't do both > backup and snapshot with the same ISDN line. > > Please let me know if I'm in error. > > JOE > ----- Original Message ----- > From: "Earl Aboytes" <earl@linkline.com> > To: "JZ" <jzhang0427a@yahoo.com>; <ccielab@groupstudy.com> > Sent: Tuesday, May 16, 2000 9:57 AM > Subject: RE: ISDN: Snapshot + Backup w/ profiles ? > > > > What did you find out? It seems, to me, that this should be possible. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Earl Aboytes > > Senior Technical Conultant > > GTE Managed Solutions > > 805-381-8817 > > earl.aboytes@telops.gte.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > -----Original Message----- > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of JZ > > Sent: Thursday, May 11, 2000 7:25 PM > > To: ccielab@groupstudy.com > > Subject: ISDN: Snapshot + Backup w/ profiles ? > > > > Hi, > > I'm working on the lab focus on ISDN / DDR topic. > > > > The issue I have is that is it possible to set up a > > single ISDN DDR line for both snapshot and backup by > > using profile(s) - the next generation DDR ? > > > > Case: two c2500 routers with one ISDN interface and > > Serial link for each router. ROuting protocol: RIP or > > any distance vector routing protocol. > > > > Prove it or disprove it. > > > > My guess is " No " > > > > Any suggestion can be forward to: > > > > jzhang0427a@yahoo.com > > > > Thanks, > > > > Jim > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:30 GMT-3