ADC

Monitoring cluster setup using SNMP MIB with SNMP link

SNMP MIB is device specific information that is configured on the SNMP agent for identifying a NetScaler appliance. It can identify information such as, appliance name, administrator, and location. In a cluster setup, you can now configure the SNMP MIB in any node by including the “ownerNode” parameter in the set SNMP MIB command. Without this parameter, the set SNMP MIB command applies only to the Cluster Coordinator (CCO) node.

To display the MIB configuration for a cluster node other than the CCO, include the “ownerNode” parameter in the show SNMP MIB command.

Configuring SNMP MIB on CLIP

To configure and view MIB configuration on CLIP by using the command line interface.

set snmp mib [-contact <string>] [-name <string>] [-location <string>]
      [-customID <string>] [-ownerNode <positive_integer>]
Done
show snmp mib [-ownerNode <positive_integer>]

 > set mib -contact John -name NS59 -location San Jose -customID 123 -ownerNode 3
Done
> sh mib -ownerNode 3
        --------------------
         Cluster Node ID: 3
        --------------------
        NetScaler system MIB:
        sysDescr:    NetScaler NS11.1: Build 46.4.a.nc, Date: Jun  7 2016, 10:27:29
        sysUpTime:   124300
        sysObjectID: .1.3.6.1.4.1.5951.1.1
        sysContact:  John
        sysName:     NS59
        sysLocation: San Jose
        sysServices: 72
        Custom ID: 123
 Done

> unset mib -contact -name -location -customID -ownerNode 3
 Done
> sh mib -ownerNode 3
        --------------------
         Cluster Node ID: 3
        --------------------
        NetScaler system MIB:
        sysDescr:    NetScaler NS11.1: Build 46.4.a.nc, Date: Jun 7 2016, 10:27:29
        sysUpTime:   146023
        sysObjectID: .1.3.6.1.4.1.5951.1.1
        sysContact:  WebMaster (default)
        sysName:     NetScaler
        sysLocation: POP (default)
        sysServices: 72
        Custom ID: Default
 Done

Cluster SNMP trap messages

In cluster setup, the SNMP trap alarm configurations must be done from the CLIP. The commands are propagated to each of the nodes.

For more information on configuring SNMP, see Configuring the NetScaler to generate SNMP traps.

The following are the cluster specific traps that are available:

  >sh snmp alarm | grep cluster
      CLUSTER-BACKPLANE-HB-MISSING N/A N/A 86400   ENABLED - ENABLED
      CLUSTER-CCO-CHANGE N/A N/A N/A ENABLED - ENABLED
      CLUSTER-NODE-HEALTH N/A N/A 86400 ENABLED - ENABLED
      CLUSTER-NODE-QUORUM N/A N/A 86400 ENABLED - ENABLED
      CLUSTER-OVS-CHANGE N/A N/A N/A ENABLED - ENABLED
      CLUSTER-PROP-FAILURE N/A N/A N/A ENABLED - ENABLED
      CLUSTER-SYNC-FAILURE N/A N/A N/A ENABLED - ENABLED
      CLUSTER-SYNC-PARTIAL-SUCCESS N/A N/A N/A ENABLED - ENABLED
      CLUSTER-VERSION-MISMATCH N/A N/A 86400 ENABLED - ENABLED
Monitoring cluster setup using SNMP MIB with SNMP link