The cloud admin account of AVS holds minimal administrative privileges, which might impede the manual installation of JetDr components (such as registering plugins, installing IOF etc). To overcome this challenge, we have implemented specific AVS Run commands to facilitate a seamless JetDr installation and configuration process.
This article elucidates the process of installing JetDr within an AVS environment.
\uD83D\uDCD8 Instructions
Step 1: Log in to the Azure portal (portal.azure.com)
Step 2: Navigate to the AVS private cloud platform where the deployment of JetDR is needed.
Step 3: Look for the Run command in the left panel and click on it.
Step 4: Under the packages select JSDR.Configuration.
Step 5: From the dropdown of JSDR.Configuration select Install-JetDRWithStaticIP.
JetDR can also be configured using DHCP for this select the Run command “Install-JetDRWithDHCP”
Step 6: From the Run Command form fill in the details accordingly.
If the DNS is not configured or resolving properly explicitly enable RegisterWithIp (as shown above).
Required Fields and the description.
Protected Cluster → Name of the AVS cluster which is going to be protected
DataStore → Name of the datastore where the JetStream MSA will be deployed
VMName → Name of JetStream MSA VM, for example, JetStreamServer
Cluster → Name of the AVS cluster where the JetStream MSA will be deployed
MSAIP → IP address of the JetStream MSA VM
DNS → DNS IP that the JetStream MSA VM should use
Gateway → IP address of the network gateway for the JetStream MSA VM
MSA Credentials → Credentials of the root user of the JetStream MSA VM
HostName → Hostname (FQDN) of the JetStream MSA VM
Network → Name of the NSX-T Data Center network segment where the JetStream MSA will be deployed
Retain Up to → Mention for how many days we want to retain the run command execution
Specify name for execution → Alphanumeric name of the execution, It is used to verify if the cmdlet ran successfully and should be unique for each run
Timeout → Mention the timeout value for the Run command to be executed
Step 7: The Run command status can be monitored at “Run execution status”.
More details on Run command execution can viewed by selecting the desired execution name (as shown below).
The live Run command execution state can be viewed under the information panel (below is the reference).
If the JetDR has to be applied for multiple clusters under a single DC, then execute the Run command “Enable-JetDRForCluster” (please refer to the below image). This has to be executed per cluster (one at a time).
Step 8: After successful completion of the above steps, refresh the vCenter instance for the JetDR plugin to be reflected.
Step 9: The remaining configuration can be done directly from the JetDR UI (vCenter → Datacenter → Configure → JetStream DR)
If any issues are observed please reach out to JetStream support
/wiki/spaces/KBDR/pages/2784657420