Bonding with Cisco IOS: Difference between revisions

← Older edit

Bonding with Cisco IOS (view source)

Revision as of 20:10, 26 February 2020

682 bytes added , 26 February 2020

m

→‎Configuring your Dialer interfaces: typo

CecilWard

252

edits

Revision as of 20:44, 1 June 2014 (view source) DominicBodger (talk \| contribs) No edit summary ← Older edit		Latest revision as of 20:10, 26 February 2020 (view source) CecilWard (talk \| contribs) m (→‎Configuring your Dialer interfaces: typo)
(19 intermediate revisions by 3 users not shown)
<indicator name="Front">[[File:Menu-bonding.svg\|link=:Category:Bonding\|30px\|Back up to the Bonding Page]]</indicator> [[Category:3rd Party Routers\|Cisco]] [[Category:Bonding Configuration\|Cisco]] After a few nights of meddling with my configuration, the following setup is working well for me. I would like to share it with the community. dialer pool 1 ppp chap hostname <yourAAISPuser>@a.1 ppp chap password 0 <~~yourPasword~~yourPassword> no cdp enable ! ip address <fromyourblock> <yoursubnet></nowiki> == Upstream load balancing using CEF == <nowiki>ip cef ! ip load-sharing per-packet !</nowiki> == Bringing it all together with NAT, bonding and upstream load balancing in a single router. == The following is a usable configuration. You will need to update interface names for your own equipment. A brief overview: * The use of a VRF allows two routing domains. One for internet traffic (~~AISP~~AAISP) where the [[bonding]] is undertaken, a global domain where internal hosts are connected. * Two Vlans are configured on my device, one for internal NAT clients, another for external internet facing clients. * This configuration should be extended to include the use of ip filter in the AAISP vrf to block any incoming DNS requests. Caveats: * Routing between global and a vrf in IOS is unpleasant. This configuration relies on a use of a physical [[Ethernet]] patch between GigabitEthernet0/0 and GigabitEthernet0/1 for routing traffic between the global and AAISP ~~donain~~domain. This should be unnecessary with the use of a BGP export between global and the vrf, but I never got this working. Similarly the use of NVI and BVI was investigated (please let me know if you have a more elegant solution!). <nowiki>version 15.1 service timestamps log datetime msec no service password-encryption service internal▼ ! hostname <yourhostname> boot-start-marker boot-end-marker !▼ ! no logging buffered dot11 syslog ip source-route !▼ ! ip cef ip dhcp excluded-address <excludeyourroutingaddresses> ! # DHCP for our internal network ip dhcp pool HOME network 192.168.1.0 255.255.255.0 lease 7 ! # DHCP for our external network ip dhcp pool AAISP network <~~yournetworkbase~~yourexternalnetworkbase> 255.255.255.248 domain-name home-external dns-server 217.169.20.20 ip name-server 217.169.20.20 ip name-server 217.169.20.21 ▲! ~~no [[IPv6\|ipv6]] cef~~ multilink bundle-name authenticated ! bridge irb ! # This is our ~~roting~~routing interface in the global domain, we NAT here interface GigabitEthernet0/0 description HOME-AAISP speed auto ! # This is our routing interface in the AAISP domain, you need a patch between GigabitEthernet0/0 and GigabitEthernet0/1 interface GigabitEthernet0/1 description AAISP-HOME ! ! # spanning-tree portfast gets rid of the annoying forwarding delay on PHY up interface FastEthernet1/0 no ip address ntp server 37.122.210.134 source GigabitEthernet0/0 end</nowiki> == Changing target DSL noise margin within IOS == A little known trick, be careful as this can affect your line stability. ▲ <nowiki>service internal ▲! int ATM0/0/0 # Replace <num> with the desired offset in db dsl-noisemargin -<num> !