To run your own 5G stack against a COSMOS O-RU you need two reservations: a fronthaul server
that will run your O-DU, and the O-RU itself. The server reservation comes first; the O-RU
booking hangs off it. This page lists the servers that can drive an O-RU and walks through both
bookings.
The O-RUs sit on one shared fronthaul fabric (O-RAN 7.2: eCPRI U/C-plane on VLAN 4, M-Plane and
PTP on VLAN 5). Only servers wired into that fabric, with a PTP-capable NIC, can run an O-DU against
them. Booking an O-RU moves its fronthaul onto your domain for the length of the booking: the same
radio, wherever your server is.
| Order | What | Where |
|---|---|---|
| 1 | The fronthaul server (the "parent" reservation) | the domain's scheduler (see the table below) |
| 2 | The O-RU, on a band, centre frequency and bandwidth | the O-RU scheduler |
| Domain | Servers | Notes |
|---|---|---|
| osc | srv6.osc, srv7.osc, srv17.osc, srv18.osc, srv19.osc, srv20.osc |
open-software community: osc group only (special permission); per server, one day per reservation |
| rrail | srv6.rrail, srv7.rrail |
public with restrictions: anyone, per server, 30 min to 6 h per reservation (srv7 is booked with the bubbleran group: srv1-4 + srv7) |
| rrail | srv8.rrail, srv9.rrail |
NVIDIA GH200 (arm64) with the Aerial L1; anyone, per server, 30 min to 6 h |
| sb1 | srv1-lg1.sb1, srv2-lg1.sb1, sdr1-in3.sb1 |
fully public: any user with an sb1 reservation |
All x86 fronthaul servers have an Intel E810 NIC for the fronthaul. Prepare the host before your O-DU
runs (CPU isolation, hugepages, PTP): see
real-time host preparation. Who may use
which domain is on O-RAN domains, groups and privileges.
srv6, srv8, srv9, and the bubbleran group =srv1-4 + srv7) for 30 min to 6 h per reservation.Both rrail and osc are reserved per server, not as a whole domain. On rrail one reservation
lasts 30 min to 6 h; on osc one reservation is a whole day. On both you can book consecutive slots
(several rrail slots, or several osc days in a row); the scheduler's conflict resolution decides when
other users' requests compete for the same server.
In the O-RU scheduler:
One O-RU per RF space. The Benetel RAN650 and the LiteOn FlexFi share one RF space. Both may
be on at once only on non-overlapping channels, which the scheduler enforces. All COSMOS O-RUs and
UEs are within a few metres of each other: two cells on one channel interfere.
The Benetel RAN650, the LiteOn FlexFi and the Foxconn RPQN can be booked by anyone, into sb1 or rrail
(osc members also into osc). Whoever holds the booking powers the O-RU, from the console of the
booking's domain. Additional O-RUs are available to rrail and osc group members. The scheduler powers
the O-RU off at the end of your booking.
The O-RU booking's target domain decides which console powers it. Tie the booking to osc to power
it from console.osc.cosmos-lab.org; tie it to rrail to power it from console.rrail.cosmos-lab.org;
to sb1 for console.sb1.cosmos-lab.org. With the booking active, on that console:
omf tell -a on -t liteon-oru.instrument.orbit-lab.org
omf tell -a offh -t liteon-oru.instrument.orbit-lab.org
The Benetel (benetel-oru.instrument.orbit-lab.org) and the Foxconn are powered the same way. Use the full *.instrument.orbit-lab.org name, without -d. Any other console refuses and names
the right one, for example Your reservation drives benetel-oru from rrail. Confirm the result by
pinging the O-RU from your server, not by the reply.
cosmos-oru diff before and after, andcosmos-oru reset to restore it: see| Symptom | Cause | Fix |
|---|---|---|
| The O-RU scheduler does not offer an O-RU | some O-RUs are for rrail and osc group members | see the groups page |
| Booking refused: overlapping spectrum | another booking in the same RF space covers your channel | pick a non-overlapping channel or another time |
omf tell refused for the O-RU |
wrong console, or the booking is not active now | use the console of the booking's target domain |
| The O-RU is off at the start of your slot | the previous booking ended (power off at end) | power it on from your console |
Author(s): COSMOS team · Last verified: 2026-11-19 (scheduler rules from the testbed configuration; O-RU power from console.rrail tested 2026-11-19) · Tags: oran, o-ru, reservation, scheduler, fronthaul