I want my four remote locations to be able to dial any one main office and after doing data transfer the line can be brought down. For example:
main office (A) main office (B)
remote site (C) , (d) ,(E) ,(F).
Router C, D, E, and F should be configured in such a way that any time they should be able to dial main office 'B' or 'a' and same main office 'A' or 'B' should be able to dial C,D,E,F. I don't want priority on dialer interface because router A will may have to dial router E and no other router. May be told to dial router C and not D,E,F. it's like any time any number should be dial and not specific dialing.
Following is the configuration. Where you want remote sites to dial any of the location give both dialing-in number otherwise give only one. Also change the hostnames, IP address etc.
On C, D, E or F - remote site ! hostname remote-C ! username central-A password cisco ! interface BRI0 <-- BRI interface used for DDR dialout ip address 172.20.10.2 255.255.255.0 <-- IP address. The remote address is in the same subnet. encapsulation ppp dialer idle-timeout 900 <-- The link will be disconnected if there is no interesting traffic for 900 secs. dialer map ip 172.20.10.1 name central-A broadcast 1111111 dialer map ip 172.20.10.1 name central-A broadcast 1111112 dialer load-threshold 80 outbound dialer-group 1 <-- apply interesting traffic definition from dialer-list 1 isdn switch-type basic-ni isdn spid1
isdn spid2 ppp authentication chap ppp multilink ! access-list 101 remark Define Interesting Traffic access-list 101 permit ip any any dialer-list 1 protocol ip list 101 <-- Interesting traffic is defined by access-list 101. This is applied to BRI0 using dialer-group 1.
On Central Site
! hostname central-A ! username remote-C password cisco ! interface BRI1/0 <-- BRI interface used to accept dialin ip address 172.20.10.1 255.255.255.0 <-- IP address. The remote address is in the same subnet. encapsulation ppp dialer idle-timeout 900 dialer map ip 172.20.10.2 name remote-C broadcast dialer-group 1 <-- apply interesting traffic definition from dialer-list 1 isdn switch-type basic-ni isdn spid1
isdn spid2 ppp authentication chap ppp multilink ! dialer-list 1 protocol ip permit !
Dig Deeper on Branch office network design
Related Q&A from Sudhanshu Gupta
One difference between managed and unmanaged switches is complexity. A managed switch is more complex and requires more skills, but it offers better ... Continue Reading
Unmanaged Linksys switches don't know where to send BootP and DHCP requests. Find out what to do to fix the problem of unmanaged switches and DHCP ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.