-
-
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of Citrix ADC application configuration using StyleBooks
-
-
Use ADM log messages for managing and monitoring your infrastructure
-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
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!
Add Citrix ADC as a device in Cisco ACI using APIC
You need to add a Citrix ADC as an L4-L7 device to the APIC for the network automation. The APIC performs network stitching between Leaf and the Citrix ADC device, based on the deployed service graph. You need to configure the basic settings of the device configuration, such as configuration management IP addresses, device manager, and credentials.
To register the Citrix ADC as a device in the APIC by using the APIC GUI:
-
On the menu bar, go to Tenants > All Tenants.
-
In the Work pane, double-click the tenant’s name.
-
In the Navigation pane, select tenant_name > L4-L7 Services > L4-L7 Devices.
-
In the Work pane, select Actions > Create L4-L7 Devices.
-
In the Create L4-L7 Devices dialog box, in the General section, do the following:
-
Select the Managed check box.
-
In the Name field, enter a name for the device.
-
In the Service Type drop-down list, select ADC.
-
In the Device Type field, select Physical.
Note
Make sure that for VMware ESX, you select Virtual and associate the respective Virtual Machine Manager (VMM) domain.
-
In the Physical Domain drop-down list, select the physical domain.
-
In the Mode field, select Single Node or HA Cluster, depending on your requirement.
-
In the Device Package drop-down list, select Citrix-NetScalerMAS-1.0.
-
In the Model drop-down list, select the device model. For example, Citrix ADC-MPX, or Citrix ADC-VPX.
-
-
In the Connectivity section, select Out-Of-Band or In-Band in the APIC to Device Management Connectivity field, depending on how Citrix ADC is configured in the fabric.
-
In the Credentials section, specify the user name and password for access to the device.
-
In the Device 1 and Device 2 section, respectively, complete the management related configuration.
-
In the Cluster section, complete the management related configuration for the cluster. Make sure that in the Device Manager drop-down list, you select the device manager you created in Adding Citrix ADM as a Device Manager in Cisco APIC
-
Click NEXT. The Device Configuration page appears. The hybrid mode device package does not provide device and cluster specific configuration details such as high-availability, enable/disable features and modes, configuration for NTP, SNMP, SNMP Alarms, and so on. These configurations must be done by using Citrix ADM.
-
Click FINISH. When you have successfully registered the device in the APIC, the device is added and is displayed in the Navigation pane. To view the registered device, in the Navigation pane, go to tenant_name > L4-L7 Services > L4-L7 Devices > device_name.
Important
After you register the device, make sure that there are no faults in the APIC. You can view the faults by clicking the Faults tab in the Work pane.
You can also register a Citrix ADC device by using APIs. The following is a sample XML payload for adding L4-L7 Device:
<polUni> <fvTenant name="coke"> <vnsLDevVipname="ADCCluster1"funcType="GoTo" svcType="ADC"> <vnsRsMDevAtt tDn="uni/infra/mDev-Citrix-NetScalerMAS-1.0" /> <vnsRsALDevToPhysDomP tDn="uni/phys-phys"/> <vnsCMgmt name="devMgmt"host="10.102.102.67"port="80"/> <vnsCCred name="username" value="nsroot"/> <vnsCCredSecret name="password" value="****"/> <vnsRsALDevToDevMgr tnVnsDevMgrName="MAS1"/> <vnsCDev name="ADC1" devCtxLbl="C1"> <vnsCIf name="1_1"> <vnsRsCIfPathAtt tDn="topology/pod-1/paths-101/pathep-[eth1/33]"/> </vnsCIf> <vnsCIf name="1_2"> <vnsRsCIfPathAtt tDn="topology/pod-1/paths-101/pathep-[eth1/35]"/> </vnsCIf> <vnsCMgmt name="devMgmt" host="10.102.102.65" port="80"/> <vnsCCred name="username" value="nsroot"/> <vnsCCredSecret name="password" value="****"/> </vnsCDev> <vnsCDev name="ADC2" devCtxLbl="C1"> <vnsCIf name="1_1"> <vnsRsCIfPathAtt tDn="topology/pod-1/paths-101/pathep-[eth1/34]"/> </vnsCIf> <vnsCIf name="1_2"> <vnsRsCIfPathAtt tDn="topology/pod-1/paths-101/pathep-[eth1/36]"/> </vnsCIf> <vnsCMgmt name="devMgmt" host="10.102.102.66" port="80"/> <vnsCCred name="username" value="nsroot"/> <vnsCCredSecret name="password" value="****"/> </vnsCDev> <vnsLIf name="outside"> <vnsRsMetaIf tDn="uni/infra/mDev-Citrix-NetScalerMAS-1.0/mIfLbl-outside"/> <vnsRsCIfAtt tDn="uni/tn-coke/lDevVip-ADCCluster1/cDev-ADC1/cIf-1_1"/> <vnsRsCIfAtt tDn="uni/tn-coke/lDevVip-ADCCluster1/cDev-ADC2/cIf-1_1"/> </vnsLIf> <vnsLIf name="inside"> <vnsRsMetaIf tDn="uni/infra/mDev-Citrix-NetScalerMAS-1.0/mIfLbl-inside"/> <vnsRsCIfAtt tDn="uni/tn-coke/lDevVip-ADCCluster1/cDev-ADC1/cIf-1_2"/> <vnsRsCIfAtt tDn="uni/tn-coke/lDevVip-ADCCluster1/cDev-ADC2/cIf-1_2"/> </vnsLIf> </vnsLDevV </fvTenant> </polUni>
Share
Share
In this article
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.