RE: [WISPA] Redundant Backhaul Links
If you're using all Cisco gear at your POPs EIGRP would be a better option since you can set bandwidth on the backhauls. Say for instance you may have your main backhaul with a capacity of 20MB and the backup at 10MB. EIGRP will make it's routing and load balancing decisions based on the line speed set for that interface. My 2 cents. Dylan From: [EMAIL PROTECTED] on behalf of Butch Evans Sent: Sat 12/31/2005 6:52 PM To: WISPA General List Subject: Re: [WISPA] Redundant Backhaul Links On Sat, 31 Dec 2005, Scott Reed wrote: In looking at that and some other things, I realize I really should plan for redundant links to the POPs from the NOC. I want to plan to have it so that if the primary link goes down, another like will take over. Probably looking at OSPF routing. That brings up the questions. Do I need to eventually have a link from every POP to all other POPs it can see, or do I just plan for one backup for each POP, or somewhere in between? Is there a better way than OSPF for doing this? OSPF is certainly the best bet for this scenario. With OSPF, you will have the self-healing you are looking for. You don't HAVE to have a redundant path to every pop, but doing so would obviously give you a more resiliant network. I sent you an email offlist as well. -- Butch Evans BPS Networks http://www.bpsnetworks.com/ Bernie, MO Mikrotik Certified Consultant (http://www.mikrotik.com/consultants.html) winmail.dat-- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
RE: [WISPA] Redundant Backhaul Links
Currently using all Mikrotik except for the border. That is a Cisco 2600. Scott Reed Owner NewWays Wireless Networking Network Design, Installation and Administration www.nwwnet.net The season is Christmas, not X-mas, not the holiday, but Christmas, because Christ was born to provide salvation to all who will believe! -- Original Message --- From: Dylan Bouterse [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Mon, 2 Jan 2006 11:44:28 -0500 Subject: RE: [WISPA] Redundant Backhaul Links If you're using all Cisco gear at your POPs EIGRP would be a better option since you can set bandwidth on the backhauls. Say for instance you may have your main backhaul with a capacity of 20MB and the backup at 10MB. EIGRP will make it's routing and load balancing decisions based on the line speed set for that interface. My 2 cents. Dylan From: [EMAIL PROTECTED] on behalf of Butch Evans Sent: Sat 12/31/2005 6:52 PM To: WISPA General List Subject: Re: [WISPA] Redundant Backhaul Links On Sat, 31 Dec 2005, Scott Reed wrote: In looking at that and some other things, I realize I really should plan for redundant links to the POPs from the NOC. I want to plan to have it so that if the primary link goes down, another like will take over. Probably looking at OSPF routing. That brings up the questions. Do I need to eventually have a link from every POP to all other POPs it can see, or do I just plan for one backup for each POP, or somewhere in between? Is there a better way than OSPF for doing this? OSPF is certainly the best bet for this scenario. With OSPF, you will have the self-healing you are looking for. You don't HAVE to have a redundant path to every pop, but doing so would obviously give you a more resiliant network. I sent you an email offlist as well. -- Butch Evans BPS Networks http://www.bpsnetworks.com/ Bernie, MO Mikrotik Certified Consultant (http://www.mikrotik.com/consultants.html) --- End of Original Message --- -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Redundant Backhaul Links
Yes, but do not put all your trust on OSPF alone, as its designed for full on / off failures. Redundancy often becomes a manual process in Wireless, and is really solved by good a monitoring system / policy. The reason is that most wireless links start to fail partially (packet loss), instead of full outs. As a result OSPF will not always detect properly when it becomes necessary to switch routes. One of the good features that Trango offers, is including ARQ now in all its radios. It lets us more easilly record packetloss from ARQ statistics. Tom DeReggi RapidDSL Wireless, Inc IntAirNet- Fixed Wireless Broadband - Original Message - From: Butch Evans [EMAIL PROTECTED] To: WISPA General List wireless@wispa.org Sent: Saturday, December 31, 2005 6:52 PM Subject: Re: [WISPA] Redundant Backhaul Links On Sat, 31 Dec 2005, Scott Reed wrote: In looking at that and some other things, I realize I really should plan for redundant links to the POPs from the NOC. I want to plan to have it so that if the primary link goes down, another like will take over. Probably looking at OSPF routing. That brings up the questions. Do I need to eventually have a link from every POP to all other POPs it can see, or do I just plan for one backup for each POP, or somewhere in between? Is there a better way than OSPF for doing this? OSPF is certainly the best bet for this scenario. With OSPF, you will have the self-healing you are looking for. You don't HAVE to have a redundant path to every pop, but doing so would obviously give you a more resiliant network. I sent you an email offlist as well. -- Butch Evans BPS Networks http://www.bpsnetworks.com/ Bernie, MO Mikrotik Certified Consultant (http://www.mikrotik.com/consultants.html) -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Redundant Backhaul Links
We have two connections to every ppop, so OSPF only trades data with its two peers. We limit and firewall which devices can talk OSPF to whom, to prevent hackers and customers from advertising false OSPF routes. Tom DeReggiRapidDSL Wireless, IncIntAirNet- Fixed Wireless Broadband - Original Message - From: Scott Reed To: WISPA General List Sent: Saturday, December 31, 2005 3:39 PM Subject: [WISPA] Redundant Backhaul Links I need to redesign my IP addressing before I get too many more customers. I messed up and have my APs, CPEs and customers all on the same subnets. I really want to get them separated. In looking at that and some other things, I realize I really should plan for redundant links to the POPs from the NOC. I want to plan to have it so that if the primary link goes down, another like will take over. Probably looking at OSPF routing. That brings up the questions. Do I need to eventually have a link from every POP to all other POPs it can see, or do I just plan for one backup for each POP, or somewhere in between? Is there a better way than OSPF for doing this? Scott Reed Owner NewWays Wireless Networking Network Design, Installation and Administration www.nwwnet.net The season is Christmas, not X-mas, not the holiday, but Christmas, because Christ was born to provide salvation to all who will believe! -- WISPA Wireless List: wireless@wispa.orgSubscribe/Unsubscribe:http://lists.wispa.org/mailman/listinfo/wirelessArchives: http://lists.wispa.org/pipermail/wireless/ -- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
