Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
Citrix应用ADC VPX配置在第一个boot of the Citrix ADC appliance in cloud
Install a Citrix ADC VPX instance on VMware ESX
Configuring Citrix ADC Virtual Appliances to use VMXNET3 Network Interface
Migrating the Citrix ADC VPX from E1000 to SR-IOV or VMXNET3 Network Interfaces
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Citrix应用ADC VPX配置在第一个boot of the Citrix ADC appliance on VMware ESX hypervisor
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
Install a Citrix ADC VPX instance on Linux-KVM platform
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC VPX instance on Microsoft Azure
Network architecture for Citrix ADC VPX instances on Microsoft Azure
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
配置一个high-availability setup with multiple IP addresses and NICs
配置一个high-availability setup with multiple IP addresses and NICs by using PowerShell commands
配置一个Citrix ADC VPX instance to use Azure accelerated networking
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
配置一个high-availability setup with Azure external and internal load balancers simultaneously
Upgrade and downgrade a Citrix ADC appliance
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
On-premises Citrix Gateway as an identity provider to Citrix Cloud
Authentication, authorization, and auditing configuration for commonly used protocols
Troubleshoot authentication and authorization related issues
-
AppExpert Applications and Templates
-
-
-
-
-
-
-
-
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
配置一个utomatic 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 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 for load balancing
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
Use case 15: Configure layer 4 load balancing on the Citrix ADC appliance
-
-
-
Authentication and authorization for System Users
-
Configuring the Citrix ADC to Generate SNMP Traps
-
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 Citrix ADC 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!
Configuring the Citrix ADC to generate SNMP traps
You can configure the Citrix ADC appliance to generate asynchronous events, which are calledtraps. The traps are generated whenever there are abnormal conditions on the appliance. The traps are sent to a remote device called atrap listener. It helps administrators monitor the appliance and respond promptly to any issues.
The Citrix ADC appliance provides a set of condition entities calledSNMP alarms. When the condition in any SNMP alarm is met, the appliance generates SNMP trap messages that are sent to the configured trap listeners. For example, when the LOGIN-FAILURE alarm is enabled, a trap message is generated and sent to the trap listener whenever there is a login failure on the appliance.
To configure the Citrix ADC appliance to generate traps, you need to enable and configure alarms. Then, you specify the trap listeners to which the appliance sends the generated trap messages.
启用SNMP警报
The Citrix ADC appliance generates traps only for SNMP alarms that are enabled. Some alarms are enabled by default, but you can disable them.
When you enable an SNMP alarm, the appliance generates corresponding trap messages when some events occur. Some alarms are enabled by default.
To enable an SNMP alarm by using the CLI
At the command prompt, type the following commands to set the parameters and verify the configuration:
enable snmp alarm
show snmp alarm
To enable an SNMP alarm by using the GUI
- Navigate toSystem > SNMP > Alarms, and select the alarm.
- ClickActionsand selectEnable.
Configuring alarms
The Citrix ADC appliance provides a set of condition entities calledSNMP alarms. When the condition set for an SNMP alarm is met, the appliance generates SNMP traps messages that are sent to the configured trap listeners. For example, when the LOGIN-FAILURE alarm is enabled, a trap message is generated and sent to the trap listener whenever there is a login failure on the appliance.
You can assign an SNMP alarm with a severity level. When you do this, the corresponding trap messages are assigned that severity level.
The following are the severity levels, defined on the appliance, in decreasing order of severity.
- Critical
- Major
- Minor
- Warning
- Informational
For example, if you set a warning severity level for the SNMP alarm named LOGIN-FAILURE, the trap messages generated when there is a login failure is assigned with the warning severity level.
Note
Citrix ADC supports various SNMP alarms. For more information, seeSNMP alarms.
You can also configure an SNMP alarm to log the corresponding trap messages generated whenever the condition on that alarm is met.
To configure an SNMP alarm by using the CLI
At the command prompt, type the following commands to configure an SNMP alarm and verify the configuration:
set snmp alarm
[-thresholdValue [-normalValue ]] [-time ] [-state ( ENABLED | DISABLED )] [-severity ] [-logging ( ENABLED | DISABLED )] show snmp alarm
Where,
ThresholdValue: Value for the high threshold. The Citrix ADC appliance generates an SNMP trap message when the value of the attribute associated with the alarm is greater than or equal to the specified high threshold value.
NormalValue: Value for the normal threshold. A trap message is generated if the value of the respective attribute falls to or below this value after exceeding the high threshold.
To configure SNMP alarms by using the GUI
Navigate toSystem > SNMP > Alarms, select an alarm, and configure the alarm parameters.
Configuring SNMPv1 or SNMPv2 traps
After configuring the alarms, you need to specify the trap listener to which the appliance sends the trap messages. Apart from specifying parameters such as IP or IPv6 address and the destination port of the trap listener, you can specify the type of trap (either generic or specific) and the SNMP version.
You can configure a maximum of 20 trap listeners for receiving either generic or specific traps.
You can also configure the appliance to send SNMP trap messages with a source IP address other than the Citrix ADC IP (NSIP or NSIP6) address to a particular trap listener. For a trap listener that has an IPv4 address, you can set the source IP to either a mapped IP (MIP) address or a subnet IP (SNIP) address configured on the appliance. For a trap listener that has an IPv6 address, you can set the source IP to a subnet IPv6 (SNIP6) address configured on the appliance.
You can also configure the appliance to send trap messages to a trap listener based on a severity level. For example, if you set the severity level as Minor for a trap listener, all trap messages of the severity level equal to or greater than Minor (Minor, Major, and Critical) are sent to the trap listener.
If you have defined a community string for the trap listener, you must also specify a community string for each trap that is to be sent to the listener. A trap listener for which a community string has been defined accepts only trap messages that include a community string matching the community string defined in the trap listener. Other trap messages are dropped.
To add an SNMP trap by using the CLI
At the command prompt, type the following commands to set the parameters and verify the configuration:
add snmp trap
-version ( V1 | V2 ) -destPort -communityName -srcIP -severity show snmp trap
Example:
> `add snmp trap specific 192.0.2.10 -version V2 -destPort 162 -communityName com1 -severity Major`
To configure SNMP traps by using the GUI
Navigate toSystem > SNMP > Traps, and create the SNMP trap.
Configuring SNMPv3 traps
SNMPv3 provides security capabilities such as authentication and encryption by using the credentials of SNMP users. An SNMP manager can receive SNMPv3 trap messages only if its configuration includes the password assigned to the SNMP user.
The trap destination can now receive SNMPv1, SNMPv2, and SNMPv3 trap messages.
To configure an SNMPv3 trap by using the CLI
At the command prompt, do the following:
Add an SNMPv3 trap.
add snmp trap
-version ( V1 | V2 | V3) -destPort -communityName -srcIP -severity Note
Once set, the SNMP trap version cannot be modified.
Example
> add snmp trap specific 192.0.2.10 -version V3 -destPort 162 -communityName com1 -severity Major
Add an SNMP user.
add snmp user
-group [ -authType ( MD5 | SHA ) { -authPasswd } [-privType ( DES | AES ) { -privPasswd }]] Example
> add snmp user edocs_user -group edocs_group
Bind the SNMPv3 trap to the SNMP user.
bind snmp trap
Example
> bind snmp trap specific 192.0.2.10 -version V3 -userName edocs_user -securityLevel authPriv
To configure an SNMPv3 trap by using the GUI
Add an SNMPv3 trap.
Navigate toSystem > SNMP > Traps, and create the SNMP trap by selecting V3 as the SNMP version.
Add an SNMP user.
Navigate toSystem > SNMP > Usersand create the SNMP user.
Bind the SNMPv3 trap to the SNMP user.
- Navigate toSystem > SNMP > Traps,并选择SNMP版本3的陷阱。
- Select the user to which the trap should be bound and define the appropriate Security Level.
SNMP trap logging
A Citrix ADC appliance can log SNMP trap messages (for SNMP alarms in which logging capability is enabled) when you enable the SNMP trap logging option and at least one trap listener is configured on the appliance. Now, you can specify the audit log level of trap messages sent to an external log server. The default log level is Informational. Possible values are Emergency, Alert, Critical, Error, Warning, Debug, and Notice.
For example, you can set the audit log level to Critical for an SNMP trap message generated by a logon failure. That information is then available on the NSLOG or SYSLOG server for troubleshooting.
To enable SNMP trap logging and configure trap log level by using the CLI
At the command prompt, type the following commands to configure SNMP trap logging and verify the configuration:
set snmp option [-snmpTrapLogging (ENABLED | DISABLED)][-snmpTrapLoggingLevel
] show snmp option
To enable SNMP trap logging and configure SNMP trap log level by using the GUI
Navigate toSystem > SNMP, click Change SNMP Options, and set the following parameters:
- SNMP Trap Logging—Select this check box to enable SNMP trap logging when at least one trap listener is configured on the appliance.
- SNMP Trap Logging Level—Select an audit log level for the SNMP trap. By default, the audit level for an SNMP trap is set to “Informational.”
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.