TPT-NGFW-CLUSTER-MIB :: tptNgfwClusterMemberRejectNotifyReason

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTPT-NGFW-CLUSTER-MIBtptNgfwClusterMemberRejectNotifyReason

tptNgfwClusterMemberRejectNotifyReason

Module: TPT-NGFW-CLUSTER-MIB

OID (symbolic): TPT-NGFW-CLUSTER-MIB::tptNgfwClusterMemberRejectNotifyReason

OID (numeric): 1.3.6.1.4.1.10734.3.9.3.1.1

Node type: OBJECT-TYPE

Type: ClusterMemberRejectReason

Access: accessible-for-notify

Description: The reason a device was not accepted into a cluster configuration.

What is tptNgfwClusterMemberRejectNotifyReason?

This is the reason code, carried in a tptNgfwClusterMemberRejectNotify trap, explaining why a device's attempt to join the cluster was rejected, such as duplicateNodeId. Admins use this to quickly diagnose a failed cluster join attempt, e.g. realizing two devices were misconfigured with the same node ID.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.10734tippingpointTIPPINGPOINT-REG-MIB
1.3.6.1.4.1.10734.3tpt_productsTIPPINGPOINT-REG-MIB
1.3.6.1.4.1.10734.3.9tpt_ngfwMIBsTPT-NGFW-REG-MIB
1.3.6.1.4.1.10734.3.9.3tpt_ngfw_eventsTPT-NGFW-REG-MIB
1.3.6.1.4.1.10734.3.9.3.1tpt_ngfw_paramsTPT-NGFW-REG-MIB
Numeric OIDNameModule
1.3.6.1.4.1.10734.3.9.3.1.1tptNgfwClusterMemberRejectNotifyReasonTPT-NGFW-CLUSTER-MIB