Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery

    Description

      Is there any way to monitor multiple Fortigate VDOMs? I tried to use distinct hostnames for different vdoms but still get same error in Orion:

      Already got device with SNMP-read sysName (XXXXX) and 'snmpEngineID' = 123456 (XXXXX).

      is there any way to avoid this?

       

      There is a possibility to query every VDOM by its community name:

      • <communityname>-<VDOM1_Name>
      • <communityname>-<VDOM2_Name>
      • <communityname>-<VDOM3_Name>

      .....

      But I cant add vdoms as separate hosts because I get duplicate error

      https://kb.fortinet.com/kb/documentLink.do?externalID=FD45872 

       

      Attachments

        Issue Links

          Activity

            [OBS-3709] Fortigate VDOMs monitoring

            BGP monitoring in VDOM was added some time ago.

            You can try in latest rolling revision.

            landy Mike Stupalov added a comment - BGP monitoring in VDOM was added some time ago. You can try in latest rolling revision.

            Thanks. Do I understand correctly that VDOM information will now appear under main host?

            ppa Petras Paulauskas added a comment - Thanks. Do I understand correctly that VDOM information will now appear under main host?

            Note, added exactly discovery VDOMs on main host. And discovery/polling some specific modules for each VDOM.
            Add separate device for VDOM will not be added.

            landy Mike Stupalov added a comment - Note, added exactly discovery VDOMs on main host. And discovery/polling some specific modules for each VDOM. Add separate device for VDOM will not be added.

            Discovery already added in r11706.

            Additional BGP monitoring in progress..

            landy Mike Stupalov added a comment - Discovery already added in r11706. Additional BGP monitoring in progress..

            Any status on this? We need this function aswell. 

            gmad_invid Gustav Madeland added a comment - Any status on this? We need this function aswell. 

            The information required buy Observium Bot is not needed at this stage of troubleshooting.

            ppa Petras Paulauskas added a comment - The information required buy Observium Bot is not needed at this stage of troubleshooting.

            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

              landy Mike Stupalov
              ppa Petras Paulauskas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: