3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

Description 22/1551-AVA 901 33/3 Uen D

IPWorks Network Connectivity Overview for VMware

Contents
1 Introduction
1.1 Prerequisites
1.2 Related Information

2 IPWorks VNF Network Reference Setup

2.1 Logical Network Setup

3 Network Connectivity
3.1 External Network Connectivity
3.1.1 External VLANs
3.1.2 External IP Networks
3.1.3 Exported IP Addresses
3.2 Internal Network Connectivity
3.2.1 Internal VLANs
3.2.2 Internal IP Addresses

4 Example IP Connectivity
4.1 L2 Network Connectivity Configuration
4.2 L3 Network Connectivity Configuration

Reference
List

about:blank 1/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

1 Introduction
This document provides a logical description of IPWorks VNF networking requirements.

This document is applicable for both Centralized User Database (CUDB) and Cloud Core Data-Storage Manager (CCDM), all
the CUDB shown below can be understood as CCDM.

1.1 Prerequisites
This section states the prerequisites that must be fulfilled:

– The VMware framework including hardware and relevant software components are already installed.
– The customer has a deep understanding of the cloud infrastructure on which IPWorks VNF is to be deployed.
– The customer has a deep understanding of IPWorks. The document IPWorks Technical Description has been read
and fully understood.

1.2 Related Information

Trademark information, typographic conventions, and a definition and explanation of acronyms and terminology can be
found in the following documents:

– Trademark Information
– Typographic Conventions
– Glossary of Terms and Acronyms

All configurations throughout this document, all the templates and examples are referred to:

IPWorks configuration: 4 VMs (2 SCs + 2 PLs)

about:blank 2/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

2 IPWorks VNF Network Reference Setup

The IPWorks VNF network consists of several logical networks. This document proposes a reference logical network setup
for IPWorks VNF, which is realized by the virtual networks that are listed in this document.

The reason for using different logical networks is to enable logic separation between different functions owing to, for
example, security reasons and traffic control.

It is not mandatory to use the reference logical network setup described in this document to deploy the IPWorks VNF.

The logical network setup can be altered depending on deployment-specific requirements. Any logical network setup other
than the IPWorks reference logical network setup is not elaborated further in this document according to customer site
environment.

2.1 Logical Network Setup

The IPWorks VNF exposes several network interfaces. These interfaces expose IPWorks functionality, or are used by
IPWorks to access external network functions, for example Network Time Protocol (NTP). In the reference network setup
of the IPWorks VNF, one or more of these network interfaces is allocated to a virtual network.

The following logical networks are part of the IPWorks reference network setup. This document assumes that the same
logical networks exist in an operator network, and that the operator requires that the IPWorks VNF is being connected to
these existing logical networks:

– Operation and Maintenance Network (OAM network and Provisioning network)

– Signaling Network (DNS/ENUM/AAA traffic)
– Data Network (LDAP between IPWorks and CUDB and SOAP traffic between IPWorks and PG)
– Internal Network (IPWorks VNF internal Network for internal DHCP, TFTP, NFS and so on and it does not connect to
any external network)

The issue about which IPWorks VNF interfaces are exposed in each network is described behind in the document. It is
outside the scope of this document to show how other network entities are connected to the listed logical networks.

Figure 1 shows an overview of the IPWorks VNF configuration, the associated pool allocations (profiles), and the logical
network included in the reference logical network setup.

about:blank 3/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

Figure 1 IPWorks VNF Logical Network Setup

Each logical network is realized using one or more virtual networks. This document does not describe how virtual networks
and virtual Routing Functions are realized by the VMware infrastructure.

Note: For IPWorks VNF, scaling-out operation can be performed to increase the number of Payload VMinstances. The
scaled PL VMs have the same external network as the PL-3 and PL-4. They do not have difference on the
network. The new PL will be put into the original network.

about:blank 4/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

3 Network Connectivity
The VMware network infrastructure components provide redundancy for IPWorks VNF. The active IPWorks infrastructure
consists of two VSwitches: VSwitch1 and VSwitch2.

Figure 2 IPWorks Network Connectivity

The Internal Network here means the network between IPWorks VNF and both VSwitches. And the External Network here
means the network between both VSwitch and other customer switch and router equipment.

The VSwitches provides the following L3 and L3 network function:

– Handling DNS/ENUM/AAA traffic and SS7 traffic.

– Handling LDAP and SOAP traffic.
– Handling OAM and provision traffic.

