In this section:
Add Additional VMs using the Stack Template Update
To commission a VM that is waiting to be deployed, use the sonus_dsc_hot_generator.py script to regenerate YAML with small changes. This script file is included in the dsc_swe_<rel>_<nb>_HOT.tgz that can be downloaded from the Global Support Portal (refer to Downloading Software Files).
Generate a New YAML File for Adding Extra VMs
Start
- Login to OpenStack dashboard.
- Click Project.
- Click Orchestration.
- Click Stacks.
- Click the stack on which you want to add the extra VM.
- Click Overview.
The arguments are listed in the Description.
Generate a new YAML file by executing the sonus_dsc_hot_generator.py with the original arguments but a different vm-count.
For example, if the current vm-count is 2, then change it to 3.If you want to enable the Load Balancer, you have to set the vm-count minimum to 4.
sonus_dsc_hot_generator.py --av-zones "" --config-drive true --flavour "" --ha0 None --image "" --imf0 None --imf1 None --mgt askaddr: --no-prompt --pkt0 askaddr: --pkt1 askaddr: --pkt2 None --pkt3 None --sec-group None --shared-mgt "" --ssh-key "" --ver-str 16_1_0_nb20170914 --vm-count 3 --vm-role None extraDSCVMs.yaml
The newly generated YAML file extraDSCVMs.yaml has 3 VMs enabled.
- Go to Update the Stack Template.
Update the Stack Template
Start
- Log in to the OpenStack dashboard.
- Click Project.
- Click Orchestration.
- Click Stacks.
- Click the required stack.
- Click the drop-down menu on the far-right side and select Select Template.
- Click Choose File and select the YAML file created in Generate a New YAML File for Adding Extra VMs (extraDSCVMs.yaml).
Click Next.
On the Update Stack Parameters page, the original values should be entered or there will be unexpected changes. For the new VM, new IP addresses can be assigned.
- Click Update.
- You will notice that the update is in progress.
When the update is done, the Status will be changed to Update Complete.
The new VMs will be booted up automatically while the existing VMs are not impacted. - Do one of the following:
If the new VM will be commissioned as an Application VM (not a Load Balancer), go to Commission an Application VM (not a Load Balancer).
If the new VM is commissioned as a Load Balancer Application VM, go to Commission an Application VM (Load Balancer).
Commission an Application VM (Not a Load Balancer)
Use this procedure to commission a VM that has been deployed already such as the extra VMs are deployed when the stack is created.
Start
SSH to one of the Routing and Management VMs on the DSC SWe using this VM‘s IP address.
ssh root@<ip address of the DSC SWe>
Log onto the system.
User ID: <root> password: <root password>
At the CLI prompt, enter startmenu, and press ENTER.
[root@dbagentslot1 ~]# startmenu Main Menu Sonus Networks DSC 1 - System 2 - Enter Shell l - Logout Enter Selection: 1
From the Main Menu, select System, and press ENTER.
System 1 - Date/Time 2 - Software Revisions b - Back l - Logout Enter Selection:
Select Software Revisions, and press ENTER.
Software Revisions 1 - Versions, Commission, Decommission b - Back l - Logout Enter Selection: 1
Select Versions, Commission, Decommission and press ENTER.
AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- No new load detected on system. Upload and run load .sh file on /var/log before attempting upgrade. VM (current) dsc_vm_16_1_0_nb20170828 OS: 7_3_0-1_5 (Servicepack) [none applied] CPU (previous) Not_Available OS: N/A (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) VM BUILD SERVICE O/S -SLOT----TYPE----------RELEASE--VERSION----PACK---IMAGE-------SLOT STATUS--- -------------------------------------------------------------------------------- Slot 1 ROUTING_MGMT 16.1.0 (nb20170828) SP: OS: 7_3_0-1_5 22 procs running Slot 2 ROUTING_MGMT 16.1.0 (nb20170828) SP: OS: 7_3_0-1_5 22 procs running ...please wait... ...please wait.... Slot 3 ROUTING 16.1.0 (nb20170828) SP: OS: 7_3_0-1_5 15 procs running ...please wait..... Slot 4 --TBD-- N/A SP: OS: 7_3_0-1_5 0 procs running ...please wait...... Slot 5 APPLICTN 16.1.0 (nb20170828) SP: OS: 7_3_0-1_5 3 procs running ...please wait....... Slot 6 --TBD-- N/A SP: OS: 7_3_0-1_5 0 procs running ...please wait........ Slot 7 --TBD-- N/A SP: OS: 7_3_0-1_5 0 procs running (p=servicepack is partially applied) Select VM Slot number (3 5) to decommission an optional VM. Select VM Slot number (4 6 7) to begin commissioning of individual VM. Enter slot # or ENTER to cancel:Enter the VM slot to be commissioned and press ENTER (in this example, slot 6).
------------------------------------------------------------------ Commissioning VM card in slot 6... ------------------------------------------------------------------ Pushing necessary scripts to slot 6... Pushed /opt/cpu_ss7gw/current/scripts/commission_cpu to slot6_0 Pushed /opt/cpu_ss7gw/current/scripts/install_and_patch to slot6_0 Pushed /opt/cpu_ss7gw/current/bin/.common_upgrade_functions to slot6_0 Pushed /opt/cpu_ss7gw/current/scripts/card_selection.sh to slot6_0 Pushed /opt/cpu_ss7gw/current/scripts/netconf to slot6_0 Pushed /opt/cpu_ss7gw/current/scripts/license.sh to slot6_0 Pushed /opt/cpu_ss7gw/current/scripts/re_configure.sh to slot6_0 Pushed /opt/cpu_ss7gw/current/data/slot.conf to slot6_0 Pushed /opt/cpu_ss7gw/current/data/lb.1.conf to slot6_0 Pushed /opt/cpu_ss7gw/current/data/lb.2.conf to slot6_0 Pushed /opt/cpu_ss7gw/current/data/lb.ldl.conf to slot6_0 Pushed /opt/cpu_ss7gw/current/data/licensing.conf to slot6_0 Do you want to continue? [y/n]
Enter y and press ENTER.
Please set the CPU card type for slots 6: 1 - Routing CPU 2 - Application CPU Enter desired Card Type:Select the VM type, and press ENTER (in this example, 2 for Application VM).
Choose the Application type: 1 - Load Balancer c - Others Enter desired Application Type:
Enter the required card type and press ENTER (in this example, c for Others).
Enter desired Application Type: c Please wait... Stopping everything if running... Install a new load and servicepacks if necessary ---------------------------------------------------------- --- install_and_patch script running on slot6_0... ---------------------------------------------------------- ...Installing load and servicepacks to VM card: slot6_0 -Finding MGMT VM to pull commissioning data from... Pulling commissioning data from MGMT VM 1 (slot1_0) -Comparing current O/S on this VM (slot6_0) with O/S from MGMT CPU... CPU (slot6_0) O/S: Sonus Linux release dscvm 7_3_0-1_5 MGMT VM (slot1_0) O/S: Sonus Linux release dscvm 7_3_0-1_5 -Checking load on this VM card (slot6_0) CPU (slot6_0) load: dsc_vm_16_1_0_nb20170828 found. -Checking current load on MGMT VM card: slot1_0 MGMT VM load: dsc_vm_16_1_0_nb20170828 was found. ...Loads match. Proceeding to patching. ...Checking MGMT VM for any applied servicepacks... -No servicepacks currently applied on MGMT CPU: slot1_0 --- End of install_and_patch.sh script --- Install of new load and patching of servicepacks completed. Please wait... Please press enter key to continue...Press ENTER.
Network Configuration 1 - SS7/IP Network 2 - Management Network 3 - Restart networking c - Continue to next step Enter Selection:Enter c and press ENTER.
Enter Selection: c licensing type: legacy --- MAC Address and Serial Number for CPU in slot: 6 --- -MAC Address: Readable: 89:e2:ea:83:88:15 CutPaste: 89e2ea838815 -Serial Number: F0251301-2515-2FC3-6980-C410CE654176 -Ensure you have the license keys for this APP CPU ready, and then Press <enter> to continue or "n" to abort the commissioning process.
Press ENTER.
If you are prompted to enter a license key(s) one of the following:
- If you are using the Legacy method to configure licensing for this VM, refer to Legacy Licensing Description and perform the licensing task as required.
If you are using the Local Licensing method, refer to Local Licensing Description and perform the licensing task as required.
- Navigate to the Available Software Versions screen and confirm the VM(s) has been commissioned.
- Repeat this procedure with any additional VMs that should be commissioned.
You may consider doing a Complete Configuration Backup (refer to Complete System Backup and Restore for the DSC SWe).
Commission an Application VM (Load Balancer)
Use this procedure to commission a VM that has been deployed already such as the extra VMs are deployed when the stack is created, and if you want to commission this VM as a Load Balancer VM.
Note
The Load Balancer only supports Diameter application connections and IPv4 networks. For more information about the Load Balancer, refer to Configuring Load Balancer.
If you want to commission a Load Balancer, a minimum of two Application VMs are required for redundancy.
A maximum of two Load Balancers (four Application VMs) can be added to a system.Start
SSH to one of the Routing and Management VMs on the DSC SWe using this VM‘s IP address.
ssh root@<ip address of the DSC SWe>
Log onto the system.
User ID: <root> password: <root password>
At the CLI prompt, enter startmenu, and press ENTER.
From the Main Menu, select System and press ENTER.
[root@dbagentslot1 ~]# startmenu Main Menu Sonus Networks DSC 1 - System 2 - Enter Shell l - Logout Enter Selection: 1
Select Software Revisions and press ENTER.
System 1 - Date/Time 2 - Software Revisions b - Back l - Logout Enter Selection: 2
Select Versions, Commission, Decommission and press ENTER.
Software Revisions 1 - Versions, Commission, Decommission b - Back l - Logout Enter Selection: 1
Enter the slot to be commissioned and press ENTER.
The Load Balancer does not reside on the management slots.
AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- No new load detected on system. Upload and run load .sh file on /var/log before attempting upgrade. VM (current) dsc_vm_16_1_0_nb20170712 OS: 7_3_0-1_4 (Servicepack) [none applied] CPU (previous) Not_Available OS: N/A (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) VM BUILD SERVICE O/S -SLOT----TYPE----------RELEASE--VERSION----PACK---IMAGE-------SLOT STATUS--- -------------------------------------------------------------------------------- Slot 1 ROUTING_MGMT 16.1.0 (nb20170712) SP: OS: 7_3_0-1_4 27 procs running Slot 2 ROUTING_MGMT 16.1.0 (nb20170712) SP: OS: 7_3_0-1_4 27 procs running Slot 3 --TBD-- N/A SP: OS: 7_3_0-1_4 0 procs running Slot 4 --TBD-- N/A SP: OS: 7_3_0-1_4 0 procs running (p=servicepack is partially applied) Select VM Slot number (3 4) to begin commissioning of individual VM. Enter slot # or ENTER to cancel: 3
Select Application CPU and press ENTER.
The Application CPU is the same as Application VM.
1 - Routing CPU 2 - Application CPU Enter desired Card Type:2
Select Load Balancer and press ENTER.
Choose the Application type: 1 - Load Balancer c - Others Enter desired Application Type: 1
Select a Load Balancer ID for this slot
Networking will be restarted on ALL Routing and Configured Application CPUs for changes to take effect! Please abort (CTRL-C) the commissioning process if this is not desired and try again when ready. Choose the Load Balancer ID: 1 - Load Balancer 1 (configured slots: ) 2 - Load Balancer 2 (configured slots: ) c - Skip this step Enter desired Load Balancer ID: 1
The commissioning process installs and configures the slot, then starts the applications.
Return to the Main Menu and repeat steps 4 to 10 to commission a second Application VM.
This procedure only creates one Load Balancer. To create a second Load Balancer, repeat the procedure.
Overview
Content Tools