-
Getting Started with NetScaler
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
-
Authentication and authorization for System Users
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
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!
SNMP
SNMP agent can be queried for system specific information from a remote device (SNMP Manager). Based on the query, the agent searches for the equal object identifier (OID) in the management information base (MIB) for the data requested and sends the information to the SNMP Manager. The following are the most useful SNMP OIDs for Telco deployments:
Memory
- resMemUsage (1.3.6.1.4.1.5951.4.1.1.41.2)
Percentage of memory utilization on NetScaler.
Packet Engine CPU
- resCpuUsage (1.3.6.1.4.1.5951.4.1.1.41.1)
CPU utilization percentage.
- nsCPUTable (1.3.6.1.4.1.5951.4.1.1.41.6)
This table contains information about each CPU in NetScaler.
Indexed on: nsCPUname
- nsCPUname (1.3.6.1.4.1.5951.4.1.1.41.6.1.1)
The name of the CPU.
- nsCPUusage (1.3.6.1.4.1.5951.4.1.1.41.6.1.2)
CPU utilization percentage.
Throughput
- allNicTotRxMbits (1.3.6.1.4.1.5951.4.1.1.71.1)
Number of megabits received by the NetScaler appliance.
- allNicTotTxMbits (1.3.6.1.4.1.5951.4.1.1.71.2)
Number of megabits transmitted by the NetScaler appliance.
- ipTotRxPkts (1.3.6.1.4.1.5951.4.1.1.43.25)
IP packets received.
- ipTotRxMbits (1.3.6.1.4.1.5951.4.1.1.43.27)
Megabits of IP data received.
- ipTotTxPkts (1.3.6.1.4.1.5951.4.1.1.43.28)
IP packets transmitted.
- ipTotTxMbits (1.3.6.1.4.1.5951.4.1.1.43.30)
Megabits of IP data transmitted.
Connections
Active connections:
- tcpActiveServerConn (1.3.6.1.4.1.5951.4.1.1.46.8)
Connections to a server currently responding to requests.
Total connections:
- tcpCurServerConn (1.3.6.1.4.1.5951.4.1.1.46.1)
Server connections, including connections in the Opening, Established, and Closing state.
- tcpCurClientConn (1.3.6.1.4.1.5951.4.1.1.46.2)
Client connections, including connections in the Opening, Established, and Closing state.
Note: Because of SYN-Cookie, this doesn’t include Client in Opening state
- tcpTotZombieCltConnFlushed (1.3.6.1.4.1.5951.4.1.1.46.26)
Client connections that are flushed because the client has been idle for some time.
- tcpTotZombieSvrConnFlushed (1.3.6.1.4.1.5951.4.1.1.46.27)
Server connections that are flushed because there have been no client requests in the queue for some time.
Errors
- tcpErrSynGiveUp (1.3.6.1.4.1.5951.4.1.1.46.37)
Attempts to establish a connection on the NetScaler that timed out.
- tcpErrRetransmitGiveUp (1.3.6.1.4.1.5951.4.1.1.46.60)
Number of times NetScaler terminates a connection after retransmitting the packet seven times on that connection. Retransmission happens when recieving end doesn’t acknowledges the packet.
- ifInDiscards (1.3.6.1.2.1.2.2.1.13)
The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.
- ifOutDiscards (1.3.6.1.2.1.2.2.1.19)
The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.
- ifErrTxOverflow (1.3.6.1.4.1.5951.4.1.1.54.1.36)
Number of packets that have passed through the overflow queues, during transmission on the specified interface, since the NetScaler appliance was started or the interface statistics were cleared. This gets incremented only on congested ports.
Optimized/Bypass connections
- tcpOptimizationEnabled (1.3.6.1.4.1.5951.4.1.1.46.131)
Total number of connections enabled with TCP optimization.
- tcpOptimizationBypassed (1.3.6.1.4.1.5951.4.1.1.46.132)
Total number of connections bypassed TCP Optimization.
Share
Share
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.