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

Alert chechker doesn't find trunk ports.

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • Community Edition
    • Alerting, Ports
    • Cisco devices

    Description

      I would like to create an alert checker which is monitoring special ports when on this ports allowed only 1 VLAN the checker is working properly. But if this port is a trunk port the checker is doesn't find the trunk ports.

      Could you please send me the proper steps how to I create the correct checker which will find trunk ports?

      Attachments

        Activity

          [OBS-3459] Alert chechker doesn't find trunk ports.
          landy Mike Stupalov added a comment -

          Hi Turcsek László, we have not received the additional information requested earlier from you in this issue 'I would like to create an alert checker which is monitoring special ports when on this ports allowed only 1 VLAN the checker is working properly. But if this port is a trunk port the checker is doesn't find the trunk ports.

          Could you please send me the proper steps how to I create the correct checker which will find trunk ports?'!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Turcsek László, we have not received the additional information requested earlier from you in this issue 'I would like to create an alert checker which is monitoring special ports when on this ports allowed only 1 VLAN the checker is working properly. But if this port is a trunk port the checker is doesn't find the trunk ports. Could you please send me the proper steps how to I create the correct checker which will find trunk ports?'! Issues without your response will be closed within 2 weeks.
          bot Observium Bot added a comment -

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -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 Note, this comment is added automatically.

          People

            adama Adam Armstrong
            Turcsek Turcsek László
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: