CABLING REQUIREMENTS:

Transcription

1 CABLING REQUIREMENTS: All cabling (copper and fiber) should be Belden or be of equivalent specifications. All cabling (copper and fiber) should be installed to meet or exceed manufacturer s warranty requirements. CAT6a should be used for all copper cable. All copper patch cables should be CAT6a. Patch cables used in racks should be of appropriate length to insure proper connection and neat wire management. Patch cables for rooms should be a minimum of six (6) feet long. All copper patch panels should be Belden CAT6A or be of equivalent specifications. 50- micron multi- mode shielded fiber must be used between all IDFs and the MDF. All fiber patch cables in racks shall be of appropriate length and type to insure proper connection, protection against damage, and neatness of wire management. All fiber patch panels should appropriate for type of fiber and connection use. It should be Belden or of equivalent specifications. All fiber must be a minimum of 12 strands between each IDF and the MDF. All fiber must fully support 10Gbps connectivity. All cable runs must be tested, certified, and blueprinted. Data must be organized into one complete binder per location. There must be a minimum of 6 Ethernet ports per classroom. School #1 will have a minimum of 672 Ethernet ports. School #2 will have a minimum of 432 Ethernet ports. School #3 will have a minimum of 754 Ethernet ports. LAN REQUIREMENTS: All switches should have 1Gbps access ports with 10Gbps uplink ports. All fiber optics used should be appropriate in speed and type according to the use. Fiber optics must be provided the switch Original Equipment Manufacturer or approved by the switch Original Equipment Manufacturer for use. Core switches should be equivalent or better than a Cisco Catalyst 3750X. Edge switches should be equivalent or better than a Cisco Catalyst 2960S. Proposed solution must support port aggregation (IEEE Link Aggregation Control Protocol and IEEE 802.1Q) and auto- negotiation (speed and half/full duplexing) over our data network. Proposed solution must support Power- over- Ethernet (POE) on all switch ports. All switches must be stackable. Proposed switch stacking capability must support at least 10Gbps to support our data network.

2 If chassis solution is proposed, it must maintain at least 40Gbps per slot supervisor card. Proposed solution must be upgradable to 80Gbps per slot to insure growth without swapping hardware. Proposed solution must support QoS with strict priority queuing to support Voice over IP (VoIP) Network. Shared queuing model will not be accepted. All equipment must be new in box provided by the Original Equipment Manufacturer. PORT DENSITY School #1 will require a minimum of eighteen (18) 48- port switches. School #2 will require a minimum of twelve (12) 48- port switches. School #3 will require a minimum of eighteen (18) 48- port switches. WLAN REQUIREMENTS QUANTITY and DESIGN: Please respond with a controller- based wireless solution for three (3) elementary schools. Each school will consist of up to sixty- five (65) wireless access points n connectivity must be supported throughout entire campus and able to support up to 40 wireless devices per classroom. PART I: Wireless Networking (WLAN) SOLUTION A. WLAN Network Enterprise Architecture 1. Centralized WLAN architecture with centralized controller managing thin access points, with integrated network management. 2. Self- contained, integrated, overlay solution, not requiring upgrades or enhancements to existing routers and switches. 3. The following network services or features must be integrated into the WLAN controller: AP Management Radio Frequency Management Spectrum Analysis Location Tracking 4. The same software, configurations and product functionality supported across all platforms in the product family proposed. i.e. all Access Points must be n and contain spectrum analysis functionality 5. Centralized Enterprise Wireless Networking Architecture Hierarchical Design Central wireless controller at the network core to manage dependent school based WLAN controllers. Should be expandable to support up to 20 school- based controllers. Central Wireless network controller should share the following with the school based WLAN controllers: o Same software o Network Functionality o Management Interface: GUI and CLI Management of school- based controller includes:

3 o o o Software updates Configuration changes Monitoring of school based controller displaying the following: controller/ap status, client status, WLAN security threats B. Authentication/Encryption 1. The solution must have support for the following features: MAC based authentication 802.1X based authentication WPA2/AES link layer encryption WEP link layer encryption WPA/TKIP link layer encryption LEAP, PEAP, EAP- TLS, EAP- TTLS, EAP- GTC authentication Integrated RADIUS termination C. Access Points a/b/g/n functionality certified by the Wi- Fi alliance. 2. Support 802.3af standard Power- over- Ethernet (PoE). 3. APs must not hold internal network information or certificates for authentication such as passwords, encryption keys, or security information. If there is a need, then the access point must contain a TPM (Trusted Protection Module) or equivalent for information protection. 4. All access points should be capable of multi- function services including: data access, location tracking, enterprise mesh, and RF monitoring at no additional cost. 5. All access points should support spectrum analysis functionality with always- on centralized monitoring for real- time FFT, spectrograms, channel utilization, channel availability, and graphs without requiring external laptop use. 6. All access points installed in classrooms should be installed in the middle of the room mounted to the ceiling grid and visible. E. WLAN Communication 1. Support discovery protocol from APs to find and sync with switch/controller, that works over routed and switched subnets and that does not require reconfiguration or features on routers or switches. 2. All AP configuration and service delivery information centrally managed and maintained via the switch/controller. 3. The controller should be capable of generating live RF heat maps, displaying RF coverage patterns and channel distribution in real time. D. WLAN Security 1. Central Encryption/De- encryption of the path between the AP and the controller via standards- based protocols. 2. Support policy based forwarding on the AP with integrated firewall for per user role- based access control. 3. Role- based policy enforcement available as part of the solution, in addition to VLAN/port based policy enforcement. 4. Rules for access rights based on any combination of time, location, user identity, device identity, and extended attributes from the authentication database. 5. The WLAN infrastructure must be able to take action including allowing the traffic, denying the traffic, rejecting the traffic, routing the traffic, destination or source NAT the traffic, modify the QoS level of the traffic, and blacklist the client for policy matches. 6. Automatic Rogue AP classification (from interfering APs) and automatic rogue AP containment.

