--- title: "Interoperability testing: your device against other vendors | TEST4NET" description: "Your device against emulated peers and real devices of other vendors on the CloudLAB bench: BGP, OSPF, MPLS, EVPN, IPsec, TLS, Wi-Fi, a pass or fail matrix per pair" --- [Skip to content](https://test4net.com/services/interoperability-testing#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/interoperability-testing?hsLang=en) [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/test-automation?hsLang=en) [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](https://test4net.com/solutions/sd-wan?hsLang=en) [Cloud & NFV Virtual appliances and cloud services under load](https://test4net.com/solutions/cloud-nfv?hsLang=en) [5G & Mobile Core Transport and core functions under subscriber traffic](https://test4net.com/solutions/5g-mobile-core?hsLang=en) [Wi-Fi Wi-Fi 6 clients and access points, Wi-Fi 7 in progress](https://test4net.com/solutions/wi-fi?hsLang=en) [Storage & Infrastructure Storage networks and servers under realistic I/O](https://test4net.com/solutions/storage?hsLang=en) [AI / Switching Fabric (RoCEv2) Lossless Ethernet for GPU clusters: PFC, ECN, fabric load](https://test4net.com/solutions/ai-fabric-rocev2?hsLang=en) [All technologies](https://test4net.com/services#coverage) [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](https://test4net.com/cloudlab#how) [Equipment & Capabilities L2-3 to 100G, L4-7 past 200G, Wi-Fi, WAN emulation](https://test4net.com/cloudlab#equipment) [Access Plans Hourly sessions, subscriptions, dedicated racks](https://test4net.com/cloudlab/plans?hsLang=en) [Hosted DUT Testing Ship the box or upload the VM, we run the tests](https://test4net.com/cloudlab/hosted-dut?hsLang=en) [Open the CloudLAB portal](https://lab.test4net.com) Our tools [Traffic Generator L4-7 and security traffic past 200 Gbit/s, app mix library](https://test4net.com/products/traffic-generator?hsLang=en) [WANemu Delay, jitter, loss and bandwidth shaping per link](https://test4net.com/products/wanemu?hsLang=en) [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/products#lead-form) 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](https://test4net.com/faq?hsLang=en) [All resources](https://test4net.com/resources?hsLang=en) [BGP Route exchange, policy and convergence](https://test4net.com/blog/how-we-test-bgp?hsLang=en) [OSPF & IS-IS IGP adjacency, flooding and SPF timing](https://test4net.com/blog/how-we-test-ospf-is-is?hsLang=en) [MPLS & SR LDP, RSVP‑TE and SR‑MPLS label paths](https://test4net.com/blog/how-we-test-mpls-and-segment-routing?hsLang=en) [EVPN / VXLAN Overlay fabrics, MAC/IP routes, multi-homing](https://test4net.com/blog/how-we-test-evpn-vxlan?hsLang=en) [IPsec & IKEv2 Tunnel setup, rekeying and throughput](https://test4net.com/blog/how-we-test-ipsec-and-ikev2?hsLang=en) [TLS / HTTPS Handshakes, cipher suites and inspection](https://test4net.com/blog/how-we-test-tls-and-https?hsLang=en) [RoCEv2 Lossless Ethernet, PFC and ECN for AI fabrics](https://test4net.com/blog/how-we-test-rocev2?hsLang=en) [Wi-Fi 6 / 6E / 7 802.11ax/be, OFDMA, MLO and roaming](https://test4net.com/blog/how-we-test-wi-fi-6-6e-7?hsLang=en) [All protocols](https://test4net.com/blog/tag/protocols?hsLang=en) [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](https://test4net.com/methodologies/rfc-6349?hsLang=en) [RFC 5180 IPv6 benchmarking methodology](https://test4net.com/methodologies/rfc-5180?hsLang=en) [ITU-T Y.1564 Ethernet service activation: CIR, EIR, KPIs per service](https://test4net.com/methodologies/y-1564?hsLang=en) [ITU-T Y.1731 Ethernet OAM: delay, jitter, loss and SLA monitoring](https://test4net.com/methodologies/y-1731?hsLang=en) [TR-398 Wi-Fi in-premises performance test plan](https://test4net.com/methodologies/tr-398?hsLang=en) [All methodologies](https://test4net.com/methodologies?hsLang=en) 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](https://test4net.com/faq?hsLang=en) [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](https://test4net.com/lab?hsLang=en) [Partners Test tool vendors and IT partners we work with](https://test4net.com/partners?hsLang=en) [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/interoperability-testing?hsLang=en) [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/test-automation?hsLang=en) [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](https://test4net.com/solutions/sd-wan?hsLang=en) [Cloud & NFV](https://test4net.com/solutions/cloud-nfv?hsLang=en) [5G & Mobile Core](https://test4net.com/solutions/5g-mobile-core?hsLang=en) [Wi-Fi](https://test4net.com/solutions/wi-fi?hsLang=en) [Storage & Infrastructure](https://test4net.com/solutions/storage?hsLang=en) [AI / Switching Fabric (RoCEv2)](https://test4net.com/solutions/ai-fabric-rocev2?hsLang=en) [All technologies](https://test4net.com/services#coverage) 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](https://test4net.com/cloudlab#how) [Equipment & Capabilities](https://test4net.com/cloudlab#equipment) [Access Plans](https://test4net.com/cloudlab/plans?hsLang=en) [Hosted DUT Testing](https://test4net.com/cloudlab/hosted-dut?hsLang=en) [Open the CloudLAB portal](https://lab.test4net.com) Our tools [Traffic Generator](https://test4net.com/products/traffic-generator?hsLang=en) [WANemu](https://test4net.com/products/wanemu?hsLang=en) [Book a demo](https://test4net.com/contacts?hsLang=en) [New: our own test tools Our own tools, in beta this autumn](https://test4net.com/products#lead-form) - Resources Read [Blog](https://test4net.com/blog?hsLang=en) [Industry News](https://test4net.com/news?hsLang=en) [FAQ](https://test4net.com/faq?hsLang=en) [All resources](https://test4net.com/resources?hsLang=en) Technologies / Protocols [BGP](https://test4net.com/blog/how-we-test-bgp?hsLang=en) [OSPF & IS-IS](https://test4net.com/blog/how-we-test-ospf-is-is?hsLang=en) [MPLS & SR](https://test4net.com/blog/how-we-test-mpls-and-segment-routing?hsLang=en) [EVPN / VXLAN](https://test4net.com/blog/how-we-test-evpn-vxlan?hsLang=en) [IPsec & IKEv2](https://test4net.com/blog/how-we-test-ipsec-and-ikev2?hsLang=en) [TLS / HTTPS](https://test4net.com/blog/how-we-test-tls-and-https?hsLang=en) [RoCEv2](https://test4net.com/blog/how-we-test-rocev2?hsLang=en) [Wi-Fi 6 / 6E / 7](https://test4net.com/blog/how-we-test-wi-fi-6-6e-7?hsLang=en) [All protocols](https://test4net.com/blog/tag/protocols?hsLang=en) 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](https://test4net.com/methodologies/rfc-6349?hsLang=en) [RFC 5180](https://test4net.com/methodologies/rfc-5180?hsLang=en) [ITU-T Y.1564](https://test4net.com/methodologies/y-1564?hsLang=en) [ITU-T Y.1731](https://test4net.com/methodologies/y-1731?hsLang=en) [TR-398](https://test4net.com/methodologies/tr-398?hsLang=en) [All methodologies](https://test4net.com/methodologies?hsLang=en) 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](https://test4net.com/faq?hsLang=en) - Company [About Us](https://test4net.com/about?hsLang=en) [Why TEST4NET](https://test4net.com/why-test4net?hsLang=en) [Lab & Certifications](https://test4net.com/lab?hsLang=en) [Partners](https://test4net.com/partners?hsLang=en) [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) / Interoperability testing # Two vendors on one bench before they meet in your network We put your device next to the implementations it will talk to: emulated peers of several vendors from the bench generators and real second-vendor boxes in the same rack. Every pair runs your configuration and your software versions, through session setup, policy, failover and the negative cases where one side sends an option the other does not expect. You get a compatibility matrix with a pass or a fail per pair, the logs of both sides and a fix list for the vendor. From 1 week. [Request an interop test](https://test4net.com/services/interoperability-testing#lead-form) [What we pair](https://test4net.com/services/interoperability-testing#pairs) Compatibility matrix, one device role ABCD BGP session, policy, 1M routes OSPF and IS-IS adjacency, SPF EVPN type 2 and multi-homing IPsec IKEv2 setup and rekey Failover between the two sides PassPass with a noteFail - **From 1 week**for one device role and up to 4 peers - **1G to 100G**ports on the bench, both sides cabled - **2 logs per pair**your side and the peer side, in the report - **Your versions**the firmware you will deploy, on both ends The pair on the bench Emulated peers several implementations BGP OSPF IS-IS EVPN IPsec Your device Second vendor real box in the rack Your configuration Your software versions Logs of both sides Why a second implementation ## Three things a single-vendor lab cannot show you A conformance test proves the device follows the RFC. An interoperability test proves it works with the implementation on the other end of the cable, which reads the same RFC in its own way. 1. ### Optional fields and defaults Both sides are compliant, one sends a capability the other ignores, and the session stays up with half the routes. The RFC allows both readings; only a pair test shows which one your network gets. 2. ### Timers that never match Hello, hold, DPD and rekey timers have vendor defaults that differ by a factor of 3. The pair works on a quiet bench and flaps under load. We run the pair with the timers of your templates and with traffic. 3. ### The failover nobody rehearsed A link is pulled between two vendors and each one converges by its own rules. The gap in milliseconds is a property of the pair, and it goes into the report per pair. What we pair ## Six protocol areas, each with its own negative cases The pairs come from your network diagram: the device under test against every implementation it will peer with. For each area the table shows what is checked and which negative cases are part of the run. | Area | Pairs on the bench | What is checked | Negative cases | | --- | --- | --- | --- | | 01Routing | BGP, OSPF and IS-IS against emulated peers and a second-vendor router | Session setup, address families, policy, route exchange, convergence after a link loss | Unknown capabilities, unexpected attributes, MTU mismatch, authentication mismatch | | 02MPLS and segment routing | LDP, RSVP-TE and SR-MPLS between two implementations | Label exchange, label stack depth, LSP setup, fast reroute between the two sides | Unsupported TLVs, SID conflicts, label range mismatch | | 03EVPN and VXLAN | A leaf of one vendor with spines and leaves of another | Route types 2, 3 and 5, multi-homing, MAC mobility, ARP suppression, traffic across the overlay | Different ESI handling, sequence number conflicts, inconsistent VNI to VRF mapping | | 04IPsec and IKEv2 | Gateways of two vendors, 1 to 5,000 tunnels | IKE and child SA setup, cipher negotiation, rekey, NAT traversal, DPD, traffic inside | Mismatched proposals, fragmentation, rekey collisions, lifetime defaults | | 05TLS and HTTPS | Clients and servers of several stacks through a proxy or firewall | TLS 1.2 and 1.3 handshakes, cipher selection, certificates, inspection with traffic inside | Unsupported extensions, 0-RTT, renegotiation, certificate chains of 3 and 4 | | 06Wi-Fi | Access points with clients of several chipsets, 10 to 200 clients | Association, WPA3 and WPA2 mixed, roaming with 802.11r, k and v, throughput per client | Legacy data rates, band steering refusals, PMF mismatch | Routing, MPLS and EVPN pairs run against emulated peers and against a real second-vendor device when you ship one or we have it in the rack. Security and Wi-Fi pairs run against the emulated clients and servers of the bench. How a project runs ## Four steps from the network diagram to the fix list 1. 1 ### Pairs Day 1 Your diagram and device list become a pair list: who peers with whom, over which protocol, with which configuration template Pair list and quote 2. 2 ### Bench Days 2–3 Your device in the rack or your virtual appliance on our hosts, the second vendor cabled next to it, emulated peers configured from your templates Bench diagram, port map, both configurations 3. 3 ### Run Days 3–5 Every pair through setup, policy, scale, failover and the negative cases, with traffic. Each fail is reproduced once more with captures on both sides Matrix filled in, captures per fail 4. 4 ### Report Day 5 and later The matrix, the evidence per pair, the configurations of both ends and a fix list written for the vendor: what to change, on which side, with the capture that shows why Report, fix list, one call with the vendor on request Typical scenarios ## Where the pair test pays for itself A second vendor arrives in the core, a tender asks for a mixed estate, an integrator has to sign for a network built from three price lists. Three cases from projects of this type, with the numbers rounded and no client named. Composite scenarios from projects of this type. Numbers are realistic and not from one client. Vendor swap in the core A new router model replaces half of the core, the other half stays. BGP comes up, 1M routes load, and a community attribute set by the old side is silently dropped by the new one. Found on the bench in the policy pass, fixed with one line of configuration before the cutover. Mixed fabric from a tender Leaves from one vendor, spines from another, both EVPN-compliant. All-active multi-homing works until a link in the ESI fails and the two sides disagree on the mass withdraw. The pair test shows a 4-second half-black hole; the tender report says which side to fix. Site-to-site VPN estate Gateways of two vendors, a few hundred tunnels. Setup passes, the rekey of the IKE SA fails on one direction after the lifetime expires, every 8 hours in production. On the bench it fails in an afternoon, with the proposals of both sides in the capture. The report ## A matrix, and behind every cell the evidence The first page is the matrix: pairs down the side, implementations across, a pass, a fail or a pass with a note in every cell. Every cell links to a record with the configuration of both ends, the captures and the counter values at the moment of the fail. What the record of one pair holds Configurations The device under test and the peer, as they ran, so the vendor can reproduce the case without a call. Captures A capture per fail from each end of the cable: the option one side sent and what the other side did with it. Numbers Routes received, sessions up, tunnels established, convergence gap in milliseconds, per pair and per run. Fix list What to change, on which side, in which version it is known to be fixed when the vendor has said so. [Functional and conformance testing](https://test4net.com/services/functional-conformance-testing?hsLang=en) [Routers and switches on the bench](https://test4net.com/solutions/routing-switching?hsLang=en) [How we test BGP, EVPN, IPsec and more](https://test4net.com/blog/tag/protocols?hsLang=en) P-03 EVPN and VXLAN Fail ### Mass withdraw after an ESI link failure, leaf A with spine B Pair Leaf under test (vendor A, your firmware) against spine and peer leaf of vendor B, all-active multi-homing on one ESI Procedure 5,000 MAC addresses learned behind the ESI, traffic from the emulated hosts across the overlay, one ESI link pulled, forwarding timed per flow Result Mass withdraw sent per MAC instead of per ESI; gap of 4 s on the worst flow, 2.1 s median; 0 ms expected by the design Evidence Captures on both ends, BGP EVPN table of the peer before and after, per-flow loss from the generator Fix Leaf side: enable the ESI-based withdraw the vendor lists for this release; retest passed with a gap of 180 ms Questions before the pair list ## What buyers and integrators ask first Do you have the second vendor's device, or do we ship it? Both happen. Routing, switching and security devices of the common vendors are often in the rack already; if not, you ship the second device to the lab or run it as a virtual appliance on our hosts. Emulated peers of several implementations are always available from the bench generators. How is this different from a conformance test? Conformance checks one device against the standard. Interoperability checks two implementations against each other, with your configuration on both. Many projects run both: conformance first to find the clear defects, then pairs to find what only appears between two readings of the same RFC. The conformance service is described on its own page. Which configuration runs on the bench? Yours. We take the templates from both sides of the pair, with the timers, authentication, policy and address families of production. A test on default settings would show you a pair that never exists in your network. What if the two vendors blame each other? The report carries the capture from each end of the cable, so the option sent and the reaction to it are both on record. The fix list says which side changes what. On request we join the call with both vendors and walk through the capture. Can you test more than two vendors at once? Yes. One device role against up to 4 peer implementations fits the 1-week project; a tender with several roles and 3 or more vendors is planned as a matrix with its own schedule, usually 2 to 3 weeks. Can we watch the run? You get a CloudLAB login for the project: the bench, the generator statistics and the console of your device in a browser, live, while the pairs run. Your engineer can repeat any case after the project. ## Send the network diagram and the two device lists. The pair list and the quote come back in a day. From 1 week for one device role. The second vendor's device comes from the rack, from you or as a virtual appliance. [Request an interop test](https://test4net.com/services/interoperability-testing#lead-form) [All services](https://test4net.com/services?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/services/interoperability-testing#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 put your device next to the implementations it will talk to: emulated peers of several vendors from the bench generators and real second-vendor boxes in the same rack. Every pair runs your configuration and your software versions, through session setup, policy, failover and the negative cases where one side sends an option the other does not expect. You get a compatibility matrix with a pass or a fail per pair, the logs of both sides and a fix list for the vendor. From 1 week.", "isPartOf" : { "@type" : "WebPage", "url" : "https://test4net.com/services" }, "name" : "Interoperability testing", "provider" : { "@type" : "Organization", "name" : "TEST4NET", "url" : "https://test4net.com/" }, "serviceType" : "Multi-vendor interoperability testing of network and security equipment", "url" : "https://test4net.com/services/interoperability-testing" } ``` ```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/services/interoperability-testing", "name" : "Interoperability testing", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Both happen. Routing, switching and security devices of the common vendors are often in the rack already; if not, you ship the second device to the lab or run it as a virtual appliance on our hosts. Emulated peers of several implementations are always available from the bench generators." }, "name" : "Do you have the second vendor's device, or do we ship it?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Conformance checks one device against the standard. Interoperability checks two implementations against each other, with your configuration on both. Many projects run both: conformance first to find the clear defects, then pairs to find what only appears between two readings of the same RFC. The conformance service is described on its own page." }, "name" : "How is this different from a conformance test?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yours. We take the templates from both sides of the pair, with the timers, authentication, policy and address families of production. A test on default settings would show you a pair that never exists in your network." }, "name" : "Which configuration runs on the bench?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "The report carries the capture from each end of the cable, so the option sent and the reaction to it are both on record. The fix list says which side changes what. On request we join the call with both vendors and walk through the capture." }, "name" : "What if the two vendors blame each other?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes. One device role against up to 4 peer implementations fits the 1-week project; a tender with several roles and 3 or more vendors is planned as a matrix with its own schedule, usually 2 to 3 weeks." }, "name" : "Can you test more than two vendors at once?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "You get a CloudLAB login for the project: the bench, the generator statistics and the console of your device in a browser, live, while the pairs run. Your engineer can repeat any case after the project." }, "name" : "Can we watch the run?" } ] } ```