Contents
| 1 | Introduction |
| 1.1 | Prerequisites |
2 | Overview |
| 2.1 | Traffic Impact |
3 | IPv6 Configuration |
| 3.1 | Adding VIP IPv6 Addresses to the System |
| 3.2 | Deactivate MTAS |
| 3.3 | Add Diameter IPv6 Addresses |
| 3.4 | MTAS Configuration |
1 Introduction
This document describes how to enable and configure IPv6 for the MTAS towards its peer nodes.
1.1 Prerequisites
It is assumed that the user of this document is familiar with the O&M area, in general.
1.1.1 Licenses
No licenses are needed.
1.1.2 Documents
Before starting any procedure in this document, ensure that the following documents are available:
1.1.3 Conditions
The following conditions must apply:
An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
The Signaling Manager is connected.
2 Overview
The MTAS can be configured to use either IPv4 or IPv6 for the interfaces supporting IPv6. The external Media Resource Function Controller (MRFC) must use the same IP version as supported by the interfaces to the Serving CSCF (S-CSCF) and Interrogating CSCF (I-CSCF) (IPv6). External MRFC uses SIP and therefore supports IPv6.
The MTAS can use either IPv4 or IPv6 for the H.248 messages on the Mp interface, depending on the capabilities of the MRFC. This also applies towards the Media Resource Function Processor (MRFP), depending on its capabilities.
More interfaces supporting the IPv6 are shown in Figure 1.
IPv4 and IPv6 cannot be used in parallel on the same "logical" interface by the MTAS. It is possible to configure both IPv6 and IPv4 on the same physical interfaces as shown in MTAS SW Installation.
It is recommended to configure the MTAS with IPv6 after the CSCF and HSS have been configured with IPv6. It is also recommended to remove the A Resource Record in Domain Name System (DNS) server for the MTAS that is connected to the DNS SRV Resource Record used for the MTAS on the ISC interface.
The external interfaces used by the MTAS and weather they support either IPv4 or IPv6, or both, are shown in Figure 1.
2.1 Traffic Impact
Implementing IPv6 on the MTAS has some impact on the traffic, since the MTAS must be deactivated before it can be configured. Therefore, the traffic must be moved to the secondary MTAS before starting to implement IPv6 on the primary MTAS.
When the implementation is finished, the primary MTAS must be activated before moving back the traffic from the secondary MTAS. After that the user can implement IPv6 on the secondary MTAS.
3 IPv6 Configuration
IPv6 configuration includes the following main activities:
- Adding Diameter IPv6 addresses
- Configuring MTAS
The IP configuration attributes are shown in Table 1.
|
Name |
Value |
Description |
|---|---|---|
|
platform-vip (IPv4) |
|
The external VIP address of the O&M network using transport protocol IPv4.
Observe that a node can use either IPv4, IPv6, or both, as follows: For an explanation of the VIP address concept, refer to Virtual IP Address Management. |
|
platform-vip (IPv6) |
|
The external VIP address of the O&M network using transport protocol IPv6.
Observe that a node can use either IPv4, IPv6, or both, as follows: For an explanation of the VIP address concept, refer to Virtual IP Address Management. |
|
traffic-vip (IPv4) |
|
The VIP address of the traffic network using transport protocol IPv4.
Observe that a node can use either IPv4, IPv6, or both, as follows: For an explanation of the VIP address concept, refer to Virtual IP Address Management. |
|
traffic-vip6 (IPv6) |
|
The VIP address of the traffic network using transport protocol IPv6.
Observe that a node can use either IPv4, IPv6, or both, as follows: For an explanation of the VIP address concept, refer to Virtual IP Address Management. |
|
external_IO1_IP_address |
|
The IP address of IO Processor 1. This processor is normally the secondary IO. |
|
external_IO2_IP_address |
|
The IP address of IO Processor 2. This processor is normally the primary IO. |
|
Node Id |
The identity of the node. | |
|
Domain name |
The domain name for the node. |
3.1 Adding VIP IPv6 Addresses to the System
This section describes how to configure VIP IPv6 addresses in the system.
3.1.1 Add VIP IPv6 Address to the System
To add a VIP IPv6 address to the system, refer to Virtual IP Address Management.
3.1.2 Backup after Adding VIP Address
Create a backup according to Create Backup and System Backup and Restore.
3.1.3 Health Check
After adding VIP address, make sure that the MTAS is operational by performing a health check according to MTAS Health Check.
3.2 Deactivate MTAS
Before IPv6 configuration is performed, the MTAS must be deactivated.
To deactivate MTAS before IPv6 implementation:
- Move the traffic to the secondary MTAS.
- Deactivate the MTAS according to the instructions in Section 3.2 Deactivating MTAS in MTAS Node Management Guide.
- Note:
- It is recommended to deactivate the MTAS gracefully.
3.3 Add Diameter IPv6 Addresses
This section describes how to add and connect Diameter IPv6 addresses.
3.3.1 Disable Own Node
Disable the own node according to the instructions in Configure Own Node.
3.3.2 Add IPv6 to Own Node
Add IPv6 to the own node for Diameter according to the instructions in Configure Own Node.
An example of the input when adding IPv6 to the own node for Diameter is shown in Example 1.
Example 1 IPv6 to Own Node Added for TCP
objectClass: DIA-CFG-NeighbourNode ipAddressesList: 0:2001:1B70:4292:0251::71
3.3.3 Add IPv6 to Peer Node
Add IPv6 to the peer node for Diameter according to the instructions in Configure Peer Node and Connections.
An example of how to add IPv6 to the peer node is shown in Example 2.
Example 2 IPv6 to Peer Node Adding for TCP
objectClass: DIA-CFG-NeighbourNode ipAddressesList: 0:2001:1B70:4292:0251::73
3.3.4 Enable Own Node
Enable the own node according to the instructions in Configure Own Node.
3.3.5 Create New Peer Node Connection with IPv6
Create a peer node connection with IPv6 according to the instructions in Configure Peer Node and Connections.
An example on how to create a peer node connection with IPv6 is shown in Example 3.
Example 3 Create New Peer Node Connection with IPv6
objectClass: DIA-CFG-Conn ipAddressesList: 0:2001:1B70:4292:0251::73
When the IPv6 connections are made, the existing IPv4 connections can be deleted if necessary.
3.3.6 Create Backup after MTAS Configuration
Create a backup according to Create Backupand System Backup and Restore.
3.4 MTAS Configuration
This section describes the configuration of the MTAS interfaces towards peer nodes and how to change these nodes to IPv6.
- Note:
- To be able to configure the peer nodes, the MTAS must be deactivated. Before the MTAS is activated, the peer nodes must be configured with IPv6 on the affected interfaces.
For more information about the MTAS IP-specific attributes, refer to Managed Object Model (MOM).
3.4.1 SIP Configuration
The mtasSipIpVersion configures the MTAS to use IPv6 for SIP for the interfaces ISC, Ma, Mr, and Pw. This attribute must be set to 1 since only one IP version (IPv6 only) can be used.
Check that the mtasSipIcscfName attribute is an FGDN.
Change to IPv6 for SIP according to the instructions in Section 3, Changing IP-version in MTAS SIP Management Guide.
3.4.2 H.248 Configuration
The mtasMpControllerIpVersion attribute defines what type of IP protocol the MTAS uses for H.248 messages on the Mp interface towards the MRFP. Whether MTAS supports IPv6 or IPv4 towards the MRFP, depend on the capabilities of the MRFC.
The External MRFC uses SIP and can therefore handle IPv6.
To change the IP protocol version for the MRFC, refer to MTAS Media Control Management Guide.
3.4.3 Parlay X Configuration
The mtasParlayXIpVersion attribute defines what type of IP protocol the MTAS uses on both the Parlay X interface and the Cr interface. If peers of these interfaces use IPv6, this attribute must be changed for IPv6. The Cr interface is used together with Mr interface in case of External MRFC deployment.
To change the value of the attribute, refer to MTAS Parlay X Management Guide.
3.4.4 NameDB Configuration
The MtasIdPres.mtasIdPresDbIpVersion attribute defines the type of IP protocol the MTAS uses for sending and receiving SOAP messages on the NameDb interface to a Calling Name Server. If the Calling Name Server uses IPv6, this attribute must be changed for IPv6.
To change the IP protocol version of the Calling Name Server, refer to MTAS Calling Name Identity Presentation Management Guide.
3.4.5 DNS Configuration
The MTAS can use either IPv4 or IPv6 to communicate with the DNS. The IPv6 addresses for the DNS servers must be added if IPv6 is the preferred network protocol.
For more information about the DNS attributes for common components, refer to Managed Object Model (MOM).
To identify the Diameter object for the DNS LDAP object:
- Supply the distinguished LDAP name for the DNS object.
Enter the MTAS address as local address and one or several (one primary
and one or several secondary) DNS servers:
dn: applicationName=DNS, nodeName=<applNodeName>
An example of how to configure DNS for IPv6 is shown in Example 4.
Example 4 Configure DNS
dn: applicationName=DNS, nodeName=jambala DnsLocalAddress: [2001:1B70:4292:0251::76] objectClass: DNS-Application DnsServerEntry: 0:[2001:1B70:4292:0250::4]:53 DnsServerEntry: 1:[2001:1B70:4292:0251::6]:53
3.4.6 Perform Health Check
Before activating the MTAS, make sure that the MTAS is operational by performing a health check according to MTAS Health Check.
3.4.7 Activate MTAS
After IPv6 configuration for the MTAS is performed, the MTAS must be activated.
To activate the MTAS, do the following:
- Activate the MTAS according to the instructions in Section 3.1 Activating MTAS in MTAS Node Management Guide.
- Move the traffic from the secondary MTAS to this MTAS.
3.4.8 Perform a Backup of MTAS
Perform a backup according to Create Backupand System Backup and Restore.