[basic training]data configuration of mediax3600

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

Huawei Confidential

Confidentiality: INTERNAL23/4/8

英文标题 :40-47pt

副标题 :26-30pt

字体颜色 : 反白内部使用字体 :

FrutigerNext LT Medium

外部使用字体 : Arial

中文标题 :35-47pt

字体 : 黑体副标题 :24-28pt

字体颜色 : 反白字体 : 细黑体

Data Configuration of MediaX V300R005C03

ISSUE 2.0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

After learning this course, you will be able to:

Grasp the basic procedure for configuring the Mediax3600.

Grasp the relevant configuration commands of the Mediax3600.


Chapter 1 How to Configure the MediaX3600Chapter 1 How to Configure the MediaX3600

Chapter 2 Configuring the MediaX3600 Hardware Data Chapter 2 Configuring the MediaX3600 Hardware Data

Chapter 3 About the MediaX3600 NE and Module Data Chapter 3 About the MediaX3600 NE and Module Data

Chapter 4 Local Office Configuration of the MediaX3600Chapter 4 Local Office Configuration of the MediaX3600

Chapter 5 Feature data configuration of the MediaX3600 Chapter 5 Feature data configuration of the MediaX3600

Chapter 6 Interconnection Configuration of the MediaX3600 Chapter 6 Interconnection Configuration of the MediaX3600

Chapter 7 Maintaining the MediaX3600 Chapter 7 Maintaining the MediaX3600


How to Configure the MediaX3600

MediaX3600

MDXDB

OMS2600

E-Mail serverCCF

MRS

Web Portal

OSS

S-CSCF

SNMP

NFS

Web layerControl layerMedia layerBSS/OSS layer

In the IMS network, the billing and signaling functions are integrated in one network.

DPU

MDXSU

SIPSIP

SOAP

SMTP

Diameter

MDXDU

BSS

MDXBU

MDXRU

SPG2800

SOAP

VoicXML

Data conferencing server

HTTP

Assume that we have completed the networking and installation of the MediaX following the guide, of which the networking diagram is as follows:


How to Configure the MediaX3600

The IP addresses and configuration of the networking are as follows: The IP addresses of all the modules of the MediaX (including the User Portal)

are allocated as follows: External IP address of the web plane: 2.1.37.204 External IP address of the SIP plane: 2.1.37.204 IP address provided by the NFS server: 2.1.36.0/255.255.254.0

After all the modules of the MediaX are installed, the module IDs are as follows: 1: MDXSU; 2: MDXDU; 3: MDXHU; 4: MDXDB; 5: MDXRU; 6: MDXBU Configuration information of the peripheral NEs of the MediaX:

MRS: The type is MRS6200, the IP address is 2.1.37.97, the port of the SIP message is 5060, and the PSI is [email protected].

CSCF IP address: 2.1.37.43; domain name: ims5.mediax.com Configuration of the CCF: host domain name: ccf.huawei.com; domain: huawei.com; port:

1813; IP address: 2.1.37.210 IP address of the OMU server: 172.16.128.1; both the FTP username and the FTP

password are ims_omu. email server: smtp.hawei.com IP address of data conference server: 2.1.37.211

How would we configure the MediaX to make the system run normally? The following text describes how to configure the MediaX MML according to the preceding networking information.


Chapter 2 Configuring the MediaX3600 Chapter 2 Configuring the MediaX3600

Hardware Data Hardware Data

2.1 Numbering Devices

2.2 Configuring the Hardware Data

2.3 Configuring the MediaX3600 without the

disk array


Rules for Numbering Racks and Subracks

Rules for numbering racks: Only one integrated rack numbered 0 regularly is configured. The service processing racks are numbered sequentially from 1.

Rules for numbering subracks: The integrated rack holds up to two Huawei Open Standards Telecom Architecture

(OSTA) subracks. Each service processing rack holds up to three OSTA subracks, and

the numbering rules are as follows: Physically, the subracks in the rack are numbered from top downward according to the

installation location. If the serial number of the subracks in the integrated rack is 0 to 1,

the serial number in the service processing rack is 0 to 2. Logically, the subracks between the racks are numbered in an ascending order from

the smaller rack number to the greater one. If the serial number of the subracks in the

integrated rack is 0 to 1, the serial number of the subracks in the service processing

rack is 2 to 4. You must configure only one basic subrack, which is numbered 0 regularly. The serial

numbers of other subracks ascend according to the numbering rules.


Rules for Numbering Slots

Slot 0 in subrack 0 of the integrated rack is

always used to hold the OMU.

By default, slot 6 and slot 7 hold the

Switching Unit (SWU). The corresponding

Switching Interface Unit (SWI) is installed in

slot 6 and slot 7 at the rear of the subrack.

The software types for slot 1 and slot3

are MXMMU, which can provide the audio

conference and video conference. The

software type for slot 2 is MXDCU, which

can provide the data conference.

USI2

USI2

USI2

USI2

SWI

SWI

UPB0

UPB0

UPB0

SWU

SWU

00 01 02 03 04 05 06 07 08 09 10 11 12 13

BACK

FRONT

00 01 02 03 04 05 06 07 08 09 10 11 12 13

SMU SMU

SDM SDM

UPB0


Chapter 2 Configuring System Hardware Data Chapter 2 Configuring System Hardware Data



2.3 Configuring the MediaX3600 without the disk

array


Configuring Hardware - Rack

Configuring rack ADD RACK: It is used to add a rack.

ADD RACK: RN=0, LTITLE="home1", POSNUM=0, ROWNUM=0,

COLNUM=0;

MOD RACK: it is used to modify the relevant parameters of a rack, for

example, site number, row number, column number and site name.

RMV RACK: It is used to remove a rack.

You can add a rack according to the ascending order of number; you can

delete a rack according to the descending order of number. Before deleting a

rack, you must delete the configurations of relevant subracks on the rack.


Configuring Hardware - Subrack

Configuring subrack ADD SUBRACK: It is used to add a subrack.

ADD SUBRACK: RN=0, PN=0, SBRN=0, TYPE=ATCA, SBVER=R2, SRMUSN1=4,

SRMUSN2=5, SBRNNM="MEDIAX0";


Configuring Hardware - Board

ADD BRD: It is used to add a board. ADD BRD: RN=0, PN=0, SN=1, LN=FRONT, FBRDHTYP=DBU5; ADD BRD: RN=0, PN=0, SN=3, LN=FRONT, FBRDHTYP DBU5; ADD BRD: RN=0, PN=0, SN=1, LN=BACK, BBRDHTYP=USI2; ADD BRD: RN=0, PN=0, SN=3, LN=BACK, BBRDHTYP=USI2;

Configuration description Before configuring a board, add a subrack. Configuring boards refers to configuring information of various functional boards of

the MediaX, including board type, serial number, and location. After adding these two boards on OMU, run command STR INSTBRD to start the

software installation or use the OSTA remote GUI to reboot the board in slot1 and slot 3 and then press F12 to start the software installation.


Chapter 2 Configuring the MediaX3600 Chapter 2 Configuring the MediaX3600

Hardware Data Hardware Data



2.3 Configuring the MediaX3600 without the

disk array

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

Configuring the MediaX3600 without disk array----STEP 1

After the two boards are installed, use the remote control function provided by the OSTA to log in to the board in logical slot 1. Then, switch to the /opt/appsoft/MediaX3600/tool directory and run the SetupNonDiskHA.sh script to configure the HA environment without disk arrays for the two boards. In /SetupNonDiskHA.sh 1 3, the numbers indicate the logical slot numbers of the active board and the standby board, respectively.


Configuring the MediaX3600 without disk array----STEP 2

