01- m2000 commissioning guide

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 1 About This Manual

Chapter 1 About This Manual

1.1 Purpose of This Manual

This manual describes how to commission the M2000 system, including connecting

and commissioning devices related to the M2000 server and client. The

commissioning covers the following aspects: O&M network commissioning, NE

access, commissioning of remote alarm notification service, commissioning of the

alarm box and plate, and commissioning of the dial-up service.

For details on installing and commissioning the M2000 server and client, see the

following manuals:

iManager M2000 Mobile Element Management System Hardware Installation

Manual

iManager M2000 Mobile Element Management System Software Installation

Manual

iManager M2000 Mobile Element Management System HA System Hardware

Installation Manual

iManager M2000 Mobile Element Management System HA System Software

Installation Manual

1.2 Intended Users

This manual is intended for network management engineers. To use this manual, you

should know the basics of data communication network and mobile communications

network management.

1.3 Organization of This Manual

This manual consists of the following chapters:

Chapter 1 About This Manual introduces the purpose, intended users, and

organization of this manual.

Chapter 2 Overview of Commissioning describes the M2000 system

commissioning and the external devices involved.

Chapter 3 Commissioning of O&M Network describes how to commission the

O&M network, including how to configure each network device and port.

Chapter 4 Access of NEs to M2000 describes how to access NEs to the M2000

system and verify the access.

Chapter 5 Commissioning of Remote Alarm Notification Service describes how

to commission the remote alarm notification service.

Huawei Technologies Proprietary

1

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 1 About This Manual

Chapter 6 Commissioning of Alarm Box describes how to install and set the

alarm box, and how to verify its operation.

Chapter 7 Commissioning of Alarm Plate describes how to install and set the

alarm plate, and how to verify its operation.

Chapter 8 Commissioning of Dial-Up Connection describes how to commission

the dial-up connection and verify its operation.

1.4 References

This manual refers to the following documents:

iManager M2000 Mobile Element Management System Hardware Installation

Manual

iManager M2000 Mobile Element Management System Software Installation

Manual

iManager M2000 Mobile Element Management System HA System Hardware

Installation Manual

iManager M2000 Mobile Element Management System HA System Software

Installation Manual

iManager M2000 Mobile Element Management System Operation Manual


2

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 2 Overview of Commissioning

Chapter 2 Overview of Commissioning

2.1 About This Chapter

This manual introduces devices connected to the M2000 system and their networks,

and describes the procedure for commissioning these external devices.

2.2 Network Connection

The M2000 system consists of an M2000 server and multiple clients. Figure 1-1

shows the connection between the M2000 and the external devices.

Figure 1-1 External devices connected to the M2000

The external devices are connected to the M2000 in two ways:

Through the serial port cable. These devices include the Modem and the alarm

box. The devices, the M2000 server and clients compose the M2000 system in a

broad sense.

Through the TCP/IP-based O&M network. These devices include NEs and

network connection devices managed by network management system (NMS)

and M2000, such as the cross multiplex device, LAN switch, router and firewall.

2.3 Commissioning Procedure

The M2000 system commissioning includes the connecting and commissioning of

each related device. Table 1-1 shows the procedure in detail.


1

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 2 Overview of Commissioning

Table 1-1 M2000 system commissioning procedure

No. Step Purpose Reference

1

Commission

the O&M

network.

Construct the O&M network,

and ensure that the M2000

communicates with NE

devices and the upper NMS

through TCP/IP.

Chapter 3

Commissioning of O&M

Network

2

Cover various

NEs into the

management

of the M2000

system.

Install the mediation software

for each NE to access the

M2000 system, and set up

management objects for these

NEs to operate on and

maintain them through the

M2000.

Chapter 4 Access of NEs

to M2000

3

Commission

Modem and

the remote

alarm

notification

function.

Ensure that the alarm

information can be sent to

users in SMSs and e-mails.

Chapter 5

Commissioning of

Remote Alarm

Notification Service

4

Commission

the alarm box

or plate.

Ensure that the alarm box or

plate gives audio or visual

alarm accordingly.

Chapter 6

Commissioning of Alarm

Box

Chapter 7

Commissioning of Alarm

Plate

5

Commission

the dial-up

connection.

Ensure that the remote user

can use the PSTN network to

log in to the M2000 system

through dial-up.

Chapter 8

Commissioning of Dial-

Up Connection


2

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 3 Commissioning of O&M Network

Chapter 3 Commissioning of O&M Network


This chapter describes the O&M networking mode and the procedure to set each

networking device.

3.2 System Networking

3.2.1 Overview of Networking

The M2000 system communicates with NEs through the TCP/IP protocol. The

physical layer can use the partial or whole E1/T1, or the DDN/X.25 mode to transmit

data.

The M2000 supports two networking modes: local area network (LAN) and wide area

network (WAN). The networking plan depends on the geographical location of NEs

and user requirements. Use the LAN when all the NEs are located in the same

network segment. Otherwise, use the WAN.

3.2.2 LAN Networking

I. Networking Diagram

For the LAN networking, the M2000 can connect NEs in both star and bus networking

modes.

Use the star networking to connect all NEs in the LAN to the M2000 through a LAN

Switch or concentrator, as shown in Figure 1-2.


1


Figure 1-2 LAN star networking diagram

Figure 1-2 is a general networking diagram. It omits details about connecting some

network devices such as the router.

II. Commissioning Procedure

Table 1-1 shows the commissioning procedure for the LAN networking.

Table 1-1 Commissioning procedure for the LAN networking

No. Operation

1Use network cables to connect the M2000 server, clients and various NEs

to LAN switch A in the public network.

2Connect devices in the M2000 server system (including the disk array, local

console and SC) to LAN switch B through the private network.

3

If there is only one LAN switch, divide VLANs on the switch to distinguish

between the public and private networks. see the appropriate manual for

details on the configuration.

To set up communication channels from the M2000 to NodeB through RNC, you

should set routes to the NodeB. Set these routes in two ways:

Through the router. See 3.5 Configuring Quidway AR 28-10 Router for setting

the router.


2


Through the M2000 server. Configure the default static route or multiple routes

on the M2000 server. For details, see M2000 Administrator Guide or M2000 HA

System Administrator Guide.

III. Dial-Up Access

The M2000 also supports the dial-up access mode. To use this connection mode, a

dial-up server must be installed in the M2000 system.

The M2000 client accesses the M2000 dial-up server through the PSTN network, and

the dial-up server assigns an IP for this client. In this way, the user logs in to the

M2000 system through the M2000 client interface.

For details on the dial-up connection, see Chapter 8 "Commissioning of Dial-Up

Connection”.

3.2.3 WAN Networking

I. Networking Mode

A WAN is composed of multiple LANs. The LANs are connected with each other in

different modes. Table 1-2 lists details about the networking mode.

Table 1-2 WAN networking mode

Networking mode Description

Through partial

E1/T1

This is a common networking mode. It uses idle timeslots

in the existing E1/T1 transmission line to transmit the NMS

data. The advantage of this networking mode is that every

operator has its own E1/T1 transmission network. In this

way, it is convenient to provide transmission channels,

assign network addresses and maintain the communication

channels based on existing resources. This saves the

operator’s investment to a great extent.

Through whole

E1/T1

The whole E1/T1 networking does not require timeslot

extract and interchange. The whole E1/T1 with the 2 M

bandwidth is available for transmitting the NMS data. This

mode suits cases with redundant transmission resources

and large quantities of data.

Through DDN/X.25 This networking mode uses the conventional Digital Data

Network (DDN) or X.25 network to transmit the NMS data.

It has the advantages of reliable communications over the

private line and stable transmission quality, but has the

disadvantage of high cost.


3


II. Partial E1/T1 Networking Mode and the Commissioning Procedure

To use the partial E1/T1 networking mode, you should configure the timeslot cross

device Mercury3600, the router and the LAN switch, as shown in Figure 1-3. This

networking mode does not require the firewall. If necessary, set the firewall between

the M2000 server and NEs or clients.

Figure 1-3 Partial E1/T1 networking mode

Table 1-1 shows the commissioning procedure for the partial E1/T1 networking mode.

Table 1-1 Commissioning procedure for the partial E1/T1 networking

No. Operation Reference

1

Use network cables to connect the M2000

server, clients and various NEs to the LAN

switch in the public network. Follow Table

1-1 to connect and configure devices in the

M2000 system in the private network, such

as the disk array, local console and SC.

None

2 Configure the LAN switch.User manual of the LAN

switch

3 Configure the router at the NE side.3.5 “Configuring Quidway AR

28-10 Router”


4



4Configure the router at the M2000 server

side.

3.6 “Configuring Quidway

3640 Router”

5Configure the timeslot cross device

Mercury3600.

3.4 “Configuring Timeslot

Cross Device Mercury 3600”

6 Set the firewall if any in the network. 3.3 “Setting Firewall Port”

III. Whole E1/T1 Networking Mode and the Commissioning Procedure

To use the whole E1/T1 networking mode, you should configure the router and LAN

switch, as shown in Figure 1-4. This networking mode does not require the firewall. If

necessary, set the firewall between the M2000 server and NEs or clients.

Figure 1-4 Whole E1/T1 networking mode

Table 1-1shows the commissioning procedure for the whole E1/T1 networking mode.

Table 1-1 Commissioning procedure for the whole E1/T1 networking


1

Use network cables to connect the M2000

server, clients and various NEs to the LAN

switch in the public network. Follow Table 1-1 to

connect and configure devices in the M2000

system in the private network, such as the disk

array, local console and SC.

None


5



2 Configure the LAN switch.User manual of the LAN

switch

3 Configure the router at the NE side.

3.5 “Configuring

Quidway AR 28-10

Router”

4 Configure the router at the M2000 server side.3.6 “Configuring

Quidway 3640 Router”

5 Set the firewall if any in the network.3.3 “Setting Firewall

Port”

IV. DDN/X.25 Networking Mode and the Commissioning Procedure

The network devices and commissioning procedure for the DDN/X.25 networking

mode are the same as those for the whole E1/T1 networking mode. The only

difference lies in that the E1/T1 networking use the E1/T1 cable while the DDN/X.25

networking uses the DDN or X.25 private cable.

3.3 Setting Firewall Port

3.3.1 Introduction to Firewall

The firewall function is to filter the traffic and to protect the system from network

attack. A firewall device is required between two different security areas.

I. Filtering Traffic

The firewall filters traffic through a set of security check rules. It allows only network

data that meets set conditions to pass Thus it ensures the network security.

In the O&M network, the device type, quantity and the type of traffic between device

nodes are limited and specific. This makes it possible to set the firewall to filter invalid

traffic.

In the O&M network, the valid traffics include:

Data stream between the M2000 server and various NEs

Data stream between the M2000 server and various clients

Data stream between the M2000 server and the NMS

Data stream between LMT and devices

Data stream for updating virus codes


6


II. Protecting Against Network Attack

When configuring the firewall, ensure to enable the following functions:

Protecting against the IP fraudulence attack

Protecting against the Land attack

Protecting against the Smurf attack

Protecting against the Fraggle attack

Protecting against the WinNuke attack

Protecting against the SYN Flood attack

Protecting against the ICMP Flood attack

Protecting against the UDP Flood attack

Controlling ICMP redirection packets

Controlling ICMP destination unreachable packets

Protecting against the address scan attack

Protecting against the port scan attack

Controlling IP packets with the source site option

Controlling IP packets with the route record option

Enabling the Tracert packet control

Protecting against the Ping of Death attack

Protecting against the Teardrop attack

Checking validity of TCP packets

Checking IP fragmentation packets

Controlling oversize ICMP packets

3.3.2 Configuring Firewall

The M2000 server communicates with NEs, clients and the NMS through the

TCP/UDP protocol.

The firewall security policies work with the IP address and TCP/UDP port number to

filter the data traffic. The TCP/UDP port number ranges from 0 to 65535. The range is

divided into three segments:

Port numbers 0-1023 are for identifying some standard services, such as FTP,

Telnet, SMTP and TFTP.

Port numbers 1024-49151 are for Internet Assigned Number Authority (IANA) to

assign to registered applications.

Port numbers 49152-65535 are private and can be assigned dynamically to any

applications.

According to various networking security requirements, you can set the firewall:

Between the M2000 server and various NEs. For details on setting the firewall

port, see 3.3.3 “Setting Ports Between M2000 Server and NEs”.


7


Between the M2000 server and clients. For details on setting the firewall port,

see 3.3.4 “Setting Ports Between M2000 Server and Clients”.

Between the M2000 server and the NMS. For details on setting the firewall port,

see 3.3.5 “Setting Ports Between M2000 Server and NMS”.

3.3.3 Setting Ports Between M2000 Server and NEs

To install the firewall between the M2000 server and NEs, Open the ports at the NE

side and the M2000 server side according to the following requirements:

Open some ports at the NE side to any port at the M2000 server side, so that

any port at the server side can access ports at the NE side behind the firewall.

Open some ports at the M2000 server side to any port at the NE side, so that

any port at the NE side can access ports at the server side behind the firewall.

Table 1-2 lists the ports to open at the NE side.

Table 1-2 Port numbers used by NE services

NE type UDP port TCP port

RNC 12320, 21, 23, 6000, 6001, 6002, 6007, 6021, 6022,

6088, 6099, 6100 and 16002

CG 12320, 21, 23, 6000, 6001, 6002, 6007, 6010, 6099,

6100 and 16002

HLR 12320, 21, 23, 6000, 6001, 6002, 6005, 6006, 6007,

6008, 6009, 6099 and 16002

MGW 12320, 21, 23, 6000, 6001, 6002, 6006, 6007, 6010,

6099, 6100 and 16002

GGSN 12320, 21, 23, 6000, 6001, 6006, 6099, 6100 and

16002

SGSN 123, 161 and 16220, 21, 23, 5000, 6000, 6001, 6002, 6006, 6099,

6100, 6101 and 16002

NodeB 123 20, 21, 23, 6000, 6001, 6006 and 6007

IWF 12320, 21, 23, 7000, 7001, 7005, 7007, 7011, 7021,

7099 and 16002

MSC

Server123

20, 21, 23, 6000, 6001, 6002, 6004, 6005, 6006,

6007, 6008, 6009, 6099 and 16002

IP device 161 and 162 -


8


NE type UDP port TCP port

BSC - 8888

GT800

BSC- 8888

MSC - 8888

HLR36 - 8888

PCU/

PCU33161 8888

CHLR - 8888

iMSC - 6000, 6001 and 6002

tMSC - 6000, 6001 and 6002

CBSC - 21, 6000, 6001, 6002 and 6009

CMSC - 6000, 6001 and 6002

AAA - 1888, 6000

HA - 21, 6000, 6001, 6002, 16002

CHLR98

20123

20, 21, 23, 6000, 6001, 6002, 6005, 6006, 6007,

6008, 6009, 6099, 16002

PDSN - 21, 6000, 6001, 6002 and 16002

RAC - 21, 6000, 6001, 6002 and 6009

MSCe 12320, 21, 23, 6000, 6001, 6002, 6004, 6005, 6006,

6007, 6008, 6009, 6099 and 16002

POC - 21, 6000 and 6001

GLMS - 21, 6000 and 6001

Table 1-3 describes the use of each port.

Table 1-3 Use of ports used by NE services

Port type Port No. Use

TCP 20 and 21 For loading NE software, and uploading and

downloading software and logs


9



23 For maintaining the Telnet service

6000For the M2000 to deliver maintenance commands and

for the NE to respond

6001 For the NE to report alarm data

6002 For the NE to report performance data

6099 For the NE to report configuration data

16002For the NE to report performance data covering all

counters

8888 For communication with BAM

Other portsFor the alarm box, commissioning and binary packets,

depending on the NE type

UDP

123 For synchronizing the NTP time

161 SNMP AGENT

162 SNMP TRAP

Table 1-4 lists the ports to open at the M2000 server side and their use.

Table 1-4 Number and use of ports used by services on the M2000 server for

connecting NEs


TCP20 For FTP control

21 For FTP data

UDP 123 For synchronizing the NTP time

3.3.4 Setting Ports Between M2000 Server and Clients

To install the firewall between the M2000 server and clients, open ports according to

the following requirements:


10


Open some ports at the M2000 server side to any port at the M2000 client side,

so that any port at the client side can access ports at the server side behind the

firewall.

Open some ports at the M2000 client side to any port at the M2000 server side,

so that any port at the server side can access ports at the client side behind the

firewall.



connecting clients


TCP

20 and 21 For FTP control and data

23 For maintaining the Telnet service

6050 For Xserver

7100 For the Sun font service

7777 For the M2000 log service

8088 and 9088 For the report server

9025 For the M2000 audit service

9990 For the Kernel monitoring

9999 For the TAO CORBA name service

10119 For the diagnosis tool

19999 For the TAO notification service

51001-51016 and

51213-51219For application processes of each M2000 service

53000 For the M2000 monitoring process


Table 1-6 lists the ports to open at the M2000 client side and their use.


11


Table 1-6 Number and use of ports used by M2000 clients for connecting the M2000

server


TCP6000 For the server to connect when the client runs Winaxe

53100 For delivering CORBA events


3.3.5 Setting Ports Between M2000 Server and NMS

To install the firewall between the M2000 server and the NMS, open ports according

to the following requirements:

Open some ports at the M2000 server side to any port at the NMS side, so that any

port at the NMS side can access ports at the server side behind the firewall.



connecting the NMS


TCP

51210For connecting the CORBA interface of the NMS

for the M2000 northbound service

8765 For forwarding M2000 alarms to the NMS

4100 For the Sybase database service

UDP 8001 and 10163 For the M2000 SNMP service

3.4 Configuring Timeslot Cross Device Mercury 3600

3.4.1 Introduction to Mercury 3600

I. Overview

Mercury 3600 is a digital cross connection device (DACS) produced by TAINET.

It supports multiple interface standards and has powerful timeslot cross capability.

Mercury 3600 has five general slots for holding 4-channel E1 and 2-channel V.35

interface modules (or the DATA module). It provides up to 16 E1 channels, and

supports cross connection of any timeslot between any two ports.


12


Any port supports the performance monitoring and system maintenance with the local

or remote loop.

II. Front View

TAINETMEACURY 3600

Figure 1-5 Front view of the Mercury 3600

As shown in Figure 1-5, the Mercury 3600 has 20 LEDs, one fluorescent 16x2 liquid

crystal display (LCD), four buttons and one terminal interface on its front panel. The

LEDs on the front panel reflects the major or minor alarm and the system status,

including the number of modules, version, and the current date and time.

III. Rear View

4-E1 4-E14-E14-E1 4-E1

Figure 1-6 Rear view of the Mercury 3600

The back panel of the Mercury 3600 has five slots for holding interface modules, such

as the 4-channel E1 and 2-channel V.35 interface modules. As shown in Figure 1-6,

all the five slots of the Mercury 3600 hold 4-channel E1 interface modules. The

Mercury 3600 uses the AC power supply. It can also use the DC power supply.

Figure 1-7 shows an interface module.

Figure 1-7 Interface module plug-in

Different interface modules provide different types of interfaces. Select the type of

modules according to the actual need.


13


Insert the module in the back panel of the Mercury 3600 and fix it.

Ensure to change the module, when the power is switched off. Insert the new module

into the slot, screw the module, and then switch on the equipment.

IV. Performance

Table 1-1 Basic performance of the Mercury 3600

Item Description

Features

Provide five slots and support up to 16 E1s.

Support five access modes: E1, T1, V.35, IDSL and IP.

Can be used as CSU/DSU, E1-T1 converter, multi-channel

CSU or DACS.

Can provide 512x512 timeslots for interchange.

Can use the terminal settings.

Can use AC or DC power supply.

Network interface

(E1)

Line rate: 2.048 Mbit/s 50 ppm

Line code: AMI/HDB3

Input signal: up to ITU-T G.703

Jitter tolerance: up to ITU-T G.823

User equipment

interface (V.35/RS-

530/X.21/RS-449)

Data rate: Nx64 kbit/s (N = 1-31)

Clock control

Support the E1/T1 port as the master clock source.

Support the E1/T1 port as the slave clock source.

Provide an internal clock.

Provide the clock holdover mode.

Support automatic clock mode selection.

Power supply

AC or DC power supply

DC: from -36 V to -72 V

AC: 90 VAC to 240 VAC and 50/60 Hz


14


Item Description

Physical

characteristics

Dimension: 43 cm W x 33 cm H x 4.4 cm D [16.93 in. W x

12.99 in. H x 1.73 in. D]

Temperature: 0C [32F] to 50C [122F]

Humidity: 0-95% (congelation)

Installation: on the 19’’ rack (for the desktop)

Weight: 3 Kg [6.615 lb]

V. Interface Cable Numbering

The five interface slots on the back panel of the Mercury 3600 are numbered from 1

to 5 from right to left. Each interface module plug-in card corresponds to several

interfaces, A, B, C and D respectively.

Table 1-2 lists the interface module and cable marks for the BNC interface of the 4-

channel E1.

Table 1-2 Marks of interface cables for the 4-channel E1 interface module on the

Mercury 3600

Interface TX RX

A Red Orange

B Green Yellow

C Blue Purple

D Black Grey

Note:

Table 1-2 does not apply to the case when the interface cables connecting the 4-

channel E1 interface modules are marked by TX and RX.

For example:

If you insert a 4-channel E1 interface module in slot 1, 4 channels of E1 links can

be accessed, with the interfaces numbered as 1A, 1B, 1C and 1D.

If you insert a 2-channel V.35 interface module in slot 2, 2 channels of V.35 links

can be accessed, with the interfaces numbered as 2A and 2B.


15


Caution:

Slot 5 shares the same interface resources as slot 4. Set the interfaces to 4A or 4B.

Slot 5 is not used if idle interfaces exist.

VI. Introduction to RJ48

If the impedance of the E1 transmission equipment for the network connection is 120

ohm, use the interface module and cables matching this impedance on the Mercury

3600, and use the balanced cable (4-core twisted pair) as the transmission cable. In

this case, the interface uses the RJ48 interface standard. Table 1-3 defines the

interface.

Table 1-3 RJ48 interface cable sequence

Pin Description

1 Receiver -

2 Receiver +

3 -

4 Transmit -

5 Transmit +

6 -

7 -

8 -

This interface can also use the RJ45 connecter. The cable sequence is the same as

that described in Table 1-3.

3.4.2 Mercury 3600 LEDs and Common Commissioning Commands

I. LEDs on Front Panel

After you switch on the Mercury 3600, the indicators on the front panel that

correspond to the port with a plug-in turn on. In addition, there are also three general

indicators on the front panel.


16


Table 1-4 describes the meaning of each indicator.

Table 1-4 Description of indicators on the front panel of the Mercury 3600

Indicator Meaning

Indicators corresponding to

the port with a plug-in

Red Indicates that the link is faulty.

Yellow Indicates that one end is faulty.

Green Indicates that the link is normal.

Three general indicators RedIndicates that faulty links exist in the

network system.

YellowIndicates that one end of the network

system is faulty.

GreenIndicates that all physical links in the

network system are normal.

II. Common Commands for Commissioning Mercury 3600

Table 1-5 lists the common commands for commissioning Mercury3600.

Table 1-5 Common commands for commissioning the Mercury 3600

Command Use

ALM To view alarm information.

BOOT To reset the equipment.

CLK PortID

To define the port to extract the clock. You can only

extract the clock from ports A and C. When PortID is

INT, it means to extract the internal clock.

STAT PortID To view the port state.

XC Port1ID Port2ID To interchange all timeslots at ports 1 and 2.

XV Port1 TSa Port2 TSb

Count

To interchange Count timeslots, with TSa at port 1

and TSb at port 2 as the start timeslots.

V35 PortID Count1

Count2

To define that Count2 timeslots from timeslot Count1

at this port are for the V.35 interface module.

LINK PortID RCRC:X

TCRC:X

To define that links at port PortID go through CRC at

data receiving and transmitting. X = 0 means no


17


Command Use

CRC, and X = 1 means to adopt the CRC.

LOGL To view Profile.

LOGB To define the start of a Profile.

LOGE N Filename To define the end of a Profile.

LOGI N RebootTo define that the system invokes automatically No.

N Profile on reboot.

LOGR N To invoke No. N Profile manually.

LOGV N To view No. N Profile.

CLS To clear the screen.

DATE TIME To set the date and time.

3.4.3 Before Configuration

This section uses an instance to introduce the scheme planning and commissioning

procedure.

I. Planning Scheme

Figure 1-8 shows the timeslot cross scheme for the Mercury 3600.

Figure 1-8 Mercury 3600 timeslot cross scheme

Use idle timeslots in the E1 line from the switch to transmit NMS information.

Connect the E1 line with idle timeslots to port 1A on the E1 interface module on

the Mercury 3600.


18


Connect the cable from the router to port 2A on the V.35 interface module.

Interchange all timeslots at ports 1A and 2A to port 1B. In this way, port 1B

integrates all information on ports 1A and 2A.

Connect port 1B to the remote E1 network.

II. Installing and Connecting Hardware

Install the Mercury 3600 according to Mercury 3600 Installation Manual.

Figure 1-9 shows how to connect Mercury3600 with peripheral devices.

Figure 1-9 Mercury 3600 engineering connecting diagram

The connection is described as follows:

Insert a 4-channel E1 interface module in slot 1 on the back panel of the Mercury

3600. The switch extends a pair of E1 cables with idle timeslots to connect a pair

of terminals on the DDF rack in the transmission equipment room. This pair of E1

cables then jumps to port 1A on the E1 interface module. In this way, the

Mercury 3600 is connected to the switch through port 1A and the corresponding

E1 port on the switch. Connect port 1B on this E1 interface module to the

transmission equipment, and then connect it to the remote end in the WAN (the

E1 network).

Interchange all timeslots at port 1A to port 1B.

Insert a 2-channel V.35 interface module in slot 2 on the back panel of Mercury

3600. Connect port 2A on this module to port S (the WAN network port) on the

router. The Mercury 3600 defines some timeslots at port 2A as channels for

transmitting NMS messages, and interchanges these timeslots to port 1B to


19


extend them to the remote end. In this way, port 1B integrates information on

both ports 1A and 2A.

At the other end of the network, the Mercury 3600 extracts the timeslots for

transmitting NMS messages in the same way, and communicates with the

corresponding LAN through the router.

3.4.4 Procedure

According to 3.4.3 I. Planning Scheme, configure the Mercury 3600 as follows:

I. Configuring HyperTerminal

2) A serial port cable with 9-pin connectors at both ends is delivered with the

Mercury 3600. Use the cable to connect the terminal port on the front panel of

the Mercury 3600 and the serial port on the PC.

3) Run the HyperTerminal program, and set up a connection. Use the serial port

connection, and set the communications parameters as: 19200 bit/s, eight data

bits, no check bit, one stop bit, flow control as Xon/Xoff.

4) Switch on the Mercury 3600, and HyperTerminal displays information about

Mercury 3600. Now the Mercury 3600 enters the inquiry state.

Note:

You can use any type of emulation terminal programs, such as the HyperTerminal of

Windows 2000.

II. Logging in to Mercury 3600

To modify the parameters of the Mercury 3600, execute the following command to log

in to the Mercury 3600:

Mercury>Login _parameter 1 _parameter 2

Parameter 1: username, with the default setting as TAINET.

Parameter 2: password, with the default setting as 3600.

Execute HELP commands to query the method and syntax for using each specific

command.

III. Configuring Mercury 3600 at One Side

5) Define the start of a new Profile.

MERCURY> LOGB

6) Extract the clock from port 1A.


20


MERCURY> CLK 1A //Ensure to extract the clock on the two Mercury 3600s in the

same way.

7) Define that the links at port 1A do not go through CRC.

MERCURY> LINK 1A RCRC:0 TCRC:0

8) Define that the links at port 1B do not go through CRC.

MERCURY> LINK 1B RCRC:0 TCRC:0

9) Interchange all timeslots at port 1A to port 1B.

MERCURY> XC 1A 1B

10) Define timeslots.

MERCURY> DATA 2A 4 TYPE:4 //For the 2P-DATA module, define that port 2A is

a V.35 interface and the bandwidth is 4 timeslots.

Or

MERCURY> V35 2A 1 2 //For the 2P-V35, define that the two timeslots from

the first timeslot at port 2A form the bandwidth, and that port 2A is a V.35 interface

and is connected to the WAN network port on the router.

11) Interchange timeslots.

MERCURY> XT 2A 0 1B 1 2 //For the 2P-DATA module, interchange timeslot 0 on

port 2A and timeslot 1 on port 1B. Altogether interchange two timeslots.

Or

MERCURY> XT 2A 1 1B 1 2 //For the 2P-V35 module, interchange timeslot 1

on port 2A and timeslot 1 on port 1B. Altogether two timeslots are interchanged and

transmitted to the remote end through port 1B as channels for NMS messages.

12) Save all the above commands into the first Profile.

MERCURY> LOGE 1 HEXI1 //HEXI1 is the file name. It is definable.

MERCURY> LOGI 1 //The system invokes the first Profile automatically on

boot.

13) Exit HyperTerminal, and reset the Mercury 3600.

The configuration of the Mercury 3600 at one side of the network is complete.

