Ericsson KGET Parser
Paste a KGET configuration dump and explore the managed-object tree, filter attributes, and export to JSON — all in your browser.
KGET (Configuration Get) is Ericsson's plain-text snapshot of a node's entire Managed Object (MO) tree. Every RAN engineer who works with Ericsson ENM, OSS-RC, or AMOS has stared at a KGET dump trying to find one attribute in 50 MB of indented text. This free online KGET parser turns that dump into an interactive, searchable tree: expand a ManagedElement down to each NRCellDU, SectorCarrier, or EUtranCellFDD, filter attributes by name, and export any subtree as JSON. Everything runs in your browser — your config never leaves the page, so it's safe to use with production data. Typical users are Ericsson RAN engineers, integration engineers, network auditors, and anyone debugging a gNodeB MO inconsistency who'd rather click through a tree than grep a file.
KGET Input
Paste the full output of an Ericsson KGET / AMOS 'get .' command. Parsing happens entirely in your browser.
Frequently Asked Questions
What is an Ericsson KGET dump?
KGET is the Ericsson configuration export format produced by AMOS, ENM CLI, or OSS-RC commands like "get ." It is a plain-text representation of every Managed Object (MO) on a node — eNodeB, gNodeB, RBS, or BSC — including all attributes and their current values.
Is the parsed data ever uploaded to a server?
No. Parsing runs entirely in JavaScript inside your browser. Your configuration text is never sent over the network, never logged, and never stored — you can verify this in your browser devtools network tab.
How large a KGET can I paste?
Modern browsers handle multi-megabyte strings comfortably. The parser streams lines and builds a tree in one pass, so 10–50 MB KGETs work on a typical laptop. Very large dumps may take a second or two to render.
Can I export the tree?
Yes. Click "Export JSON" to download the parsed tree as structured JSON that you can feed into Python, Node, or jq for further automation.
How It Works
The parser treats KGET output as an indentation-based hierarchy. Each non-indented line that matches the Name=Instancepattern is a managed object; lines indented below it are the object's attributes. Nested objects are detected by a deeper indent level.
- Attributes are parsed as
name type valuetriples. - Reference, Struct, and Sequence attributes keep their raw text value.
- Use the filter box to show only MOs whose class or attributes match a substring.
- Export JSON to feed the parsed tree into your own scripts.
Master this in our 5G/6G Academy courses
Go beyond the calculator — learn the 3GPP specs, real-world planning trade-offs, and hands-on labs from TELCOMA Global engineers.
How to explore an Ericsson KGET dump
- Run KGET on the node. From the node CLI or your OSS, run the KGET command and capture the full text output.
- Paste the dump. Copy the captured text and paste it into the input box.
- Parse. The tool reads the managed-object instances and their attributes into a collapsible tree.
- Search and expand. Type an MO name or attribute to filter, then expand the branch you care about to read its values.
Frequently asked questions
- What is an Ericsson KGET dump?
- KGET is the command on Ericsson nodes that prints the current managed-object configuration — every MO instance and its attribute values — as a text dump. RAN engineers grab a KGET output to see exactly how a cell, sector or transport object is set up without clicking through the element manager. The dump can run to thousands of lines, which is why a tree view that lets you fold and search it is handy.
- Is my config dump uploaded anywhere?
- No. The parser runs entirely in your browser — the text you paste is processed on your own machine and nothing is sent to a server or stored anywhere. That matters because a KGET dump can carry site names, IP addresses and other details you would not want leaving your network. Close the tab and it is gone.
- Does this work for both LTE and 5G nodes?
- It works on KGET-style dumps from Ericsson radio nodes generally, so eNodeB and gNodeB configs both parse into the same managed-object tree, and BSC dumps too. The tool reads the MO structure rather than assuming a specific RAT, so as long as the output follows the usual KGET layout you can browse it.
Get the next 5G/LTE engineering deep-dive in your inbox
These calculators give you the number — the weekly digest gives you the theory. One technical breakdown every Tuesday, plus first access to new tools. Unsubscribe in one click.
Calculator gave you the answer? Learn the theory in 7 days, free.
Full Pro access — 142+ hands-on exercises, 20+ troubleshooting scenarios, 21 certifications, TelcoMentor AI coach. No credit card. See pricing on /pricing.
- No credit card
- Full Pro access
- 21 verifiable certs
- TELCOMA since 2009