This article describes the issue of authentication success, but single node visibility in the SNMP monitoring tool (Zabbix, Akips, etc.) when trying to poll one of the nodes in the SRX cluster with SNMPv3.

• The SNMPv3 engine IDs should be kept different for individual nodes in case the solution in KB27191 [juniper.net] does not work with the same engine ID for some of the networking tools.
• Once we observe that the SNMP engine ID is different, the authentication for individual nodes should be applied under the respective group nodeX configuration hierarchy.

• The CLI command to check the engine ID

> show snmp v3 

Local engine ID: 80 00 0a xx xx xx xx xx f1          
Engine boots:           1
Engine time:      3644310 seconds
Max msg size:       65507 bytes

• In case the SNMP tool is not able to detect the cluster node, please verify that under group nodeX each node has a unique host-name configured.

set groups node0 system host-name Node-FW00
set groups node1 system host-name Node-FW01