--- title: "Router and Switch Testing: RFC 2544, Route Scale, Convergence | TEST4NET" description: "Independent testing of routers and switches on the CloudLAB bench: RFC 2544 and RFC 2889, 1M routes, convergence after failure. Test plan and quote in 1–3 business days." --- [Skip to content](https://test4net.com/solutions/routing-switching#main-content) [![TEST4NET](https://test4net.com/hubfs/test4net-logo-fixed-2.svg)](https://test4net.com/?hsLang=en) - Services - Products - Resources - Company [News](https://test4net.com/news?hsLang=en) [Login](https://lab.test4net.com) [Support](https://test4net.com/support?hsLang=en) What we test By technology Industries [Load & Performance Testing Throughput, sessions and latency up to and past the rated limit](https://test4net.com/services/load-performance-testing?hsLang=en) [Functional & Conformance Testing Features against the spec, RFC compliance with evidence](https://test4net.com/services/functional-conformance-testing?hsLang=en) [Interoperability Testing Multi-vendor behaviour, before it reaches production](https://test4net.com/services#interop) [Security & Resilience Testing NGFW, IPS and VPN efficacy and performance with threats on the wire](https://test4net.com/services/security-resilience-testing?hsLang=en) [Test Plan & Methodology Design What to test, how, and what counts as a pass](https://test4net.com/services/test-plan-design?hsLang=en) [Test Automation & CI/CD Regression suites wired into your release pipeline](https://test4net.com/services#automation) [Training Programs Hands-on courses for your test engineers](https://test4net.com/services#training) [Equipment Repair Diagnostics and repair of test equipment](https://test4net.com/services#repair) [All services](https://test4net.com/services?hsLang=en) [Routing & Switching RFC 2544 and RFC 2889 on real ports, 1G to 100G](https://test4net.com/solutions/routing-switching?hsLang=en) [Firewalls & NGFW RFC 9411 throughput with inspection switched on](https://test4net.com/solutions/firewalls-ngfw?hsLang=en) SD-WAN & WAN Path selection and QoS under emulated WAN conditions Cloud & NFV Virtual appliances and cloud services under load 5G & Mobile Core Transport and core functions under subscriber traffic Wi-Fi Wi-Fi 6 clients and access points, Wi-Fi 7 in progress Storage & Infrastructure Storage networks and servers under realistic I/O [AI / Switching Fabric (RoCEv2) Lossless Ethernet for GPU clusters: PFC, ECN, fabric load](https://test4net.com/solutions/ai-fabric-rocev2?hsLang=en) All technologies [Telecom Operators Pre-deployment acceptance and vendor comparison](https://test4net.com/solutions/industries#telecom) [Network & Security Vendors Independent validation of your product claims](https://test4net.com/solutions/industries#vendors) [System Integrators Proof for the customer before the rollout](https://test4net.com/solutions/industries#integrators) [Enterprise & Banks Upgrades and new platforms checked before production](https://test4net.com/solutions/industries#enterprise) [All industries](https://test4net.com/solutions/industries?hsLang=en) Not sure where to start? Test plan and quote in 1–3 business days Tell us what you run and what worries you. We propose the tests, tools and timeline. [Request a test plan](https://test4net.com/contacts?hsLang=en) CloudLAB How It Works Pick a scenario, run it in the live lab, get the report Equipment & Capabilities L2-3 to 100G, L4-7 past 200G, Wi-Fi, WAN emulation Access Plans Hourly sessions, subscriptions, dedicated racks Hosted DUT Testing Ship the box or upload the VM, we run the tests [Open the CloudLAB portal](https://lab.test4net.com) Our tools Traffic Generator L4-7 and security traffic past 200 Gbit/s, app mix library WANemu Delay, jitter, loss and bandwidth shaping per link [Book a demo](https://test4net.com/contacts?hsLang=en) New: our own test tools Our own tools, in beta this autumn Built in our lab, priced per gigabit. Join the beta list and see them first. [Join the beta list](https://test4net.com/contacts?hsLang=en) Read Technologies / Protocols Methodologies [Blog Case studies, test insights and lab notes](https://test4net.com/blog?hsLang=en) [Industry News What is changing in network testing and infrastructure](https://test4net.com/news?hsLang=en) FAQ How the lab, sessions and reports work BGP Route exchange, policy and convergence OSPF & IS-IS IGP adjacency, flooding and SPF timing MPLS & SR LDP, RSVP‑TE and SR‑MPLS label paths EVPN / VXLAN Overlay fabrics, MAC/IP routes, multi-homing IPsec & IKEv2 Tunnel setup, rekeying and throughput TLS / HTTPS Handshakes, cipher suites and inspection RoCEv2 Lossless Ethernet, PFC and ECN for AI fabrics Wi-Fi 6 / 6E / 7 802.11ax/be, OFDMA, MLO and roaming All protocols [RFC 2544 Throughput, latency, frame loss and back-to-back](https://test4net.com/methodologies/rfc-2544?hsLang=en) [RFC 2889 LAN switch benchmarking: forwarding, MAC learning, congestion](https://test4net.com/methodologies/rfc-2889?hsLang=en) [RFC 9411 / RFC 3511 Firewall and NGFW performance benchmarking](https://test4net.com/methodologies/rfc-9411-rfc-3511?hsLang=en) RFC 6349 TCP throughput and buffer delay testing RFC 5180 IPv6 benchmarking methodology ITU-T Y.1564 Ethernet service activation: CIR, EIR, KPIs per service ITU-T Y.1731 Ethernet OAM: delay, jitter, loss and SLA monitoring TR-398 Wi-Fi in-premises performance test plan All methodologies Read [Case studies, test insights and lab notes Blog](https://test4net.com/blog?hsLang=en) [What is changing in network testing and infrastructure Industry News](https://test4net.com/news?hsLang=en) How the lab, sessions and reports work FAQ [About Us Independent lab in Armenia, team and history](https://test4net.com/about?hsLang=en) [Why TEST4NET What you get that vendor slides never show](https://test4net.com/why-test4net?hsLang=en) Lab & Certifications Bench capacity, methods and the standards we test against Partners Test tool vendors and IT partners we work with [Contacts Talk to an engineer, not a sales bot](https://test4net.com/contacts?hsLang=en) [Support portal](https://test4net.com/support?hsLang=en) - Services What we test [Load & Performance Testing](https://test4net.com/services/load-performance-testing?hsLang=en) [Functional & Conformance Testing](https://test4net.com/services/functional-conformance-testing?hsLang=en) [Interoperability Testing](https://test4net.com/services#interop) [Security & Resilience Testing](https://test4net.com/services/security-resilience-testing?hsLang=en) [Test Plan & Methodology Design](https://test4net.com/services/test-plan-design?hsLang=en) [Test Automation & CI/CD](https://test4net.com/services#automation) [Training Programs](https://test4net.com/services#training) [Equipment Repair](https://test4net.com/services#repair) [All services](https://test4net.com/services?hsLang=en) By technology [Routing & Switching](https://test4net.com/solutions/routing-switching?hsLang=en) [Firewalls & NGFW](https://test4net.com/solutions/firewalls-ngfw?hsLang=en) SD-WAN & WAN Cloud & NFV 5G & Mobile Core Wi-Fi Storage & Infrastructure [AI / Switching Fabric (RoCEv2)](https://test4net.com/solutions/ai-fabric-rocev2?hsLang=en) All technologies Industries [Telecom Operators](https://test4net.com/solutions/industries#telecom) [Network & Security Vendors](https://test4net.com/solutions/industries#vendors) [System Integrators](https://test4net.com/solutions/industries#integrators) [Enterprise & Banks](https://test4net.com/solutions/industries#enterprise) [All industries](https://test4net.com/solutions/industries?hsLang=en) [Not sure where to start? Test plan and quote in 1–3 business days](https://test4net.com/contacts?hsLang=en) - Products CloudLAB How It Works Equipment & Capabilities Access Plans Hosted DUT Testing [Open the CloudLAB portal](https://lab.test4net.com) Our tools Traffic Generator WANemu [Book a demo](https://test4net.com/contacts?hsLang=en) [New: our own test tools Our own tools, in beta this autumn](https://test4net.com/contacts?hsLang=en) - Resources Read [Blog](https://test4net.com/blog?hsLang=en) [Industry News](https://test4net.com/news?hsLang=en) FAQ Technologies / Protocols BGP OSPF & IS-IS MPLS & SR EVPN / VXLAN IPsec & IKEv2 TLS / HTTPS RoCEv2 Wi-Fi 6 / 6E / 7 All protocols Methodologies [RFC 2544](https://test4net.com/methodologies/rfc-2544?hsLang=en) [RFC 2889](https://test4net.com/methodologies/rfc-2889?hsLang=en) [RFC 9411 / RFC 3511](https://test4net.com/methodologies/rfc-9411-rfc-3511?hsLang=en) RFC 6349 RFC 5180 ITU-T Y.1564 ITU-T Y.1731 TR-398 All methodologies Read [Blog Case studies, test insights and lab notes](https://test4net.com/blog?hsLang=en) [Industry News What is changing in network testing and infrastructure](https://test4net.com/news?hsLang=en) FAQ How the lab, sessions and reports work - Company [About Us](https://test4net.com/about?hsLang=en) [Why TEST4NET](https://test4net.com/why-test4net?hsLang=en) Lab & Certifications Partners [Contacts](https://test4net.com/contacts?hsLang=en) [News](https://test4net.com/news?hsLang=en) [Login](https://lab.test4net.com) [Support](https://test4net.com/support?hsLang=en) [Services](https://test4net.com/services?hsLang=en) / Routing and switching # Routers and switches: forwarding, scale and convergence measured before the cutover We test campus and data-center switches, edge and core routers, EVPN-VXLAN fabrics, white-box switches and virtual routers on the CloudLAB L2-3 bench: 1G, 10G and 100G ports, RFC 2544 and RFC 2889 for forwarding, emulated BGP, OSPF, IS-IS and EVPN neighbours with up to 1M routes for scale, and link, peer and node failures with traffic running. A run takes from 2 weeks and ends with a report that holds forwarding rate and latency per frame size, the route and MAC limits where the box stops, the loss window per failure in milliseconds, and the config export of the run. Test plan and quote in 1–3 business days. [Request a test plan](https://test4net.com/solutions/routing-switching#lead-form) [See the device classes](https://test4net.com/solutions/routing-switching#classes) **Loss window after a link failure** Core pair, 1M BGP routes, traffic running. Same failure before and after tuning. 050100 FORWARDED, % 0500100015002000 TIME AFTER FAILURE, MS design 500 ms Delivered config · 1.9 s Tuned config, day 8 · 180 ms Delivered config Tuned config, day 8 - **1G · 10G · 100G**ports on the L2-3 bench - **1M routes**emulated BGP, OSPF, IS-IS and EVPN neighbours - **From 2 weeks**for a run - **1–3 days**test plan and quote When the number is needed ## Three moments in a network refresh when the datasheet stops being an answer A datasheet gives the forwarding rate of an empty box with default timers. Each moment below asks what the box does with your routes, your policy and your failures, and each gets its own scope. The cases stay the same, so the shortlist result, the acceptance result and the post-upgrade result compare. 1. 1 ### Shortlist Tender, 2–3 models Every candidate runs the same forwarding, scale and convergence cases on the same ports with the same emulated neighbours. Vendors see the plan before the first packet and the results after the last. Ranked table per KPI, scale limit per model, 3–4 weeks for 3 boxes 2. 2 ### Acceptance Before the cutover The delivered boxes with the production config: routing policy, timers, BFD, ECMP, ACLs and QoS from your export. Measured against your design, with your route table and your failure list, before the first production packet. Signed report with pass and fail per case, config exports, from 2 weeks 3. 3 ### Change NOS upgrade or policy change The acceptance cases run again on the new release, the new line card or the new route policy. What moved, by how much, and whether the box still clears the design. Production stays up; we test the spare or the lab pair. Diff per KPI against the last run, 3 business days What we test ## Five device classes, and the numbers each one has to show The bench is the same, the traffic and the pass criteria are not. The table is the starting point of the plan; your design and your route table set the thresholds. | Device class | Numbers in the report | Traffic and config on the bench | Typical size | | --- | --- | --- | --- | | 01Campus access and aggregation switch | RFC 2544 forwarding rate and latency per frame size, RFC 2889 full-mesh and congestion behaviour, MAC table limit, STP and LACP failover time | Frames on every port at once, VLANs and Q-in-Q as configured, a link and a stack member taken down with traffic running | 24–48 ports, 1G and 10G, 100G uplinks | | 02Data-center leaf and spine, EVPN-VXLAN | EVPN route and VTEP scale, hosts per leaf, ECMP balance, convergence on leaf, spine and uplink loss, traffic between overlays | Emulated VTEPs and hosts behind them, route types 2 and 5 from your snapshot, multi-homing as configured, one leaf and one spine failed on purpose | 32–64 ports, 100G | | 03Edge and core router | Routes held in FIB, convergence on link and peer loss with a full table, forwarding at 10G to 100G with the full table loaded, MPLS and segment-routing paths | Hundreds of emulated BGP, OSPF and IS-IS neighbours, up to 1M routes, your policy and timers, BFD as configured, link and peer failures in sequence | 8–32 ports, 10G and 100G | | 04Virtual router | The same KPIs per instance size and vCPU count, forwarding per core, route scale against memory, behaviour when the host is loaded | Image on the bench hypervisor or in your tenant, the same neighbours and failures as the hardware class | 1–20 Gbps per instance | | 05White-box switch with SONiC or another open NOS | Feature checklist against the RFP, forwarding and scale as for the leaf class, convergence per failure, upgrade behaviour of the NOS | Your NOS build and config, the same emulated fabric as the leaf class, the upgrade run with traffic | 32 ports, 100G | Any vendor, physical or virtual, including white-box hardware with an open NOS. Named test tools are picked for the setup and listed in the report. The bench around one router pair Peers emulated BGP, OSPF, IS-IS Generator ports RFC 2544 frames, 1G to 100G R-1 · 1M routesR-2 · 1M routes Router pair under test your policy, timers, BFD, ECMP Hosts and VTEPs emulated, thousands per leaf Config and counters FIB, CPU, per-port counters LINK OR PEER DOWN ON PURPOSE loss window · convergence forwarding rate · latency Around the box ## What sits on each side of the router while it is measured A forwarding number only means something with the right things around the device: the route table it will carry, the policy it will apply, and the failures it has to survive. All three are on the bench at once. 1. ### Scale from your network Route count and prefix mix from your table snapshot, MAC and host counts per VLAN or VTEP, neighbour count per protocol. The bench emulates them, so the box sees its own future, not a lab default. 2. ### Your config, line by line Routing policy, timers, BFD, ECMP and hashing, ACLs and QoS from your export. The report shows which line each loss window or scale limit traces back to. 3. ### Failures with traffic running Link down, peer lost, supervisor switchover, NOS upgrade. Each one with the full table loaded and traffic on every port, timed from the last packet to the first packet back. Typical scenario ## A core pair rated for 2M routes, a datasheet convergence of 50 ms, and a 1.9 s hole in the traffic An operator hands over a new core router pair for acceptance. The datasheet says 2M routes and sub-50 ms convergence. With the production config, 1M BGP routes and traffic on every port, a link failure stops traffic for 1.9 s against a design of 500 ms. The run log points at BFD left off on one peer group and default hold timers on the other. The vendor and the operator tune BFD and switch on prefix-independent convergence on day 8, the rerun gives 180 ms, and forwarding at 100G holds 92% of line rate at 64 bytes and 100% from 128 bytes with the full table loaded. The pair goes into the cutover on a signed report, and the same cases run again after the next release in 3 days. 1.9 s → 180 ms loss window on link failure with 1M routes 92% of 100G line rate at 64 bytes, full table loaded 12 days from the first packet to the signed report Composite scenario from projects of this type. Numbers are realistic and not from one client. Loss window on link failure, ms Delivered config Tuned config, day 8 1900 180 Design 500 0500100015002000 beyond the design clears the design What you take away ## Four numbers that end the argument, and the table they live in The report is built for the meeting after the test: the vendor, the integrator and your network team read the same table, with the pass band from the design next to the measured value Each number comes with its evidence: generator statistics, FIB and CPU counters from the box, captures and the config export of the run Forwarding Rate and latency per frame size under RFC 2544, full-mesh and congestion under RFC 2889, with the full route table loaded. Not the empty-box figure. Scale Routes, MACs, VTEPs and neighbours where the box stops or slows, so the design has a ceiling with a margin, not a datasheet maximum Convergence Loss window in milliseconds per failure type, link, peer, node and upgrade, with traffic on every port, not on an idle box Policy Pass and fail per feature in your config, the config lines behind each failed case, and the behaviour of the box through the upgrade ACC-CORE-03 Acceptance, core router pair Rerun, day 8 ### Result table, 6 of 16 cases | KPI | Pass band | Measured | Result | | --- | --- | --- | --- | | Forwarding at 100G, 64 bytes, full table | ≥ 90% | 92% | Pass | | Latency at 100G, 1518 bytes | ≤ 10 µs | 6.8 µs | Pass | | BGP routes held in FIB | ≥ 1M | 1.2M | Pass | | Link failure, loss window | ≤ 500 ms | 180 ms | Pass | | Peer loss with BFD, loss window | ≤ 1 s | 0.9 s | Pass | | ECMP balance across 4 uplinks | ≤ 10% | 14% | Pass with a note | Where it runs ## The CloudLAB L2-3 bench, and the pages behind this one Boxes ship to CloudLAB or we connect the bench to your lab; virtual routers run on the bench hypervisor or in your tenant, and you watch the run through the portal. The bench has 1G, 10G and 100G ports and emulates hundreds of BGP, OSPF, IS-IS and EVPN neighbours with up to 1M routes and thousands of hosts. The method is RFC 2544 and RFC 2889 for forwarding, and written cases you sign off for scale, convergence and policy. [How a load run goes, step by step](https://test4net.com/services/load-performance-testing?hsLang=en) [RFC 2544: throughput, latency, loss](https://test4net.com/methodologies/rfc-2544?hsLang=en) [RFC 2889: switch benchmarks](https://test4net.com/methodologies/rfc-2889?hsLang=en) [Protocol conformance: BGP, OSPF, EVPN](https://test4net.com/services/functional-conformance-testing?hsLang=en) ### Related reading - [BlogSONiC passes 5 billion dollars. The acceptance test is still on the buyer](https://test4net.com/blog/sonic-5-billion-2026-white-box-acceptance-on-buyer?hsLang=en) - [BlogWhy vendor benchmarks are not enough for infrastructure decisions](https://test4net.com/blog/datasheet?hsLang=en) - [Blog387 network outages in one week. Does your edge survive an ISP failure?](https://test4net.com/blog/network-outage-report-october-2026-387-incidents-a-week?hsLang=en) - [BlogVIAVI State of the Network 2027: 58% test before deployment](https://test4net.com/blog/viavi-state-of-the-network-2027-58-percent-test-before-deployment?hsLang=en) Before the brief ## What network teams ask first Which routers and switches can you test? Any vendor and any form factor: campus and data-center switches, edge and core routers, EVPN-VXLAN leaf and spine, white-box hardware with SONiC or another open NOS, and virtual routers. We need the models, the port plan and an export of the config; the rest is in the plan. Is it tested with our config and our routes? Yes. Routing policy, timers, BFD, ECMP, ACLs and QoS come from an anonymised export; the route table and the host counts come from your snapshot. A vendor-default run can be added as a second baseline so you see what the config costs. How much scale can the bench emulate? Hundreds of BGP, OSPF and IS-IS neighbours, up to 1M routes, thousands of EVPN hosts and VTEPs, on 1G to 100G ports. A larger table or more sessions is agreed per setup and written into the plan before the quote. What about MPLS, segment routing and IPv6? Label-switched paths, SR-MPLS and SRv6 are emulated on the bench the same way as plain BGP and IS-IS: neighbours, labels and traffic, then the failures. IPv6 and dual-stack run in every case by default, not as a separate option. Do you ship the box back? Yes. Boxes go into the CloudLAB rack with KVM and console access and return after the run. For a network that is already racked we connect the bench to your lab over a dedicated link and test a spare or the lab pair. How long does it take and what do we get? Test plan and quote in 1–3 business days after the brief. A run takes from 2 weeks for one device role and 3–4 weeks for a shortlist of 3 models or a leaf-spine pod. The report holds the result table, forwarding and latency per frame size, convergence logs, FIB and CPU counters, captures and config exports, and the rerun of fixed items is part of the plan. ## Send the models, the port plan and the config export. The plan comes back in 1–3 business days. No prices on the site: scope first, then the quote. The vendor and the integrator can sit in on the brief. [Request a test plan](https://test4net.com/solutions/routing-switching#lead-form) [How the load run goes](https://test4net.com/services/load-performance-testing?hsLang=en) Send the shortlist ## You have the method. Now get the numbers. Name the models and the KPIs that matter. An engineer replies within one business day with a test plan draft and a quote. Prefer to chat? [Message an engineer on WhatsApp](https://wa.me/37491612709) We use what you send only to answer you. See our [Privacy Policy](https://test4net.com/privacy-policy?hsLang=en). [Send the shortlist](https://test4net.com/solutions/routing-switching#lead-form) [![TEST4NET LLC](https://test4net.com/hubfs/test4net-logo-fixed.svg)](https://test4net.com?hsLang=en) Independent testing and validation for telecom, information security and cloud infrastructure – real insights, not assumptions [mailto:sales@test4net.com](mailto:sales@test4net.com) #### Navigate - [Home](https://test4net.com/?hsLang=en) - [Why TEST4NET](https://test4net.com/why-test4net?hsLang=en) - [About us](https://test4net.com/about?hsLang=en) - [Contact](https://test4net.com/contacts?hsLang=en) - [Blog](https://test4net.com/blog?hsLang=en) - [Industry News](https://test4net.com/news?hsLang=en) #### Get in touch Sales [sales@test4net.com](mailto:sales@test4net.com) Support [support.test4net.com](https://support.test4net.com) © 2026 TEST4NET LLC. All rights reserved. [Privacy Policy](https://test4net.com/privacy-policy?hsLang=en) [Legal](https://test4net.com/legal?hsLang=en) ```json { "@context" : "https://schema.org", "@id" : "https://test4net.com/#organization", "@type" : "Organization", "address" : { "@type" : "PostalAddress", "addressCountry" : "AM", "addressLocality" : "Yerevan", "postalCode" : "0033", "streetAddress" : "3 Hakob Hakobyan Street (Mergelyan Hub)" }, "alternateName" : "TEST4NET", "contactPoint" : { "@type" : "ContactPoint", "availableLanguage" : [ "en", "ru", "hy" ], "contactType" : "sales", "email" : "sales@test4net.com", "telephone" : "+374-60-88-88-99" }, "description" : "Independent, vendor-neutral lab for testing network and cybersecurity products — NGFW, WAF, IPS, DLP and SASE — and an authorized distributor of test, measurement and network infrastructure solutions.", "email" : "sales@test4net.com", "foundingDate" : "2024", "image" : "https://test4net.com/hubfs/og-t4n.png", "logo" : "https://test4net.com/hubfs/test4net-logo-fixed-2.svg", "name" : "TEST4NET LLC", "sameAs" : [ "https://www.linkedin.com/company/test4net/", "https://t.me/TEST4NET", "https://www.facebook.com/people/Test4net-LLC/61591470856077/" ], "telephone" : "+374-60-88-88-99", "url" : "https://test4net.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://test4net.com/#website", "@type" : "WebSite", "inLanguage" : "en", "name" : "TEST4NET", "potentialAction" : { "@type" : "SearchAction", "query-input" : "required name=search_term_string", "target" : { "@type" : "EntryPoint", "urlTemplate" : "https://test4net.com/hs-search-results?term={search_term_string}" } }, "publisher" : { "@id" : "https://test4net.com/#organization" }, "url" : "https://test4net.com/" } ``` ```json { "@context" : "https://schema.org", "@type" : "Service", "areaServed" : "Worldwide", "description" : "We test campus and data-center switches, edge and core routers, EVPN-VXLAN fabrics, white-box switches and virtual routers on the CloudLAB L2-3 bench: 1G, 10G and 100G ports, RFC 2544 and RFC 2889 for forwarding, emulated BGP, OSPF, IS-IS and EVPN neighbours with up to 1M routes for scale, and link, peer and node failures with traffic running. A run takes from 2 weeks and ends with a report that holds forwarding rate and latency per frame size, the route and MAC limits where the box stops, the loss window per failure in milliseconds, and the config export of the run. Test plan and quote in 1–3 business days.", "isPartOf" : { "@type" : "WebPage", "url" : "https://test4net.com/services" }, "name" : "Routing and switching", "provider" : { "@type" : "Organization", "name" : "TEST4NET", "url" : "https://test4net.com/" }, "serviceType" : "Router and switch testing: RFC 2544 and RFC 2889 forwarding, route and MAC scale, BGP, OSPF, IS-IS and EVPN convergence, failover with traffic", "url" : "https://test4net.com/solutions/routing-switching" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://test4net.com/services", "name" : "Services", "position" : 1 }, { "@type" : "ListItem", "item" : "https://test4net.com/solutions/routing-switching", "name" : "Routing and switching", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Any vendor and any form factor: campus and data-center switches, edge and core routers, EVPN-VXLAN leaf and spine, white-box hardware with SONiC or another open NOS, and virtual routers. We need the models, the port plan and an export of the config; the rest is in the plan." }, "name" : "Which routers and switches can you test?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes. Routing policy, timers, BFD, ECMP, ACLs and QoS come from an anonymised export; the route table and the host counts come from your snapshot. A vendor-default run can be added as a second baseline so you see what the config costs." }, "name" : "Is it tested with our config and our routes?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Hundreds of BGP, OSPF and IS-IS neighbours, up to 1M routes, thousands of EVPN hosts and VTEPs, on 1G to 100G ports. A larger table or more sessions is agreed per setup and written into the plan before the quote." }, "name" : "How much scale can the bench emulate?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Label-switched paths, SR-MPLS and SRv6 are emulated on the bench the same way as plain BGP and IS-IS: neighbours, labels and traffic, then the failures. IPv6 and dual-stack run in every case by default, not as a separate option." }, "name" : "What about MPLS, segment routing and IPv6?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes. Boxes go into the CloudLAB rack with KVM and console access and return after the run. For a network that is already racked we connect the bench to your lab over a dedicated link and test a spare or the lab pair." }, "name" : "Do you ship the box back?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Test plan and quote in 1–3 business days after the brief. A run takes from 2 weeks for one device role and 3–4 weeks for a shortlist of 3 models or a leaf-spine pod. The report holds the result table, forwarding and latency per frame size, convergence logs, FIB and CPU counters, captures and config exports, and the rerun of fixed items is part of the plan." }, "name" : "How long does it take and what do we get?" } ] } ```