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

Juniper switch/firewall alert not working for VC ports /Cluster failure

Details

    • New Feature
    • Resolution: Unresolved
    • Minor
    • None
    • Enterprise Edition
    • Alerting
    • None

    Description

      Observium Version - 20.12.10875 (7th December 2020)

      Alerts not triggered in Juniper when a device is in Virtual chassis or Chassis cluster.

      EX/QFX Juniper Switches virtual chassis ports are not listed other than the master.

      SRX firewall node failure alert not coming up.

      Please check and update the status

       

       

       

       

       

       

      Attachments

        Issue Links

          Activity

            [OBS-3928] Juniper switch/firewall alert not working for VC ports /Cluster failure

            You have to enable snmp statistics for vcp ports of other members:

            set virtual-chassis vcp-snmp-statistics

             

            It's a hidden setting (does not show up with tab-completion), might be useful to add this to documentation for Juniper Virtual Chassis...

             

            cfr: [vcp-snmp-statistics | Junos OS | Juniper Networks|https://www.juniper.net/documentation/us/en/software/junos/virtual-chassis-ex-4200-4500/topics/ref/statement/vcp-snmp-statistics-edit-virtual-chassis.html]

            bankdelen-6160660 Walter Smet added a comment - You have to enable snmp statistics for vcp ports of other members: set virtual-chassis vcp-snmp-statistics   It's a hidden setting (does not show up with tab-completion), might be useful to add this to documentation for Juniper Virtual Chassis...   cfr: [vcp-snmp-statistics | Junos OS | Juniper Networks|https://www.juniper.net/documentation/us/en/software/junos/virtual-chassis-ex-4200-4500/topics/ref/statement/vcp-snmp-statistics-edit-virtual-chassis.html]
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Adam,

            Sorry for the inconvenience. Kindly check and let me know if any details required.

            This is regarding this request 

            OBS-3928 - Juniper switch/firewall alert not working for VC ports /Cluster failure

            vigneshmuthukrishnan Vignesh added a comment - Hi Adam, Sorry for the inconvenience. Kindly check and let me know if any details required. This is regarding this request  OBS-3928 - Juniper switch/firewall alert not working for VC ports /Cluster failure

            It's not clear what this ticket is about.

            Please do not assume that we know anything at all about your devices.

            adama Adam Armstrong added a comment - It's not clear what this ticket is about. Please do not assume that we know anything at all about your devices.
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Team,

            Please update the status.

            Could you please clarify as what is possible and not possible.

            Our requirement is to expose the Virtual chassis ports and nodes for monitoring and alerting if in case of any failure.

            Awaiting your update.

            vigneshmuthukrishnan Vignesh added a comment - Hi Team, Please update the status. Could you please clarify as what is possible and not possible. Our requirement is to expose the Virtual chassis ports and nodes for monitoring and alerting if in case of any failure. Awaiting your update.
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Mike,

             

            Any update regarding the Juniper SRX firewall Virtual chassis node failure alert?

            Regarding the  OBS-2049 Support for Juniper Virtual Chassis Ports - 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 the "JUNIPER-VIRTUALCHASSIS-MIB" haven't polled at all.

             

            Can you please check and update the status?

            vigneshmuthukrishnan Vignesh added a comment - Hi Mike,   Any update regarding the Juniper SRX firewall Virtual chassis node failure alert? Regarding the  OBS-2049 Support for Juniper Virtual Chassis Ports - 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 the "JUNIPER-VIRTUALCHASSIS-MIB" haven't polled at all.   Can you please check and update the status?
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Mike,

            Can you check on the node failure alert within the virtual chassis?

            vigneshmuthukrishnan Vignesh added a comment - Hi Mike, Can you check on the node failure alert within the virtual chassis?
            vigneshmuthukrishnan Vignesh added a comment -

            How about the node failure (Physical Switch) within the virtual chassis?

            I can see observium is monitoring those nodes but the alerts are not triggered.

            Refer the screenshot

            vigneshmuthukrishnan Vignesh added a comment - How about the node failure (Physical Switch) within the virtual chassis? I can see observium is monitoring those nodes but the alerts are not triggered. Refer the screenshot
            vigneshmuthukrishnan Vignesh added a comment -

            Hi Mike,

            Alert should be triggered for both Virtual Chassis-Ports as well as node failure within the virtual chassis. Above switch has three nodes in the VC.

            I'll share the details of Juniper SRX firewall SNMP dump to check on the chassis cluster node failure.

            vigneshmuthukrishnan Vignesh added a comment - Hi Mike, Alert should be triggered for both Virtual Chassis-Ports as well as node failure within the virtual chassis. Above switch has three nodes in the VC. I'll share the details of Juniper SRX firewall SNMP dump to check on the chassis cluster node failure.

            I think you need write JTAC to vendor about this.

            landy Mike Stupalov added a comment - I think you need write JTAC to vendor about this.

            As I see in your snmp dump, only this ports listed here:

            IF-MIB::ifDescr.101 = STRING: vcp-255/1/0
            IF-MIB::ifDescr.102 = STRING: vcp-255/1/0.32768
            IF-MIB::ifDescr.103 = STRING: vcp-255/1/1
            IF-MIB::ifDescr.104 = STRING: vcp-255/1/1.32768
            IF-MIB::ifType.101 = INTEGER: other(1)
            IF-MIB::ifType.102 = INTEGER: propVirtual(53)
            IF-MIB::ifType.103 = INTEGER: other(1)
            IF-MIB::ifType.104 = INTEGER: propVirtual(53)
            IF-MIB::ifOperStatus.101 = INTEGER: up(1)
            IF-MIB::ifOperStatus.102 = INTEGER: up(1)
            IF-MIB::ifOperStatus.103 = INTEGER: up(1)
            IF-MIB::ifOperStatus.104 = INTEGER: up(1)

            observium can monitor only what device report..

            landy Mike Stupalov added a comment - As I see in your snmp dump, only this ports listed here: IF-MIB::ifDescr.101 = STRING: vcp-255/1/0 IF-MIB::ifDescr.102 = STRING: vcp-255/1/0.32768 IF-MIB::ifDescr.103 = STRING: vcp-255/1/1 IF-MIB::ifDescr.104 = STRING: vcp-255/1/1.32768 IF-MIB::ifType.101 = INTEGER: other(1) IF-MIB::ifType.102 = INTEGER: propVirtual(53) IF-MIB::ifType.103 = INTEGER: other(1) IF-MIB::ifType.104 = INTEGER: propVirtual(53) IF-MIB::ifOperStatus.101 = INTEGER: up(1) IF-MIB::ifOperStatus.102 = INTEGER: up(1) IF-MIB::ifOperStatus.103 = INTEGER: up(1) IF-MIB::ifOperStatus.104 = INTEGER: up(1) observium can monitor only what device report..

            People

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

              Dates

                Created:
                Updated: