Page History
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
| Panel | ||||
|---|---|---|---|---|
In this section:
|
Creating Networks
...
:
- 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.
| Note |
|---|
Make sure all your NICs are physically plugged in (link light on) before spawning VM instance using qcow2 image. Otherwise, an incorrect port mapping may occur (logical to physical), and your SBC may not function properly. |
To Create Networks
...
Log on to Horizon GUI as admin user.
...
On the navigation pane, click Project > Network > Networks.
...
Click Create Network. In Create Network screen, specify the following values:
Enter Network Name.
Select UP from Admin State drop-down menu.
- Tick the Create Subnet check box.
Click Next.
Caption 0 Figure 1 Creating Network Span
...
In Subnet tab:
Enter Subnet Name.
Enter Network Address for the subnet in Network Address field.
Select IPv4 from IP Version drop-down menu.
Enter Gateway IP. You may disable the gateway by enabling the Disable Gateway check box.
Click Next.
Caption 0 Figure 1 Creating Subnet Span
...
In Subnet Details, specify the following values:
Disable Enable DHCP check box.
Enter IP address range (
<start_ip_addr>, <end_ip_addr>) in Allocation Pools. For example,10.0.0.100, 10.0.0.250.Enter DNS Name Servers.
Enter additional routes for host in Host Routes.
Click Create.
Caption 0 Figure 1 Creating Subnet Details Note For IPv6 with DHCP enabled, ensure that subnet details IPv6 Address Configuration Mode is set to DHCPv6 stateful: Address discovered from OpenStack DHCP as demonstrated in the example screen capture below.
- 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
...
| Caption | ||||
|---|---|---|---|---|
| ||||
| Pagebreak |
|---|
Creating Routers
...
each external network with one or more internal networks.
...
Procedure
On the navigation pane, click Project > Network > Routers.
Click Create Router.
In Create Router screen, specify the following values:
Enter router name in Router Name field.
Select UP from Admin State drop-down menu.
- Select the external network from External Network drop-down menu.
Select Centralized from Router Type drop-down menu.
Note Do not select Distributed as Router Type.
Span Click Create Router.
Caption 0 Figure 1 Creating Router
Adding an Interface to a Router
- Select a router to add an interface to it.
In Router Details screen, click Interface tab.
Caption 0 Figure 1 Router Details Span - Click Add Interface.
- In Add Interface screen, specify the following values:
- Select a subnet from the Subnet drop-down menu. Example : mgt-mt2
- Enter an IP address for the interface in the IP Address field; this is an optional field.
Click Add Interface to complete adding an interface to the selected router.
Caption 0 Figure 1 Add Interface
| Pagebreak |
|---|
...
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.
| Info | ||
|---|---|---|
| ||
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. |
Overview
Content Tools