[SIP IP] 11 sip.networkcard.no=BACK7 12 sip_gateway=null 13 sip_gw_destination= 14 sip_gw_netmask= 15 sip.floatIP.address=160.10.210.27 16 sip.floatIP.netMask=255.255.0.0 17 media1.sip.ipaddr=160.10.210.26 18 media1.sip.netmask=255.255.0.0 19 media2.sip.ipaddr=160.10.210.74 20 media2.sip.netmask=255.255.0.0 [WEB IP] 21 web.networkcard.no=BACK5 22 web_gateway=null 23 web_gw_destination= 24 web_gw_netmask= 25 web.floatIP.address=70.10.210.27 26 web.floatIP.netMask=255.255.0.0 27 media1.web.ipaddr=70.10.21.26 28 media1.web.netmask=255.255.0.0 29 media2.web.ipaddr=70.10.210.74 30 media2.web.netmask=255.255.0.0

[NFS IP] 31 nfs.networkcard.no=BACK6 32 nfs_gateway=null 33 nfs_gw_destination= 34 nfs_gw_netmask= 35 nfs.floatIP.address=60.10.210.33 36 nfs.floatIP.netMask=255.255.0.0 37 media1.nfs.ipaddr=60.10.210.26 38 media1.nfs.netmask=255.255.0.0 39 media2.nfs.ipaddr=60.10.210.74 40 media2.nfs.netmask=255.255.0.0 [OSS/BSS IP] boss.networkcard.no=BACK8 41 boss_gateway=null 42 boss_gw_destination= 43 boss_gw_netmask= 44 boss.floatIP.address=45.4.4.4 45 boss.floatIP.netMask=255.255.0.0 46 media1.boss.ipaddr=45.4.4.7 47 media1.boss.netmask=255.255.0.0 48 media2.boss.ipaddr=45.4.4.13 49 media2.boss.netmask=255.255.0.0

When you run the script, the system prompts you to enter the following information ：


Configuring the MediaX3600 without disk array---- STEP 3

Example of IP address configuration on the SIP plane:

[SIP IP] 11 sip.networkcard.no=BACK7 12 sip_gateway=10.85.132.1 13 sip_gw_destination=10.85.0.0 14 sip_gw_netmask=255.255.0.0 15 sip.floatIP.address=160.10.210.27 16 sip.floatIP.netMask=255.255.0.0 17 media1.sip.ipaddr=160.10.210.26 18 media1.sip.netmask=255.255.0.0 19 media2.sip.ipaddr=160.10.210.74 20 media2.sip.netmask=255.255.0.0


Configuring the MediaX3600 without disk array----start the nodes

With the VCS client, all resources nodes form top to bottom should be started and run the online operation.Right click the resource nodes and choose online.The picture shows all resources nodes are started.


Question

What are the rules for numbering racks, subracks, and slots?

Which data needs to be added for adding hardware data?


Adding Module Data

Modules refer to internal processing units of a board. In adding a module, we need to add the proper processes on the board.

The modules of the MediaX3600 include the following: MediaX Business Unit (MDXBU) Service logic unit, which is a core logic unit of the MediaX3600, and is used to process the service

logics of the MediaX3600. MediaX DataBase Unit (MDXDB) Database logic unit, which uses the DB2 database, LDAP database and NFS services. SIP DPU Unit (MDXSU) SIP DPU logic unit, which is used for load balancing of SIP messages. Diameter DPU Unit (MDXDU) Diameter DPU logic unit, which is used for load balancing of Diameter messages. MediaX Resource Unit (MDXRU) License and resource service logic unit, which is used for license control and resource allocation.


Adding NE Data

/*---------- Run the command on the OMS client----------*/ ADD ME: MEID=111, METYPE=MEDIAX, MEVER="

V300R005C01B018", MEVD="HUAWEI";


Add the module data

/*---------- Run the command on the MediaX3600 client- ----------*/ /*add the modules*/ ADD MODULE: MID=1, MT=MDXDB, RN1=0, PN1=0, SN1=1, RN2=0,

PN2=0, SN2=3, MNAME="MDXDB0"; ADD MODULE: MID=2, MT=MDXSU, RN1=0, PN1=0, SN1=1, RN2=0,

PN2=0, SN2=3, MNAME="MDXSU0"; ADD MODULE: MID=3, MT=MDXDU, RN1=0, PN1=0, SN1=1, RN2=0,

PN2=0, SN2=3, MNAME="MDXDU0"; ADD MODULE: MID=4, MT=MDXRU, RN1=0, PN1=0, SN1=1, RN2=0,

PN2=0, SN2=3, MNAME="MDXRU0"; ADD MODULE: MID=5, MT=MDXBU, RN1=0, PN1=0, SN1=1, RN2=0,

PN2=0, SN2=3, MNAME="MDXBU0“

If MediaX3600 work in the single-system, the information for

standby is not necessary.




Chapter 3 About the MediaX3600 NE and Module DataChapter 3 About the MediaX3600 NE and Module Data






Configuring MDXSU /*---------- Run the command on the MediaX3600 client- ----------*/ /*Configuring SIP DPU*/

MOD SIPDPU: MID=2, SDID=1, EXIP=“2.1.37.204"; /* Configuring SIP switching border NE (SCSCF )*/

MOD OUT: MID=2, OID=1, TYPE=CSCF,

NETP=“2.1.37.43", NEPORT=5060;


Configuring MDXDB data

/*---------- Run the command on the MediaX3600 client- ----------*/ /*Configuring NFS server*/

ADD NFSSVR: MID=1, INDEX=2, DIR="/opt/record",

NETWORK=“2.1.36.0", MASK="255.255.254.0";


Configuring MDXRU data

/*---------- Run the command on the MediaX3600 client- ----------*/

/*Configuring MRS(MRFC) data*/ ADD MRS: MID=4, MRSID=1, TYPE=MRFC_MRFP, IP="160.10.201.110", PORT=5060,

PSI="sip:[email protected]", RGNID=1, VIDPOT=1000, VIDADPT=1000, MUTPIC=1000, AUDPOT=1000;

/*Configuring MRS(MCU) data*/ ADD MRS: MID=4, MRSID=2, TYPE=MCU, IP="164.199.33.39", PORT=5060,

PSI="sip:[email protected]", RGNID=1, VIDPOT=1000, BNDWTH=1000, VIDADPT=1000, MUTPIC=1000;

/* update license*/ UPDATE LICENSE: MID=4, LICID=1;

NOTE ：1 、 Before run the command UPDATE LICENSE, the new license file must be saved in the path

/opt/appsoft/MediaX3600/mdxru/conf/server/osgi/conf/com.huawei.mediax.resourceservice.server.2 、 After updating the license file, you can run command DSP LICENSE: MID=4; to check the license information.


Configuring MDXBU data

/*---------- Run the command on the MediaX3600 client- ----------*/ /* Configuring conference data*/

MOD CONF: MID=6, CONFID=1, HCFP="70",

HPIP=“huawei.com“; /* Configuring dialog service*/

MOD DIASVR: MID=6, DIAID=1, IP=“2.1.37.204",

PORT=5060; /* Configuring VoiceXML data*/

MOD BUVXS: MID=6, BUWID=1, IP=“2.1.37.204";


Configuring offline charging /*---------- Run the command on the MediaX3600 client- ----------*/

/* Configuring Diameter DPU*/ MOD DIAMDPU: MID=3, DDID=1, DOMAIN="relay.mediax.huawei.com",

REALM="mediax.huawei.com"; /* Configuring charging route*/ MOD ROUTE: MID=3, ROID=1, HOST="ccf.huawei.com", RELAY="huawei.com"; /* Configuring CCF*/ MOD DPUCHRG: MID=3, DCID=1, TYPE=CCF, HOST="ccf.huawei.com",

PORT=1813; /* Configuring MDXBU*/ MOD DPUCHRG: MID=3, DCID=2, TYPE=MEDIAX, HOST="client.mediax.com",

PORT=1810; /* Configuring offline charging*/ MOD CCFCHRG: MID=6, CCID=1, OH="client.mediax.com", OR="mediax.com",

OP=1810, DH="ccf2.huawei.com", DR="huawei.com", RH="relay.mediax.huawei.com", RP=1812;

/* Configuring the mapping between the host domain name and the host IP address of the CCF*/ ADD HOST: MID=3, HID=20, HOST="ccf.huawei.com", IP=“2.1.37.210"; /* Configuring the mapping between the host domain name and the host IP address of the Diameter DPU*/ ADD HOST: MID=3, HID=22, HOST="relay.mediax.huawei.com", IP=“2.1.37.204"; /* Configuring the mapping between the host domain name and the host IP address of the MDXBU*/ ADD HOST: MID=3, HID=21, HOST="client.mediax.com", IP=“2.1.37.204";


Configuring the data conference server connected

/*---------- Run the command on the MediaX3600 client- ----------*/ /* Configuring MediaX Data Resource*/ MOD DATARSC: MID=5, DRID=1, DOMAIN="2.1.37.211",

PORT=8080, DATAFLAG="/servlet/meeting",

LDAPHOST="2.1.37.211", LDAPPORT=389, LDAPADM="cn=root",

LDAPPWD=“huawei"; /* Configuring the mapping between the host domain name and the host IP

address of the data conference server */ ADD HOST: MID=3, HID=1, HOST="sametime.huawei.com",

IP=""2.1.37.211";


Configuring the mail server

/*---------- Run the command on the MediaX3600 client-----------*/

/* Configuring the mail server*/ MOD MAILSVR: MID=5, MSID=1,

SMTPSVR="smtp.huawei.com", SND="tester",

SNDEML="[email protected]", ACCT="admin",

PWD="******";

The user name and password can be got form the mail server.


Configuring FTP

/*---------- Run the command on the MediaX3600 client-----------*/

/* Configuring FTP data*/ MOD FTP: MID=5, FTPID=1, IP=“172.16.128.1",

FUSER=omu", PWD=“omu", REDIR="/Huawei/CGP";

This configuration is to send the PCDR to OMU, so OMU can

check the MediaX performance measure result.


Configuring User portal （ not MML ）

Configuration file path:

/opt/appsoft/MediaX3600/userportal/tomcat/webapps/portal/ROOT/WEB-INF/

classes/conf.xml

Configuring the Soap service:

soapUrl ： mediax web service IP:8666+"/axis/services/MediaXWebServicePort"

soapNBIUrl :mediax web service IP:8666+"/axis/services/MediaXProvisionPort "

notifyAddress :mediax web service

IP+"/axis/services/MediaX_WebServiceSkeleton "

Configuring sametime data conference server:

SameTimeUrl ： the domain name of the data conference server







Chapter 6 Interconnection Configuration of the MediaX3600Chapter 6 Interconnection Configuration of the MediaX3600



Configuring CSCF

/*---------- Run the command on the CSCF client-----------*/

Configuring the SPSI to add the IMPU(IP Multimedia Public

Identity), which is the identifier used to communicate with other

users.

ADD SPSI: SID=0, PSITYP=SIPWILDCARDEDPSI,

IMPU="sip:132!*[email protected]";


Configuring CSCF

/*---------- Run the command on the SPG-HSS client-----------*/

ADD PSI: PISI="[email protected]", PUSI="sip:132!*!

@huawei.com", PUSITYPE=WPUSI; /*---------- Run the command on the SPG-HSS client-----------*/

ADD IFC: PUSIS=SIPURI, PUSI="132!*[email protected]",

PRIORITY=0, SERVER="sip:2.1.37.204",

TRIGPT="<TriggerPoint><ConditionTypeCNF>0</Conditi

onTypeCNF><SPT><ConditionNegated>0</

ConditionNegated><Group>5</

Group><SessionCase>2</SessionCase></SPT></

TriggerPoint>";


Configuring CCF

/*---------- Run the command on the CCF client-----------*/

ADD AP: CCFID=1, APID=1, APNAME="MediaX", LWSIZE=1024, MPS=5000, PTTYPE=TCP, REALM="huawei.com", LOCIDT="ccf.huawei.com";

ADD PEER:CCFID=1,APID=1,PERIDT="relay.mediax.huawei.com",NDTYPE=MediaX,REALM="mediax.huawei.com",SERRACR=NO;

