Skip to content
NetSense Docs

Genexis Saturn and Mars OLTs

Genexis GPON OLTs (Saturn SOLT33-08P / SOLT33-16P and Mars MOLT33-08P) poll over SNMP like any other OLT, but their syslog side has a trap that costs most deployments their ONU down reasons: the platform has two separate logging subsystems, and the one carrying ONU events is off by default.

The trap: logging is not ont-logging

Section titled “The trap: logging is not ont-logging”

The CLI has two independent log paths:

  • logging carries the general system log: logins, config commands, link up/down.
  • ont-logging carries the ONU/ONT events: online, offline, and the down reason.

Configuring only logging <server> looks like working syslog, general events arrive and the Syslog tab is not empty, but no ONU events ever reach NetSense. The symptom one level up: down ONUs on these OLTs show only SNMP Check as the reason, never Power Off or Optical Loss, because the events that carry the reason stay in a local buffer on the OLT.

The config

Section titled “The config”

On every Saturn/Mars OLT, both subsystems point at your NetSense agent:

ont-logging timestamps datetime
ont-logging <agent-ip>          ! forwards ONU/ONT events to NetSense
logging <agent-ip>              ! general system log
logging facility system

The tell when you inspect an existing config: logging buffered means the general log is flowing, but ont-logging buffer all means ONU events go to the local buffer only; the ont-logging <agent-ip> line is what pushes them to the server.

This is a per-OLT setting: apply it on every Saturn/Mars unit in the fleet, not just the first one you test.

What you should see

Section titled “What you should see”

Within moments of applying the config, ONU events appear in the device’s Syslog tab in NetSense as %ONTMNT-5-ONT-LOG lines carrying the PON port, the ONU, the state change and the reason:

Genexis Saturn OLT Syslog tab in NetSense showing ONTMNT ONU event lines: offline with reason POWER_OFF, LOSI and LOAMI, and matching online events

Reading the reasons:

Reason in the event Meaning
POWER_OFF The ONU lost power and sent a dying gasp: subscriber-side power issue.
LOSI Loss of signal: the optical path to the ONU is broken (fiber, connector, splitter).
LOAMI Loss of management channel: the ONU stopped answering OMCI, often a reboot or a flapping link.

With these flowing, NetSense’s real-time ONU status, down-reason classification and Partial PON detection all work on the Genexis fleet exactly as on other vendors.

Verify with a test ONU

Section titled “Verify with a test ONU”

Same procedure as on any OLT platform: power one test ONU off at the adapter and expect an offline, reason: POWER_OFF event within moments, then power it on, let it come online and pull its fiber, expecting LOSI. Both should land in the Syslog tab as they happen.

Section titled “Related”
  • General syslog setup, the source-IP rule and delivery troubleshooting: Sending device syslog to NetSense
  • Genexis ONTs (Earth/Titanium CPE line) are a separate topic from these OLTs; their serials carry the GNXS prefix you will see in the event log when Genexis ONUs sit under the OLT.