The COSMOS O-RUs are shared instruments. A commercial O-RU keeps whatever the last user wrote into
it, and the next user's DU fails silently on a radio that looks healthy. If you change an O-RU's
configuration, you must put it back to its known (golden) configuration before you leave. This
page shows how, with one command from the cosmos-oru-tools package, and how to check that it
worked.
The rule: you may change an O-RU's configuration only if you leave it as found. Run
cosmos-oru diffbefore you start and after you finish, andcosmos-oru resetto restore it.
O-RU firmware changes are not done by users. They need a request to the testbed administrators
(sysadmins), who perform them.
Every O-RU on the fabric has one golden per software stack: a full capture of the O-RU's stored
configuration, registers and M-Plane mode, taken when that stack was declared working on it. The
golden is the "known configuration". cosmos-oru compares the live O-RU with a golden (diff), and
writes the golden back (reset), including the power cycle that some settings need.
| O-RU | cosmos-oru name |
Goldens (stacks) | Supported |
|---|---|---|---|
| LiteOn FlexFi | liteon |
ocudu, duranta, amarisoft, bubbleran, aerial |
yes |
| Benetel RAN650 | benetel |
ocudu, duranta, aerial, aerial-3ru |
yes |
| Foxconn RPQN-7801 | foxconn |
ocudu |
not yet: ask the testbed administrators |
Use the golden of the stack your DU is closest to. A user running an OCUDU image uses ocudu. A
user running an OAI or Duranta image uses duranta (on the Benetel this also selects M-Plane
mode, see below).
cosmos-oru runs there as root.cosmos-oru-tools package on that host. The COSMOS 5G images (ocudu.ndz, duranta.ndz)apt-get update && apt-get install cosmos-oru-tools
(from apt.cosmos-lab.org, suite noble; every COSMOS image has this repository configured)./etc/cosmos/oru-credentials. Copy them to your node's/run/cosmos (a RAM disk, cleared at the next reboot) from the console:cosmos-oru-creds-push srv19.osc.cosmos-lab.org
On the DU host:
cosmos-oru list
cosmos-oru status benetel
cosmos-oru diff benetel ocudu
Real output (srv1-lg1.sb1, 2026-11-19, just after a Duranta run had left the Benetel in its own
state):
liteon LiteOn FlexFi mgmt <address> goldens: aerial, amarisoft, bubbleran, duranta, ocudu
benetel Benetel RAN650 mgmt <address>,<address> goldens: aerial, aerial-3ru, duranta, ocudu
foxconn Foxconn RPQN mgmt - goldens: ocudu (not supported yet)
Benetel RAN650: answers ping on <address>
reservation : #191 <user> n78 3350.010 MHz / 100 MHz until 2026-11-24T01:00:00Z
TXMeanPower : No signal.
DRIFT cfg compression want dynamic_compressed have static_compressed
DRIFT cfg mimo_mode want 1_2_3_4_4x2 have 1_2_3_4_4x4
DRIFT cfg tdd_pattern_1 want DDDDDDDSUU have DDDSU
DRIFT cfg tdd_pattern_2 want DDDDDDDSUU have DDDSU
DRIFT reg C032A want 0x3 have 0xf
DRIFT reg C0350 want 0x1 have 0x0
DRIFT file tdd.xml want 0f8ba3f098ea99d6a744c7187edeef25 have 6a8139f4e8c2c93d213f35d11a66929b
Every DRIFT line is a value that differs from the golden: want is the golden's, have is the
O-RU's. Here the Benetel holds Duranta's settings, so an OCUDU DU started now would get a radio with
the wrong compression, MIMO mode and TDD pattern. diff is read-only; it changes nothing. Its exit
status is 0 when the O-RU matches and 1 when it drifts.
reset restores on the channel of your O-RU reservation, not the golden's own channel. In
cosmos-oru-tools 1.16, diff still compares against the golden's channel, so after a good reset it
can show one centre_frequency_hz (or bandwidth) line whose have is your booked channel: that line
is expected. The next release compares diff on the reserved channel too.
Save the first diff output: it is the state you have to leave behind if you found the O-RU in a
state other than a golden.
cosmos-oru reset benetel ocudu
reset does, in order:
--center-freq <MHz> --bandwidth <MHz> override it;ocudu: standalone, duranta: M-Plane).It ends with a line that starts [cosmos-oru] READY: naming the O-RU, the stack and the channel. Any
other ending (do NOT start the DU, a timeout) means the restore did not complete: read the message,
fix the cause, and run reset again.
reset needs to power the O-RU. Power works only from the console of the domain your O-RU
reservation is tied to, with the reservation active. A reservation tied to osc is powered from
console.osc.cosmos-lab.org, one tied to rrail from console.rrail.cosmos-lab.org. If omf is not
on your DU host (the usual case), reset prints the exact command, waits while you run it on that
console, and confirms the result by ping:
omf tell -a offh -t benetel-oru.instrument.orbit-lab.org
omf tell -a on -t benetel-oru.instrument.orbit-lab.org
A console that is not your reservation's refuses and names the right one, for example
Your reservation drives benetel-oru from rrail.
cosmos-oru diff benetel ocudu ; echo "exit $?"
cosmos-oru status benetel
Done means:
diff prints no DRIFT lines and exits 0 (with 1.16: at most the one channel line of Step 1, exit 1);status shows the O-RU answering ping (LiteOn: SYNCHRONIZED and RF ready);Then power the O-RU off from your reservation's console, unless the next user asked you to leave it on.
| O-RU | Trap | What to do |
|---|---|---|
| LiteOn | Never hand-write its persistent keys, and never use its "reset to default". A factory reset puts it on a factory static IP address that the fabric cannot reach | Use only cosmos-oru reset. If it stops answering after a change, ask the testbed administrators |
| LiteOn | An O-RU that boots while a DU streams fronthaul at it may never synchronise | Stop your DU before reset; reset warns when it sees a DU |
| Benetel | Switching between M-Plane and standalone mode reboots the O-RU | Expected. reset waits for it |
| Benetel | In M-Plane mode (Duranta) the DU writes registers after it starts, so a diff taken while the DU runs shows reg drift |
Diff with the DU stopped, or against the golden of the stack that is running |
| Both | Jumbo frames on the O-RU's fronthaul port are part of the golden | reset re-applies them; do not change the MTU by hand |
| Both | diff exit 1 right after a change you made on purpose is normal |
It tells you what to restore. Restore before you leave |
| Foxconn | No golden tooling yet | Do not change its configuration; ask the testbed administrators |
READY after two reset runs.Write to the COSMOS support address on the portal with the O-RU,
your reservation number, and the cosmos-oru diff / reset output.
| Symptom | Cause | Fix |
|---|---|---|
cosmos-oru: unknown O-RU |
a typo, or an old package | cosmos-oru list; apt-get install --only-upgrade cosmos-oru-tools |
no golden for <oru> with <stack> |
that stack has never been declared working on that O-RU | use the nearest stack's golden, or ask the administrators |
| login or key errors | the O-RU logins are not on the node (or the node rebooted: /run is cleared) |
cosmos-oru-creds-push <node> on the console |
a DU is ALREADY sending fronthaul |
your DU, or one somebody left running | stop yours; otherwise ask the administrators. Never pass --allow-streaming-du for someone else's DU |
| the power prompt never completes | the command was run on the wrong console, or the reservation ended | run it on your O-RU reservation's console; check the reservation |
WARNING: no active reservation |
no active O-RU booking | book it; without one the golden's own channel is used |
Author(s): COSMOS team · Last verified: 2026-11-19 (list, status and diff run on srv1-lg1.sb1; reset as run by the COSMOS tutorials) · Tested image/release: cosmos-oru-tools 1.16 · Tags: oran, o-ru, golden, cosmos-oru, benetel, liteon