Prior to installing the DSC SWe, you have to define the VM's communication interfaces and network configuration on the KVM Host. It is recommended that you create an IP plan before installing the DSC SWe software. You can provide appropriate network connectivity between a VM and your IP network. Record and maintain the IP information for future reference.
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.
Refer to DSC SWe and vSP2000 Network Engineering for additional information on configuring the VM and the physical interfaces on the KVM Host.
To assist you in creating an IP plan, the following table summarizes the network devices within a VM.
VM network device names
VM Virtual Network Device | 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 (in any VM). You may use one or more of these interfaces in each VM, depending on your redundancy and throughput requirements. SCTP multi-homing may be used if multiple packet interfaces are configured in a VM. |
imf0, imf1 | Monitoring interface (optional, for use with IMF) |
Note
The following three management IP addresses are required for configuration of the VM management network:
- two IP addresses are required for the VMs (one IP address for each VM)
- one shared IP address is required for both VMs, depending on required network connections
The following table shows an example of IP information needed for the KVM Host.
Installation IP Checklist for the KVM Host
| Parameter | Examples of values for a Linux KVM Host |
|---|---|
| Primary network interface name (Host subnet - physical port) | eth0 |
| Hostname(s) | norwayDSC01, norwayDSC02 |
| IP address of the Host subnet (Host physical interface) | 10.54.164.234, 10.54.164.81 |
| Default router | 10.54.164.1 |
| Netmask of subnet | 255.255.255.0 |
The following table shows an example of IP information needed for the initial configuration of each Routing and Management VMs in slot 1 and slot 2.
Installation IP Checklist for the Management VM
| Parameter | Examples of values for Routing and Management VM in slot 1 | Examples of values for Routing and Management VM in slot 2 |
|---|---|---|
Guest VM Configuration | ||
| VM Name | dscSWe20 | dscSWe30 |
| VM Interface | mgt0 | mgt1 |
| VM Management IP address | 10.54.164.88 | 10.54.164.89 |
| Shared Management IP address |
|
|
| Default router | 10.54.164.1 | 10.54.164.1 |
| Netmask of subnet | 255.255.255.0 | 255.255.255.0 |
| Host Configuration | ||
| Host name | norwayDSC01 | norwayDSC02 |
| Host Physical Interface | eth0 | eth0 |
| Host IP address | 10.54.164.234 | 10.54.164.81 |
The following table shows an example of IP information needed for the network configuration on each Routing or Load Balancer VM (both configured on Application VMs).
Installation IP Checklist for Diameter and SS7 Network Traffic
| Parameter | Examples of values for Routing or Load Balancer VM | Examples of values for Routing or Load Balancer VM |
|---|---|---|
| VM Name | dscSWe20 | dscSWe30 |
| VM Interface | pkt0 | pkt0 |
| VM Routing IP address | 10.54.165.66 | 10.54.165.67 |
| Netmask of subnet | 255.255.255.0 | 255.255.255.0 |
| VM Interface | pkt1 | pkt1 |
| VM Routing IP address | 10.54.166.58 | 10.54.166.59 |
| Netmask of subnet | 255.255.255.0 | 255.255.255.0 |
Note
The subnets for mgt, pkt0 and pkt1 must be different.
Overview
Content Tools