DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
The following steps describe the procedures to upgrade the Azure using IAC:
Create Network Security Group rules to allow the instance to allow SSH access to SBC MGT IP on ports 22, 2024, 444, and 443. Refer to Instantiate Standalone SBC on Azure > Create Network Security Group.
If the NIC for the IAC instance was created in the same subnet as the SBC MGT, this step is not needed.
Run az login and sign in as a user with the role 'owner' for the subscription.
If not yet created, create a Service Principal that contains 'owner' permissions for the subscription. For example:
az ad sp create-for-rbac -n rbbn-iac --role="owner" --scopes="/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXa511"
Export the following values from the Service Principal:
export ARM_SUBSCRIPTION_ID="<subscription_id>" export ARM_TENANT_ID="<tenant_id>" export ARM_CLIENT_ID="<client_id>" export ARM_CLIENT_SECRET="<client_secret>"
You can add this values to the file and source it before running the upgrade command.
Make a directory to extract the IAC tarball.
Copy the IAC tarball to the created directory created above and change it to that directory.
Extract the IAC tarball using tar -zxvf.
Follow the instructions available in
./README.md
to set up IAC the environment.
Change to management/SBC/upgrade/.
Follow the instructions available in ./
management/SBC/upgrade/README.azure.md
to edit the necessary files and run the upgrade.
Information about the update required in the azure_access.yml and upgrade-revert.yml files are available at the last paragraph of README.azure.md
.