-
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!
Configure network interfaces
Network interfaces in the NetScaler appliance are numbered in <slot><port> notation. After configuring your interfaces, display the interfaces and their settings to verify the configuration. You can also display this information to troubleshoot a problem in the configuration.
To manage the network interfaces, you can do the following;
- Enable some interfaces and disable others.
- Reset an interface to renegotiate its settings.
- Clear the accumulated statistics for an interface.
To verify the configuration, you can display the interface settings. You can display the statistics for an interface to evaluate its health.
Set the network interface parameters
The network interface configuration is neither synchronized nor propagated. For an HA pair, you must perform the configuration on each unit independently.
Note:
In an HA setup, if the
tag allparameter is enabled, then the HA packets are also tagged with the VLAN traffic. However, there might be issues with the high availability communication. Therefore, it is recommended to configure NSVLAN or HA SYNC VLAN for HA traffic.
- For NSVLAN configuration, see Configuring NSVLAN.
- For HA SYNC VLAN configuration, see Configure HA SYNC VLAN.
To set the network interface parameters by using the CLI:
At the command prompt, type:
- set interface <id> [-speed <speed>] [-duplex <duplex>] [-flowControl <flowControl>] [-autoneg ( DISABLED | ENABLED )] [-haMonitor ( ON | OFF )] [ ( ON | OFF )] [-tagall ( ON | OFF )] [-lacpMode <lacpMode>] [-lacpKey<positive_integer>] [-lacpPriority <positive_integer>] [-lacpTimeout (LONG | SHORT )] [-ifAlias <string>] [-throughput <positive_integer>][-bandwidthHigh <positive_integer> [-bandwidthNormal <positive_integer>]]
- show interface [<id>]
<!--NeedCopy-->
Example:
> set interface 1/8 -duplex full
Done
<!--NeedCopy-->
To set the network interface parameters by using the GUI:
Navigate to System > Network > Interfaces, select the network interface that you want to modify (for example, 1/8), click Edit, and then set the parameters.
Setting the receive ring size and ring type for an interface
You can increase the receive ring size and ring type for IX, F1X, F2X, or F4X interfaces on NetScaler MPX and SDX platforms.
An increased ring size provides more cushion to handle burst traffic, but might impact the performance. A ring size of up to 8192 is supported for IX interfaces. A ring size of up to 4096 is supported for F1X, F2X, and F4X interfaces. The default ring size remains 2048.
Interface ring types are elastic by default. They increase or decrease in size based on packet arrival rate. You can configure the ring type as “fixed” in which case the ring size does not change based on traffic rate.
Note: This feature is supported from release 13.0 build 41.x, and supported on platforms that have IX, F1X, F2X, or F4X interfaces.
Use the show hardware command to identify whether your appliance has IX, F1X, F2X, or F4X interfaces.
Examples:
The following model has 16 F1X (10G) interfaces and 4 F4X (40G) interfaces.
> sh hardware
Platform: NSMPX-25000-40G 20*CPU+16*F1X+4*F4X+2*E1K+2*CVM N3 250040
Manufactured on: 12/16/2016
CPU: 2800MHZ
Host Id: 234913926
Serial no: N43RJCRV3X
Encoded serial no: N43RJCRV3X
Netscaler UUID: 336a32d6-2cfa-11e8-bf01-00e0ed5dd23c
BMC Revision: 4.08
Done
<!--NeedCopy-->
The following model has 2 1X (10G) interfaces.
> sh hardware
Platform: NSMPX-10500 8*CPU+2*E1K+8*E1K+2*IX+8*CVM 1620 760100
Manufactured on: 12/27/2010
CPU: 2832MHZ
Host Id: 1707114630
Serial no: 7VZZV1ZXJ4
Encoded serial no: 7VZZV1ZXJ4
Netscaler UUID: eb1bfd72-5176-11e7-ba18-00e0ed1b0d12
Done
<!--NeedCopy-->
To configure ring size and ring type by using the CLI At the command line, type:
set interface <id> -ringsize <positive_integer> -ringtype ( Elastic | Fixed )
<!--NeedCopy-->
Parameters:
ringsize:
The receive ring size of the interface. A higher number provides more buffers to handle incoming traffic.
Default value: 2048 Minimum value: 512 Maximum value: 16384
ringtype:
The receive ring type of the interface. A fixed ring type preallocates the configured number of buffers irrespective of traffic rate. In contrast, an elastic ring, expands and shrinks based on incoming traffic rate.
Possible values: Elastic, Fixed
Default value: Elastic
Example:
> set interface 40/2 -ringsize 4096 -ringtype Fixed
Done
> show interface 40/2
1) Interface 40/2 (40G Ethernet, CR4, 40 Gbit) #21 flags=0xc020 <ENABLED, UP, UP, autoneg, HAMON, HEARTBEAT, 802.1q> MTU=1500, native vlan=10, MAC=00:e0:ed:75:14:2a, uptime 119h26m32s
Requested: media AUTO, speed AUTO, duplex AUTO, fctl OFF,throughput 0
Actual: media UTP, speed 40000, duplex FULL, fctl OFF, throughput 40000
LLDP Mode: NONE, LR Priority: 1024
RX: Pkts(1443972660032) Bytes(1457207315336105) Errs(0) Drops(53319) Stalls(0)
TX: Pkts(1452311431262) Bytes(1458534011197761) Errs(0) Drops(788) Stalls(0)
NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0)
Bandwidth thresholds are not set.
Rx Ring: Configured size=4096, Actual size=4096, Type: Fixed
Done
<!--NeedCopy-->
The last line shows the configured and actual ring size, and the ring type.
To configure ring size and ring type by using the GUI:
- Navigate to System > Network > Interfaces.
- Select your interface and click Edit.
-
In Ring Size, specify one of the following:
-
IX interfaces: 512, 1024, 2048, 4096, or 8192.
-
F1X, F2X, or F4X interfaces: 512, 1024, 2048, or 4096.
-
- In Ring Type, select Elastic or Fixed.
- Click OK.
Enable and disable network interfaces
By default, the network interfaces are enabled. Disable any network interface that is not connected to the network, so that it cannot send or receive packets. Disabling a network interface that is connected to the network in a high availability setup can cause a failover.
For more information about high availability, see High Availability.
To enable or disable a network interface by using the CLI:
At the command prompt, type:
- enable interface <interface_num>
- show interface <interface_num>
- disable interface <interface_num>
- show interface <interface_num>
<!--NeedCopy-->
Example:
> enable interface 1/8
Done
> show interface 1/8
Interface 1/8 (Gig Ethernet 10/100/1000 MBits) #2
flags=0x4004000 <ENABLED, DOWN, BOUND to LA/1, down, autoneg, 802.1q>
MTU=1514, MAC=00:d0:68:15:fd:3d, downtime 906h58m40s
Requested: media UTP, speed AUTO, duplex FULL, fctl OFF, throughput 0
RX: Pkts(0) Bytes(0) Errs(0) Drops(0) Stalls(0)
TX: Pkts(0) Bytes(0) Errs(0) Drops(0) Stalls(0)
NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0)
Bandwidth thresholds are not set.
Done
<!--NeedCopy-->
To enable or disable a network interface by using the GUI:
- Navigate to System > Network > Interfaces.
- Select the network interface and, in the Action list, select Enable or Disable.
Reset network interfaces
Network interface settings control properties such as duplex and speed. To renegotiate the settings of a network interface, you must reset it.
To reset a network interface by using the CLI:
At the command prompt, type:
- reset interface <interface_num>
- show interface <interface_num>
<!--NeedCopy-->
Example:
> reset interface 1/8
Done
<!--NeedCopy-->
To reset a network interface by using the GUI:
- Navigate to System > Network > Interfaces.
- Select the network interface and, in the Action list, select Reset Interface.
Monitor a network interface
You can display network interface statistics to monitor parameters and use the information to check the health of the network interface. You can monitor parameters, such as packets sent and packets received, throughput, Link Aggregate Control Protocol (LACP) data units, and errors. You can clear the statistics of a network interface to monitor its statistics from the time the statistics are cleared.
To display the statistics of the network interfaces by using the CLI:
At the command prompt, type:
- stat interface <interface_num>
<!--NeedCopy-->
Example:
> stat interface 1/8
Done
<!--NeedCopy-->
To clear a network interface’s statistics by using the CLI:
At the command prompt, type:
- clear interface <interface_num>
<!--NeedCopy-->
Example:
> clear interface 1/8
Done
<!--NeedCopy-->
To display the statistics of an Interface by using the GUI:
Navigate to System > Network > Interfaces, select the network interface, and click Interface Statistics.
To clear a network interface’s statistics by using the GUI:
- Navigate to System > Network > Interfaces.
- Select the network interface and, in the Action list, select Clear Statistics.
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.