Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Install a Citrix ADC VPX instance on VMware ESX
配置Citrix ADC Virtual Appliances to use VMXNET3 Network Interface
配置Citrix ADC Virtual Appliances to use Single Root I/O Virtualization (SR-IOV) Network Interface
Migrating the Citrix ADC VPX from E1000 to SR-IOV or VMXNET3 Network Interfaces
配置Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
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
配置Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
配置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
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
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure address pools (IIP) for a Citrix Gateway appliance
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
Configuring authentication, authorization, and auditing policies
Configuring Authentication, authorization, and auditing with commonly used protocols
使用an on-premises Citrix Gateway as the identity provider for Citrix Cloud
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
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
使用source IP address of the client when connecting to the server
使用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
使用case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
使用case 3: Configure load balancing in direct server return mode
使用case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
使用case 7: Configure load balancing in DSR mode by using IP Over IP
使用case 10: Load balancing of intrusion detection system servers
使用case 12: Configure Citrix Virtual Desktops for load balancing
使用case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Authentication and authorization
-
Configuring the Citrix ADC for SNMPv3 Queries
-
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 Citrix ADC for SNMPv3 queries
简单网络管理协议版本3 (SNMPv3) is based on the basic structure and architecture of SNMPv1 and SNMPv2. However, SNMPv3 enhances the basic architecture to incorporate administration and security capabilities, such as authentication, access control, data integrity check, data origin verification, message timeliness check, and data confidentiality.
To implement message level security and access control, SNMPv3 introduces the user-based security model (USM) and the view-based access control model (VACM).
- 使用r-Based Security Model.The user-based security model (USM) provides message-level security. It enables you to configure users and security parameters for the SNMP agent and the SNMP manager. USM offers the following features:
- Data integrity:To protect messages from being modified during transmission through the network.
- Data origin verification:To authenticate the user who sent the message request.
- Message timeliness:To protect against message delays or replays.
- Data confidentiality:To protect the content of messages from being disclosed to unauthorized entities or individuals.
- View-Based Access Control Model.The view-based access control model (VACM) enables you to configure access rights to a specific subtree of the MIB based on various parameters, such as security level, security model, user name, and view type. It enables you to configure agents to provide different levels of access to the MIB to different managers.
Citrix ADC supports the following entities that enable you to implement the security features of SNMPv3:
- SNMP Engines
- SNMP Views
- SNMP Groups
- SNMP Users
These entities function together to implement the SNMPv3 security features. Views are created to allow access to subtrees of the MIB. Then, groups are created with the required security level and access to the defined views. Finally, users are created and assigned to the groups.
Note:
The view, group, and user configuration are synchronized and propagated to the secondary node in a high availability (HA) pair. However, the engine ID is neither propagated nor synchronized as it is unique to each Citrix ADC appliance.
To implement message authentication and access control, you need to do the following:
Setting the engine ID
SNMP engines are service providers that reside in the SNMP agent. They provide services such as sending, receiving, and authenticating messages. SNMP engines are uniquely identified using engine IDs.
The Citrix ADC appliance has a unique engineID based on the MAC address of one of its interfaces. It is not necessary to override the engineID. However, if you want to change the engine ID, you can reset it.
To set the engine ID by using the command line interface
At the command prompt, type the following commands to set the parameters and verify the configuration:
set snmp engineId
show snmp engineId
Example
> set snmp engineId 8000173f0300c095f80c68
To set the engine ID by using GUI
Navigate toSystem>SNMP>使用rs, clickConfigure Engine IDand type an engine ID.
Configure a view
SNMP views restrict user access to specific portions of the MIB. SNMP views are used to implement access control.
To add an SNMP view by using the command line interface
At the command prompt, type the following commands to set the parameters and verify the configuration:
add snmp view
-type ( included | excluded ) show snmp view
<名称> < subtr rm snmp视图ee>
Where,
Name. Name for the SNMPv3 view. It can consist of 1 to 31 characters that include uppercase and lowercase letters, numbers, and the hyphen (-), period (.) pound (#), space ( ), at sign (@), equals (=), colon (:), and underscore (_) characters. You should choose a name that helps identify the SNMPv3 view.
Subtree. A particular branch (subtree) of the MIB tree that you want to associate with this SNMPv3 view. You must specify the subtree as an SNMP OID. This is an argument of maximum Length: 99.
type. Include or exclude the subtree, specified by the subtree parameter, in or from this view. This setting can be useful when you have included a subtree, such as A, in an SNMPv3 view and you want to exclude a specific subtree of A, such as B, from the SNMPv3 view. This is a mandatory argument. Possible values: included, excluded.
Examples
add snmp view SNMPv3test 1.1.1.1 -type included sh snmp view SNMPv3test rm snmp view SNMPv3test 1.1.1.1
To configure an SNMP view by using the GUI
Navigate toSystem>SNMP>Views,and create the SNMP view.
Configure a group
SNMP groups are logical aggregations of SNMP users. They are used to implement access control and to define the security levels. You can configure an SNMP group to set access rights for users assigned to that group, thereby restricting the users to specific views.
You need to configure an SNMP group to set access rights for users assigned to that group.
To add an SNMP group by using the command line interface
At the command prompt, type the following commands to set the parameters and verify the configuration:
add snmp group
-readViewName show snmp group
Where,
Name. Name for the SNMPv3 group. Can consist of 1 to 31 characters that include uppercase and lowercase letters, numbers, and the hyphen (-), period (.) pound (#), space ( ), at sign (@), equals (=), colon (:), and underscore (_) characters. You should choose a name that helps identify the SNMPv3 group.
securityLevel. Security level required for communication between the Citrix ADC appliance and the SNMPv3 users who belong to the group. Specify one of the following options:
noAuthNoPriv. Require neither authentication nor encryption.
authNoPriv. Require authentication but no encryption.
authPriv. Require authentication and encryption. Note: If you specify authentication, you must specify an encryption algorithm when you assign an SNMPv3 user to the group. If you also specify encryption, you must assign both an authentication and an encryption algorithm for each group member. This is a mandatory argument. Possible values: noAuthNoPriv, authNoPriv, authPriv.
readViewName. Name of the configured SNMPv3 view that you want to bind to this SNMPv3 group. An SNMPv3 user bound to this group can access the subtrees that are bound to this SNMPv3 view as type INCLUDED, but cannot access the ones that are type EXCLUDED. If the Citrix ADC appliance has multiple SNMPv3 view entries with the same name, all such entries are associated with the SNMPv3 group. This is a mandatory argument. Maximum Length: 31
To configure an SNMP group by using the GUI
Navigate toSystem>SNMP>Groups, and create the SNMP group.
Configuring a user
SNMP users are the SNMP managers that the agents allow to access the MIBs. Each SNMP user is assigned to an SNMP group.
You need to configure users at the agent and assign each user to a group.
To configure a user by using the command line interface
At the command prompt, type the following commands to set the parameters and verify the configuration:
add snmp user
-group [-authType ( MD5 | SHA ) {-authPasswd } [-privType ( DES | AES ) {-privPasswd }]] show snmp user
Where,
authType is the authentication option available while configuring an user. There are two authentication types such as MD5 and SHA.
privType is the encryption option available while configuring an user. There are two types of encryption such as DES of key size 128 bit, and AES of key size 128 bit.
Example
> add snmp user edocs_user -group edocs_group
To configure an SNMP user by using the GUI
Navigate toSystem>SNMP>使用rs, and create the SNMP user.
Share
Share
这个产品文档预览Citrix进行dential.
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.