Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-5326

FS.com FSOS NG: PoE, VSU stack health, per-unit naming, DAC DOM fix and LLDP 'OID not increasing' fix

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • None
    • Discovery, OS

    Description

      Summary

      Improvements for FS.com switches running FSOS NG (fsos-ng): PoE (per unit and per port), VSU stack health, per-unit naming of fans, PSUs and temperatures in stacks, bogus DOM sensors removed on DAC cables, and a fix for LLDP walks aborting with "OID not increasing".

      Patch: 05-fscom-fsos-ng.patch (attached). Apply from the Observium root with patch -p1 < 05-fscom-fsos-ng.patch. It was built against trunk SVN BASE and applies cleanly. FS-POE-MIB and FS-VSU-MIB already ship with Observium.

      What it adds / fixes

      • PoE per unit: "Unit N PoE" budget/consumption power and operational status, from POWER-ETHERNET-MIB pethMainPse* (index = stack unit).
      • PoE per port:
        • Consumed power from FS-POE-MIB ifPoeConsumingPwr (mW, index = ifIndex).
        • Status from pethPsePortDetectionStatus. Its index is unit*100 + port, matched to ports through ifDescr U/0/P. Value 0 is skipped, and fault is a warning.
      • VSU stack health (FS-VSU-MIB): topology shape (ring/chain), member device status and role, and VSL port state.
      • Per-unit naming: FS-SYSTEM fan, PSU and temperature descriptions are now "Unit N ...", so entries in a stack are no longer ambiguous.
      • Fan speed: fsSystemFanStatusSpeed gets min = 0. The S3410 always reports 0 rpm, so only fan status is meaningful there.
      • DAC/copper modules: every FS-FIBER-MIB DOM sensor now checks fsFiberTransceiverType notmatch Copper. 10G DAC stack cables reported garbage DDM values (6.553 V, 0.131 A) that created bogus sensors.
      • LLDP "OID not increasing": the FSOS NG agent sometimes returns a non-increasing OID while walking a large LLDP neighbour table. net-snmp then aborts the whole bulkwalk, causing partial LLDP data and eventlog warnings on every column. $config['os']['fsos-ng']['snmp']['noincrease'] = TRUE adds -Cc, exactly as the warning suggests. Bulk performance is kept, unlike disabling bulk.

      Files

      File Status Purpose
      includes/definitions/mibs/fscom.inc.php changed "Unit N" descriptions, fan min 0, FS-POE-MIB states, FS-VSU-MIB status definitions
      includes/definitions/mibs/fscom/fs-fiber-mib.inc.php changed Skip DOM sensors on copper/DAC modules
      includes/definitions/os/fscom.inc.php changed fsos-ng: FS-POE-MIB, FS-VSU-MIB, snmp noincrease
      includes/discovery/sensors/fs-poe-mib.inc.php new PoE per unit and per port (power and status)

      Notes for maintainers

      • Generic POWER-ETHERNET-MIB is not enabled for fsos-ng: its port index (unit*100+port) doesn't map to ifIndex, so values would land on the wrong ports.
      • Per-port PoE limits. When the port has no configured maximum (ifPoeMaxPwrSet unset, 2147483647), the discovery sets fixed limits of warn 12 W / alert 15.4 W (802.3af class 0). Otherwise Observium's automatic limit (value x 1.5) alerts constantly on low-draw devices (a 1.5 W phone gets a 2.25 W limit). If you prefer, these could become config options.

      Testing

      • S3410-48TS-P, FSOS 11.4, three-unit VSU ring.
      • LLDP: -Cc confirmed in the actual snmpbulkwalk command; full neighbour table returned and no new eventlog warnings.
      • php -l clean.

      Attachments

        Activity

          People

            landy Mike Stupalov
            rebeluca Luca Rebellato
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: