1 / 17

Redundant Routers

Redundant Routers. Jordan Curzon Charles Smutz. Purpose. Redundancy/Reliability Remove Single points of failure Manual Load Balancing Use both internet Links Other Services DNS DHCP Network Management. Redundancy through HA. Availability Monitoring Resource Management IP Takeover

stacia
Download Presentation

Redundant Routers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Redundant Routers Jordan Curzon Charles Smutz

  2. Purpose • Redundancy/Reliability • Remove Single points of failure • Manual Load Balancing • Use both internet Links • Other Services • DNS • DHCP • Network Management

  3. Redundancy through HA • Availability Monitoring • Resource Management • IP Takeover • Gratuitous ARP • http://www.ultramonkey.org/3/ip_address_takeover.html • Permanent/Service Addresses

  4. Normal Operation

  5. Router Failure

  6. Switch Redundancy • Distribution switches as single point of failure

  7. Multiple Switches

  8. LAN Isolation

  9. Redundancy using ST

  10. Other Redundancy Issues • Power • Cable Runs

  11. Routing with Iptables • Standard linux software router • Firewall with Iptables rules • NAT (MASQ) • Port Forwarding (DNAT) • Same Rule Set on each router • Separate chain for packets destined for each public address (P1, P2) • Same port can be use on each address • Shorter chains for better performance

  12. DNS • Master/Slave • Slave loads zones from Master via zone transfer • Resolve requests instead of forwarding to BYU servers

  13. DHCP • Failover • Primary and Secondary Server split pool • Same config file—both have static leases • Included sym link to primary/secondary config • Proprietary communication over arbitrary ports (519,520) • Compile from Source!

  14. Manual Load Balancing • Static leases point to R1, dynamic to R2 for primary default gateway

  15. Config Versioning/Syncing • Murcurial

  16. Network Management • Ping permanent Address • Optionally send Email with HA • Optionally use SNMP

  17. Live Demo • Off to 385

More Related