ā11-27-2014 07:41 AM - edited ā03-05-2019 12:15 AM
Hi All,
please excuse my ignorance but I need a some help as the guy who setup our 1841 router is no longer about,
we currently have our 1841 setup with 2 ADSL lines in a bond, we are moving over to FTTC which requires Ethernet so
my first question is what cards do I need to replace the ADSL HWIC cards with
and as FTTC still requires the router to Auth for a connection will I need to make any changes to the existing router config
many thanks in advance
Martin
Solved! Go to Solution.
ā11-27-2014 02:20 PM
The key bits are below. You have two ATM interfaces for your ADSL, configured for PPPoA.
interface ATM0/0/0 pvc 0/38 encapsulation aal5mux ppp dialer dialer pool-member 1 ! interface ATM0/1/0 pvc 0/38 encapsulation aal5mux ppp dialer dialer pool-member 1
Given that you're moving to Fast Ethernet, the termination will likely be PPPoE and so your configuration will look like this:
interface FastEthernet0/0/0 pppoe-client dial-pool-number 1 ! interface FastEthernet0/0/1 ! FastEthernet0/1/0 if you do two HWIC-1FE instead of one HWIC-2FE pppoe-client dial-pool-number 1
All of the IPv4 functionality is on your Dialer0 interface, so the above configuration will just re-home it onto the two new physical interfaces. As long as your ISP doesn't expect any other changes and everything is communicating on the native VLAN, that should do it.
ā11-27-2014 08:11 AM
If you're using two ADSL connections on one or more HWICs and connecting to your LAN, one of the two on-board Fast Ethernet interfaces on your 1841 should be unused. If this is the case, you should be able to get away without purchasing a new HWIC. If not, an HWIC-1FE will give you the additional interface that you need.
With the change in interface, you'll need to make a change in the router's configuration, though likely not a major one. The specific changes will depend on how your router is currently configured. If you're just using dialler pools and a dialler interface, you should be able to get away with adding the new Fast Ethernet interface to the pool... but there may be complexities depending on your provider. Here, for example, if we're not using the provider's equipment, we have to set up a Fast Ethernet sub-interface tagged with VLAN 35 and assign the dialler to that. Your provider may have its own idiosyncrasies.
Also, the 1841 router is only rated for a sustained throughput of ~40Mb/s. If your new service exceeds that by much, you may want to consider upgrading to something a bit more powerful.
ā11-27-2014 08:36 AM
Hi Jody
thanks for the quick response, I probably should have mentioned we are using the on board FE 0/0 and FE 0/1 interfaces for our LAN side, I believe (from memory) that we are using dialler pools
one feeds our data network and the other our VOIP,
if we change our incoming ADSL to FTTC it is Ethernet based connection as against a BT to RJ11 ASDL
so the 2 HWIC ADSL cards that are fitted will be made redundant
my understanding (as little as it is) I either need to replace with 2 x HWIC-1FE cards or 1 x HWIC-2FE card, so that bit is easy
as we are staying with the same ISP the logon details for the connection will remain the same to auth for the service its just basically knowing what the config changes that I need to make and confirmation of the correct HWIC cards
ā11-27-2014 08:40 AM
Are you getting two FTTC connections? If so, then two HWIC-1FE or one HWIC-2FE will work. If you're only getting one connection, then you'll only need one HWIC-1FE. Just remove the two ADSL HWICs and put in the new one(s) and you're good to go hardware-wise.
Assuming that there are no VLAN requirements for your ISP, you should just be able to add the dialler pool configuration to the new Fast Ethernet interfaces and go.
ā11-27-2014 08:44 AM
Yes the lines are currently in a bond so we are upgrading both :) this should give about 150Mb down and 35Mb upload
Ok so if I get a copy of the running config it should show the existing HWIC cards in the pool, will these need removing or do they just disappear when the cards are removed
then how easy is it to add the new HWIC card(s) to the pool
ā11-27-2014 08:50 AM
They should just disappear when the cards are removed.
Adding the HWICs to the pool should just be a matter of entering "pppoe-client dialer-pool #" on the new Fast Ethernet interfaces. If you can post your existing ATM interface configurations, I can probably be of a bit more assistance.
ā11-27-2014 10:05 AM
thanks I have just struggled to find the login details !!
so here it is
Moon-Router#en
Moon-Router#show running-conf
Building configuration...
Current configuration : 5667 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname Moon-Router
!
boot-start-marker
boot system flash flash:c1841-broadband-mz.124-12.bin
boot-end-marker
!
logging buffered 4096
enable secret 5 $1$pYsP$4aarfVuoA8r62RZ8XD31i0
!
no aaa new-model
ip cef
!
!
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.1 192.168.1.10
!
ip dhcp pool Moon
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 208.67.220.220
!
ip dhcp pool VOIP
import all
network 192.168.100.0 255.255.255.0
default-router 192.168.100.1
dns-server 208.67.220.220 208.67.222.222
option 150 ip 212.187.206.45
!
!
no ip domain lookup
ip domain name mooncomputers.local
multilink bundle-name authenticated
!
!
username admin privilege 15 password 7 08151F4D0148564253
username martin password 7 044B5F535A361C5C0D590912040E00447B7E
archive
log config
hidekeys
!
!
!
!
!
interface FastEthernet0/0
description VOIP-WAN
ip address 192.168.200.254 255.255.255.0
ip accounting output-packets
speed 100
full-duplex
no cdp enable
!
interface FastEthernet0/1
description Office-LAN
ip address 192.168.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly
speed 100
full-duplex
!
interface FastEthernet0/1.20
description DEV-LAN
encapsulation dot1Q 20
ip address 192.168.1.1 255.255.255.0
ip access-group dev2in in
ip accounting output-packets
ip nat inside
ip virtual-reassembly
!
interface FastEthernet0/1.200
description VOIP-LAN
encapsulation dot1Q 200
ip address 192.168.100.1 255.255.255.0
ip policy route-map VOIP-PATH
!
interface ATM0/0/0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface ATM0/1/0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface Dialer0
ip address negotiated
ip access-group out2in in
no ip proxy-arp
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer persistent
dialer-group 1
no cdp enable
ppp reliable-link
ppp authentication chap callin
ppp chap hostname newvoip-moon@ipadsl
ppp chap password 7 151F04030A3C242D38
ppp pap sent-username newvoip-moon@ipadsl password 7 045604090137434719
ppp multilink
ppp multilink endpoint hostname
!
ip route 0.0.0.0 0.0.0.0 Dialer0
!
!
ip http server
ip http access-class 23
ip http authentication local
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat inside source list 1 interface Dialer0 overload
ip nat inside source static tcp 192.168.1.50 5060 interface Dialer0 5060
ip nat inside source static tcp 192.168.1.4 443 interface Dialer0 443
ip nat inside source static tcp 192.168.1.4 80 interface Dialer0 80
ip nat inside source static udp 192.168.0.109 69 interface Dialer0 69
!
ip access-list extended dev2in
permit ip host 192.168.1.20 192.168.0.0 0.0.0.255
permit ip host 192.168.1.4 192.168.0.0 0.0.0.255
permit icmp any any echo-reply
permit ip host 192.168.1.33 any
remark Radiator test
permit ip host 192.168.1.34 any
permit ip host 192.168.1.35 any
deny ip 192.168.1.0 0.0.0.255 192.168.0.0 0.0.0.255 log
permit ip any any
ip access-list extended out2in
permit udp any eq ntp any
permit udp host 65.55.21.23 eq ntp any
permit tcp any any gt 1023 established
permit udp host 8.8.8.8 eq domain host 95.141.154.51
permit udp host 212.187.206.45 eq 5060 host 95.141.154.51
permit udp host 212.187.206.45 host 95.141.154.51
permit udp host 194.238.48.2 eq ntp any
permit tcp any host 95.141.154.51 eq 443
permit tcp any host 95.141.154.51 eq www
permit udp any eq 17771 any
permit udp host 208.67.222.222 eq domain host 95.141.154.51
permit gre any any
permit udp host 208.67.220.220 eq domain host 95.141.154.51
permit icmp any any
permit udp any eq isakmp host 95.141.154.51
permit udp any eq non500-isakmp host 95.141.154.51
permit udp any any eq tftp
permit ip host 95.141.153.81 any
deny ip any any log
!
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 1 permit 192.168.0.0 0.0.0.255
access-list 1 permit 10.6.32.0 0.0.3.255
access-list 1 permit 10.6.0.0 0.0.255.255
access-list 100 deny ip 192.168.100.0 0.0.0.255 192.168.0.0 0.0.0.255
access-list 100 permit ip 192.168.100.0 0.0.0.255 any
route-map VOIP-PATH permit 10
match ip address 100
set ip precedence critical
set ip next-hop 192.168.200.1
!
route-map VOIP-PATH permit 20
!
route-map VOIP-PATH permit 200
!
!
!
control-plane
!
banner motd ^CCCC
WARNING: You have accessed a network device operated by Mooncomputers. You are
required to have a personal authorisation from the network administrator before
you use this system and you are strictly limited to the use set out in that
authorisation. Unauthorised access to or misuse of this system is prohibited
and may constitute an offence under the Computer Misuse Act 1990.
If you disclose any information obtained through this system without authority,
Mooncomputers Ltd may take appropriate action against you. This may include lega
l
proceedings, prosecution and disciplinary action up to and including dismissal.^
C
!
line con 0
logging synchronous
login local
line aux 0
line vty 0 4
access-class 1 in
exec-timeout 0 0
privilege level 15
password 7 01075507535A555A
logging synchronous
login
transport input all
line vty 5 15
access-class 1 in
exec-timeout 0 0
password 7 001040050C0A5853
logging synchronous
login
transport input all
!
scheduler allocate 20000 1000
ntp clock-period 17178672
ntp server 194.238.48.2
end
ā11-27-2014 02:20 PM
The key bits are below. You have two ATM interfaces for your ADSL, configured for PPPoA.
interface ATM0/0/0 pvc 0/38 encapsulation aal5mux ppp dialer dialer pool-member 1 ! interface ATM0/1/0 pvc 0/38 encapsulation aal5mux ppp dialer dialer pool-member 1
Given that you're moving to Fast Ethernet, the termination will likely be PPPoE and so your configuration will look like this:
interface FastEthernet0/0/0 pppoe-client dial-pool-number 1 ! interface FastEthernet0/0/1 ! FastEthernet0/1/0 if you do two HWIC-1FE instead of one HWIC-2FE pppoe-client dial-pool-number 1
All of the IPv4 functionality is on your Dialer0 interface, so the above configuration will just re-home it onto the two new physical interfaces. As long as your ISP doesn't expect any other changes and everything is communicating on the native VLAN, that should do it.
ā11-28-2014 12:54 AM
Thanks Jody that's great,
just one last question then, we have a spare 1841 so if I copy the new config into a text document, what's the correct way to upload it to the spare router :)
ā11-28-2014 04:48 AM
Just copy the startup-config to a TFTP server and then copy the file from the TFTP server back to the startup-config of the spare router. This will keep an exact copy of the configuration on the backup so that it can be used as a hot spare.
Alternately, you can copy the startup-config to a USB flash drive via the 1841's USB port and copy it back to the backup's startup-config.
ā11-28-2014 08:58 AM
ok I thought I could do it through telnet as copy and paste and just had to run a command at the Prompt in config mode
Moon-Router(config)#
ā11-28-2014 09:02 AM
You can do that too, but it will add your new configuration to any existing configuration rather than replacing it.
ā11-28-2014 10:04 AM
the spare 1841 is clean its not got any hwic cards in at all, and has been factory reset :)
is there a guide to copying a config and saving it as a running config that I could read ? I feel that I have burdened you with so much already :)
ā11-28-2014 10:14 AM
A clean configuration makes things easier, but you still have to factor in the fact that interfaces are shut down on a clean configuration and you have to manually bring them back up when pasting in new configuration directives from the terminal. It's still an option, but involves extra steps.
Conveniently, Cisco has a document outlining the basics for configuration backup and restore here: http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-122-mainline/46741-backup-config.html
It's no burden at all.
ā12-03-2014 10:44 AM
Hi Jody
That worked a treat thanks, ive now got to get the update IOS as my router has got c1841-broadband-mz.124-15.T.bin on it and for the 2 port hwic card minimum needed is c1841-broadband-mz.124-20.T.bin
God I don't know how you guys cope with bloody Cisco lol
I also need to know how I award you credit for your assistance please
Thanks Martin
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide