139223420 maintenance experience issue265 microwave products 385821

PrefaceMaintenance ExperienceEditorial Committee

Maintenance ExperienceNewsroom

Address:No. 55 , H i - t ech Road Sou th ,

ShenZhen, P.R.China

Post code: 518057

Contact: Ning Jiating

Tel: +86-755-26776049

Fax: +86-755-26772236

Document support Email: [email protected]

Technical support website: http://ensupport.zte.

com.cn

Maintenance Experience Editorial CommitteeZTE CorporationSeptember 2011

In pursuit of the idea “First-class service, Customer service”, and in order to make more profits and provide better services for our customers, we have edited Maintenance Experience (Issue 265) for microwave products of ZTE, which includes 12 articles about maintenance cases.

With the wide application of microwave products of ZTE, routine maintenance, a major job of the technical maintenance personnel of operators, has become more and more important. This issue, which collects articles written by microwave technical personnel of ZTE, describes practical cases and corresponding solutions that are often met during the commissioning and maintenance procedure. We hope it will be helpful to your routine maintenance work.

For more articles of maintenance experience and related technical materials, please log in to ZTE technical support website http://ensupport.zte.com.cn.

If you have any requirement, question, or suggestion, please feel free to contact us. Your attention and support are greatly appreciated.

Maintenance ExperienceBimonthly for Microwave ProductsNo.15 Issue 265, September 2011

Director: Qiu Weizhao

Deputy Director: Huang Dabin

Editors:Fang Xi, Wang Zhaozheng, Xu Xinyong,

Xiao Shuqing, Zhang Jian, Zhang Jiebin,

Zhou Guifeng, Zhao Cen, Zhao Haitao,

Jiang Haijun, Xu Zhijun, Huang Ying, Ge Jun,

Dong Yemin, Dong Wenbin

Technical Senior Editors:Luo Liming, Chen Hui, Zhu Linlin

Executive Editor:Wang Zhao

ContentsZXMW S500 Microwave NE Is Displayed as Disconnected on NetNumen R31 Client .............................2

Incorrect Antenna Direction Causes Interruption .......................................................................................4

ZXMW SR10 S340 Layer-2 Switching Function and Ethernet Data Service Fault....................................5

NetNumen U31 Server Fails to Start Due to Change of IP Address .........................................................10

Link Disconnection due to Inconsistent Working Modes at Both Ends ......................................................13

ZXMW SR10 I200 Code Error ...................................................................................................................14

Migration of Microwave Network Element Management System ..............................................................15

Mismatching Soft Waveguide and Feeder Interface Leads to Water Entry ...............................................17

ZXMW NR8250 Site Interruption ...............................................................................................................18

ZXMW SR10 XPIC Function Failure .........................................................................................................19

NR8250 Multi-Directional Parameter Configuration ..................................................................................21

ZXMW SR10 S340 Allows Frequency Modification at Both Local and Remote Ends ...............................22

Maintenance Experience2

September 2011 Issue 265

⊙ Wan Tao / ZTE Corporation

ZXMW S500 Microwave NE Is Displayed as Disconnected on NetNumen R31 Client

SymptomsIn a Cell-C project, the NetNumen

R31 EMS fails to monitor four microwave

links, namely, 4041—4099, 4099—4113,

4099—4178, and 4099—8311, as shown

in Figure 1.

Analysis and TroubleshootingCheck the following items:

Whether the hardware connection is proper.

Whether the IDU version is correct.

Whether the equipment is powered on.

Whether the network cables are correctly made.

Whether the IP configuration is correct.

Whether the EMS port has faults.

Abstract: NetNumen R31 Network Element Management System (EMS), developed by

ZTE Corporation, manages and monitors microwave NEs. This article describes how to

handle the out-of-control fault of ZXMW S500 on the NetNumen R31.

Version: NetNumen R31

Figure 1. Equipment Connection

Microwave Products 3

www.zte.com.cn

Troubleshooting1. Check the historical alarms on the EMS and

find that there is no alarm for the four microwave

links. The circuits work normally. Also, BSC

engineers confirm that the BTS devices operate

properly. Therefore, the problem is not caused by

device power-down.

2. On the EMS server, use the Ping command

to test sites 4041 and 4099 and get responses.

The IP address of site 4011 is 192.168.20.45 and

that of 4099 is 192.168.20.177. This indicates that

sites 4041 and 4099 can be connected.

3. Manually synchronize the NE clock of site

4099. After the synchronization is completed, the

link 4041—4099 restores and can be monitored.

However, the other sites cannot be pinged through

and the synchronization fails.

4. Go to site 4099 and check the following

items:

Whether the EMS cab les are proper ly

connected as shown in Figure 2.

Whether the device IP conf igurat ion is

consistent with that of the EMS client.

Whether the network cables are correctly made.

The result shows that the network

cable between IDU (4099 4041) and

IDU (4099 4113) is faulty.

Make a new network cable and use

the Ping command to check the IP

addresses of the devices 4099 4113,

4009 4178, and 4099 8311. The ping

commands succeed.

5. Return to the equipment room and

synchronize the NEs out of control on the

EMS. The fault is removed.

SummaryThe out-of-control of microwave

NEs on EMS may be caused by many

reasons. If such a fault occurs, check

the EMS server first. If the problem

cannot be solved, go to the site and

check the network cable itself and the

cable connection, port connection, IP

configuration, and others. For ZXMW

S500, hot restart is also an effective

method. ■

Figure 2. Correct EMS Cable Connections



SymptomsIn a Cell-C project, two microwave

links have normal receiving level but are

disconnected.

AnalysisThe two microwave links are installed

at the same t ime and have normal

receiving level. This means that the two

microwave links can receive signals.

The link disconnection may be caused

by interference. Normal receiving level

indicates that the interference signal is

strong. Thus, the most probable reason is

that the antenna directions are incorrect.

Troubleshooting1. Power off the device at one end of

the first hop, and find that the receiving

level at the other end has no obvious

change.

2. Power off the device at one end of

the second hop, and find that the receiving

level at the other end also has no obvious

change. This indicates that the antenna

azimuth may be improper.

3. Check the antenna azimuth and

adjust the antennas, as shown in Figure 1.

The link restores normal.

Incorrect Antenna Direction Causes Interruption⊙ Feng Peixuan / ZTE Corporation

SummaryI f t w o o r m o r e m i c r o w a v e h o p s a r e

commissioned on site and the antenna azimuths

are close with each other, antenna directions may

be incorrect. Therefore, when commissioning

each microwave hop, carefully check the azimuths

according to the design. ■

Version: ZXMW SR10 S200 V2.00 (6.6.2.0.0.22)

Keywords: Antenna azimuth, interference, antenna adjustment

Figure 1. Antenna Direction Diagram


www.zte.com.cn

SymptomsAs an extension of optical transmission,

microwave transmission connects a remote site

to an optical node. Exchange of data between the

remote site and the optical node is implemented by

S340 R2. In case that the RNC and UMTS Node B

are disconnected, troubleshoot the Ethernet service

between the optical node and Node B and find that

RNC cannot ping the Node B at site Torrijos Carter.

The topology graph from site Torrijos Carter to the

optical node San Miguelito is shown in Figure 1.

Table 1 describes the configuration.

ZXMW SR10 S340: Ethernet Data Service Fault over Layer-2 Switching Function⊙ Zhang Jinwu/ ZTE Corporation

Abstract: This article is about ZXMW SR10 S340 R2. It provides a reference for solving the

problem of Ethernet data service fault when data exchange is implemented through S340

layer-2 switching function, if the site has no switch.

Version: ZXMW SR10 S340 V2.00 (6.6.2.0.0.22-1)

EMS Version: NetNumen R31 V1.06.030c P0001

Keywords: 802.1ag, CCM message, MAID, MEP/MIP, Layer-2 switching function, ID

Access, Trunk

NodeBNAME VLANIDIP for UMTS FE MASK:255.255.255.240

GW IP for UMTS FE MASK:255.255.255.240

Torrijos Carter 127 10.221.84.126 10.221.84.116Villa Zaita 20 10.221.84.149 10.221.84.148CD Torrijos

Carter 24 10.221.84.215 10.221.84.212

Gonzalillo 2 291 10.221.84.231 10.221.84.228

Table 1. Node B VLAN Configuration Table of Optical Node San Miguelito

Figure 1. Topology Graph Between Faulty Site Gonzallilo 2 and Optical Node



Analysis1. On the RNC, ping the other three

sites, CD Torrijos Carter, Villa Zaita,

and Gonzalli lo2 on the same optical

transmission channel, and get response.

This indicates that the optical transmission

is normal.

2. Find a port not in service on the

Nodal of the optical node San Miguelito,

and set it to Access 127 port. Set the IP

address of the PC to 10.221.84.100/28

and connect it to the Access 127 port.

Ping IP address 10.221.84.123, and the

response times out. Ping IP address

10.221.84.116 of VLAN 291 gateway and

get the response.

3. Log in and check the Ethernet port

configuration. Port 3 (connected with Node

B) of site Torrijos Carter is in Trunk Mode

(Allow VLAN 1, 127). Other related ports

all have VLAN 127 access. Thus, the

problem is located in the related ports or

BBU interface board.

TroubleshootingDetermine the working status of point-

to-point port. Use the 802.1ag layer-3

switch fault locating protocol on S340 and

troubleshoot as follows:

1. Log in to the IDU of optical node

San Miguelito. Choose Service OAM > MAID list. Click Add to add a new Maid

List, as shown in Figure 2. The VLAN ID of

point-to-point port must be consistent with

the level.

2. Log in to the IDU of site T Carter.

Choose Service OAM > MAID List. Click

Add to add a new Maid List, as shown in

Figure 3.

3. Log in to the IDU of optical node

San Miguelito. Choose Service OAM > MAID List. Click 3G FE T Carter Maid in

Figure 2. Adding a Maid List for Optical Node San Miguelito

Figure 3. Adding Local MEP@San Miguelito

Figure 4. Adding Local MEP@T Carter


www.zte.com.cn

Maid List, and click Add in Local MEP to add the local MEP, as shown in Figure 3.

Level: consistent with the Level in Maid List

VLAN ID: consistent with the VLAN ID in Maid List

Ethernet Port: The port to be tested. Port 3 of San Miguelito 3 is connected with optical

transmission ADM.

Local MEP ID: Allocated ID, unique in a Maid List. The range is 1-8191.

Direction: UP stream

Priority: The priorities of the local end and remote end must be the same.

4. Log in to the IDU of T-Carter. Choose Service OAM > MAID List. Click 3G FE T Carter Maid in Maid List, and click Add in Local MEP to add the local MEP, as shown in Figure 4.

5. Log in to the IDU of site San Miguelito. Choose Service OAM > MAID List. Click 3G FE T Carter Maid in Maid List, and click Add in Remote MEP to add the remote MEP, as shown in

Figure 5.

6. Log in to the IDU of site T Carter. Choose > MAID List. Click 3G FE T Carter Maid in Maid List, and click Add in Remote MEP to add the remote MEP, as shown in Figure 6.

Figure 5. Adding Remote MEP@San Miguelito

Figure 6. Adding Remote MEP@T Carter



7. Log in to the IDUs of San Miguelito

and T Carter respectively. Choose > MAID List. Click 3G FE T Carter Maid in Maid List. Select Enable for periodical CCM

message sending, and then click Apply,

as shown in Figure 7.

8. After step 7 is performed at the

Figure 7. Activating CMM Message Sending Function

both local and remote ends, choose Service OAM > MAID List. The two ports become normal in

Monitoring state in the path, as shown in Figure 8.

Alternatively, click the button shown in Figure 9

to ping the MAC address.

If the link and interface are normal, the ping

command succeeds, as shown in Figure 10.

Figure 8. 802.1ag Function in Monitoring State

Figure 9. Ping Remote MAC Address


www.zte.com.cn

SummaryCurrently, for ZXMW SR340 R2, the Ethernet

service and TDM service have corresponding

maintenance and diagnosis functions. The fault

can be located layer by layer till the root.

To solve similar faults, make use of the S340

R2 maintenance function by referring to the

transmission topology graph. The fault can be

located to the end point, that is, BBU. Notify Node

B engineers to replace the BBU interface board.

Then, the problem can be solved. ■

Figure 10. Result of Pinging Remote MAC Address



Oracle:

Enter the command for starting the database listener.

SymptomsA NetNumen U31 server works

normally after installation. The customer requires modifying the host name and domain name. After the server IP address is changed, the NetNumen U31 fails to start.

Analysis1. Check the database connection. S t a r t t h e U 3 1 c o n f i g u r a t i o n

management platform under directory /uif. Run the following commands:

The dialog box shown in Figure 1 appears.

Select Database Configuration > Database Connection Configuration. In the right pane, enter the new IP address in the Database IP or hostname field. Click Test DB Connection. The following dialog box pops up, as shown in Figure 2.

This indicates that the database connection fails.

2. Check the database listener. Right-click in the blank area of the

desktop and select Open Terminal from

⊙ Wang Liang / ZTE Corporation

NetNumen U31 Server Fails to Start Due to Change of IP Address

the shortcut menu. The command line interface is opened.

Run the following command to switch to user

Abstract: This article describes how to solve the problem of NetNumen U31 startup failure due

to change of server IP address.

Version: ZXMW NR10 8250 (1.00.0001), ZXMW NetNumen U31 V12.10.010d

Keywords: Change server IP address, fail to start

bash-3.00# cd U31R58/EMS\

(030dP003\)/uif/

bash-3.00# ./runPlugCenter.sh

# su oracle

bash-3.00$ lsnrctl start

Figure 1. UEP’s DB Config Dialog Box

Figure 2. Message Box


www.zte.com.cn

The system output is as follows:

L S N R C T L f o r S o l a r i s : V e r s i o n

10.2.0.1.0 - Production on 20-JUN-2011

10:08:10

Copyright (c) 1991, 2005, Oracle. All

rights reserved.

Starting /oracle/u01/app/oracle/

product/10g/bin/tnslsnr:please wait...

T N S L S N R f o r S o l a r i s : V e r s i o n

10.2.0.1.0 - Production

System parameter file is /oracle/u01/

app/oracle/product/10g/network/admin/

listener.ora

Log messages written to /oracle/u01/

app/oracle/product/10g/network/log/

listener.log

Listening on: (DESCRIPTION=(ADDRESS=(P

ROTOCOL=ipc)(KEY=EXTPROC1)))

Error listening on: (DESCRIPTION=(ADDR

ESS=(PROTOCOL=TCP)(HOST=10.128.154.146

)(PORT=1521)))

TNS-12545: Connect failed because

target host or object does not exist

TNS-12560: TNS:protocol adapter error

TNS-00515: Connect failed because

target host or object does not exist

Solaris Error: 126: Cannot assign

requested address

Listener failed to start. See the

error message(s) above...

The system output shows that the listener fails to start. The reason is that the target host or object does not exist, as the messages in red shows.

The messages in blue shows that the IP address for connecting the database listener is: HOST=10.128.154.146, which is different from the modified IP address 10.128.154.145. Therefore, the oracle listener needs to be modified.

3. Modify the listener program.Under directory /oracle/u01/app/

oracle/product/10g/network/admin, find files listener.ora and tnsnames.ora, and double-click them. As shown in Figure 3, change the HOST value to the new IP address of the server.

Save the f i le and exit . Enter the following command:

The system output is as follows:

Figure 3. Modifying Listener IP Address

$ lsnrctl start

LSNRCTL for Solaris: Version

10.2.0.1.0 - Production on

20-JUN-2011 11:26:55

Copyright (c) 1991, 2005,

Oracle. All rights reserved.

Starting /oracle/u01/app/

o r a c l e / p r o d u c t / 1 0 g / b i n /



tnslsnr: please wait...

TNSLSNR for Solaris: Version

10.2.0.1.0 - Production

System parameter file is /

oracle/u01/app/oracle/product/

10g/network/admin/listener.ora

Log messages written to /


10g/network/log/listener.log

Listening on: (DESCRIPTION=(AD

DRESS=(PROTOCOL=ipc)(KEY=EXTPR

OC1)))

Listening on: (DESCRIPTION=(AD

DRESS=(PROTOCOL=tcp)(HOST=10.1

28.154.145)(PORT=1521)))

Connecting to (DESCRIPTION=(AD

DRESS=(PROTOCOL=IPC)(KEY=EXTPR

OC1)))

STATUS of the LISTENER

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

Alias LISTENER

Version TNSLSNR for Solaris:

Version 10.2.0.1.0 - Production

Start Date 20-JUN-2011 11:26:55

Uptime 0 days 0 hr. 0 min. 0

sec

Trace Level off

Security ON: Local OS

Authentication

SNMP OFF

Listener Parameter File /


10g/network/admin/listener.ora

Listener Log File /


10g/network/log/listener.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=ip

c)(KEY=EXTPROC1)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tc

p)(HOST=10.128.154.145)(PORT=1521)))

Services Summary...

S e r v i c e " P L S E x t P r o c " h a s 1

instance(s).

Instance "PLSExtProc", status

UNKNOWN, has 1 handler(s) for this

service...

The command completed successfully

The last message indicates that the listener

starts successfully.

Run the U31 configuration center again. After

the database connection test is conducted, the

dialog box shown in Figure 4 pops up:

This indicates that the U31 is connected with

the database. Because the network service name

is not created, database backup and restoration

cannot be implemented.

4. Create the network service name.

After that, the U31 can normally back up and

restore data.

TroubleshootingThis fault is removed after the HOST value

in the listener.ora file under directory /oracle/u01/app/oracle/product/10g/network/admin is

modified.

SummaryAf ter a server IP address is changed,

c o r r e s p o n d i n g m o d i f i c a t i o n s s h o u l d b e

implemented on the database. ■

Figure 4. Message Box


www.zte.com.cn

SymptomsDuring the debugging of a one-hop 8250

device, it is found that the receiving levels of both

ends are normal, but one end cannot access the

peer end after being closed. The background

noise is normal and the IP addresses are within

the same network segment. After E1 loopback is

implemented, the background has no available

path.

Analysis and Troubleshooting1. Check the receiving level, and find that the

value is normal.

2. The device has no alarm.

3. No interference is detected.

4. Check the microwave configuration and find

Link Disconnection due to Inconsistent Working Modes at Both Ends

⊙ Liu Wo / ZTE Corporation

that the working modes at both ends are

different. One is 4E1+14M+16QAM and

the other is 8E1+14M+16QAM.

5. Modify the configurations at both

ends. The problem is solved.

SummaryFor NR8250, the device may not

access the peer end even through the

receiving level is normal. Also the E1

loopback may be faulty. Therefore, the

configuration consistency is important.

Ensure that the configurations are correct

on the operation interface. ■

Abstract: In an Indoset project, the microwave link is connected and the receiving level is

normal. After E1 loopback is performed, the link is disconnected due to inconsistent working

modes at both ends.

Version: ZXMW NR8250 V2.00

Keywords: Receiving level, link disconnection



SymptomAfter a device is installed, the receiving

levels are normal, which are -36 dBm

and -38 dBm respectively at both ends.

However, there are error codes with 10-8

at one end and 10-6 to 10-8 at the other

end.

AnalysisThe problem of code error with normal

receiving level is generally caused by

interference. However, frequency scanning

has been implemented before installation.

The frequency points to be used are

designed according to the scanning result,

and serious interference should not have

occurred.

Different from other devices, I200

allows clock configuration. If the clocks of

the microwave devices on the same hop

⊙ Liu Lei / ZTE Corporation

ZXMW SR10 I200 Code Error

are not synchronized, code errors may occur.

TroubleshootingCheck the clock configuration of the microwave

device and find that both ends are set to Master

and the clocks are not locked. Change the remote

IDU to Slave mode, refresh, and lock the clock.

Check the Metering and find that code error does

not appear any longer.

SummaryI200 has many differences with other devices.

Pay special attention during configuration and

inspection. Clock configuration is easy to be

ignored during on-site configuration. If the

clock is not locked, code error may occur and

communication quality is affected. Therefore, in

case that code error occurs on I200, check the

clock configuration first. ■

Version: ZXMW SR10 I200

Keyword: Error Code


www.zte.com.cn

SymptomsThe database of a microwave EMS server is

installed on partition C. With the accumulation of

database files, this partition (10 G capacity) has no

sufficient space to save the database. In this case,

the database should be migrated.

Figure 1 shows that partition C has only 130 M

space available.

⊙ Liu Lei / ZTE Corporation

Migration of Microwave Network Element Management System

AnalysisThe NetNumen R31 system is installed

on partition C during installation. With

the increase of data in the database, the

remaining space of partition C is reduced

and partition C may be totally occupied.

To solve this problem, try the following

methods:

Abstract: This article describes how to migrate a database to another hard disk when the

hard disk of the microwave EMS server reaches the limit.

Version: ZXMW SR10 S200, ZXMW PR10 S400/500

EMS Version: R31V1.06.030cP001

Keywords: Database, Migration

Figure 1. Disk C Usage



1. Periodically clean the database

and delete the obsolete data. This method

cannot fundamentally solve the problem.

2. Remove the database from the

server and install the database on a hard

disk with a large capacity. This method

requires the backup of database files.

3. Migrate the database.

TroubleshootingThe procedure for migrat ing the

database is as follows:

1. Log in to the EMS database as user

sa.

2. Split the database. Do as follows:

In the database directory, right-click

folder UEP_CAF_FM and select Task > Split. Perform the same operation on

folders uep and UEP_PM.

3. Find the three files under the database

installation directory on partition C. Cut them to a

new location, for example, partition E.

4. Add the database files. Do as follows:

Log in to the database again. Right-click

Database and select Add to open the Add dialog

box.

5. Add the newly saved database f i les

(UEP_CAF-FM, uep, and UEP_PM). After the files

are added completely, close the database.

6. Start the NetNumen R31 server and client,

and they operate properly. This indicates that

database files are successfully saved on partition E.

SummaryThe EMS software can be installed on partition

C. However, it is not recommended to install the

database on partition C either. ■


www.zte.com.cn

SymptomsThe connection surfaces of the waveguide

and the antenna feeder interface are bare

without waterproof rings. This may lead to water

penetration into the antenna feeder due to the

aging of protection layer of the clue or tape. As a

result, microwave link may be disconnected.

AnalysisThe contact surface of the two waveguide

interfaces has no waterproof ring during installation

and the equipment is commissioned. If no measure

is taken, future maintenance will cost large work

effort. As time elapses, aged clue or tape fails

to prevent water entry into the feed. As a result,

magnetic power is accumulated and cannot be

sent out through the antenna and thus the link

is disconnected. The fault is caused by incorrect

waveguide model standard configuration, as shown

in Figure 1.

TroubleshootingBecause the equ ipment ins ta l la t ion is

completed, it is recommended to use a round-

rectangle waveguide convertor. Figure 2 shows

the solution for antenna and soft waveguide

connection.

SummaryThis problem is caused by configuration error

Mismatching Soft Waveguide and Feeder Interface Leads to Water Entry⊙ Wen Daming / ZTE Corporation

or manufacturer negligence. The result

is transmission interruption and frequent

alarms about network service failure. ■

Version: ZXMW SR10 S340 V

Keywords: Waveguide, configuration, link disconnection

Figure 1. No Waterproof Ring Between Antenna Waveguide and Software Waveguide

Figure 2. Antenna and ODU Connection



SymptomsDuring the installation phase of a

microwave project, the microwave link

is interrupted a second time after being

restored from an interruption half a month

before.

AnalysisTo solve the problem, the following

measures are taken:

1. Go to the site and check the IDU

voltage. It is found that the voltage is

normal.

2. Check the IF cable connectors and

the waterproofing effect. It is found no

connector is loose and no feeder or device

has water.

3. Check the IDU running logs. It is

found that the IDU was cold restarted for

multiple times that day.

⊙ Li Changguo / ZTE Corporation

ZXMW NR8250 Service Interruption

4. Analyze the running logs and historical

alarms, and determine that the problem is caused

by the power supply rather than the IDU hardware.

5. Ask the customer to check the power supply

equipment, which uses an Emerson power cabinet.

The customer feeds back that the power is normal.

6. Check the history records of the related BTS

and find multiple voltage alarms, which are -48V

alarm (198092550) and -44V alarm (198092551).

This proves the existence of voltage fluctuation.

TroubleshootingAsk the customer to check the power cabinet

and solve the unstable voltage problem.

SummaryIn most cases, cold restart of site equipment is

caused by power supply problems, such as power

failure and unstable voltage. ■

Abstract: During the commissioning phase of a microwave project, the microwave link is

interrupted twice a month, thus causing service failures at six sites. The investigation shows

that the problem is caused by frequent restarting of IDU.

Version: ZXMW NR8250 (1.00.000j)

Keyword: Service Interruption


www.zte.com.cn

SymptomsA ZXMW SR10 S300 microwave device is

used in a project. The site ID is re5007-52101. The

device configuration is 7G 2*STM-1 HSB 2m. The

receiving level is normal during the commissioning.

However, the XPIC function cannot be implemented

and alarms are generated, as shown in Figure 1.

Analysis and Troubleshooting1. Check the receiving level of re5007 and

522101 and find the value is -32 dBm. This

indicates that the software configuration is correct.

2. Check the XPIC cables of ODU and find that

that the XPIC cables are all correctly connected.

3. Check the IF cable connection, which is

comparatively complicated and easy to cause

exceptions:

Connection of re5007 IF cables:The two IDM modules on the r ight are

connected to a vertically-polarized ODU.

ZXMW SR10 XPIC Function Failure⊙ Chen Haiping / ZTE Corporation

The two IDM modules on the left are

connected to a horizontally-polarized

ODU.

The two IDM modules on the right are

connected to a horizontally-polarized

ODU.

The two IDU modules on the left are

connected to a vertically-polarized

ODU.

To implement the XPIC function for an

S300 device, in the two IDUs of a one-

hop device, the IDM modules with the

same slot number must use the same IF

connection mode.

Therefore, adjust the IF connection of

522101 to be the same as that of re5007.

Check and ensure that the receiving level

meets the design requirement, that is, -32

dBm. Then, enable the XPIC function. No

Abstract: This article describes how to solve the problem of XPIC function failure for ZXMW

SR10.

Version: S300 (idc_swr_4.95s20)

Keyword: XPIC

Figure 1. Alarms

Connection of 522101 IF cables:



alarm is raised. Figure 2 shows the device connection.

SummaryIf the XPIC function cannot be implemented, check the XPIC cable connection first. Then,

check whether the IF cables with the same slot number are connected in the same way. ■

Figure 2. Device Connection


www.zte.com.cn

SymptomsThe configuration of ZXMW NR8250 multi-

directional parameters requires the configuration of link KACUNG-KELAPA as shown in Figure 1. During the configuration of KACUNG parameters, it is found that the frequency cannot be entered.

Analysis and TroubleshootingThe hardware installation is completed. Site

KACUNG has two directions. Configure the parameters for the direction from KACUNG to KELAPA:

1. Ask the local engineers and confirm that the configured frequency is correct.

De te rm ine t he ODU f requency range displayed on the radio link interface, which is 7285500¬7355500 kHz.

Check the parameter configuration table and find that the frequency of KACUNG in the direction to KELAPA is 7408000 kHz. It is in H sub-band and beyond the detected ODU frequency range.

Therefore, the problem is caused by ODU type.2. Check the shipment DO. It is found that the

shipment DO is correct and the configuration in this direction is ODU of H sub-band indeed. Check the shipment records and no mistake is found.

As the site KACUNG has two directions, it is doubted that the direction is incorrect. Check the parameters from KACUNG to the other site SIMPANG_IBUL, and find that the frequency of KACUNG in this direction is 7317000 kHz, in G sub-band. This value is within the ODU frequency range displayed on the interface.

NR8250 Multi-Directional Parameter Configuration⊙ He Fengchao / ZTE Corporation

Notify the local employees to ask the distributor to check the cable connection. The result shows that the connection and antenna azimuth are correct, but the IF cable is connected to an ODU in another direction. After the direction is corrected, the parameter becomes configurable.

SummaryNR8250 parameter configuration is

simple. If exceptions occur, first make sure that the parameters are correct. Then, check that the software configuration and hardware connection related to this parameter are completed. In this instance, only hardware model is related to ODU frequency. Therefore, check the hardware, such as cable connection and ODU model, and solve the detected problem. ■

Version: ZXMW NR8250 (1.00.000j)

Keywords: Multi-directional parameter configuration

Figure 1. Networking Diagram



SymptomAn on-site engineer modif ies the

frequency at the local site, but forgets the

original frequency. As a result, the link

is down and cannot be restored within a

short period. To solve the problem, the

engineer has to go to the remote site to

modify the frequency.

Analysis and TroubleshootingMisoperation by on-site engineers

cannot be completely avoided during

implementation of a large project. For

S340 provides a new function to prevent

such a problem. As shown in Figure 1, a

new option “Set also remote unit” is added

to the frequency configuration dialog

⊙ Pu Suqin / ZTE Corporation

ZXMW SR10 S340 Allows Frequency Modification at Both Local and Remote Ends

box in the new version. If this option is selected,

the frequency at the remote end is also modified

at the same the time when the frequency of this

hop is modified. This avoids site down due to

misoperation.

SummaryThis function is practical but always lacks

of attention from on-site engineers. A better

application of this function can reduce operation

risks and costs. ■

Abstract: Frequency modification at the local and remote ends of a link is quite common

during actual commissioning and maintenance. Any misoperation, for example, when

determining the existence of frequency interference and preventing frequency interference,

may cause the link down. In addition, engineers have to go to the both sites to solve

problems. The new version of S340 supports frequency modification at both ends, avoiding

the risk of manual operation mistakes.

Version: ZXMW SR10 S340 V2.00 (6.6.2.0.0.22)

Keywords: Frequency modification at both ends

Figure 1. Frequency Setting Dialog Box in New S340 Version

139223420 maintenance experience issue265 microwave products 385821

Documents

maintenance cases

maintenance experience

maintenance procedure

routine maintenance

microwave productsno

customer service

related technical materials

document support email