In this section:
A DSC VM contains several virtual network devices that are used for different types of traffic. For example, the pkt0 interface is intended for Diameter or SS7/IP traffic, while the mgt0 interface is intended for management traffic. The virtual network devices must be integrated into your IP infrastructure to provide IP connectivity to the appropriate systems while taking into account operational requirements such as redundancy, throughput, and latency.
The following provides a brief overview on integrating a DSC SWe into your IP network infrastructure.
Each DSC VM has virtual network devices for:
The naming of these devices within the VMs depends on their intended function. It is up to you to provide appropriate network connectivity between a VM and your IP network, using your Host OS configuration and IP port cabling. Each configured virtual network device on a VM needs its own unique IP address and appropriate network labels or names. Additionally, a shared management IP address is provisioned; this shared management IP address migrates from one management device to the other, depending on available IP connectivity with the management gateway.
For additional information on configuring a DSC VM for your network connections, refer to
The following table summarizes the virtual network devices configured on a DSC SWe (on VMware and on KVM).
Virtual Network Devices on a DSC SWe (on VMware and on KVM)
DSC VM | Intended Function |
---|---|
mgt0 | Management interface for VM 1 |
mgt1 | Management interface for VM 2 |
ha0 | Internal communication between DSC VMs |
pkt0, pkt1, pkt2, pkt3 | Packet interfaces (all VMs). You may use one or more of these interfaces in each VM, depending on your redundancy and throughput requirements. |
imf0, imf1 | Monitoring interface (optional, for use with IMF) |
The DSC SWe (on OpenStack) deployment expects to have one management network and two packet networks. These networks are as follows:
The IP Networks used by the DSC SWE Platforms must be of high quality so these platforms can meet their throughput and latency requirements. See the Customer Network Requirements for the DSC SWe for more specific requirements and see Creating an IP Plan on OpenStack for detailed information about planning the IP network.
For provider networks, the IP addresses are assigned from the subnet allocation pools. These IP addresses for a network are assigned to each interface. ha0 is statically assigned.
Supported IP Network Interfaces
Interface | Description |
---|---|
mgt0 | Management interface for VM 1 |
mgt1 | Management interface for VM 2 |
ha0 | Internal communication between DSC VMs |
pkt0, pkt1, pkt2, pkt3 | Packet interfaces (all VMs). You may use one or more of these interfaces in each VM, depending on your redundancy and throughput requirements. |
imf0, imf1 | Monitoring interface (optional, for use with IMF) |
It is recommended that you create an IP Plan before installing the DSC SWe. IP plan is generally created using an Excel spreadsheet and is intended to capture information such as hostname, logical IP addresses, and so on which help in configuring the DSCsystem. It is important to create the IP plan even for simple networks so that the system information is available during installation, also this information acts as a reference for future configuration changes.
The naming of the network devices within the VM depends on the intended function. Each configured VM virtual network device requires its own unique IP address. Additionally, a shared management IP address is provisioned; this shared management IP address migrates from one management device to the other depending on available IP connectivity with the management gateway.
For more information about creating an IP plan, see the following: