Prior to instantiating the SBC SWe Cloud on OpenStack, you must create networks within the tenant for various purposes. Create these networks in the following order:

  • Management (MGT0) - used for OA&M access. SSH to the CLI, or browser access to the EMA is through management network.
  • High-Availability (HA) - used for high-availability communications between nodes.
  • Signaling/media (PKT0, PKT1) - used for SIP signaling and media. This includes SIP peers within the same network, SIP peers on different networks within the same cloud, and peers on the public internet or in any network that requires exiting the cloud.
  • Signaling/media (PKT0_S, PKT1_S) (Optional) - If you plan to implement packet port redundancy two additional signaling/media networks are needed for the secondary packet ports.
  • Management (MGT1) (Optional) - If you plan to implement a second management port, a second management network is also required.

You can create the required networks and their subnets within your project in OpenStack using the Horizon dashboard GUI or using the CLI interface. Log in as an administrator to have all configuration options available.  Based on your network requirements, you can also create routers to connect each external network with one or more internal networks. Refer to OpenStack documentation or the documentation provided by your OpenStack vendor for more information. 

During orchestration of your deployment you must provide the names of the networks you want to use. This can be done through the Heat template, environment file, or GUI if you deploy using Heat templates. If you deploy using VNFM, you are prompted for network names during orchestration. 

Note:

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

  • No labels