I have an alarm nr cells as below:
Mo configuration exceeds resources enabled by the key
Shortage of nr tdd channels bandwidth 5 mhz cxx4012322
Please guide me
That alarm is a licensing/capacity gate, not a fault. “MO configuration exceeds resources enabled by the key” means the bandwidth you’ve provisioned on the node is more than your installed capacity licence entitles. The second line pins it down: the specific pool short is NR TDD Channel Bandwidth, and it’s short by a 5 MHz increment. So the sum of NR TDD bandwidth you’ve configured across cells exceeds the licensed NR TDD bandwidth capacity on that node.
How to confirm it on the node:
- lt all
- alt → confirm the active alarm and the exact MO raising it
- Check the licensed capacity vs configured usage for the NR TDD bandwidth feature. On Baseband: kget or lkget on the capacity licence keys, and compare “licensed” against “currently used” for the NR TDD bandwidth pool. get . bandwidth on the NRSectorCarrier / NRCellDU MOs shows what you’ve configured per carrier.
You have two ways out:
- Reduce configured bandwidth back within the licence — e.g. drop a carrier or a cell’s bandwidth by the 5 MHz that’s over. The alarm clears immediately once configured <= licensed.
- Add the capacity licence — install the additional NR TDD bandwidth capacity key so the entitlement covers what you’ve configured. This is the correct fix if the extra bandwidth is intended.
Root cause is almost always someone added a carrier / widened bandwidth (or a new cell was defined) without the matching capacity licence installed first. Check what changed on that node recently.
Which Baseband and release are you on, and is this a single cell or the whole node? I can give you the exact kget/licence MO to read on your load.