IV. Configuring Mercury 3600 at the Other Side

Configure the Mercury 3600 at the other side of the network in the same way. Note to

use the actual port number and timeslots to interchange. The procedure is as follows:

14) Define the start of Profile.

MERCURY>LOGB

15) Extract the clock from port 1A.


21


MERCURY>CLK 1A //Extract the clock from the peer-end Mercury 3600 as the

master clock, so that the two Mercury 3600s use the same clock.

16) Define that the links at port 1B do not go through CRC.

MERCURY> LINK 1B RCRC:0 TCRC:0

17) Define that the links at port 1A do not go through CRC.

MERCURY> LINK 1A RCRC:0 TCRC:0

18) Exchange all timeslots on port 1B to port 1A.

MERCURY> XC 1B 1A

19) Define that one timeslot from timeslot 1 on port 2A uses the V.35 interface

standard and is connected to the WAN port on the router.

MERCURY> V35 2A 1 2

20) Interchange two timeslots from timeslot 1 at ports 2A and 1A as channels for

NMS messages.

MERCURY> XT 2A 1 1A 1 2

21) Save all the above commands into the first Profile.

MERCURY> LOGE 1 WGZX //The file name is WGZX.

MERCURY> LOGI 1 //The system invokes the first Profile automatically on

boot.

22) Exit HyperTerminal, and reset the Mercury 3600.

Now, the two Mercury 3600s at both sides of the network are configured ready. When

the physical links work properly, the indicator on the front panel of the Mercury 3600

for the connected port turns green.

3.5 Configuring Quidway AR 28-10 Router

3.5.1 Introduction to Quidway AR 28-10

I. Overview

Quidway AR 28-10 works as the router for NE devices in the M2000 remote

networking.

Note:

The content described in this section applies only to the common networking. For

more information, see related technical documents about Quidway AR 28-10.


22


II. Back Panel

Figure 1-1 shows the back panel of Quidway AR 28-10.

1) Power switch 2) Power socket

3) Grounding screw 4) Fixed interface (WAN)

5) Console port (CON) 6) Auxiliary port (AUX)

7) Fixed Ethernet interface

(LAN0)8) MIM slot 0

9) SIC slot 1 10) SIC slot 2

Figure 1-1 Back panel of Quidway AR 28-10

III. Components and Performance

Table 1-1 lists components and main indices of the Quidway AR 28-10 router.

Table 1-1 Components and main indices of the Quidway AR 28-10 router.

Item Description

Slot2 SIC slots (Up to 2 SICs can be configured as needed.)

1 MIM slot (Up to 1 MIM can be configured as needed.)

Fixed interface

1 10/100Mbps Ethernet interface

1 WAN interface

1 AUX port

1 console port

CPU MPC8241

Boot ROM 512 KB

SDRAM 64 MB (can be extended to 128MB)

Flash memory 8MB


23


Item Description

Dimensions (W x H

x D)442mm x 44.4mm x 300mm (including the rubber feet)

Weight 6kg

Input voltage

Rated voltage range: 100-240V a.c.; 50/60Hz

Maximum voltage range: 90-264V a.c.; 50/60Hz

Rated voltage range: -48- -60V d.c.

Maximum voltage range: -36- -72V d.c.

3.3V d.c., 5V d.c., 12V d.c.

Maximum Power 60W

Operating

temperature0 to 40oC

Operating relative

humidity10%-90% (non-condensing)

Note:

Router program operates in SDRAM (Synchronous Dynamic Random Access

Memory).

Flash memory is used to save router program files, configuration files and so on.

Boot ROM is used to save boot and initialization programs of the router.

IV. Fixed Interfaces

Quidway AR 28-10 Router provides 1 fixed console port, 1 AUX port, Ethernet

interface(s), and 1 synchronous/asynchronous interface. Their attributes are

introduced below.

23) Console port (CON)

Table 1-1 Attributes of the console port

Attribute Description

Connector RJ45

Interface RS232


24



standard

Baud rate 9600bps to 115200 bps

9600bps by default

Services

supported

Connecting with character terminal

Connecting with the serial interface of the local PC and operating the

terminal emulator on the PC

Command line interface

24) AUX port (AUX)

Table 1-1 Attributes of the AUX port


Connector RJ45

Interface

standardRS232

Baud rate 300 to 115.2kbps

Services

supported

Modem dial-up

Backup

Operating as the console port when the CON fails

Protocols

supported

PPP

SLIP

MP

25) Fixed Ethernet interface (LAN)

Table 1-1 Attributes of the Ethernet interface


Connector RJ45

Interface MDI

Frame format

supported

Ethernet_II


25



Ethernet_SNAP

IEEE 802.2

IEEE 802.3

Operating

mode

10/100Mbps autosensing

Full duplex/half duplex

Network

protocol

supported

IP

Novell IPX

Note:

Ethernet MDI (Media Dependent Interface) is the typical Ethernet interface on

ordinary network cards. MDIX is crossover media-dependent interface, which is

generally used on Hubs or LAN switches.

26) Fixed Wide Area Network interface (WAN)

Table 1-1 Attributes of the WAN interface

AttributeDescription

Synchronous Asynchronous

Connector DB50

Interface

standard

and

operating

mode

V.24

(RS232)V.35

V.24 (RS232)

DTE, DCE DTE DCE

Minimum

baud rate

(bps)

1200 1200 1200 300

Maximum

baud rate

(bps)

64k 4.096M 2.048M 115.2k


26


AttributeDescription

Synchronous Asynchronous

Services

supported

DDN leased line

Backup

Terminal access

Modem dial-up

Asynchronous leased

line

Terminal access

Backup

Protocols

supported

PPP

MP

LAPB

HDLC

SDLC

X.25 (ITU-T X series recommendations )

Frame Relay

PPP

SLIP

MP

3.5.2 QuidwayAR 28-10 Command View

The command line of the Quidway AR 28-10 router adopts the hierarchical protection

to avoid intrusion of unauthorized users.

Different commands should be executed on the corresponding command views. Table

1-2 lists functional features of the common command views and commands for

entering each view.

Table 1-2 Common command views of Quidway AR 28-10

Command

view

Function Prompter Entry

command

Exit command

User view Display basic

information

about

operation and

statistics

<Quidway> Enter right

after

connecting to

the router

quit

disconnects from

the router

System

view

Configure

system

parameters

[Quidway] Key in

system-view

in user view

quit

returns to user

view


27


Command

view

Function Prompter Entry

command

Exit command

User

interface

view

Manage the

asynchronous

and logical

interfaces on

the router

[Quidway-

ui0]

Key in user-

interface 0 in

system view

quit

returns to system

view

Synchronou

s/

asynchrono

us serial

interface

view

Configure

synchronous/a

synchronous

serial interface

parameters

[Quidway-

Serial0/0]

Key in

Interface

serial 0/0 in

system view

quit

returns to system

view

Asynchrono

us serial

interface

view

Configure

asynchronous

serial interface

parameters

[Quidway-

async 0/0]

Key in

Interface

async 0/0 in

system view

quit

returns to system

view

Ethernet

interface

view

Configure

Ethernet

interface

parameters

[Quidway-

Ethernet0/0]

Key in

Interface

ethernet 0/0

in system view

quit

returns to system

view

AUX

interface

view

Configure

AUX interface

parameters

[Quidway-

aux0]

Key in

interface aux

0 in system

view

quit

returns to system

view


I. Overview of Scheme Planning

Before configuring the router, plan the following information according to the actual

networking:

IP address and subnet mask of port Ethernet0/0 in the local Ethernet network

IP address and subnet mask of port Serial0/0 in the WAN

Destination network segment, subnet mask and next hop IP address for the

wide-used static route

Encapsulated protocols for the WAN

Clock at the WAN port


28


II. Routes

The route table contains two types of routes:

Static routes. You can set the route in the route table manually. Static routes are

commonly used in networking to realize access to the remote network.

Dynamic routes. Dynamic routes in the route table are addressed by the bound

dynamic routing protocols, such as OSPF, RIP, IGRP and BGP. With these

protocols, the router can discover the corresponding routes dynamically in the

network. The route priority varies according to the corresponding protocol.

III. Encapsulated Protocols for WAN

For smooth communications, communications protocols encapsulated on the WAN

port on the local router must conform to those for the WAN port on the peer-end

router.

The common communications protocols are as follows:

HDLC

PPP

X.25

SLIP

Frame Relay

LAPB

IV. Clock at the WAN Port

When using the partial E1/T1 networking mode, the WAN port on the Quidway AR 28-

10 router works as a synchronous serial port. The synchronous serial port can work

as a DTE and DCE. Therefore, you should select the clock accordingly.

If as a DCE, it needs to provide clock for the peer-end DET. In this case, select

DCEclk.

If as a DTE, it receives clock from the peer-end DCE. For the synchronous

equipment, the receiving and transmitting clocks are mutually independent.

Therefore, you can select the receiving or transmitting clock of the DCE as the

receiving clock of the DTE. It is the same case with the DTE transmitting clock.

In this way, four combinations are available. That is, the clock at the DTE side

has four choices, as shown in Table 1-3.

Table 1-3 Clock selection for the synchronous serial port at the DTE side

Selection Meaning

DTEclk1 TxClk = TxClk, RxClk = RxClk

DTEclk2 TxClk = TxClk, RxClk = TxClk


29


Selection Meaning

DTEclk3 TxClk = RxClk, RxClk = TxClk

DTEclk4 TxClk = RxClk, RxClk = RxClk

In this table, TxClk is the transmitting clock and RxClk the receiving clock. The clock

in front of “=” is the DTE-side clock, while that behind “=” is the DCE-side clock.

In the partial E1/T1 networking, the router is a DTE, and the Mercury 3600 is a DCE.

Therefore, the Mercury 3600 provides the clock for the router.

V. Instance


procedure.

Plan the IP address of port Ethernet0/0 in the local Ethernet network as

129.9.0.1 and the subnet mask as 255.255.0.0.

Plan the IP address of port Serial0/0 in the WAN as 129.8.0.1 and the subnet

mask as 255.255.0.0.

Plan the destination network segment of the static route as 129.10.0.0, subnet

mask as 255.255.0.0 and next hop IP address as 129.8.0.2.

Plan the encapsulated protocol for the WAN as PPP.

Plan the clock at the WAN port as DTEclk2.

VI. Installing and Connecting Hardware

Install the router according to Quidway AR 28-10/28-11 Routers Installation Manual.

Figure 1-2 shows how to connect Quidway AR 28-10 with peripheral devices.

Figure 1-2 Connecting Quidway AR 28-10

3.5.4 Procedure

According to the planning in 3.5.3 V. Instance, configure Quidway AR 28-10 as

follows:


30


I. Configuring HyperTerminal

27) Use the configuration cable delivered with Quidway AR 28-10 to connect console

port (CON) on it and the serial port on the PC.


connection, and set the baud rate to 9600, data bit to 8, no parity check, stop bit

to 1, flow control to none.

29) Switch on Quidway AR 28-10, and HyperTerminal displays the self-check

information about Quidway AR 28-10. When the self-check is complete, the

system prompts you to press Enter.

30) Press Enter, and the system enters the <Quidway> state.

II. Configuring Router

This section describes how to use the command line to configure the router.

The detailed procedure for configuring Quidway AR 28-10 is as follows:

31) Log in the router.

Switch on the router, and the system carries out the self-check. When the self-check

is complete, the system enters the user view, namely, the <Quidway> state.

32) Enters the system view

<Quidway> system-view

33) Execute the following command to check the router configuration data:

[Quidway] display current-configuration

The system displays the router configuration.

34) Set the system name as the prompter.

[Quidway] sysname ×××

35) Set the IP address and subnet mask for the Ethernet port.

If the set IP address and mask do not meet the actual requirements, execute the

corresponding commands to modify them. For example, to modify the IP of

Ethernet0/0, execute the following commands:

[Quidway] interface ethernet 0/0 //Enter the environment for setting port

Ethernet0/0.

[Quidway-Ethernet0/0] undo ip address xxx.xxx.xxx.xxx 255.xxx.xxx.xxx //Delete

the IP address previously configured for this port.

[Quidway-Ethernet0/0] ip address 129.9.0.1 255.255.0.0 //Reset the IP address

and mask for this port.

[Quidway-Ethernet0/0] quit //Go back to the prompter [Quidway].

36) Set the static route.


31


If the set static route does not meet the actual requirements, execute the following

corresponding commands to modify it:

[Quidway] undo ip route-static ip-address (destination IP) mask (subnet mask) ip-

address (next hop IP) //Delete the previously set static route.

[Quidway] ip route-static 129.10.0.0 255.255.0.0 129.8.0.2 //Reset the static

route.

37) Set the IP address and subnet mask for the WAN port.

[Quidway] interface serial 0/0 //WAN port. Define serial 0/0 according to the

actual connection.

[Quidway-Serial0/0] undo ip address xxx.xxx.xxx.xxx 255.xxx.xxx.xxx //Delete

the IP address previously configured for this port.

[Quidway-Serial0/0] ip address 129.8.0.1 255.255.0.0 //Reset the IP address and

mask for this port.

[Quidway-Serial0/0] quit //Go back to the prompter [Quidway].

38) Encapsulate protocols for the WAN port.

The WAN port on the Quidway AR 28-10 router is encapsulated with the PPP protocol

by default. To modify the encapsulated communications protocol, execute the

following commands:

[Quidway] interface serial 0/0 //Enter the configuration mode for the WAN port

Serial0/0.

[Quidway-Serial0/0] link-protocol ppp //Encapsulate PPP.

[Quidway-Serial0/0] quit //Go back to the prompter [Quidway].

39) Set the clock for the WAN port.

The Quidway AR 28-10 router works by default as a DTE in the network. It uses the

clock in the DTEclk1 mode. To modify the clock mode, execute the following

command:

[Quidway] clock DTEclk2 //Set the clock mode to DTEclk2.

40) Save the configured data into Flash Memory.

[Quidway] save

41) Reboot the router.

[Quidway] reboot

This command will reboot the system. The current configuration has not

been saved and will be lost if you continue. Continue? [Y/N]

The interface definition and static route configuration are complete. When the router

is restarted, enter the user view, and check and modify the configured data.


32


III. Checking Configuration and Debugging Systemand debugging

When the router configuration at both sides of the network is complete, carry out the

system debugging as follows:

42) Display the status of Serial0/0.

When the router configuration is complete at both sides of the network, execute the

following command on any router to display the Serial0/0 status:

[Quidway] display interface serial 0/0

Serial0/0 is up, line protocol is up

physical layer is synchronous

interface is DTE, clock is DTECLK1, cable type is V35

Encapsulation is PPP