3.1 External Network Connectivity

This section specifies how the IPWorks VNF is connected to the external or customer network. All the described networks
and IP addresses are routable through the customer network. Before starting to configure the IPWorks VNF network, all
the details (IP addresses, network, VLAN tags, and so on) referenced in this section must be agreed with the customer. In
general, all VLANs are tagged unless stated otherwise.

3.1.1 External VLANs

This section lists the external VLAN used in the IPWorks VNF network.

about:blank 5/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware
There are four kinds of external VLANs in IPWorks VNF:

– Signaling traffic: DNS/ENUM/AAA/SS7 traffic (SIG_CN_SP1)

– DATA traffic: including SOAP notifications from the CUDB and LDAP traffic between IPWorks VNF and CUDB
(SIG_DATA_SP1)
– OAM traffic (OM_CN_SP1)
– Provisioning traffic (OM_CN_SP2)

3.1.2 External IP Networks

Table 1 lists all the external networks and VLANs for IPworks. The GW_ip in the table is external gateway IP addresses.

Note: In subsequent sections, the value with bracket <> means that the customer must set the value to the variant.

Table 1 External Network and VLANs

Network Network Configuration Description

OAM network OM_CN_SP1 VLAN name for OAM network to customer network
<OM_CN_SP1_VID> VLAN IP for OM_CM_SP1 to be defined both in internal network and
(OM_CN_SP1: between VYOS and customer network router
site switch)
<OM_CN_SP1_VSW1_IP> Gateway for customer network for OAM towards IPWorks on vswitch1
<OM_CN_SP1_VSW2_IP> Gateway for customer network for OAM towards IPWorks on vswitch2
<OM_CN_SP1_VRRP_IP> VRRP address used as the gateway for customer network for OAM towards
IPWorks
<OM_CN_SP1_VRRP_GW_IP> External gateway for OAM traffic on OM_CN_SP1 from both vswitches
Provisioning network OM_CN_SP2 VLAN name for provisioning traffic to customer network
<OM_CN_SP2_VID> VLAN ID for OM_CN_SP2 to be defined both in internal network and
(OM_CN_SP2: between VYOS and customer network router
site switch)
<OM_CN_SP2_VSW1_IP> Gateway for customer network for provisioning traffic towards IPWorks on
vswitch1
<OM_CN_SP2_VSW2_IP> Gateway for customer network for provisioning traffic towards IPWorks on
vswitch2
<OM_CN_SP2_VRRP_IP> VRRP address used as gateway for customer network for provisioning traffic
towards IPWorks
<OM_CN_SP2_VRRP_GW_IP> External gateway for provisioning traffic on OM_CN_SP2 from both
vswitches
Sig traffic network SIG_CN_SP1 VLAN name for DNS/ENUM/AAA traffic network to customer network
<SIG_CN_SP1_VID> VLAN ID for SIG_CN_SP1 to be defined both in internal network and
(between VYOS and site switch) customer network router
<SIG_CN_SP1_VSW1_IP> Gateway for customer network for DNS/ENUM/AAA traffic towards IPWorks
on vswitch1
<SIG_CN_SP1_VSW2_IP> Gateway for customer network for DNS/ENUM/AAA traffic towards IPWorks
on vswitch2
<SIG_CN_SP1_VRRP_IP> VRRP address used as gateway for customer network for DNS/ENUM/AAA
traffic towards IPWorks
<SIG_CN_SP1_VRRP_GW_IP> External gateway for DNS/ENUM/AAA traffic on SIG_CN_SP1 from both
vswitches
Sig data network SIG_DATA_SP1 VLAN name for LDAP/SOAP traffic(2) network to customer network
<SIG_DATA_SP1_VID> VLAN ID for SIG_DATA_SP1 to be defined both in internal network and
(between VYOS and site switch) customer network router
<SIG_DATA_SP1_VSW1_IP> Gateway for customer network for LDAP/SOAP traffic towards IPWorks on
vswitch1
<SIG_DATA_SP1_VSW2_IP> Gateway for customer network for LDAP/SOAP traffic towards IPWorks on
vswitch2
<SIG_DATA_SP1_VRRP_IP> VRRP address used as gateway for customer network for LDAP/SOAP traffic
towards IPWorks
<SIG_DATA_SP1_VRRP_GW_IP> External gateway for LDAP/SOAP traffic on SIG_DATA_SP1 from both
vswitches

about:blank 6/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

3.1.3 Exported IP Addresses

