Sie sind auf Seite 1von 23
DX MSS 15, Feature Documentation, version 7 Feature 1840: High Capacity Virtual MGW Support in

DX MSS 15, Feature Documentation, version 7

Feature 1840: High Capacity Virtual MGW Support in MSS

DN0954599

Issue 5-0-0

Feature 1840: High Capacity Virtual MGW Support in MSS

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners.

Copyright © 2017 Nokia. All rights reserved.

f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.

Feature 1840: High Capacity Virtual MGW Support in MSS

Table of Contents

This document has 23 pages

Summary of changes 5 1 Installation and testing 6 1.1 Configuration requirements 6 1.1.1 Network
Summary of changes
5
1
Installation and testing
6
1.1
Configuration requirements
6
1.1.1
Network elements involved
6
1.1.2
Hardware effects
6
1.1.3
Firmware effects
6
1.2
Remarks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
1.3
Installation and activation
7
1.3.1
Feature activation
7
1.3.2
IP routing configuration
7
1.3.3
IPDU and load balancer configuration
8
1.3.4
Unit pool configuration
10
1.3.5
Interrogating detailed unit status information
11
1.3.6
Creating new Multimedia Gateway entries in the MGW database
12
1.3.7
Additional PRFILE-based H.248 Load Balancer configuration
possibilities
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14
1.4
Testing
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
15
1.4.1
Test environment
15
1.4.2
Prerequisites for testing
15
1.4.3
Test execution and expected results
15
1.5
Troubleshooting
16
1.5.1
No response is received when sending H.248 messages to the
IPDU
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
16
1.5.2
No answer received after switchover
16
1.5.3
Unsuccessful MGW registration to an IPDU
17
1.5.4
Excessive IPDU load
17
1.5.5
Internal connection to IPDU failed
18
1.5.6
Controlling unit not available
19
1.6
Collecting logs from IPDUs and signaling units
20
1.7
Deactivating the feature
21
1.8
Deactivation
testing
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
22
1.8.1
Test environment
22
1.8.2
Prerequisites for testing
22
1.8.3
Test execution and expected results
23

Feature 1840: High Capacity Virtual MGW Support in MSS

List of Figures

Figure 1

Example configuration for MSC Server (MSS)

8

Feature 1840: High Capacity Virtual MGW Support in MSS

Summary of changes

Summary of changes

Changes made between issues 5-0-0 and 4-0-1

The document has been updated to include information on the Single pool H.248 Load Balancer functionality.

Changes made between issues 4-0-1 and 4-0-0

Steps Pinging between the IP addresses of the IPDU and signaling units and Configuring ann internal logical IP address for the IPDUs have been modified in section IP Routing Configuration .

Changes made between issues 4-0-0 and 3-1-0

Section Configuring Unit Pool and MGW parameters has been modified to include changes brought by the WGMHAN and UPOHAN improvement for SU IP address configuration functionality.

Steps for creating EL0 and EL1 interfaces and their bonding have been changed in section IP Routing Configuration .

Section IPDU and IP LB configuration has been modified to include the Load balancer handling MML (JJ) INT / EXT parameter improvement functionality.

The recommended minimum configuration for IPDUs has been modified in section Hardware effects .

A note with a warning not to disable the EL4 or EL5 physical interfaces on IPDUs or any logical VLAN interfaces has been added to section IP Routing Configuration .

Changes made between issues 3-1-0 and 3-0-1

Steps Configuring internal logical virtual IP addresses for SIGUs/CCSUs and Creating node-specific logical IP addresses for SIGUs/CCSUs have been modified in section IP Routing Configuration .

Editorial updates have been made throughout the document.

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

1 Installation and testing

1.1 Configuration requirements

1.1.1 Network elements involved

The following network elements are needed:

MSC Server (MSS)

Multimedia Gateway (MGW)

This feature functions on the SIGTRAN Signaling Units (SIGUs)/Common Channel Signaling Units (CCSUs) and IP Director Units (IPDUs) of the MSS.

1.1.2 Hardware effects

This feature has no effects on hardware.

1.1.3 Firmware effects

This feature has no effects on firmware.

1.2 Remarks

The feature can be used only with SCTP transport between the MSS and MGW.

Linux IPDUs are needed in the MSS. The Load Balancer application (LB) runs in the IPDU.

The maximum configuration is 5+1 IPDUs.

