Re: ppp multilink on 2500/3600

Discussion in 'Cisco' started by Klaus Kruse, Oct 23, 2003.

  1. Klaus Kruse

    Klaus Kruse Guest

    Hello Aaron,

    I tried to config the routers that way.
    The serial-IF was no problem, on the bri-IF I cannot config the dialer
    pool-member AND the dialer priority. One of them is ok, but both isn't
    possible by the IOS.
    There's also one question: the bri-IF must dial a phone-number to the other
    router, how can I config this number in a way, the ser0-IF didn't use it to
    connect to the other router (that's what I saw using my current config).

    Now I change the 11.0-Router into a 12.0-Router, I hope, my line got more
    stable now (since 2 weeks I use only bri-ppp-Multilink, but that's not what
    I want)

    Regards.

    Klaus

    Aaron Leonard hat geschrieben:

    > OK, this should work. I think. (On the 12.0 side; doubtful on the 11.0
    > side which I doubt supports dialer profiles.)
    >
    > interface serial
    > dialer dtr
    > dialer pool-member 1
    > dialer priority 10
    > ppp authentication chap
    > bandwidth 64
    >
    > interface bri0
    > dialer pool-member 1
    > dialer priority 5
    > ppp authentication chap
    > bandwidth 64
    >
    > interface dialer 1
    > dialer pool 1
    > dialer remote-name OTHERROUTER
    > dialer max-call 3
    > dialer rotor best
    > dialer-group 1
    > dialer load-threshold 40 ! experiment with this
    > dialer idle-timeout 60
    > ppp authentication chap
    >
    > Be sure to have CHAP (or PAP) authentication set up and working on all
    > links.
    >
    > By the way, you do NOT necessily have to (or want to) have PPP multilink
    > turned on for this to work. I think MLPPP was pretty new in 11.0 and I
    > don't know how solidly it worked there. If you don't do multilink, then
    > (I'm pretty sure) you'll get dialer per-packet load balancing.
    >
    > Aaron
    >
    > ---
    >
    > ~ I tried, it didn't work for interface beeing member of a rotary-group
    > (the ~ ser0-interface). Removing the interface from the rotary-group
    > enables the ~ command, but I can't get back the IF to the rotary-group.
    > ~
    > ~ On the dialer-Interface the command is not available.
    > ~
    > ~
    > ~
    > ~ Aaron Leonard hat geschrieben:
    > ~
    > ~ > Just make the leased line interface be "dialer dtr" -
    > ~ > this should get you going.
    > ~ >
    > ~ > Aaron
    > ~ >
    > ~ > ---
    > ~ >
    > ~ > ~ Oh my god, how can anyone understand this...
    > ~ > ~
    > ~ > ~ 1) there's NO 3600-Router in this game, sorry for that
    > ~ > ~ 2) the Cisco-Examples going only on something like that:
    > ~ > ~ two ser-Interfaces or two BRI-Interfaces or two async-Interfaces.
    > ~ > ~ I never saw, that they combine a serial-Interface AND
    > BRI-Interfaces,
    > ~ > ~ and that's my problem...
    > ~ > ~
    > ~ > ~ Klaus Kruse
    > ~ > ~
    > ~ > ~
    > ~ > ~ Klaus Kruse hat geschrieben:
    > ~ > ~
    > ~ > ~ > Hello all.
    > ~ > ~ >
    > ~ > ~ > After searching and reading tons of docu an examples my problems
    > still ~ > ~ > where. I send them here, maybe one of you can help me.
    > ~ > ~ >
    > ~ > ~ > I want to connect two 2503-Routers here with a 64kBit-leased-Line
    > on ~ > SER0 ~ > and additional 'bandwith-on-demand' on BRI0.
    > ~ > ~ > The IOS on one Side is 12.0(27), the other side is 11.0(21). Both
    > ~ > sides I ~ > configure to put the interfaces into a dialer
    > rotary-group. ~ > ~ > In the office I only can test the BRI-line because
    > there is no ~ > ~ > leased-line.
    > ~ > ~ >
    > ~ > ~ > Some more facts:
    > ~ > ~ > router1: WAN-side is 200.250.205.1, IOS 12.0(27)
    > ~ > ~ > router2: WAN-side is 200.250.205.2, IOS 11.0(21)
    > ~ > ~ >
    > ~ > ~ > So I put the routers together, activate some debug-switches:
    > ~ > ~ >
    > ~ > ~ > router1#debug interface serial 0
    > ~ > ~ > Condition 1 set
    > ~ > ~ > router1#term mon
    > ~ > ~ > router1#debug serial packet
    > ~ > ~ > Serial network packets debugging is on
    > ~ > ~ > router1#debug dialer events
    > ~ > ~ > Dial on demand events debugging is on
    > ~ > ~ >
    > ~ > ~ >
    > ~ > ~ > 2.) ping to router2
    > ~ > ~ >
    > ~ > ~ > saarbruecken2#ping 200.250.205.2
    > ~ > ~ >
    > ~ > ~ > Type escape sequence to abort.
    > ~ > ~ > Sending 5, 100-byte ICMP Echos to 200.250.205.2, timeout is 2
    > seconds: ~ > ~ >
    > ~ > ~ > 2d21h: Se0 DDR: rotor dialout [priority]
    > ~ > ~ > 2d21h: Se0 DDR: Dialing cause ip (s=200.250.205.1,
    > d=200.250.205.2) ~ > ~ > 2d21h: Se0 DDR: Attempting to dial 8966260.....
    > ~ > ~ > Success rate is 0 percent (0/5)
    > ~ > ~ >
    > ~ > ~ > Ups - the serial-IF tries to dial... The serial-IF is a leased
    > line ~ > that ~ > shouldn't have to dail - but how to tell the router.
    > ~ > ~ >
    > ~ > ~ > The time from starting the ping until the BRI-IF establish the
    > ~ > connection ~ > to router2 is about 30 seconds - and that's to long.
    > ~ > ~ > Now I'm searching how to tell the routers that they always use the
    > ~ > ~ > leased-line on ser0 for the basic-traffic an later, after the
    > reaching ~ > a ~ > threshold, add one or both of the BRI-B-channel.
    > ~ > ~ >
    > ~ > ~ > I found some configuration-examples on cisco, but they never
    > combine ~ > ~ > different IF's, they always use the same IF's or use
    > different IF's ~ > then ~ > they use ser0 as basic and bri0 as backup for
    > ser0. ~ > ~ >
    > ~ > ~ > I add the config of both routers and it would be very kind if
    > anyone ~ > can ~ > help me with those two boxes. It can't be that I'm the
    > first ~ > person who ~ > tried to do this.
    > ~ > ~ >
    > ~ > ~ > Thanks.
    > ~ > ~ >
    > ~ > ~ > -------------------------------------
    > ~ > ~ > ## Router1 ##
    > ~ > ~ > !
    > ~ > ~ > version 12.0
    > ~ > ~ > service timestamps debug uptime
    > ~ > ~ > service timestamps log uptime
    > ~ > ~ > service password-encryption
    > ~ > ~ > service udp-small-servers
    > ~ > ~ > service tcp-small-servers
    > ~ > ~ > !
    > ~ > ~ > hostname router1
    > ~ > ~ > !
    > ~ > ~ > enable secret 5 $1$Q.5r$LZlZPzvPMlZBC/UsOWWMl1
    > ~ > ~ > !
    > ~ > ~ > username router2 password 7 130E021E0202053822372B3B
    > ~ > ~ > ip subnet-zero
    > ~ > ~ > isdn switch-type basic-net3
    > ~ > ~ > !
    > ~ > ~ > !
    > ~ > ~ > !
    > ~ > ~ > interface Ethernet0
    > ~ > ~ > ip address 192.168.99.103 255.255.255.0
    > ~ > ~ > ip helper-address 192.168.99.5
    > ~ > ~ > no ip directed-broadcast
    > ~ > ~ > !
    > ~ > ~ > interface Serial0
    > ~ > ~ > no ip address
    > ~ > ~ > no ip directed-broadcast
    > ~ > ~ > encapsulation ppp
    > ~ > ~ > no ip mroute-cache
    > ~ > ~ > dialer in-band
    > ~ > ~ > no fair-queue
    > ~ > ~ > pulse-time 1
    > ~ > ~ > compress stac
    > ~ > ~ > ppp authentication chap
    > ~ > ~ > !
    > ~ > ~ > interface Serial1
    > ~ > ~ > no ip address
    > ~ > ~ > no ip directed-broadcast
    > ~ > ~ > shutdown
    > ~ > ~ > !
    > ~ > ~ > interface BRI0
    > ~ > ~ > no ip address
    > ~ > ~ > no ip directed-broadcast
    > ~ > ~ > encapsulation ppp
    > ~ > ~ > no ip route-cache
    > ~ > ~ > no ip mroute-cache
    > ~ > ~ > no keepalive
    > ~ > ~ > dialer rotary-group 1
    > ~ > ~ > isdn switch-type basic-net3
    > ~ > ~ > no fair-queue
    > ~ > ~ > !
    > ~ > ~ > interface Dialer1
    > ~ > ~ > ip address 200.250.205.1 255.255.255.0
    > ~ > ~ > no ip directed-broadcast
    > ~ > ~ > encapsulation ppp
    > ~ > ~ > dialer in-band
    > ~ > ~ > dialer idle-timeout 50
    > ~ > ~ > dialer map ip 200.250.205.2 name router2 broadcast <phone-number>
    > ~ > ~ > dialer load-threshold 50 either
    > ~ > ~ > dialer-group 1
    > ~ > ~ > no fair-queue
    > ~ > ~ > ppp authentication chap
    > ~ > ~ > ppp multilink
    > ~ > ~ > !
    > ~ > ~ > ip classless
    > ~ > ~ > ip route 0.0.0.0 0.0.0.0 192.168.99.20
    > ~ > ~ > !
    > ~ > ~ > access-list 101 permit ip any any
    > ~ > ~ > access-list 101 permit icmp any any
    > ~ > ~ > dialer-list 1 protocol ip list 101
    > ~ > ~ > !
    > ~ > ~ > line con 0
    > ~ > ~ > transport input none
    > ~ > ~ > line aux 0
    > ~ > ~ > transport input all
    > ~ > ~ > line vty 0 4
    > ~ > ~ > password 7 05080F1C73474A
    > ~ > ~ > login
    > ~ > ~ > !
    > ~ > ~ > end
    > ~ > ~ > ------------------------------------------------------
    > ~ > ~ > ## Router 2 ##
    > ~ > ~ > version 11.0
    > ~ > ~ > service password-encryption
    > ~ > ~ > service udp-small-servers
    > ~ > ~ > service tcp-small-servers
    > ~ > ~ > !
    > ~ > ~ > hostname router2
    > ~ > ~ > !
    > ~ > ~ > enable secret 5 $1$H9yz$V4odXqiQkMU6JhFo5ITnq1
    > ~ > ~ > enable password 7 045802155D2A48
    > ~ > ~ > !
    > ~ > ~ > username router1 password 7 0500130328424F1B1016141A
    > ~ > ~ > ip subnet-zero
    > ~ > ~ > no ip domain-lookup
    > ~ > ~ > isdn switch-type basic-net3
    > ~ > ~ > !
    > ~ > ~ > interface Loopback0
    > ~ > ~ > ip address 200.200.254.33 255.255.255.252
    > ~ > ~ > !
    > ~ > ~ > interface Ethernet0
    > ~ > ~ > description not used for tests
    > ~ > ~ > no ip address
    > ~ > ~ > shutdown
    > ~ > ~ > !
    > ~ > ~ > interface Serial0
    > ~ > ~ > no ip address
    > ~ > ~ > no ip mroute-cache
    > ~ > ~ > encapsulation ppp
    > ~ > ~ > dialer in-band
    > ~ > ~ > dialer idle-timeout 50
    > ~ > ~ > dialer rotary-group 1
    > ~ > ~ > no fair-queue
    > ~ > ~ > compress stac
    > ~ > ~ > pulse-time 1
    > ~ > ~ > !
    > ~ > ~ > interface Serial1
    > ~ > ~ > no ip address
    > ~ > ~ > shutdown
    > ~ > ~ > !
    > ~ > ~ > interface BRI0
    > ~ > ~ > no ip address
    > ~ > ~ > no ip directed-broadcast
    > ~ > ~ > no ip mroute-cache
    > ~ > ~ > encapsulation ppp
    > ~ > ~ > dialer idle-timeout 50
    > ~ > ~ > dialer rotary-group 1
    > ~ > ~ > dialer load-threshold 50 either
    > ~ > ~ > no fair-queue
    > ~ > ~ > !
    > ~ > ~ > interface Dialer1
    > ~ > ~ > ip address 200.250.205.2 255.255.255.0
    > ~ > ~ > encapsulation ppp
    > ~ > ~ > dialer in-band
    > ~ > ~ > dialer idle-timeout 50
    > ~ > ~ > dialer map ip 200.250.205.1 name router1 broadcast <phone-number>
    > ~ > ~ > dialer load-threshold 50 either
    > ~ > ~ > dialer-group 1
    > ~ > ~ > no fair-queue
    > ~ > ~ > ppp multilink
    > ~ > ~ > ppp authentication chap
    > ~ > ~ > !
    > ~ > ~ > ip classless
    > ~ > ~ > ip route 0.0.0.0 0.0.0.0 200.250.205.1
    > ~ > ~ > access-list 100 deny udp any any eq netbios-ns
    > ~ > ~ > access-list 100 permit ip any any
    > ~ > ~ > access-list 100 deny udp any any eq netbios-dgm
    > ~ > ~ > dialer-list 1 protocol ip list 101
    > ~ > ~ > !
    > ~ > ~ > line con 0
    > ~ > ~ > line aux 0
    > ~ > ~ > transport input all
    > ~ > ~ > line vty 0 4
    > ~ > ~ > password 7 0822455D5B1201
    > ~ > ~ > login
    > ~ > ~ > !
    > ~ > ~ > end
    > ~ > ~ >
    > ~ > ~ > ------------------------------
    > ~ > ~ > Klaus Kruse
    > ~ > ~ > Networkadmin
    > ~ > ~ > ZIT
    > ~ > ~ >
     
    Klaus Kruse, Oct 23, 2003
    #1
    1. Advertising

  2. ~ I tried to config the routers that way.
    ~ The serial-IF was no problem, on the bri-IF I cannot config the dialer
    ~ pool-member AND the dialer priority. One of them is ok, but both isn't
    ~ possible by the IOS.

    Sorry, that was my bad. For a dialer pool-member, you have to
    specify the priority on the dialer pool-member line:

    W2N-3.14-2524-B(config-if)#dialer pool 1 priority ?
    <0-255> Priority
    W2N-3.14-2524-B(config-if)#dialer pool 1 priority 5

    ~ There's also one question: the bri-IF must dial a phone-number to the other
    ~ router, how can I config this number in a way, the ser0-IF didn't use it to
    ~ connect to the other router (that's what I saw using my current config).


    I just now tried this in lab (on a box with unconnected interfaces,
    running 12.1), and it seemed like it worked OK (config below.)
    When I pinged 1.1.1.1, DDR first tried to raise DTR on Serial0, then
    when that failed to bring up the link, it tried BRI0.

    Aaron

    ---

    W2N-3.14-2524-B#show run int dialer1
    Building configuration...

    Current configuration : 147 bytes
    !
    interface Dialer1
    ip unnumbered Ethernet0
    encapsulation ppp
    dialer pool 1
    dialer remote-name foo
    dialer string 5551234
    dialer-group 1
    end

    W2N-3.14-2524-B#show run int serial0
    Building configuration...

    Current configuration : 159 bytes
    !
    interface Serial0
    no ip address
    encapsulation ppp
    no ip route-cache
    no ip mroute-cache
    dialer dtr
    dialer pool-member 1 priority 10
    no fair-queue
    end

    W2N-3.14-2524-B#show run int bri0
    Building configuration...

    Current configuration : 205 bytes
    !
    interface BRI0
    no ip address
    encapsulation ppp
    no ip route-cache
    no ip mroute-cache
    dialer pool-member 1 priority 5
    isdn switch-type basic-ni
    isdn spid1 919472490800
    isdn spid2 919472490901
    end

    W2N-3.14-2524-B#show run | i 1.1.1.1
    ip route 1.1.1.1 255.255.255.255 Dialer1 permanent

    ---


    ~ Now I change the 11.0-Router into a 12.0-Router, I hope, my line got more
    ~ stable now (since 2 weeks I use only bri-ppp-Multilink, but that's not what
    ~ I want)
    ~
    ~ Regards.
    ~
    ~ Klaus
    ~
    ~ Aaron Leonard hat geschrieben:
    ~
    ~ > OK, this should work. I think. (On the 12.0 side; doubtful on the 11.0
    ~ > side which I doubt supports dialer profiles.)
    ~ >
    ~ > interface serial
    ~ > dialer dtr
    ~ > dialer pool-member 1
    ~ > dialer priority 10
    ~ > ppp authentication chap
    ~ > bandwidth 64
    ~ >
    ~ > interface bri0
    ~ > dialer pool-member 1
    ~ > dialer priority 5
    ~ > ppp authentication chap
    ~ > bandwidth 64
    ~ >
    ~ > interface dialer 1
    ~ > dialer pool 1
    ~ > dialer remote-name OTHERROUTER
    ~ > dialer max-call 3
    ~ > dialer rotor best
    ~ > dialer-group 1
    ~ > dialer load-threshold 40 ! experiment with this
    ~ > dialer idle-timeout 60
    ~ > ppp authentication chap
    ~ >
    ~ > Be sure to have CHAP (or PAP) authentication set up and working on all
    ~ > links.
    ~ >
    ~ > By the way, you do NOT necessily have to (or want to) have PPP multilink
    ~ > turned on for this to work. I think MLPPP was pretty new in 11.0 and I
    ~ > don't know how solidly it worked there. If you don't do multilink, then
    ~ > (I'm pretty sure) you'll get dialer per-packet load balancing.
    ~ >
    ~ > Aaron
    ~ >
    ~ > ---
    ~ >
    ~ > ~ I tried, it didn't work for interface beeing member of a rotary-group
    ~ > (the ~ ser0-interface). Removing the interface from the rotary-group
    ~ > enables the ~ command, but I can't get back the IF to the rotary-group.
    ~ > ~
    ~ > ~ On the dialer-Interface the command is not available.
    ~ > ~
    ~ > ~
    ~ > ~
    ~ > ~ Aaron Leonard hat geschrieben:
    ~ > ~
    ~ > ~ > Just make the leased line interface be "dialer dtr" -
    ~ > ~ > this should get you going.
    ~ > ~ >
    ~ > ~ > Aaron
    ~ > ~ >
    ~ > ~ > ---
    ~ > ~ >
    ~ > ~ > ~ Oh my god, how can anyone understand this...
    ~ > ~ > ~
    ~ > ~ > ~ 1) there's NO 3600-Router in this game, sorry for that
    ~ > ~ > ~ 2) the Cisco-Examples going only on something like that:
    ~ > ~ > ~ two ser-Interfaces or two BRI-Interfaces or two async-Interfaces.
    ~ > ~ > ~ I never saw, that they combine a serial-Interface AND
    ~ > BRI-Interfaces,
    ~ > ~ > ~ and that's my problem...
    ~ > ~ > ~
    ~ > ~ > ~ Klaus Kruse
    ~ > ~ > ~
    ~ > ~ > ~
    ~ > ~ > ~ Klaus Kruse hat geschrieben:
    ~ > ~ > ~
    ~ > ~ > ~ > Hello all.
    ~ > ~ > ~ >
    ~ > ~ > ~ > After searching and reading tons of docu an examples my problems
    ~ > still ~ > ~ > where. I send them here, maybe one of you can help me.
    ~ > ~ > ~ >
    ~ > ~ > ~ > I want to connect two 2503-Routers here with a 64kBit-leased-Line
    ~ > on ~ > SER0 ~ > and additional 'bandwith-on-demand' on BRI0.
    ~ > ~ > ~ > The IOS on one Side is 12.0(27), the other side is 11.0(21). Both
    ~ > ~ > sides I ~ > configure to put the interfaces into a dialer
    ~ > rotary-group. ~ > ~ > In the office I only can test the BRI-line because
    ~ > there is no ~ > ~ > leased-line.
    ~ > ~ > ~ >
    ~ > ~ > ~ > Some more facts:
    ~ > ~ > ~ > router1: WAN-side is 200.250.205.1, IOS 12.0(27)
    ~ > ~ > ~ > router2: WAN-side is 200.250.205.2, IOS 11.0(21)
    ~ > ~ > ~ >
    ~ > ~ > ~ > So I put the routers together, activate some debug-switches:
    ~ > ~ > ~ >
    ~ > ~ > ~ > router1#debug interface serial 0
    ~ > ~ > ~ > Condition 1 set
    ~ > ~ > ~ > router1#term mon
    ~ > ~ > ~ > router1#debug serial packet
    ~ > ~ > ~ > Serial network packets debugging is on
    ~ > ~ > ~ > router1#debug dialer events
    ~ > ~ > ~ > Dial on demand events debugging is on
    ~ > ~ > ~ >
    ~ > ~ > ~ >
    ~ > ~ > ~ > 2.) ping to router2
    ~ > ~ > ~ >
    ~ > ~ > ~ > saarbruecken2#ping 200.250.205.2
    ~ > ~ > ~ >
    ~ > ~ > ~ > Type escape sequence to abort.
    ~ > ~ > ~ > Sending 5, 100-byte ICMP Echos to 200.250.205.2, timeout is 2
    ~ > seconds: ~ > ~ >
    ~ > ~ > ~ > 2d21h: Se0 DDR: rotor dialout [priority]
    ~ > ~ > ~ > 2d21h: Se0 DDR: Dialing cause ip (s=200.250.205.1,
    ~ > d=200.250.205.2) ~ > ~ > 2d21h: Se0 DDR: Attempting to dial 8966260.....
    ~ > ~ > ~ > Success rate is 0 percent (0/5)
    ~ > ~ > ~ >
    ~ > ~ > ~ > Ups - the serial-IF tries to dial... The serial-IF is a leased
    ~ > line ~ > that ~ > shouldn't have to dail - but how to tell the router.
    ~ > ~ > ~ >
    ~ > ~ > ~ > The time from starting the ping until the BRI-IF establish the
    ~ > ~ > connection ~ > to router2 is about 30 seconds - and that's to long.
    ~ > ~ > ~ > Now I'm searching how to tell the routers that they always use the
    ~ > ~ > ~ > leased-line on ser0 for the basic-traffic an later, after the
    ~ > reaching ~ > a ~ > threshold, add one or both of the BRI-B-channel.
    ~ > ~ > ~ >
    ~ > ~ > ~ > I found some configuration-examples on cisco, but they never
    ~ > combine ~ > ~ > different IF's, they always use the same IF's or use
    ~ > different IF's ~ > then ~ > they use ser0 as basic and bri0 as backup for
    ~ > ser0. ~ > ~ >
    ~ > ~ > ~ > I add the config of both routers and it would be very kind if
    ~ > anyone ~ > can ~ > help me with those two boxes. It can't be that I'm the
    ~ > first ~ > person who ~ > tried to do this.
    ~ > ~ > ~ >
    ~ > ~ > ~ > Thanks.
    ~ > ~ > ~ >
    ~ > ~ > ~ > -------------------------------------
    ~ > ~ > ~ > ## Router1 ##
    ~ > ~ > ~ > !
    ~ > ~ > ~ > version 12.0
    ~ > ~ > ~ > service timestamps debug uptime
    ~ > ~ > ~ > service timestamps log uptime
    ~ > ~ > ~ > service password-encryption
    ~ > ~ > ~ > service udp-small-servers
    ~ > ~ > ~ > service tcp-small-servers
    ~ > ~ > ~ > !
    ~ > ~ > ~ > hostname router1
    ~ > ~ > ~ > !
    ~ > ~ > ~ > enable secret 5 $1$Q.5r$LZlZPzvPMlZBC/UsOWWMl1
    ~ > ~ > ~ > !
    ~ > ~ > ~ > username router2 password 7 130E021E0202053822372B3B
    ~ > ~ > ~ > ip subnet-zero
    ~ > ~ > ~ > isdn switch-type basic-net3
    ~ > ~ > ~ > !
    ~ > ~ > ~ > !
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Ethernet0
    ~ > ~ > ~ > ip address 192.168.99.103 255.255.255.0
    ~ > ~ > ~ > ip helper-address 192.168.99.5
    ~ > ~ > ~ > no ip directed-broadcast
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Serial0
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > no ip directed-broadcast
    ~ > ~ > ~ > encapsulation ppp
    ~ > ~ > ~ > no ip mroute-cache
    ~ > ~ > ~ > dialer in-band
    ~ > ~ > ~ > no fair-queue
    ~ > ~ > ~ > pulse-time 1
    ~ > ~ > ~ > compress stac
    ~ > ~ > ~ > ppp authentication chap
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Serial1
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > no ip directed-broadcast
    ~ > ~ > ~ > shutdown
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface BRI0
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > no ip directed-broadcast
    ~ > ~ > ~ > encapsulation ppp
    ~ > ~ > ~ > no ip route-cache
    ~ > ~ > ~ > no ip mroute-cache
    ~ > ~ > ~ > no keepalive
    ~ > ~ > ~ > dialer rotary-group 1
    ~ > ~ > ~ > isdn switch-type basic-net3
    ~ > ~ > ~ > no fair-queue
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Dialer1
    ~ > ~ > ~ > ip address 200.250.205.1 255.255.255.0
    ~ > ~ > ~ > no ip directed-broadcast
    ~ > ~ > ~ > encapsulation ppp
    ~ > ~ > ~ > dialer in-band
    ~ > ~ > ~ > dialer idle-timeout 50
    ~ > ~ > ~ > dialer map ip 200.250.205.2 name router2 broadcast <phone-number>
    ~ > ~ > ~ > dialer load-threshold 50 either
    ~ > ~ > ~ > dialer-group 1
    ~ > ~ > ~ > no fair-queue
    ~ > ~ > ~ > ppp authentication chap
    ~ > ~ > ~ > ppp multilink
    ~ > ~ > ~ > !
    ~ > ~ > ~ > ip classless
    ~ > ~ > ~ > ip route 0.0.0.0 0.0.0.0 192.168.99.20
    ~ > ~ > ~ > !
    ~ > ~ > ~ > access-list 101 permit ip any any
    ~ > ~ > ~ > access-list 101 permit icmp any any
    ~ > ~ > ~ > dialer-list 1 protocol ip list 101
    ~ > ~ > ~ > !
    ~ > ~ > ~ > line con 0
    ~ > ~ > ~ > transport input none
    ~ > ~ > ~ > line aux 0
    ~ > ~ > ~ > transport input all
    ~ > ~ > ~ > line vty 0 4
    ~ > ~ > ~ > password 7 05080F1C73474A
    ~ > ~ > ~ > login
    ~ > ~ > ~ > !
    ~ > ~ > ~ > end
    ~ > ~ > ~ > ------------------------------------------------------
    ~ > ~ > ~ > ## Router 2 ##
    ~ > ~ > ~ > version 11.0
    ~ > ~ > ~ > service password-encryption
    ~ > ~ > ~ > service udp-small-servers
    ~ > ~ > ~ > service tcp-small-servers
    ~ > ~ > ~ > !
    ~ > ~ > ~ > hostname router2
    ~ > ~ > ~ > !
    ~ > ~ > ~ > enable secret 5 $1$H9yz$V4odXqiQkMU6JhFo5ITnq1
    ~ > ~ > ~ > enable password 7 045802155D2A48
    ~ > ~ > ~ > !
    ~ > ~ > ~ > username router1 password 7 0500130328424F1B1016141A
    ~ > ~ > ~ > ip subnet-zero
    ~ > ~ > ~ > no ip domain-lookup
    ~ > ~ > ~ > isdn switch-type basic-net3
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Loopback0
    ~ > ~ > ~ > ip address 200.200.254.33 255.255.255.252
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Ethernet0
    ~ > ~ > ~ > description not used for tests
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > shutdown
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Serial0
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > no ip mroute-cache
    ~ > ~ > ~ > encapsulation ppp
    ~ > ~ > ~ > dialer in-band
    ~ > ~ > ~ > dialer idle-timeout 50
    ~ > ~ > ~ > dialer rotary-group 1
    ~ > ~ > ~ > no fair-queue
    ~ > ~ > ~ > compress stac
    ~ > ~ > ~ > pulse-time 1
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Serial1
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > shutdown
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface BRI0
    ~ > ~ > ~ > no ip address
    ~ > ~ > ~ > no ip directed-broadcast
    ~ > ~ > ~ > no ip mroute-cache
    ~ > ~ > ~ > encapsulation ppp
    ~ > ~ > ~ > dialer idle-timeout 50
    ~ > ~ > ~ > dialer rotary-group 1
    ~ > ~ > ~ > dialer load-threshold 50 either
    ~ > ~ > ~ > no fair-queue
    ~ > ~ > ~ > !
    ~ > ~ > ~ > interface Dialer1
    ~ > ~ > ~ > ip address 200.250.205.2 255.255.255.0
    ~ > ~ > ~ > encapsulation ppp
    ~ > ~ > ~ > dialer in-band
    ~ > ~ > ~ > dialer idle-timeout 50
    ~ > ~ > ~ > dialer map ip 200.250.205.1 name router1 broadcast <phone-number>
    ~ > ~ > ~ > dialer load-threshold 50 either
    ~ > ~ > ~ > dialer-group 1
    ~ > ~ > ~ > no fair-queue
    ~ > ~ > ~ > ppp multilink
    ~ > ~ > ~ > ppp authentication chap
    ~ > ~ > ~ > !
    ~ > ~ > ~ > ip classless
    ~ > ~ > ~ > ip route 0.0.0.0 0.0.0.0 200.250.205.1
    ~ > ~ > ~ > access-list 100 deny udp any any eq netbios-ns
    ~ > ~ > ~ > access-list 100 permit ip any any
    ~ > ~ > ~ > access-list 100 deny udp any any eq netbios-dgm
    ~ > ~ > ~ > dialer-list 1 protocol ip list 101
    ~ > ~ > ~ > !
    ~ > ~ > ~ > line con 0
    ~ > ~ > ~ > line aux 0
    ~ > ~ > ~ > transport input all
    ~ > ~ > ~ > line vty 0 4
    ~ > ~ > ~ > password 7 0822455D5B1201
    ~ > ~ > ~ > login
    ~ > ~ > ~ > !
    ~ > ~ > ~ > end
    ~ > ~ > ~ >
    ~ > ~ > ~ > ------------------------------
    ~ > ~ > ~ > Klaus Kruse
    ~ > ~ > ~ > Networkadmin
    ~ > ~ > ~ > ZIT
    ~ > ~ > ~ >
     
    Aaron Leonard, Oct 27, 2003
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Gerd Thümmler

    ppp multilink lost many fragments

    Gerd Thümmler, Jul 11, 2003, in forum: Cisco
    Replies:
    0
    Views:
    2,938
    Gerd Thümmler
    Jul 11, 2003
  2. Gerd Thuemmler
    Replies:
    0
    Views:
    2,362
    Gerd Thuemmler
    Nov 27, 2003
  3. Karnov
    Replies:
    1
    Views:
    8,691
    CCIE8122
    May 24, 2004
  4. Phil J
    Replies:
    0
    Views:
    572
    Phil J
    Nov 1, 2004
  5. BillyJoe
    Replies:
    0
    Views:
    3,138
    BillyJoe
    Mar 5, 2004
Loading...

Share This Page