-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
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
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
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
-
-
-
-
-
Authentication and authorization for System Users
-
-
Export SYSLOG securely over SSL
-
-
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!
Export syslog securely over SSL
You can securely export syslog over SSL (Secure Sockets Layer) ensuring that sensitive log data traverses the network in an encrypted and authenticated manner. By leveraging SSL, you can safeguard syslog transmissions against eavesdropping, tampering, and unauthorized access.
Export audit logs securely over an SSL connection by authenticating the syslog server
The following are the configuration steps to send audit logs securely over an SSL connection by authenticating the syslog server:
-
Copy the CA certificate. CA certificate is the certificate issued to the syslog server by the Certificate Authority. The certificate is available in the
/nsconfig/ssl
folder.-
Run the following command on the certificate:
openssl x509 -noout -hash -in <ca_certificate> <!--NeedCopy-->
The result is a hash (for example 6d2962a8), a series of alphanumeric characters based on the Distinguished Name of the certificate.
-
Run the following command to create a symbolic link to the certificate that uses the hash returned by the previous command and the
.0
suffix.ln -s <ca_certificate> 6d2962a8.0 <!--NeedCopy-->
-
-
Enable load balancing and SSL features.
enable ns feature LoadBalancing enable ns feature SSL <!--NeedCopy-->
-
Add an SSL cert key by giving the CA certificate path.
add ssl certkey server_cacert -cert <path_to_ca_cert> <!--NeedCopy-->
-
Add a service of type
SSL_TCP
with the IP address of the syslog server and the port on which the syslog server listens for SSL packets.add service syslog_service <syslog_server_ip> SSL_TCP <syslog_server_port> <!--NeedCopy-->
-
Bind the cert key to the service by giving the option
-CA
.bind ssl service syslog_service -certkeyName server_cacert -CA <!--NeedCopy-->
-
Enable the server authentication in the service.
set ssl service syslog_service -serverAuth ENABLED <!--NeedCopy-->
-
Add a load balancing virtual server of type TCP with an IP address and port 514. Add SNIP address in the load balancing virtual server IP’s subnet.
add lb vserver lb_vserver TCP <lb_vserver_ip> 514 add ns ip <IP> <subnet> -type SNIP <!--NeedCopy-->
-
Bind the service to the load balancing virtual server.
bind lb vserver lb_vserver syslog_service <!--NeedCopy-->
-
Add syslog action with the IP address as load balancing virtual IP address, port number as 514 and transport as TCP.
add syslogaction sys_act <lb_vserver_ip> -loglevel all -transport TCP -serverPort 514 <!--NeedCopy-->
-
Add
syslogpolicy
and bind the policy to system global.add syslogpolicy sys_pol true sys_act bind syslogglobal -policyname sys_pol -priority 1 <!--NeedCopy-->
Export audit logs securely over SSL connection through mutual authentication
The following are the configuration steps to send audit logs securely over SSL connection through mutual authentication:
-
Copy the CA certificate. CA certificate is the certificate issued to the syslog server by the Certificate Authority. The certificate is available in the
/nsconfig/ssl
folder.-
Run the following command on the certificate:
openssl x509 -noout -hash -in <ca_certificate> <!--NeedCopy-->
The result is a hash (for example 6d2962a8), a series of alphanumeric characters based on the Distinguished Name of the certificate.
-
Run the following command to create a symbolic link to the certificate that uses the hash returned by the previous command and the .0 suffix.
ln -s <ca_certificate> 6d2962a8.0 <!--NeedCopy-->
-
-
Add the SSL cert key by giving the CA certificate path.
add ssl cert key server_cacert -cert <path_to_ca_cert> <!--NeedCopy-->
-
Add the SSL cert key by giving the client certificate (NetScaler’s certificate) with the key.
add ssl certkey client_cacert -cert <path_to_client_cert> -key <path_to_client_key> <!--NeedCopy-->
-
Add service of type
SSL_TCP
with the IP address of syslog server and the port on which the syslog server listens for SSL packets.add service syslog_service <syslog_server_ip> SSL_TCP <syslog_server_port> <!--NeedCopy-->
-
Bind the cert key (server) to the service by giving the option
-CA
.bind ssl service syslog_service -certkeyName server_cacert -CA <!--NeedCopy-->
-
Bind the cert key (client) to the service.
bind ssl service syslog_service -certkeyName client_cacert <!--NeedCopy-->
-
Enable the server authentication in the service.
set ssl service syslog_service -serverAuth ENABLED <!--NeedCopy-->
-
Add load balancing virtual server of type TCP with an IP address and port 514. Add SNIP address in the load balancing virtual server IP’s subnet.
add lb vserver lb_vserver TCP <lb_vserver_ip> 514 <!--NeedCopy-->
-
Bind the service to a load balancing virtual server.
bind lb vserver lb_vserver syslog_service <!--NeedCopy-->
-
Add syslog action with the IP address as load balancing virtual IP address, port as 514 and transport as TCP.
add syslogaction sys_act <lb_vserver_ip> -loglevel all -transport TCP -serverPort 514 <!--NeedCopy-->
-
Add syslog policy and bind this policy to system global.
add syslogpolicy sys_pol true sys_act bind syslogglobal -policyname sys_pol -priority 1 <!--NeedCopy-->
With this configuration, SYSLOGTCP connection gets established from NetScaler’s IP address (NSIP) to load balancing virtual server’s IP address (LB VIP) and SSL_TCP connection gets established from Subnet IP(SNIP) of NetScaler to the back end syslog server. The audit log messages are then sent to syslog server over the SSL_TCP connection.
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.