4 7. Utilization of the same server / user interface for wireless intrusion prevention and wireless data collection. 8. Blacklisting of wireless devices after wireless denial of service attack is detected from the wireless system. 9. Ability to identify wireless users who violate policy and quarantine them at the untrusted network. 10. Ability to prevent students, faculty and staff from connecting to non GGUSD WiFi networks while on school premises in order to stop them from bypassing GGUSD security and content filtering policies. I. WLAN RF Administration 1. Enable ease of deployment and ongoing administration with automatic adjustment of individual AP power and channel settings to maximize performance around other APs, limit the effects of interference (both and non ), and detect and correct any RF coverage holes. 2. Dynamic load balancing to automatically distribute clients to the least loaded channels. 3. Load balancing across 2.4GHz to 5GHz bands without the use of client specific configurations or software. 4. Capability to enable airtime fairness across different types of clients running different operating systems, providing preferred access for fast clients over slow clients. 5. Co- channel interference and adjacent channel mitigation mechanisms. 6. Capability to prioritize critical applications on the wireless network originating from the same device. 7. System should support the above functions in real time and without the need to perform any network baselines or manually administered measurements and must be based on real RF information versus models in management systems. J. WLAN Performance 1. WLAN infrastructure should increase capacity as it increases coverage automatically; neighboring access points should dynamically select channels. 2. The controller should support deployment of APs across the wide area network link and should incorporate processing for local connections. K. Origin of Products 1. All WLAN Controllers, Access Points, and Software must be new in box provided by the Original Equipment Manufacturer. PART II: WLAN Administration System A. Administration 1. Administrative rights partitioning - different administrators must have different access rights. 2. Configuration and policy changes applied globally to all systems and APs from a single entry point. 3. Integrated compliance reporting functions, as well as providing various reports regarding users and devices. B. Monitoring 1. Accurate, real- time location tracking of devices and users, including rogue Access Points and security violators without separate location tracking or wireless intrusion appliance/software. 2. RF maps of actual coverage and data rates without the requiring baselines of network signals and/or material modeling of buildings.

5 3. Ability to deliver real- time Access Point and user stats, and advanced search capabilities based on user name, MAC address, IP address, device name. C. Origin of Products: WLAN Management/Monitoring System 1. WLAN Management/Monitoring System must be provided by the Original Equipment Manufacturer. PART III: Warranty and Support 1. 24x7 telephone and access to a technical assistance center staffed by support engineers 2. Next Day Replacement of Defective Equipment 3. Advance Replacement of Defective Equipment 4. Access to Software Upgrades 5. Access to support web portal 6. Duration: one to three years included 7. Please itemize service and maintenance cost after the warranty period VOICE OVER IP (VoIP) REQUIREMENTS: VoIP system must support a minimum of one hundred (100) users with a minimum of an individual extension and voice- mail. All office area phones must be capable of handling multiple lines, call forwarding, caller- id, and fully integrate into the intercom system enabling paging throughout each campus. Each location should have a minimum of three (3) wireless units to be used as needed. Each location should have a minimum of 1 audio/video conferencing phone. VoIP system should fully integrate into local- area- network (LAN) and wireless- local- area- network (WLAN) using QoS where needed to insure call quality to every user. VoIP system should support a loud ringer in the cafeteria areas to insure cafeteria staff hears all calls. All equipment must be new in box provided by the Original Equipment Manufacturer. Uninterruptible Power Supply (UPS) REQUIREMENTS: Each MDF and IDF must have a UPS that can provide a minimum of an hour of Uninterruptible Power Supply with the load for that specific MDF or IDF. Each UPS must be configured for Network Management. Each MDF and IDF must have enough receptacles for complete redundancy as needed by equipment in the associated MDF and IDF. Each MDF must have metered rack mountable PDU s and must be configured for network management. Each MDF must have the appropriate Step Down Transformer with 5-20 receptacles.

6 Rack REQUIREMENTS: Each MDF and IDF must have appropriate sized rack for installed equipment. Each MDF rack must have front and rear doors. Each MDF rack must have removable side panels. Each MDF rack must have Leveling feet. Each MDF rack must have Rear cable management channels and capable of attaching PDU s. All racks must be keyed alike. Wall mountable racks are preferred in IDF s where possible. Additional Information: Bid is due at Murfreesboro City Schools, 2552 South Church Street Murfreesboro, TN by Feb. 28 th at 2:00pm CST. You can mail your bid in attention to Becky Sally or deliver your bid to the address listed above. Any bids received after Feb. 28 th at 2:00pm CST will not be considered. There will be a mandatory tour and questions session on Feb. 14 th at 10:00am CST at Bradley Academy, 511 Mercury Blvd. Murfreesboro, TN If you cannot make the above date or time, make- ups will be done by appointment only on Feb. 15 th. You must schedule your appointment in writing with dustin.jones@cityschools.net by February 13, 2013 to attend on this date. If you have any questions feel free to contact MCS technology at