Details
-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
-
Enterprise Edition
-
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
- relates to
-
OBS-2049 Support for Juniper Virtual Chassis Ports
-
- Closed
-
Activity
Hi Mike,
Can you check on the node failure alert within the virtual chassis?
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
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.
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..
Hi Mike,
Please find the port details.
show virtual-chassis vc-port
localre:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
0/54 Configured -1 Up 40000 1 vcp-255/0/54
0/55 Configured -1 Up 40000 2 vcp-255/0/55
fpc1:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
0/53 Configured -1 Up 40000 2 vcp-255/0/53
0/54 Configured -1 Up 40000 0 vcp-255/0/54
fpc2:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
0/53 Configured -1 Up 40000 1 vcp-255/0/53
0/55 Configured -1 Up 40000 0 vcp-255/0/55
Please show screenshot(s) with which port you mean (and which alerts should be triggered).
Hi Adam,
I've attached the full snmp dump from the device.
Please let me know if you need any other details.
SNMP MIB information from Juniper
https://www.juniper.net/documentation/software/index_mibs.html
General questions and device support you always can discuss in our Discord channel, click here for connect.
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.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf 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.
Hi Mike,
Any update regarding the Juniper SRX firewall Virtual chassis node failure alert?
Regarding the
OBS-2049Support 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?