In this section:
Overview
The DSC SWe - vSP2000 software deployment consists of single or multiple VMs installed on a VHE Host. The DSC SWe - vSP2000 software contains a Linux-based operating system and an application layer that provides Diameter (for DSC) and SS7 (for both DSC and vSP2000) routing functions. To enable the DSC SWe - vSP2000, the VM requires external network connections to activate the core routing function on the DSC SWe - vSP2000. The Installer tool establishes the required network connections from the VM to the VHE Host.
Note
The MA-RMS is the physical server hardware that runs VHE as the host OS. The core DSC SWe - vSP2000 runs as a VM with its own guest OS.
Network Interface Levels
Three levels of network interfaces are defined to establish connections from the VM to the physical ports on the VHE Host, as follows:
- Software level contains the virtual machine (VM) network tap interfaces. At the software level, the DSC SWe - vSP2000 requires virtual connections to the VM network tap interfaces to enable the core routing function.
- VHE host OS level contains the virtual Bridge interfaces. The VHE Host OS level consists of connections made between the VM's network tap interfaces and the VHE Host's virtual Bridge devices.
- MA-RMS host hardware level consists of external (physical) Ethernet interfaces. The MA-RMS hardware level consists of connections made between the virtual Bridges and external Ethernet ports.
External Network
The external network consists of the following components:
- Physical cable connections between the MA-RMS and the next hop router.
- Direct cable connections between physical MA-RMS servers to enable the VM-to-VM High Availability (HA) communication link.
Note
Considering the external network infrastructure before defining the first three network levels (software, VHE Host OS, and hardware) simplifies the VHE host configuration once the required external network connections are known.
Network Tap Interfaces
Network tap interfaces are created within each VM, and are defined as follows:
- For DSC SWe: mgt, pkt0, pkt1, imf0, imf1, and ha.
- For vSP2000: mgt, pkt0, pkt1, imf0, imf1, and ha.
Management Interfaces
The management interfaces (mgt) are configured on the Routing and Management VM1 and VM2 and carry data traffic for management functions (for example, user login).
Packet Interfaces
The packet interfaces (pkt0 and pkt1) are each assigned a local IP address and are designated for Diameter or SS7 network traffic.
Monitoring Interfaces
The monitoring interfaces (imf0 and imf1) are for traffic monitoring. The virtual ha0 or ha network interface is used to communicate provisioning and status data between VMs.
High Availability Interface
The High Availability (HA) interface is a dedicated low-latency communication interface designed to improve communication robustness between VMs and used to communicate status and other network data. The HA interface is implemented in the active-active configuration using two VMs operating independently on either a single MA-RMS Host or two individual MA-RMS Hosts. The active-active architecture is resilient to system failures by providing an auto mechanism that allows one DSC SWe - vSP2000 to take control and provide service if the other fails.
Note
For DSC SWe - vSP2000 systems, the HA uses bridge br2-103.
Installer Tool
The Installer tool provides network configuration scripts based on VHE Host reference configurations. The network configuration scripts define the virtual Bridge devices on the VHE Host and establish connections between the virtual Bridges and external Ethernet ports.
Deployment Reference Configurations
A number of possible external network scenarios may be implemented when considering all levels of the VHE Host network connectivity. The DSC SWe - vSP2000 VMs do not have to be physically installed on the VHE Host. They can be deployed in a cloud or installed across multiple servers because the communication between a DSC SWe - vSP2000 VM and a VHE Host on a MA-RMS is through the High Availability (HA) interface. For example, one VM can be created in virtual slot 1 on the VHE Host and another VM can be created in virtual slot 2 on a separate KVM VHE Host. Based on the server being deployed, the TDM links are optionally provided by the dual Quad T1/E1 PCIe Communications Interface Card.
Note
A redundant configuration requires a pair of VMs running on separate MA-RMS hosts.
The following sections show the three variations of how a VM and/or TDM Card maybe set-up with the network tap interfaces for either a DSC SWe or a vSP2000. These configurations can be used in a combination with each other.
Note for vSP2000
For additional information about the network configurations for the vSP2000 on MA-RMS, refer to C20 SP2000 Engineering Rules (SEB-09-00-005). This guide is only available as a PDF for download from the Ribbon Support Portal. For information on how to download this PDF, refer to Accessing Information from the Documentation Center.
DSC SWe References
The following figure shows the DSC SWe VM and VHE Host reference configuration.
DSC SWe MA-RMS with DSC SWe Only
The following figure shows the DSC SWe VM, TDM cards, and VHE Host reference configuration.
DSC SWe MA-RMS with DSC SWe and TDM cards
The following figure shows the TDM cards and VHE Host reference configuration
MA-RMS with TDM Cards Only
Virtual SP2000 References
The following figure shows the vSP2000 VM and VHE Host reference configuration.
vSP2000 MA-RMS with vSP2000 Only
The following figure shows the vSP2000 VM, TDM cards, and VHE Host reference configuration.
vSP2000 MA-RMS with vSP2000 and TDM cards
The following figure shows the TDM cards and VHE Host reference configuration.
MA-RMS with TDM cards Only
Verify the VHE Host Configuration
The VHE is configured and setup by a Ribbon Technician with VLAN IDs provided by the customer. To verify the host configurations are correct, use the following procedure.
Note
For general information on VHE, refer to Virtual Hosting Environment 3.0 Documentation.
The Virtual Hosting Environment Administration Guide (630-02720-01) is a generic VHE guide that should only be used as a reference guide. If you require help with VHE, contact Customer Support.
VHE Host Information
| Information needed | Value | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| VHE Hostname/IP | defined at host install | |||||||||
| VHE Host Root User Password | defined at host install | |||||||||
| VHE Host SSH admin User | secadm | defined at host install | ||||||||
| VHE Host SSH admin password | defined at host install | |||||||||
DSC SWe VLAN Information
| VLAN TEMPLATE NAME | BRIDGE | DSC Interface | VLAN ID | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| C20_DATAOAM_VLAN | br0 | mgt | ||||||||
| C20_DATACALLP_VLAN | br1 | pkt0 | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt0 | pkt1 | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt1 | imf0 | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt2 | imf1 | ||||||||
| C20_HA_4_VLAN | br2-103 | ha | ||||||||
vSP2000 VLAN Information
| VLAN Information: LB/LJ (C20 RMS) | BRIDGE | DSC Interface | VLAN ID | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| C20_DATAOAM_VLAN | br0 | mgt | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt0 | pkt0 | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt1 | pkt1 | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt2 | imf0 | ||||||||
| NETWORK_TEMPLATE_OPTION_BOND1_VLAN | br1-opt3 | imf1 | ||||||||
| C20_HA_4_VLAN | br2-103 | ha | VLAN ID only defined is GEO | |||||||
Note
For the DSC SWe, the pkt0 is not an option; however, on the vSP2000, pkt0 is an option.
Start
Execute the following command at the prompt:
# ifconfig
The configured virtual Bridge devices and the port mapping are displayed.Example DSC SWe Outputbr0 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:16 inet addr:172.29.20.197 Bcast:172.29.20.223 Mask:255.255.255.224 inet6 addr: fe80::2e0:edff:fe5f:2b16/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2679930 errors:0 dropped:0 overruns:0 frame:0 TX packets:746302 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3309289608 (3.0 GiB) TX bytes:2163443855 (2.0 GiB) br1 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14261 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:403988 (394.5 KiB) TX bytes:578 (578.0 b) br1-opt0 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:108 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6144 (6.0 KiB) TX bytes:578 (578.0 b) br1-opt1 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:578 (578.0 b) br1-opt2 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:578 (578.0 b) br2-103 Link encap:Ethernet HWaddr 00:20:30:A4:D8:00 inet6 addr: fe80::2e0:edff:fe5f:2b19/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:39339364 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2674886336 (2.4 GiB) TX bytes:578 (578.0 b)Example vSP2000 Outputbr0 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:16 inet addr:172.29.20.197 Bcast:172.29.20.223 Mask:255.255.255.224 inet6 addr: fe80::2e0:edff:fe5f:2b16/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2679930 errors:0 dropped:0 overruns:0 frame:0 TX packets:746302 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3309289608 (3.0 GiB) TX bytes:2163443855 (2.0 GiB) br1-opt0 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:108 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6144 (6.0 KiB) TX bytes:578 (578.0 b) br1-opt1 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:578 (578.0 b) br1-opt2 Link encap:Ethernet HWaddr 00:E0:ED:5F:2B:17 inet6 addr: fe80::2e0:edff:fe5f:2b17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:578 (578.0 b) br1-opt3 Link encap:Ethernet HWaddr 00:E0:ED:38:E4:FF inet6 addr: fe80::2e0:edff:fe38:e4ff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:103618 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6968786 (6.6 MiB) TX bytes:648 (648.0 b) br2-103 Link encap:Ethernet HWaddr 00:20:30:A4:D8:00 inet6 addr: fe80::2e0:edff:fe5f:2b19/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:39339364 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2674886336 (2.4 GiB) TX bytes:578 (578.0 b)Execute the following command at the prompt:
# brctl show
The virtual Bridge name and member interfaces for each Bridge are displayed. The column Interfaces indicate the VLAN ID.
Example DSC SWe Output# brctl show bridge name bridge id STP enabled interfaces br0 8000.00e0ed5f2b16 no bond0.172 br1 8000.00e0ed5f2b17 no bond1.173 br1-opt0 8000.00e0ed5f2b17 no bond1.201 br1-opt1 8000.00e0ed5f2b17 no bond1.301 br1-opt2 8000.00e0ed5f2b17 no bond1.302 br2-103 8000.002030a4d800 no bond2.103
Example vSP2000 Output# brctl show bridge name bridge id STP enabled interfaces br0 8000.00e0ed5f2b16 no bond0.172 br1-opt0 8000.00e0ed5f2b17 no bond1.201 br1-opt1 8000.00e0ed5f2b17 no bond1.202 br1-opt2 8000.00e0ed5f2b17 no bond1.301 br1-opt3 8000.00e0ed5f2b1 no bond1.302 br2-103 8000.002030a4d800 no bond2.103
Overview
Content Tools