1 / 24

How To Build a Redundant, Fault Tolerant, Load Balanced, Traffic Managed Wireless network

KEEPING IT UP. How To Build a Redundant, Fault Tolerant, Load Balanced, Traffic Managed Wireless network. a bella mia company. A Little Background. Jeremy Kinsey “Known as Jer” to his friends. CEO and Co-Founder of Bella Mia, Inc. Been an ISP for 6 years Been a WISP for 2 + years.

sophie
Download Presentation

How To Build a Redundant, Fault Tolerant, Load Balanced, Traffic Managed Wireless network

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. KEEPING IT UP How To Build a Redundant, Fault Tolerant, Load Balanced, Traffic Managed Wireless network a bella mia company

  2. A Little Background • Jeremy Kinsey “Known as Jer” to his friends. • CEO and Co-Founder of Bella Mia, Inc. • Been an ISP for 6 years • Been a WISP for 2 + years

  3. So you are a Wireless ISPBut how do you make your system Redundant?

  4. Some Assumptions • You have at least 2 WPOPS (Wireless Points of Presence) • You already have a redundant network, ie., are running BGP, have two providers, etc. • You have a good understanding of Cisco Routers and various routing protocols.

  5. Assuming you have all that, lets take a look at how things break down.

  6. Lets Start at the WPOP • 3 180 degree Sectors • 3 runs of Heliax • 4 radios Proxim COR’s • Cisco 1600 Series Router • UPS • Switch

  7. Where do the pieces fit? • One Sector per side of tower • One Radio per sector • UPS, Radio, Switch, Router in enclosure at tower base. • Router connected to T1 and NOC

  8. The Big Picture Wireless PTP WPOP 2 WPOP 1 T1 T1 Internet Bandwidth Manager Router NOC

  9. So what do we have? Redundancy at the WPOP (3 separate radios & antennas) Redundancy in the entire system (multiple paths, traffic re-routed on the fly) Shared bandwidth (load balanced traffic, and bandwidth delivered where it is needed on demand)

  10. Another Key Point! Maintenance! _ Imagine Zero Down Time • Easily add to existing infrastructure • Upgrade Remote Devices • Replace Downed Gear

  11. But does it Work? Well Let’s See it in Action!

  12. Some Examples WPOP 1 Aggregate Traffic WPOP 2 Aggregate Traffic Traffic Flow over PTP between WPOP 1 & WPOP 2

  13. What does it look like when a pipe goes down? PTP under normal conditions PTP with 1 T1 Down • 1 Pipe goes down, traffic automatically re-routed over backup link • Pipe comes back up, PTP traffic will return to normal • Your users never know what happened

  14. Where do you go from here?

  15. Endless Expansion! Wireless PTP Wireless PTP WPOP 3 WPOP 1 WPOP 2 Wireless PTP T1 T1 Bandwidth Manager Wireless PTP to NOC Internet WPOP 4 Router NOC

  16. So How Do I Do It? • Now for the routing side of the “Keeping It Up”session • Josh Easton, CTO Bella Mia, Inc. • Routing protocols used and why

  17. OSPF • Open Shortest Path First • Allows for redundancy • Smarter routing of traffic

  18. Brief intro to OSPF • Every network link (T1, ethernet, etc.) has a cost • When multiple paths are available, lowest cost path is chosen • Costs can be manipulated to route your traffic ideally

  19. How does OSPF fit in? Cost = 10 Wireless PTP WPOP 2 WPOP 1 T1 T1 Cost = 64 Cost = 64 Internet Bandwidth Manager Router NOC

  20. Why these costs? • T1 has a default cost of 64 • 10Mbit ethernet’s default cost is 10 • Traffic from WPOP1 to WPOP2 will take the wireless PTP link if it’s available, else it will use T1s • Traffic from WPOP1 to Internet goes via the local T1, else via the wireless PTP link to WPOP2 and then via WPOP2’s T1

  21. Sample Cisco router config • Note: Need IP+ image to do OSPF on 1600 interface Ethernet0 ip address 10.0.0.1 255.255.255.0 ! Just an example ip address ip ospf message-digest key 1 md5 <Put OSPF password here> exit interface Serial0 ip address 10.0.1.1 255.255.255.0 ! Just an example ip address ip ospf message-digest key 1 md5 <Put OSPF password here> exit router ospf 100 redistribute connected subnets redistribute static subnets network 10.0.0.1 0.0.0.0 area 0 network 10.0.1.1 0.0.0.0 area 0 default-information originate always area 0 authentication message-digest ospf log-adjacency-changes exit

  22. OSPF in a larger network Cost = 45 Cost = 10 Wireless PTP Wireless PTP WPOP 3 WPOP 1 WPOP 2 Cost = 10 Cost = 64 Cost = 64 Wireless PTP T1 T1 Bandwidth Manager Wireless PTP to NOC Cost = 10 Internet WPOP 4 Router NOC

  23. Why these costs? • Cost from WPOP1 to WPOP3 is manually set at 45 • Traffic from one WPOP to another WPOP will use the wireless backbone by default • WPOP3 and WPOP4 use WPOP4’s link to the NOC to get on the Internet • WPOP1 and WPOP2 use their T1s to get on the Internet • If any link goes down, traffic will be routed around the damage

  24. Questions?

More Related