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

Sophos Firewall SNMP OID for IPsec tunnel status

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • OS

    Description

      Hello,

      Is it possible to extend the OIDs added to Observium so far to include those for monitoring IPsec tunnels for Sophos Firewall?

      I am sending the official Sophos article on the subject and the OIDs included in it:

      • sfosIPSecVpnConnStatus: Connection status of IPsec tunnel
        • oid: .1.3.6.1.4.1.2604.5.1.6.1.1.1.1.9
        • {}inactive: 0
        • active: 1
        • partially-active: 2 
      • sfosIPSecVpnActivated: Activation status of IPsec tunnel
        • oid: .1.3.6.1.4.1.2604.5.1.6.1.1.1.1.10
        • inactive: 0
        • active: 1

      https://support.sophos.com/support/s/article/KBA-000010117?language=en_US

       

      If you need anything let me know

       

      Attachments

        Activity

          [OBS-4980] Sophos Firewall SNMP OID for IPsec tunnel status
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            helpdeskclip Helpdesk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: