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

Support for Juniper Virtual Chassis Ports

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Juniper's EX and QFX switches stack together over Virtual Chassis Ports (VCP).
      Juniper have decided that only the master switch's VCP ports get exposed through the standard ifEntry MIB.

      To get the statistics from all the other VCP ports in the stack you need to poll - juniper/JUNIPER-VIRTUALCHASSIS-MIB

      If it were possible to poll this MIB and expose the interfaces in Observium, then that would be great!

      Many thanks.

      Attachments

        1. discovery_debug.log
          618 kB
        2. poll_debug.log
          1.01 MB

        Issue Links

          is mentioned by

          Improvement - An improvement or enhancement to an existing feature or task. OBS-3945 Juniper VCP ports not exposed even after

          • Major - Major loss of function.
          • Pending Response
          relates to

          New Feature - A new feature of the product, which has yet to be developed. OBS-3928 Juniper switch/firewall alert not working for VC ports /Cluster failure

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Review

          Activity

            [OBS-2049] Support for Juniper Virtual Chassis Ports
            landy Mike Stupalov added a comment -

            Support improved in r10853.

            landy Mike Stupalov added a comment - Support improved in r10853.
            mcujba Maxim Cujba added a comment -

            Hello Mike,

             

            I collect requested information.

            1. full snmp dump from device - file myagent.snmpwalk
            2. discovery debug log - file discovery_debug.log
            3. poller debug log - file poll_debug.log

            This is link to vendor MIBs https://www.juniper.net/documentation/software/index_mibs.html

             

            –

            Best regards,

            Maxim

            mcujba Maxim Cujba added a comment - Hello Mike,   I collect requested information. full snmp dump from device - file myagent.snmpwalk discovery debug log - file discovery_debug.log poller debug log - file poll_debug.log This is link to vendor MIBs https://www.juniper.net/documentation/software/index_mibs.html   – Best regards, Maxim
            landy Mike Stupalov 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
            landy Mike Stupalov 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
            mcujba Maxim Cujba added a comment -

            Hello,

             

            Confirm.

            I also have same problem. Observium no detect model for juniper devices. It do not activate corect mibs(ex. mibs/juniper/JUNIPER-CHASSIS-CLUSTER-MIB)

             

            Best regards,

            Maxim

            mcujba Maxim Cujba added a comment - Hello,   Confirm. I also have same problem. Observium no detect model for juniper devices. It do not activate corect mibs(ex. mibs/juniper/JUNIPER-CHASSIS-CLUSTER-MIB)   Best regards, Maxim
            pmcossey Pierre-Marie COSSEY added a comment -

            Hello

            To complete this request, could it be possible (with the same MIB) to display virtual-chassis global informations (model, role and status of each member). We currently face a stack of 6 switches with a missing member and no way to easily detect this defect.

             Thanks for your work.

             Regards

             PM

            pmcossey Pierre-Marie COSSEY added a comment - Hello To complete this request, could it be possible (with the same MIB) to display virtual-chassis global informations (model, role and status of each member). We currently face a stack of 6 switches with a missing member and no way to easily detect this defect.  Thanks for your work.  Regards  PM

            People

              landy Mike Stupalov
              thomasn Thomas Nicholson
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: