Router platform configurations

Use the platform pages when building or reviewing a complete router configuration. Each example combines the port, route-server sessions, Add-Path and ECMP, ROV using the CNX validators, NTP, and a domestic-only export policy.

The examples terminate the service on a logical aggregate, even if the initial connection has only one physical link. This keeps the Layer-3 configuration on a stable interface and allows a later CNX-provisioned link to join the LAG without moving the VLAN, addresses, policies, or BGP sessions. A LAG is not a requirement: members may replace the aggregate shown in an example with a physical interface for a direct-port connection.

CNX provisions LAG and MLAG only within a single site. A CNX-provisioned MLAG may use different access switches at that site. CNX does not offer and will not configure a LAG across CNX sites; multi-site connections use separate member attachments.

• Cisco IOS XE
• Junos OS
• Huawei VRP

The subject guides remain the authority for the purpose and operational checks of each feature:

• IX port
• Route-server BGP
• Add-Path and ECMP
• Traffic steering
• RPKI validators and ROV
• Member time service

All platform configurations are patterns, not ready-to-paste production configurations. Replace every placeholder, retain the router's existing control-plane protection, and validate the candidate configuration against the exact hardware and software release before committing it.

Every complete example configures all three route servers and all three RPKI validators. CNX may rotate individual nodes out of service during routine rolling maintenance without customer notification; a single configured endpoint is therefore not a complete or redundant CNX configuration.