DS-6211 MSO Software

Installation and Configuration Guide

Copyright Information
Hytera is the trademark or registered trademark of Hytera Communications Corporation Limited (the
Company) in PRC and/or other countries or areas. The Company retains the ownership of its trademarks
and product names. All other trademarks and/or product names that may be used in this manual are
properties of their respective owners.

The product described in this manual may include the Company’s computer programs stored in memory
or other media. Laws in PRC and/or other countries or areas protect the exclusive rights of the Company
with respect to its computer programs. The purchase of this product shall not be deemed to grant, either
directly or by implication, any rights to the purchaser regarding the Company’s computer programs. Any
of the Company’s computer programs may not be copied, modified, distributed, decompiled, or
reverse-engineered in any manner without the prior written consent of the Company.

Disclaimer
The Company endeavors to achieve the accuracy and completeness of this manual, but no warranty of
accuracy or reliability is given. All the specifications and designs are subject to change without notice
due to continuous technology development. No part of this manual may be copied, modified, translated,
or distributed in any manner without the express written permission of us.

We do not guarantee, for any particular purpose, the accuracy, validity, timeliness, legitimacy or
completeness of the Third Party products and contents involved in this manual.

If you have any suggestions or would like to learn more details, please visit our website at:
http://www.hytera.com.
 Software Installation and Configuration Guide Contents

Contents
Documentation Information .................................................................................................................... 1
1. Installing and Configuring Operating System .................................................................................. 3
1.1 Making a USB Boot Disk .................................................................................................................. 3
1.2 Installing Linux OS ............................................................................................................................ 5
1.2.1 Default Installation .................................................................................................................. 5
1.2.2 Customized Installation .......................................................................................................... 8
1.3 Configuring OS parameters ............................................................................................................ 22
1.3.1 Configuring Linux OS on Single MSO Server ...................................................................... 22
1.3.2 Configuring Linux OS on Master and Slave MSO Servers .................................................. 28
1.3.3 Configuring MSO Data Synchronization .............................................................................. 34
1.3.4 Creating Database Files ....................................................................................................... 40
1.3.5 Backing Up the Database File.............................................................................................. 44
1.3.6 Recovering the Database ..................................................................................................... 46
1.3.7 Backing Up Database during System Operation ................................................................. 48
1.3.8 Backing Up Statistics Data ................................................................................................... 49
2. Configuring the Applications ............................................................................................................ 50
2.1 Obtaining Applications and License ............................................................................................... 50
2.1.1 Obtaining the MSO Applications .......................................................................................... 50
2.1.2 Obtaining MSO License File ................................................................................................ 50
2.2 Configuration Instructions ............................................................................................................... 51
2.2.1 Instructions on VOS.Config.db ............................................................................................. 51
2.2.2 Running the Software ........................................................................................................... 72
3. Upgrading and Configuring the MTU ............................................................................................... 74
3.1 Upgrading the MTU Program ......................................................................................................... 74
3.1.1 Querying the Version and Configuration Information........................................................... 74
3.1.2 Upgrading the MTU .............................................................................................................. 78
3.2 Configuring the MTU Software ....................................................................................................... 87
3.2.1 Old Model MTU .................................................................................................................... 87
3.2.2 New Model MTU................................................................................................................... 91
4. Configuring PSTN Gateway ............................................................................................................ 100
4.1 Networking Mode .......................................................................................................................... 100
4.1.1 FXO/FXS-based Mode ....................................................................................................... 100
4.1.2 E1-based Mode .................................................................................................................. 100
4.2 Making a Configuration................................................................................................................. 100
4.2.1 Logging in to PSTN Gateway ............................................................................................. 100
4.2.2 Configuring IP Address of LAN0 ........................................................................................ 102
4.2.3 Configuring SIP Server....................................................................................................... 103
i
 Contents Software Installation and Configuration Guide

4.2.4 Configuring the Rule........................................................................................................... 103

5. Configuring the Firewall .................................................................................................................. 106
5.1 Network Architecture .................................................................................................................... 106
5.2 Setting the Hyper Terminal ........................................................................................................... 106
5.3 Making a Configuration................................................................................................................. 109
5.3.1 Configuring the Basic Information ...................................................................................... 109
5.3.2 Configuring the GRE over IPsec VPN ............................................................................... 109
5.3.3 Configuring the Safety Information .....................................................................................110
6. Configuring the Core Router........................................................................................................... 113
6.1 Network Architecture .................................................................................................................... 113
6.2 Setting the Hyper Terminal ........................................................................................................... 113
6.3 Making a Configuration................................................................................................................. 116
6.3.1 Configuring the Basic Information .......................................................................................116
6.3.2 Configuring the GRE over IPsec VPN ................................................................................116
6.3.3 Viewing the Configuration ...................................................................................................117
7. Configuring the Core Switch........................................................................................................... 118
7.1 Network Architecture .................................................................................................................... 118
7.2 Setting the Hyper Terminal ........................................................................................................... 118
7.3 Making a Configuration................................................................................................................. 121
7.3.1 Making the Basic Configuration ......................................................................................... 121
7.3.2 Configuring the VLAN......................................................................................................... 121
7.3.3 Configuring the Static Route .............................................................................................. 122
7.3.4 Viewing the Configuration .................................................................................................. 122

ii
 Software Installation and Configuration Guide Documentation Information

Documentation Information
This section describes the conventions and revision history of this document.

Documentation Conventions
Icon Conventions
Icon Description

Tip Indicates information that can help you make better use of your product.

Note Indicates references that can further describe the related topics.

Caution Indicates situations that could cause data loss or equipment damage.

Warning Indicates situations that could cause minor personal injury.

Danger Indicates situations that could cause major personal injury or even death.

Notation Conventions
Item Description

The quotation marks enclose the name of a software interface element. For
""
example, click "OK".

The text in boldface denotes the name of a hardware button. For example, press the
Bold
PTT key.

The symbol directs you to access a multi-level menu. For example, to select "New"
->
from the "File" menu, we will describe it as follows: "File -> New".

Revision History
Version Release Date Description

V6.5.00 January 2019  Upgraded to V6.5.00.

V6.1.00 January 2018  Upgraded to V6.1.00.

 Upgraded to V6.0.00.
V6.0.00 October 2017
 Updated the image of system startup screen.

V5.0.01 February 2017 Corrected one descriptive error.

1
 Documentation Information Software Installation and Configuration Guide

Version Release Date Description

V5.0.00 May 2016 Upgraded to V5.0.00.

Added description on log and license configuration items

V4.0.01 July 2015 regarding the VOS.config file, and modified certain command
lines.

V4.0 April 2015 Upgraded to V4.0.

V3.1 December 2014 Upgraded to V3.1.

V3.0 February 2014 Upgraded to V3.0.

V2.0 October 2013 Upgraded to V2.0.

V1.0 April 2013 Changed the configuration items.

V0.1 April 2013 Initial release.

2
 Installing and Configuring Operating System Software Installation and Configuration Guide

1. Installing and Configuring Operating

System
Please note that the figures in this document are for reference only. The elements shown in the figures,
including the file name and version number etc may change and shall be subject to the actual conditions.

1.1 Making a USB Boot Disk

Step 1 Insert a USB disk.

Step 2 Open the UltraISO, find the iso file in the release package from
"Complex_V6.5.00.009\MSC\OS\OS_CentOS(64-bit)_V6.5.013" and double click it, as shown
in the figure below.

Step 3 Click "Bootable" in the toolbar and select "Write Disk Image …", as shown in the figure below.

3
 Software Installation and Configuration Guide Installing and Configuring Operating System

Step 4 Select the USB disk from the "Disk Drive" drop-down list and click "Format", and then click
"Write" after formatting of the USB disk.

4
 Installing and Configuring Operating System Software Installation and Configuration Guide

Step 5 After the writing is complete, click "Close" to finish.

1.2 Installing Linux OS

The OS to be installed on the MSO server is Linux, which must be installed using a Linux system
installation USB disk according to the following procedure.

Note
 If the MSO server adopts DELL, go ahead with the following procedure.
 If the MSO server adopts IBM M5 or SR550, please refer to the Linux installation procedure in
Hytera DS-6210 MSO Software Installation and Configuration Guide V6.5.XX.

OS installation can be divided into default installation and customized installation.

1.2.1 Default Installation

The default installation is available for computers that meet the following configurations:

 Only one hard disk or one RAID is available.

 The OS is installed through USB boot disk or virtual drive.

5
 Software Installation and Configuration Guide Installing and Configuring Operating System

The default configurations are as follows:

1. Language: English
2. Keyboard type: us
3. Time zone: America/New York
4. Root password: Hytera#123
5. Partition: boot partition (500 G), swap partition (memory), and root partition (other capacities)

Step 1 Boot the server from the USB boot disk and select "Install VOS system Default" on the welcome
interface.

Step 2 Select "Hard drive" for "Installation Method" and then click "OK".

6
 Installing and Configuring Operating System Software Installation and Configuration Guide

Step 3 All drives that can be identified by the system will be displayed and normally the bootable USB
drive will be identified as "sda4" or "sdb4". If the selection is correct, the installation will proceed.
Otherwise, reselect the correct drive.

Step 4 After the installation, click "Reboot".

7
 Software Installation and Configuration Guide Installing and Configuring Operating System

1.2.2 Customized Installation

Step 1 Boot the server from the USB disk.

1. Insert the USB disk into the server and power on the server. The following window will
appear after system self-check.

2. Press F11 to enter the "Boot Manager" menu.

8
 Installing and Configuring Operating System Software Installation and Configuration Guide

3. Enter the "Harddisk" menu and select the USB disk boot mode.

Step 2 Enter the system boot interface.

1. Select "Install VOS System" and press Enter.

9
Software Installation and Configuration Guide Installing and Configuring Operating System

2. Select the language as English and press "OK".

3. Select the keyboard type as "US" and press "OK".

10
Installing and Configuring Operating System Software Installation and Configuration Guide

4. Select the "Installation Method" as "Hard drive" and press "OK"

5. All the drives that can be identified by the system will be displayed and normally the USB
disk will be identified as sda4 or sdb4. If the selection is correct, the installation will proceed,
otherwise, reselect the correct drive.

11
 Software Installation and Configuration Guide Installing and Configuring Operating System

Step 3 Enter the installation interface.

1. Click "Next", as shown in the figure below.

12
Installing and Configuring Operating System Software Installation and Configuration Guide

13
 Software Installation and Configuration Guide Installing and Configuring Operating System

2. Enter the "Root Password" and "Confirm" fields with a same number (e.g., Hytera#123), then
click "Next" and click "Use Anyway" in the pop-up dialog box.

Step 4 Set up the hard disk partition.

1. Select "Create Custom Layout". This selection is a must.

14
Installing and Configuring Operating System Software Installation and Configuration Guide

2. Select "sdb" and click "Delete", then click "Delete" again in the pop-up dialog box to delete
the original partitions.

3. The following figure shows the partitions after deletion. Do not delete the installation USB
disk by mistake.

15
Software Installation and Configuration Guide Installing and Configuring Operating System

4. Click "Back" and select "Use All Space".

5. Click "Next".

16
Installing and Configuring Operating System Software Installation and Configuration Guide

6. Select the hard disk intended for the installation (do not select the installation USB disk) and
select "BootLoader".

7. Click "Next" to access the current hard disk partition.

17
Software Installation and Configuration Guide Installing and Configuring Operating System

8. Select "lv_home" and click "Delete", and then click "Delete" again in the pop-up dialog box.

9. Select "lv_root" and click "Edit" to modify the size of "lv_root".

18
Installing and Configuring Operating System Software Installation and Configuration Guide

10. Enter an appropriate value in the "Size (MB)" field and click "OK" to confirm,

11. The following figure shows the hard disk partitions after the modification.

19
Software Installation and Configuration Guide Installing and Configuring Operating System

12. Click "Next" and then select "Write changes to disk" in the pop-up dialog box to format the
hard disk. The formatting process may take minutes depending on size of the hard disk.

13. The following interface appears when the formatting process is completed, and then click
"Next" to install the system.

20
 Installing and Configuring Operating System Software Installation and Configuration Guide

Step 5 Install the system.

1. The following figure shows the installation window.

2. After the installation is completed, click "Reboot" and remove the USB disk.

21
 Software Installation and Configuration Guide Installing and Configuring Operating System

1.3 Configuring OS parameters

1.3.1 Configuring Linux OS on Single MSO Server
Operation Flow
Step 1 Install and configure the Linux OS.

Step 2 Set the role of the server.

Step 3 Set the IP address, mask, and gateway.

Step 4 Set system time.

Step 5 Enable logAgent.

Step 6 Enable tomcat.

Step 7 Install and enable HA.

Step 8 Install MySQL database.

Step 9 Back up the database.

Step 10 Upload and configure the applications.

Step 11 Enable autorun.

Procedures
Step 1 Log in to the OS.

To log in to the Linux system, use the username "root" and password "Hytera#123" (note that
the inputs will not be displayed).

22
 Installing and Configuring Operating System Software Installation and Configuration Guide

Step 2 Configure role.

Instructions:

1. Role is an independent setting used to distinguish the role of the MSO, and is not associated
with other settings.

2. Role is used to distinguish the shared server scenario that whether the MSO is deployed
separately, the centralized network management system (CNMS) is deployed separately, or
both are deployed on the shared server.

3. All servers need to be configured with the role. All servers must be set to “mso”, except that
the CNMS server should be set to “cnms” or “dual”.

4. The role is not required for a base station (BS). Leave its default value as “Unconfigured”.

5. Once the role is modified, it cannot be restored to “Unconfigured”.

6. If it is set to cnms or dual, it is not necessary to restore to Unconfigured, but it must be

changed to the same mso as the MSO.

The server has three role options:

1. mso: server of traditional MSO.

2. cnms: server of the CNMS.

3. dual: shared server of the CNMS and the MSO.

Configuration:

Run the following command:

vos-cmd -m role

Please input the role of this server [mso/cnms/dual]:

mso

View the current configuration status.

vos-cmd -s

The following result suggests that the configuration is successful.

role status:mso

23
 Software Installation and Configuration Guide Installing and Configuring Operating System

Step 3 Set the IP address and subnet mask.

1. Configure the network card eth0.

a. Suppose that the IP address of eth0 is set to 20.0.8.2 and netmask is set to

255.255.255.0, then run the following command.

vos-cmd -m eth0

Please input ip address:

20.0.8.2

Please input netmask:

255.255.255.0

You input IP: 20.0.8.2 netmask: 255.255.255.0

b. Run the following command to enable the network.

vos-cmd -o eth0

c. Run the following command to view the current network configuration.

vos-cmd -s eth0

2. Configure the gateway.

a. Suppose that the gateway address is 20.0.8.1, then run the following command.

vos-cmd -m gw

Please input default gw:

20.0.8.1

You input gw: 20.0.8.1

b. Run the following command to enable the gateway.

vos-cmd -o gw

c. Run the following command to view the current gateway configuration.

vos-cmd -s gw

Step 4 Set the system time and synchronize hardware time with the system time.

1. The system time must use the UTC time. Run the following command to set the system time:

date MMDDhhmmyyyy.ss

For example, if the current Beijing time is 18:30 pm on November 26, 2014, then run the
"date 112610302014.00" command.

24
 Installing and Configuring Operating System Software Installation and Configuration Guide

2. After the system clock is successfully set, run the "hwclock -w" command to synchronize the
hardware time with the system time. If no error prompt is returned, it indicates that the
synchronization is successful.

Note
 Run the "hwclock" command to query the hardware time.
 Run the "date" command to query the system time.

The hardware time must be identical with the system time.

Step 5 Set time synchronization on the NTP server.

1. Run the following command to enable the NTP server.

vos-cmd -o ntps

2. Run the following command to query the NTP service on MSO server.

vos-cmd -s ntps

3. If there is an upper-layer NTP server, you must run the following command to set the IP
address of the upper-layer GPS clock source. Otherwise, skip this step.

vos-cmd -m ntps

Please Ntpdate ip address:

xx.xx.xx.xx (IP address of GPS clock source, two IP addresses are supported, separated
by a space)

Note
For local or offsite MSO redundancy, if there is no GPS clock source, the master and
slave MSO servers function as a clock source for each other.

Step 6 Run the following command to install USB dongle software.

vos-service aksusbd install

25
 Software Installation and Configuration Guide Installing and Configuring Operating System

Note
If the license is based on a USB dongle, it is required to install the dongle software. If
the license is based on the machine code, skip this step.

Step 7 Configure logAgent.

1. Run the following command to install the logAgent.

vos-service vsftpd install

2. Run the following command to enable the logAgent.

vos-cmd -o logc

3. Run the following command to view the status of the logAgent.

vos-cmd -s logc

Step 8 Set the tomcat service.

1. Run the following command to install the tomcat service application.

vos-service tomcat install

2. Run the following command to enable tomcat service.

vos-cmd -o tomcat

Note
This setting is related to the role and redundancy mode. If the server role is cnms or
dual, and the server is deployed in local, offsite or local+offsite rendundancy mode,
then the tomcat service process is started by the rendundancy mode, and no need to
run the “vos-cmd –o tomcat” command.

If the CNMS is deployed in standalone mode, or shares server with single MSO, run
the “vos -cmd –o tomcat” command to enable tomcat.

3. Run the following command to view the status of tomcat service.

vos-cmd -s tomcat

Step 9 Configure HA on the server.

1. Run the following command to install hapl.

vos-service hapl install

vos-service inotify-tools install

vos-service csync2 install

26
 Installing and Configuring Operating System Software Installation and Configuration Guide

vos-service rsync install

2. Run the following command to set HA on the server.

vos-cmd -m ha

Now you will configure ha, please to make sure [y/n]

Please select project type:

1)pdt

2)business

Please select working mode:

1) tsc

2) mso

3) tsc+mso (tsc)

4) tsc+mso (mso)

5)rmso

Please select machine count:

1) one_machine

2) two_machine

1 (Here, "1" should be selected)

3. Run the following command to start the HA.

vos-cmd -o ha

4. Run the following command to check the status of the HA

vos-cmd -s ha

Step 10 Install MySQL.

1. Run the following command to install MySQL.

vos-service mysql install

Step 11 Create database files (using scripts provided in the MSO DB_Server folder). For details, refer to
1.3.4.

Step 12 Back up the database.

27
 Software Installation and Configuration Guide Installing and Configuring Operating System

For details, refer to 1.3.5.

Step 13 Set MySQL auto-startup.

1. Run the following command to enable MySQL.

vos-cmd -o mysql

Now you will open mysql, this is not permitted in MSO backup mode,please to make
sure [y/n]

2. Run the following command to check the status of MySQL.

vos-cmd -s mysql

Step 14 Reboot the system.

In order to reboot the system, Run the "reboot" command to reboot the system, and put the
configuration into effect.

1.3.2 Configuring Linux OS on Master and Slave MSO Servers

To configure the master and slave MSO servers, back up the license file of HyteraHA software on the
two MSO servers first if HyteraHA software has been installed on these servers. To back up the license
file, copy the "License.txt" file under the "/opt/HyteraHA/sys" directory to "/opt/local/sbin/osbak" (cp
/opt/HyteraHA/sys/License.txt /opt/local/sbin/osbak) and stored it in the local computer, and then run
the "rm -rf /opt/HyteraHA" command.
Operation Flow
Step 1 Install and configure OS on both servers respectively.

Step 2 Configure the IP address, mask, and gateway on both servers respectively.

Step 3 Configure system time on both servers respectively.

Step 4 Enable logAgent on both servers respectively.

Step 5 Enable tomcat on both servers respectively.

Step 6 Configure the dedicated network interface for data synchronization on both severs respectively.

Step 7 Configure the HA, HyteraHA License and application services.

Step 8 Install and enable MySQL on both servers respectively.

Step 9 Back up database on both servers respectively.

Step 10 Configure HA on both servers respectively.

Step 11 Enable HA on both servers, and restart the servers.

28
 Installing and Configuring Operating System Software Installation and Configuration Guide

Note
For master and slave MSO servers, it is disallowed to run the "vos-cmd -omysql"
command to start MySQL.

Procedures
Step 1 Install OS on both the master and slave MSO servers and configure the IP address, mask,
gateway, system time, NTPS, logAgent, and tomcat.

For details, refer to Step 1 to Step 8 of 1.3.1.

Step 2 Configure an independent data synchronization channel on both servers (for local backup only).

If the conditions are met on the site, the two servers must be directly connected by a cable
connecting two separate network interfaces on the two servers. More specifically, you need to
configure and enable the eth1 network card on the two servers respectively, and then connect
the two servers via eth1 using a network cable. Suppose that the eth1 IP address of master
MSO server is set to 192.168.20.9, eth1 IP address of slave MSO server is set to 192.168.20.8,
and the subnet mask is set to 255.255.255.0 for both of the servers, do as follows.

1. Configure the master MSO server

a. Run the following command to configure the IP address of the eth1 network interface.

vos-cmd -m eth1

Please input ip address:

192.168.20.9

Please input netmask:

255.255.255.0

You input IP: 192.168.20.9 netmask: 255.255.255.0

b. Run the following command to enable the eth1 network interface.

vos-cmd -o eth1

2. Configure the slave MSO server

a. Run the following command to configure the IP address of the eth1 network interface.

vos-cmd -m eth1

Please input ip address:

192.168.20.8

Please input netmask:

255.255.255.0
29
 Software Installation and Configuration Guide Installing and Configuring Operating System

You input IP: 192.168.20.8 netmask: 255.255.255.0

b. Run the following command to enable the eth1 network interface.

vos-cmd -o eth1

Step 3 Configure HA on the master and slave servers.

1. Local Redundancy

a. Run the following commands to install HyteraHA, inotify-tools, hapl, rsync and csync2.

vos-service HyteraHA install

vos-service inotify-tools install

vos-service csync2 install

vos-service rsync install

vos-service hapl install

b. Configure the hapl.

Suppose that the IP address of the local machine is 20.0.8.3, IP address of the peer
machine is 20.0.8.4, the virtual IP address is 20.0.8.2, gateway is 20.0.8.1, the
synchronization directory is "/opt/local/bin/VOS/cur" (default path), the number of peer
machine checks is 3, the check interval is 2,000 ms, the heartbeat interval is 3s, and the
group ID of master and slave MSO servers is 255. Run the following command.

Note
The group ID must be a unique number within 1 to 255. It is recommended that the
group ID of master and slave MSO servers is set to 255.

vos-cmd -m ha

Now you will configure ha, please to make sure [y/n]

Please select project type:

1) pdt

2) business

Please select working mode:

1) tsc

2) mso

30
Installing and Configuring Operating System Software Installation and Configuration Guide

3) tsc+mso(tsc)

4) tsc+mso(mso)

5) rmso

6) tmso

Please select machine count:

1) one_machine

2) two_machine

Please select state:

1) master

2) slave

1 (Set it to "1" in the case of master MSO server, and "2" in the case of slave MSO server)

Please input the sync dir(/opt/local/bin/VOS/cur):/opt/local/bin/VOS/cur

Please input the local IP:

20.0.8.3 (IP address of the local MSO server)

Please input the peer IP:

20.0.8.4 (IP address of the peer MSO server)

Please input the gateway:

20.0.8.1 (gateway IP address)

Please input the virtual IP:

20.0.8.2 (the master and slave servers must have the same virtual IP address)

Please input the group ID(1~255): 255 (the group ID set on the slave and master servers
must be the same and should not be identical with any other group ID)

Please input the environment check times(3): 3 (the recommended settings is 3)

Please input the environment check interval(ms)(2000ms): 2000 (the recommended

settings is 2000ms)

Please input the delay between advertisements(s)(3s): 3 (the recommended settings for
heartbeat check interval is 3s)

2. Offsite Redundancy

a. Run the following commands to install HyteraGHA, rsync, hapl, inotify-tools and csync2.
31
Software Installation and Configuration Guide Installing and Configuring Operating System

vos-service HyteraGHA install

vos-service inotify-tools install

vos-service csync2 install

vos-service rsync install

vos-service hapl install

b. Run the following command to configure hapl.

vos-cmd -m ha

Now you will configure ha, please to make sure [y/n]

Please select project type:

1) pdt

2) business

Please select working mode:

1) tsc

2) mso

3) tsc+mso(tsc)

4) tsc+mso(mso)

5) rmso

6) tmso

Please select machine count:

1) one_machine

2) two_machine

2 (it must be set to "2" in the case of offsite redundancy)

It is disallowed to enable auto-startup for the MySQL after above settings.

3. Local + offsite redundancy.

a. Run the following command to install hapl and HyteraTHA.

vos-service HyteraTHA install

vos-service inotify-tools install

32
 Installing and Configuring Operating System Software Installation and Configuration Guide

vos-service csync2 install

vos-service rsync install

vos-service hapl install

b. Configure hapl.

vos-cmd -m ha

Now you will configure ha, please to make sure [y/n]

Please select project type:

1) pdt

2) business

Please select working mode:

1) tsc

2) mso

3) tsc+mso (tsc)

4) tsc+mso (mso)

5) rmso

6) tmso

Enable HA (enable HA first before configuration. See 1.3.3 for details)

vos-cmd -o ha

Check whether HA is enabled:

vos-cmd -s ha

Restart the server to validate HA:

reboot

After the server restarts, configure HyteraTHA.

It is disallowed to enable auto-startup for the MySQL after above settings.

Step 4 Configure the HyteraHA License and application service. See 1.3.3 for details.

Step 5 Create database files.

33
 Software Installation and Configuration Guide Installing and Configuring Operating System

Create database files on the two servers, respectively (using the scripts provided in the
DB_Server folder). For details, refer to 1.3.4.

Step 6 Back up the database.

Back up the database on both servers respectively. For details, refer to 1.3.5.

Note
 For local or offsite redundancy, enable HA after HA (local mode) or GHA (offsite
mode) is configured, HA License is imported and the hapl is configured.

 For local+offsite redundancy, enable HA first, and then import the License and
configure HA.

 If the redundancy does not work well, run “vos-cmd –c ha” command and reboot
servers to configure the HA again.

Step 7 Run the following command to enable HA.

vos-cmd -o ha

Run the following command to check the configuration.

vos-cmd -s ha

After configuration is completed, you can run the command "vos-cmd -s" to check
configuration status. And then restart the server to validate the configuration.

1.3.3 Configuring MSO Data Synchronization

Local Redundancy
Step 1 Install HA.

Step 2 Prepare the license for HA.

1. Run "VOS-Hostid" command to obtain the host ID of the local machine. (It is required to
calculate the License file based on "hostid".)

VOS-Hostid

2. Save the obtained License in "License.txt" file, as shown in the following figure.

34
 Installing and Configuring Operating System Software Installation and Configuration Guide

3. Use sftp to upload "License.txt" file to "/tmp".

4. Run "VOS-Loadlic" command to import the license file.

VOS-Loadlic

Caution
Do not frequently import the license file.

Step 3 Configure HA.

Run the following command to configure HA.

VOS-HAConfig

Please select state:

1) master

2) slave

(Set it to "1" in the case of master MSO server, and "2" in the case of slave MSO server.)

Please select database type:

1) mysql

2) oracle

35
Software Installation and Configuration Guide Installing and Configuring Operating System

3) null

(Select database type according to the installed database. If database is not needed,
choose null.)

Please input Local Host’s Data IP:

192.168.20.9 (eth1 IP address of the local MSO server)

Please input Remote Host’s Data IP:

192.168.20.8 (eth1 IP address of the peer MSO server)

Please input Public NIC [eth0/bond0]:

eth1 (data synchronization interface)

Note
If you enter a wrong value, you can press "Backspace" to delete it provided that a
monitor is used. In the event of the SSH remote mode, you should press "Delete" to
delete the incorrect value.

36
 Installing and Configuring Operating System Software Installation and Configuration Guide

Step 4 Enable auto-startup for HA.

Run the "VOS-Cmd" command to enable auto-startup for HA.

vos-cmd -o ha

Step 5 Query the configuration.

Run the "VOS-HAQuery" command to query the configuration.

VOS-HAQuery

Offsite Redundancy
Step 1 Install HA.

Step 2 Prepare the license for HA.

1. Run "VOS-Hostid" command to obtain the host ID of the local machine. (It is required to
calculate the License file based on "hostid".)

VOS-Hostid

2. Save the obtained License in "License.txt" file, as shown in the following figure.

3. Use sftp to upload "License.txt" file to "/tmp".

4. Run "VOS-Loadlic" command to import the license file.

37
 Software Installation and Configuration Guide Installing and Configuring Operating System

VOS-Loadlic

Caution
Do not frequently import the license file.

Step 3 Configure HA.

 Configuring HA

VOS-GHAConfig

Note
If you enter a wrong value, you can press "Backspace" to delete it provided that a
monitor is used. In the event of the SSH remote mode, you should press "Delete" to
delete the incorrect value.

Please select state:

1) master

2) slave

(Set it to "1" in the case of master MSO server, and "2" in the case of slave MSO server. )

Please select database type:

1) mysql

2) oracle

3) null

(Select database type according to the installed database. If database is not needed,
choose null.)

Please input Local Host’s Data IP:

20.0.8.2 (the IP address of the local machine for data synchronization)

38
Installing and Configuring Operating System Software Installation and Configuration Guide

Please input Remote Host’s Data IP:

20.0.8.3 (the IP address of the peer machine for data synchronization)

Please input Public NIC [eth0/bond0]:

eth0 (the port for data synchronization, by default it is eth0)

Now You can input third-ip (one is recommended), and then input q to quit:

20.0.8.1 (Gateway IP address of MSO)

20.0.4.1 (Gateway IP address of BS)

(This address is an IP address helping to judge whether the master and slave servers are
operating normally. The number of such IP addresses shall not exceed 3, and such IP
address is recommended to be a BS IP address, gateway IP address, or another public
device IP address.)

Now You can input bind-ip (>=1), and input q to quit:

20.0.8.2 (bind ip address, which will be explained later)

Now you can set data transmit bandwidth, units: kB/s

(transmit bandwidth: You can set the bandwidth for data synchronization, the unit is kB/s. It
is disabled by default. Make sure the local servers and the remote servers have the same
value for this bandwidth.)

Now you can set take-over timeout, units: s

(take-over timeout: You can set the time after which the remote system will take over the
service, the unit is second, and the value should be an integer. If you do not want to input a
value, press Enter. The default value is 45.)

39
 Software Installation and Configuration Guide Installing and Configuring Operating System

Note
Explanation about Bind-IP under MSO centralized deployment:

In this case, you should set the Bind-IP as the local IP address on the local and
remote MSO servers respectively.

Offsite Redundancy with Local Master and Slave Servers

For configuration of offsite redundancy with local master and slave servers, refer to the "HyteraTHA
Configuration" file under the "Complex_V6.5.00.009\MSC\OS_CentOS(64-bit)_V6.5.006" directory from
the release package.

1.3.4 Creating Database Files

Step 1 Run the following command to install MySQL.

vos-service mysql install

Step 2 Run the following command to manually start the MySQL.

40
 Installing and Configuring Operating System Software Installation and Configuration Guide

/etc/init.d/services/mysql start

Step 3 Prior to creating data files, place the released "my.cnf" file into the "/etc/" folder under the root
directory and run the following command to delete the control M characters.

dos2unix my.cnf

Step 4 Stop the MySQL database and clear the database files.

Run the following command to stop the database:

/etc/init.d/services/mysql stop

Run the following three commands to clear the database files:

rm -rf /opt/local/mysql/data/hytpdt*

rm -rf /opt/local/mysql/data/bill_query

rm -rf /opt/local/mysql/data/ib*

Step 5 Run the "reboot" command to restart the OS.

Step 6 Check whether the MySQL database is started after the reboot. If not, run the following
command to manually start the MySQL database again.

/etc/init.d/services/mysql start

Step 7 Place sqlite3, hss_tsc and offline_bill in the release package

(MSC\MSC_Mysql\DS6211\Centralized\MSC_V6.5.00.009\MSO-DBServer) and a blank
"tsc.db" file to the "/opt/remotepath" folder, then run the following command.

cd /opt/remotepath/

chmod 777 *

dos2unix hss_tsc

dos2unix offline_bill

Note
Do not perform dos2unix operation on sqlite3, otherwise, the sqlite3 may be
damaged.

Step 8 Find the "db_install" installation folder under the "/opt/local/bin/VOS/db" directory.

Step 9 Run the following command.

cd /opt/local/bin/VOS/db/db_install

41
 Software Installation and Configuration Guide Installing and Configuring Operating System

Step 10 Place all shell scripts and database scripts under

"MSC\MSC_Mysql\DS6211\Centralized\MSC_V6.5.00.009\MSO-DBServer" to the "db_install"
folder.

 Shell script

 setup_root (changes password of MySQL database)

 setup_mso (installs and configures the respective databases)

 setvariable (modifies MySQL database parameters)

 event_minute (sets timed task performed every minute)

 event_hour (sets timed task performed every hour)

 event_minute (defines timed tasks performed in each day)

 bill_dump_excel (backs up the traffic statistics data into an excel file)

 nm_data_bill (traffic statistics script)

 nm_hss_data (traffic statistics script)

 init_nm_db.sh (sets the UI language of NMC)

 event_nm_day (newly added in 5.3, required for NMC)

 event_nm_lastmin_hour (newly added in 5.3, required for NMC)

 event_nm_hour (newly added in 5.3, required for NMC)

 Database script

 hytpdtbilldb.sql (traffic statistics database)

 hytpdtbilldb_h.sql (traffic statistics database)

 bill_query.sql (traffic statistics database)

 hytpdtgpsdb.sql (GPS data database)

 hytpdtnmdb.sql (network management database)

 hytpdtvaucdb.sql (authentication center database)

 hytpdthssdb.sql (MSO database)

 hytpdtsmssdb.sql (short data message store and forward database)

 hytpdtsmsshistorydb.sql (short data message store and forward database)

 hytpdtkdmcdb.sql (KDMC database)

 mysqlroot.sql (changes password of MySQL database)

 setvariable.sql (modifies MySQL database parameters)

42
 Installing and Configuring Operating System Software Installation and Configuration Guide

 Chinese.sql (sets Chinese UI of NMC)

 English.sql (sets English UI of NMC)

Step 11 Run the following command to set execute permissions on the above listed files and then
execute these files to complete installation and configuration.

chmod 777 *

Step 12 Run the following command to remove the control M characters due to file conversion.

dos2unix *

Step 13 Run the following command so that "end" is displayed on the display of the computer.

./setup_root

Step 14 Run the following commands.

./setvariable

./setup_mso

Note
You must input "all" no matter whether all the databases are required or not.

Step 15 If you want to install all the above databases, input "all" and then input "1" (Chinese version) or
"2" (English version) according to the prompt. The installation completes when the prompt "End"
is displayed.

43
 Software Installation and Configuration Guide Installing and Configuring Operating System

Caution
After installation is completed, the "vos_bill", "vos_nm", "vos_vauc", "vos_gps",
"vos_mso" and "vos_smss" files will appear in the folder. Do not delete these files,
because they are used to guide how to do auto-backup.

If the traffic statistics data is relatively large, it will affect overall system performance.
Therefore, a threshold is set. Once the threshold is exceeded, the expired data will be
exported to the "/opt/local/bin/VOS/db/bill_excel/" folder in Excel format. If you need to
query the data that have already been deleted from the database, you can send the
Excel file associated with the corresponding date to us for parsing.

1.3.5 Backing Up the Database File

Step 1 Upload the following files and the "statistic" folder (from
"Complex_V6.5.009\MSC\MSC_Mysql\DS6211\Centralized\MSC_V6.5.00.009\MSO-DBServer
") to the "/opt/local/bin/VOS/db/db_backup" folder.

 backup_bill (backs up database)

 backup_nm (backs up database)

 backup_vauc (backs up database)

 backup_mso (backs up database)

 backup_smss (backs up database)

 backup_gps (backs up database)

 backup_dayupdate (backs up data daily)

 delete_backup (deletes data backed up on the same date from the previous year)
44
 Installing and Configuring Operating System Software Installation and Configuration Guide

 source_mso (recovers database)

 statistic folder

Step 2 Run the following command to set permissions on the files and remove the control M
characters.

cd /opt/local/bin/VOS/db/db_backup

chmod 777 *

dos2unix backup_*

dos2unix delete_backup

dos2unix source_mso

cd /opt/local/bin/VOS/db/db_backup/statistic

chmod 777 *

dos2unix *

The system automatically executes the above listed baking up scripts and backup-deleting
script.

Step 3 Modify MySQL backup settings.

1. Run the following command to modify MySQL backup time according to your local time zone.
Time zone range is [-12, 12].

vos-cmd -m db

Please select database type:

1) mysql

2) oracle

Please input time zone:

8 (input your local time zone)

2. Run the following command to enable backup service.

vos-cmd -o db

3. Run the following command to check the backup service status.

vos-cmd -s

Step 4 Restart the server.

reboot

45
 Software Installation and Configuration Guide Installing and Configuring Operating System

Step 5 Input the following command in the command line after the restart.

crontab -l

Check whether all of event_minute, event_hour and event_day are started. If not, contact us for
technical support.

Step 6 If you want to manually back up the database (e.g., bill database), run the following command.

./backup_bill

Caution
 To delete the "delete_backup" script of history backup file means to delete backup
files generated in the same month of previous year.

 If the traffic statistics data is relatively large, it will affect overall system performance.
Therefore, a threshold is set. Once the threshold is exceeded, the expired data will be
exported to the "/opt/local/bin/VOS/db/bill_excel/" folder in Excel format. If you need
to query the data that have already been deleted from the database, you can send the
Excel file associated with the corresponding date to us for parsing.

1.3.6 Recovering the Database

Database recovery is to import the backed up SQL files to the database again.

This operation is only to import the SQL file to the database without adding data.

Step 1 Place "source_mso" file to the "/opt/local/bin/VOS/db/db_backup/" folder and run the following
command.

chmod 777 *

46
 Installing and Configuring Operating System Software Installation and Configuration Guide

dos2unix source_mso

./source_mso

Step 2 Press Enter.

To recover the hytpdtbilldb database, if the backed up file "bill_201150906.sql" exits, input "bill",
and press Enter, as shown in the following figures.

Step 3 Input "bill", and press Enter.

Step 4 Input "20150906", and press Enter, as shown in the following figure.

Step 5 If the file to be imported is too large, you may need to wait for a relatively long time. When "End"
appears, it indicates the importing is completed.

47
 Software Installation and Configuration Guide Installing and Configuring Operating System

1.3.7 Backing Up Database during System Operation

Step 1 After the commissioning is completed, check whether all data is correct and the system
operates normally. If yes, manually run the "backup_dayupdate" script. Then a "latest" folder
containing new backup files will be generated in the script folder.

cd /opt/local/bin/VOS/db/db_backup/

./backup_dayupdate

Step 2 Copy all files in the "latest" folder to the "normal" folder via SSH, or by running the following
command.

cp -aR /opt/local/bin/VOS/db/db_backup/latest/*

/opt/local/bin/VOS/db/db_backup/normal/

Note
If significant change occurs in the data such as user data, be sure to perform the backup
and replace the old files in the "normal" folder with the latest backup files.

48
 Installing and Configuring Operating System Software Installation and Configuration Guide

1.3.8 Backing Up Statistics Data

Run the following command to create an initial statistics data backup file.

cd /opt/local/bin/VOS/cur

chmod 777 prepef

./prepef -T5

49
 Software Installation and Configuration Guide Configuring the Applications

2. Configuring the Applications

2.1 Obtaining Applications and License
2.1.1 Obtaining the MSO Applications
Obtain the released applications and put the required files in the same folder. Afterwards, modify the
parameters in the configuration files based on the actual conditions. Lastly, upload all configuration files
to the "opt/local/bin/VOS/cur" directory of the MSO server through remote access of the Secure Shell
(SSH) software. All files are shown in the figure below.

2.1.2 Obtaining MSO License File

Obtain machine code of the MSO server or Dongle, and then send the ID to the related personnel to
obtain "VOS.lic" (i.e., license file) for the MSO server. Afterwards, upload the "VOS.lic" to the
"/opt/local/bin/VOS/cur" directory of the MSO server.

 To obtain the machine code of MSO server, run the following command.

cd /opt/local/bin/VOS/cur

chmod 777 *

./VOS.exe -s

 To obtain the machine code of Dongle, run the following command.

50
 Configuring the Applications Software Installation and Configuration Guide

cd /opt/local/bin/VOS/cur

chmod 777 *

./VOS.exe -u

2.2 Configuration Instructions

2.2.1 Instructions on VOS.Config.db
There are four MSO deployment modes: single MSO, local MSO redundancy, and offsite MSO
redundancy. For the local MSO redundancy, the IP addresses of the master and slave MSO servers as
indicated in its configuration file are the same, as well as the virtual IP address set in the HA software.
For the offsite MSO redundancy, the IP addresses of the master and slave MSO servers as indicated in
its configuration file are their respective local IP addresses. Other configuration items in the configuration
files of the master and slave MSO servers are the same with the single MSO server. Here we take the
configuration file of single MSO server as example.

In the Windows OS, use the SQLite to open the configuration file "VOS.Config.db" and change the
corresponding settings.

 Configure the log and license settings.

Parameter Value Remarks

“0x40000F4E” indicates that the

MSO log printing is enabled. If it is
LOG/LOGLEVEL 0x40000F4E set to the default “0X00”, the logs
cannot be printed after opening
Logview.

The license server monitors the port

60008. 20.0.2.2 is the IP address of
0:60008 TCP/SERVER/20.0.2.2:60008/0.0.0.0:0 the license server, while 0.0.0.0
means that the IP address of the
peer will not be detected.

51
 Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

The former is the IP address of the

local machine (i.e., MSO server),
LOGAGENT/FTP 20.0.2.2/20.0.2.100
while the latter is the IP address of
the log server.

The value can be "guest" or

"upload". "guest" indicates that the
LOGAGENT/FTPUSER upload FTP data transfer rate is 8 K,
"upload" indicates that the FTP data
transfer rate is 1 M.

 The following figure shows the application programs that run when the VOS platform starts. To run
the programs with start of the VOS platform, change "false" to "true".

52
 Configuring the Applications Software Installation and Configuration Guide

 Configure CRT by modifying the IP address of the corresponding server according to the network
planning, as shown the following figure.

53
Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

The former is the IP address of the local machine

CRT 2/false/20.0.2.2:6088/20.0.0.2:8000 (i.e., MSO server). The latter is the IP address of
the peer machine (i.e., TSC 1).

The former is the IP address of the local machine

CRT 2/false/20.0.2.2:6088/20.0.0.10:8000 (i.e., MSO server). The latter is the IP address of
the peer machine (i.e., TSC 2).

The former is the IP address of the local machine

(i.e., MSO server). The latter is the IP address of
CRT 2/false/20.0.2.2:6088/20.0.0.18:8000 the peer machine (i.e., TSC 3). The command lines
can be added according to the actual number of
TSCs.

The former is the IP address of the local machine

(0.0.0.0 means that the IP address of the local
machine will not be checked). The latter is the IP
CRT 1/false/0.0.0.0:7000/20.0.2.130:6080
address of the peer machine (i.e., MTU). If the
number of MTU is more than 1, the command line
can be added accordingly.

The former is the IP address of the local machine

CRT 1/false/0.0.0.0:7000/20.0.2.188:7000
(0.0.0.0 means that the IP address of the local
54
Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

machine will not be checked), while the latter is the

IP address of the peer machine (i.e., patrol server).

SPGP and MSO are deployed on the same server,

CRT 0/false/20.0.2.2:6088/20.0.2.2:8088
the two IP addresses are the same.

SPGP and MSO are deployed on the same server,

CRT 0/false/20.0.2.2:6088/20.0.2.2:8088
the two IP addresses are the same.

SMSS and MSO are deployed on the same server,

CRT 0/false/20.0.2.2:6088/20.0.2.2:8010
the two IP addresses are the same.

SIPGW and MSO are deployed on the same

CRT 0/false/20.0.2.2:6088/20.0.2.2:8086
server, the two IP addresses are the same.

IDSC and MSO are deployed on the same server,

CRT 2/false/20.0.2.2:6088/20.0.2.2:6001
the two IP addresses are the same.

WLHSW and MSO are deployed on the same

CRT 2/false/20.0.2.2:6088/20.0.2.2:9001
server, the two IP addresses are the same.

WDHSW and MSO are deployed on the same

CRT 2/false/20.0.2.2:6088/20.0.2.2:9002
server, the two IP addresses are the same.

PHSW and MSO are deployed on the same server,

CRT 2/false/20.0.2.2:6088/20.0.2.2:9003
the two IP addresses are the same.

GWHSW and MSO are deployed on the same

CRT 2/false/20.0.2.2:6088/20.0.2.2:9004
server, the two IP addresses are the same.

MGHSW and MSO are deployed on the same

CRT 2/false/20.0.2.2:6088/20.0.2.2:9005
server, the two IP addresses are the same.

V-Auc and MSO are deployed on the same server,

CRT 2/true/20.0.2.2:8888/20.0.2.2:5002
the two IP addresses are the same.

CHSS and MSO are deployed on the same server,

CRT 2/false/20.0.2.2:6088/20.0.2.2:8886
the two IP addresses are the same.

CRT 2/false/20.0.2.2:6088/20.0.2.2:8887 CBILL and MSO are deployed on the same server,

55
 Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

the two IP addresses are the same.

 Configure HSW, IDSC, CBill and HSS by modifying the IP address of the corresponding server by the
network planning, as shown the following figure.

Parameter Value Remarks

IDSC and MSO are deployed on the same server,

IDSC 2/true/20.0.2.2:6001/20.0.2.2:6088
the two IP addresses are the same.

SWL and MSO are deployed on the same server,

SWL 2/true/20.0.2.2:9001/20.0.2.2:6088
the two IP addresses are the same.

SWD and MSO are deployed on the same server,

SWD 2/true/20.0.2.2:9002/20.0.2.2:6088
the two IP addresses are the same.

PHSW and MSO are deployed on the same server,

PHSW 2/true/20.0.2.2:9003/20.0.2.2:6088
the two IP addresses are the same.

GWHSW and MSO are deployed on the same

GWHSW 2/true/20.0.2.2:9004/20.0.2.2:6088
server, the two IP addresses are the same.

MGHSW and MSO are deployed on the same

MGHSW 2/true/20.0.2.2:9005/20.0.2.2:6088
server, the two IP addresses are the same.

CHSS and MSO are deployed on the same server,

CHSS 2/true/20.0.2.2:8886/20.0.2.2:6088
the two IP addresses are the same.

CBILL and MSO are deployed on the same server,

CBILL 2/true/20.0.2.2:8887/20.0.2.2:6088
the two IP addresses are the same.

56
 Configuring the Applications Software Installation and Configuration Guide

 Modify the IP address of the corresponding server according to the network planning, as shown the
following figure.

Parameter Value Remarks

The former is the IP address of the local machine

(i.e., MSO server). The latter is the IP address of the
GPSS 2/false/20.0.2.2:29876/0.0.0.0
peer machine (0.0.0.0 means that the IP address of
the peer machine will not be checked).

 Configure V_AUC by modifying the IP address of the corresponding server by the network planning,
as shown the following figure.

Parameter Value Remarks

The former is the IP address

of the local machine (i.e.,
VOS/SERVICES/IServices/V_AuC 2/false/20.0.2.2:5002/0.0.0.0:8002 MSO server). The latter is
the IP address of the peer
machine (0.0.0.0 means that

57
Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

the IP address of the peer

machine will not be
checked).

The two IP addresses are

VOS/SERVICES/IServices/V_AuC 2/false/20.0.2.2:5002/20.0.2.2:8888 the same, i.e., MSO server
IP address.

0: Without backup hardware

authentication server;
SlaveAuCSwitch 0
1: With backup hardware
authentication server.

IP address of the backup

SlaveAucUDPAddr 10.0.100.222:3696 hardware authentication
server.

IP address of the
AucUDPAddr 10.0.100.220:5000
authentication server.

KDMC and MSO are

deployed on the same
KdmcUDPAddr 20.0.2.2:5500 server. So, this IP address is
the address of the MSO
server.

IP address of the server

where the V_AuC module is
LocalUDPAddr 20.0.2.2:3696
installed, i.e., the IP address
of the MSO server.

Password for E_KEY file,

consistent with
EKeyPassword 11111111
authentication password
configured via the CPS.

58
 Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

HKeyPassword 11111111 Password for H_KEY file.

Authentication key format. 1:

DailMode 2 E_KEY.dat; 2: E-KEY.dmr.
The default setting is 2.

 Configure the database by modifying the IP address of the corresponding server by the network
planning, as shown the following figure.

Parameter Value Remarks

DBServer HssServerIp 20.0.2.2 IP address of the HSS database.

DBServer BillServerIp 20.0.2.2 IP address of the BILL database.

Database type. 0: SQLite; 1:

DBServer DBType 1
MySQL; 2: Oracle.

IP address of the HSS database. If

DB_Server RemoteServerIPAderss 20.0.2.2 the MSC is deployed with the HSS, it
becomes the IP address of the MSC.

Database type. 0: SQLite; 1:

DB_SERVER DBType 1
MySQL; 2: Oracle.

DBServer TopoDBUserName root User name used to log in to the

59
Software Installation and Configuration Guide Configuring the Applications

database.

(for MySQL database, configure it as

root;

for oracle database, configure it as

hytpdtnmdb)

Password used to log in to the

database.

DBServer TopoDBPwd root (for MySQL database, configure it as

root; for oracle database, configure
it as test)

Port used to log in to the database.

(for MySQL database, configure it as

DBServer TopoServerPort 3306
3306; for oracle database, configure
it as 1521)

User name used to log in to the bill

query database.

DBServer BillQueryDBUserName root (for MySQL database, configure it as

root; for oracle database, configure
it as bill_query)

Password used to log in to the bill

query database.

DBServer BillQueryDBPwd root (for MySQL database, configure it as

root; for oracle database, configure
it as test)

Port used to log in to the bill query

database.

DBServer BillQueryServerPort 3306 (for MySQL database, configure it as

3306; for oracle database, configure
it as 1521)

Instance name of the database.

DBServer InstanceName hytpdtnmdb
(for MySQL database, configure it as

60
 Configuring the Applications Software Installation and Configuration Guide

hytpdtnmdb; for oracle database,

configure it as oradb)
 Set the MSO ID according to the planning, as shown in the following figure.

Parameter Value Remarks

MSO SystemID 0x9F00 System ID. It is used to distinguish multiple MSOs.

MSO DMRCmptMode 0 System model. 0: PDT; 1: DMR.

Encryption flag.

0x1: Hytera encryption

0x2: DMRA encryption

MSO g_EncryptFlag 0x4
0x3: DMR encryption

0x4: PDT encryption

(if encryption is not required, keep the default settings)

MSO g_AISTypeMode 0 0: Hytera AIS standard; 1: Standard AIS

Dial Scheme

0: Scheme 1;

1: Scheme 3;

MSO DialPlan 1 2: 1343E

3: MPT1343

4: DMR

5: P3 and CPSX co-site

61
 Software Installation and Configuration Guide Configuring the Applications

7: DMR and MPT1343 co-site

2: g.711a

MSO AISAudioMode 2 3: g.711u

6: AMBE+2™
 Configure the SDS by modifying the GPS data format, as shown the following figure.

Parameter Value Remarks

SDS GPS_DATA_Mode 0 0: standard mode; 1: manufacturer’s own mode.

 Configure the CRM by modifying the CRM data format, as shown the following figure.

Parameter Value Remarks

Number of HSWs. For centralized deployment, leave

CRM GwHswNumber 2
the default value unchanged.

CRM 0/GWHSWID 0x5290 ID of the first GWHSW.

Because GWHSW and MSO are deployed on the

CRM 0/GWHSWEx_IP 20.0.2.2
same server, the two IP addresses are the same.

CRM 1/GWHSWID 0x5291 ID of the second GWHSW and the like.

Because GWHSW and MSO are deployed on the

CRM 1/GWHSWEx_IP 20.0.2.2
same server, the two IP addresses are the same.

 Configure the MGHSW by modifying the AIS voice streams type, as shown the following figure.

Parameter Value Remarks

Voice packet sending interval for AIS. 1: 20

MGHSW/AIS AIS_VoiceStreamsType 1
ms; 0: 60 ms

 Configure the SIPGW and PSTNGW by modifying the IP address of the corresponding server by the
network planning, as shown the following figure.

62
 Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

SIPGW IP 20.0.2.2 IP address of the SIPGW node (i.e., IP address of the MSO server).

PSTNGW IP 20.0.2.2 IP address of the PSTNGW node (i.e., IP address of the MSO server).

 Configure the MTU by modifying the IP address of the corresponding server according to the network
planning, as shown the following figure.

Parameter Value Remarks

The number of MTUs. Configure this value according to the

MTU Number 1
planning.

0/ID: the starting serial number increments when there are

more than one MTU, for example, the second MTU
corresponds to 1/ID; the value corresponds to the MTU ID.
MTU 0/ID 0 x 6000
0x6000: the MTU ID, which increments when there are more
than one MTU, for example, the second MTU corresponds to
0x6001.

IP address of the MTU.

0/IP: the starting serial number increments when there are

MTU 0/IP 20.0.2.130
more than one MTU, for example, the second MTU
corresponds to 1/IP

0/SigPort: the starting serial number increments when there

MTU 0/SigPort 6080 are more than one MTU, for example, the second MTU
corresponds to 1/SigPort

MTU 0/TrafSendPort 6000 0/TrafSendPort: the starting serial number increments when

63
 Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

there are more than one MTU, for example, the second MTU
corresponds to 1/TrafSendPort

0/TrafRecvPort: the starting serial number increments when

MTU 0/TrafRecvPort 6000 there are more than one MTU, for example, the second MTU
corresponds to 1/TrafRecvPort

0/EncryptFlag: the starting serial number increments when

there are more than one MTU, for example, the second MTU
MTU 0/EncryptFlag 0
corresponds to 1/EncryptFlag

Encryption flag. 0: unencrypted; 1: encrypted.

 Configure the SAG, as shown in the following figure.

Parameter Value Remarks

Mode of communication between SAG and the

SPGPCommunicationProtocol 0
SPGP module. 0: IPC; 1: UDP; 2: TCP.

IP address and the port of the machine where the

SPGP module is located if the value of
SpgpAddress 20.0.2.2:8001
"SPGPCommunicationProtocol" is not "0".
Otherwise, this parameter is invalid.

Mode of communication between the SAG and

GpssCommunicationProtocol 0
the GPSS.

IP address and port for communication between

GpssAddress 20.0.2.2:8003 the SAG and GPSS in case of the TCP-IP
communication mode.

LocalUdpAddress 20.0.2.2:38000 IP address and port for local UDP transfer.

64
 Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

LocalIpcAddress 20.0.2.2:8005 IP address and port for local IPC communication.

IP address and port of the network management

TomAddress 20.0.2.2:10086
server.

Mode of communication between the SAG and

OmCommunicationProtocol 0
the network management server.

IP address and port for communication between

OmIp 20.0.2.2:8001 the SAG and network management server in
case of the TCP-IP communication mode.

Dialing scheme. 3: PDT; 4: DMR; 6: MPT1343.

SYS_MODE 3
The default value is 3.

 Configure the AISGW, as shown in the following figure.

Parameter Value Remarks

AISGW AISGWIP 20.0.2.2:5062 IP address and port of AISGW.

 Configure the SPGP, as shown in the following figure.

Parameter Value Remarks

MsoCommunicationProtocol 0 0: IPC; 1: UDP; 2: TCP.

MsoIp 20.0.2.2:6000 IP address and port of MSO server.

SipCommunicationProtocol 0 0: IPC; 1: UDP; 2: TCP.

SipIp 20.0.2.2:8000 IP address and port of SIP server.

"0" means that the local IP address will be

LocalPdtIp 0:7000
automatically obtained. If there are multiple

65
 Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

addresses, this parameter must be specifically set

here.

OmCommunicationProtocol 0 0: IPC; 1: UDP; 2: TCP.

IP address and port of the network management

OmIp 20.0.2.2:8001
agent module.

ReqMsgTimer 10000 Default timer.

GPSSCommunicationProtocol 0 0: IPC; 1: UDP; 2: TCP.

GPSSIp 20.0.2.2:19876 IP address and port of DSS.

Encryption flag.

0x10: HYTERA soft encryption

EncryptFlag 0x10 0x20: DMRA encryption

0x30: MTU hard encryption

0x40: TF card hard encryption

 Configure the PSTNGW by modifying the IP address of the corresponding server according to the
network planning, as shown the following figure.

Parameter Value Remarks

Communication protocol between PSTNGW and

SPGPCommunicationProtocol 0
SPGP.

IP address and port for communication between

SPGPIP 20.0.2.2:8011 the PSTNGW and network management server
in case of the TCP-IP communication mode.

66
 Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

Communication protocol between PSTNGW and

TomProtocalType 0
network management server.

IP address and port for communication between

TOMIp 20.0.2.2:8013 the PSTNGW and network management server
in case of the TCP-IP communication mode.

SIPIp 20.0.2.2:18765 IP address of the PSTNGW deployment server.

PSTNIp 10.0.100.98:5060 IP address and port of PSTN device.

Time interval for sending PSTN heartbeat

PSTN_OPTION_TIME 0 OPTION. It must be consistent with the PSTN
gateway settings.

 Configure the SIPGW by modifying the IP address of the corresponding server according to the
network planning, as shown the following figure.

67
Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

SYS_NUM 2 The number of systems that are interconnected.

SYSID_MYSELF 1 System ID of the current system.

Call_Fsm_Timer 300000 SIPGW status timer.

SYS1_ID 40704 ID of system 1.

SYS1_IP 20.0.2.2:0 IP address of system 1.

This parameter indicates IP address configuration

for local or offsite MSO redundancy. The former IP
SYS1_IP_BAKSYSTEM 0:0 address should be IP address of the slave MSO
server. If the value is 0:0, it means that the system
does not have a slave MSO.

SIP port of system 1. The value 0 represents the

SYS1_SendPort 5060
default port number 5060.

System version. For example, 600 represents V6.0

SYS1_VERSION 600
and 500 represents V5.0.

SYS2_ID 40705 ID of system 2.

SYS2_IP 20.0.2.10:0 IP address of system 2.

This parameter indicates IP address configuration

for local or offsite MSO redundancy. The former IP
SYS2_IP_BAKSYSTEM 0:0 address should be IP address of the slave MSO
server. If the value is 0:0, it means that the system
does not have a slave MSO.

SIP port of system 2. The value 0 represents the

SYS2_SendPort 5060
default port number 5060.

SYS2_VERSION 600 System version. For example, 600 represents V6.0

68
 Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

and 500 represents V5.0.

Voice coding format for system interconnection. 87:

RTP_Type 89
AMBE+2™; 89: SELP; 93: NVOC.

0: heartbeat message will be sent; 1: heartbeat

message will not be sent (for the interconnected
HB_FLAG 1
systems, if the peer system adopts offsite MSO
redundancy, this parameter should be set to 0.)

Heartbeat cycle. The unit is second and the default

HB_CYCLE 5000
is 5 second.

0: heartbeat check is enabled; 1: heartbeat check is

disabled (for the interconnected systems, if the peer
HB_CHECK_LINK_FLAG 1
system adopts offsite MSO redundancy, this
parameter should be set to 0.)

One MSO server sends five heartbeat signals to a

HB_LINK_BREAK_COUNT 5 peer. If no response is received, it will stop sending
heartbeat signals to the peer.

MsoIp 20.0.2.2:6088 IP address of the MSO.

MsoCommunicationProtocol 0 0: UDP; 2: TCP.

GPS subscription format.

GPS_FORMAT 0 0: NMEA text;

1: NEMA binary.

GPS text format.

GPS_NMEA_Type 0 0: GPGLL;

1: GPRMC.

1: Short;

SIPType 1 2: Full;

0: Auto.

 Configure the Agent, as shown in the following figure.

69
 Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

IP address of the network management server (for

single MSO server, it indicates the IP address of the
MSO server; for local MSO redundancy, it indicates
OM_SERVER_IP 20.0.2.2
the virtual IP address of the MSO; for offsite MSO
redundancy, it indicates the IP address of the
master MSO server.)

IP address of the slave MSO server when offsite

OM_SLAVE_IP 20.0.2.2
MSO redundancy is adopted.

IP address of the network management agent, i.e.,

AGENT_IP 20.0.2.2
IP address of the MSO server.

 Configure the TFTP_SERVER, as shown in the following figure.

Parameter Value Remarks

IP address of the TFTP server. The TFTP server is

generally implemented together with the network
TFTP_IPAdress 20.0.2.2
management server in the MSO server, so, the IP
address here is the IP address of the MSO server.

IP address for HSS synchronization. The HSS is

generally implemented together with the database in
NM_HSS_TFTP_IPAdress 20.0.2.2
the MSO server, so, the IP address here is the IP
address of the MSO server.

 Configure the KDMC, as shown in the following figure.

70
Configuring the Applications Software Installation and Configuration Guide

Parameter Value Remarks

IP address for the UDP service provided by KDMC.

This service is often hosted on the MSO server, so,
Local_UDP_IP 20.0.2.2
the IP address here is the IP address of the MSO
server.

Local_UDP_Port 5500 Port for the UDP service provided by KDMC.

IP address of the VACU server. The VAUC service

VAUC_UDP_IP 20.0.2.2 is generally deployed on the MSO server, so, the IP
address here is the IP address of the MSO server.

VAUC_UDP_Port 5501 Port for the UDP service provided by VAUC.

Password for the "KDMCKey.dat" file, and also the

CIPHER 11111111
password for the OTAR key generator.

DBServerIp 20.0.2.2 IP address of the HSS database.

Database type.

0: SQLite;
DBType 1
1: MySQL;

2: Oracle.

Port used to log in to the database.

DBServerPort 3306 (for MySQL database, configure it as 3306;

for oracle database, configure it as 1521)

User name used to log in to the database.

DBUserName root
(for MySQL database, configure it as root;
71
 Software Installation and Configuration Guide Configuring the Applications

Parameter Value Remarks

for oracle database, configure it as hytpdtnmdb)

Password used to log in to the database.

DBPwd root (for MySQL database, configure it as root;

for oracle database, configure it as test)

Instance name of the database.

InstanceName hytpdtkdmcdb
(for MySQL database, configure it as hytpdtnmdb)

2.2.2 Running the Software

Step 1 Copy the modified MSO configuration file to the "opt/local/bin/VOS/cur/data" folder of the MSO
server. Run the following command to set execute permission on the files in the "cur" folder, and
remove the control M characters from the database script.

chmod 777 *

dos2unix car_cfg_*.ini

dos2unix keyfile.conf

dos2unix start_mysql.sh

dos2unix stop_mysql.sh

Step 2 Enable auto-startup for the software.

1. Run the following command to enable auto-startup.

vos-cmd -o autorun

2. Run the following command to view the auto-startup status.

vos-cmd -s autorun

(Optional) If necessary, run the following command to disable the auto-startup.

vos-cmd -c autorun

Step 3 Run "reboot" command to restart the system.

reboot

Step 4 To view the processes that have already been started, run the ps -ef|grep exe command.

To manually start a process, run the “VOS-Start” command;

To manually terminate a process, run the “VOS-Stop” command;

To manually restart a process, run the "VOS-Reset" command.

72
Configuring the Applications Software Installation and Configuration Guide

73
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

3. Upgrading and Configuring the MTU

This chapter describes how to configure and upgrade the MTU. If the MTU version is consistent with the
version matching table, directly configure the MTU. If not, first upgrade the MTU and then configure it.
For more information about checking the version, refer to 3.1.1.

3.1 Upgrading the MTU Program

The upgrade method described in this section is applicable to the old model MTU (from V3.0 or earlier to
V5.0) as well as the new model MTU which is provided with console port and USB port on its rear panel.

Caution
Telnet and tftp services are required in order to support the upgrade.

3.1.1 Querying the Version and Configuration Information

3.1.1.1 Old Model MTU
Step 1 Start the PuTTY tool and set the serial port as follows: baud rate: 115200, data bits: 8, parity:
none, stop bits: 1 bit, flow control: none.

74
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 2 Connect the MTU to the computer using a serial cable, and then turn on the MTU and check the
MTU configuration information, as shown in the following figure. The first number underlined in
red indicates the MTU version.

Caution
Do not hot plug or unplug the serial cable.

3.1.1.2 New Model MTU

Step 1 Start the PuTTY tool and set the serial port as follows: baud rate: 115200, data bits: 8, parity:
none, stop bits: 1 bit, flow control: none.

75
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

Step 2 Connect the MTU at its CONSOLE port using a USB cable, and then power on the MTU and
check the MTU configuration information, as shown in the figure below.

76
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 3 If the IP address of the MTU is already known, you can view the MTU configuration using
"MTU_PSS" (this application is provided in software package
"Complex_V6.5.00.009\Tools\MTU-PSS_V6.5.001\Release"). Configure the IP address of the
computer such that it is in the same network segment with the MTU. Directly connect the MTU
and the computer using a network cable. Run the MTU_PSS, input the "MTU IP" and "Local
Port", leave the "Port" by default (7777), then click "Connect", as shown in the figure below.

77
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

3.1.2 Upgrading the MTU

3.1.2.1 Old Model MTU (earlier than V3.0)
Step 1 Check the MTU configuration. If the IP address of the MTU is not 192.168.40.110 by default, set
the IP address of the computer in the same subnet as the IP address of the MTU. If the IP
address of the MTU is the default 192.168.40.110, set the IP address of the computer to
192.168.40.5.

Step 2 Log in to the MTU system through Telnet and back up the ESN file. You also need to open
tftpd32.

1. Run "putty.exe".

78
Upgrading and Configuring the MTU Software Installation and Configuration Guide

2. Input the IP address of the MTU in the host name line and choose "Telnet" from connection type.

3. Click "Open".

 Login name: root

 Password: 123456

4. Press Enter.

5. Run the "cd /yaffs2/" command to enter the "yaffs2" directory. Run the "Is" command to view
contents in the directory, as shown in the figure below.

cd /yaffs2/

ls

79
Software Installation and Configuration Guide Upgrading and Configuring the MTU

6. Run "tftpd32.exe" on the Windows server to start the tftp service, and then run the following
command.

tftp -pl fiel.c 192.168.40.5 (this IP address is the IP address of the computer
running the upgrade tool)

A "fiel.c" file is generated in the tftp service directory (where the tftpd32.exe is located) to
save the ESN file.

Step 3 Upgrade the MTU.

1. Place the upgrade file "MTU.bin" and "MTU_update.img" to the upgrade folder (the default
folder, or the folder where the tftpd32.exe is located) and enable the tftp service.

2. Set the IP address of the computer to "192.168.40.5" (fixed).

3. Restart the MTU.

4. When "Hit any key to stop autoboot" is displayed, press Enter to enter the uboot interface,
as shown in the figure below.

80
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

5. Upgrade the MTU program.

Run "tftp 31000000 MTU_update.img" command to copy the upgrade script into the
memory

Run "autoscr 31000000" command to execute the upgrade script

The MTU will be restarted automatically and the system information will be output through
the serial port. The MTU configurations are recovered to default values (IP address:
192.168.40.110, CODEC: AMBE+2™, gain: 4).

Step 4 Write the ESN file back.

1. Log into the MTU system through Telnet again (IP address of MTU: 192.168.40.110).

2. Run the following command:

cd /yaffs2/

81
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

tftp -gr fiel.c 192.168.40.5 (fixed)

ls

3. Run the following command:

cp /25_2_30_esn /yaffs2/

./25_2_30_esn

The write-back completes when "change ok" appears.

3.1.2.2 Old Model MTU (later than V3.0)
Step 1 Check the MTU configuration. If the IP address of the MTU is not 192.168.40.110 by default, set
the IP address of the computer as the IP address of the MTU. If the IP address of the MTU is
the default 192.168.40.110, set the IP address of the computer to 192.168.40.5.

Step 2 Log in to the MTU system through Telnet and back up the configuration file "config.ini". You also
need to open tftpd32.

1. Run "putty.exe".

82
Upgrading and Configuring the MTU Software Installation and Configuration Guide

2. Input the IP address of the MTU in the host name line and choose "Telnet" from connection type.

3. Click "Open".

 Login name: root

 Password: 123456

4. Press Enter.

5. Run the "cd /yaffs2/" command to enter the "yaffs2" directory. Run the "Is" command to view
contents in the directory, as shown in the figure below.

cd /yaffs2/

ls

83
Software Installation and Configuration Guide Upgrading and Configuring the MTU

6. Run "tftpd32.exe" on the Windows server to start the tftp service, and then run the following
command.

tftp -pl config.ini 192.168.40.5 (this IP address is the IP address of the computer
running the upgrade tool)

A "fiel.c" file is generated in the tftp service directory (where the tftpd32.exe is located) to save
the "config.ini" file.

Step 3 Upgrade the MTU.

1. Place the upgrade file "MTU.bin" and "MTU_update.img" to the upgrade folder (the default
folder, or the folder where the tftpd32.exe is located) and enable the tftp service.

2. Set the IP address of the computer to "192.168.40.5" (fixed).

3. Restart the MTU.

4. When "Hit any key to stop autoboot" is displayed, press Enter to enter the uboot interface,
as shown in the figure below.

84
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

5. Upgrade the MTU program.

Run " tftp 31000000 cram_update.img" command to copy the upgrade script into the
memory

Run "autoscr 31000000" command to execute the upgrade script

The MTU will be restarted automatically and the system information will be output through
the serial port. The MTU configurations are recovered to default values (IP address:
192.168.40.110, CODEC: AMBE+2™, gain: 4).

Step 4 Write the configuration file back.

1. Log into the MTU system through Telnet again (IP address of MTU: 192.168.40.110).

2. Run the following command:

cd /yaffs2/

tftp -gr config.ini 192.168.40.5 (fixed)

85
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

Restart the MTU after the write-back completes and the configurations take effect.
3.1.2.3 New Model MTU
Step 1 Open MTU_PSS and connect the MTU to the computer.

Step 2 Click "Update" tab, select "Application", "uImage", "Rootfs", "Convert" or "Fireware" from the
"Update Type" drop-down list and load the update file (the directory is
"Complex_V6.5.00.009\MSC\MTU\MTU_V6.5.04.004\UpdateBinFile"), then click "Update"
button, as shown in the figure below.

1. Select the "Update Type".

2. Select the update file.

86
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 3 Restart the MTU after the Application, uImage and Rootfs are all upgraded.

Note
 Application: application file
 uImage: kernel image file
 Rootfs: file system

3.2 Configuring the MTU Software

3.2.1 Old Model MTU
3.2.1.1 Modifying the configuration items
Step 1 After the upgrade of the MTU software, all of the MTU’s configurations remain default except
the MAC address. You can modify the configuration items as per actual needs. The
configuration options are saved in the "/yaffs2/config.ini" folder and can be modified by "vi"
command:

cd /yaffs2/

ls

vi config.ini

Note
 Input "a" or "i" to edit the configuration file.

 After the modification, press Esc, then press "Shift+:" to enter the command line

87
Software Installation and Configuration Guide Upgrading and Configuring the MTU

mode, input "wq!" and click Enter to save and quit.

 Restart the MTU to make the configurations take effect.

The contents of the configuration file are shown in the following figure.

The items include:

 MTU_IP: IP address of the MTU

 MTU_SIG_PORT: signal port of the MTU

 MTU_VOICE_PORT: voice port of the MTU

 MTU_MAC_ADDRESS: MAC address of the MTU

 MTU_GATEWAY: gateway of the MTU

 MTU_MASK: mask of the MTU

 WD_GAN_SET: gain adjustment of the wired terminal (maximum: 8, values larger than 8
will be taken as 8)

 WL_CODEC_TYPE: voice coding scheme of the wireless terminal (AMBE+2™ and SELP)

 CC_*_IP: IP address of the *th MSO (e.g., CC_1_IP represents the IP address of the 1st
MSO)
88
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

 CC_*_SIG_PORT: signal port of the *th MSO (e.g., CC_1_SIG_PORT represents the
signal port of the 1st MSO)

 NVOC_AGC_STATE: auto gain switch state of NVOC (0: off, 1: on, default: 0)

Note
The MTU of version later than MTU3.0.03.003 supports separate control, i.e., it can be
controlled by different NEs, and each NE can control multiple voice lines simultaneously
without interference among each other.

Separate control shall satisfy the following two conditions:

 Multiple LDSs configured on the same MTU cannot call each other.

 One MTU works for one system only and cannot be controlled by multiple systems.

Step 2 Alternatively, you can check the MTU version by running the following command:

cd /yaffs2/

vi version.txt

Press Esc, then press "Shift+:" to enter the command line mode, input "wq!" and click Enter to
save and quit.

Note
The version number can be queried only and cannot be changed. Even if it is changed, it
will recover after the MTU is restarted.

3.2.1.2 Encrypting the MTU (soft encryption)

Step 1 Open the MTU_ENCRYPT_Tool which can be found in the release package
"Complex_V6.5.00.009\Tools\MTU_ENCRYPT_Tool_V2.5.001", as shown in the following
figure.

89
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

Step 2 Select the key length from the "Encrypt Length" drop-down list and then click "Add".

Step 3 Enter the key value under "Key Value" field and then click Enter.

Step 4 Click "Export file" to generate the key file.

Step 5 Click "OK" in the pop-up dialog box. Now a key file named "encrypt_table" is created in the
folder where the MTU_ENCRYPT_Tool is located.

90
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 6 Place the "encrypt_table" file into the folder where the PuTTY tool is located. Open the PuTTY
tool. You also need to open tftpd32. Upload the "encrypt_table" file to the MTU by running the
following command:

cd /yaffs2/

tftp -gr encrypt_table 192.168.40.5 (this IP address is the IP address of the

computer running the upgrade tool)

Step 7 Modify the configuration file "config.ini" according to section 3.2.2.1. Modify the CC item to the
IP address and the port number to those of the corresponding MSO or LDS.

Step 8 Restart the MTU to make the configurations take effect.

3.2.2 New Model MTU

3.2.2.1 Modifying the configuration items
Step 1 Open MTU_PSS and connect the MTU to the computer.

91
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

Step 2 Configure the MTU parameters as described in the table below.

Parameter Description Remarks

VERSION Version Unchangeable

MTU IP IP address of MTU Subject to actual condition.

MTU MASK Subnet mask of MTU Subject to actual condition.

MTU GATEWAY Gateway IP address of MTU Subject to actual condition.

MTU MAC MAC address of MTU Unchangeable

MTU SIG PORT Signaling port of MTU Default value: 6080

MTU VOICE PORT Voice port of MTU Default value: 600

Voice coding and decoding

MTU WL TYPE NOVC or SELP or AMBE+2™
scheme

MTU WD GAIN Gain of the wired terminal Range: 1 to 8, default value: 4

Options include PERIPHERALS,

HARD ENCRYPT TYPE Hard encryption type OBDMR, OBPDT and LDS. Currently,
only OBPDT is supported.

92
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Parameter Description Remarks

IP address of cipher
ENCRYPT PERIPHERALS IP Not used in 5.0
machine

MTU ENCRYPT PORT 1 Encryption port Not used in 5.0

MTU ENCRYPT PORT 2 Encryption port Not used in 5.0

Communication protocol used for MTU.

UDP is used by default. If serious
SIG TYPE Signaling type signaling packet loss occurs, TCP may
be used. In that case, make sure the
API and MSO are both modified.

Step 3 Click "Set All" to configure basic parameters of the MTU.

Step 4 Click the "CC Info" tab to configure the parameters as described in the table below.

Parameter Description Remarks

IP address of the MSO server, recording server or dispatch server.

CC1 IP IP address 1
The default port number is 7000.

93
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

IP address of the MSO server, recording server or dispatch server.

CC2 IP IP address 2
The default port number is 7000.

IP address of the MSO server, recording server or dispatch server.

CC3 IP IP address 3
The default port number is 7000.

IP address of the MSO server, recording server or dispatch server.

CC4 IP IP address 4
The default port number is 7000.

IP address of the MSO server, recording server or dispatch server.

CC5 IP IP address 5
The default port number is 7000.

IP address of the MSO server, recording server or dispatch server.

CC6 IP IP address 6
The default port number is 7000.

IP address of the MSO server, recording server or dispatch server.

CC7 IP IP address 7
The default port number is 7000.

IP address of the MSO server, recording server or dispatch server.

CC8 IP IP address 8
The default port number is 7000.

Step 5 Click "MTU Info" tab after the configuration and click "Restart" to restart the MTU.

Caution
It is recommended to restart the MTU by "Restart" command after the configurations are
made. If you want to power off the MTU, wait at least five seconds after the configurations
are made, otherwise, the configurations may not succeed.

3.2.2.2 Encrypting the MTU

Soft Encryption
Step 1 Open the MTU_ENCRYPT_Tool which can be found in the release package
"Complex_V6.5.00.009\Tools\MTU_ENCRYPT_Tool_V2.5.001", as shown in the following
figure.

94
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 2 Select the desired length of encryption key under the "Encrypt Length" option, and then click
"Add", as shown in the following figure.

Step 3 Enter the key value under "Key Value" field and then click Enter.

Step 4 Click "Export file" to generate the key file.

95
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

Step 5 Click "OK" in the pop-up dialog box. Now a key file named "encrypt_table" is created in the
directory where the MTU_ENCRYPT_Tool is located.

Step 6 Open MTU_PSS and connect the MTU to the computer. Click "Update" to load the encryption
key file "encrypt_table". Then click "Put" to import the "encrypt_table" file to "/home" folder of the
MTU.

Caution
MTU_PSS and PuTTY tool cannot run at the same time.

Step 7 Open the PuTTY tool and log in to the MTU through telnet.

96
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 8 Check if the "encrypt_table" file is present in the "/home" folder.

Step 9 Import the "encrypt_table" file to the "loadapp" folder by running the following command.

cd /loadapp

cp /home/encrypt_table /loadapp

ls

reboot

Step 10 Open MTU_PSS and connect to the MTU, then click "CC Info" tab to configure the IP address
and port of the corresponding MSO or LDS, according to section 91.

97
 Software Installation and Configuration Guide Upgrading and Configuring the MTU

Step 11 Restart the MTU to make the configurations take effect.

Hard Encryption
Step 1 Open MTU_PSS and connect the MTU (with built-in encryption board) to the computer directly
using a network cable.

Step 2 Click "CC Info" tab to configure the IP address and port of the corresponding MSO or LDS,
according to section 91.

98
 Upgrading and Configuring the MTU Software Installation and Configuration Guide

Step 3 Select the HARD ENCRYPT TYPE according to section 91.

Step 4 Restart the MTU to bring the configurations into effect.

99
 Software Installation and Configuration Guide Configuring PSTN Gateway

4. Configuring PSTN Gateway

4.1 Networking Mode
The networking mode of the PSTN gateway includes FXO/FXS-based mode and E1-based mode.

4.1.1 FXO/FXS-based Mode

The voice gateway employs the FXO to connect to FXS of PBX, and uses FXS to connect to FXO of
PBX. Thus the terminal in the DMR system can communicate with the telephone, as shown in the
following figure.

FXO FXS
DMR
FXS FXO

PBX
PSTN
Gateway

4.1.2 E1-based Mode

The voice gateway employs the E1 to connect to E1 of PBX. Thus the terminal in the DMR system can
communicate with the telephone, as shown in the following figure.

E1 E1
DMR

PBX
PSTN
Gateway

4.2 Making a Configuration

4.2.1 Logging in to PSTN Gateway
Requirement
Prepare a PC and connect it to the network with which the PSTN voice gateway works.
Additional Information
 As for the PSTN gateway, the default IP address is "192.168.1.10" and subnet mask is
"255.255.255.0".

100
 Configuring PSTN Gateway Software Installation and Configuration Guide

 By default, the username for login is "admin" and the password is "nice".
Procedure
Step 1 Configure the IP address of the PC. Make sure that this IP address is in the same network
segment as the PSTN gateway. Now we take Windows 7 for example.

1. Click in the lower-right corner of your screen.

2. Click "Open Network and Sharing Center".

3. Click "Change adapter settings" in the left navigation tree and go to "Network Connection"
page.

4. Right-click "Local Area Connection" and select "Properties" in the context menu to access
"Local Area Connection Properties" dialog.

5. Select "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties" to access "Internet
Protocol Version 4 (TCP/IPv4) Properties" dialog, as shown in the following figure.

6. Set the IP address and subnet mask, and then click "OK".

Note
Here we take "192.168.1.3" as an exemplary IP address.

101
 Software Installation and Configuration Guide Configuring PSTN Gateway

Step 2 Open Internet Explorer and input "http://192.168.1.10" (i.e., IP address of the PSTN voice
gateway) in the address field, and then a dialog box appears, as shown in the figure below.

Step 3 Input the username and password, and then click "OK".

Note
To obtain the latest parameter settings, click "Read ROM" after login each time.

4.2.2 Configuring IP Address of LAN0

Procedure
Step 1 Click "Network" from the left navigation tree to access the following page.

Step 2 Enter the IP address, subnet mask and default gateway IP address based on your actual
conditions, and then click "OK".

Note
The IP Address of LAN0 is the true IP Address of PSTN gateway in the network.

Step 3 Reboot the gateway to make configurations take effect.

Toggle the power switch of PSTN gateway to "OFF" and then to "ON".

102
 Configuring PSTN Gateway Software Installation and Configuration Guide

4.2.3 Configuring SIP Server

Procedure
Step 1 Click in front of the "VOIP" Parameter in the left navigation tree, and select "Server" to
access the following page.

Step 2 Enter the "<IP address of central server>: 18765" in the "Domain" field. Then click "OK" and
"Write ROM".

Note
Leave other parameters in the above page at their default value.

Step 3 Reboot the gateway to make configurations take effect.

Click "Reboot" and a dialog box appears, then click "OK" to finish.

4.2.4 Configuring the Rule

Procedure
Step 1 Click in front of the "Rule" parameter in the left navigation tree, and select "Router" to
access the following page.

103
 Software Installation and Configuration Guide Configuring PSTN Gateway

Step 2 Select the routing parameter of all items with the "SID" of "09" and click "Modify".

Step 3 Click the value in the "Description" field. The following page appears.

104
 Configuring PSTN Gateway Software Installation and Configuration Guide

Step 4 Enter the IP address of central server in the "Addr" field, and click "OK". Then click "Write
ROM".

Note
Leave the port at its default value.

Step 5 Reboot the gateway to make your modifications take effect after modifying all items with "SID"
of 09.

Click "Reboot" and a dialog box appears, then click "OK" to finish.

Caution
If the system adopts DMR dialing scheme, please contact us for technical support to get
the PSTN template.

105
 Software Installation and Configuration Guide Configuring the Firewall

5. Configuring the Firewall

The following takes USG2220 for example.

5.1 Network Architecture

In this example, the firewall works in the router mode. The E1/2 interface is connected with the user
network; the E1/0 interface is connected with the core switch; and the E0/0 and E0/1 interfaces are
respectively connected with the final port of each VLAN of the Layer 2 switch.

The topology is shown below:

E0/12 E0/0
Local
NMC E1/0/47
E1/0

E0/24 E0/1
Firewall Core
Core Router
Switch

Local
LDS

5.2 Setting the Hyper Terminal

Here we take a Windows XP hyper terminal for example.

Step 1 Use the console cable to connect the serial port on the computer and the console port on the
firewall.

Cable

Serial Port Console Port

Step 2 Select "Start -> All Programs -> Accessories -> Communications -> Hyper Terminal", and the
"Connection Description" dialog will appear.

106
 Configuring the Firewall Software Installation and Configuration Guide

Step 3 Enter "H3C" in the "Name" field, and select an icon. Then click "OK", and the "Connect To"
dialog will appear.

Step 4 Select a serial port used for connection. Then click "OK", and the port property dialog will
appear.

107
 Software Installation and Configuration Guide Configuring the Firewall

Step 5 Configure the parameters. Then click "OK", and the "H3C-Hyper Terminal" window will appear.

Step 6 Power up the firewall for self-check. After the self-check is completed, press the Enter key on
the keyboard. Then the command prompt will appear.
108
Configuring the Firewall Software Installation and Configuration Guide

5.3 Making a Configuration

Note
This section only introduces the specific operations. The IP address, interface and other
information need to be configured according the actual requirements.

5.3.1 Configuring the Basic Information

<USG2200>system-view

[USG2200]sysname SZ_FW_1

[SZ_FW_1]firewall tcp-mss 1432

[SZ_FW_1]aaa

[SZ_FW_1-aaa]local-user root password cipher hytera

[SZ_FW_1-aaa]local-user root level 1

[SZ_FW_1-aaa]local-user root service-type web terminal telnet ssh ftp

[SZ_FW_1-aaa]quit

[SZ_FW_1]super password cipher hytera@123

[SZ_FW_1]user-interface console 0

[SZ_FW_1-ui-console0]authentication-mode aaa

[SZ_FW_1-ui-console0]quit

[SZ_FW_1]interface LoopBack 1

[SZ_FW_1-LoopBack1]ip address 20.0.3.247 255.255.255.255

[SZ_FW_1-LoopBack1]quit

[SZ_FW_1]interface GigabitEthernet 0/0/0

[SZ_FW_1-GigabitEthernet0/0/0]ip address 20.0.14.6 255.255.255.252

[SZ_FW_1-GigabitEthernet0/0/0]quit

[SZ_FW_1]interface GigabitEthernet 0/0/1

[SZ_FW_1-GigabitEthernet0/0/1]ip address 1.1.1.1 255.255.255.0

[SZ_FW_1-GigabitEthernet0/0/1]quit

5.3.2 Configuring the GRE over IPsec VPN

Configuring the ACL
[SZ_FW_1]acl number 3001

[SZ_FW_1-acl-adv-3001]rule 5 permit ip source 1.1.1.1 0 destination 1.1.1.2 0

[SZ_FW_1-acl-adv-3001]quit

Configuring the IKE PEER

[SZ_FW_1]ike proposal 1

109
Software Installation and Configuration Guide Configuring the Firewall

[SZ_FW_1-ike-proposal-1]authentication-algorithm md5

[SZ_FW_1-ike-proposal-1]quit

[SZ_FW_1]ike peer todnr_1

[SZ_FW_1-ike-peer-todnr_1]pre-shared-key hytera

[SZ_FW_1-ike-peer-todnr_1]undo version 2

[SZ_FW_1-ike-peer-todnr_1]remote-address 1.1.1.2

[SZ_FW_1-ike-peer-todnr_1]quit

Configuring the IPsec Proposal

[SZ_FW_1]ipsec proposal todnr

[SZ_FW_1-ipsec-proposal-todnr]quit

Configuring the IPsec Policy

[SZ_FW_1]ipsec policy todnr 1 isakmp

[SZ_FW_1-ipsec-policy-isakmp-todnr-1]security acl 3001

[SZ_FW_1-ipsec-policy-isakmp-todnr-1]proposal todnr

[SZ_FW_1-ipsec-policy-isakmp-todnr-1]ike-peer todnr_1

[SZ_FW_1-ipsec-policy-isakmp-todnr-1]quit

Applying the IPsec Policy

[SZ_FW_1]interface GigabitEthernet 0/0/1

[SZ_FW_1-GigabitEthernet0/0/1]ipsec policy todnr

[SZ_FW_1-GigabitEthernet0/0/1]quit

Configuring the GRE Tunnel

[SZ_FW_1]interface Tunnel 1

[SZ_FW_1-Tunnel1]ip address 10.0.0.1 255.255.255.0

[SZ_FW_1-Tunnel1]tunnel-protocol gre

[SZ_FW_1-Tunnel1]source GigabitEthernet0/0/1

[SZ_FW_1-Tunnel1]destination 1.1.1.2

[SZ_FW_1-Tunnel1]gre key 888888

[SZ_FW_1-Tunnel1]quit

5.3.3 Configuring the Safety Information

Configuring the Safety Zone
[SZ_FW_1]firewall zone trust

[SZ_FW_1-zone-trust]add interface GigabitEthernet0/0/0

[SZ_FW_1-zone-trust]quit

[SZ_FW_1]firewall zone untrust

110
Configuring the Firewall Software Installation and Configuration Guide

[SZ_FW_1-zone-untrust]add interface GigabitEthernet0/0/1

[SZ_FW_1-zone-untrust]quit

[SZ_FW_1]firewall zone dmz

[SZ_FW_1-zone-dmz]add interface Tunnel 1

[SZ_FW_1-zone-dmz]quit

[SZ_FW_1]firewall zone dmz

[SZ_FW_1-zone-dmz]add interface Tunnel 1

[SZ_FW_1-zone-dmz]quit

Configuring the Safety Policy

[SZ_FW_1]firewall packet-filter default permit interzone local dmz

[SZ_FW_1]firewall packet-filter default permit interzone trust dmz

[SZ_FW_1]policy interzone local untrust inbound

[SZ_FW_1-policy-interzone-local-untrust-inbound]policy 0

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]action permit

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]policy service service-set esp

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]policy service service-set telnet

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]policy service service-set ssh

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]policy service service-set icmp

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]policy service service-set gre

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]policy service service-set udp

[SZ_FW_1-policy-interzone-local-untrust-inbound-0]quit

[SZ_FW_1-policy-interzone-local-untrust-inbound]quit

Configuring the Attack Defense

[SZ_FW_1]firewall defend udp-short-header enable

[SZ_FW_1]firewall defend http-flood enable

[SZ_FW_1]firewall defend port-scan enable

[SZ_FW_1]firewall defend ip-sweep enable

[SZ_FW_1]firewall defend teardrop enable

[SZ_FW_1]firewall defend route-record enable

[SZ_FW_1]firewall defend source-route enable

[SZ_FW_1]firewall defend ip-fragment enable

[SZ_FW_1]firewall defend tcp-flag enable

[SZ_FW_1]firewall defend winnuke enable

[SZ_FW_1]firewall defend fraggle enable

111
Software Installation and Configuration Guide Configuring the Firewall

[SZ_FW_1]firewall defend tracert enable

[SZ_FW_1]firewall defend icmp-unreachable enable

[SZ_FW_1]firewall defend icmp-redirect enable

[SZ_FW_1]firewall defend large-icmp enable

[SZ_FW_1]firewall defend ping-of-death enable

[SZ_FW_1]firewall defend icmp-flood enable

[SZ_FW_1]firewall defend udp-flood enable

[SZ_FW_1]firewall defend syn-flood enable

[SZ_FW_1]firewall defend smurf enable

[SZ_FW_1]firewall defend land enable

[SZ_FW_1]firewall defend ip-spoofing enable

[SZ_FW_1]firewall defend arp-flood enable

[SZ_FW_1]firewall defend arp-spoofing enable

[SZ_FW_1]firewall defend sip-flood enable

Configuring the Static Route

[SZ_FW_1]ip route-static 20.0.2.0 24 GigabitEthernet0/0/0

[SZ_FW_1]ip route-static 20.0.10.0 255.255.255.248 Tunnel 1

[SZ_FW_1]quit

<SZ_FW_1>save

112
 Configuring the Core Router Software Installation and Configuration Guide

6. Configuring the Core Router

Here we take AR2220 for example.

6.1 Network Architecture

In this example, the communication is made available between the network segment (20.0.2.0/24) of the
core router and the network segment (20.0.0.0/29) of the base station router via the VPN.

The topology is shown below:

202.97.1.2/30 202.96.1.2/30 Ethernet0/0
Ethernet0/1
202.96.1.1/30
20.0.2.0/24 202.97.1.1/30 Ethernet0/0
Ethernet
20.0.0.0/29
Tunnel 1 Tunnel 1
Core 20.0.1.1/29 Gre over ipsec vpn 20.0.1.2/29 BS
Router Router

6.2 Setting the Hyper Terminal

Here we take a Windows XP hyper terminal for example.

Step 1 Use the console cable to connect the serial port on the computer and the console port on the
router.

Cable

Serial Port Console Port

Step 2 Select "Start -> All Programs -> Accessories -> Communications -> Hyper Terminal", and the
"Connection Description" dialog will appear.

113
 Software Installation and Configuration Guide Configuring the Core Router

Step 3 Enter "H3C" in the "Name" field, and select an icon. Then click "OK", and the "Connect To"
dialog will appear.

Step 4 Select a serial port used for connection. Then click "OK", and the port property dialog will
appear.

114
 Configuring the Core Router Software Installation and Configuration Guide

Step 5 Configure the parameters. Then click "OK", and the "H3C-Hyper Terminal" window will appear.

Step 6 Power up the router for self-check. After the self-check is completed, press the Enter key on the
keyboard. Then the command prompt will appear.

115
Software Installation and Configuration Guide Configuring the Core Router

6.3 Making a Configuration

Note
This section only introduces the specific operations. The IP address, interface and other
information need to be configured according the actual requirements.

6.3.1 Configuring the Basic Information

<Huawei>sys

<Huawei>system-view

[Huawei]sysname XX_CR_1

[XX_CR_1]aaa

[XX_CR_1-aaa]local-user root password cipher hytera

[XX_CR_1-aaa]local-user root service-type telnet ssh terminal

[XX_CR_1-aaa]local-user root privilege level 1

[XX_CR_1-aaa]quit

[XX_CR_1]super password cipher hytera@

[XX_CR_1]user-interface vty 0 4

[XX_CR_1-ui-vty0-4]authentication-mode aaa

[XX_CR_1-ui-vty0-4]quit

[XX_CR_1]user-interface console 0

[XX_CR_1-ui-console0]authentication-mode aaa

[XX_CR_1-ui-console0]quit

[XX_CR_1]interface g0/0/0

[XX_CR_1-GigabitEthernet0/0/0]description connect to XX_CS_1

[XX_CR_1-GigabitEthernet0/0/0]ip address 20.0.29.1 30

[XX_CR_1]interface g0/0/1

[XX_CR_1-GigabitEthernet0/0/1]

[XX_CR_1-GigabitEthernet0/0/1]description connect to internet

[XX_CR_1-GigabitEthernet0/0/1]ip address 202.96.1.1 30

[XX_CR_1]interface LoopBack 0

[XX_CR_1-LoopBack0]ip address 20.0.30.248 32

6.3.2 Configuring the GRE over IPsec VPN

Configuring the GRE Tunnel
[XX_CR_1]interface Tunnel0/0/0

[XX_CR_1-Tunnel0/0/0]description connect to XX-BS-1

116
Configuring the Core Router Software Installation and Configuration Guide

[XX_CR_1-Tunnel0/0/0]tunnel-protocol gre

[XX_CR_1-Tunnel0/0/0]source 202.96.1.1

[XX_CR_1-Tunnel0/0/0]destination 202.96.1.5

[XX_CR_1-Tunnel0/0/0]gre key 888888

[XX_CR_1-Tunnel0/0/0]ip address 20.0.1.1 29

Configuring the IPsec Proposal

[XX_CR_1]ipsec proposal 1

Configuring the IKE PEER

[XX_CR_1]ike peer br v1

[XX_CR_1-ike-peer-br]local-address 202.96.1.1

[XX_CR_1-ike-peer-br]pre-shared-key simple hytera

Configuring the IPsec Policy Template

[XX_CR_1]ipsec policy-template br 1

[XX_CR_1-ipsec-policy-templet-br-1]ike-peer br

[XX_CR_1-ipsec-policy-templet-br-1]proposal 1

[XX_CR_1]ipsec policy hyt 1 isakmp template br

Applying the IPsec Policy

[XX_CR_1]int g0/0/1

[XX_CR_1-GigabitEthernet0/0/0]ipsec policy hyt

Configuring the Static Route

ip route-static 20.0.0.0 255.255.255.248 Tunnel0/0/0

ip route-static 20.0.30.1 255.255.255.255 Tunnel 0/0/0

ip route-static 20.0.30.254 255.255.255.255 20.0.29.2

ip route-static 20.0.16.0 255.255.255.0 20.0.29.2

ip route-static 20.0.28.0 255.255.255.0 20.0.29.2

ip route-static 202.96.1.0 255.255.255.0 202.96.1.2

6.3.3 Viewing the Configuration

<XX_CR_1>disp cur

117
 Software Installation and Configuration Guide Configuring the Core Switch

7. Configuring the Core Switch

Here we take S3700-52P-EI-AC for example.

7.1 Network Architecture

The topology is shown below:

E0
/0

Core Router E1
/0 /0 /41
/48 E1
Central
Control
Server

/0/47 E1
E1 /0/
1
E0/0 Core
Switch

Firewall BS

7.2 Setting the Hyper Terminal

Here we take a Windows XP hyper terminal for example.

Step 1 Use the console cable to connect the serial port on the computer and the console port on the
switch.

Cable

Serial Port Console Port

Step 2 Select "Start -> All Programs -> Accessories -> Communications -> Hyper Terminal", and the
"Connection Description" dialog will appear.

118
 Configuring the Core Switch Software Installation and Configuration Guide

Step 3 Enter "H3C" in the "Name" field, select an icon, click "OK", and the "Connect To" dialog will
appear.

Step 4 Select a serial port used for connection, click "OK", and the port property dialog will appear.

119
 Software Installation and Configuration Guide Configuring the Core Switch

Step 5 Configure the parameters, click "OK", and the "H3C-Hyper Terminal" window will appear.

Step 6 Power up the switch for self-check. After the self-check is completed, press the Enter key on the
keyboard. Then the command prompt will appear.

120
 Configuring the Core Switch Software Installation and Configuration Guide

7.3 Making a Configuration

In this example, the core switch needs to be configured with multiple VLANs. Here we take VLAN10,
VLAN4000, VLAN4070 and VLAN4080 for example.

Note
This section only introduces the specific operations. The IP address, interface and other
information need to be configured according the actual requirements.

7.3.1 Making the Basic Configuration

<Quidway>system-view

[Quidway]sysname XX_CS_1

[XX_CS_1]aaa

[XX_CS_1-aaa]local-user root password cipher hytera

[XX_CS_1-aaa]local-user root service-type telnet ssh terminal

[XX_CS_1-aaa]local-user root privilege level 1

[XX_CS_1-aaa]quit

[XX_CS_1]super password cipher hytera@

[XX_CS_1]user-interface vty 0 4

[XX_CS_1-ui-vty0-4]authentication-mode aaa

[XX_CS_1-ui-vty0-4]quit

[XX_CS_1]user-interface console 0

[XX_CS_1-ui-console0]authentication-mode aaa

[XX_CS_1-ui-console0]quit

7.3.2 Configuring the VLAN

VLAN and gateway address for BS connected directly or via the E1 link
[XX_CS_1]vlan 10

[XX_CS_1-vlan10]description connect to BS1

[XX_CS_1]interface Ethernet0/0/1

[XX_CS_1-Ethernet0/0/1]port link-type access

[XX_CS_1-Ethernet0/0/1]port default vlan 10

[XX_CS_1]interface vlanif 10

[XX_CS_1-Vlanif10]ip address 20.0.16.1 29

Configuring the VLAN for the MSO server

[XX_CS_1]vlan 4000

[XX_CS_1-vlan4000]description connect to MSO-SERVER-1

121
Software Installation and Configuration Guide Configuring the Core Switch

[XX_CS_1]interface Ethernet0/0/40

[XX_CS_1-Ethernet0/0/40]port link-type access

[XX_CS_1-Ethernet0/0/40]port default vlan 4000

[XX_CS_1]interface vlanif 4000

[XX_CS_1-Vlanif10]ip address 20.0.28.1 29

[XX_CS_1-vlan4000]description connect to MSO-SERVER-1

[XX_CS_1]interface Ethernet0/0/40

[XX_CS_1-Ethernet0/0/40]port link-type access

[XX_CS_1-Ethernet0/0/40]port default vlan 4000

[XX_CS_1]interface vlanif 4000

[XX_CS_1-Vlanif10]ip address 20.0.28.1 29

Configuring the VLAN for the firewall

[XX_CS_1]vlan 4070

[XX_CS_1-vlan4070]description connect to FW

[XX_CS_1]int Ethernet0/0/47

[XX_CS_1-Ethernet0/0/47]port link-type access

[XX_CS_1-Ethernet0/0/47]port default vlan 4070

[XX_CS_1]interface vlanif 4070

[XX_CS_1-Vlanif4070]ip address 20.0.29.5 30

Configuring the VLAN for the core router

[XX_CS_1]vlan 4080

[XX_CS_1-vlan4080]description connect to XX_CR_1

[XX_CS_1]interface Ethernet0/0/48

[XX_CS_1-Ethernet0/0/48]port link-type access

[XX_CS_1-Ethernet0/0/48]port default vlan 4080

[XX_CS_1]interface Vlanif 4080

[XX_CS_1-Vlanif4080]ip address 20.0.29.2 30

7.3.3 Configuring the Static Route

[XX_CS_1]ip route-static 0.0.0.0 0.0.0.0 20.0.29.1

7.3.4 Viewing the Configuration

[XX_CS_1]disp cur

122
is the trademark or registered trademark of Hytera Communications Corporation Limited.
2019 Hytera Communications Corporation Limited. All Rights Reserved.