Hello All,
In my current project I have to manage Huawei RAN BBu, however all my experience is on Ericsson RAN BBU. As a fresher into Huawei RAN what all things I have to start with, preferably must known commands. Please let me know
Hello All,
In my current project I have to manage Huawei RAN BBu, however all my experience is on Ericsson RAN BBU. As a fresher into Huawei RAN what all things I have to start with, preferably must known commands. Please let me know
Coming from Ericsson, the fastest way in is to map the verbs — the object-model idea is the same, only the syntax and names change.
Syntax model: Huawei MML is verb + object : KEY=VALUE, comma-separated, semicolon-terminated. Example: DSP CELL: LocalCellId=0; Read with DSP/LST (no rights needed), change with MOD/ADD/RMV.
Verb map from Ericsson (moshell/AMOS):
Must-know starter set:
Three things different from Ericsson:
Ready reference on the same forum with the everyday troubleshooting commands and screenshots: “Routine Troubleshooting MML Commands in Huawei” (topic 30905). Start there, then keep the MML Command Reference for your exact BBU version open alongside — command availability tracks the version (V100R0xx).
Thank you. How can I compare cabinet, subrack, slot no of Huawei with Ericsson? In Ericsson we usually connect TX and cpri to BBU, however in Huawei we will connect TX to one card of BBU and CPRI to another card of same BBU?
Two different addressing models, so there’s no clean 1:1 map. Huawei addresses every board by a three-part physical coordinate — Cabinet No (CN) + Subrack No (SRN) + Slot No (SN) — and every MML command and cabling reference uses that triplet, e.g. DSP BRD: CN=0, SRN=0, SN=x;. Ericsson modern Baseband is a single integrated unit addressed by the FRU/board and its port, so it has no direct CN/SRN/SN equivalent; the Huawei model is more explicit about physical position.
On your TX-vs-CPRI observation — architecturally you’re right, and it’s the core difference. Huawei splits the functions across separate boards in the same BBU subrack: the main control + transmission board carries the backhaul TX (transport/IP ports), and the baseband board carries the CPRI/fronthaul to the RRU/AAU. So backhaul and CPRI land on two different cards of the same BBU. Ericsson integrates main control, transport and baseband into one Baseband unit, so both terminate on the same board — that’s the contrast you’re seeing.
DSP BRD:;
That lists every board with its CN/SRN/SN and board type, so you can see precisely which slot is the control/transmission board (where TX terminates) and which is the baseband board (where CPRI terminates) on your BBU.
Tell me your BBU model (BBU3900 / BBU3910 / BBU5900) and paste the DSP BRD output, and I’ll map each slot to its Ericsson-equivalent function and confirm the TX vs CPRI board split for your exact configuration.
BBU5900 is used
Display Board
-------------
Cabinet No. Subrack No. Slot No. Config Type SubBoard Type Administrative State Standby Status Operational State Alarm Status Availability Status WorkMode
0 0 1 UBBP NULL Unblocked NULL Enabled Normal Normal NULL
0 0 2 UBBP NULL Unblocked NULL Enabled Normal Normal NULL
0 0 7 UMPT NULL NULL Active Enabled Normal Normal NORMAL
0 0 16 FAN NULL NULL NULL Enabled Normal Normal NULL
0 0 19 UPEU NULL NULL NULL Enabled Normal Normal NULL
0 60 0 MRRU NULL Unblocked NULL Enabled Normal Normal NULL
0 80 0 MRRU NULL Unblocked NULL Enabled Normal Normal NULL
0 200 0 MRRU NULL Unblocked NULL Enabled Normal Normal NULL
(Number of results = 8)
Mapped to your DSP BRD, BBU5900. Cabinet 0, main subrack 0:
Slot 7 — UMPT (Main Processing & Transmission): control + backhaul TX terminates here. This is where your Ericsson “TX to BBU” cable lands. Ethernet/transport ports (and GPS/clock) are on this board. Active per the dump.
Slots 1 and 2 — UBBP (BaseBand Processing): CPRI/fronthaul to the radios terminates here. This is where your Ericsson “CPRI to BBU” lands — but on a different board than TX, which is exactly the split you asked about. Two UBBPs = baseband capacity across the radios.
Slot 16 — FAN. Slot 19 — UPEU (power + external alarm/E1 interface). Infrastructure, no TX or CPRI.
So the Ericsson-vs-Huawei answer you were after, confirmed on your own hardware: TX → UMPT (slot 7), CPRI → UBBP (slot 1/2). Two separate boards in the same BBU5900 subrack. Ericsson integrates both onto one Baseband; Huawei separates control/transport (UMPT) from baseband (UBBP).
The MRRUs are your radios, addressed as separate subracks (SRN 60 / 80 / 200, slot 0 each), not boards inside the BBU — that subrack-number-per-radio scheme is how Huawei references the RRU in cabling and in CPRI-port config, versus the BBU boards which all sit in SRN 0.
To see which UBBP CPRI port each MRRU is wired to (the fronthaul topology), run:
DSP BRD:; (already have it) LST RRUCHAIN:;
LST RRUCHAIN gives the CPRI chain/ring/star mapping — which UBBP slot+port each MRRU hangs off, and whether any are daisy-chained. That’s the piece that completes the physical picture for troubleshooting CPRI or planning capacity.
In Ericsson we have CPRI port A,B,C,D etc and we can see data 1 and data 2 of RRU connected to which cpri port of BBU using command hget^rilink. I have given LST RRU chain for Huawei for the same above node, can you please tell me to which port of UBBP cpri connected?
List RRUCHAIN Configure Information
-----------------------------------
Chain No. Topo Type Backup Mode Head Cabinet No. Head Subrack No. Head Slot No. Head Port No. Head SubPort No. Tail Cabinet No. Tail Subrack No. Tail Slot No. Tail Port No. Tail SubPort No. BreakPoint Position1 BreakPoint Position2 Access Type CPRI Line Rate(Gbit/s) Local Cabinet No. Local Subrack No. Local Slot No. Protocol Type Severely Errored Second Threshold User-Defined Rate Negotiation Switch Bit Rate Set(Gbit/s) Rate Change Period(s) Reserved Bandwidth
1 CHAIN COLD 0 0 1 0 0 NULL NULL NULL NULL NULL Invalid Invalid local port Auto 255 255 255 DEFAULT 1E-6 OFF 1.25:YES&2.5:YES&3.0:YES&4.9:YES&6.1:YES&9.8:YES&10.1:YES 1 NULL
2 CHAIN COLD 0 0 2 2 0 NULL NULL NULL NULL NULL Invalid Invalid local port Auto 255 255 255 DEFAULT 1E-6 OFF 1.25:YES&2.5:YES&3.0:YES&4.9:YES&6.1:YES&9.8:YES&10.1:YES 1 NULL
3 CHAIN COLD 0 0 2 3 0 NULL NULL NULL NULL NULL Invalid Invalid local port Auto 255 255 255 DEFAULT 1E-6 OFF 1.25:YES&2.5:YES&3.0:YES&4.9:YES&6.1:YES&9.8:YES&10.1:YES 1 NULL
(Number of results = 3)