Same dial-pool-number on different interfaces?! (Cisco 886 VDSL change modem)

[roesch4alc]

Hello all,

my questions is regarding the use of dialer groups. The setup, my question is about, spoke router (cisco 886)dials into the internet with a pppoe over a vdsl modem connected to port fa0 (working well in the moment). This is the connection I am using for connecting to one of the local computers (teamviewer). As you propably know, the router is also vdsl capable. So my questions is (because I´m not at the location and I would like to do this remotely) if I can also configure a same dial-pool-number (dial-pool-number 1 in my case) to different interfaces without conflicts? After that I would tell the local staff to switch the cabling from the external dsl modem to the cisco integrated one. After that I want the dialer0 to come up again without doing anything else. If the internal modem firmware is compatible to the provider dslam, would it work, as i described it?

The relevant commands for that

pppoe enable group global
pppoe-client dial-pool-number 1

I configuration language, this is what I want to do: While pppoe-client dial-pool-number 1 is configured for vlan 200, I would also like to configure it for the interface ethernet0 simultaneously, like this:

interface Ethernet0.7
description VDSL Internet - VLAN 7 tagged
encapsulation dot1Q 7
no ip route-cache
pppoe enable group global
pppoe-client dial-pool-number 1

interface Vlan200
no ip address
pppoe enable group global
pppoe-client dial-pool-number 1

The rest of the config would remain...

Relevant Part of the current config:

interface Ethernet0
no ip address
!
interface FastEthernet0
switchport access vlan 200
no ip address
!
interface FastEthernet1
no ip address
!
interface FastEthernet2
no ip address
!
interface FastEthernet3
no ip address

!
interface Vlan200
no ip address
pppoe enable group global
pppoe-client dial-pool-number 1
!
interface Dialer0
ip address negotiated
ip access-group 103 in
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip flow ingress
ip nat outside
ip inspect CiscoFW out
ip virtual-reassembly in
encapsulation ppp
ip tcp adjust-mss 1452
dialer pool 1
dialer-group 1
ppp authentication chap callin
ppp chap hostname donknow
ppp chap password donknow
ppp ipcp route default
no cdp enable
crypto map SDM_CMAP_1
crypto ipsec df-bit clear

Best Regards

Sebastian

[Philip D'Ath · Accepted solution]

Yes you can.  We often deploy routers like this so all the ports are configured up, and the site can plug in whatever protocol they have with no router changes.

[roesch4alc]

Hi,

thanks for your reply. I´m familiar with the reload command, but I didn´t want to do any changes, that won´t work for sure... But ok, I will try that and see, if it is working.

Best Regards

Sebastian

[roesch4alc]

Hi,

I´ve done this configuration, and yes, it works fine and as expected.

Thanks!

[Philip D'Ath]

When you are doing risky changes remotely you can do things like schedule the router to reboot in 10 minutes.

reload in 10

Make the risky change.  If it goes wrong, the router will reboot in 10 minutes undoing the change.  It the change works then cancel the reboot:

reload cancel