COMMUNITY COLLEGE OF ALLEGHENY COUNTY PURCHASING DEPARTMENT 800 ALLEGHENY AVENUE, PITTSBURGH, PA 15233

Transcription

1 COMMUNITY COLLEGE OF ALLEGHENY COUNTY PURCHASING DEPARTMENT 800 ALLEGHENY AVENUE, PITTSBURGH, PA ADDENDUM 3 REQUEST FOR PROPOSAL NETWORK HARDWARE AND SOFTWARE JULY 27, 2017 The following additional information is hereby made a part of this RFP: **************************************************************************** Various questions and answers: 1. Regarding the correlation between the topology shown on pg. 33 and the client port count - The description on pg. 33 says the red dotted line is a pt-pt fiber link between WH and CO-NOC via AL. - However, the client port count document says there s a circuit between WH and AL? (there is no drop in AL according to the description above). Note page 5 of RFP CCAC Infrastructure Upgrade Phase 2: Campus Optical Node Upgrade Project for description -. West Hills center (WH) has a point-to-point leased dark fiber connection to Allegheny campus (AL). 2. On pg. 33, we believe the black line between West Hills and Allegheny is a fiber pair creating a 3-way junction in Allegheny. - The red dotted line is a switch/router circuit from West Hills through Allegheny up to CO- NOC. - If this is the case, the client port doc. needs to be updated (replace Allegheny with CO-NOC). Within the context of site AL and site WH, RFP is asking client ports at WH and AL. Refer to 22.0 APPENDIX F: Client Side Port Count ed dated July 21,2017 for actual client port count. 3. In Appendix F - There appears to be an error in labeling the top of the chart for first section says CO-NOC yet the Node A for traffic immediately below in table says SO-DR this appears to be a typo and site A of all of these in this immediate table below should replace SO-DR with CO-NOC Reference: RFP 3094 Phase 2: Campus Optical Node Upgrade Project. Answered in Addendum 2 - RFP Network Hardware and Software.

2 4. (Option 2) in Appendix G - The customer requested two Options ; The first is standard non client protected. In this model all traffic is in pairs anyway so a demand of the dual pair is sent in opposite directions around ring providing client/card/path protection (given 1 per direction). Option 2 says now consider Client protection. Does the customer want is to take a Y cable to every demand and further Y cable split the client and send to two different cards and then send a working path/client protect option? This option of Y cable splitting each client to dual cards provides that if a fiber cut were to occur then each client has a splitter and in a fiber ring failure stays up. The ability to keep every client up even during path failure comes at a doubling of the optics cost. The non-client splitter/ trunk splitter approach (option 1) is already resilient given the demands are in pairs and would be diversely routed east/west. Are we interpreting what is desired out of option 2 correctly? It seems unnecessary and thus the reason for the question. Reference: RFP 3094 Phase 2: Campus Optical Node Upgrade Project. In option 2, RFP is asking vendors to provide their best resilient solution against simultaneous fiber cut and optical hardware failure. 5. What length of support should be quoted? (1yr, 3yr or 5yr) Please quote for: Year 1, One Year, maintenance and licensing cost. Year 2, One Year, maintenance and licensing cost. Year 3, One Year, maintenance and licensing cost. Year 4, One Year, maintenance and licensing cost. Year 5, One Year, maintenance and licensing cost. 6. Will you be reusing DC power, or should that be quoted as well? Please refer RFP 3094 Phase 2: Campus Optical Node Upgrade Project, Section How many POE ports are being used in the core today? If we would move the POE items out of the core equipment and into the Edge what impact would that have on the supplied port count as it stands today? Please refer RFP 3093 Phase 1: Campus Core Switch Upgrade Project, PoE requirement is removed. 8. How many 100GE circuits are needed between CO-NOC and SO-DR and how many 10GE encrypted circuits between these two sites? The answer is either 2 x 100GE or 4 x 100GE, and 20 x 10GE encrypted or 40 x 10GE encrypted between CO-NOC and SO-DR? Answered in Addendum 2 - RFP Network Hardware and Software.

3 9. In the RFP for Quote Option 2, vendors are asked to provide a client side protection quote. Does the port count at all sites remain the same for the client side protection as compared with the unprotected? For example, at NO there is a requirement for a total of four ports. Does this port count for Option 2 (client side protection) remain the same, or does it change from 4 ports to 2 ports, as the optical layer is providing East-West protection? There is no change to port count. 10. This question is related to RFP Phase 02: Vendors are asked to submit samples of proposed systems prior to proposal due date. Will you accept a lab tour upon request with lab testing of proposed system equipment performed at vendor labs? CCAC may ask vendor to demonstrate their proposed solution over WebEx or virtual. 11. For the Core Switch RFP, table 20 makes reference to Two Core Chassis Ethernet Fabric. Does Core Chassis Ethernet Fabric refer to the supervisor modules in the chassis or is CCAC asking for two separate chassis at each campus? RFP envision core chassis Ethernet fabrics having features such as eliminate the need for individual switch management, permit switches to automatically share information, reduce the complexities of managing and configuring traditional Ethernet switches, and dealing with the limitations of Spanning Tree Protocol and algorithms. As a result, policies can be centrally applied, and bandwidth can be scaled without manual reconfiguration. Ethernet fabrics can be externally programmable via API, which can extend orchestration and automation capabilities to independent systems. 12. This looks like a general rip and replace of current catalyst 6513's for phase 0. Those catalyst 6500's look like they need 1GB copper / Fiber. Is this a requirement or can we add 1GB switches that have SFP+ and copper ports to uplink into the core switch? Ref: RFP 3093 Phase 1: Campus Core Switch Upgrade Project RFP is asking vendor to propose their best solution as delineated in RFP. And that to submit their best solutions that meets college requirements. 13. Please confirm whether the module and transceiver counts listed in the tables for each site represent the total count for the site or the count per chassis Reference: RFP 3093 Phase 1: Campus Core Switch Upgrade Project. Transceivers count per site.

4 14. The tables list specific quantities of 1G and 40G line cards / modules that should be included in the design, but there is no quantity of 10G line cards specified even though there are many 10G transceivers. Was the intention to support all of the 10G links via breakout cables from 40G ports? 10G LR links cannot be supported via breakout cables, so may we simply include the necessary quantity of 10G and 40G line cards needed to support the number of transceivers listed? Reference: RFP 3093 Phase 1: Campus Core Switch Upgrade Project. Goal of 40G ports with 10G links via breakout cables is to repurpose during RFP 3095 Phase 3: Campus Edge/Access Switch Upgrade Project implementation. Please provide best possible solution. 15. Are the transceiver counts listed in the tables the total number of transceivers that must be accommodated by the chassis configuration? In some cases there seem to be more line cards requested than would be needed to support the transceiver count. For instance, the table for CO-NOC calls for 2 40G line cards but only 4 40G transceivers. Other sites call for 40G line cards when no 40G transceivers are requested. Should the requested number of line cards be included regardless of transceiver port count and line card port density? Reference: RFP 3093 Phase 1: Campus Core Switch Upgrade Project. Goal of 40G ports with 10G links via breakout cables is to repurpose those 40G ports in RFP 3095 Phase 3: Campus Edge/Access Switch Upgrade Project. 16. The tables list a certain number of 40G line cards per chassis but do not specify how many 40G ports are required per line card. Is there a requirement for a certain number of 40G ports per chassis? Goal of 40G line cards with 10G breakout cables is to meet 10G and 40G port count requirement. 17. A certain number of 100G ports are requested but no 100G transceivers are specified. Should pricing include 100G transceivers? RFP 3093 Phase 1: Campus Core Switch Upgrade Project and RFP 3094 Phase 2: Campus Optical Node Upgrade Project is asking compatible 100G transceivers. Please price compatible 100G transceivers between Core Switch and Optical node. 18. Some of the sites require 10G copper transceivers. Is the intention here 10G DAC (twinax) cables, or 10GigT? 10GigT transceivers in an SFP+ port support a maximum of 30m; please confirm this will meet the requirement. 10GigE copper ports transceiver supporting maximum available length.

5 19. What type of fiber optic cable is available and will CCAC use for the 40 Gig uplinks from the Edge switch to the core? Each TR has both Single mode fiber and Multimode fiber (62.5µ or 50µ). 20. Are the access / edge switches running any proprietary protocols between themselves or between the edge and core switches at the moment? Please note section 2.1 of RFP 3095 Phase 3: Campus Edge/Access Switch Upgrade Project for the explanation. 21. Does CCAC have any parallel fiber runs or is this going to done on the existing fibers on the sonnet ring or even between stacks and core switches? Please note section 2.1 of RFP 3094 Phase 2: Campus Optical Node Upgrade Project for the explanation and 20.0 APPENDIX D Fiber Characterization. 22. What are the fiber specs between the edge stack locations and the core? SMF / OM3 or OM4? along with distances please for each uplink. Each TR has both Single mode fiber and Multimode fiber (62.5µ or 50µ). 23. For each campus how many stacks and what are the switch totals in each stack? Please refer 20.0 Appendix D of RFP 3095 Phase 3: Campus Edge/Access Switch Upgrade Project and respective notes for switch count in each stack. 24. Are all 10G ports on the core uplinks dual honed? Please note section 2.1 of RFP 3095 Phase 3: Campus Edge/Access Switch Upgrade Project for the explanation. 25. The proposed Ethernet Fabric chassis based switch should have at least eight slots to accommodate future growth. Is this total slots or 8 or more and how many extra slots would be needed for future growth? Please note section 3.0 of RFP 3093 Phase 1: Campus Core Switch Upgrade Project for the explanation. RFP is asking vendors for the best possible solution. 26. Is the growth expectancy the same for each campus? RFPs are asking vendors for best possible solution. 27. Besides circuit and client port requirements described in Appendix E and F, are there other existing services that must be migrated from the ONS15454 to the new optical solution? Please refer RFP 3094 Phase 2: Campus Optical Node Upgrade Project for comprehensive requirements and expected turnkey solution.

6 28. Is there extra rack space and power at each site to install the new optical solution side by side with ONS15454 prior to circuit migration? Please refer RFP 3094 Phase 2: Campus Optical Node Upgrade Project for comprehensive requirements and expected turnkey solution. 29. About Quote Option 2 with 100GE client side protection, does this option entail doubling the 100GE client port count as detailed in Appendix F? Please refer RFP 3094 Phase 2: Campus Optical Node Upgrade Project for comprehensive requirements and expected turnkey solution. RFP is asking vendors for the best possible solution. 30. Optical section 5.11 of the RFP states "Vendor must submit samples of proposed systems prior to proposal due date. Please reconfirm this requirement and its due date of August 8, CCAC may ask the vendor to demonstrate their proposed solution over WebEx or virtual. 31. What is the ITU Spec that the network fiber meets in the RFP Proposal 3094 Phase 2? Are all segments between the sites the same type of fiber? Please note section 2.1 of RFP 3094 Phase 2: Campus Optical Node Upgrade Project for the explanation and 20.0 APPENDIX D Fiber Characterization. End of Addendum 3. *************************************************************************** Sign addendum and submit to the College with your proposal. Company Name Bidder s Signature (Vendor contact person)