LCP opened, IPCP opened, IPXCP initial

5 minutes input rate 0.00 bytes/sec, 0.00 packets/sec

5 minutes output rate 1.19 bytes/sec, 0.06 packets/sec

Input queue is 0/75/0 (current/max/drops)

Queueing strategy: FIFO

Output Queue :(size/max/drops)0/75/0

6 packets input, 88 bytes, 0 no buffers

27 packets output, 466 bytes, 0 no buffers

0 input errors, 0 CRC, 0 frame errors

0 overrunners, 0 aborted sequences, 0 input no buffers

DCD=UP DTR=UP DSR=UP RTS=UP CTS=UP

If the above information contains the following, it shows that the whole link layer is

configured:

Serial0/0 is up, line protocol is up.. LCP opened, IPCP opened DCD=UP

DTR=UP DSR=UP RTS=UP CTS=UP

43) Check the remote network.

Execute ping to check whether the remote network is connected.

[Quidway] ping xxx.xxx.xxx.xxx (IP of E0 on the peer-end router)

If the system displays the following information, it shows that the WAN port is not

activated:

Serial0/0 is down

In this case, execute the following commands to activate the WAN port:

[Quidway] interface serial 0/0

[Quidway-Serial0/0] undo shutdown

If still failed, check the cable connection to ensure that all the cables are connected

correctly and tightly.


33


If the system displays:

Serial0/0 is up, line protocol is down......

If you fail to ping the local Serial0/0 and the WAN port and E0 corresponding to the

peer-end router, it shows that the connection is not working. In this case, ensure that

all the cables are connected correctly and tightly.

You can use the self-loop to check if the communications problem is caused by faulty

links. Check further the router configuration, including the IP address, mask, static

route, protocol encapsulated on the WAN port, the corresponding timeslot, and the

extracted clock. Locate the problem, and ensure that you can ping the peer-end LAN

successfully.

3.6 Configuring Quidway 3640 Router

3.6.1 Introduction to Quidway 3640

I. Overview

Quidway 3640 is a modularized router of Huawei R2600/3600 series. It works as the

network-side router in the M2000 remote network.

Note:

The content described in this section applies only to the common networking. For

more information, see the related technical documents about Quidway 3640.

II. Rear View

Figure 1-1shows the rear view of Quidway 3640.

Figure 1-1 Rear view of Quidway 3640

III. Interfaces

Quidway 3640 provides up to four slots for network interfaces. You can configure up

to four interface modules according to the actual need.

This section describes the Ethernet module and WAN module used in the M2000

system network.

There are two types of Ethernet modules:

1-port 10Base-T/100Base-TX Fast Ethernet interface module (1FE)


34


2-port 10Base-T/100Base-TX Fast Ethernet interface module (2FE)

The 1FE module provides one 10/100 Mbps Ethernet RJ-45 interface, while the 2FE

module provides two.

Ethernet ports on Quidway 3640 are numbered from Ethernet 0. For example, if you

insert the 1FE module in slot 1 and the 2FE module in slot 2, the Ethernet port for slot

1 is numbered Ethernet 0, and those for slot 2 are numbered Ethernet 1 and Ethernet

2.

There are four types of WAN modules:

1-port channelized cE1/PRI module (1E1)



2SA/4SA fast synchronous/asynchronous serial port module

Each cE1 interface is a Controller E1. The Controller E1 ports are numbered as

follows:

The first Controller E1 port is numbered Controller E1 0.

From slot 0, the Controller E1 ports are numbered increasingly by degrees. The

first Controller E1 port on the module in the following slot is numbered as the

number of the last Controller E1 port on the module in the current slot plus one.

On the same interface module, the Controller E1 ports are numbered the same

as the numbers marked on the module panel.

For example, if you insert a 4E1 module in slot 1 and a 2E1 module in slot 3 on

Quidway 3640, the four cE1/PRI ports on the module in slot 1 are numbered from

Controller E1 0 to Controller E1 3, and the two on the module in slot 3 are numbered

Controller E1 4 and Controller E1 5.

3.6.2 Quidway 3640 Command View

The command line of the Quidway routers adopts the hierarchical protection to avoid

intrusion of unauthorized users.

Different commands need to be executed on the corresponding command views.

Table 1-1 lists functional features of the common command views and the commands

for entering each view.

Table 1-1 Command views of Quidway 3640

Name Function Prompter Entry

command

Exit

command

System view For setting

system

parameters

[Router] Enter this view

by logging on

the router.

Exit this

view by

logging off


35



command

Exit

command

the router.

View for the

synchronou

s serial port

For setting

parameters

for the

synchronous

serial port

[Router-Serial0] Type “interface

serial 0” on

any view to

enter this view.

Type “quit”

to go back

to the

system

view.

View for the

asynchrono

us serial

port

For setting

parameters

for the

asynchronou

s serial port

[Router-Async0] Type “interface

async 0” on

any view to

enter this view.

Type “quit”

to go back

to the

system

view.

View for port

AUX

For setting

parameters

for port AUX

[Router-Aux0] Type “interface

aux 0” on any

view to enter

this view.

Type “quit”

to go back

to the

system

view.

View for port

AM

For setting

parameters

for port AM

[Router-AM0] Type “interface

am 0” on any

view to enter

this view.

Type “quit”

to go back

to the

system

view.

View for port

Ethernet

For setting

parameters

for port

Ethernet

[Router-Ethernet0] Type “interface

ethernet 0” on

any view to

enter this view.

Type “quit”

to go back

to the

system

view.

View for port

CE1

For setting

the timeslot

binding

mode and

physical

layer

parameters

for port CE1

[Router-E1-0] Type

“controller e1

0” on any view

to enter this

view.

Type “quit”

to go back

to the

system

view.

View for port For setting [Router-T1-0] Type Type “quit”


36



command

Exit

command

CT1 the timeslot

binding

mode and

physical

layer

parameters

for port CT1

“controller t1

0” on any view

to enter this

view.

to go back

to the

system

view.


I. Overview of Scheme Planning

Before configuring the router, plan the following information according to the actual

networking:

IP address and subnet mask of port E0 in the local Ethernet network

IP address and subnet mask of port S0 in the WAN

Destination network segment, subnet mask and next hop IP address for the

wide-used static route

Type of the WAN port, and the communications protocol to bind to interfaces,

such as X.25, Frame Relay and HDLC

Network protocol to use, such as AppleTalk, IP and IPX (usually IP selected)

II. WAN Port Working Mode

The WAN cE1/PRI port works in two modes: E1 and cE1/PRI.

When working in the E1 mode, it is an interface with a bandwidth as 2 Mbit/s and

with no timeslot division. It has the same logical characteristics as the

synchronous serial port. It supports link layer protocols such as PPP, Frame

Relay, LAPB and X.25, and supports network protocols such as IP and IPX.

When working in the cE1/PRI mode, it is divided into 32 timeslots physically.

These timeslots are numbered from 0 to 31. When working as a cE1 interface, it

divides randomly all timeslots except timeslot 0 into several groups. The

timeslots in each group are bound and work as a channel-group interface. This

bound interface supports link layer protocols such as PPP, Frame Relay, LAPB

and X.25, and supports network protocols such as IP and IPX.


37


Note:

In the partial E1/T1 networking, Quidway 3640 works as the router in the Network

Management Center (NMC). It communicates directly with various NE-side routers

through port E1. The communication process is as this: the Mercury 3600, a timeslot

cross equipment, aggregates NMS information of various managed NEs to one E1

port, and then transmits the aggregated information to port E1 on the router.

Therefore, it is important to configure port E1 on Quidway 3640.

III. Instance


procedure.

Plan the IP address of the Ethernet port in the local Ethernet network as

10.11.100.1 and the subnet mask as 255.255.255.0.

Plan the IP address of the WAN port as 133.133.133.1 and the subnet mask as

255.255.255.252.

Plan the destination network segment of the static route as 10.11.1.0, subnet

mask as 255.255.255.0 and next hop IP address as 133.133.133.2.

IV. Installing and Connecting Hardware

Install the router according to Quidway 3640 Installation Manual.

Figure 1-2shows how to connect Quidway 3640 with peripheral devices.

Figure 1-2 Connecting Quidway 3640

3.6.4 Procedure

According to the planning in 3.6.3 III. Instance, configure Quidway 3640 as follows:

I. Configuring HyperTerminaling

44) Use the configuration cable delivered with Quidway 3640 to connect port

CONSOLE on it and the serial port on the PC.


38



connection, and set the communications parameters as: 9600 bit/s, no parity

check, one stop bit, flow control as Xon/Xoff.

46) Switch on Quidway 3640, and HyperTerminal displays the self-check information

about Quidway 3640. When the self-check is complete, the system prompts you

to press Enter.

47) Press Enter, and the system enters the Router state.

II. Configuring Routering

You can configure the Quidway 3640 series routers in two ways:

The setup mode

The command line mode

This section describes how to use the command line to configure the router.

Note:

The system prompts to configure the router in the setup mode on the first boot. You

can also execute the command setup to enter the setup mode, as follows:

[Quidway] setup

The detailed procedure for configuring Quidway 3640 is as follows:

48) Log in to the router.

Switch on the router, and the system carries out the self-check. When the self-check

is complete, the system enters the system view, namely, the Router state.

49) Set the system name as the prompter.

[Quidway] sysname ×××

50) Set the IP address and subnet mask for the Ethernet port.

[Router] interface ethernet 0 //Enter the mode for configuring the specified

Ethernet port E0.

[Router-Ethernet0] ip address 10.11.100.1 255.255.255.0 //Reset the IP address

and mask for E0.

51) Set the WAN port cE1/PRI.

[Router] controller e1 0 //Set the E1 port with the number as 0.

[Router-E1-0] code ami | hdb3 //Set the line code format to AMI or HDB3. The

system default setting is HDB3.

[Router-E1-0] using e1|ce1 //The cE1/PRI port works in the E1 or cE1/PRI mode.

The system default setting is the cE1 mode.


39


[Router-E1-0] frame-format crc4 //Set the frame check mode of the cE1/PRI port

to the 4-byte CRC. You can also set not to use the CRC.

Note:

Set whether to use the CRC according to the specific network communications

requirements. If the Mercury 3600 that communicates with the router uses the CRC,

set the CRC for the router; otherwise, do not.

[Router-E1-0] channel-set 1 timeslot-list 1-4 //Define that channel set 1 binds

timeslots 1, 2, 3 and 4.

Note:

Timeslot 0 is usually not involved in the channel definition. It is used for synchronizing

the clock during the line communications. Therefore, the timeslot binding starts from

timeslot 1.

52) Set the virtual serial port.

[Router-E1-0] interface serial 0:1

[Router-Serial0:1] ip address 133.133.133.1 255.255.255.252

[Router-Serial0:1] link-protocol ppp

[Router-Serial0:1] quit

53) Set the static route.

If the set static route does not meet the actual requirements, execute the following

corresponding commands to modify it:

[Router] ip route-static 10.11.1.0 255.255.255.0 133.133.133.2 //Reset the static

route.

54) Save the setting and check the configuration.

Press Ctrl+Z to go back to the prompter Router.

[Router] save //Save the configuration into the flash memory.

[Router] display cur //Display the configuration.

III. Checking Configuration and Debugging Systemand debugging

When the router configuration at both sides of the network is complete, carry out the

system debugging as follows:


40


55) Display the status of the WAN port serial 0.

When the router configuration is complete at both sides of the network, execute the

following command on any router to display the S0 status:

[Router] display interface serial 0

The displayed port information includes:

Physical status of the port and protocol status

Physical characteristics of the port, such as synchronous/asynchronous,

DTE/DCE, selected clock, baud rate and external cables

IP address of the port

Link layer protocols encapsulated on the port and their running status and

statistics

Input/output message statistics.

56) Check the remote network.

Execute ping to check whether the remote network is connected.

[Router] ping xxx.xxx.xxx.xxx (IP of Ethernet0/0 on the peer-end router)

If you can ping the port, it shows that the configuration is correct and the network is

usable. Otherwise, check the configuration and the network connection.

You can use the self-loop to check if the communication problem is caused by faulty

links. Check further the router configuration, including the IP address, mask, static

route, protocol encapsulated on the WAN port, the corresponding timeslot, and the

extracted clock. Locate the problem, and ensure that you can ping the peer-end LAN

successfully.


41

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 4 Access of NEs to M2000

Chapter 4 Access of NEs to M2000

4.1 About This Manual

To access NEs to the M2000 means to access NEs to the M2000 O&M system. In

this way, you can operate on and maintain all the NEs through the M2000. Before

giving NEs access to the M2000, the NEs are debugged and they work properly.

This chapter introduces the order to access various NEs into the M2000 system, and

describes how to install the NE mediation software, create NEs and verify functions of

each interface.

4.2 Before Access

Before accessing NEs to the M2000:

57) Check if the connection between the M2000 system and the NEs to access is

normal.

Execute the following command on the M2000 server:

ping <NE IP>

If the connection is normal, the NE responds to the ping command.

58) Prepare the mediation installation package for these NEs.

For example, the mediation installation package for the M2000V200R002C02B006

UMG is iManagerM2000_UMG_MATCH_ENG_V200R002C02B006.tar.

59) Check the running status of M2000 services.

Log in to the M2000 server as root, and then execute the following command:

# svc_adm -cmd status

In normal circumstances, the information returned by the system contains [Not

Runing : 0 ]. This shows that all the M2000 services are started.

60) Check the running status of the high availability (HA) system, if any.

Log in to any of the two M2000 servers as root, and then execute the following

command:

# scstat

In normal circumstances, the system returns the following information:

Cluster Nodes: Both two nodes are online.

Cluster Transport Paths: There are two transport paths, and both are online.

Quorum Votes by Node: Both nodes are online.


1


Quorum Votes by Device: The device is online.

Device Group Servers: The active server configured by the device group ossdg

is the active node, and the standby server is the standby node.

Device Group Status: The device group ossdg is online.

Resource Groups and Resources: The resource group oss_rg contains

resources such as osssvr, ossdg_rs, sybase_rs and ossapp_rs.

Resource Groups: oss_rg is online on the active node and offline on the standby

node.

Resources: All resources are online on the active node and offline on the

standby node.

If the system is installed with two tape drives, rmt/1 and rmt/2 are displayed,

both in offline status.

4.3 Access Procedure

Table 1-1 shows the procedure for accessing an NE to the M2000 system.

Table 1-1 NE access procedure

Step Action Reference

1Install the mediation software of the NE on the

M2000 server.

4.4 Installing NE

Mediation Software

2Create the NE in the topology tree on the

M2000 client.4.5 Creating an NE

3Check the alarm management interface

between the M2000 and the NE.

4.6 Checking Alarm

