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

concurrent connection graph for checkpoint firewalls

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Community Edition, Professional Edition
    • Web Interface
    • None

    Description

      For Checkpoint firewalls the concurrent connection graph is missing - it was there in the older versions (2017) but disappeared in the GUI, but is still collected when polling.

      I recently opened OBS-3508 which was closed but not solved, i don't know how to re-open and my comment was not answered, so im creating a new one.

      Please check the attached files, the poller gatheres the OID's, but the graph is not generated.
      This are the two ones which are missing:
      fwPeakNumConn - 1.3.6.1.4.1.2620.1.1.25.4
      fwNumConn - 1.3.6.1.4.1.2620.1.1.25.3

      There are also additional ones collected on the poller run which would be of interest if you could graph them:
      fwPacketsRate.0 = 14575756610
      fwAcceptedBytesTotalRate.0 = 10494335964519
      fwDroppedBytesTotalRate.0 = 1803492671
      fwDroppedTotalRate.0 = 24280746
      fwAccepted.0 = 2237564854
      fwRejected.0 = 3974
      fwDropped.0 = 24147507
      fwLogged.0 = 154468814

      Thanks,
      Alex

      Attachments

        Issue Links

          Activity

            [OBS-3559] concurrent connection graph for checkpoint firewalls

            Thanks Adam

            ajoelly.magna Alexander Joelly added a comment - Thanks Adam

            I've rewritten the definitions using the current state of the checkpoint MIB. The graphs should reappear now.

            If you get draw errors, you might need to remove the RRD file, but since it's been broken for a long time, probably not.

            The change is in r10872

            adama Adam Armstrong added a comment - I've rewritten the definitions using the current state of the checkpoint MIB. The graphs should reappear now. If you get draw errors, you might need to remove the RRD file, but since it's been broken for a long time, probably not. The change is in r10872
            adama Adam Armstrong added a comment - - edited

            It seems this is because Checkpoint changed their MIB and removed/renamed a bunch of OIDs, breaking our code that collects this data.

            Classic vendor nonsense.

            adama Adam Armstrong added a comment - - edited It seems this is because Checkpoint changed their MIB and removed/renamed a bunch of OIDs, breaking our code that collects this data. Classic vendor nonsense.

            People

              adama Adam Armstrong
              ajoelly.magna Alexander Joelly
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: