understand wireless Network setup.

understand wireless Network setup.

I would like to understand in the Nutshell  how comapnies setup Wirless network

I believe you Need a wireless controller, Wireless Controller will be connected to you existng Wired LAN switches, if you plan to give access from Wireless Network to Wired and vice-versa.

Then comes the Access Point part, I believe you need to  configure Access points to connect wirelessly to the Wireless Controller.

If I am missing any step, please correct me.

Tahnk you
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

There's many way of deploying with or without wireless controllers. Ideally, if you have many access points you would want controllers as a central point of management. Access points at some point would need to connect to wired lan switches and yes, wireless lan controllers connect to switches.
In order to answer this, we will need to know a little more about your requirements:

In order to determine what will best meet your needs, we will need to know the following:

Size of the Company (number of Stories per location) , Number of Locations (one or more than one), Composite of the buildings, etc..

This would be a good place to start:

Reference : http://www.wireless-nets.com/resources/tutorials/define_network_requirements.html

Requirements to consider
Before implementing a wireless network, consider the following types of requirements:

Applications. Ultimately, the wireless network must support user applications, so be sure to fully define them in the requirements. This could be general office applications, such as web browsing, email, and file transfer, or it could be wireless patient monitoring in a hospital or voice telephony in a warehouse. Be as specific as possible. The application requirements enable designers to specify applicable throughput, technologies and products when designing the system.

Environment. Provide a description of the environment where the wireless network will operate. For buildings, include the floor plan, type construction, and possible locations for mounting access points. For outdoor areas, include satellite images, aerial photographs, or drawings. Walk through the areas to verify accuracy of these items. Take lots of photos. In addition to a visible inspection, consider performing a RF site survey. All of this will capture the environment in a way that will help designers choose the right technical elements.

Coverage areas. This describes where users will need access to the wireless network. They might only need connectivity in their offices and conferences rooms, but they may also need connectivity inside power utility rooms and the cafeteria. Also, carefully think about whether coverage is needed in stairwells, elevators, and parking garages. These are difficult-to-cover areas and can drive the cost of the wireless network very high. By properly specifying coverage area, you’ll avoid the unnecessary expense of installing access points where they’re not needed. Unless obvious, also identify the country where the wireless network will operate. This impacts channel planning and product availability.

End users. Be sure to identify whether users are mobile or stationary, which provides a basis for including enhanced roaming in the design. Mobile users will move about the facility and possible roam across IP domains, creating a need to manage IP addresses dynamically. Some users, however, may be stationary, such as wireless desktops.

Client devices. You should specify the client devices (and existing client radios) to ensure the solution accommodates them in the most effective manner. For example, you could specify that users will have laptops running Microsoft Vista operating system with integrated 802.11b/g radios. This provides a basis for deciding on the type of client radios to specify for other client devices during the design and whether there’s a need to support legacy devices (i.e., 802.11b/g).

Existing infrastructure. Be certain to describe all existing applicable infrastructure. Identify locations and availability of communications closets, switch types and available ports, PoE interfaces, fiber runs, conduit, authentication servers, VPN ports, and operational support systems.

Security. Describe the sensitivity of the information that will traverse the wireless network. If possible, cite existing corporate wireless security policies. You’ll likely need to require encryption and authentication of all client devices. Be sure to give security requirements plenty of thought so that you design a solution that will protect the company’s valuable resources.

Funding. The requirements stage of a wireless network project is a good time to ask how much money is available. If funding limits are known, then you’ll know how much there is to work with when designing the system. In most cases, however, a company will ask how much the system will cost. You’ll then need to define the requirements and design the system before giving a cost estimate. In this situation, consider stating requirements with options, such as with and without signal coverage provided in parking garages. You can then provide two separate cost estimates based on optional signal coverage.

Schedules. Of course a company will generally want the wireless network installed “yesterday,” but we all know that’s impossible. You’ll need to nail down a realistic completion date, though, and plan accordingly. For example, you may be defining requirements in July, and a retail store will likely demand that a wireless price marking application be installed by the end of September.
After defining these elements, you should have enough information to design the solution. Before proceeding, though, ensure you have consensus from all stakeholders, such as executives, users, and the operational support organization. If requirements are not clear enough, you should do some prototyping or pilot testing to fully understand requirements before spending money on the design and installation.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jskfanAuthor Commented:
Just one floor , pretty big floor though, which means we might need to use several access points
CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Depends on a lot of things. ITguy's answer touched into a lot of it.

But regardless, you should always do a wireless survey. Understand where your interference and weak spots are, and plan appropriately.

  • Figure out how many wireless networks you need. A lot of places run 2, one for corporate, one for guests. Only cover areas that need to be covered (i.e. if you had a warehouse wireless network, does it make sense to be broadcasting it outside of the warehouse?
  • Security requirements. You may want a captive portal and force users to sign in via AD authentication. Another option could be that you want certificate based authentication. Some of these answers depend on the knowledge of the IT organization.
  • Compatibility/integration. You may have a requirement that your APs can integrate with certain other pieces of infrastructure.
  • Budget/support - How much are you willing to spend, and how much support are you looking for from the vendor?

The way a lot of organizations have been going is the deployment of controllers for management of the APs being deployed (this allows for quicker updates and deployments). Many times, the controllers are hardware devices, but they don't have to be. Ubiquiti is one maker where the controller is actually software.
fred hakimRetired ITCommented:
Way too many possibilities  exist on how to set up a company network.  It goes well beyond just wireless surveys, user counts, and apps.  

Give us some basics and we can point you in the right direction.  

1. How many geographic locations?

2. How many users at those locations?  

3. How many servers?

4.  Will servers/data be shared across geographic locations?  

5. Will users have Internet access?  

6. Will any servers need Internet access?  

7.  Any public (web / FTP / etc) servers?  

8 What is the mix of local users connecting via Ethernet, WiFi?  

9. Do you have remote users or customers?  

10 Do remote folks need to access internal or external servers (or both)

11. What sort of SLA is expected (service / up time)  

12.  Do you need to meet any government specs (ie: HIPPA)
jskfanAuthor Commented:
Thank you
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Networking

From novice to tech pro — start learning today.