Discovery and reconciliation
Discovery and reconciliation
Section titled “Discovery and reconciliation”When a gateway-enabled GNE is collected, rConfig discovers the RNEs behind it and keeps the set of RNE devices in step with what the GNE reports. You do not maintain the list by hand.
What runs, and when
Section titled “What runs, and when”Discovery happens at the end of every GNE collection, gated by the tl1Gateway flag on the template (setup):
- rConfig collects the GNE’s own configuration over its session.
- On the same session it runs the neighbour command (
RTRV-NBR:ALLby default) and parses the reachable RNE TIDs. - It reconciles those TIDs against the RNE devices already linked to this GNE.
To trigger it, collect the GNE: open the device and click Download Now, or let its scheduled task run.
Reconciliation states
Section titled “Reconciliation states”Each RNE carries a discovery state, shown in the TL1 Gateway panel on both the GNE and the RNE:
| State | Meaning |
|---|---|
discovered | The GNE reported this RNE on the last discovery. |
missing | The RNE was present before but the GNE no longer reports it (removed, renamed, or unreachable). The device and its history are kept, not deleted. |
manual | The RNE device was created by an operator rather than by discovery. |
A missing RNE flips back to discovered automatically the next time the GNE reports it again.
Discovered RNEs on a GNE, with one flagged missing
New RNEs are collected automatically
Section titled “New RNEs are collected automatically”When discovery finds an RNE for the first time, rConfig creates the device and queues a first collection for it straight away, routed through the GNE. Re-running discovery does not re-collect RNEs it already knows, so a GNE with a large fleet is not re-pulled on every run. After the first pull, each RNE follows its own schedule like any other device.
A standalone GNE (one whose RTRV-NBR returns no neighbours) simply creates no RNEs. Discovery still runs; it just finds nothing.
Next step: Collect the RNEs.