In normal conditions, the traffic sourced by the VIPs (see Table 2) can exit from either one of the vswitch. That is, both
vswitches are active for packets sourced by IPWorks. The issue about which router is going to be used to forward an IP
packet is determined by the IPWorks eVIP application and bond interface status.

For OAM and provisioning traffic, IPWorks does not use eVIP. IPWorks uses movable IP (MIP) for OAM related traffics.

Table 2 lists the OAM MIP addresses required by IPWorks VNF and the eVIP addresses required by IPWorks VNF different
traffics.

Table 2 Address of OAM MIP and eVIP

External IPs Network Parameters Description
Public Exported IP address <MIP_OAM_IP> Movable IP address for System management and OSS traffic, this MIP belongs to
IPW_OM_SP1 network
<MIP_PROV_IP> Moveable IP address for provisioning traffic (IPWCLI), this MIP belongs to IPW_OM_SP2
network
<MIP_PROV1_IP> Moveable IP address for EDAAgent, this MIP belongs to IPW_OM_SP2 network. If this
configuration is not needed, the value should be the same as <MIP_PROV_IP>.
<MIP_PROV2_IP> Moveable IP address for NPSOAP traffic, this MIP belongs to IPW_OM_SP2 network. If
this configuration is not needed, the value should be the same as <MIP_PROV_IP>.
<VIP_TRF_IP1> VIP address for DNS/ENUM/AAA traffic
<VIP_TRF_IP2> VIP address for AAA traffic
<VIP_SS7_IP1> VIP address for SS7 traffic for PL
<VIP_SS7_IP2> VIP address for SS7 traffic for PL
<VIP_DATA_IP> VIP addresses for LDAP/SOAP traffic (1)

(1) including SOAP notification from the CUDB related to data changes

3.2 Internal Network Connectivity

The Tenant Internal networks here are not only the IPWorks VNF internal network (which is used for IPWorks cluster nodes
internal communication for DHCP/TFTP/NFS/TIPC and so on), but also the network connectivity for IPWorks VNF to
communicate with external network.

3.2.1 Internal VLANs

This section specifies how the IPWorks VNF is connected in the internal network before connecting to external or customer
network.

In general, all VLANs are tagged unless stated otherwise.

There are five kinds of internal VLANs in IPWorks VNF:

– Signaling traffic: DNS/ENUM/AAA/SS7 traffic (IPW_SIG_SP1)

– DATA traffic: including SOAP notifications from the CUDB and LDAP traffic between IPWorks VNF and CUDB
(IPW_DATA_SP1)
– OAM traffic (IPW_OM_SP1)
– Provisioning and SQL data replication traffic (IPW_OM_SP2)
– Internal traffic (IPW_INT_SP)

3.2.2 Internal IP Addresses

Table 3 lists all the internal networks and VLANs for IPWorks. The GW_IP in the table is internal gateway IP addresses.

about:blank 7/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware
Table 3 Internal IP Address
Networks Network Configuration Description
IPW_OM_SP1 VLAN name for OAM network to site router network.
<IPW_OM_SP1_NW> Network CIDR for IPW_OM_SP1 network
<IPW_OM_SP1_VID> VLAN ID for IPW_OM_SP1 to be defined in tenant internal network
<IPW_OM_SP1_VSW1_IP> Vswitch1 IP which belongs to IPW_OM_SP1 network
OAM network
<IPW_OM_SP1_VSW2_IP> Vswitch2 IP which belongs to IPW_OM_SP1 network
(IPW_OM_SP1)
<IPW_OM_SP1_SC1_IP> SC1 IP in IPW_OM_SP1
<IPW_OM_SP1_SC2_IP> SC2 IP in IPW_OM_SP1
<MIP_OAM_IP> The MIP IP belongs to IPW_OM_SP1 network
<IPW_OM_SP1_VRRP_GW_IP> Gateway for IPW_OM_SP1 from IPWorks VNF towards both vswitches
IPW_OM_SP2 VLAN name for provisioning and SQL data replication network to site router network
<IPW_OM_SP2_NW> Network CIDR for IPW_OM_SP2 network
<IPW_OM_SP2_VID> VLAN ID for IPW_SIG_SP2 to be defined in tenant internal network
<IPW_OM_SP2_VSW1_IP> Vswitch1 IP which belongs to IPW_OM_SP2 network
Provisioning and SQL <IPW_OM_SP2_VSW2_IP> Vswitch2 IP which belongs to IPW_OM_SP2 network
data replication network
(IPW_OM_SP2) <IPW_OM_SP2_SC1_IP> SC1 IP in IPW_OM_SP2
<IPW_OM_SP2_SC2_IP> SC2 IP in IPW_OM_SP2
<MIP_PROV_IP> The MIP IP belongs to IPW_OM_SP2 network
<MIP_PROV1_IP> The MIP IP belongs to IPW_OM_SP2 network
<IPW_OM_SP2_VRRP_GW_IP> Gateway for IPW_OM_SP2 from IPWorks VNF towards both vswitches
IPW_SIG_SP1 VLAN name for IPWorks traffic network to left and right network.
<IPW_SIG_SP1_NW> Network CIDR for IPW_SIG_SP1 network
<IPW_SIG_SP1_VID> VLAN ID for IPW_SIG_SP1 to be defined in internal network
<IPW_SIG_SP1_VRRP_GW_IP> Gateway for IPW_SIG_SP1 from IPWorks VNF towards both vswitches
Sig traffic network <IPW_SIG_SP1_VSW1 _IP> Vswitch1 IP which belongs to IPW_SIG_SP1 network
(IPW_SIG_SP1) <IPW_SIG_SP1_VSW2 _IP> Vswitch2 IP which belongs to IPW_SIG_SP1 network
<IPW_SIG_SP1_FEE1_IP> IPWorks VNF resilient FEE IP Addresses for IPW_SIG_SP1 network
<IPW_SIG_SP1_FEE2_IP> IPWorks VNF resilient FEE IP Addresses for IPW_SIG_SP1 network
<IPW_SIG_SP1_FEE3_IP> IPWorks VNF resilient FEE IP Addresses for IPW_SIG_SP1 network
<IPW_SIG_SP1_FEE4_IP> IPWorks VNF resilient FEE IP Addresses for IPW_SIG_SP1 network
IPW_DATA_SP1 VLAN name for LDAP/SOAP traffic network to left and right network.
<IPW_DATA_SP1_NW> Network CIDR for IPW_DATA_SP1 network
<IPW_DATA_SP1_VID> VLAN ID for IPW_DATA_SP1 to be defined in internal network
<IPW_DATA_SP1_VRRP_GW_IP> Gateway for IPW_DATA_SP1 from IPWorks VNF towards both vswitches
<IPW_DATA_SP1_VSW1_IP> Vswitch1 IP which belongs to IPW_DATA_SP1
<IPW_DATA_SP1_VSW2_IP> Vswitch2 IP which belongs to IPW_DATA_SP1
Sig data network
IPWorks VNF resilient FEE IP Addresses for IPW_DATA_SP1 network. For details, refer to
(IPW_DATA_SP1) <IPW_DATA_SP1_FEE1_IP>
the section Resilient FEE IP Addresses in eVIP Internetworking Reference [5].
IPWorks VNF resilient FEE IP Addresses for IPW_DATA_SP1 network. For details, refer to
<IPW_DATA_SP1_FEE2_IP>
the section Resilient FEE IP Addresses in eVIP Internetworking Reference [5].
IPWorks VNF resilient FEE IP Addresses for IPW_DATA_SP1 network. For details, refer to
<IPW_DATA_SP1_FEE3_IP>
the section Resilient FEE IP Addresses in eVIP Internetworking Reference [5].
IPWorks VNF resilient FEE IP Addresses for IPW_DATA_SP1 network. For details, refer to
<IPW_DATA_SP1_FEE4_IP>
the section Resilient FEE IP Addresses in eVIP Internetworking Reference [5].

about:blank 8/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

4 Example IP Connectivity
Since L2 configuration is much more specified to the hardware, and the L3 is more general, in this section, it only provides
an IP connectivity for IPWorks VNF.

4.1 L2 Network Connectivity Configuration

Table 4 External Network Configuration

Network Network Configuration

OAM Network <OM_CN_SP1_VID> = 430
<OM_CN_SP1_VSW1_IP> = 10.196.249.109
<OM_CN_SP1_VSW2_IP> = 10.196.249.110
<OM_CN_SP1_VRRP_IP> = 10.196.249.108
<OM_CN_SP1_VRRP_GW_IP> = 10.196.249.105
Provisioning network <OM_CN_SP2_VID> = 438
<OM_CN_SP2_VSW1_IP> = 10.196.249.173
<OM_CN_SP2_VSW2_IP> = 10.196.249.174
<OM_CN_SP2_VRRP_IP> = 10.196.249.172
<OM_CN_SP2_VRRP_GW_IP> = 10.196.249.169
Sig traffic network <SIG_CN_SP1_VID> = 484
<SIG_CN_SP1_VSW1_IP> = 10.196.251.29
<SIG_CN_SP1_VSW2_IP> = 10.196.251.30
<SIG_CN_SP1_VRRP_IP> = 10.196.251.28
<SIG_CN_SP1_VRRP_GW_IP> = 10.196.251.25
Sig data network <SIG_DATA_SP1_VID> = 451
<SIG_DATA_SP1_VSW1_IP> = 10.196.250.21
<SIG_DATA_SP1_VSW2_IP> = 10.196.250.22
<SIG_DATA_SP1_VRRP_IP> = 10.196.250.20
<SIG_DATA_SP1_VRRP_GW_IP> = 10.196.250.17

Table 5 Internal Network Configuration

Networks Network Configuration

OAM network <IPW_OM_SP1_NW> = 10.196.245.48/28
<IPW_OM_SP1_VID> = 363
<IPW_OM_SP1_VSW1_IP> = 10.196.245.50
<IPW_OM_SP1_VSW2_IP> = 10.196.245.51
<IPW_OM_SP1_SC1_IP> = 10.196.245.52
<IPW_OM_SP1_SC2_IP> = 10.196.245.53
<MIP_OAM_IP> = 10.196.245.54
<IPW_OM_SP1_VRRP_GW_IP> = 10.196.245.49
Provisioning and SQL data replication <IPW_OM_SP2_NW> = 10.196.245.176/28
network <IPW_OM_SP2_VID> = 370
<IPW_OM_SP2_VSW1_IP> = 10.196.245.178
<IPW_OM_SP2_VSW2_IP> = 10.196.245.179
<IPW_OM_SP2_SC1_IP> = 10.196.245.180

about:blank 9/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

<IPW_OM_SP2_SC2_IP> = 10.196.245.181
<MIP_PROV_IP> = 10.196.245.182
<MIP_PROV1_IP> = 10.196.245.183
<IPW_OM_SP2_VRRP_GW_IP> = 10.196.245.177
Sig traffic network <IPW_SIG_SP1_NW> = 192.168.19.128/26
<IPW_SIG_SP1_VID> = 1484
<IPW_SIG_SP1_VRRP_GW_IP> = 192.168.19.129
<IPW_SIG_SP1_VSW1 _IP> = 192.168.19.130
<IPW_SIG_SP1_VSW2 _IP> = 192.168.19.131
<IPW_SIG_SP1_FEE1_IP> = 192.168.19.132
<IPW_SIG_SP1_FEE2_IP> = 192.168.19.133
<IPW_SIG_SP1_FEE3_IP> = 192.168.19.134
<IPW_SIG_SP1_FEE4_IP> = 192.168.19.135
Sig data network <IPW_DATA_SP1_NW> = 192.168.2.128/26
<IPW_DATA_SP1_VID> = 1451
<IPW_DATA_SP1_VRRP_GW_IP> = 192.168.2.129
<IPW_DATA_SP1_VSW1_IP> = 192.168.2.130
<IPW_DATA_SP1_VSW2_IP> = 192.168.2.131
<IPW_DATA_SP1_FEE1_IP> = 192.168.2.132
<IPW_DATA_SP1_FEE2_IP> = 192.168.2.133
<IPW_DATA_SP1_FEE3_IP> = 192.168.2.134
<IPW_DATA_SP1_FEE4_IP> = 192.168.2.135

4.2 L3 Network Connectivity Configuration

Table 6 VSwitch1 Static Routing

Virtual Router Destination Next-hop VLAN

sig_cn_sp This default route covers all <SIG_CN_SP1_VRRP_GW_IP> (VRRP) <SIG_CN_SP1_VID>=484
DNS/ENUM/AAA/SS7 traffic from = 10.196.251.25
IPWorks VNF to external.
<VIP_TRF_IP1> <IPW_SIG_SP1_FEE1_IP>= <IPW_SIG_SP1_VID>=1484
192.168.19.132

<VIP_TRF_IP2> <IPW_SIG_SP1_FEE2_IP>=
192.168.19.133

VIP_SIG_SS7_IP1 <IPW_SIG_SP1_FEE3_IP>=
192.168.19.134
VIP_SIG_SS7_IP2
<IPW_SIG_SP1_FEE4_IP>=
192.168.19.135
sig_data_sp This default route covers all LDAP <SIG_DATA_SP1_VRRP_GW_IP>= <SIG_DATA_SP1_VID>=451
traffic from IPWorks VNF to external. 10.196.250.17
<VIP_DATA_IP> <IPW_DATA_SP1_FEE1_IP>= <IPW_DATA_SP1_VID>=
192.168.2.132 1451

<IPW_DATA_SP1_FEE2_IP>=
192.168.2.133

<IPW_DATA_SP1_FEE3_IP>=
192.168.2.134

<IPW_DATA_SP1_FEE4_IP>=
192.168.2.135

about:blank 10/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware
om_cn_sp These static routes cover NTP, SNMP, <OM_CN_SP1_VRRP_GW_IP>= <OM_CN_SP1_VID>= 430
OAM, provisioning, and SQL data 10.196.249.105
replication traffic from IPWorks VNF to <OM_CN_SP2_VID>= 438
external.
<MIP_OAM_IP> <IPW_OM_SP1_VSW1_IP>= <IPW_OM_SP1_VID>= 363
10.196.245.50
<MIP_PROV_IP> <IPW_OM_SP2_ VSW1 _IP> = <IPW_OM_SP2_VID>= 370
10.196.245.178
<MIP_PROV1_IP> <IPW_OM_SP2_ VSW1 _IP> = <IPW_OM_SP2_VID>= 370
10.196.245.179

Table 7 VSwitch2 Static Routing

Virtual Router Destination Next-hop VLAN

sig_cn_sp This default route covers all <SIG_CN_SP1_VRRP_GW_IP> (VRRP) = <SIG_CN_SP1_VID>=484
DNS/ENUM/AAA/SS7 traffic from 10.196.251.25
IPWorks VNF to external.
<VIP_TRF_IP1> <IPW_SIG_SP1_FEE1_IP>= 192.168.19.132 <IPW_SIG_SP1_VID>=1484

<VIP_TRF_IP2> <IPW_SIG_SP1_FEE2_IP>= 192.168.19.133

VIP_SIG_SS7_IP1
<IPW_SIG_SP1_FEE3_IP>= 192.168.19.134
VIP_SIG_SS7_IP2
<IPW_SIG_SP1_FEE4_IP>= 192.168.19.135
sig_data_sp This default route covers all LDAP traffic <SIG_DATA_SP1_VRRP_GW_IP>= <SIG_DATA_SP1_VID>=451
from IPWorks VNF to external. 10.196.250.17
<VIP_DATA_IP> <IPW_DATA_SP1_FEE1_IP>= 192.168.2.132 <IPW_DATA_SP1_VID>= 1451

<IPW_DATA_SP1_FEE2_IP>= 192.168.2.133

<IPW_DATA_SP1_FEE3_IP>= 192.168.2.134

<IPW_DATA_SP1_FEE4_IP>= 192.168.2.135
om_cn_sp These static routes cover NTP, SNMP, <OM_CN_SP1_VRRP_GW_IP>= <OM_CN_SP1_VID>= 430
OAM, provisioning, and SQL data 10.196.249.105
replication traffic from IPWorks VNF to <OM_CN_SP2_VID>= 438
external.
<MIP_OAM_IP> <IPW_OM_SP1_VSW1_IP>= 10.196.245.51 <IPW_OM_SP1_VID>= 363
<MIP_PROV_IP> <IPW_OM_SP2_ VSW1 _IP> = 10.196.245.179 <IPW_OM_SP2_VID>= 370
<MIP_PROV1_IP> <IPW_OM_SP2_ VSW1 _IP> = 10.196.245.179 <IPW_OM_SP2_VID>= 370

about:blank 11/12
3/27/24, 3:05 PM IPWorks Network Connectivity Overview for VMware

Reference List
Ericsson Documents
[1] Trademark Information.
[2] Typographic Conventions.
[3] Glossary of Terms and Acronyms.
[4] IPWorks Technical Description.
[5] eVIP Internetworking, 1/155 19-APR 901 0467/3 Uen

Legal | © Ericsson AB 2019, 2020, 2021

Copyright © Ericsson AB 2019, 2020, 2021. All rights reserved. No part of this document may be reproduced in any form
without the written permission of the copyright owner.

Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology,
design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the
use of this document.

Trademarks All trademarks mentioned herein are the property of their respective owners. These are shown in the document
Trademark Information.

about:blank 12/12