By utilizing H.248 load balancing, the number of used IP addresses on the H.248 interface is reduced. Instead of having a direct H.248 connection from every SIGU/CCSU toward virtual Multimedia Gateways (vMGWs), the SIGUs/CCSUs are organized into a pool and the pool has a direct connection toward the vMGWs through the IPDU. Both SIGUs and CCSUs can belong to the same pool. Multiple computer units with several internal IP addresses can be hidden behind a single logical (external) IP address.

In some cases the signaling unit does not have to be organized into a pool. It can have a direct connection toward the vMGW without the IPDU.

A maximum of 127 signaling units can be configured in the unit pool of the MSC Server.

For information on the MSS LAN Topology, see the Site Connectivity Configuration for MSC Server document.

For information on MGW unit pool handling commands, refer to the Unit Pool Handling (JE), Command Reference Manual .

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

For information on MGW data handling commands, refer to the Media Gateway Data Handling (JG), Command Reference Manual .

For information on handling load balancer parameters, refer to the Load Balancer Configuration Handling (JJ), Command Reference Manual .

1.3 Installation and activation

The steps that need to be followed to install and activate this feature are illustrated by means of an example network configuration. By adapting the example commands given below to the architecture of your network, you can follow the same steps to install and activate this feature on your network.

1.3.1 Feature activation

Procedure

1 Activating the 'H248 Load Balancer in MSS' (FEA1473) license

Use the following command to activate the license:

ZW7M:FEA=1473:ON;

g Note: The H.248 load balancer can be configured either in ON or CONF state. In CONF state, the feature is only configured, the feature functionality is not in use. In ON state, the feature is configured and the feature functionality is in use for the already configured H.248 unit pool configurations.

2 H.248 Load Balancer overload control

H.248 load balancer overload control is a generic feature on top of the H.248 load balancer in MSS feature.

If FEA1473 license is activated (ON state), the H.248 overload control functionality

can be controlled with the H248LB_OLC_CONTROL (012:0125) PRFILE

parameter. The parameter controls whether the ticketing service is used to protect the IPDU or not.

The default value of this parameter is TRUE.

1.3.2 IP routing configuration

When adding a specific unit to the unit pool, the following IP addresses are displayed in the guidance text:

IPADDR : IP address(es) assigned to VLAN1591

IPADDRSEC : IP address(es) assigned to VLAN1592

IPADDRLOGINT : internal IP address(es) assigned to VLAN1000

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

g Note: This is an example guidance text based on the external VLAN configuration used in this document.

Figure 1

Example configuration for MSC Server (MSS)

Bond0

