Huawei MAE-Access Deep Dive: 5G Workflow for Operations Engineers

What MAE-Access actually replaces

Huawei rebranded U2020 to MAE-Access (Mobile Automation Engine for Access) several releases ago, but in most operator NOCs the old name still gets used. MAE-Access is the element manager for Huawei RAN — 4G eNodeB, 5G gNodeB (BBU 5900 series with AAU 5613/5639/etc.), and the integrated MetaAAU radios. It sits alongside MAE-Deployment (provisioning) and MAE-Optimization (SON-style automation), and increasingly under iMaster MAE as the umbrella product.

This is a working-engineer view: how to do alarm work, performance analysis, and configuration audits in MAE-Access without getting lost in the menu tree.

The four panes you will live in

Most daily work is alarms and PM. Configuration is touched only for changes or audits.

Alarm management workflow

Filtering for what matters

The out-of-the-box alarm list is overwhelming. Build saved filters:

• Severity = Critical or Major
• NE Type = gNodeB
• Alarm category = Equipment Fault, Communication Alarm, Quality of Service
• Cleared = No

MAE-Access supports alarm correlation rules — when a parent alarm (e.g., "S1/N2 link broken") clears its dependent alarms ("Cell unavailable"), the latter are auto-suppressed. Verify the correlation rule set is enabled; some operators disable it during migrations and forget to re-enable.

Common 5G alarms and what they mean

The ID numbers are stable across recent SRAN releases (SRAN 19.x and later).

Drill-down from alarm to cause

1. Right-click alarm -> "Locate to NE" — opens NE in topology.
2. Right-click again -> "Browse Performance Data" — pulls the most relevant counters for that alarm category.
3. Open MML console -> DSP CELL to confirm cell state.
4. Open MML -> LST NRCELL to verify configuration matches expectation.

Performance management

Counter queries

The PM query interface is template-based. Build templates per use case:

• 5G accessibility (CSSR breakdown)
• 5G mobility (HOSR per pair)
• 5G throughput and PRB usage
• 5G coverage (RSRP/SINR distributions)

Huawei counter naming follows N.<Domain>.<Metric> for 5G NR, e.g., N.RRC.ConnReq.Att, N.RRC.ConnReq.Succ, N.User.PdcpSdu.DL.Vol. The full reference is in the SRAN PM Counter Reference document for your specific software baseline.

Useful 5G counter set

KPI formulas

5G CSSR = (N.RRC.ConnReq.Succ / N.RRC.ConnReq.Att)
        * (N.NgSig.ConnEst.Succ / N.NgSig.ConnEst.Att)
        * (N.PDUSession.SetupReq.Succ / N.PDUSession.SetupReq.Att)

ERAB Drop Rate = N.ERAB.AbnormRel / (N.ERAB.NormRel + N.ERAB.AbnormRel)

DL PRB Utilization = N.PRB.DL.Used.Avg / N.PRB.DL.Avail

Configuration workflow

MML console

MAE-Access exposes the MML console per NE. Common 5G commands:

LST NRCELL:                       # list all NR cells on this gNB
LST NRCELL: NrCellId=1;
DSP CELL: LocalCellId=1;          # dynamic cell state
MOD NRCELL: NrCellId=1, ...;      # modify cell parameters
ACT NRCELL: NrCellId=1;           # activate (unblock) a cell
DEA NRCELL: NrCellId=1;           # deactivate (block)
LST NRDUCELL:                     # DU-side cell config
LST NRCELLALGOSWITCH: NrCellId=1; # algorithm switches
LST GNBCUUP:                      # CU-UP user plane config

Huawei MML is verb-first (LST, MOD, ADD, RMV, ACT, DEA, DSP, STR, STP). Parameters are key=value pairs separated by commas, ended with semicolon.

Bulk configuration

For multi-NE changes, use the Bulk Configuration tool inside MAE-Access. Workflow:

1. Export current configuration as XML for affected NEs.
2. Modify XML (script, spreadsheet template, etc.).
3. Validate offline with the configuration validation tool.
4. Import preview, then commit.

Never commit without preview. The validation tool catches schema errors but not semantic errors (e.g., a PCI conflict).

Configuration audit

MAE-Access has a configuration audit feature comparing current config against a baseline template. Use cases:

• Detect drift after troubleshooting (engineers leaving temporary parameter changes in place)
• Verify a new-site rollout matches the cluster template
• Check that mandatory feature flags (e.g., specific 5G features) are activated consistently

Schedule a weekly audit; review the diff before approving as the new baseline.

Vendor-specific gotchas

> Huawei NRCELL config is split between CU and DU. Changing a parameter on NRCELL (CU-side) does not change NRDUCELL (DU-side). Always check both.

• Algorithm switches are off by default. Many features (e.g., advanced beam management, MU-MIMO pairing) require explicit MOD NRCELLALGOSWITCH activation.
• License-controlled features show as configured but inactive if license is missing — LST LICENSE to verify.
• After a cell modification, run DSP CELL to confirm operational state. The MOD response says "success" even when the cell fails to come back up.
• PM data is collected at 15-min granularity by default; for fault investigation, switch the affected NEs to 5-min granularity temporarily.
• CME (Configuration Management Express) is the offline planning tool; do not confuse it with MAE-Access live configuration.

A short daily routine

1. Critical/Major alarm review (saved filter).
2. Top 20 worst CSSR cells (yesterday).
3. Top 20 worst HOSR cell pairs.
4. New alarms in the last 8 hours not yet acknowledged.
5. Any configuration audit drift.

This takes 30 minutes once you have the templates set up and surfaces 90% of issues before they become tickets.

Takeaway: MAE-Access rewards engineers who build saved filters, PM templates, and audit baselines — without them you are clicking through menus all day.

The Huawei toolchain, without the client

Three parsers take Huawei output directly:

MML parser for commands and their responses,

counter parser for performance exports, and

LTE PCI analyzer for confusion and collision

checks.

For the step after the counters,

dropped calls in gNB logs is the

log-reading version of the same question.