Physical characteristics |
Modular chassis, compatible with 19 "rack |
Maximum height 6 RU |
Voltage: AC 100V or 220V |
Redundant and hot-swappable controllers |
Redundant and hot-swappable power supply N+ 1 |
Performance |
IPv4 Routes - Minimum capacity for 10,000,000 (ten million) unicast routes in the RIB table, and 6,000,000 (six million) routes in the FIB table. |
IPv6 Routes - Minimum capacity for 6,000,000 (six million) unicast routes in the RIB table, and 2,000,000 (two million) in the FIB table. |
Separation of the control plan from the data plan |
IPv4 and IPv6 packet forwarding in hardware |
Jumbo frame support with at least 9100 bytes (IP MTU) |
Minimum throughput of 2.4 Tbps |
Interfaces |
Minimum of 12 (twelve) 100GbE ports divided in two line cards, of which: - • 06 (six) ports populated with a 100GBASE-LR4 transceiver
- • 06 (six) ports for future expansion
The ports must be able to support transfers of 100Gbps in a single flow. |
Minimum of 5 (five) 10GbE ports populated, preferably with SFP + 10GBASE-LR transceivers, but option with 40G/100G modules of type 4x10G / 10x10G will be accepted as long as the transceiver is compatible with 10GBASE-LR |
Functionalities – If licenses are needed, they must be included |
Static routing (IPv4 and IPv6) |
OSPF: ▪ RFC 2328 e 5340 - OSPFv2 e OSPFv3 ▪ RFC 1587 - OSPF NSSA option ▪ RFC 2370 - OSPF Opaque LSA options ▪ RFC 3623 - Graceful OSPF restart |
BGP: ▪ RFC 1771 - BGP4 ▪ RFC 1997 - Communities Attribute ▪ RFC 2283 - Multiprotocol Extensions ▪ RFC 2385 - TCP MD5 Signature Option |
▪ RFC 2842/3392 - Capabilities Advertisement ▪ RFC 2545 - Multiprotocol Extensions for IPv6 Inter-domain Routing ▪ RFC 2918 - Route Refresh Capability ▪ RFC 4893/6793 - Support for four-octet ASN space ▪ Draft – BGP PIC (Prefix-Independent Convergence) ▪ RFC 5575 – Flow-specification (IPv4) ▪ draft-ietf-idr-flow-spec-v6 – Flow-specification (IPv6) ▪ Desirable - draft-ietf-idr-flowspec-interfaceset – Applying BGP flowspec rules on a specific interface set ▪ Ability to configure which router interfaces will process Flows-Spec filters ▪ Desirable – draft-ietf-idr-flowspec-redirect-ip BGP Flow-Spec Redirect to IP Action - |
IS-IS: ▪ RFC 1142 or ISO/IEC 10589 (ISO 8473) ▪ RFC 1195 - Use of OSI IS-IS for Routing in TCP/IP and Dual Environments ▪ RFC 2966 or RFC 5302 - Domain-Wide Prefix Distribution with Two-Level IS-IS ▪ RFC 2763 or RFC 5301 - Dynamic Hostname Exchange Mechanism for IS-IS ▪ RFC 5120 - M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-IS) |
MPLS: ▪ RFC 2205 - Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification ▪ RFC 3031 - Multiprotocol Label Switching Architecture ▪ RFC 3032 - MPLS Label Stack Encoding ▪ RFC 5036 - LDP Specification ▪ RFC 3209 - RSVP-TE: Extensions to RSVP for LSP Tunnels ▪ RFC 3270 - Multi-Protocol Label Switching (MPLS) Support of Differentiated Services. ▪ RFC 5443 - LDP IGP Synchronization |
Multicast: ▪ RFC 1112 - Host Extensions for IP Multicasting ▪ RFC 2236 - Internet Group Management Protocol, Version 2 ▪ RFC 3376 - Internet Group Management Protocol, Version 3 ▪ IGMP Snooping ▪ RFC 2710 – Multicast Listener Discovery (MLD) for IPv6 ▪ RFC 2362 - Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification ▪ Anycast RP ▪ MSDP |
QoS: ▪ 8 hardware queues ▪ RFC 2475 - DIFFServ: Mechanisms of classification, marking, traffic prioritization, applicable by physical and logical interfaces, without impact on packet forwarding performance) ▪ Rate-limit: Bandwidth limitation on physical and logical interfaces, applicable without impact on packet forwarding performance |
MPLS Traffic Engineering: ▪ RFC 2205 - Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification ▪ RFC 4090 - Fast Reroute Extensions to RSVP-TE for LSP Tunnels ▪ RFC 3906 - Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels |
▪ RFC 3477 - Signaling Unnumbered Links in Resource Reservation Protocol—Traffic Engineering (RSVP-TE) ▪ RFC 5305 - IS-IS Extensions for Traffic Engineering ▪ RFC 5307 - IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) ▪ RFC 3630 - Traffic Engineering (TE) Extensions to OSPF Version 2 ▪ RFC 3209- RSVP-TE (Resource Reservation Protocol—Traffic Engineering): Extensions to RSVP for LSP (Label Switched Path) Tunnels |
Pseudo wire or equivalent, L2circuit (Martini), L2VPN (Kompela), L3VPN, BGP-VPLS e EVPN |
VIRTUALIZATION (on a single physical chassis): VR – Virtual Router or VRF-lite (minimum 12), including the ability to import and export routing information between configured instances. |
E-OAM (802.1ag, 802.3ah, Y.1731), MPLS OAM (LSP Ping, LSP Traceroute) |
ISSU, NSR, Graceful restart, with support to the main routing protocols |
BFD (in OSPF, BGP and static routes) for IPv4 and IPv6 |
802.1Q (VLANs), 802.3ad (LAG up to 8 ports per group), 802.3ah (LFM), 802.1ag (CFM) |
Management: ▪ SNMPv2c, SNMPv3 ▪ Provide bit / packet traffic statistics per physical port and logical port (VLAN) ▪ Console access via SSH2 and console port (suitable cable provided with equipment) ▪ Export Netflow v9 or IPFIX or S-Flow (minimum support for IPv4 and IPv6, desirable MPLS) ▪ Support group of users with different levels of access ▪ Support NETCONF / YANG ▪ Telemetry support desirable |
Authentication (RADIUS, TACACS+) |
uRPF strict or loose configurable per port. Allow uRPF exception setting per port. Support for feasible-path mode is desirable. |
NTP or SNTP clock synchronization |
GRE (RFC 2784) |
PBR (policy-based routing) or FBF (filter-based forwarding) - Source-based routing Support for subinterfaces or logical interfaces where IPv4 and IPv6 addresses can be configured with VLAN from local scope to port. Support multiple services on the same physical port (IP routing, switching, MPLS VPN) |
SSHv2 console access |
