Core, PE and peering routers for the full internet table

IP Infusion delivers the IP core and peering router: OcNOS-SP preloaded on qualified routers that hold the full internet BGP table in hardware, validate routes with RPKI and run an SR-MPLS core with TI-LFA, under one support contract.

14.4 Tbpscore router capacity
26OcNOS-SP platforms
600+operators run OcNOS

Every role in the core runs OcNOS-SP

OcNOS-SP runs the PE router at the service edge, the P router in the SR-MPLS core, the peering router at the internet edge and the route reflector. You size each role by hardware and license.

PE routers connect customer sites to P routers in an SR-MPLS core; peering routers connect the core to internet transit and an IXP; route reflectors serve the iBGP sessions Customersite Customersite PE routerL3VPN · EVPN PE routerL3VPN · EVPN P routerTI-LFA · Flex-Algo P routerTI-LFA · Flex-Algo Peering routerfull table · RPKI Peering routerfull table · RPKI Internettransit IXPpeering Route reflector SR-MPLS core iBGP iBGP

What OcNOS-SP runs in the core and at the peering edge

Every row below runs on all 26 OcNOS-SP platforms unless marked, from the OcNOS Feature Matrix.

CapabilityWhat it doesWhere
Full internet BGP tableHeld in hardware, IPv4 and IPv6, on a platform with an external TCAM in the forwarding pathSelected platforms
RPKIRejects routes that fail origin validation at the edgeAll OcNOS-SP, from 7.0
BGP FlowSpec and RTBHPushes DDoS filters and blackhole routes to the edge. See DDoS mitigation.All OcNOS-SP
Large communities, Add-Path, PIC EdgeTags routes for peering policy, advertises multiple paths and speeds convergence at the edgeAll OcNOS-SP
Route reflection and confederationsScale iBGP without a full meshAll OcNOS-SP
BGP-LS and egress peer engineeringExports the topology and egress peer segments to a controller, which steers traffic to a chosen peerAll OcNOS-SP
Segment routing over IS-IS and OSPFOne label-switched path for every service between sitesAll OcNOS-SP
TI-LFAA precomputed loop-free backup path per destinationAll OcNOS-SP
Flex-AlgoA second forwarding plane, for example low latency, on the same IS-IS topologyAll OcNOS-SP
SR-TE with PCEPExplicit paths computed by a PCEAll OcNOS-SP
SRv6, initial supportL3VPN and EVPN services over an IPv6 data plane, with more SRv6 capability in development10 of 26 platforms
LDP and SR interworkingAn SR mapping server adds segment routing next to an LDP core, node by nodeAll OcNOS-SP
L3VPN and EVPN over MPLSCustomer services at the PE routerAll OcNOS-SP

Support varies by platform and license. Check each model in the OcNOS Feature Matrix.

Routers by role

Size the core for capacity and buffering. Size the peering edge for the forwarding path that holds the table.

UfiSpace S9610-36D router

Core (P) router

UfiSpace S9610-36D

Jericho 2C+ · 14.4 Tbps

36 × 400G

UfiSpace S9600-72XC router

Full-table peering edge

UfiSpace S9600-72XC

Qumran 2C · 2.4 Tbps

64 × 25G, 8 × 100G, with OP2 external TCAM

UfiSpace S9600-56DX router

Service edge (PE)

UfiSpace S9600-56DX

Qumran 2C · 4.8 Tbps

4 × 25G, 48 × 100G, 8 × 400G

Edgecore AS7946-30XB router

Compact PE

Edgecore AS7946-30XB (AGR400)

Qumran 2C · 2.4 Tbps

4 × 25G, 22 × 100G, 4 × 400G

NWP Services runs the S9600-72XC with OP2 external TCAM to hold the full table. See every qualified router on the OcNOS Hardware Compatibility List.

Questions about the core and the peering edge.

The PE router joins customer sites to the core: it imposes the transport label and holds the L3VPN and EVPN service state. The P router switches labeled packets between PE routers and holds no customer routes, so it spends its capacity on forwarding and fast reroute. OcNOS-SP runs both roles.
Yes, on a platform with an external TCAM in the forwarding path. NWP Services runs two UfiSpace S9600-72XC routers with OP2 external TCAM and OcNOS-SP, holding the full internet routing table, IPv4 and IPv6, in hardware.
Clients peer only with route reflectors, which pass routes between them, so the core needs no iBGP full mesh. OcNOS-SP supports BGP route reflection and BGP confederations on every OcNOS-SP platform.
Yes. From OcNOS 7.0, OcNOS-SP rejects RPKI-invalid routes at the edge. BGP FlowSpec and RTBH push DDoS filters and blackhole routes to the same edge, and large communities carry your peering policy.
The core runs SR-MPLS with TI-LFA and Flex-Algo, on all 26 OcNOS-SP platforms. OcNOS-SP has initial SRv6 support for L3VPN and EVPN services on 10 of the 26, with more SRv6 capability in development. Check each model in the OcNOS Feature Matrix.
Node by node. LDP and SR interworking with an SR mapping server lets segment routing and LDP forward across one domain, so a new router joins the existing core over standard IS-IS, OSPF and BGP and you convert one role at a time.

Plan your core and peering edge.

We map your PE, P and peering roles to qualified routers, the segment routing design and the support plan.