BSP 8100 Network Configuration Guide

Ericsson Service-Aware Policy Controller

1 BSP 8100 Network Configuration Guide Introduction

This document provides information to define the hardware, software and network components, and the network configuration needed to run the SAPC in a blades BSP system.

2 BSP 8100 Network Configuration Guide Overview

This section provides an overview of the hardware and software components used to configure the SAPC internal and external networks, as well as a general network description.

The configuration described here applies to BSP 8100 Ericsson Blade System. For other vendor blade systems similar hardware functional elements must be considered:

Hardware components
- CMXs constitute the cluster 10-GB backplane and work as routers and switches between the different blades and the external network.
- SCXs constitute the cluster 1-GB backplane and work as switches for booting, scaling, and OAM purposes between the different blades and the external network.
- Blade system with at least four blades.
Software components
- BSP software R12.0.1.
- SUSE Linux Enterprise Server, SLES with KVM.
- The SAPC software.

A blade system is a hardware system with one complete SAPC running. Each blade has one different role with the following distribution:

SC-1 and SC-2 are the system controllers (SCs). The Operation and Maintenance (OAM) traffic is done through these blades. They are virtualized.
PL-x is the traffic payload in the basic scenario. PCC deployment traffic (such as Gx, Rx) is handled through these blades. These machines are not virtualized and run directly in the blade hardware.

Attention!

The blade system can have a variable number of blades. In this network configuration guide, three scenarios are explained. A first scenario with four blades, minimum deployment scenario. Then a scenario of one subrack (12 blades) and finally a complete cabinet scenario with three subracks (36 blades). Depending on the number of blades and the delivery needs (external database, geographical redundancy or traffic separation), follow the most adequate scenario. In all scenarios, the 1-GB interfaces are connected to the SCX while the 10-GB interfaces are connected to the CMX.

Refer to SAPC Network Description.

2.1 BSP 8100 Minimal Configuration. Four Physical Blades

In this first scenario, the two first blades are system controllers and the two next blades are traffic payloads.

2.1.1 BSP 8100 System Controller Blades Minimal Configuration

Figure 1 Minimal Configuration. System Controllers

System controllers are virtualized, so virtual bridges are defined.

Bridge br_mgmt is used for management purposes and connects the eth2 of the Virtual Machines with the eth2 and eth3 of the physical blades through a bond to provide High Availability for the 1-GB backplane.
Bridge br_bp0 and br_bp1 are the 10-GB backplane bridges which connect the eth0 and the eth1 of the Virtual Machines with the physical blades. A bond is created between these eth0 and eth1 interfaces of the Virtual Machines to provide High Availability for the 10-GB backplane.

System controllers are connected to the external network through VIP FEE. These connections are used for load balancing purposes through a virtual IP. For this purpose OAM VLANs are used. System controllers also provide an external OAM IP address independent of the VIP-OAM.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.1.2 BSP 8100 Payload Blades Minimal Configuration

Figure 2 Minimal Configuration. Traffic Payloads

Payloads are not virtualized, so no virtual bridges are defined. A bond is created between eth0 and eth1 to provide High Availability for the 10-GB backplane. Besides, another bond is created between eth2 and eth3 to provide High Availability for the 1-GB backplane.

Payloads are connected to the external network through VIP FEEs. Four VIPs are defined for Traffic, External Database, GeoRed (Replication), and Traffic Separation in case that traffic exists, and additional FEEs can be defined. These connections are used for load balancing purposes through a virtual IP.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.2 BSP 8100 Single Subrack Configuration. 12 Physical Blades

The two first blades are system controllers and the rest blades are traffic payloads. Each blade has a different role depending on the needs.

2.2.1 BSP 8100 System Controller Blades Subrack Configuration

Configuration applies the same as in BSP 8100 System Controller Blades Minimal Configuration.

2.2.2 BSP 8100 Traffic Blades Subrack Configuration

Traffic payload blades follow different network configuration depending on the customer needs. This chapter describes a scenario with all functionality. Depending on the customer needs, PLs are configured accordingly.

PL-3 and PL-4 are used for traffic purposes in all scenarios. All external diameter traffic is received through these two.
In case external database is configured, the next two PLs are used for this purpose. PL-5 and PL-6 in this example scenario.
In case GeoRed is configured, the next two PLs are used for this purpose. PL-7 and PL-8 in this example scenario.
In case traffic separation is configured, the next two PLs are used for this purpose. PL-9 and PL-10 in this example scenario.
Rest of the PLs have no external communication.

2.2.2.1 Traffic Payload Blades

Figure 3 Subrack Configuration. Traffic Payloads

Traffic payloads are not virtualized, so no virtual bridges are defined. A bond is created between eth0 and eth1 to provide High Availability for the 10-GB backplane. Besides, another bond is created between eth2 and eth3 to provide High Availability for the 1-GB backplane.

Traffic payloads are connected to the external network through VIP Traffic FEEs. These connections are used for load balancing purposes through a virtual IP.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.2.2.2 External Database Payload Blades

Figure 4 Subrack Configuration. External Database Payloads

External database payloads are not virtualized, so no virtual bridges are defined. A bond is created between eth0 and eth1 to provide High Availability for the 10-GB backplane. Besides, another bond is created between eth2 and eth3 to provide High Availability for the 1-GB backplane.

External database payloads are connected to the external network through VIP ExtDB FEEs. These connections are used for load balancing purposes through a virtual IP.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.2.2.3 GeoRed Payload Blades

Figure 5 Subrack Configuration. GeoRed Payloads

GeoRed payloads are not virtualized, so no virtual bridges are defined. A bond is created between eth0 and eth1 to provide High Availability for the 10-GB backplane. Besides, another bond is created between eth2 and eth3 to provide High Availability for the 1-GB backplane.

GeoRed payloads are connected to the external network through VIP Replication FEEs. These connections are used for load balancing purposes through a virtual IP.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.2.2.4 Traffic Separation Payload Blades

Figure 6 Subrack Configuration. Traffic Separation Payloads

Traffic separation payloads are not virtualized, so no virtual bridges are defined. A bond is created between eth0 and eth1 to provide High Availability for the 10-GB backplane. Besides, another bond is created between eth2 and eth3 to provide High Availability for the 1-GB backplane.

Traffic separation payloads are connected to the external network through VIP Replication FEEs. These connections are used for load balancing purposes through a virtual IP.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.2.2.5 Remaining Payload Blades

Figure 7 Subrack Configuration. Remaining Payload Blades

Remaining payloads are not virtualized, so no virtual bridges are defined. A bond is created between eth0 and eth1 to provide High Availability for the 10-GB backplane. Besides, another bond is created between eth2 and eth3 to provide High Availability for the 1-GB backplane.

Internal connectivity is done through the 10 GB interfaces connected to both CMX routers (which also provide switching capabilities). Both CMXs are interconnected to achieve High Availability.

2.3 BSP 8100 Whole Rack Configuration. 36 Physical Blades

The two first blades are system controllers and the rest blades are traffic payloads. The installation described in BSP 8100 Single Subrack Configuration. 12 Physical Blades has to be done for the first subrack. In this chapter, additional networking is included for the additional second and third subracks.

Warning!

Additional FEEs are needed for each type of traffic for the second and third subracks. For a second subrack, in a scenario with External Database, GeoRed, and Traffic Separation, apart from normal diameter traffic, PL-15 and PL-16 are used for Traffic FEEs, PL-17 and PL-18 for External Database FEEs, PL-19 and PL-20 for GeoRed FEEs, and PL-21 and PL-22 for Traffic Separation FEEs. For a third subrack, in a scenario with External Database, GeoRed, and Traffic Separation, apart from normal diameter traffic, PL-27 and PL-28 are used for Traffic FEEs, PL-29 and PL-30 for External Database FEEs, PL-31 and PL-32 for GeoRed FEEs, and PL-33 and PL-34 for Traffic Separation FEEs. Same configuration described above is applied.

2.3.1 BSP 8100 Traffic Blades Whole Rack Configuration

Apart from the traditional networking we do as the other subrack, an extra networking to intercommunicate the second, and third subracks with the first one is needed.

2.3.1.1 Non-Front End Blades

For non-front end blades, the following extra networking must be done.

Figure 8 Whole Rack Configuration. Non-Front End Payload Blades

2.3.1.2 Front End Payload Blades

Figure 9 Whole Rack Configuration. Front End Payload Blades

Additional front end payload blades are needed in the new subracks. New FEEs are created in that case as Figure 9 shows.

3 BSP 8100 Networks Allocation

This section specifies how the SAPC is connected to the network, detailing all the VLANs and networks. The examples are based on IPv4, but IPv6 is also supported, except for the Blade Server Platform (BSP) northbound interface and cluster internal traffic networks, where only IPv4 is supported, according to BSP RDA (Reference Deployment Architecture). Before starting to configure the SAPC network, agree with the customer on all the details (IP addresses, Network, VLAN Tags, and so on) referenced in this section. Although most of the references in this document mention only one additional traffic separation network, there are no logical restrictions on the number of traffic networks and the corresponding ALBs to be defined.

All VLANs are tagged unless explicitly stated.

3.1 BSP 8100 VLANs

Table 1 VLANs for One Subrack
VLAN Name	VLAN ID	Interface	Ports	Comments	Attributes
sapc_om2_sp	137	Blade: mgmt0	SCX 0-X: BP1, BP3, E3 CMX 0-Y: E3, E4, E5, GE4	SCs only. Hypervisor Management	vlanType = PRIVATE lanTopology = BASE_AND_DATA switchSide = COLLAPSED portAssignment = MANUAL AdditionalPort=0-X:BP1 AdditionalPort=0-X:BP3
sapc_mgmt_sp	138	Blade: mgmt1 VM: eth2	SCX 0-X: BP1, BP3, E3 CMX 0-Y: E3, E4, E5	SCs only. System Management	vlanType = PRIVATE lanTopology = BASE_AND_DATA switchSide = COLLAPSED portAssignment = MANUAL AdditionalPort=0-X:BP1 AdditionalPort=0-X:BP3
sapc_boot_sp	4001	VM: eth2 PL: bond1	SCX 0-X: BPn* (untagged)	LDE Boot and Scaling	vlanType = DEFAULT lanTopology = BASE switchSide = COLLAPSED
sapc_int_sp	4003	bond0	CMX 0-Y: BPn* (untagged), E3, E4	Cluster Internal	vlanType = DEFAULT lanTopology = DATA switchSide = COLLAPSED
sapc_tipc_pdl	100	eth0	CMX 0-26: BPn	Left TIPC	vlanType = PRIVATE lanTopology = DATA switchSide = LEFT
sapc_tipc_pdr	101	eth1	CMX 0-28: BPn	Right TIPC	vlanType = PRIVATE lanTopology = DATA switchSide = RIGHT
sapc_om1_sp1	130	bond0	CMX 0-Y: BP1, E3, E4	eVIP Router Link O&M Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED portAssignment = MANUAL AdditionalBlade=0-1
sapc_om1_sp2	131	bond0	CMX 0-Y: BP3, E3, E4	eVIP Router Link O&M Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED portAssignment = MANUAL AdditionalBlade=0-3
sapc_sig1_sp1	120	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link Signaling Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig1_sp2	121	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link Signaling Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig2_sp1	140	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link LDAP Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig2_sp2	141	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link LDAP Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig3_sp1	150	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link Replication Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig3_sp2	151	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link Replication Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig4_sp1	122	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link Signaling Traffic Rx	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_sig4_sp2	123	bond0	CMX 0-Y: BPn (n not 1 nor 3), E3, E4	eVIP Router Link Signaling Traffic Rx	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED ExcludedBlade=0-1 ExcludedBlade=0-3
sapc_om2_sp1	132	bond0	CMX 0-Y: BP1, E3, E4	eVIP Router Link O&M Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED portAssignment = MANUAL AdditionalBlade=0-1
sapc_om2_sp2	133	bond0	CMX 0-Y: BP3, E3, E4	eVIP Router Link O&M Traffic	vlanType = PRIVATE lanTopology = DATA switchSide = COLLAPSED portAssignment = MANUAL AdditionalBlade=0-3

For multiple subracks, additional ports are added for the previous VLANs.

Table 2 VLANs for Whole Rack
VLAN Name	VLAN ID	Interface	Ports	Comments
sapc_boot_sp	4001	SCs: eth2 PLs: bond1	SCX 0-X: E1, E2 SCX m-X: BPn* (untagged), E1	LDE Boot and Scaling
sapc_int_sp	4003	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn* (untagged), E1	Cluster Internal
sapc_tipc_pdl	100	eth0	CMX 0-26: E1, E2	Left TIPC
sapc_tipc_pdr	101	eth1	CMX 0-28: E1, E2	Right TIPC
sapc_sig1_sp1	120	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link Signaling Traffic
sapc_sig1_sp2	121	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link Signaling Traffic
sapc_sig2_sp1	140	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link LDAP Traffic
sapc_sig2_sp2	141	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link LDAP Traffic
sapc_sig3_sp1	150	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link Replication Traffic
sapc_sig3_sp2	151	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link Replication Traffic
sapc_sig4_sp1	122	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link Signaling Traffic Rx
sapc_sig4_sp2	123	bond0	CMX 0-Y: E1, E2 CMX m-Y: BPn, E1	eVIP Router Link Signaling Traffic Rx

3.2 BSP 8100 IP Addressing

Each SAPC requires a set of IP addresses agreed with the customer before configuring the SAPC.

Table 3 IPv4 Network and VLAN for BSP Management
Network Address	Mask	Type	Usage	VLAN ID	Virtual Router	VLAN Name/Tag
bsp_om_net	/29	Public	BSP Northbound OAM network	4054	dmx_om_vr	%{bsp_om_net}
			Collapsed IP for BSP Northbound OAM			%{bsp_om_addr}
			VRRP IP for BSP Northbound OAM			%{bsp_om_gw}
			CMX26 IP for BSP Northbound OAM			%{bsp_om_cmx26_addr}
			CMX28 IP for BSP Northbound OAM			%{bsp_om_cmx28_addr}
	N/A	N/A	VR ID for BSP Northbound OAM	N/A		%{bsp_om_vrid}
om_sibb_sp_net	N/A	Private	Uplink VLAN connected to external network for BSP Northbound traffic	om_sibb_sp_id	dmx_om_vr	%{om_sibb_sp_id}
	/29		Uplink VRRP IP connected to external network for BSP Northbound traffic			%{om_sibb_sp_addr}
			Uplink CMX26 IP connected to external network for BSP Northbound traffic			%{om_sibb_sp_addr1} with net suffix (CIDR)
			Uplink CMX28 IP connected to external network for BSP Northbound traffic			%{om_sibb_sp_addr2} with net suffix (CIDR)
			Uplink CMX26 gateway for BSP Northbound traffic			%{om_sibb_sp_gw1}
			Uplink CMX28 gateway for BSP Northbound traffic			%{om_sibb_sp_gw2}
	N/A	N/A	Uplink VR ID for BSP Northbound traffic	N/A		%{om_sibb_sp_vrid}

Table 4 IPv4 Network and VLAN for SAPC
Network Address	Mask	Type	Usage	VLAN ID	Virtual Router	VLAN Name/Tag
169.254.69.0	/24	Link-Local	Backplane booting & scaling network	4001	om_cn_sp	sapc_boot_sp
172.16.100.0	/24	Link-Local	Backplane cluster internal communication network	4003	om_cn_sp	sapc_int_sp
192.168.206.4	/30	Private	Cross shelf link internal AS network for signaling traffic	25	sig_cn_1_sp	sig_cn_1_sp_inlcl
sig_cn_1_sp_nlcl_net	/30	Private	Cross shelf link external AS network for signaling traffic	26	sig_cn_1_sp	sig_cn_1_sp_nlcl
			Cross shelf link external AS CMX26 IP for signaling traffic			%{sig_cn_1_sp_nlcl_addr1} without net suffix
			Cross shelf link external AS CMX26 IP for signaling traffic with network suffix			%{sig_cn_1_sp_nlcl_addr1_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for signaling traffic			%{sig_cn_1_sp_nlcl_addr2} without net suffix
			Cross shelf link external AS CMX28 IP for signaling traffic with network suffix			%{sig_cn_1_sp_nlcl_addr2_cidr} with net suffix (CIDR)
192.168.205.4	/30	Private	Cross shelf link internal AS network for signaling 2 traffic	15	sig_cn_2_sp	sig_cn_2_sp_inlcl
sig_cn_2_sp_nlcl_net	/30	Private	Cross shelf link external AS network for signaling 2 traffic	16	sig_cn_2_sp	sig_cn_2_sp_nlcl
			Cross shelf link external AS CMX26 IP for signaling 2 traffic			%{sig_cn_2_sp_nlcl_addr1} without net suffix
			Cross shelf link external AS CMX26 IP for signaling 2 traffic with network suffix			%{sig_cn_2_sp_nlcl_addr1_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for signaling 2 traffic			%{sig_cn_2_sp_nlcl_addr2} without net suffix
			Cross shelf link external AS CMX28 IP for signaling 2 traffic with network suffix			%{sig_cn_2_sp_nlcl_addr2_cidr} with net suffix (CIDR)
192.168.208.4	/30	Private	Cross shelf link internal AS network for OAM traffic	35	om_cn_sp	om_cn_sp_inlcl
om_cn_sp_nlcl_net	/30	Private	Cross shelf link external AS network	36	om_cn_sp	om_cn_sp_nlcl
			Cross shelf link external AS CMX26 IP for OAM traffic			%{om_cn_sp_nlcl_addr1} without net suffix
			Cross shelf link external AS CMX26 IP for OAM traffic with network suffix			%{om_cn_sp_nlcl_addr1_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for OAM traffic			%{om_cn_sp_nlcl_addr2} without net suffix
			Cross shelf link external AS CMX28 IP for OAM traffic with network suffix			%{om_cn_sp_nlcl_addr2_cidr} with net suffix (CIDR)
192.168.207.4	/30	Private	Cross shelf link internal AS network for LDAP traffic	45	sig_data_1_sp	sig_data_1_sp_inlcl
sig_data_1_sp_nlcl_net	/30	Private	Cross shelf link external AS network for LDAP traffic	46	sig_data_1_sp	sig_data_1_sp_nlcl
			Cross shelf link external AS CMX26 IP for LDAP traffic			%{sig_data_1_sp_nlcl_addr1} without net suffix
			Cross shelf link external AS CMX26 IP for LDAP traffic with network suffix			%{sig_data_1_sp_nlcl_addr1_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for LDAP traffic			%{sig_data_1_sp_nlcl_addr2} without net suffix
			Cross shelf link external AS CMX28 IP for LDAP traffic with network suffix			%{sig_data_1_sp_nlcl_addr2_cidr} with net suffix (CIDR)
192.168.209.4	/30	Private	Cross shelf link internal AS network for replication traffic	55	sig_data_2_sp	sig_data_2_sp_inlcl
192.168.204.4	/30	Private	Cross shelf link internal AS network for provisioning traffic	65	om_cn_2_sp	om_cn_2_sp_inlcl
om_cn_2_sp_nlcl_net	/30	Private	Cross shelf link external AS network	66	om_cn_2_sp	om_cn_2_sp_nlcl
			Cross shelf link external AS CMX26 IP for provisioning traffic			%{om_cn_2_sp_nlcl_addr1} without net suffix
			Cross shelf link external AS CMX26 IP for provisioning traffic with network suffix			%{om_cn_2_sp_nlcl_addr1_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for provisioning traffic			%{om_cn_2_sp_nlcl_addr2} without net suffix
			Cross shelf link external AS CMX28 IP for provisioning traffic with network suffix			%{om_cn_2_sp_nlcl_addr2_cidr} with net suffix (CIDR)
192.168.206.1	/32	Private	CMX26 internal AS local address	N/A	sig_cn_1_sp	N/A
192.168.206.2	/32	Private	CMX28 internal AS local address	N/A	sig_cn_1_sp	N/A
192.168.205.1	/32	Private	CMX26 internal AS local address	N/A	sig_cn_2_sp	N/A
192.168.205.2	/32	Private	CMX28 internal AS local address	N/A	sig_cn_2_sp	N/A
192.168.208.1	/32	Private	CMX26 internal AS local address	N/A	om_cn_sp	N/A
192.168.208.2	/32	Private	CMX28 internal AS local address	N/A	om_cn_sp	N/A
192.168.207.1	/32	Private	CMX26 internal AS local address	N/A	sig_data_1_sp	N/A
192.168.207.2	/32	Private	CMX28 internal AS local address	N/A	sig_data_1_sp	N/A
192.168.204.1	/32	Private	CMX26 internal AS local address	N/A	om_cn_2_sp	N/A
192.168.204.2	/32	Private	CMX28 internal AS local address	N/A	om_cn_2_sp	N/A
192.168.209.1	/32	Private	CMX26 internal AS local address	N/A	sig_data_2_sp	N/A
192.168.209.2	/32	Private	CMX28 internal AS local address	N/A	sig_data_2_sp	N/A
N/A	N/A	N/A	TIPC VLAN through left CMX	100	N/A	sapc_tipc_pdl
N/A	N/A	N/A	TIPC VLAN through right CMX	101	N/A	sapc_tipc_pdr
192.168.216.0	/27	Private	eVIP router link for signaling traffic	120	sig_cn_1_sp	sapc_sig1_sp1
192.168.216.32	/27	Private	eVIP router link for signaling traffic	121	sig_cn_1_sp	sapc_sig1_sp2
192.168.218.0	/29	Private	eVIP router link for OAM traffic	130	om_cn_sp	sapc_om1_sp1
192.168.218.8	/29	Private	eVIP router link for OAM traffic	131	om_cn_sp	sapc_om1_sp2
192.168.217.0	/27	Private	eVIP router link for LDAP traffic	140	sig_data_1_sp	sapc_sig2_sp1
192.168.217.32	/27	Private	eVIP router link for LDAP traffic	141	sig_data_1_sp	sapc_sig2_sp2
192.168.219.0	/27	Private	eVIP router link for replication traffic	150	sig_data_2_sp	sapc_sig3_sp1
192.168.219.32	/27	Private	eVIP router link for replication traffic	151	sig_data_2_sp	sapc_sig3_sp2
192.168.220.0	/27	Private	eVIP router link for signaling traffic 2 (Rx)	122	sig_cn_2_sp	sapc_sig4_sp1
192.168.220.32	/27	Private	eVIP router link for signaling traffic 2 (Rx)	123	sig_cn_2_sp	sapc_sig4_sp2
192.168.221.0	/29	Private	eVIP router link for provisioning traffic	132	om_cn_2_sp	sapc_om2_sp1
192.168.221.8	/29	Private	eVIP router link for provisioning traffic	133	om_cn_2_sp	sapc_om2_sp2
192.168.100.0	/24	Private	System Management Network	138	N/A	sapc_mgmt_sp
sapc_om2_sp_net	/29	Public	Hypervisor management network	137	om_cn_sp	sapc_om2_sp
			VRRP IP for hypervisor management			%{sapc_om2_sp_gw}
			CMX26 IP for hypervisor management			%{sapc_om2_sp_cmx26_addr} with net suffix (CIDR)
			CMX28 IP for hypervisor management			%{sapc_om2_sp_cmx28_addr} with net suffix (CIDR)
	N/A	N/A	VR ID for hypervisor management	N/A		%{sapc_om2_sp_vrid}
sapc_sig_cn_1_vip	/32	Public	VIP signaling address	N/A	sig_cn_1_sp	%{sapc_sig_cn_1_vip} with net suffix (CIDR)
sapc_sig_cn_2_vip	/32	Public	VIP signaling 2 (Rx) address	N/A	sig_cn_2_sp	%{sapc_sig_cn_2_vip} with net suffix (CIDR)
sapc_om_cn_vip1	/32	Public	VIP OAM address	N/A	om_cn_sp	%{sapc_om_cn_vip1} with net suffix (CIDR)
sapc_om_cn_vip2	/32	Public	VIP provisioning address	N/A	om_cn_sp	%{sapc_om_cn_vip2} with net suffix (CIDR)
sapc_sig_data_1_vip	/32	Public	VIP LDAP address	N/A	sig_data_1_sp	%{sapc_sig_data_1_vip} with net suffix (CIDR)
sapc_sig_data_2_vip	/32	Public	VIP replication address	N/A	sig_data_2_sp	%{sapc_sig_data_2_vip} with net suffix (CIDR)
sig_cn_1_pr_net	N/A	Private	Uplink VLAN connected to external network for signaling traffic	sig_cn_1_pr_id	sig_cn_1_sp	%{sig_cn_1_pr_id}
	N/A		Uplink OSPF area for signaling traffic ⁽¹⁾			%{sig_cn_1_pr_ospf}
	/29		Uplink CMX26 IP for signaling traffic			%{sig_cn_1_pr_addr1} with net suffix (CIDR)
			Uplink CMX28 IP for signaling traffic			%{sig_cn_1_pr_addr2} with net suffix (CIDR)
			Uplink gateway 1 for signaling traffic ⁽²⁾			%{sig_cn_1_pr_gw1}
			Uplink gateway 2 for signaling traffic ⁽²⁾			%{sig_cn_1_pr_gw2}
sig_cn_2_pr_net	N/A	Private	Uplink VLAN connected to external network for signaling 2 traffic	sig_cn_2_pr_id	sig_cn_2_sp	%{sig_cn_2_pr_id}
	N/A		Uplink OSPF area for signaling 2 traffic ⁽¹⁾			%{sig_cn_2_pr_ospf}
	/29		Uplink CMX26 IP for signaling 2 traffic			%{sig_cn_2_pr_addr1} with net suffix (CIDR)
			Uplink CMX28 IP for signaling 2 traffic			%{sig_cn_2_pr_addr2} with net suffix (CIDR)
			Uplink gateway 1 for signaling 2 traffic ⁽²⁾			%{sig_cn_2_pr_gw1}
			Uplink gateway 2 for signaling 2 traffic ⁽²⁾			%{sig_cn_2_pr_gw2}
om_cn_pr_net	N/A	Private	Uplink VLAN connected to external network for OAM traffic	om_cn_pr_id	om_cn_sp	%{om_cn_pr_id}
	N/A		Uplink OSPF area for OAM traffic ⁽¹⁾			%{om_cn_pr_ospf}
	/29		Uplink CMX26 IP for OAM traffic			%{om_cn_pr_addr1} with net suffix (CIDR)
			Uplink CMX28 IP for OAM traffic			%{om_cn_pr_addr2} with net suffix (CIDR)
			Uplink gateway 1 for OAM traffic ⁽²⁾			%{om_cn_pr_gw1}
			Uplink gateway 2 for OAM traffic ⁽²⁾			%{om_cn_pr_gw2}
om_cn_2_pr_net	N/A	Private	Uplink VLAN connected to external network for provisioning traffic	om_cn_2_pr_id	om_cn_2_sp	%{om_cn_2_pr_id}
	N/A		Uplink OSPF area for provisioning traffic ⁽¹⁾			%{om_cn_2_pr_ospf}
	/29		Uplink CMX26 IP for provisioning traffic			%{om_cn_2_pr_addr1} with net suffix (CIDR)
			Uplink CMX28 IP for provisioning traffic			%{om_cn_2_pr_addr2} with net suffix (CIDR)
			Uplink gateway 1 for provisioning traffic ⁽²⁾			%{om_cn_2_pr_gw1}
			Uplink gateway 2 for provisioning traffic ⁽²⁾			%{om_cn_2_pr_gw2}
sig_data_1_pr_net	N/A	Private	Uplink VLAN connected to external network for LDAP traffic	sig_data_1_pr_id	sig_data_1_sp	%{sig_data_1_pr_id}
	N/A		Uplink OSPF area for LDAP traffic ⁽¹⁾			%{sig_data_1_pr_ospf}
	/29		Uplink CMX26 IP for LDAP traffic			%{sig_data_1_pr_addr1} with net suffix (CIDR)
			Uplink CMX28 IP for LDAP traffic			%{sig_data_1_pr_addr2} with net suffix (CIDR)
			Uplink gateway 1 for LDAP traffic ⁽²⁾			%{sig_data_1_pr_gw1}
			Uplink gateway 2 for LDAP traffic ⁽²⁾			%{sig_data_1_pr_gw2}
sig_data_2_pr_net	N/A	Private	Uplink VLAN connected to external network for replication traffic	sig_data_2_pr_id	sig_data_2_sp	%{sig_data_2_pr_id}
	/29		Uplink CMX26 IP for replication traffic			%{sig_data_2_pr_addr1} with net suffix (CIDR)
			Uplink CMX28 IP for replication traffic			%{sig_data_2_pr_addr2} with net suffix (CIDR)
			Uplink gateway 1 for replication traffic			%{sig_data_2_pr_gw1}
			Uplink gateway 2 for replication traffic			%{sig_data_2_pr_gw2}

(1) This parameter is specific and mandatory only for a GeoRed deployment.

(2) This parameter is specific and mandatory only for a Standalone deployment. BFD enabled is also mandatory on the SRs side to ensure a fast failover recovery.

Table 5 IPv6 Network and VLAN for SAPC
Network Address	Mask	Type	Usage	VLAN ID	Virtual Router	VLAN Name/Tag
fd00:0:0:206::	/64	ULA	Cross shelf link internal AS network for signaling traffic	25	sig_cn_1_sp	sig_cn_1_sp_inlcl
sig_cn_1_sp_nlcl_net	/64	ULA	Cross shelf link external AS network for signaling traffic	26	sig_cn_1_sp	sig_cn_1_sp_nlcl
			Cross shelf link external AS CMX26 IP for signaling traffic			%{sig_cn_1_sp_nlcl_addr1_ipv6} without net suffix
			Cross shelf link external AS CMX26 IP for signaling traffic with network suffix			%{sig_cn_1_sp_nlcl_addr1_ipv6_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for signaling traffic			%{sig_cn_1_sp_nlcl_addr2_ipv6} without net suffix
			Cross shelf link external AS CMX28 IP for signaling traffic with network suffix			%{sig_cn_1_sp_nlcl_addr2_ipv6_cidr} with net suffix (CIDR)
fd00:0:0:205::	/64	ULA	Cross shelf link internal AS network for signaling 2 traffic	15	sig_cn_2_sp	sig_cn_2_sp_inlcl
sig_cn_2_sp_nlcl_net	/64	ULA	Cross shelf link external AS network for signaling 2 traffic	16	sig_cn_2_sp	sig_cn_2_sp_nlcl
			Cross shelf link external AS CMX26 IP for signaling 2 traffic			%{sig_cn_2_sp_nlcl_addr1_ipv6} without net suffix
			Cross shelf link external AS CMX26 IP for signaling 2 traffic with network suffix			%{sig_cn_2_sp_nlcl_addr1_ipv6_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for signaling 2 traffic			%{sig_cn_2_sp_nlcl_addr2_ipv6} without net suffix
			Cross shelf link external AS CMX28 IP for signaling 2 traffic with network suffix			%{sig_cn_2_sp_nlcl_addr2_ipv6_cidr} with net suffix (CIDR)
fd00:0:0:208::	/64	ULA	Cross shelf link internal AS network for OAM traffic	35	om_cn_sp	om_cn_sp_inlcl
om_cn_sp_nlcl_net	/64	ULA	Cross shelf link external AS network	36	om_cn_sp	om_cn_sp_nlcl
			Cross shelf link external AS CMX26 IP for OAM traffic			%{om_cn_sp_nlcl_addr1_ipv6} without net suffix
			Cross shelf link external AS CMX26 IP for OAM traffic with network suffix			%{om_cn_sp_nlcl_addr1_ipv6_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for OAM traffic			%{om_cn_sp_nlcl_addr2_ipv6} without net suffix
			Cross shelf link external AS CMX28 IP for OAM traffic with network suffix			%{om_cn_sp_nlcl_addr2_ipv6_cidr} with net suffix (CIDR)
fd00:0:0:207::	/64	ULA	Cross shelf link internal AS network for LDAP traffic	45	sig_data_1_sp	sig_data_1_sp_inlcl
sig_data_1_sp_nlcl_net	/64	ULA	Cross shelf link external AS network for LDAP traffic	46	sig_data_1_sp	sig_data_1_sp_nlcl
			Cross shelf link external AS CMX26 IP for LDAP traffic			%{sig_data_1_sp_nlcl_addr1_ipv6} without net suffix
			Cross shelf link external AS CMX26 IP for LDAP traffic with network suffix			%{sig_data_1_sp_nlcl_addr1_ipv6_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for LDAP traffic			%{sig_data_1_sp_nlcl_addr2_ipv6} without net suffix
			Cross shelf link external AS CMX28 IP for LDAP traffic with network suffix			%{sig_data_1_sp_nlcl_addr2_ipv6_cidr} with net suffix (CIDR)
fd00:0:0:209::	/64	ULA	Cross shelf link internal AS network for replication traffic	55	sig_data_2_sp	sig_data_2_sp_inlcl
fd00:0:0:204::	/64	ULA	Cross shelf link internal AS network for provisioning traffic	65	om_cn_2_sp	om_cn_2_sp_inlcl
om_cn_2_sp_nlcl_net	/64	ULA	Cross shelf link external AS network	66	om_cn_2_sp	om_cn_2_sp_nlcl
			Cross shelf link external AS CMX26 IP for provisioning traffic			%{om_cn_2_sp_nlcl_addr1_ipv6} without net suffix
			Cross shelf link external AS CMX26 IP for provisioning traffic with network suffix			%{om_cn_2_sp_nlcl_addr1_ipv6_cidr} with net suffix (CIDR)
			Cross shelf link external AS CMX28 IP for provisioning traffic			%{om_cn_2_sp_nlcl_addr2_ipv6} without net suffix
			Cross shelf link external AS CMX28 IP for provisioning traffic with network suffix			%{om_cn_2_sp_nlcl_addr2_ipv6_cidr} with net suffix (CIDR)
fd00::192:168:206:1	/128	ULA	CMX26 internal AS local address	N/A	sig_cn_1_sp	N/A
fd00::192:168:206:2	/128	ULA	CMX28 internal AS local address	N/A	sig_cn_1_sp	N/A
fd00::192:168:205:1	/128	ULA	CMX26 internal AS local address	N/A	sig_cn_2_sp	N/A
fd00::192:168:205:2	/128	ULA	CMX28 internal AS local address	N/A	sig_cn_2_sp	N/A
fd00::192:168:208:1	/128	ULA	CMX26 internal AS local address	N/A	om_cn_sp	N/A
fd00::192:168:208:2	/128	ULA	CMX28 internal AS local address	N/A	om_cn_sp	N/A
fd00::192:168:207:1	/128	ULA	CMX26 internal AS local address	N/A	sig_data_1_sp	N/A
fd00::192:168:207:2	/128	ULA	CMX28 internal AS local address	N/A	sig_data_1_sp	N/A
fd00::192:168:204:1	/128	ULA	CMX26 internal AS local address	N/A	om_cn_2_sp	N/A
fd00::192:168:204:2	/128	ULA	CMX28 internal AS local address	N/A	om_cn_2_sp	N/A
fd00::192:168:209:1	/128	ULA	CMX26 internal AS local address	N/A	sig_data_2_sp	N/A
fd00::192:168:209:2	/128	ULA	CMX28 internal AS local address	N/A	sig_data_2_sp	N/A
fd00:0:0:11::	/64	ULA	eVIP router link for signaling traffic	120	sig_cn_1_sp	sapc_sig1_sp1
fd00:0:0:12::	/64	ULA	eVIP router link for signaling traffic	121	sig_cn_1_sp	sapc_sig1_sp2
fd00:0:0:31::	/64	ULA	eVIP router link for OAM traffic	130	om_cn_sp	sapc_om1_sp1
fd00:0:0:32::	/64	ULA	eVIP router link for OAM traffic	131	om_cn_sp	sapc_om1_sp2
fd00:0:0:15::	/64	ULA	eVIP router link for LDAP traffic	140	sig_data_1_sp	sapc_sig2_sp1
fd00:0:0:16::	/64	ULA	eVIP router link for LDAP traffic	141	sig_data_1_sp	sapc_sig2_sp2
fd00:0:0:17::	/64	ULA	eVIP router link for replication traffic	150	sig_data_2_sp	sapc_sig3_sp1
fd00:0:0:18::	/64	ULA	eVIP router link for replication traffic	151	sig_data_2_sp	sapc_sig3_sp2
fd00:0:0:13::	/64	ULA	eVIP router link for signaling traffic 2 (Rx)	122	sig_cn_2_sp	sapc_sig4_sp1
fd00:0:0:14::	/64	ULA	eVIP router link for signaling traffic 2 (Rx)	123	sig_cn_2_sp	sapc_sig4_sp2
fd00:0:0:33::	/64	ULA	eVIP router link for provisioning traffic	132	om_cn_2_sp	sapc_om2_sp1
fd00:0:0:34::	/64	ULA	eVIP router link for provisioning traffic	133	om_cn_2_sp	sapc_om2_sp2
sapc_sig_cn_1_vip	/128	Public	VIP signaling address	N/A	sig_cn_1_sp	%{sapc_sig_cn_1_vip_ipv6} with net suffix (CIDR)
sapc_sig_cn_2_vip	/128	Public	VIP signaling 2 (Rx) address	N/A	sig_cn_2_sp	%{sapc_sig_cn_2_vip_ipv6} with net suffix (CIDR)
sapc_om_cn_vip1	/128	Public	VIP OAM address	N/A	om_cn_sp	%{sapc_om_cn_vip1_ipv6} with net suffix (CIDR)
sapc_om_cn_vip2	/128	Public	VIP provisioning address	N/A	om_cn_sp	%{sapc_om_cn_vip2_ipv6} with net suffix (CIDR)
sapc_sig_data_1_vip	/128	Public	VIP LDAP address	N/A	sig_data_1_sp	%{sapc_sig_data_1_vip_ipv6} with net suffix (CIDR)
sapc_sig_data_2_vip	/128	Public	VIP replication address	N/A	sig_data_2_sp	%{sapc_sig_data_2_vip_ipv6} with net suffix (CIDR)
sig_cn_1_pr_net	N/A	ULA	Uplink VLAN connected to external network for signaling traffic	sig_cn_1_pr_id	sig_cn_1_sp	%{sig_cn_1_pr_id}
	N/A		Uplink OSPF area for signaling traffic ⁽³⁾			%{sig_cn_1_pr_ospf}
	/64		Uplink CMX26 IP for signaling traffic			%{sig_cn_1_pr_addr1_ipv6} with net suffix (CIDR)
			Uplink CMX28 IP for signaling traffic			%{sig_cn_1_pr_addr2_ipv6} with net suffix (CIDR)
			Uplink gateway 1 for signaling traffic ⁽⁴⁾			%{sig_cn_1_pr_gw1_ipv6}
			Uplink gateway 2 for signaling traffic ⁽⁴⁾			%{sig_cn_1_pr_gw2_ipv6}
sig_cn_2_pr_net	N/A	ULA	Uplink VLAN connected to external network for signaling 2 traffic	sig_cn_2_pr_id	sig_cn_2_sp	%{sig_cn_2_pr_id}
	N/A		Uplink OSPF area for signaling 2 traffic ⁽³⁾			%{sig_cn_2_pr_ospf}
	/64		Uplink CMX26 IP for signaling 2 traffic			%{sig_cn_2_pr_addr1_ipv6} with net suffix (CIDR)
			Uplink CMX28 IP for signaling 2 traffic			%{sig_cn_2_pr_addr2_ipv6} with net suffix (CIDR)
			Uplink gateway 1 for signaling 2 traffic ⁽⁴⁾			%{sig_cn_2_pr_gw1_ipv6}
			Uplink gateway 2 for signaling 2 traffic ⁽⁴⁾			%{sig_cn_2_pr_gw2_ipv6}
om_cn_pr_net	N/A	ULA	Uplink VLAN connected to external network for OAM traffic	om_cn_pr_id	om_cn_sp	%{om_cn_pr_id}
	N/A		Uplink OSPF area for OAM traffic ⁽³⁾			%{om_cn_pr_ospf}
	/64		Uplink CMX26 IP for OAM traffic			%{om_cn_pr_addr1_ipv6} with net suffix (CIDR)
			Uplink CMX28 IP for OAM traffic			%{om_cn_pr_addr2_ipv6} with net suffix (CIDR)
			Uplink gateway 1 for OAM traffic ⁽⁴⁾			%{om_cn_pr_gw1_ipv6}
			Uplink gateway 2 for OAM traffic ⁽⁴⁾			%{om_cn_pr_gw2_ipv6}
om_cn_2_pr_net	N/A	ULA	Uplink VLAN connected to external network for provisioning traffic	om_cn_2_pr_id	om_cn_2_sp	%{om_cn_2_pr_id}
	N/A		Uplink OSPF area for provisioning traffic ⁽³⁾			%{om_cn_2_pr_ospf}
	/64		Uplink CMX26 IP for provisioning traffic			%{om_cn_2_pr_addr1_ipv6} with net suffix (CIDR)
			Uplink CMX28 IP for provisioning traffic			%{om_cn_2_pr_addr2_ipv6} with net suffix (CIDR)
			Uplink gateway 1 for provisioning traffic ⁽⁴⁾			%{om_cn_2_pr_gw1_ipv6}
			Uplink gateway 2 for provisioning traffic ⁽⁴⁾			%{om_cn_2_pr_gw2_ipv6}
sig_data_1_pr_net	N/A	ULA	Uplink VLAN connected to external network for LDAP traffic	sig_data_1_pr_id	sig_data_1_sp	%{sig_data_1_pr_id}
	N/A		Uplink OSPF area for LDAP traffic ⁽³⁾			%{sig_data_1_pr_ospf}
	/64		Uplink CMX26 IP for LDAP traffic			%{sig_data_1_pr_addr1_ipv6} with net suffix (CIDR)
			Uplink CMX28 IP for LDAP traffic			%{sig_data_1_pr_addr2_ipv6} with net suffix (CIDR)
			Uplink gateway 1 for LDAP traffic ⁽⁴⁾			%{sig_data_1_pr_gw1_ipv6}
			Uplink gateway 2 for LDAP traffic ⁽⁴⁾			%{sig_data_1_pr_gw2_ipv6}
sig_data_2_pr_net	N/A	ULA	Uplink VLAN connected to external network for replication traffic	sig_data_2_pr_id	sig_data_2_sp	%{sig_data_2_pr_id}
	/64		Uplink CMX26 IP for replication traffic			%{sig_data_2_pr_addr1_ipv6} with net suffix (CIDR)
			Uplink CMX28 IP for replication traffic			%{sig_data_2_pr_addr2_ipv6} with net suffix (CIDR)
			Uplink gateway 1 for replication traffic			%{sig_data_2_pr_gw1_ipv6}
			Uplink gateway 2 for replication traffic			%{sig_data_2_pr_gw2_ipv6}

(3) This parameter is specific and mandatory only for a GeoRed deployment.

(4) This parameter is specific and mandatory only for a Standalone deployment. BFD enabled is also mandatory on the SRs side to ensure a fast failover recovery.

Table 6 IP Allocation of Internal Networks for SAPC
IP Address	Node	Interface	Comment
169.254.69.0/24	Network	N/A	VLAN sapc_boot_sp Booting & Scaling network
.1	SC-1	eth2
.2	SC-2	eth2
.n	PL-n	bond1
.242	SC-1 SC-2	eth2:2	Boot MIP address
.200 - .232			Temporary IP address pool for scaled blades
.253	CMX 0-26	vlan1.4001	ARP target on CMX 0-26
.254	CMX 0-28	vlan1.4001	ARP target on CMX 0-28
172.16.100.0/24	Network		VLAN sapc_int_sp Cluster Internal network
.1	SC-1	bond0
.2	SC-2	bond0
.n	PL-n	bond0
.105	SC-1 SC-2	bond0:2	la-ldap MIP address
.241	SC-1 SC-2	bond0:3	uetrace MIP address
.243	SC-1 SC-2	bond0:1	NFS MIP address
.244	One of the PL nodes	bond0:1	SS7 CPM MIP address
.253	CMX 0-26	vlan1.4003	ARP target on CMX 0-26
.254	CMX 0-28	vlan1.4003	ARP target on CMX 0-28

Table 7 IPv4 OSPF Stub Areas
Network	Gateways	VLAN	OSPF Area	Comments
192.168.218.0/29	CMX 0-26: 192.168.218.1	130	0.1.1.1	O&M Traffic
192.168.218.0/29	CMX 0-28: 192.168.218.2	130	0.1.1.1	O&M Traffic
192.168.218.8/29	CMX 0-26: 192.168.218.9	131	0.1.1.1	O&M Traffic
192.168.218.8/29	CMX 0-28: 192.168.218.10	131	0.1.1.1	O&M Traffic
192.168.218.0/29	CMX 0-26: 192.168.221.1	132	0.1.1.2	Provisioning Traffic
192.168.218.0/29	CMX 0-28: 192.168.221.2	132	0.1.1.2	Provisioning Traffic
192.168.218.8/29	CMX 0-26: 192.168.221.9	133	0.1.1.2	Provisioning Traffic
192.168.218.8/29	CMX 0-26: 192.168.221.10	133	0.1.1.2	Provisioning Traffic
192.168.216.0/27	CMX 0-26: 192.168.216.1	120	0.0.1.1	Signaling Traffic
192.168.216.0/27	CMX 0-28: 192.168.216.2	120	0.0.1.1	Signaling Traffic
192.168.216.32/27	CMX 0-26: 192.168.216.33	121	0.0.1.1	Signaling Traffic
192.168.216.32/27	CMX 0-28: 192.168.216.34	121	0.0.1.1	Signaling Traffic
192.168.217.0/27	CMX 0-26: 192.168.217.1	140	0.0.1.2	LDAP Traffic
192.168.217.0/27	CMX 0-28: 192.168.217.2	140	0.0.1.2	LDAP Traffic
192.168.217.32/27	CMX 0-26: 192.168.217.33	141	0.0.1.2	LDAP Traffic
192.168.217.32/27	CMX 0-28: 192.168.217.34	141	0.0.1.2	LDAP Traffic
192.168.219.0/27	CMX 0-26: 192.168.219.1	150	0.0.1.3	Replication Traffic
192.168.219.0/27	CMX 0-28: 192.168.219.2	150	0.0.1.3	Replication Traffic
192.168.219.32/27	CMX 0-26: 192.168.219.33	151	0.0.1.3	Replication Traffic
192.168.219.32/27	CMX 0-28: 192.168.219.34	151	0.0.1.3	Replication Traffic
192.168.220.0/27	CMX 0-26: 192.168.220.1	122	0.0.1.4	Signaling Rx Traffic
192.168.220.0/27	CMX 0-28: 192.168.220.2	122	0.0.1.4	Signaling Rx Traffic
192.168.220.32/27	CMX 0-26: 192.168.220.33	123	0.0.1.4	Signaling Rx Traffic
192.168.220.32/27	CMX 0-28: 192.168.220.34	123	0.0.1.4	Signaling Rx Traffic

Table 8 IPv6 OSPF Stub Areas
Network	Gateways	VLAN	OSPF Area	Comments
fd00:0:0:31::/64	CMX 0-26: fd00:0:0:31::1	130	0.1.1.1	O&M Traffic
fd00:0:0:31::/64	CMX 0-28: fd00:0:0:31::2	130	0.1.1.1	O&M Traffic
fd00:0:0:32::/64	CMX 0-26: fd00:0:0:32::1	131	0.1.1.1	O&M Traffic
fd00:0:0:32::/64	CMX 0-28: fd00:0:0:32::2	131	0.1.1.1	O&M Traffic
fd00:0:0:33::/64	CMX 0-26: fd00:0:0:33::1	132	0.1.1.2	Provisioning Traffic
fd00:0:0:33::/64	CMX 0-28: fd00:0:0:33::2	132	0.1.1.2	Provisioning Traffic
fd00:0:0:34::/64	CMX 0-26: fd00:0:0:34::1	133	0.1.1.2	Provisioning Traffic
fd00:0:0:34::/64	CMX 0-26: fd00:0:0:34::2	133	0.1.1.2	Provisioning Traffic
fd00:0:0:11::/64	CMX 0-26: fd00:0:0:11::1	120	0.0.1.1	Signaling Traffic
fd00:0:0:11::/64	CMX 0-28: fd00:0:0:11::2	120	0.0.1.1	Signaling Traffic
fd00:0:0:12::/64	CMX 0-26: fd00:0:0:12::1	121	0.0.1.1	Signaling Traffic
fd00:0:0:12::/64	CMX 0-28: fd00:0:0:12::2	121	0.0.1.1	Signaling Traffic
fd00:0:0:15::/64	CMX 0-26: fd00:0:0:15::1	140	0.0.1.2	LDAP Traffic
fd00:0:0:15::/64	CMX 0-28: fd00:0:0:15::2	140	0.0.1.2	LDAP Traffic
fd00:0:0:16::/64	CMX 0-26: fd00:0:0:16::1	141	0.0.1.2	LDAP Traffic
fd00:0:0:16::/64	CMX 0-28: fd00:0:0:16::2	141	0.0.1.2	LDAP Traffic
fd00:0:0:17::/64	CMX 0-26: fd00:0:0:17::1	150	0.0.1.3	Replication Traffic
fd00:0:0:17::/64	CMX 0-28: fd00:0:0:17::2	150	0.0.1.3	Replication Traffic
fd00:0:0:18::/64	CMX 0-26: fd00:0:0:18::1	151	0.0.1.3	Replication Traffic
fd00:0:0:18::/64	CMX 0-28: fd00:0:0:18::2	151	0.0.1.3	Replication Traffic
fd00:0:0:13::/64	CMX 0-26: fd00:0:0:13::1	122	0.0.1.4	Signaling Rx Traffic
fd00:0:0:13::/64	CMX 0-28: fd00:0:0:13::2	122	0.0.1.4	Signaling Rx Traffic
fd00:0:0:14::/64	CMX 0-26: fd00:0:0:14::1	123	0.0.1.4	Signaling Rx Traffic
fd00:0:0:14::/64	CMX 0-28: fd00:0:0:14::2	123	0.0.1.4	Signaling Rx Traffic

3.2.1 BSP 8100 IP Addresses of External Elements

This section covers all the IP addresses in the customer network that do not belong to the SAPC but needed when configuring it.

Table 9 IP Addresses of External Elements
IP Address	Network	Use
`<NTP1-SERVER>`	`<NTP1-NETWORK>/<NTP-NETMASK>`	NTP Server
`<SNMP1-SERVER>`	`<SNMP1-NETWORK>/<SNMP-NETMASK>`	SNMP Server
`<DNS1-SERVER>`	`<DNS1-NETWORK>/<DNS-NETMASK>`	DNS Server

There can be several NTP servers.

Copyright	© Ericsson AB 2018. 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.