Ce article a été traduit automatiquement. (Clause de non responsabilité)
Scripts PowerShell supplémentaires pour le déploiement Azure
Cette section fournit les applets de commande PowerShell avec lesquels vous pouvez effectuer les configurations suivantes dans Azure PowerShell :
- Provisionner une instance autonome Citrix ADC VPX
- Provisionnez une paire Citrix ADC VPX dans une configuration haute disponibilité avec un équilibreur de charge externe Azure
- Provisionner une paire Citrix ADC VPX dans une configuration haute disponibilité avec l’équilibreur de charge interne Azure
Consultez également les rubriques suivantes pour les configurations que vous pouvez effectuer à l’aide des commandes PowerShell :
- Configurer une configuration haute disponibilité avec plusieurs adresses IP et cartes réseau à l’aide des commandes PowerShell
- Configurer GSLB sur les instances Citrix ADC VPX
- Configurer GSLB sur une configuration haute disponibilité active de secours NetScaler
- Configurer plusieurs adresses IP pour une instance Citrix ADC VPX en mode autonome à l’aide des commandes PowerShell
Provisionner une instance autonome Citrix ADC VPX
-
Créer un groupe de ressources
Le groupe de ressources peut inclure toutes les ressources de la solution, ou uniquement les ressources que vous souhaitez gérer en tant que groupe. L’emplacement spécifié ici est l’emplacement par défaut des ressources de ce groupe de ressources. Assurez-vous que toutes les commandes permettant de créer un équilibreur de charge utilisent le même groupe de ressources.
$rgName="\<resource group name\>" $locName="\<location name, such as West US\>" New-AzureRmResourceGroup -Name $rgName -Location $locNamePar exemple :
$rgName = "ARM-VPX" $locName = "West US" New-AzureRmResourceGroup -Name $rgName -Location $locName -
Créer un compte de stockage
Choisissez un nom unique pour votre compte de stockage qui ne contient que des lettres et des chiffres minuscules.
$saName="\<storage account name\>" $saType="\<storage account type, specify one: Standard\_LRS, Standard\_GRS, Standard\_RAGRS, or Premium\_LRS\>" New-AzureRmStorageAccount -Name $saName -ResourceGroupName $rgName -Type $saType -Location $locNamePar exemple :
$saName="vpxstorage" $saType="Standard\_LRS" New-AzureRmStorageAccount -Name $saName -ResourceGroupName $rgName -Type $saType -Location $locName -
Créer un jeu de disponibilité
Le jeu de disponibilité permet de garder vos machines virtuelles disponibles pendant les temps d’arrêt, par exemple pendant la maintenance. Un équilibreur de charge configuré avec un jeu de disponibilité garantit que votre application est toujours disponible.
$avName="\<availability set name\>" New-AzureRmAvailabilitySet -Name $avName -ResourceGroupName $rgName -Location $locName -
Créer un réseau virtuel
Ajoutez un nouveau réseau virtuel avec au moins un sous-réseau, si le sous-réseau n’a pas été créé précédemment.
$FrontendAddressPrefix="10.0.1.0/24" $BackendAddressPrefix="10.0.2.0/24" $vnetAddressPrefix="10.0.0.0/16" $frontendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Name frontendSubnet -AddressPrefix $FrontendAddressPrefix $backendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Name backendSubnet -AddressPrefix $BackendAddressPrefix New-AzureRmVirtualNetwork -Name TestNet -ResourceGroupName $rgName -Location $locName -AddressPrefix $vnetAddressPrefix -Subnet $frontendSubnet,$backendSubnetPar exemple :
$frontendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Name frontendSubnet -AddressPrefix $FrontendAddressPrefix $backendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Name backendSubnet -AddressPrefix $BackendAddressPrefix New-AzureRmVirtualNetwork -Name TestNet -ResourceGroupName $rgName -Location $locName -AddressPrefix $vnetAddressPrefix -Subnet $frontendSubnet,$backendSubnet -
Créer une carte réseau
Créez une carte réseau et associez la carte réseau à l’instance Citrix ADC VPX. Le sous-réseau frontal créé dans la procédure ci-dessus est indexé à 0 et le sous-réseau arrière est indexé à 1. Créez maintenant une carte réseau de l’une des trois façons suivantes :
-
Carte réseau avec adresse IP publique
``` $nicName=”<name of the NIC of the VM>”
$pip = New-AzureRmPublicIpAddress -Name $nicName -ResourceGroupName $rgName -Location $locName -AllocationMethod Dynamic
$nic = New-AzureRmNetworkInterface -Name $nicName -ResourceGroupName $rgName -Location $locName -SubnetId $vnet.Subnets[$subnetIndex].Id -PublicIpAddressId $pip.Id
- NIC with Public IP and DNS label
$nicName="\<nom de la carte réseau de la VM\>" $domName="\<libellé du nom de domaine\>" $pip = New-AzureRmPublicIpAddress -Nom $nicName -ResourceGroupName $rgName -DomainNameLabel $domName -Emplacement $locName -AllocationMethod DynamiqueBefore assigning `$domName`, check it is available or not by using command:Test-AzureRmDnsAvailability -DomainQualifiedName $domName -Location $locName $nic = New-AzureRmNetworkInterface -Nom $nicName -ResourceGroupName $rgName -Emplacement $locName -SubnetId $vnet.Sous-réseaux\[$subnetIndex\].Id -PublicIpAddressId $pip.IdFor example:$nicName="frontendNIC" $domName="vpxazure" $pip = New-AzureRmPublicIpAddress -Name $nicName -ResourceGroupName $rgName -DomainNameLabel $domName -Location $locName -AllocationMethod Dynamic $nic = New-AzureRmNetworkInterface -Name $nicName -ResourceGroupName $rgName -Location $locName -SubnetId $vnet.Subnets\[0\].Id -PublicIpAddressId $pip.Id-
NIC with Dynamic Public Address and Static Private IP address*
Make sure that the private (static) IP address you add to the VM should be the same range as that of the subnet specified.
$nicName="\<nom de la carte réseau de la VM\>" $staticIP="\<adresse IP statique disponible sur le sous-réseau\>" $pip = New-AzureRmPublicIpAddress -Nom $nicName -ResourceGroupName $rgName -Emplacement $locName -AllocationMethod Dynamique $nic = New-AzureRmNetworkInterface -Nom $nicName -ResourceGroupName $rgName -Emplacement $locName -SubnetId $vnet.Sous-réseaux\[$subnetIndex\].Id -PublicIpAddressId $pip.Id -PrivateIpAddress $staticIP -
-
Create a virtual object
$vmName=”<VM name>”
$vmSize=”<VM size string>”
$avSet=Get-AzureRmAvailabilitySet -Name $avName -ResourceGroupName $rgName
$vm=New-AzureRmVMConfig -VMName $vmName -VMSize $vmSize -AvailabilitySetId $avset.Id
- Get the Citrix ADC VPX image
$pubName=”<Image publisher name>”
$offerName=”<Image offer name>”
$skuName=”<Image SKU name>”
$cred=Get-Credential -Message “Type the name and password of the local administrator account.”
Provide your credentials that is used to login into VPX
$vm=Set-AzureRmVMOperatingSystem -VM $vm -Linux -ComputerName $vmName -Credential $cred -Verbose
$vm=Set-AzureRmVMSourceImage -VM $vm -PublisherName $pubName -Offer $offerName -Skus $skuName -Version “latest”
$vm=Add-AzureRmVMNetworkInterface -VM $vm -Id $nic.Id
For example:
$pubName = « citrix »
The following command is used for displaying all offers from Citrix:
Get-AzureRMVMImageOffer -Location \$locName -Publisher \$pubName | Sélectionner une offre
$offerName= "netscalervpx110-6531"
The following command is used to know sku offered by publisher for specific offer name:
| Get-AzureRMVMImageSku -Location $locName -Publisher $pubName -Offer $offerName | Select Skus |
- Create a virtual machine
$diskName=”<name identifier for the disk in Azure storage, such as OSDisk>”
For example:
$diskName="dynamique"
$pubName = « citrix »
$offerName= "netscalervpx110-6531"
$skuName= "netscalerbyol"
$storageAcc=Get-AzureRmStorageAccount -ResourceGroupName $rgName -Nom $saName
$osDiskUri=$storageAcc.PrimaryEndpoints.Blob.ToString() + "vhds/" + $diskName+ ".vhd"
$vm=Set-AzureRmVMOSDisk -VM $vm -Nom $diskName -VhdUri $osDiskUri -CreateOption à partir de l'image
When you create VM from Images present in marketplace, use the following command to specify the VM plan:
Set-AzureRmVMPlan -VM $vm -Publisher $pubName -Product $offerName -Name $skuName
New-AzureRmVM -ResourceGroupName $rgName -Location $locName -VM $vm
Provision a Citrix ADC VPX pair in a high availabilty setup with an Azure external load balancer
Log on to AzureRmAccount using your Azure user credentials.
1) Create a resource group
The location specified here is the default location for resources in that resource group. Make sure that all commands used to create a load balancer use the same resource group.
$rgName=”<resource group name>”
$locName=”<location name, such as West US>”
New-AzureRmResourceGroup -Name $rgName -Location $locName
For example:
$rgName = "ARM-LB-NS"
$locName = « Ouest des États-Unis »
New-AzureRmResourceGroup -Nom $rgName -Emplacement $locName
2) Create a storage account
Choose a unique name for your storage account that contains only lowercase letters and numbers.
$saName=”<storage account name>”
$saType=”<storage account type, specify one: Standard_LRS, Standard_GRS, Standard_RAGRS, or Premium_LRS>”
New-AzureRmStorageAccount -Name $saName -ResourceGroupName $rgName -Type $saType -Location $locName
For example:
$saName="vpxstorage"
$saType="Norme\_LRS"
Nouveau-AzureRmStorageAccount -Nom $saName -ResourceGroupName $rgName -Type $saType -Emplacement $locName
3) Create an availability set
A load balancer configured with an availability set ensures that your application is always available.
$avName=”<availability set name>”
New-AzureRmAvailabilitySet -Name $avName -ResourceGroupName $rgName -Location $locName
4) Create a virtual network
Add a new virtual network with at least one subnet, if the subnet was not created previously.
$vnetName = "LBVnet"
$FrontendAddressPrefix="10.0.1.0/24"
$BackendAddressPrefix="10.0.2.0/24"
$vnetAddressPrefix="10.0.0.0/16"
$frontendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Nom frontendSubnet -AddressPrefix$FrontendAddressPrefix
$backendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Nom backendSubnet -AddressPrefix$BackendAddressPrefix
$vnet=New-AzureRmVirtualNetwork -Nom $vnetName -Nom du groupe de ressources $rgName -Emplacement $locName -Préfixe d'adresse $vnetAddressPrefix-Sous-réseau $frontendSubnet,$backendSubnet
Note:
Choose the AddressPrefix parameter value as per your requirement.
Assign front end and back end subnet to the virtual network that you created earlier in this step.
If the front end subnet is the first element of array vnet, subnetId should be $vnet.Subnets[0].Id.
If the front end subnet is the second element in the array, the subnetId should be $vnet.Subnets[1].Id, and so on..
5) Configure front end IP address and create back end address pool
Configure a front end IP address for the incoming load balancer network traffic and create a back end address pool to receive the load balanced traffic.
$pubName="PublicIp1"
$publicIP1 = New-AzureRmPublicIpAddress -Nom $pubName-ResourceGroupName $rgName -Emplacement $locName -AllocationMethod Statique -DomainNameLabel nsvpx
Note: Check for the availability of the value for DomainNameLabel.
$FIPName = "ELBFIP"
$frontendIP1 = New-AzureRmLoadBalancerFrontendIpConfig -Nom $FIPName -Adresse IP publique $publicIP1
$BEPool = "Pool de backend LB"
$beaddresspool1= New-AzureRmLoadBalancerBackendAddressPoolConfig -Nom $BEPool
8) Create a health probe
Create a TCP health probe with port 9000 and interval 5 seconds.
$healthProbe = New-AzureRmLoadBalancerProbeConfig -Nom HealthProbe -Protocole Tcp -Port 9000 -IntervalInSeconds 5 -ProbeCount 2
9) Create a load balancing rule
Create a LB rule for each service that you are load balancing.
For example:
You can use the following example to load balance http service.
$lbrule1 = New-AzureRmLoadBalancerRuleConfig -Nom "HTTP-LB" -FrontendIpConfiguration $frontendIP1 -BackendAddressPool $beAddressPool1 -Sonde $healthProbe -Protocole Tcp -FrontendPort 80 -BackendPort 80
10) Create inbound NAT rules
Create NAT rules for services that you are not load balancing.
For example, when creating a SSH access to a Citrix ADC VPX instance.
Note: Protocol-FrontEndPort-BackendPort triplet should not be the same for two NAT rules.
$inboundNATRule1= New-AzureRmLoadBalancerInboundNatRuleConfig -Nom SSH1 -FrontendIpConfiguration $frontendIP1 -Protocole TCP -FrontendPort 22 -BackendPort 22
$inboundNATRule2= New-AzureRmLoadBalancerInboundNatRuleConfig -Nom SSH2 -FrontendIpConfiguration $frontendIP1 -Protocole TCP -FrontendPort 10022 -BackendPort 22
11) Create a load balancer entity
Create the load balancer adding all objects (NAT rules, load balancer rules, probe configurations) together.
$lbName= "ELB"
$NRPLB = New-AzureRmLoadBalancer -ResourceGroupName $rgName -Nom $lbName -Emplacement $locName -InboundNatRule $inboundNATRule1, $inboundNATRule2 -FrontendIpConfiguration $frontendIP1 -LoadBalancingRule $lbrule1 -BackendAddressPool $beAddressPool1 -Sonde $healthProbe
12) Create a NIC
Create two NICs and associate each NIC with each VPX instance
a) NIC1 with VPX1
For example:
$nicName= "NIC1"
$lbName= "ELB"
$bePoolIndex=0
\* Les index des règles commencent à 0.
$natRuleIndex=0
$subnetIndex=0
\* Index du sous-réseau frontal
$lb=Get-AzureRmLoadBalancer -Nom $lbName -Nom du groupe de ressources $rgName
$nic1=New-AzureRmNetworkInterface -Nom $nicName -ResourceGroupName $rgName -Emplacement $locName -Sous-réseau $vnet.Sous-réseaux\[$subnetIndex\] -LoadBalancerBackendAddressPool $lb.BackendAddressPools\[$bePoolIndex\] -LoadBalancerInboundNatRule $lb.InboundNatRules\[$natRuleIndex\]
b) NIC2 with VPX2
For example:
$nicName= "NIC2"
$lbName= "ELB"
$bePoolIndex=0
$natRuleIndex=1
* Second Inbound NAT (SSH) rule we need to use
$subnetIndex=0
* Frontend subnet index
$lb=Get-AzureRmLoadBalancer -Nom $lbName -Nom du groupe de ressources $rgName
$nic2=New-AzureRmNetworkInterface -Nom $nicName -ResourceGroupName $rgName -Emplacement $locName -Sous-réseau $vnet.Sous-réseaux\[$subnetIndex\] -LoadBalancerBackendAddressPool $lb.BackendAddressPools\[$bePoolIndex\] -LoadBalancerInboundNatRule$lb.InboundNatRules\[$natRuleIndex\]
13) Create Citrix ADC VPX instances
Create two Citrix ADC VPX instances as part of the same resource group and availability set, and attach it to the external load balancer.
a) Citrix ADC VPX instance 1
For example:
$vmName= "VPX1"
$vmSize="Norme\_A3"
$pubName = « citrix »
$offerName= "netscalervpx110-6531"
$skuName= "netscalerbyol"
$avSet=Get-AzureRmAvailabilitySet -Nom $avName -Nom du groupe de ressources $rgName
$vm1=New-AzureRmVMConfig -VMName $vmName -VMSize $vmSize -AvailabilitySetId $avset.Id
$cred=Get-Credential -Message « Saisissez les informations d'identification qui seront utilisées pour se connecter à l'instance VPX »
$vm1=Set-AzureRmVMOperatingSystem -VM $vm1 -Linux -ComputerName $vmName -Credential $cred -Verbose
$vm1=Set-AzureRmVMSourceImage -VM $vm1 -PublisherName $pubName -Offre $offerName -Skus $skuName -Version « la plus récente »
$vm1=Ajouter-AzureRmVMNetworkInterface -VM $vm1 -Id $nic1.Id
$diskName="dynamique"
$storageAcc=Get-AzureRmStorageAccount -ResourceGroupName $rgName -Nom $saName
$osDiskUri1=$storageAcc.PrimaryEndpoints.Blob.ToString() + "vhds1/" + $diskName+ ".vhd"
$vm1=Set-AzureRmVMOSDisk -VM $vm1 -Nom $diskName -VhdUri $osDiskUri1 -CreateOption à partir de l'image
Set-AzureRmVMPlan -VM $vm1 -Éditeur $pubName -Produit $offerName -Nom $skuName
New-AzureRmVM -ResourceGroupName $rgName -Location $locName -VM $vm1
b) Citrix ADC VPX instance 2
For example:
$vmName= "VPX2"
$vmSize="Norme\_A3"
$avSet=Get-AzureRmAvailabilitySet -Nom $avName -Nom du groupe de ressources $rgName
$vm2=New-AzureRmVMConfig -VMName $vmName -VMSize $vmSize -AvailabilitySetId $avset.Id
$cred=Get-Credential -Message " Tapez les informations d'identification qui seront utilisées pour se connecter à l'instance VPX "
$vm2=Set-AzureRmVMOperatingSystem -VM $vm2 -Linux -ComputerName $vmName -Credential $cred -Verbose
$vm2=Set-AzureRmVMSourceImage -VM $vm2 -PublisherName $pubName -Offre $offerName -Skus $skuName -Version « la plus récente »
$vm2=Ajouter-AzureRmVMNetworkInterface -VM $vm2 -Id $nic2.Id
$diskName="dynamique"
$storageAcc=Get-AzureRmStorageAccount -ResourceGroupName $rgName -Nom $saName
$osDiskUri1=$storageAcc.PrimaryEndpoints.Blob.ToString() + "vhds2/" + $diskName+ ".vhd"
$vm2=Set-AzureRmVMOSDisk -VM $vm2 -Nom $diskName -VhdUri $osDiskUri1 -CreateOption à partir de l'image
Set-AzureRmVMPlan -VM $vm2 -Éditeur $pubName -Produit $offerName -Nom $skuName
New-AzureRmVM -ResourceGroupName $rgName -Location $locName -VM $vm2
14) Configure the virtual machines
When both the Citrix ADC VPX instances start, then connect to both Citrix ADC VPX instances using the SSH protocol to configure the virtual machines.
a) Active-Active: Run the same set of configuration commands on the command line of both the Citrix ADC VPX instances.
b) Active-Passive: Run this command on the command line of both the Citrix ADC VPX instances.
add ha node #nodeID <nsip of other Citrix ADC VPX>
In Active-Passive mode, run configuration commands on the primary node only.
Provision a Citrix ADC VPX pair in a high availability setup with Azure internal load balancer
Log on to AzureRmAccount using your Azure user credentials.
1) Create a resource group
The location specified here is the default location for resources in that resource group. Make sure all commands to create a load balancer use the same resource group.
$rgName=”<resource group name>”
$locName=”<location name, such as West US>”
New-AzureRmResourceGroup -Name $rgName -Location $locName
For example:
$rgName = "ARM-LB-NS"
$locName = « Ouest des États-Unis »
New-AzureRmResourceGroup -Nom $rgName -Emplacement $locName
2) Create a storage account
Choose a unique name for your storage account that contains only lowercase letters and numbers.
$saName=”<storage account name>”
$saType=”<storage account type, specify one: Standard_LRS, Standard_GRS, Standard_RAGRS, or Premium_LRS>”
New-AzureRmStorageAccount -Name $saName -ResourceGroupName $rgName -Type $saType -Location $locName
For example:
$saName="vpxstorage"
$saType="Norme\_LRS"
Nouveau-AzureRmStorageAccount -Nom $saName -ResourceGroupName $rgName -Type $saType -Emplacement $locName
3) Create an availability set
A load balancer configured with an availability set ensures that your application is always available..
$avName=”<availability set name>”
New-AzureRmAvailabilitySet -Name $avName -ResourceGroupName $rgName -Location $locName
4) Create a virtual network
Add a new virtual network with at least one subnet, if the subnet was not created previously.
$vnetName = "LBVnet"
$vnetAddressPrefix="10.0.0.0/16"
$FrontendAddressPrefix="10.0.1.0/24"
$BackendAddressPrefix="10.0.2.0/24"
$vnet=New-AzureRmVirtualNetwork -Nom $vnetName -Nom du groupe de ressources $rgName -Emplacement $locName -Préfixe d'adresse $vnetAddressPrefix-Sous-réseau $frontendSubnet,$backendSubnet\`
$frontendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Nom frontendSubnet -AddressPrefix$FrontendAddressPrefix
$backendSubnet=New-AzureRmVirtualNetworkSubnetConfig -Nom backendSubnet -AddressPrefix$BackendAddressPrefix
Note: Choose the AddressPrefix parameter value as per your requirement.
Assign front end and back end subnet to the virtual network that you created earlier in this step.
If the front end subnet is the first element of array vnet, subnetId should be $vnet.Subnets[0].Id.
If the front end subnet is the second element in the array, the subnetId should be $vnet.Subnets[1].Id, and so on..
5) Create an back end address pool
$beaddresspool= New-AzureRmLoadBalancerBackendAddressPoolConfig -Nom "LB-backend"
6) Create NAT rules
Create NAT rules for services that you are not load balancing.
$inboundNATRule1= New-AzureRmLoadBalancerInboundNatRuleConfig -Nom "Inboundnatrule1" -FrontendIpConfiguration $frontendIP -Protocole TCP -FrontendPort 3441 -BackendPort 3389
$inboundNATRule2= New-AzureRmLoadBalancerInboundNatRuleConfig -Nom "RDP2" -FrontendIpConfiguration $frontendIP -Protocole TCP -FrontendPort 3442 -BackendPort 3389
Use front end and back end ports as per your requirement.
7) Create a health probe
Create a TCP health probe with port 9000 and interval 5 seconds.
$healthProbe = New-AzureRmLoadBalancerProbeConfig -Nom "HealthProbe" " -Protocole tcp -Port 9000 -IntervalInSeconds 5 -ProbeCount 2
8) Create a load balancing rule
Create a LB rule for each service that you are load balancing.
For example:
You can use the following example to load balance http service.
$lbrule = New-AzureRmLoadBalancerRuleConfig -Nom "lbrule1" -FrontendIpConfiguration $frontendIP -BackendAddressPool $beAddressPool -Sonde $healthProbe -Protocole Tcp -FrontendPort 80 -BackendPort 80
Use front end and back end ports as per your requirement.
9) Create a load balancer entity
Create the load balancer adding all objects (NAT rules, load balancer rules, probe configurations) together.
$NRPLB = New-AzureRmLoadBalancer -ResourceGroupName $rgname -Nom "InternalLB" -Emplacement $locName -FrontendIpConfiguration $frontendIP -InboundNatRule $inboundNATRule1,$inboundNatRule2 -LoadBalancingRule $lbrule -BackendAddressPool $beAddressPool -Sonde $healthProbe
10) Create a NIC
Create two NICs and associate each NIC with each Citrix ADC VPX instance
$backendnic1= New-AzureRmNetworkInterface -ResourceGroupName $rgName -Name lb-nic1-be -Location $locName -PrivateIpAddress 10.0.2.6 -Subnet $backendSubnet -LoadBalancerBackendAddressPool $nrplb.BackendAddressPools\[0\] -LoadBalancerInboundNatRule $nrplb.InboundNatRules\[0\]
This NIC is for Citrix ADC VPX 1. The Private IP should be in same subnet as that of subnet added.
$backendnic2= New-AzureRmNetworkInterface -ResourceGroupName $rgName-Name lb-nic2-be -Location $locName-PrivateIpAddress 10.0.2.7 -Subnet $backendSubnet -LoadBalancerBackendAddressPool $nrplb.BackendAddressPools\[0\] -LoadBalancerInboundNatRule $nrplb.InboundNatRules\[1\].
This NIC is for Citrix ADC VPX 2.The parameter Private IPAddress can have any private IP as per your requirement.
11) Create Citrix ADC VPX instances
Create two VPX instances part of same resource group and availability set and attach it to the internal load balancer.
a) Citrix ADC VPX instance 1
For example:
$vmName= "VPX1"
$vmSize="Norme\_A3"
$avSet=Get-AzureRmAvailabilitySet -Nom $avName -Nom du groupe de ressources $rgName
$vm1=New-AzureRmVMConfig -VMName $vmName -VMSize $vmSize -AvailabilitySetId $avset.Id
$cred=Get-Credential -Message « Saisissez les informations d'identification qui seront utilisées pour se connecter à l'instance VPX »
$vm1=Set-AzureRmVMOperatingSystem -VM $vm1 -Linux -ComputerName $vmName -Credential $cred -Verbose
$vm1=Set-AzureRmVMSourceImage -VM $vm1 -PublisherName $pubName -Offre $offerName -Skus $skuName -Version « la plus récente »
$vm1=Ajouter-AzureRmVMNetworkInterface -VM $vm1 -Id $backendnic1.Id
$diskName="dynamique"
$storageAcc=Get-AzureRmStorageAccount -ResourceGroupName $rgName -Nom $saName
$osDiskUri1=$storageAcc.PrimaryEndpoints.Blob.ToString() + "vhds1/" + $diskName + ".vhd"
$vm1=Set-AzureRmVMOSDisk -VM $vm1 -Nom $diskName -VhdUri $osDiskUri1 -CreateOption à partir de l'image
Set-AzureRmVMPlan -VM $vm1 -Éditeur $pubName -Produit $offerName -Nom $skuName
New-AzureRmVM -ResourceGroupName $rgName -Location $locName -VM $vm1
b) Citrix ADC VPX instance 2
For example:
$vmName= "VPX2"
$vmSize="Norme\_A3"
$avSet=Get-AzureRmAvailabilitySet -Nom $avName -Nom du groupe de ressources $rgName
$vm2=New-AzureRmVMConfig -VMName $vmName -VMSize $vmSize -AvailabilitySetId $avset.Id
$cred=Get-Credential -Message " Tapez les informations d'identification qui seront utilisées pour se connecter à l'instance VPX "
$vm2=Set-AzureRmVMOperatingSystem -VM $vm2 -Linux -ComputerName $vmName -Credential $cred -Verbose
$vm2=Set-AzureRmVMSourceImage -VM $vm2 -PublisherName $pubName -Offre $offerName -Skus $skuName -Version « la plus récente »
$vm2=Ajouter-AzureRmVMNetworkInterface -VM $vm2 -Id $backendnic2.Id
$diskName="dynamique"
$storageAcc=Get-AzureRmStorageAccount -ResourceGroupName $rgName -Nom $saName
$osDiskUri1=$storageAcc.PrimaryEndpoints.Blob.ToString() + "vhds2/" + $diskName + ".vhd"
$vm2=Set-AzureRmVMOSDisk -VM $vm2 -Nom $diskName -VhdUri $osDiskUri1 -CreateOption à partir de l'image
Set-AzureRmVMPlan -VM $vm2 -Éditeur $pubName -Produit $offerName -Nom $skuName
New-AzureRmVM -ResourceGroupName $rgName -Location $locName -VM $vm2 ```
12\)**Configurer les machines virtuelles**
Lorsque les deux instances Citrix ADC VPX démarrent, connectez-vous aux deux instances Citrix ADC VPX à l'aide du protocole SSH pour configurer les machines virtuelles.
a) Actif-Actif : exécutez le même ensemble de commandes de configuration sur la ligne de commande des deux instances Citrix ADC VPX.
b) Actif-Passif : exécutez cette commande sur la ligne de commande des deux instances Citrix ADC VPX.
ajouter un nœud ha \#nodeID \<nsip d'un autre Citrix ADC VPX\>
En mode actif-passif, exécutez uniquement les commandes de configuration sur le nœud principal.