Data Reporting

4Check the performance management interface

between the M2000 and the NE.

4.7 Checking

Performance Data

Reporting

5Check the backup interface between the M2000

and the NE.

4.8 Checking NE Data

Backing Up

6Check the log management interface between

the M2000 and the NE.

4.9 Checking NE Log

Uploading

7Create an NE user for the NE on the M2000

client.4.10 Adding NE Users

8Check the MML command interface between the

M2000 and the NE.

4.11 Checking MML

Command Delivery


2


Step Action Reference

9Check the LMT interface between the M2000

and the NE.4.12 Checking LMT

4.4 Installing NE Mediation Software

4.4.1 Introduction to NE Mediation Software

The M2000 software includes the common software and the mediation software. The

common software provides basic M2000 functions, and the mediation software

mediates various types of NEs to cover them in the M2000 system for uniform

management.

Install the mediation software separately after the M2000 common software is

installed and starts working properly.

The mediation software installation package is provided based on the NE version.

Execute the installation package on the M2000 server. When the mediation software

is installed, start the M2000 client, and the system automatically downloads relevant

information to the client from the M2000 server.

The installation of the different type NE mediation is the same.

4.4.2 Preparing Installation Files

Download the mediation software installation package for the NE to be accessed from

the website, and then upload it to the M2000 server as follows:

61) Create the installation package directory /export/home/mediation.

Log in to the M2000 server as user root, and then execute the following command:

# mkdir -p /export/home/mediation

62) Upload the installation package in the bin mode to /export/home/mediation

through FTP.

For example, copy the mediation software installation package for the UMG

iManagerM2000_UMG_MATCH_ENG_V200R002C02B006.tar to the M2000 client,

and then upload it in the bin mode to /export/home/mediation on the M2000 server

through FTP.

4.4.3 Stopping M2000 Services and Collector

Before installing the mediation software, ensure to stop the M2000 services and

Collector. The stopping procedure in the single server system is different from that in

the high availability (HA) system, as described in the following.


3


I. In Signle Server System


63) Set the work environment for the M2000 system.

# cd /opt/OMC

# . ./svc_profile.sh

64) Stop all M2000 services.

# stop_svc

65) Check over the M2000 services to ensure that all the services are stopped.

# svc_ps

If there is an output for this command, execute kill_svc to stop all the services

forcibly. Repeat these operations until there is no output after you execute svc_ps.

66) Stop Collector.

# /opt/OMC/bin/stop_collector

II. In HA System

Log in to the active node as root, and then execute the following command:


# cd /opt/OMC


68) Stop all M2000 services.

# scswitch -n -j ossapp_rs

69) Check over the M2000 services to ensure that all the services are stopped.

# svc_ps

If there is an output for this command, execute kill_svc to stop all the services

forcibly. Repeat these operations until there is no output after you execute svc_ps.

70) Stop Collector.

# /opt/OMC/bin/stop_collector

4.4.4 Installing Mediation Software

The installation of the mediation software varies according to the type of the NE. This

section takes the installation of

iManagerM2000_UMG_MATCH_ENG_V200R002C02B006.tar for the MGW as an

example to describe the installation procedure. For other versions of MGW's or other

types of NEs, the only difference lies in the name of the mediation software

installation package.


4


Log in to the active node as root, and then carry out the following operations:


# cd /opt/OMC


72) Decompress the mediation software installation package.

# cd /export/home/mediation

# tar xf iManagerM2000_UMG_MATCH_ENG_V200R002C02B006.tar

The system generates a directory named install mediation automatically.

73) Install the mediation software.

# cd /export/home/mediation/installmediation

# ./install.sh

The following information is displayed for you to confirm:

the Install NE Type is : MGWNE

the Install NE Version is : UMG8900V200R003C01B053

the Install Match Version is : iManagerM2000_UMG_MATCH_ENG_V200R002C02B006

Environment variable M2K_ROOT is : /opt/OMC

Are you sure to continue? [y/n]

Enter “y” to start the installation, and enter any other character to exit the installation.

74) If this version of mediation software is installed for the first time, the installer

completes the whole installation. If already installed, the installer prompts you to

decide whether to overwrite the existing version.

The MGWNE iManagerM2000_UMG_MATCH_ENG_V200R002C02B006 mediation has been

created!

Do you want to overwrite it? [y/n]

In this case, enter "y" to uninstall the existing version, and then reinstall this version of

mediation software. Enter any other character to exit the installation. Note to check

words such as "error" or “fail” in the output returned by the system. If displayed,

contact Huawei.

Logs for the installation process are recorded into the file /var/med_install.sh.

4.4.5 Displaying Mediation Software Version

After installing the mediation software, carry out the following operations to display

the mediation software version and to check the whole system.



5



# cd /opt/OMC


76) Display the version information.

Take the MGW for example.

# displayVersion -ne MGW //

Check the output for the following information:

<MGW>

Match Version : iManagerM2000_UMG_MATCH_ENG_V200R002C02B006

NE Version : UMG8900V200R003C01B053

If the screen displays the above information, it shows that the mediation version is

copied correctly. In this case, you can restart the M2000 client to create NEs.

If it is not contained in the output, you should reinstall the mediation software. Check

the following path to ensure that it is the correct installation for the M2000:

Environment variable M2K_ROOT is /opt/OMC.

If the installation path is correct, and if you still fail to install the mediation software,

contact Huawei.

4.4.6 Restarting M2000 Services and Collector

Before installing the mediation software, you should stop M2000 services and

Collector. Restart them when the installation is complete. The startup procedure in the

single server system is different from that in the HA system, as described in the

following.

I. In Single Server System


77) Start M2000 services.

# start_svc

You can open a Telnet window to log in to the server when the M2000 services are

starting. To monitor the startup process, execute the following command:

# tail -f /opt/OMC/startsvc.log

When all the M2000 services are started about 10 minutes later, close this Telnet

window.

78) Start Collector.

# /opt/OMC/bin/start_collector


6


II. In HA System


79) Start M2000 services.

# scswitch -e -j ossapp_rs

80) Start Collector.

# /opt/OMC/bin/start_collector

4.5 Creating an NE

4.5.1 Creating a UMTS NE

I. Description

Create a UMTS NE in the topology tree on the M2000 client.

After the NE is created, the M2000 generates management objects for this NE.

Through the automatic synchronization with the NE, the M2000 obtains the NE

configuration, and then saves it into the M2000 database. In addition, maintenance

channels are established between the M2000 and the UMTS NE to enable the M2000

server to manage the UMTS NE.

II. Prerequisites

Before creating the UMTS NE, ensure that:

The connection between the M2000 system and the UMTS NE is normal.

M2000 services are working properly.

The mediation software for the UMTS NE is installed successfully on the server.

The UMTS & GSM option is selected during the installation of the M2000 client.

The M2000 is authorized to manage the UMTS and GSM NEs.

III. Procedure

All UMTS NEs except Node B are created on the M2000 client in the same

procedure. Take the RNC creation for example, and the procedure is as follows:

81) Select the subnet.

Plan the location of the RNC in the topology tree and the subnet it belongs to.

If the subnet with the NE does not exist in the topology tree, you should create

the subnet. Right-click on the topology tree, and then select Create Physical

Subnet. In the displayed dialog box, enter the subnet name, and then choose

the subnet in the topology tree.

If the subnet with the NE already exists, choose the subnet in the topology tree.

82) Create the RNC.


7


Right-click on the topology tree, and select Create NE on the displayed menu. In the

displayed dialog box, select Access Network Series as the category and RNC as

the NE type, and then click Next. Enter the name and IP address of the NE, and then

click Finish.

Figure 1-1 shows the process for creating the RNC.

Figure 1-1 Creating RNC

83) Carry out the automatic synchronization.

After creating the NE, a corresponding icon is displayed on the topology tree for the

NE. If both the physical and logical connection between the NE and the M2000 works

properly, the M2000 synchronizes data with the NE to obtain the NE configuration.

The synchronization status is displayed in the topology tree.

84) Set the file server.

Choose Software > File Server Setting, and then select the NE type in the

navigation tree in the left part of the displayed window. In this example, select RNC.

In the right part window, select the created NE and the name of its file server.

You can select the OMC or the RNC itself as the file server for the created RNC NE

(OMC refers to the M2000). If there is a firewall between the RNC and the OMC, you

must select OMC as the file server. It is the same case with other NEs.

Now, the creation of the UMTS NE is complete. The M2000 can obtain automatically

the default performance data, alarm and log information of the NE.

4.5.2 Creating a GSM NE

I. Description

Create a GSM NE in the topology tree on the M2000 client.


8


The M2000 generates a management object for the UMTS NE, gets the configuration

information by synchronization with the NE, and saves it in the M2000 database. In

addition, the M2000 sets up maintenance channels with the NE and has it managed.

II. Prerequisites

Before creating a GSM NE, ensure that:

The physical and logical connections between the M2000 system and NEs work

properly.


The mediation software for the NE is installed successfully on the server.

The UMTS & GSM option is selected during the installation of the M2000 client.

The user account with the required privileges is created on the NE BAM.

Note:

Access the NE from the M2000 client with the user account to obtain the NE data.

While creating the NE on the M2000 client, you should also enter the username and

password. Ensure that they are the same as those set on the NE.

See the NE user manual to create the user account on the NE BAM.

III. Procedure

All GMS NEs are created on the M2000 client in the same procedure. Take the BSC

creation for example, the procedure is as follows:


Plan the location of the BSC in the topology tree and the subnet it belongs to.




this subnet in the topology tree.

If the subnet with the NE already exists, choose this subnet in the topology tree.

86) Create the BSC.


displayed dialog box, select Access Network Series as the category and BSC as the

NE type, and then click Next. Enter the name and IP address of the NE, and the

username and password of the account created on the NE BAM, as shown in Figure

1-1. Click Finish.


9


Figure 1-1 Creating BSC (1)

Figure 1-2 shows the process for creating the BSC.

Figure 1-2 Creating BSC (2)





Meanwhile, the synchronization status is displayed in the topology tree.


10


Now, the creation of the GSM NE is complete. The M2000 can obtain automatically


4.5.3 Creating a CDMA NE

I. Description

Create a CDMA NE in the topology tree on the M2000 client.

After the NE is created, the M2000 generates management objects for this NE.

Through the automatic synchronization with the NE, the M2000 obtains the NE

configuration, and then saves it into the M2000 database. In addition, the M2000 sets

up maintenance channels with the NE and has it managed.

II. Prerequisites

Before creating the CDMA NE, ensure that:

The connection between the M2000 system and NEs is normal.


The mediation software for the NE is installed successfully on the server.

The CDMA option is selected during the installation of the M2000 client.

The user account with the required privileges is created on the NE BAM.

Note:

Access the NE from the M2000 client with the user account to obtain the NE data.

While creating the NE on the M2000 client, you should also enter the username and

password. Ensure that they are the same as those set on the NE.

See the NE user manual to create the user account on the NE BAM.

III. Procedure

All CDMA NEs are created on the M2000 client in the same procedure. Take the

CMSC creation for example, and the procedure is as follows:


Plan the location of the CMSC in the topology tree and the subnet it belongs to.





If the subnet with this NE already exists, choose the subnet in the topology tree.

89) Create the CMSC.


11



displayed dialog box, select Core Network Series as the category and CMSC as the

NE type, and then click Next. Enter the name and IP address of the NE and the

username and password of the account created on the NE BAM, as shown in Figure

1-1. Click Finish.

Figure 1-1 Creating CMSC (1)

Figure 1-2 shows the process for creating the CMSC.

Figure 1-2 Creating CMSC (2)



12





Meanwhile, the synchronization status is displayed in the topology tree.

Now, the creation of the CDMA NE is complete. The M2000 can obtain automatically


4.5.4 Creating an IP Device

I. Description

Create an IP device in the topology tree on the M2000 client.

After the IP device is created, the M2000 generates management objects for the IP

device, and saves them into the M2000 database. In addition, the M2000 sets up

maintenance channels with the IP device and has it managed.

II. Prerequisites

Before creating an IP device, ensure that:

The connection between the M2000 system and the IP device is normal.


The M2000 authorizes the required privileges for the IP device.

III. Procedure


Plan the location of the IP device in the topology tree and the subnet it belongs to.





If the subnet with the NE already exists, choose the subnet in the topology tree.

92) Create the IP device.


displayed dialog box, select IP Device Series as the category and IP Device as the

NE type, and then click Next. Enter the name and IP address of the NE, and then

click Finish.

Now, the creation of the IP device is complete. The M2000 can obtain automatically

alarm information of the IP device.


13


4.5.5 Creating RAN

I. Description

Create a UMTS RAN in the topology tree on the M2000 client.

An RAN contains an RNC and multiple NodeBs in the RNC. After the RAN is created,

the M2000 generates management objects for these NEs. Through the automatic

synchronization with these NEs, the M2000 obtains the NE configuration, and then

saves it into the M2000 database. In addition, the M2000 sets up maintenance

channels with the NE and has it managed.

II. Prerequisites

Before creating the RAN, ensure that:

The connection between the M2000 system and NEs in the UMTS RAN is

normal.


The mediation software for each NE is installed successfully on the server.

Physical channels are set up between the RNC and NodeBs, and the interface

data is configured.

The UMTS/GSM option is selected during the installation of the M2000 client.

The required privileges are obtained.

III. Procedure

An RAN contains an RNC and multiple NodeBs hosted in the RNC. Create the RNC

first, and then each NodeB.

See 4.5.1 III. “Procedure” to create the RNC.

Creat the NodeBs one by one in the same way as that for the RNC; or create them all

at once, as follows:

93) Select the RNC.

Select the RNC with all the NodeBs in the topology tree.

94) Search automatically and create the NodeBs.

Right-click the RNC node and select Search. The system performs the following

operations automatically:

sSearchesing all the NodeBs hosted in the RNC, c

reates Creating topological objects forall the searched NodeBs

Displaying the topology in the topology view them in the topology tree, and then

synchronizes Synchronizing data with these NodeBs.

95) Set the file server.


14


Choose Software > File Server Setting. Select any NodeB node in the navigation

tree in the left part of the displayed window, and the created NodeB NEs are

displayed in the right part window. Select the file server for each of them.

You can select the OMC or the corresponding RNC as the file server for the created

NodeB NE. (The OMC refers to the M2000.) If there is a firewall between the RNC

and the OMC, you must select the OMC as the file server.

Now, the creation of the UMTS RAN is complete. The M2000 can obtain automatically

the default performance data, alarm and log information of the RAN.

4.5.6 Creating NEs in Batches

I. Description

Create multiple NEs in batches in the topology tree on the M2000 client.

After these NEs are created, the M2000 generates management objects for these

NEs. Through the automatic synchronization with these NEs, the M2000 obtains the

NE configuration, and then saves it into the M2000 database. In addition, the M2000

sets up maintenance channels with the NE and has it managed.

This applies only to the UMTS NEs, but not the GSM or CDMA NEs.

II. Prerequisites

Before creating NEs in batches, ensure that:

The connection between the M2000 system and NEs is normal.


The mediation software for each NE is installed successfully on the server.

The UMTS/GSM option is selection during the installation of the M2000 client.

The required privileges are obtained.

III. Procedure

Create multiple NEs in batches on the M2000 client as follows:

96) Edit the file for creating NEs in batches.

Create a CSV template for creating NEs in batches. Open the template, enter the NE

information, and then save the file.

For specifications on the NE template, see M2000 Operation Manual.


Plan the location of these NEs in the topology tree and the subnets they belong to.






15


If the subnet with this NE already exists, choose the subnet in the topology tree.

98) Import the file for creating NEs in batches.

Right-click on the topology tree and select Create Physical NEs in batches. In the

displayed dialog box, select a CSV file containing information of NEs to be created in

batches. Click OK, and the system creates automatically all NEs defined in the file.

After the creation of multiple NEs in batches is complete, the M2000 obtains the

default performance data, alarm and log information of these NEs automatically.

4.6 Checking Alarm Data Reporting

I. Description

Once created, the NE reports the alarm information to the M2000, so that you can

browse the information on the M2000 client.

You cannot view the NE alarm information if the NE access fails or the M2000 and

the NE do not match in the alarm interface.

Checking the alarm data reporting means to ensure that the NE is accessed correctly,

the alarm interface between the M2000 and the NE works properly, and that the

software version matches.

II. Prerequisites

Before checking the function, ensure that:

The NE is successfully created in the M2000 system.

The NE in the topology tree is connected with the M2000 system.

III. Procedure

Log in to the M2000 client and the NE LMT, and then carry out the following

operations:

99) Open the M2000 alarm browser.

On the M2000 client, choose Fault > Current Fault Alarm Browser to display Alarm

Browse, Query and Statistics.

100)View the current alarm.

Select the NE and click Apply, and the system displays the alarm information in a

dialog box as shown in Figure 1-1.


16


Figure 1-1 Displaying alarm information

101)Generate an alarm on the NE.

Pull out a trunk cable, and the LMT for the NE displays the trunk alarm.

102)Ensure that you can view the alarm on the M2000.

Open the window for displaying the alarm information.

In normal circumstances, it shows the alarm information on the NE.

4.7 Checking Performance Data Reporting

I. Description

After an NE is created, the NE reports the default performance data to the M2000, so

that you can browse it on the M2000 client.

You cannot view the performance data on the M2000 client if the NE access fails or

the M2000 and the NE do not match in the performance interface.

Checking the performance data reporting means to ensure that the NE is accessed

correctly, the performance interface between the M2000 and the NE works properly,

and that the software version matches.

II. Prerequisites





17


III. Procedure

Log in the M2000 client as admin, and then carry out the following operations:

103)Open the M2000 performance query window.

On the M2000 client, choose Performance > Query Result to display Query Result.

104)Set query conditions.

Click New Query to display Query. In the navigation tree on the left, select the NE

and the involved measurement sets; in the right part window, select objects (limited to

only available objects in the system), counters and measurement period. Click Query.

The queried results are shown in Figure 1-1

Figure 1-1 Querying performance information

105)Ensure that you can view the performance data on the M2000 client.

In normal circumstances, the system displays the performance data in Query Result

after you define the measurement period.

4.8 Checking NE Data Backing Up

I. Description

When a UMTS NE is created, the M2000 backs up the NE data through the NE data

backup function of the software management interface.

If the NE data is backed up successfully, it shows that the NE is accessed correctly,

the NE data backup function of the software management interface between the

M2000 and the NE works properly, and that the software version matches.


18


At present, the M2000 can back up data of only UMTS NEs instead of GSM and

CDMA NEs.

II. Prerequisites




III. Procedure


106)Open the M2000 manual backup window.

On the M2000 client, choose Tools > System Backup > Manual Backup to display

Manual Backup, as shown in Figure 1-1.

Figure 1-1 Manual backup

107)Select the NE you want to back up.

Select NE, and select the accessed NE, and then click Start. In the displayed dialog

box, click Yes, and the system displays Backup Browser.

108)Observe the backup progress.

The lower part of Backup Browser shows the backup progress. In normal

circumstances, the progress changes from 0% to 100%.

109)Ensure that the M2000 backs up the NE data.

When the backup progress reaches 100%, select Backup List.


19


In normal circumstances, you can see data files of the backed-up NE.

4.9 Checking NE Log Uploading

I. Description

When a UMTS NE is created, the M2000 obtains the NE logs through the NE log

uploading function of the software management interface.

If the NE log uploading is successful, it shows that the NE is accessed correctly, the

NE log uploading function of the software management interface between the M2000

and the NE works properly, and that the software version matches.

At present, only logs of UMTS NEs can be uploaded to the M2000. Logs of GSM and

CDMA NEs cannot be uploaded.

II. Prerequisites

Before checking the information, ensure that:



III. Procedure


110) Synchronize NE logs.

On the M2000 client, right-click the NE in the topology tree, and then select

Synchronize NE Log.

111) Open Software Browser.

On the M2000 client, choose Software > Browser to display Software Bowser.

112) Observe the upload progress.

The lower part of Software Browser shows the progress for uploading the NE logs.

In normal circumstances, the progress changes from 0% to 100%.

113) Check the NE logs on the M2000 client.

When the progress reaches 100%, choose System > Log Management > Log

Query and Statistic on the M2000 client.

In the displayed Log Management, choose NE Log under Log Query in the

navigation tree, and select the NE in Filter Condition, and then click Query, as

shown in Figure 1-1


20


Figure 1-1 Querying NE logs

In normal circumstances, logs of the NE are displayed in the lower part of Log

Management.

4.10 Adding NE Users

I. Description

Adding NE users means to create users for a specified NE and authorize them the

authority for MML command groups. In this way, they can execute MML commands of

the NE and run the LMT.

At present, you can add NE users for UMTS NEs only.

II. Prerequisites

Before adding an NE user, ensure that:



III. Procedure


114) Open Security Management.

On the M2000 client, choose System > Security Management to display Security

Management.

115) Create an NE user.


21


Right-click the NE in the navigation tree on the left, and then select Add NE User to

display Add NE User. Select the user account from the list, and then click OK. The

system binds the M2000 user account to the NE, so that the user becomes NE user.

116) Bind command groups.

In the navigation tree on the left, right-click the created NE user under the node User,

and select Bind NE to display Bind User to NE.

Select command groups from the list on the right and then click OK, so that the user

can execute commands in these command groups, as shown in Figure 1-1.

Figure 1-1 Binding NE user to command groups

Now, an NE user is added successfully.

Use the user account to log in, and ensure that you can execute MML commands and

start the LMT of the NE.

4.11 Checking MML Command Delivery

I. Description

After creating the NE and adding the NE user, deliver MML commands on the NE

through the MML command window on the M2000 client.

Checking MML command delivery means to ensure that the NE is accessed correctly,

the NE user is added successfully, the security management interface between the

M2000 and the NE works properly, and that the software version matches.

II. Prerequisites

Before checking this function, ensure that:


22




Users are added for the NE.

III. Procedure

Log in the M2000 client as the user bound to the NE, and then carry out the following

operations:

117) Open MML Command.

Choose Configuration > MML Command to display MML Command, as shown in

Figure 1-1.

Figure 1-1 MML command

118) Obtain information about MML commands for the NE.

In the navigation tree in the upper part window, select the NE, and the system obtains

MML command file automatically for the NE.

119) Execute MML commands.

In the lower part window in Figure 1-1, enter the MML command, and the system

displays the returned information in the upper part window. For example, enter LST

EMS for RNC NEs, and the system displays information about the M2000 operator.


23


Figure 1-1 Responding to MML command

In normal circumstances, the NE responds to the delivered MML command.

4.12 Checking LMT

I. Description

After creating the NE and add the NE user, you can start the LMT of the NE on the

M2000 client.

Checking the LMT means to ensure that the NE is accessed correctly, the NE user is

added successfully, the security management interface between the M2000 and the

NE works properly, and that the software version matches.

At present, you can start the LMT for UMTS NEs only. GSM and CDMA NEs do not

support this function.

II. Prerequisites




Users are added for the NE.

The LMT software of the NE is installed on the PC, and the LMT version matches

the NE version.

III. Procedure

Log in the M2000 client as the user bound to the NE, and then carry out the following

operations:


24


120)Start the LMT.

In the topology tree, right-click the NE and select Maintenance Client to display the

local maintenance system of the NE.

Note:

For the non-GSM NE, the LMT provides only one operation menu, namely,

[Maintenance].

For the GSM NE, the LMT provides multiple operation menus, such as Traffic

Statistics, Data Management. In addition, the LMT provides different operation

menus for different GSM NEs.

121)Log in the LMT.

Log in the LMT as the NE user.

In normal circumstances, you can start and log in to the NE LMT on the M2000 client

automatically as the NE user. No extra username or password is necessary.


25

Commissioning GuideiManager M2000 Mobile Element Management System

Chapter 5 Commissioning of Remote Alarm Notification

Service

Chapter 5 Commissioning of Remote Alarm

Notification Service


This chapter introduces the remote alarm notification service and describes how to

commission the remote alarm notification service.

5.2 Introduction to Remote Alarm Notification

5.2.1 Introduction to Remote Alarm Notification Service

The M2000 provides the remote alarm notification service. Through this service, the

system delivers real time alarm information to you by short messages, over telephone

or by e-mails.

5.2.2 Introduction to Alarm-Notification-over-BP/Telephone

Alarm-Notification-over-BP/Telephone is a function based on the remote alarm

notification service provided by the M2000. Through this function, you can get the real

time alarm information over BP/telephone. That is, when an alarm occurs, your BP

beeps and displays the alarm information, or your fixed phone rings.

You can set in the system that which alarms trigger your BP or telephone.

To use this function, you should connect the M2000 server or client to the PSTN

network through a wired Modem.

5.2.3 Introduction to Alarm-Notification-by-Short-Messages

Alarm-Notification-by-Short-Messages is a function based on the remote alarm

notification service provided by the M2000. Through this function, you can get the real

time alarm information in short messages over your cell phone. That is, when an

alarm occurs, you receive a short message on your cell phone showing the alarm

information.

You can set in the system that information about which alarms is sent to your cell

phone in short messages.

To use this function, you should connect the M2000 client to the PSTN network

through a wireless Modem.


1



Service

5.2.4 Introduction to Alarm-Notification-by-E-mail

Alarm-Notification-by-e-mail is a function based on the remote alarm notification

service provided by the M2000. Through this function, you can get the real time alarm

information by e-mails. That is, when an alarm occurs, you receive an e-mail in your

e-mail box showing the alarm information.

You can set in the system that information about which alarms is sent to your Email

box in e-mails.

To use this function, you should connect the M2000 system to the SMTP server of the

Internet.

5.3 Commissioning Alarm-Notification-over-BP/Telephone

5.3.1 Commissioning Procedure

Figure 1-1 shows the procedure for commissioning

Alarm-Notification-over-BP/Telephone.

Figure 1-1 Procedure for commissioning Alarm-Notification-over-BP/Telephone

Table 1-1 describes this procedure in detail.


2



Service

Table 1-1 Description of the procedure for commissioning Alarm-Notification-over-

BP/Telephone

No. Step Reference Description

1

Install a

wired

Modem.

Install an external

wired Modem.

5.3.2 Installing

External Wired

Modem

You can install the

Modem on the

server or the client.

The latter is

recommended.

The M2000 system

needs only one

Modem for Alarm-

Notification-over

BP/Telephone.

Install an internal

wired Modem.

5.3.3 Installing

Internal Wired

Modem

2Commission

the Modem.

Commission the

server side

Modem.

5.3.4

Commissioning

Server Side

Modem

The server and the

client use different

operating systems.

Accordingly, the

procedure for

commissioning the

Modem varies.

Commission the

client side

Modem.

5.3.5

Commissioning

Client Side

Modem

3 Configure related parameters.

5.3.6

Configuring

Parameters for

Alarm-

Notification-over-

BP/Telephone

Configure

parameters for this

function on the

client.

4 Check this function.

5.3.7 Checking

Alarm-

Notification-over-

BP/Telephone

5.3.2 Installing External Wired Modem

You can install the external wired Modem on the M2000 server (the Sun server) or the

client (the PC).


3



Service

I. Checking Serial Ports

To install the Modem on the server

Serial port A and serial port B on some types of Sun servers refer to the same

physical serial port, for example, Sun Fire V880 and Sun Fire V890 servers. Ensure

not to connect two devices on these two ports at the same time. For example, avoid

connecting wired and wireless Modems at the same time.

To install the Modem on the client

Before installing any hardware, ensure to shut down the M2000 client.

Check whether there is an alarm box connected to the client. If so, specify the

number of the serial port occupied by the alarm box. Ensure to connect the Modem to

an unused serial port.

To view the serial port used by the alarm box, check the value of PortName in the file

<Installation directory of M2000 client>\style\defaultstyle\conf\alarmclient\

alarmboxconfig.xml. For example, <PARA name="PortName" value="COM1" />

shows that the alarm box is connected on serial port COM1.

Note:

If the M2000 client has only one serial port and the port is connected to an alarm box,

disconnect the alarm box from the client, and modify the value of PortName to an

inexistent serial port, such as COM10, to install the Modem.

If the system is not installed with an alarm box, modify the value of PortName to an

inexistent serial port, such as COM10.

II. Installing Modem

Install an external wired Modem as follows:

122)Connect the serial port cable.

Use the serial port cable delivered with the Modem to connect the Modem to the

M2000 server or client. One end connects the Modem, and the other connects the

serial port on the M2000 server or client.

Note:

Use a connector if the interface of the serial port cable is different from the serial port

on the M2000 server or client.


4



Service

123)Connect the power cable.

Use the DC power cable delivered with the Modem. For details on connecting the

power cable, see the Specifications delivered with the Modem.

124)Connect the telephone line.

Connect the telephone line to port Line on the Modem. For details, see the

Specifications delivered with the Modem.

125) Install the Modem driver.

See the Specifications delivered with the Modem to install the Modem driver.

5.3.3 Installing Internal Wired Modem

You can only install the internal wired Modem on the M2000 client, namely, the PC.


Install the internal wired Modem as follows:

126)Switch off the PC.

127)Open the PC chassis.

128) Insert the Modem into the PCI slot.

Choose an available PCI slot and open the cover over it. Insert the Modem into the

slot, and ensure that the gilded joint part of the Modem is pressed tightly into the PCI

slot. Close the cover to fix the Modem in the slot.

129)Connect the telephone line.

Connect the telephone line to port line on the Modem. For details, see the

Specifications delivered with the Modem.

130)Close the PC chassis.


See the Specifications delivered with the Modem to install the Modem driver.

5.3.4 Commissioning Server Side Modem

On the server side, you can only install an external Modem. Commission it as follows:

132)Switch on the Modem, and it carries out initialization automatically.

133)Log in to the Solaris operating system of the M2000 server as root.

134)Enable the serial port, and set the baud rate.

Execute tip -9600 /dev/term/a to enable the serial port and set the baud rate.

connected

In this command, 9600 is the baud rate, and /dev/term/a stands for serial port A.


5



Service

135)Ensure that the Modem works properly.

Execute the command at to check the Modem.

OK

If the system returns OK, it shows that the Modem is connected properly.

136)Try a number to test the dialing.

Execute atdt88812345 to check the dialing.

OK

If the system returns OK, it shows that the dialing works properly.

137)Stop the dialing.

Execute the command ath to stop the dialing.

OK

138)Exit the tip command.

Execute ~. to exit tip.

[EOT]

If you fail to exit the tip command after enter ~., press Enter, and then enter ~..

5.3.5 Commissioning Client Side Modem

You can install an external or internal Modem on the M2000 client. Commission the

Modem on the client as follows:

139)Switch on the external Modem, and it carries out initialization automatically. If an

internal Modem is installed, you do not need to switch on the Modem.

140)Log in the Windows operating system of the M2000 client as administrator.

141)Choose Start > Programs (P) > Accessories > Communications >

HyperTerminal to start HyperTerminal.

142)Set up a connection. Enter the connection name, such as modem, as shown in

Figure 1-1, and then click OK.


6



Service

Figure 1-1 Setting up a connection

143)Select the serial port for connection. For example, select COM1, as shown in

Figure 1-1, and then click OK.

Figure 1-1 Selecting a serial port

144)Set attributes of the serial port according to Figure 1-1, and then click OK.


7



Service

Figure 1-1 Setting serial port attributes

145) In Figure 1-1, enter the command at for commissioning the dialing.

Figure 1-1 Commissioning the dialing

OK


8



Service

If the system returns OK, it shows that the Modem is connected properly.

146)Execute atdt88812345 to try a number to test the dialing.

OK

If the system returns OK, it shows that the dialing works properly.

147)Execute ath to stop the dialing.

OK

148)Shut down HyperTerminal.

5.3.6 Configuring Parameters for Alarm-Notification-over-BP/Telephone

You can install the Modem on the M2000 server or client (the PC). Configure the

parameters for Alarm-Notification-over-BP/Telephone only on the client (the PC).

Configure the parameters as follows:

149)Log in to the M2000 client as admin or the user that has the authority to set the

remote alarm notification.


9



Service

Note:

After installing the Modem on the client, log in to the client as admin or a user that

has the authority to set the remote alarm notification, and keep this client running.

The alarm notification is deactivated if you shut down the client or log in to the client

as any other user account.

Ensure that the parameter RemoteNotifyEventProcessor in the file <M2000

installation directory>\style\defaultstyle\conf\alarmclient\loadedcell.xml is not

commented.

150)Choose Fault > Fault Service Settings. In Remote Notify, enter the user name

and the phone or page number, select the alarms to send, and then click Add to

add a record of user information for receiving remote alarm notification.

151) In the User Information field, click Setting….

152) In the displayed Remote notify detail settings, select Phone pager. Select

Activate, and enter parameters such as Serial port and Send point. Click Set.

Note:

If you select Send by client as Send point, ensure to select Current client can be

used for phone or pager on only one client. Otherwise, the same alarm notification

may be sent many times.

153)Enter the telephone number behind Test phoneNo or pagerNo, such as

“862187654321”, and then click Test. In the displayed Test, the M2000 drives

the wired Modem to dial this number. If everything is normal, the system prompts

that the dialing is successful. Otherwise, the system prompts a failure message.

In this case, check the configuration.

154)Click Close to close Remote notify detail settings.

5.3.7 Checking Alarm-Notification-over-BP/Telephone

After installing the Modem, create an alarm manually to check Alarm-Notification-

over-BP/Telephone.

To create an alarm manually, perform the following steps::

155)Connect the telephone, and ensure that it works properly.


10



Service

156) In Remote Notify, select a record of user information, and then set to receive

the check alarm. For example, select an alarm with the NE type as OMC, such

as CPUAlarm--1, and then click Modify.

157)Choose Tools > System Monitor > Configurations to display System Monitor

Configurations.

158)Modify the CPU and memory used rate. For example, set both the CPU and

memory used rate to 2. The system generates an alarm when the CPU and

memory used rate exceeds this value. Wait until the alarm board prompts the

alarm.

In normal cases, the phone rings or the pager beeps with three ringing tones for the

system alarm. It displays the calling number if it subscribes to the Caller ID Display

(CID) function.

When the test is complete, restore the settings.

If error occurs, check and ensure that the Modem works properly, that parameters are

configured correctly, and that the service RemoteNotifyService is running on the

server.

5.4 Commissioning Alarm-Notification-by-Short-Messages

5.4.1 Commissioning Procedure

Figure 1-1 shows the procedure for commissioning Alarm-Notification-by-Short-

Messages.

Start

End

Check Alarm-Notification-by-Short-Messages

Configure related parameters

Commission wireless modem

Install wireless modem

Figure 1-1 Procedure for commissioning Alarm-Notification-by-Short-Messages

Table 1-1 describes this procedure in detail.


11



Service

Table 1-1 Description of the procedure for commissioning Alarm-Notification-by-

Short-Messages

No. Step Reference Description

1Install the wireless

Modem.

5.4.2 Installing

Wireless Modem

You can install the

Modem on the client.

The M2000 system

needs only one Modem

for Alarm-Notification-by

Short/Messages.

2Commission the wireless

Modem.

5.4.3

Commissioning

Wireless Modem

None.

3Configure related

parameters.

5.4.4 Configuring

Parameters for

Alarm-Notification-

by-Short-Messages

Configure parameters

for this function on the

client.

4 Check this function.

5.4.5 Checking

Alarm-Notification-

by-Short-Messages

None.

5.4.2 Installing Wireless Modem

The 38 Kbps Modem supports the wireless GSM/GPRS. Install the Modem on the

M2000 client (the PC).

I. Checking Serial Ports


Check whether there is an alarm box connected to the client. If so, specify the

number of the serial port occupied by the alarm box. Ensure to connect the Modem to

an unused serial port.

To view the serial port used by the alarm box, check the value of PortName in the file

<Installation directory of M2000 client>\style\defaultstyle\conf\alarmclient\

alarmboxconfig.xml. For example, <PARA name="PortName" value="COM1" />

shows that the alarm box is connected on serial port COM1.


12



Service

Note:

If the M2000 client has only one serial port and the port is connected to an alarm box,

disconnect the alarm box from the client, and modify the value of PortName to an

inexistent serial port, such as COM10, to install the Modem.

If the system is not installed with an alarm box, modify the value of PortName to an

inexistent serial port, such as COM10.

II. Installing Modem

To install the wireless Modem, perform the following steps:

159) Install the SIM card.

Install the subscriber identity module (SIM) card according to the operation guide of

the wireless Modem.

160)Disable the PIN check function of the SIM card.

Execute tip to deliver at to the SIM card to disable the personal identity number (PIN)

check function of the SIM card. If the PIN in the SIM card is 1234, execute the

following two functions:

AT+CPIN=1234

AT+CLCK="SC",0,1234

Execute the first command to submit the PIN to the SIM card for check. Execute the

second command to disable the PIN check function of the SIM card.

If the SIM card returns error after executing the second command, wait about one

minute, and then execute it again.

Note:

You can also insert the SIM card into a cell phone, and use the PIN setting in the cell

phone to disable the PIN check. The setting interface varies according to the cell

phone type. For details, see the instructions delivered with the cell phone.

161)Connect the serial port cable.

One end of the serial port cable used for installing the Modem is a DB-9 male

connector, and is connected to the Modem. The other end is a DB-9 female

connector, and is connected to the serial port on the M2000 client.


13



Service

Note:

Use a connector if the interface of the serial port cable is different from the serial port

on the M2000 client.

162)Connect the power cable.

Use the DC power cable delivered with the Modem. For details on connecting the

power cable, see the specifications delivered with the Modem.


See the specifications delivered with the Modem to install the Modem driver.

5.4.3 Commissioning Wireless Modem

Commission the wireless Modem in the same way as the wired Modem. See 5.3.5

“Commissioning Client Side Modem” to commission the wireless Modem.

5.4.4 Configuring Parameters for Alarm-Notification-by-Short-Messages

Configure the parameters for Alarm-Notification-by-Short-Messages on the client(the

PC).

To configure the parameters, perform the following steps:

164)Log in to the M2000 client as admin or the user that has the authority to set the


Note:

After you installing the modem Modem on the client, log into the client as admin or a

user account authorized with the authority for setting the alarm notification, and keep

this the client running.

The alarm notification is deactivated if you shut down the client or log in ton the client

as any other user account.

Ensure that the parameter RemoteNotifyEventProcessor in the file <M2000

installation directory>\style\defaultstyle\conf\alarmclient\loadedcell.xml is not

commented.


and the cell phone number, select the alarms to send, and then click Add to add

a record of user information for receiving remote alarm notification.


14



Service


167) In the displayed Remote notify detail settings, select SMS. Select Activate,

and enter parameters such as Serial port. Send point must be “Send by

client”. Click Set.

Note:

Ensure to select Current client can be used to send SMS on only one client.

Otherwise, the same alarm notification may be sent many times.

168) In the entry box behind Test NO, enter a cell phone number with the country

code; for example, 8613987654321. Click Test to check whether the number is

set correctly. If all the settings are correct, the system prompts that the operation

is successful, and a short message “This is a test” is sent to the set cell phone.


5.4.5 Checking Alarm-Notification-by-Short-Messages

After installing the Modem, create an alarm manually to check Alarm-Notification-by-

Short-Messages.

To create an alarm manually, perform the following steps:

170)Switch on the cell phone to be set for receiving the short message, and ensure

that it works properly.


the check alarm. For example, select an alarm with the NE type as OMC,

CPUAlarm--1, and click Modify.


Configurations.




alarm.

In normal circumstances, the cell phone receives a SMS after a short while. The

period of time from the SMS sending to the receiving depends on the mobile network.

The received SMS is in the following format:

+++ MSC id=11 15:42:06 minor restored power system ---



15



Service

If error occurs, check and ensure that the Modem works properly, parameters are


server.

5.5 Commissioning Alarm-Notification-by-Email

5.5.1 Before Commissioning

Before commissioning the Alarm-Notification-by-e-mail function, ensure that the

M2000 system is connected to the SMTP server.

5.5.2 Configuring Parameters for Alarm-Notification-by-Email

To configure the parameters of Alarm-Notification-by-e-mail, perform the following

steps:

174)Log in the M2000 client as admin or the user that has the authority to set the


Note:

If you select Send by client as Send point, ensure that:

You log in to the client as admin or a user account authorized with the

authority for setting the alarm notification, and keep the client running.

The alarm notification is deactivated if you shut down the client or log in to the

client as any other user account.

The parameter RemoteNotifyEventProcessor in the file <M2000 installation

directory>\style\defaultstyle\conf\alarmclient\loadedcell.xml is not

commented.


and the email address for receiving the notification alarms, select the alarms to

send, and then click Add to add a record of user information.


177) In the displayed Remote notify detail settings, select Email. Select Activate,

and enter parameters such as Hostname or IP of SMTP and Send point. Click

Set.


16



Service

Note:

If you select Send by client as Send point, ensure to select Current client can be

used to send Emails on only one client. Otherwise, the same alarm notification may

be sent many times.

178) In the entry box behind Address of receiver, enter an e-mail address for

receiving the notification; for example, [email protected]. Click Test. An alarm

notification e-mail is sent to this e-mail address, with “Alarm for test” attached

indicating that this is a test e-mail.


5.5.3 Checking Alarm-Notification-by-Email

To create an alarm manually to check Alarm-Notification-by-e-mail, perform the

following steps:

180)Ensure that the SMTP server connected to the M2000 system works properly.


the check alarm. For example, select an alarm with the NE type as OMC,

CPUAlarm--1, and click Modify.


Configurations.




alarm.

In normal circumstances, the e-mail is sent to the set address after a short while. The

period of time from the e-mail sending to the receiving depends on the Internet

network. The received e-mail is in the following format:

+++ HuaWei

Alarm category: Fault

Alarm severity: Major

Alarm date: 2004-10-01

Alarm time: 12:30:00

Confirm date:

Confirm time:

Restore date:

Restore time:

Product type: Mobile


17

mailto:[email protected]



Service

Alarm type: Power system

Internet serial number: 888

Equipment serial number: 9

NE ID: iMAP

NE type: MSC

Alarm ID: 2

Alarm name: Alarm name used in the test productid=2 netype=0 alarmid=2

Attched information: Alarm for test

--- End


If error occurs, check and ensure that the SMTP works properly, parameters are


server.


18

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 6 Commissioning of Alarm Box

Chapter 6 Commissioning of Alarm Box


This chapter introduces the operations for installing and commissioning the alarm box

that are closely related to the M2000 commissioning.

For details on the alarm box, see General Alarm Box User Manual.

6.2 Cabling Power Cable and Serial Port Cable

I. Power Cable

Three types of power supply are available for the alarm box: AC 220 V, AC 110 V and

DC -48 V. The factory setting is AC 220 V. Choose one of the above power supplies

for the alarm box.

II. Fuse

For the AC 110 V power supply, choose the fuse with specifications as F, 2A, H, 250

V; for the AC 220 V power supply, choose the fuse with specifications as F, 1A, H,

250V.

III. Serial Port Cable

Use the RS232 serial port cable delivered with the alarm box. The cable length

should not be more than 80 m [314.96 in.].

In case of signal interference, ensure not to cable the serial port and the power cable

in parallel in the same tube.

6.3 Installing and Fixing Alarm Box

6.3.1 Introduction to Alarm Box

The M2000 system uses the general alarm box of Huawei, as shown in Figure 1-1.

The dimensions of the alarm box are 412 mm x 282 mm x 90 mm [16.22 in. x 11.10

in. x 3.54 in.], with the weight as 2.6 kg [5.733 lb].


1


Figure 1-1 Appearance of the alarm box

On the front of the alarm box, there are mainly the audible and visible alarm

information display (such as the four level alarm indicators and speaker) and

operation buttons. On the side there are the power supply, interface sockets, etc..

Considering the security of the alarm box, the door of the box is equipped with a lock.

Only the personnel with the keys can open the alarm box to perform operations inside

the alarm box. All the keys are the same for the convenience of the maintenance

personnel. The door of the alarm box is removable for the convenience of installation

and maintenance.

All the external cables enter the box through the protective cable sheathing at the

bottom of the box.

6.3.2 Connecting Alarm Box to M2000

You can connect the alarm box to any of the M2000 clients (PCs) or the terminal of

the NE LMT. The former is recommended.

As shown in Figure 1-2, connect one end of the RS232 serial port cable to port COM2

(recommended) on the alarm box, and the other end to port COM1 (recommended)

on the M2000 client. One end of this serial port cable is an RJ-45 connector, which

connects the port COM2 (recommended) on the alarm box. The other end is a DB-9

connector, which connects the port COM1 (recommended) on the PC working as the

M2000 client.


2


Figure 1-2 Position of the alarm box in the M2000 system

6.3.3 Fixing Alarm Box

Fix the alarm box on a wall near the M2000 client to which the alarm box is

connected.

6.4 Configuring Alarm Box

6.4.1 Setting Power Input

I. AC Power

Adjust the red switch “220 V/110 V power selection rocker switch” under the

transformer on the alarm box. When the switch shows 230, the alarm box uses the

AC 220 V power input; when it shows 115, the alarm box uses the AC 110 V power

input.

II. DC Power

When the alarm box uses the DC -48 V power supply, move the connector from JT9

to JT6, as shown by the solid arrow in Figure 1-3. Meanwhile, connect the DC -48 V

power cable to JT3 on the power board inside the alarm box, as shown by the hollow

arrow in Figure 1-3.


3


Figure 1-3 Layout of interfaces inside the alarm box

6.4.2 Configuring Serial Port

Connect the M2000 client to the RS232 serial port on the alarm box. The M2000

client uses only one RS232 serial. It is recommended to use COM2 (namely, serial

port J5) and to disable other serial ports. Figure 1-4 shows the DIP switch in such a

case. The position of S2 and S1 on the board is shown in Figure 1-3.

S2

OFF

ON

87654321

S1

OFF

ON

87654321

Figure 1-4 Setting the DIP switch of the serial port

6.4.3 Setting Alarm Box Volume

Adjust the potentiometers RP1 and RP2 on the board to set the volume of the alarm

box. The position of RP1 and RP2 on the board is shown in Figure 1-3.

Adjust RP1 to set the volume of the speaker connected on JT9, and adjust RP2 to set

the volume of the speaker connected on JT10 or the remote end sound box.


4


Set the volume as follows:

To turn up the alarm box

Adjust RP1 or RP2 counter clockwise with a Phillips screwdriver, namely, in the

direction from 3 to 1 marked on the potentiometer.

To turn down the alarm box

Adjust RP1 or RP2 clockwise with a Phillips screwdriver, namely, in the direction from

1 to 3 marked on the potentiometer.

6.5 Checking Alarm Box

6.5.1 Checking Alarm Box Power-on

I. Checking Before Power-on

Before switching on the alarm box, ensure that you:

184)You fix the alarm box firmly on the wall.

185)You select the correct external power supply, such as the AC 220 V or AC 110 V

power supply, or the DC -48 V power supply, and the fuse capacity for

connecting the AC 220 V or AC 110 V power supply.

186)You set the DIP switch of S1 and S2 is correctly.

187)You connect the external serial port cable correctly.

188)The power switch shows Off when you connect the power switch cable to JT6 or

JT9.

II. Checking Power-on

See General Alarm Box User Manual to check power-on/power-off of the indicator,

reset key and alarm sound.

6.5.2 Commissioning Alarm Box with M2000

Connect the alarm box to the PC at the M2000 client, and then start the M2000 client

to perform the following tests:

189)Test the audio and visual alarms generated on the alarm box.

Create alarms of various severities on the alarm box, and check whether it gives

corresponding audio/visual alarms.

The indicator for an alarm severity remains on as long as there are unrestored and

unacknowledged alarms of this severity.

190)Test the control of the M2000 over the alarm box.

The M2000 supports the following three operations on the alarm box:


5


Stopping the alarm sound: This operation equals to pressing the alarm

acknowledgement button on the alarm box.

Resetting the alarm box: This operation equals to pressing the reset button on

the main board of the alarm box.

Shutting down the alarm box: After this operation, the M2000 clears all alarm

information stored in the alarm box and stops the sound and light. In addition, the

M2000 does not send any alarm information to the alarm box. However, the

communications connection between the M2000 and the alarm box still exists.

If abnormal results occur, check the serial port connection between the M2000 client

and the alarm box.


6

Commissioning GuideiManager M2000 Mobile Element Management System Chapter 7 Commissioning of Alarm Plate

Chapter 7 Commissioning of Alarm Plate


This chapter introduces the operations for installing and commissioning the alarm

plate. These operations are closely related to the M2000 commissioning.

For more information, see the manual delivered with the alarm plate.

7.2 Installing Alarm Plate

You can install the alarm plate on the wall of the equipment room, or anywhere far

away from the equipment room.

Use the serial port cable to connect the COM ports on the alarm plate and the M2000

client.

According to various types of COM ports, the serial port cable provides two

connectors: DB-9 (with nine pins) and DB-25 (with 25 pins). During the installation,

ensure that the cable connector matches the COM port.

7.3 Checking Alarm Plate

Connect the alarm plate to the PC at the M2000 client, and then start the M2000

client to perform the following tests:

Create alarms of various severities on the alarm plate, and check whether it gives

corresponding audio/visual alarms.


1


Chapter 8 Commissioning of Dial-Up Connection



PSTN users can access the M2000 system through the dial-up connection.

This chapter describes how to set up and check the dial-up connection.

8.2 Introduction to Dial-Up Connection

The dial-up connection means that the M2000 client accesses the PSTN through the

Modem dial-up. The dial-up server also accesses the PSTN through the Modem. The

TCP/IP connection is set up between the dial-up server and the M2000 server. This

connection assigns an IP address to the remote operation terminal, so that you can

start the M2000 client program on the M2000 client to log in to the M2000 system, as

shown in Figure 1-1.

Figure 1-1 Dial-up connection

8.3 Commissioning Procedure

Figure 1-2 shows how to commission the dial-up connection.


1



Figure 1-2 Procedure for commissioning the dial-up connection

Prepare all the required device cables, configure the dial-up server and client, and

then check whether the dial-up connection works.

After setting up a dial-up connection successfully, connect the terminal to the PSTN

through the Modem and telephone line. Configure this terminal as the dial-up client

and ensure that this connection works. In this way, you can set up another dial-up

connection.

8.4 Connecting Devices

8.4.1 Before Connection

Before connecting the related devices, prepare devices and information as listed in

the following table:

Device or

informationQuantity Use

PC 2

Use one PC as the dial-up server and the other as the

client. Both PCs use the Windows 2000 Professional

operating system.


2



Device or

informationQuantity Use

Modem 2

Connect one Modem to the M2000 client and the

other to the dial-up server to have them accessing the

PSTN.

If the PCs are configured with a built-in Modem,

external Modems are unnecessary.

See the attached manual of the Modem to install the

Modem driver.

PSTN number 2

These two numbers are telephone numbers

corresponding to the dial-up server and client in the

PSTN.

8.4.2 Methods for Connecting Devices

As shown in Figure 1-1, connect the related devices through the serial port cable, the

telephone line, or the network cable.

I. Through Serial Port Cable

When using an external Modem, use the serial port to:

191)Connect the Modem and the dial-up server.

192)Connect the Modem and the M2000 client.

II. Through Telephone Line

Use the telephone line to:

193)Connect the Modem on the dial-up server to the PSTN.

194)Connect the Modem on the client to the PSTN.

III. Through Network Cable

Use the network cable to connect the dial-up server to the LAN switch in the M2000

system.

8.5 Configuring Dial-Up Server

8.5.1 Setting IP Address

Assign an IP address to the dial-up server. Ensure that the IP address is in the same

network segment as that of the M2000 server.


3



In the Windows operating system, set the IP address as follows:

195)Choose Start >Settings > Control Panel.

196)Double-click Network and Dial-up Connections.

197)Right-click Local Area Connection, and select Properties to display Local Area

Connection Properties.

198)Select Internet Protocol (TCP/IP) and click Properties to display Internet

Protocol (TCP/IP) Properties.

199)Select Use the following IP address to display a dialog box as shown in Figure

1-1, and set IP address, Subnet mask and Default gateway. Ensure that the

set IP is in the same network segment as the IP of the M2000 server, and then

click OK.

Figure 1-1 Setting the IP address of the dial-up server

8.5.2 Configuring Network Connection

Configure network connection for the dial-up server as follows:

200)Choose Start > Settings > Network and Dial-up Connections/Make New

Connection to display a dialog box as shown in Figure 1-1.


4



Figure 1-1 New Connection Wizard

Note:

If you configure the network and dial-up connections for the first time, the screen

displays the dialog box about location information. Click Cancel.

201)Click Next, and the system displays a dialog box as shown in Figure 1-1.


5



Figure 1-1 Network Connection Type

202)Select Accept Incoming Connections and click Next, and the system displays

a dialog box as shown in Figure 1-1.

Figure 1-1 Selecting a connection device


6



203)Select Modem, and then click Next to display a dialog box as shown in Figure 1-

1.

Figure 1-1 Incoming Virtual Private Network (VPN) Connection

204)Select Do not allow virtual private connections, and then click Next to display

a dialog box as shown in Figure 1-1.

205)Select an existing user or the user with a new dial-up connection.


7



Figure 1-1 User permissions

To select an existing user

Select a user from the user list, and then click Next to display a dialog box as shown

in Figure 1-3.

To add a user

Click Add… to display a dialog box as shown in Figure 1-2. Set the user properties,

and then click OK to display a dialog box as shown in Figure 1-3.

Figure 1-2 New User


8



Figure 1-3 Network software

206)Select all components in the list, and then click Next to display a dialog box as

shown in Figure 1-1.

Figure 1-1 New connection wizard complete


9



207)Enter a name for the connection, and then click Finish to complete configuring

the dial-up server.

8.5.3 Specifying IP Range of Dial-Up Client

Specify the IP address range of the dial-up client as follows:

208)Choose Start > Settings > Control Panel.


210)Right-click Incoming Connections, and select Properties to display Incoming

Connections Properties.

211) Select Networking to display the network setting window.

212)Select Internet Protocol (TCP/IP) and click Properties to display Incoming

TCP/IP Properties.

213)Select Specify TCP/IP addresses in TCP/IP address assignment and enter

the IP address range allowed to be allocated automatically to the dial-up client,

as shown in Figure 1-1. Click OK.

Note:

Normal routes must be available for the dial-up client to access the M2000 server.

The IP addresses of the dial-up client must not conflict with the intra-network IP

address.

Figure 1-1 Setting IP address range for the dial-up client


10



8.6 Configuring Dial-up Client

8.6.1 Configuring IP Address

When you activate a dial-up connection, the dial-up server assigns an IP address to

the dial-up client automatically. Therefore, you should set Obtain an IP address

automatically on the dial-up client.

In the Windows operating system, set Obtain an IP address automatically as

follows:

214)Choose Start >Settings >Control Panel.


216)Right-click Local Area Connection, and select Properties to display Local Area

Connection Properties.

217)Select Internet Protocol (TCP/IP) and click Properties to display Internet

Protocol (TCP/IP) Properties.

218)Select Obtain an IP address automatically, as shown in Figure 1-1. Click OK.

Figure 1-1 Setting the IP address of the dial-up server


11



8.6.2 Configuring Network Connection

Configure the dial-up client as follows:

219)Choose Start > Settings > Network and Dial-up Connections >Make New

Connection to display New Connection Wizard, as shown in Figure 1-1.

220)Click Next, and the system displays a dialog box as shown in Figure 1-1.

Figure 1-1 Network Connection Type

221)Select Dial-up to private network, and then click Next to display a dialog box

as shown in Figure 1-1.


12



Figure 1-1 Phone Number to Dial

222)Enter the telephone number to dial, namely, the number the dial-up server is

connected to, and then click Next to display a dialog box as shown in Figure 1-1.

Figure 1-1 Connection Availability


13



223)Select Only for myself, and then click Next to display a dialog box as shown in

Figure 1-1.

Figure 1-1 New Connection Wizard complete

224)Enter a name for the connection, and then click Finish to complete configuring

the dial-up client.

8.7 Checking Dial-up Connection

Activate the configured dial-up connection, and check it as follows:

225)On the client, choose Start > Settings > Network and Dial-up Connections,

and double-click the configured connection to display a dialog box as shown in

Figure 1-1.


14



Figure 1-1 Setting dial-up connection properties

226)Enter the username and password for the dial-up connection. Use the username

and password set on the dial-up server. For details, see 8.5.2 205) ”Select an

existing user or the user with a new dial-up connection.”.

227)Enter the phone number to dial, namely, the number the dial-up server is

connected to.

228)Click Dial to activate the network connection.

If the connection is activated successfully, the commissioning of the dial-up server is

complete. In this case, an icon is displayed in the status area in the toolbar to indicate

the connection status.

Otherwise, check the settings made on the dial-up server and client, especially the IP

address of the dial-up server, the user information and the telephone number.

If the connection has still failed, the problem may be that the dial-in function of the

Modem is not activated. See 8.8 “Activating Modem Dial-in” to activate the dial-in

function, and then check the connection again as described earlier in this document.

229)On the dial-up client, execute the M2000 client application. Enter the user name,

the corresponding password and the IP address of the M2000 server to log in to

the M2000 server.

If you log in successfully, the client is connected to the M2000 server, and the

topology is displayed on the client.

If you fail to log in, check if the server is working well.


15



8.8 Activating Modem Dial-in

The dial-in function of the Modem is activated by default when delivered from the

factory. However, some manufacturers do not to activate this function in consideration

of security. In this case, the dial-up connection does not work.

After installing the Modem and checking all the system settings, activate the dial-in

function as follows:

230)Choose Start > Programs > Accessories > Communications >

HyperTerminal on the dial-up server. Enter a name for the connection, and set

the properties.

231)Execute the following command on HyperTerminal to activate the dial-in function

of the Modem:

aat

The system prompts OK.

232)Execute the following command to set the ring back tone.

ats0=X

X indicates dialing in after how many ring back tones are heard. For example, ats0=5

means to dial in after five ring back tones are heard.

The system prompts OK.

233)Execute the following command to save the settings.

at&w0

The system prompts OK, and the setting is complete.


16

01- m2000 commissioning guide

Documents