-
Distributing traffic across cluster nodes
-
Managing the NetScaler cluster
-
Node groups for spotted and partially striped configurations
-
Removing a node from a cluster deployed using cluster link aggregation
-
Monitoring cluster setup using SNMP MIB with SNMP link
-
Monitoring command propagation failures in a cluster deployment
-
Monitor Static Route (MSR) support for inactive nodes in a spotted cluster configuration
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
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
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.