Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Alerting

    Description

      Regarding the existing case OBS-2049, Support for Juniper Virtual Chassis Ports (Support improved in r10853.)

      • I've upgraded the version to the latest 21.11.11755 (18th November 2021) but not all VCP ports are exposed yet.
      • In addition, some devices "JUNIPER-VIRTUALCHASSIS-MIB" haven't polled at all after the upgrade.
      • Can you please check and update the status?

      Attachments

        Issue Links

          Activity

            [OBS-3945] Juniper VCP ports not exposed even after

            Hi Vignesh, we have not received the additional information requested earlier from you in this issue 'Regarding the existing case OBS-2049, Support for Juniper Virtual Chassis Ports (Support improved in r10853.)

            • I've upgraded the version to the latest 21.11.11755 (18th November 2021) but not all VCP ports are exposed yet.
            • In addition, some devices "JUNIPER-VIRTUALCHASSIS-MIB" haven't polled at all after the upgrade.
            • Can you please check and update the status?'!

            Issues without your response will be closed within 2 weeks.

            landy Mike Stupalov added a comment - Hi Vignesh, we have not received the additional information requested earlier from you in this issue 'Regarding the existing case OBS-2049 , Support for Juniper Virtual Chassis Ports (Support improved in r10853.) I've upgraded the version to the latest 21.11.11755 (18th November 2021) but not all VCP ports are exposed yet. In addition, some devices "JUNIPER-VIRTUALCHASSIS-MIB" haven't polled at all after the upgrade. Can you please check and update the status?'! Issues without your response will be closed within 2 weeks.

            I don't think we current support collecting data from any of these MIBs. 

            Just because something exists in the MIB repository doesn't mean we have added support for it.

            adama Adam Armstrong added a comment - I don't think we current support collecting data from any of these MIBs.  Just because something exists in the MIB repository doesn't mean we have added support for it.
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Team,

             

            Any update on this request?

             

            In addition, I could see most of the Juniper mibs are supported in Observium as per the below link, but this mibs are not available in our version 21.11.11755 (18th November 2021. Guide me to add those in the server to pull more information.

            https://mibs.observium.org/

            Specific mibs

            https://mibs.observium.org/mib/JUNIPER-IPSEC-FLOW-MON-MIB/

            https://mibs.observium.org/mib/JUNIPER-JS-IPSEC-VPN-MIB/

            https://mibs.observium.org/mib/JUNIPER-CHASSIS-CLUSTER-MIB/

            https://mibs.observium.org/mib/JUNIPER-EX-SMI/

             

            vigneshmuthukrishnan Vignesh added a comment - Hi Team,   Any update on this request?   In addition, I could see most of the Juniper mibs are supported in Observium as per the below link, but this mibs are not available in our version 21.11.11755 (18th November 2021. Guide me to add those in the server to pull more information. https://mibs.observium.org/ Specific mibs https://mibs.observium.org/mib/JUNIPER-IPSEC-FLOW-MON-MIB/ https://mibs.observium.org/mib/JUNIPER-JS-IPSEC-VPN-MIB/ https://mibs.observium.org/mib/JUNIPER-CHASSIS-CLUSTER-MIB/ https://mibs.observium.org/mib/JUNIPER-EX-SMI/  
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Adam,

            Attached the necessary SNMP full dump from device. Kindly review and share your inputs.

            vigneshmuthukrishnan Vignesh added a comment - Hi Adam, Attached the necessary SNMP full dump from device. Kindly review and share your inputs.

            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 -ObentxU <hostname> .1 > myagent.snmpwalk
              snmpwalk -v2c -c <community> -t 3 -Cc --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

            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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

            People

              adama Adam Armstrong
              vigneshmuthukrishnan Vignesh
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: