Salient Specifications.xlsx
XLSX spreadsheet 26 KB Posted
- Solicitation number
- 36C10B26Q0212
About this file
This is a technical specifications document (salient specifications) for a VXLAN Leaf Access Campus Switch that the Department of Veterans Affairs is procuring. The document outlines comprehensive hardware and software requirements for an enterprise-grade 48-port multigigabit access layer switch with redundancy, advanced networking capabilities, and cloud-based management integration.
The hardware specifications require a fixed chassis with 19-inch rack mounting, AC power input, and fully redundant N:N power supplies. The switch must support a minimum of 36 ports at 100/1000/2500 Mbps and 12 ports at 100/1000/2500/5000/10000 Mbps, with four modular SFP+ uplink ports supporting 1G/10G connections. The device must include 802.3af and 802.3at Power over Ethernet capabilities on all 48 ports with configurable power levels and visibility into PoE usage, support stacking of 9+ switches with 100Gb bidirectional capability, and provide 8 configurable egress queues per port with strict priority. The operating system must support comprehensive Layer 3 protocols including IPv4/IPv6, OSPF, BGP, and VRRP, along with extensive Layer 2 features including 802.1q VLANs (minimum 255 VLANs, 4000 VLAN IDs), 802.3ad LACP, IGMP snooping, port security with 802.1x authentication, and QoS with DSCP and CoS classification. The switch requires VXLAN support per RFC 7348, RFC 8365, and RFC 7432 as the overlay protocol with Ethernet VPN (EVPN) as the control plane, capable of operating in a native IPv6 underlay network without IPv4 on non-loopback interfaces.
The management solution must be cloud-based and FedRAMP authorized, capable of managing 50,000 network devices, 200,000 access points, and 5,000 routers/firewalls through a single pane of glass across 300 primary locations with 3,000 sub-locations. The management platform must support zero-touch provisioning, role-based access control with SSO integration via SAML/ADFS, streaming telemetry with AI-driven monitoring and proactive remediation, automated compliance notifications, configuration rollback capabilities, and REST API integration for third-party tools. All licensing for required features must be perpetual, and the vendor must demonstrate leadership quadrant positioning through industry analyst recognition such as Gartner, with dual platform microservices architecture enabling seamless switching without hardware changes and advanced analytics for application performance (Teams, EHR systems) and end-user experience optimization.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
VXLAN Leaf (Access)
| Campus Access Leaf Switch Salient | |||||
| Vendor: | |||||
| OEM & Model/Part Number: | |||||
| Network OS Equipment will be shipped with: | |||||
| Network OS Equipment Release Notes PDF Document: | |||||
| ID | Ref. No. | Primary Attribute | Secondary Attribute | Specification | Provide Evidence Here |
| 1 | 1 | Chassis | Type | Fixed Configuration | |
| 2 | 19 Inch Rack Mounting | Required | |||
| 3 | Power Input Options | AC | |||
| 4 | Redundant Power (N:N) | Must include High Availability: |
Fully redundant power supplies required to power fully loaded configuration within the same Chassis. (power cords/supply must be provided)
| 2 | 1 | Packet Processor | Layer 2 Switching | Non-Blocking |
| 2 | Layer 3 Switching | Non-Blocking | ||
| 3 | IGMP Snooping & IPv6 MLD v1 & v2 | Switched in Hardware | ||
| 4 | MAC Addresses Per Switch | >=32000 | ||
| 3 | 1 | Port Interfaces | Access Port Options | 100/1000/2500 Mbps - Multigigabit - Minimum of 36 ports |
100/1000/2500/5000/10000 Mbps - Multigigabit - Minimum of 12 ports
| 2 | Uplink Port Options | Shall be modular and support a minimum of four (4) uplink ports. SFP+ connectivity in each port. Each port supports 1G/10G connections via SFP. |
| 3 | Per Switch Port Count Options | - 48 Port |
| 4 | SFP Media Flexibility Options | IEEE 802.3z-compliant 1000BASE-SX, 1000BASE-LX/LH, 1000BASE-T (RJ45), 100Base-T(RJ45), 10GBASE-SR, 10GBASE-LR,must be compatible with 3rd party OEM compliant SFPs |
| 5 | Power over Ethernet Options | - 802.3af support (48 port options, capable of supplying power to all ports) (All Power cords and supplies must be provided) |
- 802.3at support (48 port options, capable of supplying power to all ports)
- Configurable power levels per port
- Visibility into PoE power use
| 6 | Multigigabit Ethernet | 802.3bz support |
| 7 | Switch Stack Capabilities | Must be able combine 9+ switches into a single stack or management plane |
Must have a minimum of 100Gb bidirectional stacking capability
| 8 | Configurable Egress Queues | => 8 per port including Strict Priority | ||
| 4 | 1 | Operating System | Layer 3 Protocols & Features | IPv4, IPv6,ICMP,OSPF, |
Virtual Router Redundancy Protocol (VRRP) Switching load sharing configurable per packet or per session, and per session is configuration with L3 address and L4 ports Protocol Independent Multicast (PIM) v1 & v2 Nonstop forwarding with stateful switchover
2 OSPF Requirements IPv4 Open Shortest Path First (OSPF) versions 2 IPv6 Open Shortest Path First (OSPF) versions 3 MD5 authentication Configurable 32-bit loopback router ID Reference: **https://www.rfc-editor.org/rfc/rfc5340.html#section-2.2** Configurable hello packet interval Configurable router dead interval Configurable priority for DR and BDR Configurable per interface network types (P2P, broadcast, NBMA, and virtual links) Configurable cost per interface Configurable cost multiplier Ability to redistribute static routes and other protocol routes using access lists and route maps Must support Native IPv6 without IPv4 configured on ANY interface except for Loopback interfaces.
3 BGPv4 Requirements Multiprotocol Border Gateway Protocol (BGP) for IPv4 and IPv6 Must support Native IPv6 without IPv4 configured in MP-BGP EVPN Configurable 32-bit Loopback Router ID Reference: https://www.rfc-editor.org/rfc/rfc2545.html MD5 authentication Use all standard attributes Ability to enable or disable synchronization Configurable local preference per neighbor Configurable multi-exit discriminator (MED) per neighbor Configurable standard and extended communities Must support Native IPv6 without IPv4 configured on ANY interface except for Loopback interfaces.
4 Required L2 Features 802.1q, Per-port broadcast, multicast, and unicast storm control, 802.3ad (LACP), Link-Layer Discover Protocol, Jumbo Ethernet Frames with MTU up to 9100 bytes
5 Port Security - 802.1x Support
- ability to authenticate multiple devices on the same port
- MAC Authentication Bypass
- Dynamic VLAN Assignment
- Configurable number of MAC Addresses allowed per port
- Configurable actions to take when violation occurs
- Ability to configure MAC address or addresses allowed per port
- Ability to learn and stick a MAC Address per port
6 QoS Features - 802.1p class-of-service(CoS) classification
- Differentiated Services Code Point (DSCP) classification
- Support ingress classification, policing, and marking per port
- Support egress queuing/scheduling
7 Access Control Lists - Access lists in hardware
- Support for access lists source and destination L2 MAC address, Ethernet types, and Ethernet types
- Support for access lists source and destination L3 addresses with masks and L4 port numbers
- Support for prefix lists
- Ability to apply L3 access list to L2 interfaces/ports
- Ability to police (rate limit) per port, per port channel, per VLAN
8 NTP Support - Version 3 or greater Required
- Configurable NTP Peer and Server Associations
- Configurable NTP Authentication
- Configurable NTP Access Restrictions
- Configurable Source IP Address for NTP packets
- Configurable Timezone/Offset
- Configurable automatic recurring daylight savings time
- Configurable per Interface
9 802.1d Required Spanning Tree Features - Must be able to disable spanning tree per port
- Ability to transition immediately to forwarding state per port on edge ports with 802.1d/s/w
- Ability to disable topology change notifications per port on edge ports with 802.1d/s/w
- STP cost configurable per port (0 to 240) 802.1d & 802.1t
- STP priority configurable per VLAN (0 to 61,440) 802.1d & 802.1t
- Ability to prevent rogue bridges from becoming the STP root
- Ability to prevent an alternate port or a root port from assuming a designated port role due to the absence of BPDUs.
-Ability to configure STP edge ports to disable upon receiving a BPDU
10 Network Management Switch Management The solution must be FedRAMP authorized and offer cloud-native management capabilities through organization- and site-specific templates that are natively preconfigured.
Must support the following at the same time without changing OS or abilities
- Switches must work with a single instance of a FedRamped cloud based SAS management solution capable of managing 50,000 switches, 200,000 APs, 5,000 Routers/Firewalls, 4 Million NAC Authentications per day
- Single pane of glass for all routers, AP, NAC and switch platforms across all Campus, Data Center and Remote locations.
- Switches must be able to be accessed by SSH and changes are able to be made using standardized switch commands to be able to override configuration provided by SAS management solution or correct misconfigurations to allow the switch to start communicating with SAS management solution.
Support SSO integration Support Syslog, SSH, or Radius Authentication Disable telnet, ftp, and http by default IPv6 Configuration Support Secure console port with roles based AAA authentication Configurable Console & VTY timeout Ability to define and apply IP access control lists to VTY sessions Out of Band Ethernet Management Port DNS support for resolution of user-defined device names Must support intergratation with any standard 3rd party API and Application/Network management tools
| 11 | Configuration Reversal | Must support the ability to roll back the configuration to a previous configuration in the event of a misconfiguration or a change causing an outage. |
| 12 | MultiChassis EtherChannel Link Aggregation | Required: Must support MC-LAG with LACP |
13 SNMP Features - Support for SNMPv2C, & SNMPv3
- Support for traps that is an agent on the switch to send an unsolicited notifications to the SNMP manager for a configured event.
- Configurable source IP address or interface for traps.
- Supports both read-only (RO) and read-write (RW) community strings
- Ability to restrict each community string to specific IP addresses independently
- Ability to configure different SNMP versions for each SNMP manager
- Support for multiple RO and RW community strings
- Support for multiple SNMP profiles
14 Port Mirroring or similar Required
15 Remote Port Mirroring or similar Required
16 Software Image Management TFTP, FTP, SCP, HTTP, HTTPS
17 Configuration File Management TFTP, FTP, SCP, HTTP, HTTPS
18 VLAN Support >= 255 VLAN’s >= 4000 VLAN ID’s
19 Data Traffic Rate Limiting - Source and Destination IP
- Layer 4 TCP and UDP
- Source and Destination MAC
20 VOIP Features Configurable Voice-VLAN
21 Message Logging Buffer - Configurable log history size
- Configurable logging severity
- Configurable log message time stamps
22 IPv6 Underlay Network.
Physical infrastructure used for a Spine-leaf fabric.
Deployed as a Clos topology with a native IPv6 only underlay network All links between leaves and spines are point-to-point Must support MP-BGP with Native IPv6 in Underlay with PIM and IGMP Note: 32-bit values/labels represented as IPv4 addresses are acceptable (e.g. BGP router ID)
Control Plane Ethernet VPN (EVPN) is required as the overlay control plane and provides virtual connectivity between different layer 2/3 domains over an IPv6 network.
Must support Native IPv6 without IPv4 configured in MP-BGP EVPN
Overlay Networks. Segmented Tenant Networks created on top of the IPv6 only underlay network.
Must support Native IPv6 without IPv4 optimized multicast in Tenant Overlay
Must support Native IPv6 without IPv4 configured in Unicast VxLAN
Must support Native IPv6 without IPv4 configured in BUM Traffic
Must support Native IPv6 without IPv4 configured in VTEPs
| 5 | 1 | Network Fabric Virtualization | Role | Capable of leaf node |
| 2 | Protocols | VXLAN RFC 7348, RFC 8365, RFC 7432 | ||
| 6 | 1 | Licensing | Management | Capable of single instance enterprise management of licenses |
| 2 | Duration | Licensing for all required features shall be perpetual | ||
| 7 | 1 | |||
| 2 | ||||
| 8 | 1 | Scaling | Number of Locations | Must be able to manage and separate multiple locations |
Must scale to support 300 Primary locations with 3000 sub locations in a single pane of glass
| 2 | Number of Network Devices | Must support management of a minimum of 50K network device or stack of device ip addresses in a single pane of glass | ||
| 3 | Platform Support | Must support all switch models (Spine, Super Spine, Access Leaf, Server Farm Leaf, Boarder Leaf) in a single management solution. | ||
| 4 | Number of Management Points | Must support the entire VA enterprise network with a single dashboard for executive visibility and analytics | ||
| 9 | 1 | Network Device Configurations | Compliance | Must support notification of out of compliance devices for both OS and configurations. |
| 2 | Configuration Deployment | Must support configuration of device with device offline. When device comes online it must reach out to SAS and download configurations for a ZTP deployment. | ||
| 3 | Automated Changes | Must apply changes to devices by location/sub location, device model, and device function based on configurations that were determined to be non-impactful | ||
| 4 | Manual Changes | Must apply changes to devices by location/sub location, device model, and device function based on configurations from custom jobs via scheduled and unscheduled methods | ||
| 5 | Templatization | Must support the configuration of templates to be automatically applied to network devices based on role/function | ||
| 6 | Misconfiguration Prevention | Must support the automatic reversal of configuration in the event of a change causing an outage event causing the network device to be unreachable | ||
| 7 | Change Tracking | Must be able to send change data to external logging targets |
Must be able to track changes locally
| 8 | Zero Touch Provisioning | Shall demonstrate campus fabric deployment being deployed within minutes and serving clients. | ||
| 10 | 1 | Telemetry Data | Streaming | Must provide streaming telemetry information from network devices. |
Must be able to use data to provide optimization of network, provide problem location, and issue investigation.
Must be able to be export Telemetry data 2 Network Traffic Must collect data for application visibility and recognition for endpoint analytics.
Must be able to perform detailed packet inspection to support endpoint analytics.
3 Network Device Analytics Must be able to perform on network device performance analytics.
Must provide performance metrics and baselines.
Must be able to provide all devices that connected to network devices for endpoint tracking 4 Visibility Must provide end to end visibility and proactive remediation from client to cloud using Generalize Large Experience Models (LEM) Must provide proactive packet captures directly on the switch management platform
| 5 | Predictability | Streaming telemetry, AI driven monitoring and proactive identification/resolution of end user experience events. Monitoring throughput, successful connects, switch health and bandwidth | ||
| 6 | Predictability | Must be able to demonstrate how the network infrastructure will analyze network data points from applications (i.e. Teams, EHR, etc.) to troubleshoot collaboration performance and predict issues via live synthetic testing. | ||
| 11 | 1 | Authentication, Authorization, Accounting | Authentication | Must utilize SSO (via SAML/ ADFS) for user authentication using certificate based authentication |
| 2 | Authorization | Must be able to provide role based access natively within the solution | ||
| 3 | Accounting | Must be able to track and archive per user changes for up to 12 months |
Must be able to send change logs to external logging targets
| 12 | 1 | Programmability | API | Must support the utilization of API for both configuration management and system integration updates. |
| 2 | REST | Must utilize REST API to make configuration changes on network devices and zero touch provisioning | ||
| 3 | Observability | Must provide autonomous troubleshooting, remediation, and optimization of all network domains | ||
| 4 | Documentation | Must provide API programing documentation references in management solution | ||
| 5 | IPv6 | Management solution shall be capable of configuring IPv6 features on managed devices | ||
| 13 | 1 | Endpoint Data Analysis | End of Life Milestones | Must provide status of product milestone events by serial number |
| 2 | Warranty and Support Data | Must provides Status of hardware and software support by serial number | ||
| 3 | Security Vulnerabilities | Must be able to provide Common Vulnerabilities and Exposures (CVE) by installed software version | ||
| 4 | Licensing Level | Must show licensing status per device by serial number | ||
| 5 | Service Level Agreements | AI actions must be able to detect bad cables for uplinks and end user facing interfaces, detect and remediate networking loops, negotiate mismatches, and port flaps | ||
| 6 | Service Level Agreements | Proactive diagnosis of end user device authentication issues across the full stack. Demonstrate reducing MTTR and enabling network automation at large enterprise scale |
Management SAS
| Automation-Telemetry-AI Solution |
| Vendor: |
| OEM & Model/Part Number: |
| ID | Ref. No. | Primary Attribute | Secondary Attribute | Specification |
| 1 | 1 | Installation Location Options | Cloud based | Must be FedRAMP Authorized and cloud native support |
| 2 | 1 | Scaling | Number of Locations | Must be able to manage and separate multiple locations |
Must scale to support 300 Primary locations with 3000 sub locations in a single pane of glass
| 2 | Number of Network Devices | Must support management of a minimum of 50K network device or stack of device ip addresses in a single pane of glass | ||
| 3 | Platform Support | Must support all switch models (Spine, Super Spine, Access Leaf, Server Farm Leaf, Boarder Leaf) in a single management solution. | ||
| 4 | Number of Management Points | Must support the entire VA enterprise network with a single dashboard for executive visability and analytics | ||
| 3 | 1 | Network Device Configurations | Compliance | Must support notification of out of compliance devices for both OS and configurations. |
| Configuration Deployment | Must support configuration of device with device offline. When device comes online it must reach out to SAS and download configurations for a ZTP deployment. | |||
| 2 | Automated Changes | Must apply changes to devices by location/sub location, device model, and device function based on configurations that were determined to be non-impactful | ||
| 3 | Manual Changes | Must apply changes to devices by location/sub location, device model, and device function based on configurations from custom jobs via scheduled and unscheduled methods | ||
| Templatization | Must support the configuration of templates to be automatically applied to network devices based on role/function | |||
| Misconfiguration Prevention | Must support the automatic reversal of configuration in the event of a change causing an outage event causing the network device to be unreachable | |||
| 4 | Change Tracking | Must be able to send change data to external logging targets |
Must be able to track changes locally 4 1 Telemetry Data Streaming Must provide streaming telemetry information from network devices.
Must be able to use data to provide optimization of network, provide problem location, and issue investigation.
Must be able to be export Telemetry data 2 Network Traffic Must collect data for application visibility and recognition for endpoint analytics.
Must be able to perform detailed packet inspection to support endpoint analytics.
3 Network Device Analytics Must be able to perform on network device performance analytics.
Must provide performance metrics and baselines.
Must be able to provide all devices that connected to network devices for endpoint tracking
| 5 | 1 | Authentication, Authorization, Accounting | Authentication | Must utilize SSO (via SAML/ ADFS) for user authentication using certificate based authenitication |
| 2 | Authorization | Must be able to provide role based access natively within the solution | ||
| 3 | Accounting | Must be able to track and archive per user changes for up to 12 months |
Must be able to send change logs to external logging targets
| 6 | 1 | Programability | API | Must support the utilization of API for both configuration management and system integration updates. |
| 2 | REST | Must utilize REST API to make configuration changes on network devices and zero touch provisioning | ||
| 7 | 1 | IPv6 | IPv6 | Management solution shall be capable of configuring IPv6 features on managed devices |
| 8 | 1 | Licensing | Network Devices | Must include licensing for all proposed hardware for the expected useful life |
| 9 | 1 | Endpoint Data Analysis | End of Life Milestones | Must provide status of product milestone events by serial number |
| 2 | Warrenty and Support Data | Must providesStatus of hardware and software support by serial number | ||
| 3 | Security Vulnerabilities | Must be able to provide Common Vulnerabilities and Exposures (CVE) by installed software version | ||
| 4 | Licensing Level | Must show licensing status per device by serial number | ||
| 10 | 1 | Orchastration & Automation | Must provide autonomous troubleshooting, remediation, and optimization of all network domains | |
| 2 | Must provide end to end visibilty and proactive remdiation from client to cloud using Generalize Large Experience Models (LEM) | |||
| 3 | Must be able to demonstrate how the network infrastructure will analyze billions of network data points from applications (i.e. Teams, EHR, etc.) to troubleshoot collaboration performance and predict issues via live synthetic testing. | |||
| 4 | Required to be fully cloud Native for single pane of glass for management | |||
| 5 | Live telemetry and AI driven monitoring and proactive identification and resolution of service level expectations for thoroughput, successful connects, switch health, bandwidth, etc. | |||
| 6 | Shall demontrate campus fabric deployment being deployed within minutes and serving clients. | |||
| 7 | AI actions must be able to detect bad cbales for uplinks and end user facing interfaces, detect and remediate netowrking loops, negotiate mismatches, and port flaps | |||
| 8 | Proactive diagnosis of end user device authentication issues across the full stack. Demonstrate reducing MTTR and enabling network automation at large enterprise scale | |||
| 9 | Dual platform approach with microservices shall be deminstrated to deliver seamless switching without hardware changes. | |||
| 10 | End user experience through AI driven insights utilizing telemetry and automation, including proactive optimization for IoT, collaboration tools. | |||
| 11 | Innovation | Shall be listed in the Leadership quadrant through an industry expert analyst (i.e. Gartner). |
File details come from the government source that posted it. Updated .