Skip to content

One rack, every layer: the CloudLAB bench and the people behind it

L2-3 traffic generators at 1G, 10G and 100G, L4-7 and security engines at 200G and above, WAN emulators per link, a Wi-Fi bench up to Wi-Fi 6 with Wi-Fi 7 in progress, 100G ports for RoCEv2 agreed per setup. One patching field connects any unit to any instrument, your device sits in the rack or runs as a VM, and a TEST4NET engineer is on every session. Founded by an engineer with 20 years in network testing; member of three industry unions in Armenia.

Request a test plan CloudLAB plans
Capacity by layer what the rack holds today
L2-3 generators RFC 2544, 2889, routing and switching 1G · 10G · 100G L4-7 and security stateful sessions, TLS, app mixes 200G+ WAN emulators delay, jitter, loss, shaping per link, 1G–100G Wi-Fi bench clients, APs, roaming Wi-Fi 6, 7 next RoCEv2 and AI fabric PFC, ECN, queue depth 100G, per setup
  • 200G+L4-7 and security
  • 100GL2-3 and RoCEv2 ports
  • 20 yearsfounder in network testing
  • 3industry unions

Access

How your device gets in and how you get to it

Nothing is wired by hand between runs. The patching field, KVM and serial are driven from the portal, so a re-test after a firmware change is a session, not a shipment.

  1. 1

    Ship or upload

    physical unit or virtual appliance

    A physical unit is cabled in the rack with power, KVM and serial. A virtual appliance is uploaded to the lab hypervisor with the vCPU, memory and NIC profile you specify.

    In the rack within a day of arrival

  2. 2

    Open the session

    browser over HTTPS

    Your engineers see the generators, the counters and the device console in one window. A load module can also ship to your site and connect back to the rack.

    No VPN client, no software to install

  3. 3

    Run with an engineer

    every session, every plan

    A TEST4NET engineer wires the setup, runs the plan and is on chat while you watch or drive parts of the run. Daily notes say what passed and what did not.

    Report signed by the engineer who ran it

  4. 4

    Stay or ship back

    hosted unit between runs

    A unit can stay cabled for the next firmware or policy; otherwise it ships back with the report. Working files are deleted after the retention period in the Privacy Policy.

    Re-test in days, not weeks

Instruments

Commercial generators next to our own

The plan names the tool behind each test. There is no single default vendor, and the instruments stay in our rack: bench time always comes with an engineer.

  1. Traffic generators and analysers

    Hardware generators from the major test vendors for L2-3 at line rate and L4-7 with TLS and application mixes, plus our own stateful generator for app-mix profiles captured on your network

  2. Emulators and benches

    WAN emulators for delay, jitter, loss and shaping on any link of the patching field; a Wi-Fi bench with controlled clients and access points; emulated RoCEv2 endpoints on a leaf-spine pair

  3. Capture and automation

    Packet brokers and capture at 10G and 100G, console and KVM recording, scripted runs so every trial repeats with the same settings and the report pulls the numbers straight from the instruments

People and standing

Engineers first, no sales layer

TEST4NET was founded by a network engineer with 20 years in testing and operations. The team is small, works in shifts across time zones and is reached directly: the person who answers the form is the person who runs the bench.

20 years
founder in network testing and operations
1 business day
to a test plan draft, from the engineer who will run it
3 unions
UEICT, UATE and the Union of Operators of Armenia

Company certificates and the equipment list with models are shared under NDA with the test plan

Member of

  • Union of Employers of Information and Communication Technologies (UEICT)
  • Union of Advanced Technology Enterprises (UATE)
  • Union of Operators of Armenia

Scope

What the bench is not

Three lines that save a call

  1. Attacks only on the bench

    Attack and threat traffic runs only in the lab, against the unit under test. We do not attack live infrastructure and we do not do penetration testing.

  2. No instrument rental

    Instruments stay in the rack and run with a TEST4NET engineer. Bench-access plans let your team drive sessions, under the same roof.

  3. No public references

    Clients are not named, reports are not published. Typical scenarios with realistic numbers live in the blog.

Questions

About the bench

CloudLAB Plans Hosted DUT Methodologies

Where exactly is the rack?

In Armenia, in a facility with controlled access and its own power backup. Devices ship by courier to Yerevan; shipping terms and customs paperwork are part of the plan for units arriving from abroad.

Can I see photos or a list of models?

Yes, under NDA together with the test plan. The site lists capacity by layer on purpose: the mix of instruments changes as projects come and go, and a model list on a public page would be out of date within a quarter.

Do you hold certifications?

Company and engineer certificates are shared with the test plan. On the site we show the three industry unions we belong to; vendor training certificates relate to the instruments we run and are listed per project.

Is the bench shared with other clients?

The rack is shared, a session is not. Your device sits on its own patching segment and its own VLANs, sessions are scheduled so one project owns the instruments it uses, and hosted units are powered off between runs unless you ask otherwise.

What about devices above 100G?

L4-7 and security engines run at 200G and above. For L2-3 at 400G we agree the setup per project; the plan says what the bench can measure today and what would be subcontracted or deferred.

Put your device in the rack

Send the model and the KPIs that matter. A test plan draft comes within one business day and a quote in 1–3 business days.

Request a test plan CloudLAB plans

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

We use what you send only to answer you. See our Privacy Policy.