Hands-on training on the bench: your devices, real generators, our engineer
A program of 2–5 days for your test and network team. The group works in CloudLAB or in your lab: load, functional and conformance tests on the equipment you operate, traffic profiles from your network, a report that survives a vendor review. After the course the team repeats every test on its own.
- 01BriefOne call
- 02ProgramBuilt for your devices
- 03Bench days2–5 days
- 04MaterialsRepeat on your own bench
What the team gets
Three things a slide course does not give
Every exercise runs on a real generator against a real device, with a pass criterion set in advance. The group leaves with a measured result and the method behind it
A method that transfers
How to turn a tender line or an RFC clause into a test case: topology, traffic, load level, duration, pass criterion. Written down so another engineer can run it again
Hands on the generator
Each participant configures the profile, starts the run and reads the counters. Our engineer corrects the setup on the spot, so a mistake is seen once
A report the vendor accepts
What goes into the report, how a graph is read, where the limit was reached and what the number means. The team writes the report for its own devices on the last day
Program modules
Four modules, assembled around your devices
The brief decides which modules go in and how many days each takes. A firewall team spends more time on functional tests, a backbone team on load and the traffic profile.
| Module | On the bench | You take away |
|---|---|---|
| 01Load and performance | Throughput, latency and loss with your traffic mix; frame sizes, bursts and long runs | A load test plan for your device class and the limits you measured yourself |
| 02Functional and conformance | Protocol behaviour against the standard and the tender: failover, convergence, policy checks | A checklist of cases with pass criteria, reusable on the next firmware |
| 03Traffic profiles and test plans | From NetFlow and counters of your network to a generator profile; a plan written in the group | The profile and the plan for your network, ready for the next acceptance |
| 04Reporting | Reading graphs, finding the limit, separating a device fault from a test setup error | A report template and the first report, written by the team on the last day |
Module set, days per module and the device list are agreed per program at the brief
Format
Short, on real hardware, for your team only
No mixed groups and no demo rigs. The bench is ours, the devices under test are yours or from the lab stock, the generator is loaded to the limit of the device
- 2–5 days
- per program, set at the brief
- Online or on site
- remote access to the CloudLAB bench, or in your lab
- Your team
- one company per group, your devices and your tasks
How it runs
From the brief to your own bench in four steps
-
1
Brief
One callYou name the devices, the tasks of the year and the level of the group. We ask what the last test did not answer
Out: module list and dates
-
2
Program
Built for your devicesWe write the exercises on your device class and your traffic profile, with pass criteria, and send them for review
Out: program and bench schedule
-
3
Bench days
2–5 daysShort theory, long practice. Each exercise ends with a measured number and a discussion of what it means for the device
Out: results of every exercise
-
4
Materials
Repeat on your own benchConfigurations, profiles, test plans and the report template stay with the team and run on your own tools
Out: a set the team runs on its own
Typical scenario
An operator's team before a tender
Four engineers of an operator are to accept new edge routers in two months. The tender lists an RFC 2544 clause and three protocol checks; the team has a generator and has used it twice. Four days: one on the traffic profile from their own NetFlow, two on the bench with a router of the same class, one on the plan and the report. The acceptance then runs on their bench with their plan, we review the report.
- 4 days
- profile, bench, plan and report
- 4 modules
- profile, load, functional, reporting
- 1 review
- of the first acceptance report
Composite scenario from programs of this type. No client is named, the day count is illustrative
FAQ
Questions before the first call
Who is the program for?
Test and network engineers who will run acceptance or lab tests themselves: operator planning and NOC teams, enterprise network teams, QA of vendors and integrators. The level is set at the brief, from a first generator session to a method review for an experienced team.
Which devices and generators are used?
Your devices if you ship them to the lab or host the course, otherwise devices of the same class from the lab stock. The generator is the lab's own instrument; the course teaches the method, and the method transfers to any tool.
Can it run on site?
Yes. On site the group works on your tools and your devices; we bring the program, the profiles and the exercises. Online, the group gets remote access to the CloudLAB bench for the days of the course.
What does the team have at the end?
The exercises with results, the traffic profile of your network, a test plan for your device class, the report template and the first report written by the group. All of it in formats you can edit.
How is the price set?
By the number of days and modules, agreed after the brief. The quote comes together with the program draft.
Tell us the devices and the tender date
The program draft and the dates of the bench days come after one call
Send the shortlist
Who needs the training
Team size, device classes and the tests your engineers should run on their own. An engineer replies within one business day with a draft program and the day count.
Prefer to chat? Message an engineer on WhatsApp
We use what you send only to answer you. See our Privacy Policy.