Browse
Search
2012-125 IT - MXN for Installing Wireless Network
OrangeCountyNC
>
Board of County Commissioners
>
Contracts and Agreements
>
General Contracts and Agreements
>
2010's
>
2012
>
2012-125 IT - MXN for Installing Wireless Network
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/24/2012 10:30:55 AM
Creation date
6/4/2012 4:21:36 PM
Metadata
Fields
Template:
BOCC
Date
6/4/2012
Meeting Type
Work Session
Document Type
Agreement
Agenda Item
Mgr Signed
Document Relationships
2012-125 S Contract IT - MXN Corporation install wireless network $41,558.23
(Linked From)
Path:
\Board of County Commissioners\Contracts and Agreements\Contract Routing Sheets\Routing Sheets\2012
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
• Create a open Guest /Public SSID that will be encrypted and tunneled back to the <br />controller with no access to any internal resources <br />• Rate limit the Guest network to desired level for inbound and outbound traffic <br />• Create a Guest account locally on the controller or install Guest account management <br />software on a separate customer supplied computer if purchased <br />• Back up the controller configuration <br />• Perform hands on operational training on the installed product for up to three people <br />The following are our standard project assumptions for the installation of a Hewlett - <br />Packard wireless network: <br />Wireless project assumptions: <br />• All work will be performed during normal business hours <br />• The customer is knowledgeable about their network and is readily able to answer <br />questions that relate to routing, DNS, firewall and DHCP services. <br />• The customer will have a technical person available to answer any questions that we <br />might have during the installation <br />• All or at least a subset of access points will be mounted and powered up prior to an <br />MXN engineer arriving on -site <br />• If using layer 3 discovery for the access points (across VLAN's) that a DNS A record be <br />created in DNS and /or DHCP option 43 be created in the scopes that the access points <br />are in <br />• All serial numbers from the mounted access points have been recorded and a location <br />associated with it <br />• DHCP is enabled on any VLAN's that we will drop a wireless client in <br />We add a few additional assumptions for this installation: <br />• You will have a local wiring contractor install the fifty MSM430 wireless access points in <br />locations that we indicate, and they will use at least Category 5e cabling to connect <br />those access points back to the POE switches in each location <br />• You or your contractor will also provide all necessary copper and fiber jumpers <br />• You have sufficient POE ports on your Hewlett- Packard switches to power these access <br />points <br />• You don't have RADIUS set up and working, and we don't want to impose the <br />management of another system on you <br />Let's chat about this last item. We can keep security simple, or make it more <br />complicated. Our natural inclination if for the former, and this project assumes it. You <br />want guest wireless and guest wired access. The simplest way to achieve this is to <br />publish a guest wireless SSID that needs no login and has no key, and that gets funneled <br />3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.