You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

 

Note:

Make sure all your NICs are physically plugged in (link light on) before spawning VM instances. Otherwise, an incorrect port mapping may occur (logical to physical), and your SBC may not function properly.

After you have prepared your OpenStack environment (refer to Pre-Instantiation Requirements of OpenStack) and developed a Heat template for your SBC SWe deployment (refer to Developing a Heat Template), you can use standard OpenStack methods to instantiate an SBC SWe Cloud instance. You can use OpenStack Heat commands or you can use the OpenStack Horizon dashboard to create the SBC instance. Refer to OpenStack documentation or documentation from your OpenStack provider for information on deployment using Heat.

Regardless of method, during orchestration you must specify the name of the template file you want to use to create your instance. If the template file does not provide an acceptable default value for any of the parameters specified within the template, then you must provide those values when you instantiate. You can provide these values in an environment file that you identify along with the template file when you instantiate. Otherwise, the values can be provided on the command line when you create the instance or entered in the GUI screen presented when you use the Horizon UI to launch an instance. The exact parameters you are required to provide or the fields that appear on a GUI screen depend on the parameters defined in your template. 

 After deploying you can view the status of the instance once it registers with the EMS:

Log on to EMS.Click Network > Cluster Management > View Node Status. The Cluster Management / View Node Status window displays. 

EMS - View Node Status Window

 

Warning

Once an N:1 Redundancy Group (RG) is created, you must not delete any instances from the RG using the OpenStack dashboard GUI. In this case, you must remove the RG and create a new one.

 

Note

If a switchover is triggered on the SBC SWe platform due to any of the following reasons, a media outage of 20 seconds occurs for the stable calls:

  • if there is process hang in the media handling application,
  • if media handling process is manually killed or because of the core dump.

 

  • No labels