LogicalIP addresses EL0 configuredonVLAN1591: SIGU EL1 IPDU-3:10.80.62.154 IPDU-4:10.80.62.155 VLAN1591 (SCTP
LogicalIP addresses
EL0
configuredonVLAN1591:
SIGU
EL1
IPDU-3:10.80.62.154
IPDU-4:10.80.62.155
VLAN1591
(SCTP MHpri)
EL0
SIGU
EL1
EL0
IPDU-3
Bond0
Bond0
(SCTP MHpri) EL0 SIGU EL1 EL0 IPDU-3 Bond0 Bond0 EL0 SIGU EL1 EL0 SWU41 IPDU-4 EL1
EL0 SIGU EL1 EL0 SWU41 IPDU-4 EL1 EL0 SIGU EL1 VLAN1592 (SCTP MHsec) VLAN1000 LogicalIP
EL0
SIGU
EL1
EL0
SWU41
IPDU-4
EL1
EL0
SIGU EL1
VLAN1592
(SCTP MHsec)
VLAN1000
LogicalIP addresses
EL0
SIGU
(Internal)
configuredonVLAN1592:
EL1
IPDU-3:10.80.62.162
IPDU-4:10.80.62.163
MSS
Bond0
Bond0
Bond0
Bond0
(Internal) configuredonVLAN1592: EL1 IPDU-3:10.80.62.162 IPDU-4:10.80.62.163 MSS Bond0 Bond0 Bond0 Bond0
(Internal) configuredonVLAN1592: EL1 IPDU-3:10.80.62.162 IPDU-4:10.80.62.163 MSS Bond0 Bond0 Bond0 Bond0
Siteswitch1 IP/MPLS backbone Siteswitch2
Siteswitch1
IP/MPLS
backbone
Siteswitch2

EL1

SWU40

To configure IP routing for H.248 load balancing, external logical IP addresses must be assigned to the IP Director Units (IPDUs) handling load balanced H.248 traffic over the SCTP multihoming primary and secondary paths. Default gateways must be assigned for these external logical IP addresses that point toward the L3 switching units (SWU-

40/41).

For instructions on configuring SWUs, creating VLAN, Bond0, EL interfaces and configuring IP routing for H.248 load balancing, see the Site Connectivity Configuration for MSC Server document.

1.3.3 IPDU and load balancer configuration

Purpose

In the following configuration example, IPDU-3 and IPDU-4 are the units in WO-EX state. IPDU-2 is the spare unit. H.248 interfaces are configured for the load balancer units H248LB0 and H248LB1.

For a detailed description of all possible parameters, see the Load Balancer Configuration Handling (JJ), Command Reference Manual .

Procedure

1 Use the JJE command to create, modify, and delete a load balancer (LBS) configuration.

Configure two LBSs, named H248LB0 and H248LB1 of the H248 type, using the “CREATE” operation:

Step example

ZJJE:CREATE:NAME=H248LB0,TYPE=H248;

ZJJE:CREATE:NAME=H248LB1,TYPE=H248;

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

2 Define the load balancer configuration.

Use the JJC command to create, modify, and delete which load balancer configuration is running in which load balancer unit.

g Note: Use the MODIFY operation instead of CREATE if the targeted IPDU is already functioning as a load balancer unit.

Step example

ZJJC:MODIFY:IPDU,3,NAME=H248LB0;

ZJJC:MODIFY:IPDU,4,NAME=H248LB1;

Example: Load balancer configuration interrogation

ZJJI:TYPE=LBS:LTYPE=H248;

INTERROGATING LBS CONFIGURATION LBS CONFIGURATION

LBS NAME

(NAME)

:H248LB0

LBS TYPE

(TYPE)

:H.248

LBS STATE

:ACTIVE

LBS CONFIGURATION

LBS NAME

(NAME)

:H248LB1

LBS TYPE

(TYPE)

:H.248

LBS STATE

:ACTIVE

COMMAND EXECUTED

Example: Load balancer unit configuration interrogation

ZJJI:TYPE=UNIT:UTYPE=IPDU;

INTERROGATING LBS UNIT CONFIGURATION IPD UNIT INFO

 

INT

UNIT INDEX

INTERFACE

LBS NAME

TYPE

---- ----- --------- --------- ------

IPDU

3

VLAN1000

H248LB0

H.248

 

SIPLB0

SIP

IPDU

4

VLAN1000

H248LB1

H.248

 

SIPLB1

SIP

COMMAND EXECUTED

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

1.3.4 Unit pool configuration

Example for H.248 load balancer unit pool configuration.

Procedure

1 Add IPDUs to the pool.

g

Note: There is no need to create the unit pool, because it is created by default.

Step example

ZJEA:UTYPE=IPDU,UIDX=3:IPADDR=10.80.62.154,IPADDRSEC=10.80.62.

162,IPADDRLOGINT=10.102.213.100:;

ZJEA:UTYPE=IPDU,UIDX=4:IPADDR=10.80.62.155,IPADDRSEC=10.80.62.

163,IPADDRLOGINT=10.102.213.101:;

g

Note: If IPDU is selected, the MML command presents the user with valid IP addresses for the IPADDR , IPADDRSEC , and IPADDRLOGINT parameters in the help text.

The IPADDR parameter is the SCTP primary source IP address of the IPDU. The IPADDRSEC parameter is the SCTP secondary source IP address of the IPDU. The IPADDRLOGINT parameter is the internal logical IP address of the IPDU. All three IP addresses need to be given when adding IPDUs to the pool.

2 Add signaling units to the pool.

Step example

ZJEA:UTYPE=SIGU,UIDX=0;

ZJEA:UTYPE=SIGU,UIDX=1;

ZJEA:UTYPE=SIGU,UIDX=2;

ZJEA:UTYPE=SIGU,UIDX=3;

If the command is executed with the UTYPE=ALL parameter, it adds all signaling units to the pool.

ZJEA:UTYPE=ALL;

3 Interrogate the unit pool.

Use the JEI command to interrogate the H.248 unit pool to see which units are in the pool and if the signaling units are working properly with the registered MGWs:

ZJEI:ALL;

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

-----------------------------------------------------------------

H.248 UNIT POOL DATA

-----------------------------------------------------------------

IPDU LIST:

IPD UNIT: IPDU-3 IPD PRIMARY IP ADDRESS: 10.80.62.154 IPD SECONDARY IP ADDRESS: 10.80.62.162 IPD INTERNAL LOGICAL IP ADDRESS: 10.102.213.100

IPD UNIT: IPDU-4 IPD PRIMARY IP ADDRESS: 10.80.62.155 IPD SECONDARY IP ADDRESS: 10.80.62.163 IPD INTERNAL LOGICAL IP ADDRESS: 10.102.213.101

(

)

SIGNALING UNIT LIST:

UNIT | ID | LB-ID |

-----------------------------------------------------------

UNIT-INFO

|

CTRL. MGWS

SIGU

0

1

UNDER REMOVAL

0

SIGU

1

2

ACTIVE

1

SIGU

2

3

ACTIVE

1

SIGU

3

4

NOT ACTIVE

0

COMMAND EXECUTED

If one of the available connections toward a signaling unit fails, the printout shows that the unit is in “NOT ACTIVE” state. For further information, see also the JEO command in the Unit Pool Handling in MSS, JE Command Group .

If you remove a unit from the unit pool with the JER command, the JEI printout shows that this unit is in “UNDER REMOVAL” state until it is successfully removed by the system.

1.3.5 Interrogating detailed unit status information

The Load BAlancer Single unit POol status (LBASPO) file contains detailed information about the internal SCTP connection states between IPDUs and signaling units.

The JEO command is used to interrogate the LBASPO file content:

g Note: In the example, only 4 signaling units are shown. However, the theoretical maximum number of signaling units in the unit pool is 255 (or 84+6 in a standard, two- shelf configuration).

ZJEO:UTYPE=IPDU,UIDX=3;

IPDU: IPDU-3

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

UNIT | ID |

UNIT-INFO

-----------------------------

SIGU

0

UNDER REMOVAL

SIGU

1

ACTIVE

SIGU

2

ACTIVE

SIGU

3

ACTIVE

MGW ID | SCTP STREAM STATE

--------------------------

0

NOT ACTIVE

1

NOT ACTIVE

4

ACTIVE

5

ACTIVE

8

NOT ACTIVE

9

NOT ACTIVE

COMMAND EXECUTED

ZJEO:UTYPE=ALL;

IPDU: IPDU-3

UNIT | ID | UNIT-INFO

-----------------------------

SIGU

0

UNDER REMOVAL

SIGU

1

ACTIVE

SIGU

2

ACTIVE

SIGU

3

ACTIVE

IPDU: IPDU-4

UNIT | ID | UNIT-INFO

-----------------------------

SIGU

0

ACTIVE

SIGU

1

ACTIVE

SIGU

2

ACTIVE

SIGU

3

ACTIVE

COMMAND EXECUTED

If a graceful unit removal is issued by the JER command, the JEO printout shows that this unit is in “UNDER REMOVAL” state until it is successfully removed.

1.3.6 Creating new Multimedia Gateway entries in the MGW database

To create an H.248 connection to a MGW from IPDU-3, follow the instructions.

Use the following command to create a MGW:

ZJGC:NAME=MGWGEN1,ADDR="10.85.20.245",PORT=0:IPDUIDX=3:AESA="E-

5",LBCU=5,:USEPARS=5,DEFPARS=0;

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

Execution printout

MGW DATA CREATED:

MGW ID 4

MGW NAME MGWGEN1

MGW ADDRESS

10.85.20.245

PORT NUMBER

0

DOMAIN NAME

ROUTE 410

IPDU INDEX 3 UNIT TYPE SIGU UNIT INDEX 2 PRIMARY CTRL ADDRESS 10.80.62.154 SECONDARY CTRL ADDRESS 10.80.62.162 E.164 AESA 5 LOCAL BCU-ID 5 DEFAULT PARAMETER SET 0

PARAMETER SET ATTACHMENT MGW PROFILE

REGISTRATION ALLOWANCE ALLOWED REGISTRATION STATUS REGISTERED

USE DEFAULT

NOKIA

MGW PROFILE VER 20

AUDIT STATUS

ALLOWED

LOCAL PORT

2945

TRANSPORT TYPE

SCTP

SCTP PARAMETER SET NUMBER

1

SCTP MODE

H248SCTP

LOAD REDUCTION PERCENTAGE

0%

NETWORK DELAY TIME

5*10

MSEC

COMMAND EXECUTED

g Note: The controlling unit is selected by the H.248 LB when the MGW connects to the MSS.

The IPDUIDX parameter is the unit index of the IPDU that controls the given MGW.

When the IPDUIDX parameter is given, a guidance text is displayed with the available IPDU indexes of the unit pool.

/* LIST OF SELECTABLE IPD UNITS:

UNIT | IDX

-----------

IPDU

IPDU

3

4

*/

For information on configuring vMGWs, see the Integrating MGW into the MSC Server System document in the Multimedia Gateway, Operating documentation.

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

1.3.7 Additional PRFILE-based H.248 Load Balancer configuration possibilities

H.248 Load Balancer internal heartbeat configuration

There are two levels of fault detection functionality within the H.248 Load Balancer (LB) to detect problems on the internal SCTP connection between the IPDU and signaling units:

On SCTP level: The SCTP heartbeat (HB) mechanism is used to detect if the SCTP connection is broken.

On H.248 level: The H248 LB internal heartbeat mechanism can be used to detect H.248-level problem in cases when the SCTP layer is working correctly, but there is a problem on H.248 level.

The frequency of the SCTP level heartbeat mechanism is defined by the SCTP parameter set attached to the H.248 unit pool.The frequency of the H248 LB internal heartbeat mechanism can be modified with the following PRFILE parameters:

H248_LB_INT_HB_RETRY (053:0068)

This parameter defines how frequently IPDUs check the signaling units in the signaling unit list of the pool.

H248_LB_INT_HB_ACK (053:0069)

It defines how long IPDUs should wait until a given signaling unit is evaulated as being faulty.

H248_LB_INT_HB_NEXT_HB (053:0067)

It defines how long the signaling unit waits for the next H248 LB internal HB message before it evaluates IPDU as being faulty.

As the SCTP level heartbeat mechanism can detect all of the internal connection problems and the chance of an H.248-level problem (while the SCTP layer is working properly) is very minor, the default values of the PRFILE parameters are defined in a way as not to cause any unnecessary load on the system, but still handle problems without losing the registration of a MGW (in the case of a problem with the controlling unit on H.248 level).

If needed, the PRFILE values can be set to lower values by taking into account the following important rule:

The value of the H248_LB_INT_HB_NEXT_HB (053:0067) PRFILE parameter must be bigger than the sum of the H248_LB_INT_HB_RETRY (053:0068) and the

H248_LB_INT_HB_ACK (053:0069) PRFILE parameter values. Setting much smaller values is not recommended, because it generates unnecessary extra load.

Setting delay before performing controlling unit reallocation

With the CTRL_UNIT_REALLOC_TIMER (053:0087) PRFILE parameter, a timer (in

seconds) can be set before controlling unit reallocation starts. This happens after specified events.

For example, the CTRL_UNIT_REALLOC_TIMER (053:0087) PRFILE parameter

has been set to five seconds. If two signaling units are added to the pool after each other within five seconds, a controlling role optimization takes place once, five seconds after the second unit is added to the pool. But if the second signaling unit is added to the pool more than five seconds later compared to the first one, then two controlling unit optimizations take place.

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

Setting the interval of performing SCTP association establishment

The MAX_SCTP_ESTABLISHMENT_TIMER (053:0088) PRFILE parameter defines

the maximum time interval before performing an SCTP association re-establishment after an SCTP association has already been established or an SCTP connection fails.

1.4

Testing

1.4.1 Test environment

The following network elements are needed for testing the activation of this feature:

one HLR

one MSS

one MGW

two RNCs

1.4.2 Prerequisites for testing

Procedure

1 Configure the single pool H.248 load balancer as described in section Installation and activation .

2 Activate the H.248 load balancing license in the MGW.

For activation instructions, see the Nokia MGW documentation.

1.4.3 Test execution and expected results

Procedure

1 Register the MGW.

2 Initiate a call.

3 Release the call.

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

Result

MGW registration is successful over IPDU-3 and IPDU-4.

The call is established with H.248 load balancer configuration.

1.5

Troubleshooting

1.5.1 No response is received when sending H.248 messages to the IPDU

Procedure

1 Check whether the H.248 load balancer license is switched on.

2 Check whether the configuration is correct, as described in section Installation and activation .

3 Check whether pinging works between the logical IP addresses of the IPDU and the signaling unit.

4 Check whether the listening ports are open in the IPDU and the signaling unit.

Step example

ZQRS:IPDU,3;

ZQRS:SIGU,0;

1.5.2 No answer received after switchover

Description

Everything works correctly until the first IPDU switchover happens. No answer is received after the switchover when the signaling unit sends an H.248 message to the IPDU.

Instructions

Remove the unit from the pool and add it again with its logical IP address.

Check the configuration on the MGW side to ensure the vMGW points to the right IPDU.

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

1.5.3 Unsuccessful MGW registration to an IPDU

Procedure

1 Check whether the configuration is as described in section Installation and testing .

2 Check whether there is an active signaling unit in the unit pool after the MGW registration is started with the JEI command.

3 Check the IPDU to which the MGW tries to register.

4 Check whether the IPDU is in the H.248 unit pool with the JEI command.

5 Check whether the IPDU has H.248 load balancer service with the JJI command.

6 Check whether the MGW tries to register to the correct IP address of the IPDU.

7 Check whether the MGW tries to register from the correct port (if it is not defined to 0 in the MGW database).

8 Check whether port 2945 for the L IP address is in 'LISTENING' state in the IPDUs, which means that every IP is configured correctly (with the QRS and the QRL commands).

1.5.4 Excessive IPDU load

Procedure

1 Check the configured SCTP parameter sets from the MGW database (with the JGI command) for all the MGWs in the pool.

2 Check the used SCTP parameter set (with the OYO command).

SCTP bundling must be 'YES'.

g Note: The deactivation of SCTP bundling has a negative effect on the IPDU load as more, but smaller, SCTP packets generate a much higher interrupt load.

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

1.5.5 Internal connection to IPDU failed

Description

The 0x3804 INTERNAL CONNECTION TO IPDU FAILED alarm is displayed.

Instructions

This alarm indicates that the internal single-homed SCTP association between the signaling unit and the IPDU is not available. Either a new internal connection could not be established or a working internal connection has failed. When this alarm is active, the services provided by the load balancer type indicated in the alarm fields may be severely disrupted.

g Note: The value of the first information field is always 1 in case of H248 LBS.

Different actions can be taken based on the value of the second (and third) information fields:

0x0000/0x0001

This failure situation indicates that the transport layer connection between the signaling unit where this alarm is set and the IPDU indicated in the third information field is severely disrupted. Check the configuration of the transport layer between the two affected units.

0x0002

This failure indicates that the internal single-homed SCTP listening point could not be opened at the IPDU. The IP address of the listening point may have failed. (Check the fifth information field.) The port of the listening point may have failed. (Check the fourth information field.) The possible actions depend on the value of the third information field:

0x0000

The listening point cannot be established, because there is an already existing listening point at the IP address and port indicated in the fourth and fifth information fields. Check your internal listening point configuration and look for non-unique IP address and port pairs. Eliminate duplications.

0x0001

The LBS process does not have permission to open the listening point at the IP address and port indicated in the fourth and fifth information fields. Contact customer support.

0x0002

An internal error occurred while opening the internal listening point. Check where the alarm is raised and save the computer logs of the referenced type of LBS. Send all the saved information to the Nokia support representatives.

0x0003

No internal listening IP address of the referenced type of LBS is found in the LBS configuration for the given IPDU.

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

Check whether any internal listening IP address is defined for the IPDU where the alarm is raised. If no IP address is defined for the IPDU, add one.

g Note: The used IP address must be internal logical and part of the local interface configuration of the given IPDU.

0x0004

The internal listening IP address of the referenced type of LBS is not part of the IPDU's local interface configuration. Check the missing IP address in the IP ADDRESS information field. Check whether the configured internal listening IP address (indicated in the fourth information field) is part of the IPDU where the alarm is raised.

g

Note: The IP address must be internal logical.

0x0005

No source IP address can be found in the local interface configuration of the unit from where the internal single- homed SCTP association can be established. Check the ADD INFO field for the index of the IPDU to where the source IP address cannot be found at the signaling unit. Check the IP ADDRESS field for the IP address of the listening point for which no source IP address can be found in the local interface configuration of the signaling unit. Check whether the signaling unit where the alarm is raised has an IP address in its local interface configuration, which IP address is from the same subnet and the same associated interface as the IP address indicated in the fourth information field at the IPDU whose index is included in the third information field.

0xFFFF

There is an unspecified failure situation with no meaningful information. For more information about the error, check the computer logs of the H248LBS. Save the computer logs of the unit where the alarm is raised and send them to the Nokia support representatives.

Canceling the alarm

Do not cancel the alarm. The system cancels the alarm automatically when the error is resolved.

1.5.6 Controlling unit not available

Description

The 0x3827 H.248 CONTROLLING UNIT NOT AVAILABLE alarm is displayed.

Instructions

This alarm is raised when the IPDU cannot select an H.248 controlling unit for a given MGW. Controlling unit selection or re-selection may be needed due to the following reasons:

MGW has established the SCTP association to the MSS.

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

The connection toward the current controlling unit is lost due to H.248 load balancer application heartbeat failure.

The SCTP connection toward the current controlling unit is lost.

The reason code of the lost SCTP connection can be:

1

The MGW established the SCTP association to MSS and initial selection is not possible.

2

GRSD flag was set for the original controlling unit.

3

The connection toward the original controlling unit is lost due to H.248 load balancer application heartbeat failure.

5

The SCTP connection is gracefully shut down by the original controlling unit.

6

The SCTP connection toward the original controlling unit is lost due to SCTP level issues, for example, SCTP heartbeat failure.

For detailed information about the controlling unit selection failure, check the logs in

IPDU ( lnx-log -t T -n lnx-h248-log ).

The most probable reasons for selection failure are the following:

There are no (more) units in the pool.

All the remaining units in the pool have their SCTP connections toward the IPDU temporarily or permanently down.

Check whether any of the listed conditions are relevant and take appropriate actions to eliminate them.

Canceling the alarm

The alarm is cancelled by the IPDU automatically when controlling unit selection succeeds for the same MGW.

1.6 Collecting logs from IPDUs and signaling units

With the help of the instructions below, logs can be collected from the IPDUs and signaling units.

Procedure

1 Create printouts with the following commands:

ZJEI:ALL;

ZJEO:UTYPE=ALL;

2 Collect wireshark logs about the internal/external connections.

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

3 Collect LNX logs (use these commands in the IPDU service terminal):

Sub-steps

a) Activate tracing with lnx-lbop -a <internal physical IP address> trace <LBSname> on.

