Proteína Queratina

Check with the following methods to judge the user service interruption caused by abnormal transmission:

1. On OMC unified UMS client, check the status of the transmission links, such as NCP, CCP, ALCAP, MTP3B links, association and see whether it fails.

2. On OMC unified UMS client, check whether there is any resource alarm for the cell public transmission channel, No.7 link, NCP, CCP, and association. Check whether the alarm exists constantly and cannot recover.

3. In the case of ATM transmission mode, check the optical interface SD and E1 indicator of the interface board, to judge the transmission line for normality.

a. For APBE, check the optical interface SD. The indicator is solid on during the normal communication. Otherwise, there may be faults with the optical fiber.

b. For DTA, check and make sure that the E1 indicator is slowly flashing (1 time/s) during the normal communication; otherwise, there might be something wrong with the E1 connection.

c. For DTT, check and make sure that the E1 indicator is slowly flashing (1 time/s) during the normal communication. Otherwise, there may be faults on the connection. For example, solid on indicates E1 link configuration but blocked.

4. In the case of IP transmission mode, check GIPI, GIPI3, and DMP.

DMP is to deal with the system signaling processing data. GIPI4 provides ZXWR RNC external IP interface. When the fault occurs on GIPI, the communication between ZXWR RNC and other elements disconnects.

Check with the following methods to judge the working status between GIPI4, GIPI3, and DMP.

a. Check RUN on the panel. When the communication is normal, RUN is flashing slowly (one/1 s). If it is abnormal, check whether the IP cable connection is normal first, and then check to see if there is any failure alarm about the port on the GIPI4.

b. Check whether ALM on the panel is ON.

c. Query whether GIPI4/DMP CPU occupation ratio reaches 100% on the cabinet diagram on Equipment Resource Management of NMS.

Proposals to handling the link resource faults:

1. Check whether the data to be negotiated by such external NEs as Node B, CN and ZXWR RNC are consistent (such as NCP, CCP, MTP3B link, ATM address, and IP address). If there is any abnormal configuration data, the cause may be local NE or other NEs have modified the configuration data. Make confirmation and modify them.

2. If there is not abnormality, perform the self-loop on optical interface or IMA group at ZXWR RNC side.

3. If the conditions allow (for example, the distance between NEs is very small), perform the self-loop at the corresponding remote NE according to link fault location. For example, for Iub link, perform the self-loop on the optical interface of the interface board at Node B side. For Iu interface, perform the self-loop on the optical interface of the interface board at CN side.

4. If the fault disappears after the local self-loop, the cause may be the abnormal running of the peer NE. If the peer NE becomes normal after the self-loop, the cause is transmission network configuration fault.

5. If the fault still exists after the self-loop, check the optical fiber for damages and exposing. 6. For IP network, when all equipment is running normally, if the global services disconnect,

the maintenance personnel should examine whether IP network is running normally first. a. Check the association status in NM configuration management. If the association is

not in service status, recreate the association. If the creation fails, connect the cable from the interface to the debugging machine. Set the IP address of the debugging machine as the local interface IP address and check the IP network through PINGing the peer interface IP address.

b. In the performance counter, check the office IP link type QoS statistics. Know the accessibility of the peer IP address according to the packet loss rate.

c. With the dedicated instrument or software, test the transmission delay, error bit rate, jitter of the IP network, confirming whether such faults as network blocking, network thunderstorm, and virus attack, occur in the IP network.

7. If the problems fail to be solved with all above methods, launch the emergency aid, or reset the interface board.

8.3.2.1 Methods for Handling Transmission Alarms

l Determine the fault type through comparison

When the alarm exists on some interface boards, if allowed, change the boards or connect cables to determine whether the alarm is related to the board or office.

l Locate the fault through loopback

OMCR test management interface provides different loopback settings for the interface board, including line loopback of optical path, test loopback of optical path, line loopback of optical path at the system side, line loopback of E1, and test loopback of E1.

8.3.2.2 Causes for Transmission Alarms l LOS, LOF

The cause may be that the REG device directly connecting the interface board is faulty or the pigtail/flange between the local-end ODF and the equipment is faulty. AU-AIS, AU-LOP, HP-UNEQ, HP-PLM

The cause is that the SDH transport network does not enable/configure the higher order path.

l TU-AIS, TU-LOP, LP-UNEQ, LP-PLM

The cause is that the lower order path is not established in SDH transport network or the DXC configuration does not meet the requirement of networking.

l E1-AIS, E1-LOF

The cause is the connection fault between the opposite exchange and the SDH transport device, such as, E1 cable connection fault.

l RS-TIM,HP-TIM,LP-TIM

The cause is that the values of local J0, J1, and J2 are inconsistent with the configurations of SDH transport device. Alarms of these three types do not affect the services.

To eliminate the alarms, obtain the values of J0, J1, and J2 related to the transport device through the query opposite configuration and then modify the values in the database.

l RS-FERF, HP-FERF, LP-RDI, E1-RAI

Check whether there are near-end alarms on the corresponding layer first. If there are, eliminate the near-end alarms on the opposite, eliminate them first.

Specially, for E1-RAI alarms, contact the maintenance personnel of the opposite exchange to confirm whether the E1 frame format is same as the local end. E1-SLIP

If E1–SLIP occurs when the board is running normally, the cause is the clock fault.