ADD PEERLINK:CCFID=1,APID=1,PERIDT="relay.mediax.huawei.com",LINKNAME="ccf-mediax",LPADDR=“2.1.37.210",LLISPOR=13868,PADDR=“2.1.37.204",PLISPOR=1812;


Configuring MRFC

/*---------- Run the command on the MRFC client-----------*/

Use the command following to configure the HTTP service ,

which is used to get the HTTP script

ADD MHTTPS: MRFCID=0, LNKID=0, ADDRID=0,

HTTPN="111.ims5.mediax.com", IP="2.1.37.204",

LPT=7989, PPT=8666, BSUMID=1; It’s suggested to add 5 to 10 HTTP links.


Configuring MRFP

/*---------- Run the command on the MRFP client-----------*/

ADD FS: FSID=1, TYPE=NFS,

MOUNTDIR="recording"; ADD FSLNK: LNKID=1, FSID=1,

FSADDR="2.1.37.204", FSDIR="/opt/record"; Reboot the MRP6600 。


Introduction to Maintenance Commands

Through the MML maintenance commands, you can perform the following operations: Restarting each module of the system: RESTART SYSTEM: MID=1, MBID=1, ADMST=RESTART; Manual backup operation : BAK SYSTEM: BKTYPE=FULL, FSTYPE=LOCAL; 或 BAK SYSTEM: BKTYPE=FULL, FSTYPE=NET,

BKSERVERIP=“160.10.201.100", SFTPUSER=“root", SFTPPSSWD ="******", BKPATH=“/opt/tmp"; Rollback operation : RESTORE SYSTEM: RETYPE=CONFIGURE, REFNAME=“MDX_CONF_BK_090910062448.tar.gz If the backup file is generated through the network backup mechanism, copy the backup file to the /opt/backup/restore

directory on the MediaX3600 board during the rollback operation. Then, run the /opt/appsoft/MediaX3600/tools/restore_network.sh + name of the backup file script, for example, /opt/appsoft/MediaX3600/tools/restore_network.sh MDX_FULL_V300R005C03SPC011_NETWORK_090915064235.tar.gz (There is a space between the script name and the file name) to roll back the system

Note: 1. The local directory for backing up files is /opt/backup/MediaX3600/directory of each backup type. The network

backup directory is specified by the user 2. The rule for naming a backup file is as follows: MDX_backup type_bk_backup time.tar.gz. For example, if a full backup operation is performed at 15:30:45 on Oct. 11, 2009, the backup file is named MDX_FULL_BK_091011153045.tar.gz. If the file is generated through network backup, a version name and a

network backup ID are added to the backup file name, for example, MDX_FULL_V300R005C03SPC011_NETWORK_090915064235.tar.gz

3. The directory for storing the backup rollback file is /var/mediax/directory of each module



Patch upgrade and removal of patch upgrade for each module:

PATCH SYSTEM: MID=1, MBID=1, VER="V300R005C03B013SPC001", OPR=UPDATE;

Automatic backup for each module:

MOD AUTOBK: MID=1, ABID=1, TYPE=FULL, PLCY=EVERYDAY, CMMT="test";

Configuring the database dump policy for the database module:

MOD DBDUMP: MID=4, DBDID=1, PATH="/opt/dump/data", BYDSCL=80, DMPSCL=20;

Configuring the record file dump policy for the database module:

MOD RCDDUMP: MID=4, RCDID=1, PATH="/opt/dump/record", SPC=70, KPTM=180;



Problems in the current maintenance commands:

Since the operation duration of the maintenance commands is relatively long, you have

to obtain the operation logs to know the operation results through MML commands.

1) View the logs: Under the /tmp/mediax －－－－ patch operation Under the /var/mediax －－－－ backup, recovery, restart, and dumping

2) View the backup and dumping results: /opt/backup －－－－ Backup /opt/dump －－－－ Dumping

3) View the automatic operation results crontab -l

Thank youwww.huawei.com

[basic training]data configuration of mediax3600

Documents

data add mrs

configuring

service processing

data conference

host ip address

configuring

hardware data

maintenance