I am trying to design Video Surveillance Solutions for foot ball field. Here, we can not pull cable from cameras to MDF the building in Campus Environment. I am trying to incorporate Cisco bridges (Point to Multipoint Environment) in order carry data from cameras to MDF. I have attached diagram for your reference. For this solution I would like to have your advice as I am planning to deploy these bridges for the first time. I have some questions for you.
1.) I am planning to use Cisco 1410 bridges instead of 1310 bridges. Do you think Cisco 1310 series would be sufficient for my application? Please advice me on antenna selections on root and non-root bridges in case of 140 and also 1310. I would like to use external antenna specially omni for root bridge and sectoral antennas for non-root. Please advice me for the best selection.
2.) As Cisco bridging solution does not have LWAPP option. I was thinking of using WLSE for managing those bridges but I came to know that is on its EOL. Do we have any other option?
-Do we have to have separate appliance for WLSE? Can you advice me how should I order that? Please let me know how much bridges will be supported by WLSE (1 license)?
3.)I am thinking of using external antenna. I would like to use omnidirectional antenna for root bridge and sectoral antennas for non-root bridges. Please advice which antenna I should be using in case of 1410 and 1310 series.
The main differences between the 1400 series and 1300 series bridges is the fact that the 1400 uses external antennas, and the 1300s do not. Also, we need to know what radio frequencies you have available as the 1300 is 2.4 GHz (802.11g only) and the 1400 is 5 GHz (UNII 3 band). How far apart are your bridges going to be? This will determine what power and antenna types. Finally, the 1300 series bridge does have an LWAPP image allowing you to manage it via a controller, you lose the ability for it to bridge and it becomes an AP. Unless you go to the 1500 series for LWAPP/CAPWAP outdoor meshing deployment, you're going have to manage your bridges independently via the CLI or HTTP. There is no point in digging up an old WLSE off of ebay to manage those - it would be a waste of time and money IMHO.
Thank you so much for your advise. My application will be using 1310 or 1410 as a bridge(One root and 2 non-root). So I am not concern about LWAPP. But as far as I know we have 1310 series available with outdoor antenna.
The distance between bridges will be around 200-300 meters and will carry 10mbps worth of data. What will be the best solution 1410 or 1310? Can I manage those bridges from HTTP? Like doing periodic updates or firmware upgrade and other necessary task? Which antenna selection would be better in case of 1310 or 1410 for root and non-root bridges? Which bridges you suggest for campus environment?
I may be asking so much but I am going to use this product for the very first time.
I realize you are saying that you only have 10 mbps of data, but you have to remember that you are using point-to-multipoint so you would need to consider the cumulative throughput of the two non-root bridges back to the root bridge. Also, the 1310 is 802.11g only - do you have a clean airspace outdoors to use 2.4 GHz? You need to do some testing with your choice of antennas and distances. This is not something you can just input some specs, order from a catalog and install. There needs to be some onsite verification using the equipment you have and to measure your throughput. If I were chartered with doing something like this, I would perfer to use the 5 GHz spectrum due to the fact that it is a cleaner airspace and would perform better in a point-to-multipoint scenario. But I still would use some tools (laptop with Ekahau or Airmagnet, Spectrum Analyzer, etc.) to find out what frequencies are nearby. Since the 2.4 GHz and 5 GHz frequencies are unlicensed, not only do you want to use the one that will work best for your given environment, but also one that will be kind to others around you. As for the manageablility of the bridges, yes, you can access them via CLI and HTTP for the purposes of performing firmware updates. As far as antenna design goes, I'd use a patch of some sort for the root bridge, and a directional high gain for the non-root.
Thank you so much for giving me wider vision. I will really consider your points. I would like to go for 1400 series but only thing is bothering me is the cost which is almost 4times than 1310 if I am not mistaken. Is it just because of it is using 802.11a standard? I was thinking about using omni directional for root and sectoral for non-roots. What do you recommend?
I can understand your concern for the cost of the 1400 series, but the 1400 series is built for point-to-point links for up to 25 MILES!! Obviously less in cases of point-to-multipoint. The 1310 bridge can go a couple of miles as well, but the data rate is going to suffer at 2.4 GHz 'g' only. That's why I said to do some testing to verify you can get the data rates you need to support your application. The only time you actually want to use omni directional antennas with bridging are if you are creating a mesh or a repeater. For PtP to PtM, you would reduce your link budget, distance, and overall throughput by using omni directional antennas. The fact that we use the term 'point-to-point' tells you that you only want your signal to go from the root to the non-root and not elsewhere. Since we can't really contain wireless signals once they're in the air, it's up to engineers to design antennas for us that essentially cheat physics and shape the antenna pattern so that it is directional. Higher gain directional antennas will have a high 'front-to-back' ratio (F/B ratio) telling you that a certain percentage is going in front of the antenna, and a certain amount is going out the back. When the amount going out the front exceeds the amount going out the back, you begin to have a directional antenna. In addition, at larger distances, if you don't use directional antennas, it will be very difficult to align them and keep a stable connection due to the fade margin of the omni directional antennas. The bridges have a built in alignment mode with lights to help you achieve maximum throughput. When you align them, make very calculated, small changes. Don't move both sides, and don't move in both planes (horizontal, vertical). Keep your antennas pointed at one another using some binoculars or other pointing devices and get the best reading you can at the root after an initial setup. Then lock the root into place and go to the other side. Again, make calculated changes to vertical until you find the best, and then lock it down. Finish with sweeping horizontal until you get the best and lock it down. It may take you several iterations until you get it right. As for the non-root antennas, you don't want to mix antennas too much if you can avoid it, but in the case of point-to-multipoint, you've got it backwards. You want a larger angle on the root bridge, and high gain directional on the non-roots pointing back to the root. It is imperative that you know what the polarization is of each antenna (vertical vs. horizontal) and that you MATCH that polarization at both ends. Most antennas have this clearly labeled on the antenna itself, or it is specified in the user manual.
Thank you so much for detailed explanation. With my application I am not much worried about distance because the maximum distance will be 300-400 meters between two bridges no more than that. I am much concern about throughput but in both the cases maximum throughput I can achieve is 54 mbps. Of course the distance will be reduced in case of 1310 but as I said distance is not an issue because in both case I can achieve the distance with maximum data rate. What do you suggest?
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...