b) Activate log collection:

lnx-log -n lnx-h248-man -t T lnx-log -n lnx-h248-log -t T lnx-log -t T

c) Collect lbop dump:

lnx-lbop -a <internal physical IP address> dump <LBSname>

4 Use these commands on the service terminal of IPDU, because these can show the problems also:

ZDDS:IPDU,<index>;

dmesg

netstat -nape

//kernel"s logs

//the sockets and their status

ps -fewH

//running processes

route

//routing table

ifconfig

//network interfaces and their IP address

lnx-swlist -l

//loaded dmx images and their versions

//system variables

lnx-launcher -L

//status of families

lnx-log -t T lnx-pubvar

//system logs

lnx-log -t T -n ipconf //logs of lnx-ipconf

5 Collect the <package_dir>/LFILES/LOBFILGX.XML file.

6 Collect HTA (5E4) logs from the signaling units attached to the pool.

If a generic MGW registration problem occurs, it is enough to collect the logs from the primary and secondary units.

You can interrogate MGW data with the JGI command and H.248 log entries with the JGO command.

1.7 Deactivating the feature

Installation and testing

Feature 1840: High Capacity Virtual MGW Support in MSS

Procedure

1 Turn off the license.

Configure the MSS and MGW back to the original configuration to be able to use the MSS without the IPDU.

Step example

ZW7M:FEA=1473:OFF;

Step result

Turning the license off:

disables all the connections

disconnects all ongoing calls (if forced mode is used)

disables the overload control function

Turning the license from ON to CONF state:

disables all signaling unit connections, except that of the controlling unit

gracefully disconnects all ongoing calls

keeps the connections to the MGWs, but forbids the registration of new MGWs

1.8 Deactivation testing

1.8.1 Test environment

The following network elements are needed for testing the activation of the feature:

one HLR

one MSS

one MGW

two RNCs

1.8.2 Prerequisites for testing

Procedure

1 Deactivate the H.248 Load Balancing license in the MSS.

Feature 1840: High Capacity Virtual MGW Support in MSS

Installation and testing

2 Deactivate the H.248 Load Balancing license in the MGW.

For deactivation instructions, see the MGW documentation.

1.8.3 Test execution and expected results

Test execution

Procedure

1 Register the MGW.

2 Initiate a call.

3 Release the call.

Expected results

The MGW registrations are successful without the IPDU.

The call is established without H.248 Load Balancer configuration.