ZXG10 iBSCBase Station Controller Emergency Maintenance Version: V6.20.71 ZTE CORPORATION NO. 55, Hi-tech Road South, ShenZhen, P.R.China Postcode: 518057 Tel: +86-755-26771900 Fax: +86-755-26770801 URL: http://ensupport.zte.com.cn E-mail:
[email protected] LEGAL INFORMATION Copyright © 2011 ZTE CORPORATION. The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations. All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION or of their respective owners. This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein. ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION. Revision History Revision No. Revision Date Revision Reason R1.1 2011-09-30 Updated to V6.20.711C R1.0 2011-07-14 First Edition Serial Number: SJ-20110531095035-006 Publishing Date: 2011-09-30(R1.1) Contents About This Manual ......................................................................................... I Chapter 1 Overview of Emergency Maintenance .................................... 1-1 1.1 Scope of Emergency Maintenance ...................................................................... 1-1 1.2 Guide Concept of Emergency Maintenance ......................................................... 1-3 1.3 Flow of Emergency Maintenance......................................................................... 1-3 1.3.1 Determine the fault scope ......................................................................... 1-4 1.3.2 Locate fault reason and record exceptions ................................................. 1-5 1.3.3 Fault Analysis .......................................................................................... 1-5 1.3.4 Critical solution......................................................................................... 1-5 1.3.5 Restore service ........................................................................................ 1-6 1.3.6 Observe restored services ........................................................................ 1-6 1.3.7 Feedback information about emergency maintenance ................................ 1-6 1.3.8 Communication with customer .................................................................. 1-6 1.4 Precautions of Emergency Maintenance .............................................................. 1-6 1.5 Contact Information of Technical Support from ZTE .............................................. 1-6 Chapter 2 Preparation of Emergency Maintenance ................................ 2-1 2.1 Daily Preparation of Emergency Maintenance ...................................................... 2-1 2.1.1 Data Backup and System Inspection ......................................................... 2-1 2.1.2 Establish Remote Maintenance Station...................................................... 2-3 2.1.3 Preparation of important spare parts.......................................................... 2-3 2.2 Holiday Preparation of Emergency Maintenance .................................................. 2-3 2.2.1 Load Monitoring ....................................................................................... 2-3 2.2.2 Load reduction measures.......................................................................... 2-4 Chapter 3 Guide of Emergency Maintenance .......................................... 3-1 3.1 Maintenance Guide about Major Alarm ................................................................ 3-1 3.1.1 Board Alarm............................................................................................. 3-1 3.1.2 Clock alarm.............................................................................................. 3-3 3.1.3 Alarms related with interface A .................................................................. 3-4 3.1.4 Alarms on flow control .............................................................................. 3-5 3.1.5 Transmission alarms ................................................................................ 3-6 3.2 Maintenance Guide about NM Faults ................................................................... 3-7 3.2.1 Can't login NM system .............................................................................. 3-7 3.2.2 Disconnection between OMM and NM servers ........................................... 3-8 I .....................8 Get tracing signal at interface A................3.... 3-9 3....................... 3-10 3......... 3-13 Chapter 4 Fault Feedback Information .3...............................3 Disconnection between equipment and OMM server ..................................... 4-9 4.........................9 Query dynamic data at interface A..................3....................................................2..4.........................16 Query disk space... 4-17 4............................................................... 3-8 3................. 4-1 4...................................1 Mass user can't use GPRS service.......1 Get device printing file ...3........................18 Get NM profile..........1 Mass users can't call normally.........4 Maintenance Guide about PS Service Faults.....3...................................3.......................3 Get data backup ztd file from OMM ........................3-11 3.4..............................3........................... 4-1 4....19 Get operation log at client ............................................. 4-26 4.............................2 Feedback Data That Shall be Recorded.. 4-30 4....... 3-12 3............................................. 3-9 3............................................15 Check whether overstocked data exists .................3 Maintenance Guide about CS Service Faults ...........................................2 All sites under BSC can't call normally ........................... 4-28 4.... 4-13 4......................3........ 4-29 4........................................3 All sites under certain module in BSC can't call normally.................. 4-3 4..3..3....3......................3-11 3.........4 All sites under certain 100M/GB resource frame can't call normally... 4-23 4......................3.. 4-28 4......... 4-8 4..................................................................................................13 Query BVC and NSVC state... 4-6 4...........3. 4-32 II ............................................................1 Prerequisite of fault feedback ....12 Trace PS service signal .3................................................3...........3........ 4-6 4........ 4-20 4................................3.......................5 Get alarm file .............................................................................................11 Query dynamic data at site ............................................................................3..............................................3 The method to get system record ................................. 3-12 3. 3-12 3.....20 View system time zone ....5 All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call normally ..............................................3............3............................. 4-28 4. 4-24 4.............3....................................4 Get software setting ...................................3.................................................................................17 Get NM printing file.......................6 All sites under certain LAPD/LAPD2 can't call normally... 3-13 3.. 4-6 4.........7 Get 1 hour's performance data before and after fault ....................................... 3-9 3............3..7 Mass users belonging to other type can't call normally ...............4.........................................10 Get tracing signal at interface Abis........................... 4-8 4....3..2 All users under whole BSC can't use GPRS service ...................3............3-11 3..............................3........................................6 fanGet notification file ............ 4-30 4..........2 Get ZDB file .3 Some cells can't use GPRS service.............3..................................14 Get operation log of preset machine . 4-26 4.................. 4-30 4............................3...................... ...........................................22 Maintenance Record List ......................................................... 4-32 Figures............................................................................. I Tables ....................................................V III .......................... 4-32 4.................3.................4...................... III Glossary ............................................................................................21 View NM version ...............................................3............................. IV . I . Chapter 2 Preparation of Describes preparation of ZXG10 iBSC emergency maintenance. including the preparation. Emergency Maintenance Chapter 3 Guide of Describes guideline of ZXG10 iBSC emergency maintenance on Emergency Maintenance different faults. typical emergency maintenance case and fault feedback information.About This Manual Purpose This manual introduce the process of ZXG10 iBSC emergency maintenance. guideline. and process of ZXG10 iBSC Emergency Maintenance emergency maintenance. Intended Audience l l System engineer Maintenance engineer What Is in This Manual This manual contains the following chapters: Chapter Description Chapter 1 Overview of Describes applicable scope. Chapter 4 Fault Feedback Describes the methods to send fault feedback and get system log of Information ZXG10 iBSC emergency maintenance. II . ........1-6 1................ Table 1-1 User complaint Complaint content Description After receiving user complaints............. you shall fur- l Lots of speech user can't access................................ 1....................................................................................... ment result...... Alarm inspection Table 1-2 shows the alarm report that shall be viewed on emergency maintenance...1-3 Flow of Emergency Maintenance. ther check alarm information and KPI measure- l Lots of MS can't be acted as called/caller.............. you can confirm whether emergency maintenance shall be started through user complaint.....Chapter 1 Overview of Emergency Maintenance Table of Contents Scope of Emergency Maintenance . and performance report analysis.... to determine whether emergent l Lots of users can't use GPRS service fault occurs...........................1-6 Contact Information of Technical Support from ZTE....... 2........... alarm inspection................1) ZTE Proprietary and Confidential ...............1-1 Guide Concept of Emergency Maintenance........... Active board alarm in active/standby mode Board alarm Board alarm out of non-active/standby mode 1-1 SJ-20110531095035-006|2011-09-30(R1............................. Table 1-2 Alarm report on emergency maintenance Alarm Type Alarm Description Alarms on spare boards.... User complaint Table 1-1 shows user complaints about emergency maintenance......................................1-3 Precautions of Emergency Maintenance .1 Scope of Emergency Maintenance During system running.. such as OMP/OMP2 and CMP/CMP2........ you shall confirm whether emergency maintenance process shall be started. Table 1-3 KPI Indicator Indicator Type Indicator Name SDCCH Congestion rate TCH Congestion rate TCH traffic Congestion TCH availability TCH Assignment success rate Channel occupation Call success rate Changeover related Handover success rate Call drop TCH call drop rate 1-2 SJ-20110531095035-006|2011-09-30(R1. While starting emergency maintenance process under critical alarm and user complaint. and alarm analysis. Analyzing a performance report Normally. KPI indicator is not a direct condition to start emergency maintenance. Table 1-3 shows the important KPI indicators that shall be viewed and analyzed on emergency maintenance. KPI indicator shall be used as a subsidiary analysis tool and troubleshooting method.ZXG10 iBSC Emergency Maintenance Alarm Type Alarm Description Abnormal access clock Phase-locked loop out of lock Clock alarm Level 1 alarm on lost clock reference source Alarm on unreachable MTP3 office Alarms related with interface A SCCPSubsystem unavailable MSCOverload Congestion at signalling point Alarms on flow control CPUToo high load Loss of trunk frame Loss of trunk signal Relevant transmission alarms SDH/SONET: loss of signal 3. test.1) ZTE Proprietary and Confidential . in combination with user complaint. l l While KPI is changed exceptionally. see ZXG10 iBSC (V6.71) Base Station Controller Routine Maintenance. Figure 1-1 shows the flow of emergency maintenance. maintenance personnel shall keep calm. in the process of. so ZTE can provide better after-sale service for the operator. and log file to ZTE office for analysis and locating. When system or equipment encounters emergent faults. the operator shall periodically organize relevant managers and maintenance personnel for training and demonstration. 3. Prior to maintenance. along with historical fault analysis and experience. Relevant maintenance personnel shall learn more about the system in daily maintenance assignments. and to master common tools about data backup/restore. Before.3 Flow of Emergency Maintenance Emergency maintenance contains the following several steps: 1. especially to be familiar with common exceptional information about NM alarm and indicator conditions on BSC panel. or after emergency maintenance. see ZXG10 iBSC (V6. equipment alarm file. and then you shall prepare for emergent schedule.71) Base Station Controller Troubleshooting. Determine the fault scope. and send troubleshooting report. Restore service. Locate fault reason and record exceptions. 1-3 SJ-20110531095035-006|2011-09-30(R1.20. Fault analysis. you shall do troubleshooting according to emergent schedule or relevant process in referential manual. Feedback information about emergency maintenance. 8.1) ZTE Proprietary and Confidential . 1.Chapter 1 Overview of Emergency Maintenance 1. 7. maintenance personnel shall collect the alarm information about this fault. 2. 5. Critical solution. If yes. 6. 4.20.2 Guide Concept of Emergency Maintenance Emergency maintenance is suitable for the faults that shall be handled and restored immediately and have great influence on service. For more information on daily maintenance. l l l l l You shall firstly determine fault scope prior to maintenance. Communication with customer. you shall fully consider and follow below principles about emergency maintenance. Daily maintenance shall refer to ZXG10 iBSCand relevant equipment data. then check BSC hardware and transmission to determine whether the fault is caused by BSC. to do troubleshooting from inner to outer or from entire to local. For more information on normal troubleshooting. Observe restored services. 3.ZXG10 iBSC Emergency Maintenance Figure 1-1 Flow of Emergency Maintenance 1. 1-4 SJ-20110531095035-006|2011-09-30(R1.1 Determine the fault scope Determine fault scope based on three following aspects.1) ZTE Proprietary and Confidential . l Query relevant indicators in KPI to judge the affected site scope about the fault. Observe the information of equipment operation. Check the fault caused by BSS equipment or other reasons. if the problem is too complicated. 1. board indicator.3. The aim is to reduce and determine fault related equipment. Service faults often begin with user claims.2 Locate fault reason and record exceptions Pick up relevant data about alarm. If possible. so you shall register user number. technical expert remotely logins at problematic site and assists customer to solve problems through phone. ZTE will direclty appoint technical support engineer to the field for troubleshooting. and provide more accurate information on emergency maintenance.4 Critical solution Search for emergency help from ZTE customer support center. 2.3. (cellphone) 4008301118. l Determine whether it is global fault based on affected site. l Determine whether it is associated with module and special board based on based on affected site. Test arrangement. which provides 7*24 hours hotline service and remote technical support service.3. l If you can't determine the location of claiming user at BSC side. you shall search for help from CN side. and printing. 3. Remote support Based on the information provided by service hotline. and determine its involved scope. Field Technical Support Technical expert shall make emergency measures to restore normal communication as soon as possbile. or BTS that is claimed by user. BSC. l Use signaling trace and probe to find out CN.3 Fault Analysis If locating fault is caused by BSS equipment. 3.1) ZTE Proprietary and Confidential . and do troubleshooting after finding proper fault point. 1. Analyze the site for user based on different tools at BSC and CN sides. signal. arrange test at specific area. and analyze obvious phenomenon about network fault. performance. Determine fault scope through analysis of KPI indicator. 1. ZTE hotline service Customer support center hotline: (fixed line) 8008301118. 1.Chapter 1 Overview of Emergency Maintenance 1. you shall analyze field alarms. performance. and printing log. 1-5 SJ-20110531095035-006|2011-09-30(R1. to determine the influence scope of the fault. 2. and restarting. 1.1) ZTE Proprietary and Confidential . so we can timely and quickly find the fault location and solve it. l l You shall quickly find the fault location during emergency maintenance. resetting. 1.ZXG10 iBSC Emergency Maintenance 1. you shall restore system service as soon as possible. and arrange relevant persons to do test.3. If necessary.7 Feedback information about emergency maintenance After the service is restored. 1. l Mobile phone: 4008301118. Some restoration (such as board resetting) may have a great influence on system operation. ZTE mobile customer service department will submit fault analysis report to local office. and local office will communicate with customer about involved faults. you shall arrange some persons on duty within peak traffic period.4 Precautions of Emergency Maintenance Precautions of emergency maintenance are as follows. and signaling tracing data. If you can't timely find the reason. operation log. 1.3. to closely monitor network operation. If the fault has a great influence on network operation. 2.5 Restore service Find out fault reason and quickly restore normal service through remote or field ZTE technical support. you shall collect BSS network statistics report. based on feedback data on site. you shall solve it as soon as possible. 1. no matter whether maintenance personnel can solve it or not. Telephone at global ZTE customer service center l Fixed phone: 8008301118. you shall try to solve the problem through board switchover. if the problem occurs again. Local ZTE office 1-6 SJ-20110531095035-006|2011-09-30(R1.3. so it shall be performed by a experienced operator or under the guide from an operator with certain maintenance experience. they shall immediately contact ZTE customer service center or local ZTE office. If necessary.3. and send troubleshooting results to local ZTE customer service center. As such.6 Observe restored services After the service is restored. you shall confirm whether normal operation state has been restored. 1.8 Communication with customer For level 1 faults.5 Contact Information of Technical Support from ZTE Contact information of technical support from ZTE is as follows. ..1 Data Backup and System Inspection Maintenance personnel does data backup in daily maintenance.... They can restore configuration data during system faults.Chapter 2 Preparation of Emergency Maintenance Table of Contents Daily Preparation of Emergency Maintenance ...2-1 Holiday Preparation of Emergency Maintenance ... Select Management > Data Management > Data Backup...............1) ZTE Proprietary and Confidential .....1 Daily Preparation of Emergency Maintenance Daily preparation of emergency maintenance contain the following three contents: l l l Data Backup and System Inspection Establish Remote Maintenance Station Preparation of important spare parts 2. 2-1 SJ-20110531095035-006|2011-09-30(R1... Maintenance personnel can find significant faults and potential risks through daily system inspection....... Right-click the NE in physical view of topology management..... Configuration data can be manually or automatically backed-up.................1..2-3 2....... to enable the system restore normal service...... l OMM server Manual Backup 1........ 2... l Automatic Backup By default.. Path to save configuration data: /home/xxxxxxx/ums-svr/backup/sysmanager/cm....... Data Backup interface pops up...... 3.... the system backs-up OMM configuration data everyday....... select NE Management > Configuration Management in floating menu.. to call configuration management interface........... Data Backup Maintenance personnel shall backup daily data.... as shown in Figure 2-1.... 5. and click Ok button. configure save path and backup NE. Select NE.1) ZTE Proprietary and Confidential . Data Backup Result interface pops up. Figure 2-2 Data Backup Result Interface 2-2 SJ-20110531095035-006|2011-09-30(R1. Click Close button.ZXG10 iBSC Emergency Maintenance Figure 2-1 Data Backup Interface 4. as shown in Figure 2-2. If major alarm exists while checking historical alarms (within 1 week) and current alarms.1 Load Monitoring User shall monitor the load as follows.71) Base Station Controller Routine Maintenance.1. Query current BSC alarm Query the historical alarms within 24 hours at BSC Query the historical notifications within 24 hours at BSC Query important performance indicators at BSC Check the state at interface A Check the state at interface Gb View the active/standby status of the board. not just the specific holiday period.3 Preparation of important spare parts You shall prepare for sufficient spare parts for important boards on BSC.2 Holiday Preparation of Emergency Maintenance Preparation in holiday mainly aims the case of large traffic.2 Establish Remote Maintenance Station To guarantee quickly locate and solve the faults under the support of ZTE technicians. 2. If the alarms still continue. PSN. UIMU/GUIM/GUIM2. focusing on checking operation state at BSC and analyze performance indicator & historical alarms.2. Query BSC operation log Check the alarm box For system inspection. CHUB.1. 2. 2. CLKG/ICM. you shall handle it immediately. is : OMM Checking the system System inspection contains: l l l l l l l l l l l View board indicators Check communications link between the NMS and NE. 2-3 SJ-20110531095035-006|2011-09-30(R1. 2.Chapter 2 Preparation of Emergency Maintenance The directory for data backup server/home/xxxxxxx/ums-svr/backup/sysmanager. CMP/CMP2. PCAnyWhere or VPN remote access shall be always kept normal on different fields. You can contact local ZTE office while commissioning remote access.1) ZTE Proprietary and Confidential . and GLI/GLI4. you shall contact local ZTE office or customer service center.20. such as OMP/OMP2. refer to "Check Operation State at BSC" in ZXG10 iBSC (V6. UIMC. which shall be lower than 0. If more than this value. 10. If more than this value. view "the number of received SCTP packet". Total time occupied by UDPPort (hours) / available average number at UDP port. If it is classified. "the byte of received SCTP packet".2. you shall stop or close probe software.7 signaling links. you shall add more no. l Check whether SIM card for field mobile phones are classified according to specified requirements. Do your best to reduce the action of signaling trace during large traffic. Monitor the traffic at interface IPA on BSC.7 signaling link at interface A on BSC.1) ZTE Proprietary and Confidential . If more than this value. 2-4 SJ-20110531095035-006|2011-09-30(R1. "the number of transmitted SCTP packet". you shall add more circuits at interface A. Referential threshold is 70%. The protocol header in each packet has 48 bytes. l Check whether FUC flow control at BSC side is opened. If it is higher than this value. you can check whether system message about flow control at BSC side is opened. 7. l For individual site with large traffic. it is recommended to open handover for preprocessing. and that at each GB port is 700Mbps. Sum of SCTP coupling flow = (the byte of received SCTP packet + the byte of transmitted SCTP packet + (the number of received SCTP packet + the number of transmitted SCTP packet) * the bytes of protocol header in each packet)*8/ granularity of statistical report time. to reduce the influence on MP load. 2. The max flow at each 100M port is 80Mbps.4. you shall inform maintenance personnel as soon as possible.ZXG10 iBSC Emergency Maintenance 1. It is recommended to monitor load condition at CN side.8. Measures at BSC side. 4. you shall add more links at interface IPA. Monitor load value of service timeslot at interface A on BSC. Monitor the signaling load at interface IPA on BSC. The sum of received flow and the sum of transmitted flow at different ports shall be lower than 80% of general flow at IP port. Check the available average number of UDP ports and total time occupied by UDPPort in performance management. View daily CPU load on BSC at busy time in holiday. which shall be lower than 0. 6. Monitor the flow at interface IP A on BSC. During large traffic. 5. 3.2 Load reduction measures User can use the following measures to reduce load. CMP/CMP2 load at BSC can't exceed 70%. The ratio shall be lower than 0. to reduce CPU load. 8. 2. you shall add more links at interface IPA. Focus on CPU load on each board within whole monitoring period. If it is more than this value. 9. Monitor load value at no. and "the byte of transmitted SCTP packet" in performance counters of SCTP coupling measurement. Its sum of SCTP coupling flow is lower than general signaling flow of CMP/CMP2. Total signaling flow of CMP/CMP2 = 4Mbps* the number of CMP/CMP2. If the load at CN side is exceptional. 1. you shall add links at interface IPA.6 Erlang. Chapter 2 Preparation of Emergency Maintenance l l l Pause or delete unnecessary observation tasks. You shall check which BSC NE has the heaviest traffic. You can block some circuits at interface A for this BSC. l Too heavy load at switching device. 2. preventing from too high load leading to equipment degradation. 2-5 SJ-20110531095035-006|2011-09-30(R1. l Don't send lots of paging messages at the same time. l Temporarily modify two or more paging as one paging mode for CN. to reduce processing load at CN side. The one near or over upper limit shall be expanded timely. Pause or delete unnecessary measurement tasks. l Get working load about SCTP coupling at interface A. Get no.7 signaling link at interface A and working load at service timeslot.1) ZTE Proprietary and Confidential . Measures at CN side. The one near or over upper limit shall be expanded timely. l Timely start flow control function at CN side. 2-6 SJ-20110531095035-006|2011-09-30(R1.ZXG10 iBSC Emergency Maintenance This page intentionally left blank.1) ZTE Proprietary and Confidential . .3-9 Maintenance Guide about PS Service Faults.................... c.1 Active board alarm in active/standby mode 1..........1) ZTE Proprietary and Confidential ...................3-1 Maintenance Guide about NM Faults...... Symptoms The following alarms are found in real-time alarm for active board...... Replace relevant boards..1. Relevant transmission alarms..1............ go to step 3......... active/standby switchover happens............. 3-1 SJ-20110531095035-006|2011-09-30(R1....... reset active/standby board at the same time..........Chapter 3 Guide of Emergency Maintenance Table of Contents Maintenance Guide about Major Alarm.....1 Maintenance Guide about Major Alarm Maintenance guide about major alarm contains the following contents: l l l l l Board alarm..... Clock alarm.......... View board state after switchover......... b..... l 198005379 Board offline or CPU in long-term resetting state l 198005390 Wrong (CPU) sub-card position configured by database l 198066004 Communication blocked between module and OMP 2... View the working state of standby board...1 Board Alarm 3.................3-7 Maintenance Guide about CS Service Faults .............. d....................... If the fault also exits on standby board.....1.......... If the alarm continues on the active board after switchover. 3................. If the standby board is normal.................. Alarms on flow control.. Alarms related with interface A............ Troubleshooting steps: a.3-12 3.. to check whether the board is normal............... you shall plug/unplug the board again. Check whether micro switch (ENUM) of the board is opened. ALM. you can reset it by manually plugging/unplugging the board.1. Symptoms The following alarms are found in real-time alarm for CMP/CMP2 backup board.ZXG10 iBSC Emergency Maintenance e. Post inspection l The alarm is removed after checking on NM system. 3. d.3 Alarms related with CMP/CMP2 standby board 1. If ENUM switch is opened. ALM. 3. Troubleshooting steps: a. l l 198005379 Board offline or CPU in long-term resetting state 198005122 Communication link disconnected at control plane between active/standby boards 2. and check whether the board is normal. If above steps can't solve the fault. 3.1. 3-2 SJ-20110531095035-006|2011-09-30(R1. If the alarms still continue. is on and the fault exists on NM.1) ZTE Proprietary and Confidential . you shall contact local ZTE office or customer service center. Replace OMP/OMP2 board. or wrongly inserted. 3. Post inspection The alarm is removed after checking on NM system. f.1. View OMP/OMP2 board indicators to check whether red alarm indicator. is on and the fault exists on OMP/OMP2. l If possible. If the board is not at proper position. If the alarms still continue. e.2 Alarms related with OMP/OMP2 standby board 1. View rack board indicators at BSC side to check whether red alarm indicator.1. If the problem continues. b. Troubleshooting steps: a. you shall contact local ZTE office or customer service center. l l l 198005379 Board offline or CPU in long-term resetting state 198005390 Wrong (CPU) sub-card position configured by database 198005122 Communication link disconnected at control plane between active/standby boards 2. reset the board. switch the original standby OMP/OMP2 to active one while the service traffic is minimum. you shall close it. First try to reset remotely from NM. c. Check whether the board is inserted in proper slot. Symptoms The following alarms are found in real-time alarm for OMP/OMP2 backup board. Reset relevant boards.1. you shall plug/unplug the board again. b. c. you can reset it by manually plugging/unplugging the board. d. First try to reset remotely from NM. e. If the alarms still continue.1. 3. First try to reset remotely from NM. 3. If the board is not at proper position. reset the board. 3. If the problem continues. Check whether the board is inserted in proper slot. you shall close it. Replace this board. If the alarms still continue. you shall plug it properly again. Troubleshooting steps: a. Check whether micro switch (ENUM) of the board is opened.1) ZTE Proprietary and Confidential . 3-3 SJ-20110531095035-006|2011-09-30(R1. Post inspection The alarm is removed after checking on NM system. you shall contact local ZTE office or customer service center. you shall contact local ZTE office or customer service center. d. you shall close it. or wrongly inserted. If the board is not at proper position.Chapter 3 Guide of Emergency Maintenance b. Symptoms The following alarms are found in real-time alarm for OMP/OMP2 active board. you can reset it by manually. If ENUM switch is opened. e. Check whether the board is inserted in proper slot.2 Clock alarm 1. If above steps can't solve the fault.4 Board alarm out of active/standby mode 1. View rack board indicators at BSC side to check whether red alarm indicator is on and the fault exists on the board. Replace CMP/CMP2 board. f. 3. f. If the problem continues. Symptoms The following alarms are found in real-time alarm. Check whether micro switch (ENUM) of the board is opened.1. c. or wrongly inserted. l 198066003 Abnormal communication at control plane between board and its module l 198005379 Board offline or CPU in long-term resetting state l 198005390 Wrong (CPU) sub-card position configured by database 2. If ENUM switch is opened. Post inspection The alarm is removed after checking on NM system. f.ZXG10 iBSC Emergency Maintenance l 198005381 Abnormal access clock l 198005646 Phase-locked loop out of lock l 198026129 Level 1 alarm on lost clock reference source 2. c. e. high BER. If yes. Symptoms The following alarms are found in real-time alarm. If yes. refer to Check whether global data at BSC and CN sides is changed. h. to check the condition of satellite signal received. you shall check the connection condition from GPS antenna feeder to ICM board. you shall re-connect it or replace the clock cable from A-interface board to CLKG/ICM. troubleshooting in Clock Alarm. Check whether SDTB/SDTB2. Switchover CLKG/ICM board.1) ZTE Proprietary and Confidential . you shall contact local ZTE office or customer service center. or SPB/SPB2 board to get clock at interface A is normal. Troubleshooting steps: a. Troubleshooting steps: a. you shall restore the data prior to changing. Check E1/IP alarm at interface A to view whether all PCM/networks are interrupted at this interface. l 198066010 Alarm on unreachable MTP3 office l 198066005 SCCP Subsystem Unavailable 2. Check whether CLKG/ICM board is running normally. c. Check whether STM-1 and E1 are normal on the board to get clock at interface A. you shall check ICM board followed by SDTB/SDTB2. DTB. you shall contact transmission engineer to solve it. 3-4 SJ-20110531095035-006|2011-09-30(R1. or slide code alarm exist. Board Alarm shows the steps of inspection and troubleshooting. Post inspection The alarm is removed after checking on NM system. Check whether trunk interruption. If the alarms still continue. g. Board Alarm shows the steps of inspection and troubleshooting. Check whether the clock state at BSC side is exceptional. b. or SPB/SPB2 board and in-between wiring. and login the board through serial port mode.3 Alarms related with interface A 1. 3. d. DTB.1. such as "SDH/SONET: signal missing". If ICM board directly connects DDF to get A-interface clock at core side. Check whether cable connection from A-interface board to CLKG/ICM is normal. 3. b. "trunk signal missing". If the cable is loose or abnormal. If yes. If getting GPS clock. If the fault continues.2 Congestion at signalling point 1.4.1.1. Inform MSC engineer to check whether MSC is overloaded and sends corresponding overload message to BSC side.7 signaling link is overloaded. 3-5 SJ-20110531095035-006|2011-09-30(R1. If not. l 198087344 Overload of MSC FUC control mode l 198087347 Alarm on system message method during MSC overload 2. you can continue switchover the next board.4 Alarms on flow control 3. If the alarms still continue. you shall contact local ZTE office or customer service center. 3.4. 2. 3. b. l Through dynamic data observation at interface A. If no classfication.1 MSC overload 1. l 198087346 Alarm on FUC control method during SP congestion. d.Chapter 3 Guide of Emergency Maintenance d. c. 3. Gradually switchover UIMU. FUC flow control will not work. CLKG/ICM boards. signaling trace analysis and service test at interface A are normal. 3. Notify MSC engineers of checking whether no.1. test whether all signals. Check whether SIM card for field mobile phones are classified according to specified requirements. You shall check whether the service is restored while you switchover each board. Post inspection l The alarm is removed after checking on NM system. Symptoms The following alarms are found in real-time alarm. Troubleshooting steps: a. Check whether FUC bitmap at BSC side is configured properly. GUIM/GUIM2. UIMC. Post inspection l The alarm is removed after checking on NM system. l 198087349 Alarm on system message method during SP congestion. l Transmission is restored through testing. FUC flow control hasn't any influence on user service. Contact local ZTE office or customer service support center. e. Symptoms The following alarms are found in real-time alarm. Troubleshooting steps: a.1) ZTE Proprietary and Confidential . trunks. ZXG10 iBSC Emergency Maintenance b. Query whether TCH traffic and the number of TCH request in KPI indicators are greatly increased. If it is greatly increased, you can confirm SP congestion is caused by higher traffic. c. Check whether all no.7 signals are normal at this link, or any interruption or flash symptom exist. d. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flow control will not work. e. Check whether SIM card for field mobile phones are classified according to specified requirements. If no classfication, FUC flow control hasn't any influence on user service. f. Contact local ZTE office or customer service support center. 3. Post inspection l The alarm is removed after checking on NM system. l Transmission is restored through testing. 3.1.4.3 Too high CPU load 1. Symptoms The following alarms are found in real-time alarm. l 198087348 Alarm on system message control mode due to higher CPU load. l 198087345 Alarm on FUC control mode due to higher CPU load. 2. Troubleshooting steps: a. Query whether TCH traffic and the number of TCH request in KPI indicators are greatly increased. If it is greatly increased, you can confirm whether CPU overload is caused by higher traffic. b. Block corresponding cells in the region by using NM tools. c. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flow control will not work. d. Check whether SIM card for field mobile phones are classified according to specified requirements. If no classfication, FUC flow control hasn't any influence on user service. e. Contact local ZTE office or customer service support center. 3. Post inspection l The alarm is removed after checking on NM system. previously, you shall unblock the cell. l Transmission is restored through testing. If the cell is blocked 3.1.5 Transmission alarms 1. Symptoms The following alarms are found in real-time alarm. 3-6 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential Chapter 3 Guide of Emergency Maintenance l 198000512 Loss of trunk frame l 198000513 Loss of trunk signal l 198001792 SDH/SONET: loss of signal 2. Troubleshooting steps: a. Check E1/IP alarm to view whether all PCM/networks are interrupted at this interface. b. Check whether transmission cable is correct, connector is properly contacted, or cable is normal. c. Inform transmission engineer to check transmission equipment and its link. d. Replace relevant DTB, SDTB/SDTB2, and GIPI/GIPI4 boards. e. If the alarms still continue, you shall contact local ZTE office or customer service center. 3. Post inspection l The alarm is removed after checking on NM system. l Transmission is restored. 3.2 Maintenance Guide about NM Faults Maintenance guide about NM faults contains the following contents: l l l Can't login NM system; OMM Disconnection between OMM and NM servers; Disconnection between OMP/OMP2 and OMM server. 3.2.1 Can't login NM system 1. Symptoms Login from the client to the NM server fails. 2. Troubleshooting steps: There are two cases: all clients can't login or individual client can't login. So the troubleshooting can be categorized into two types. l All clients can't login. a. Check running condition of server programs, and view whether all NM processes are normal. b. check if server database is running properly. c. Check operation condition of server operating system. d. Restart the server. e. If the alarms still continue, you shall contact local ZTE office or customer service center. l Individual client can't login. 3-7 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential ZXG10 iBSC Emergency Maintenance a. check if client database is running properly. b. Check if the client IP communicates normally with the server. c. check if required Java packet exists and is normal during client operation. d. Is client attacked by virus? check if operating system is normally running. If any virus is detected, kill it. e. If the alarms still continue, you shall contact local ZTE office or customer service center. 3. Post inspection Successfully log in client and you can use it normally. 3.2.2 Disconnection between OMM and NM servers 1. Symptoms Can't start NE agent. 2. Troubleshooting steps: a. Check whether the physical link between NM server and OMM server is connected. b. Check whether the firewall ports of NM server and OMM server are opened. c. Check whether OMM FTP server is available, and check whether FTP port definition of profile is correct. d. If the alarms still continue, you shall contact local ZTE office or customer service center. 3. Post inspection NE agent is successfully enabled, and you can use it normally. 3.2.3 Disconnection between equipment and OMM server 1. Symptoms In configuration management, it is found the link between equipment and OMM is disconnected, and configuration data can't be distributed normally. 2. Troubleshooting steps: a. Check whether IP network from OMP/OMP2 to HUB is normal. l Check the network cable from OMP/OMP2 to HUB. l Check configuration of OMP/OMP2 IP address in OMM server data. b. Check whether the MP is running normally. If no, refer to troubleshooting in Board Alarm. c. Restart OMM server. 3-8 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential refer to All Sites Under BSC Can't Call Normally. All sites under certain 100M/GB resource frame can't call normally. Mass users belonging to other type can't call normally. The alarm is removed. you can use the following troubleshooting methods. Symptoms Mass users can't call normally 2. 2. you shall contact local ZTE office or customer service center. Troubleshooting 3-9 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential .3 Maintenance Guide about CS Service Faults Maintenance guide about CS service faults contains the following contents: l l l l l l l Mass users can't call normally. According to different service scope.2 All sites under BSC can't call normally 1.3. All Sites Under Certain LAPD/LAPD2 Can't Call Normally. All sites under certain LAPD/LAPD2 can't call normally. All sites under BSC can't call normally.1 Mass users can't call normally 1. All Sites Under Certain 100M/GB Resource Frame Can't Call Normally. 3. All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call normally. and Mass Users Belonging To Other Type Can't Call Normally. Post inspection Check the NMS and find the communications link between the NMS and NE is established. All Sites Under Certain BIPB/BIPB2/AIPB/AIPB2 Can't Call Normally. For more information. All sites under certain module in BSC can't call normally. Troubleshooting Based on quantity and domain of claiming users and in combination with KPI analysis and test. If the alarms still continue. 3. 3. Post inspection l The result is normal during calling test.3. 3. 3. you can determine the influence scope of this fault. All Sites Under Certain Module In BSC Can't Call Normally. Symptoms All sites under BSC can't call normally. l KPI index restores the level prior to the fault.Chapter 3 Guide of Emergency Maintenance d. refer to troubleshooting in Board Alarm. e. If yes. PSN. Check whether ring message is distributed or ground resource can be allocated normally. or control shelf. b. e. c. refer to troubleshooting in Board Alarm.1) ZTE Proprietary and Confidential . l You can call normally at all sites under BSC. b. View CMP/CMP2 alarm on this module to check whether the board or certain CPU on it can't normally function. Switchover OMP/OMP2 board. If yes. If the alarms still continue. If yes. such as OMP/OMP2 and CMP/CMP2 can't work normally. Check whether the active/standby boards for switching shelf. If yes. Post inspection l The alarm is removed after checking on NM system. reset the board. Check whether clock alarm exists by viewing global alarms. 2. l You can call normally at all sites under this module in BSC. 3. and no sound exists at one channel or in bidirection. d.ZXG10 iBSC Emergency Maintenance a. 3. refer to troubleshooting in Clock Alarm. refer to troubleshooting in Alarms Related With Interface A. If it is disconnected at interface A. Check whether the link at interface A is disconnected and global alarm issues. 3-10 SJ-20110531095035-006|2011-09-30(R1. 3. or UIMC. you shall check whether there is any alarm on AIPB/AIPB2 and BIPB/BIPB2 logical board. Replace the module on CMP/CMP2. Troubleshooting a.3 All sites under certain module in BSC can't call normally 1. you shall contact local ZTE office or customer service center. f. you shall contact local ZTE office or customer service center. refer to troubleshooting in Alarms On Flow Control.3. If signal is complete. d. c. Reset or replace this CMP/CMP2 module. l KPI index restores the level prior to the fault. Enable signaling trace based on test condition. such as GLI/GLI4. l KPI index restores the level prior to the fault. Symptoms All sites under certain module in BSC can't call normally. If yes. If the alarms still continue. View whether flow control alarm occurs due to CPU overload on this module. Post inspection l The alarm is removed after checking on NM system. Check the BIPB/BIPB2/AIPB/AIPB2 alarm to view whether the board can't work normally. If the alarms still continue. c. you shall contact local ZTE office or customer service center. Post inspection l The alarm is removed after checking on NM system. 2. Symptoms All sites under certain 100M/GB resource frame can't call normally.3. If yes. Symptoms All sites under BIPB/BIPB2/AIPB/AIPB2 can't call normally. l KPI index restores the level prior to the fault. b.5 All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call normally 1. If the alarms still continue.1) ZTE Proprietary and Confidential . d. b. If yes. Troubleshooting a. e. 3. f. Reset this UIMU/GUIM/GUIM2 board. c.4 All sites under certain 100M/GB resource frame can't call normally 1. Post inspection l The alarm is removed after checking on NM system. refer to troubleshooting in Board Alarm. refer to troubleshooting in Board Alarm. 3. l You can call normally at all sites under BIPB/BIPB2/AIPB/AIPB2. 3. Troubleshooting a. Reset this BIPB/BIPB2/AIPB/AIPB2 board. Check the UMIU/GUIM/GUIM2 alarm of this shelf to view whether the board can't work normally. l You can call normally at all sites under this resource shelf. Switchover this UIMU/GUIM/GUIM2 board.3. 2.6 All sites under certain LAPD/LAPD2 can't call normally 1. 3. Check whether ethernet cable from UIMU/GUIM/GUIM2 to CHUB is normally connected. l KPI index restores the level prior to the fault. Symptoms 3-11 SJ-20110531095035-006|2011-09-30(R1.3. Check whether clock cable from UIMU/GUIM/GUIM2 to CLKG/ICM is normally connected. you shall contact local ZTE office or customer service center.Chapter 3 Guide of Emergency Maintenance 3. 3. 3. l user can call normally. 2. b.3. SDCCH congestion rate. Contact local ZTE office or customer service support center. Some cells can't use GPRS service. If yes. 3. to determine which phase the fault occurs. TCH allocation failure rate. Check the LAPD/LAPD2 alarm to view whether the board can't work normally. If the alarms still continue.7 Mass users belonging to other type can't call normally 1. 3. you shall contact local ZTE office or customer service center.1) ZTE Proprietary and Confidential . you shall restore original backup data. Symptoms Mass users belonging to other type can't call normally. Trace and record messages at interface Abis and A to analyze it. l KPI index restores the level prior to the fault.1 Mass user can't use GPRS service 1.ZXG10 iBSC Emergency Maintenance All sites under LAPD/LAPD2 can't call normally. Symptoms 3-12 SJ-20110531095035-006|2011-09-30(R1. l You can call normally at all sites under LAPD/LAPD2. c. Post inspection l The alarm is removed after checking on NM system. Reset this LAPD/LAPD2 board from equipment. 2. l KPI index restores the level prior to the fault. d. Analyze SDCCH assignment failure rate. Troubleshooting a.4 Maintenance Guide about PS Service Faults Maintenance guide about PS service faults contains the following contents: l l l Mass user can't use GPRS service. b. TCH assignment failure rate. Check whether data is changed at BSN or CN side. If yes. refer to troubleshooting in Board Alarm. All users under whole BSC can't use GPRS service. Post inspection l The alarm is removed after checking on NM system. c. 3.4. Troubleshooting a. and TCH congestion rate in KPI indicators. Determine it is caused by the problem at BSC or CN side based on signaling process. If yes. office direction from BSC to SGSN is normal. NSVC state is normal. Symptoms Lots of users in some cells can't use GPRS service 2. b. refer to troubleshooting in Board Alarm. Post inspection l You can normally use GPRS service. e. View E1 alarm at interface Gb to check whether E1 transmission is interrupted. 3.2 All users under whole BSC can't use GPRS service 1.1) ZTE Proprietary and Confidential . you shall contact local ZTE office or customer service center. 3. Check the UPPB/UPPB2 alarm to view whether the board can't work normally. f. d. If yes. l KPI index restores the level prior to the fault. Check the DTB or GIPB/GIPB2 alarm at interface Gb to view whether the board can't work normally. 3. If the alarms still continue. If yes. Reset GIPB/GIPB2 or DTB board at interface Gb. and relevant configuration is correct. you can use the following troubleshooting methods.4. l KPI index restores the level prior to the fault. and inform transmission engineer to check E1 transmission. refer to troubleshooting in Board Alarm. Reset UPPB/UPPB2 board. For more information. you can determine the influence scope of this fault.4. g. Troubleshooting 3-13 SJ-20110531095035-006|2011-09-30(R1.3 Some cells can't use GPRS service 1. 3. you shall check whether IP cable is normal.Chapter 3 Guide of Emergency Maintenance Lots of users can't use GPRS service 2. check E1 cable. refer to All Users Under Whole BSC Can't Use GPRS Service and Some Cells Can't Use GPRS Service. If yes. Symptoms Lots of users under whole BSC can't use GPRS service 2. Troubleshooting a. l You can normally use GPRS service of this BSC. Check whether IP network at interface Gb is disconnected. c. Post inspection l The alarm is removed after checking on NM system. Troubleshooting Based on quantity and domain of claiming users and in combination with KPI analysis and test. According to different service scope. Confirm whether lots of GRPS data are changed prior to the fault. 3. Post inspection l The alarm is removed after checking on NM system. Check the UPPB/UPPB2 alarm to view whether the board or certain CPU can't work normally. If yes. refer to troubleshooting in Board Alarm. If yes.ZXG10 iBSC Emergency Maintenance a. If yes. unblock the BVC. If the alarms still continue. In dynamic data management interface. view BVC state in the cell and check whether BVC is blocked. d. l KPI index restores the level prior to the fault. l You can normally use GPRS service in this cell. you shall restore the data firstly. 3-14 SJ-20110531095035-006|2011-09-30(R1. b. c.1) ZTE Proprietary and Confidential . you shall contact local ZTE office or customer service center. .... Fault time Describes specific time of the fault..... It includes the operation cases that may cause the fault..... b. Describes the fault symptom....... For the channel state in dynamic management and error messages occurred during operation.. 1.....1 Prerequisite of fault feedback Prerequisite of fault feedback: 1....... 4...... c... you can use the record function of NETTERM to remember the operation procedures.. It describes the fault scope................ Detailed troubleshooting steps a.............. including start/end time of the fault.. 3. NM alarm..... For the operations on the server.....Chapter 4 Fault Feedback Information Table of Contents Prerequisite of fault feedback ... It is recommended that field operators keep a good habit to record operation procedures for the server............ c....... 2.............. b.. System record It records system operation state and error messages................. which is the primary method to find system errors... These are the basis of field troubleshooting..... Steps and time about field troubleshooting. If you can't express it clearly.... Fault description a. 4-1 SJ-20110531095035-006|2011-09-30(R1... you shall copy the pictures....4-6 4......4-1 Feedback Data That Shall be Recorded ... so it can provide a convenience to check whether there is any operation error..4-3 The method to get system record ... 3................. 5... 4.. and calling state...... dynamic state........ Fault time Fault description Detailed troubleshooting steps System record Fault feedback report Presented below are a brief description of different elements.................. you shall copy it in picture mode.... messages......... 2...... such as whole BSC or site. such as board state...................1) ZTE Proprietary and Confidential .. Table 4-1 Field Fault Feedback Report Feed- Re- back ceived by Feedback time Con- by Con- tact tact person Phone No. e-mail Source unit Model Fault Ver- time. Fault feedback report Table 4-1 shows fault feedback report. and description Attached pages Description of field procedure and handling Attached pages Field data feedback Attached pages Analysis and preliminary Attached pages com- Han- ments dled by Day 4-2 SJ-20110531095035-006|2011-09-30(R1. Network capacity sion symptom.ZXG10 iBSC Emergency Maintenance 5.1) ZTE Proprietary and Confidential . Refer to Get ZDB File. Configuration information Refer to Get Device Printing File. to learn configuration in- equipment or ZDB file for NM. feedback. so you shall return Feedback shall be sent based number.1) ZTE Proprietary and Confidential . in ZDB file in all active MP for the BSC. Screenshot if board in-stock version. Notification file.txt equipment printings. Alarm file.Chapter 4 Fault Feedback Information Final comments and conclusion 4. on the version of field records. Different version has different Equipment and NM version functions. Software settings about the and specified version settings. board Refer to Get Software Setting. to learn configuration informa- Refer to Get Data Backup Ztd tion.2 Feedback Data That Shall be Recorded Table 4-2 shows the feedback data required by BSC faults. formation. Configuration information in NM. ZTD backup files in NM. 4-3 SJ-20110531095035-006|2011-09-30(R1. Exc_pp. Refer to Get Alarm File. Table 4-2 Feedback data required by BSC faults System feedback records The method to get system required Purpose of Record record The indicators contain the elBoard indicator conditions on ementary fault board operation. ment of system alarm. information about Omitted Printing file of the equipment (including active/standby MP Record exceptional cases oc- for central peripheral modules): curred during BSC operation in Exc_Omp. picking up his- Notification file is the supple- torical files within a week. File From OMM. Refer to Get Notification File.txt. general software version. the system. picking up historical alarms within a week and current Alarm file records all alarms in alarms. Interface A. about signaling tracing at inter- Signaling is a very useful tool to Refer to Get Tracing Signal At face A. Fault. and BVC and NSVC states of the cell Refer to Query BVC And NSVC channel.ZXG10 iBSC Emergency Maintenance System feedback records The method to get system required Purpose of Record record Performance report within 1 hour before and after the fault. locate questions. For the fault related with interface Abis. locate questions. Refer to Get 1 Hour's Perfor- Do measurement according to You can find system operation mance Data Before And After cell level. state in performance statistics. nal. carrier. state. 4-4 SJ-20110531095035-006|2011-09-30(R1. Interface A. you shall send feedback Signaling is a very useful tool to Refer to Trace PS Service Sig- about signaling about PS. Interface Abis. vice. overstocked Refer to Check Whether OverAnalyze incomplete data stocked Data Exists. you shall return the feedback information about dynamic site If it involves calling faults at site. carrier. you shall return the feedback information about dynamic site For the fault related with PS ser- Operation log of preset machine Check whether data exists Operation condition of preset Refer to Get Operation Log Of machine Preset Machine. you shall send feed- If it involves calling faults at site.1) ZTE Proprietary and Confidential . you shall send feedback about dynamic state of the link at interface A. For the fault related with interface A. Site. back about signaling tracing at Signaling is a very useful tool to Refer to Get Tracing Signal At interface Abis. State. including cell. Refer to Query Dynamic Data At State of the link at interface A. state. and Channel state is another path to Refer to Query Dynamic Data At channel. is used to judge system state. Table 4-3 shows the feedback data required by NM faults. you shall send feedback If the problem is related with interface A or whole BSC. judge system state. locate questions. including cell. 4-5 SJ-20110531095035-006|2011-09-30(R1. so you Identify site name. Record NM operations on site. ting. Record call cases in the system. Interface Abis. Signaling trace at interface Abis. ZTD backup files in NM. carrier. Important configuration in the NM profile system. Notification File. and chan- Channel state is another path to Refer to Query Dynamic Data At nel. Record the operation conditions NM printing file of NM system.1) ZTE Proprietary and Confidential . Record fault information. judge system state. Client. Refer to Get NM Printing File. Interface Abis. Refer to Get Tracing Signal At Historical alarm file within a week and historical notification Refer to Get Alarm File and Get file within a week. ZDB file.Chapter 4 Fault Feedback Information Table 4-3 Feedback data required by NM faults System feedback records The method to get system required Check the disk space Purpose of Record record Reflect the disk condition Refer to Query Disk Space. Refer to Get NM Profile. Refer to View NM Version. For international office. Zone. Table 4-4 shows the feedback data required by site faults. Refer to Get Operation Log At Operation log at client. to learn configuration informa- Refer to Get Data Backup Ztd tion. File From OMM. Different version supports differ- Refer to Get BTS Software Set- Site version ent functions. Omitted including cell. Different version supports differNE version ent functions. number and can find corresponding site in its model. Dynamic observation condition. Reflect the information while the Refer to Get Tracing Signal At O&M signaling trace site is starting. Configuration information in NM. Table 4-4 Feedback data required by site faults System feedback records The method to get system required Purpose of Record record Identify the relation between site name and its number. locate Refer to View System Time System time zone specific time. Site. 1 21 cd /DOC0 get Exc_pp. to transfer the ZDB files into proper directory. While getting ZDB file. After the files are downloaded onto OMM server.3. File.20. Use command "get" to get Exc_Omp.txt bye 4. 2. Use command ftp to connect OMP/OMP2 on OMM. – End of Steps – Example 1. Both username and password are zte at specified port 21.txt files.3.3. 2.3 The method to get system record 4. 4.2.6.txt get Exc_Omp.1) ZTE Proprietary and Confidential . mkdir bsc1 cd bsc1 ftp 172. 5. 4. you had better establish a proper directory for each module on each BSC. 5.2 Get ZDB file 4. 6. if there are too many files. to upload the files to client. 4. such as CUTEFTP. Create a directory to save files on OMM server. 7.txt and Exc_pp. you can use ftp tool. 3.1 Get equipment ZDB file Context ZDB file is under /DOC0/DATA1 on OMP/OMP2.ZXG10 iBSC Emergency Maintenance System feedback records The method to get system required NE ZDB file Purpose of Record record Record and confirm NE configu- Refer to Get Equipment ZDB ration information.1 Get device printing file Steps 1. 3. Use command cd /DOC0 to enter into DATA0 directory. 4-6 SJ-20110531095035-006|2011-09-30(R1. to transfer ZDB file to client. VERTABLE. to upload the files to client and compress it. VERTABLE. Generated file is too small during incremental synchronization. and add generation time postfix for the file generated at last time for backup.ZDB one by one.20.ZDB. 5. 3. 3. it may generate new CFGTABLE. – End of Steps – 4-7 SJ-20110531095035-006|2011-09-30(R1. a.Chapter 4 Fault Feedback Information Steps 1. After the files are downloaded onto OMM server. 4.ZDB. you can do a synchronization action on whole table on NM client. 7. Use command cd to enter into /DOC0/DATA1. Use command get filename to download CFGTABLE. You can use ls –l command to veiw the file size. this will generate new complete ZDB file.ZDB. Use ftp tool. such as CUTEFTP. 6. 2. If current ZDB file belongs to the one genereated on incremental synchronization.3. such as CUTEFTP. Steps 1.1) ZTE Proprietary and Confidential . Creat a directory to save files on OMM server.ZDB get VERTABLE. you can use ftp tool.1 21 cd /DOC0/DATA1 get CfgTable.6. Get required ZDB files under DATA1 directory. 2. b. and DBVER. Use command ftp to connect OMP/OMP2 on OMM.2 Get OMM ZDB file Context OMM ZDB files are saved in $OMCHOME/tmp/ftp/zdb/ibscXX (XX indicates BSCID). 8.2. 4. and DBVER.ZDB.ZDB get DBVer.ZDB files. cd $OMCHOME mkdir bsc1 cd bsc1 ftp 172. Both username and password are zte at specified port 21.ZDB 4. 2. – End of Steps – Example 1. Each time you perform whole table synchronization or incremental synchronization. select BSC Software Management. select backup path. to call configuration management interface. Select Management > Data Management > Data Backup. and special version of BSC. /CM. you shall do the action of "synchronize version data from NE to OMC". Input prefix of backup filename. Use ftp tool with username/password as sysbak and port 21.3. In displayed Data Backup window. refer to Get equipment ZDB file. – End of Steps – 4. and backup description.3. and re-establish NM software settings.3. so if you can't determine whether it is consistent. snap three screenshots for version file. After acknowledgement. 4. – End of Steps – 4.4. For detailed operations. 4.ZXG10 iBSC Emergency Maintenance 4. select NE Management > Software Version Management in floating menu. common version. 2. Right-click the NE in physical view of topology management.ZDB.1 Get BSC software setting Steps 1. operate the data based on actual equipment condition. to call configuration management interface. click OK button. to download backed-up ztd file from OMM server through ftp mode. 3. 4-8 SJ-20110531095035-006|2011-09-30(R1.4 Get software setting 4.4.3. and select a NE to be backed-up. (normally on OMM server). equipment data may be inconsistent with NM data.1) ZTE Proprietary and Confidential . Right-click the NE in physical view of topology management. For setting of software version. select NE Management > Configuration Management in floating menu. 2. After the synchronization. Save it as jpg file and send feedback.2 Get BTS software setting BTS software setting can fed back by getting VerTable.3 Get data backup ztd file from OMM Steps 1. 3. synchronization operation may remove NM software setting. In Software Version Management interface. 3.1) ZTE Proprietary and Confidential . Select Quick Search in Query Setting of History Alarm.3. as shown in Figure 4-1.Chapter 4 Fault Feedback Information 4. Select a relative time in Happen Time. Figure 4-1 Select View History Alarms 2. and select all alarm types in System Type. 4-9 SJ-20110531095035-006|2011-09-30(R1.5 Get alarm file Steps 1. 4. Start Alarm Management at client. The date shall be a day within a recent week or a customized day. as shown in Figure 4-2. Select View History Alarms in View Alarm menu option of Alarm Management interface. Select System Type in Query History Alarm window. You can use % to do fuzzy searching. as shown in Figure 4-3. In NE Type.1) ZTE Proprietary and Confidential . 4-10 SJ-20110531095035-006|2011-09-30(R1. enter IBSC%.ZXG10 iBSC Emergency Maintenance Figure 4-2 Set query time of alarm 5. as shown in Figure 4-4. 4-11 SJ-20110531095035-006|2011-09-30(R1. 8. In Save window. Click OK to output alarm data.Chapter 4 Fault Feedback Information Figure 4-3 Set the Type of Alarm NE 6. Click Export button to export queried alarms.1) ZTE Proprietary and Confidential . 7. select the proper path and click Save. select Show History Alarms in floating menu to view history alarm. Figure 4-5 Displaying history alarms of the selected NE – End of Steps – 4-12 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential .ZXG10 iBSC Emergency Maintenance Figure 4-4 Alarm Save Window Note: You also can right-click the NE in resource view of alarm management. as shown in Figure 4-5. You can't select alarm Happen Time by using this method. Chapter 4 Fault Feedback Information 4. Select Quick Search in Query Setting of Notification. as shown in Figure 4-8. 4-13 SJ-20110531095035-006|2011-09-30(R1. Select View Notifications in View Alarm menu option of Alarm Management interface. and select all notification types in System Type. Select System Type in Query Notification window.1) ZTE Proprietary and Confidential . Start Alarm Management at client.6 fanGet notification file Steps 1. Figure 4-7 Select Quick Search 3. Figure 4-6 Select View Notifications 2. as shown in Figure 4-7. as shown in Figure 4-6.3. Select start/end time in Happen Time.1) ZTE Proprietary and Confidential . 4-14 SJ-20110531095035-006|2011-09-30(R1.ZXG10 iBSC Emergency Maintenance Figure 4-8 Query Notification Window 4. as shown in Figure 4-9. as shown in Figure 4-10.1) ZTE Proprietary and Confidential .Chapter 4 Fault Feedback Information Figure 4-9 Set query time of notification 5. You can use % to do fuzzy searching. enter IBSC%. In NE Type. 4-15 SJ-20110531095035-006|2011-09-30(R1. 1) ZTE Proprietary and Confidential . as shown in Figure 4-11. Click OK to output notification data. 4-16 SJ-20110531095035-006|2011-09-30(R1. Click Export button to export queried notifications. select the proper path and click Save. In Save window. 7.ZXG10 iBSC Emergency Maintenance Figure 4-10 Set the Type of Nofication NE 6. 8. 1) ZTE Proprietary and Confidential . Figure 4-12 Select Performance Management and Performance Data Query 2. as shown in Figure 4-12. 4-17 SJ-20110531095035-006|2011-09-30(R1.7 Get 1 hour's performance data before and after fault Steps 1. In Query Index of Integrated Query interface. select NE type as BSC Elements.Chapter 4 Fault Feedback Information Figure 4-11 Notification Save Window – End of Steps – 4.3. and select object type as CellFunction Type. select the NE to be viewed in resource view. select KPI index and PI index. Start Performance Management at client. as shown in Figure 4-13. Select Performance Management > Performance Data Query menu. 4-18 SJ-20110531095035-006|2011-09-30(R1. Select customized time in Query Time tab. Select the cell to be queried in measurement object. query granularity is 15 minutes. Select the NE to be queried in Query Object tab.1) ZTE Proprietary and Confidential . as shown in Figure 4-14. as shown in Figure 4-15. and summary mode is Cell (Original Polled Object).ZXG10 iBSC Emergency Maintenance Figure 4-13 Integrated Query Interface 3. and query mode is Cell. Figure 4-14 Set Query Time of Performance Data 4. Repeat above steps.1) ZTE Proprietary and Confidential . 6.Chapter 4 Fault Feedback Information Figure 4-15 Set Query Object of Performance Data 5. Figure 4-16 Select Basic Measurement Data of CS – End of Steps – 4-19 SJ-20110531095035-006|2011-09-30(R1. Queried data shall be exported as EXCEL report. query basic measurement data of CS and export it as EXCEL report. as shown in Figure 4-16. Note: Signaling trace tool shall use server/client architecture. Configure server procedure for signaling trace tool. and access to Parameter Setting interface to configure signaling trace. clientcfg. 2. Figure 4-17 Parameter Setting interface 3. Click Save button. configure Capacity of Signal Window as 20000. start and logon signaling trace client. 4-20 SJ-20110531095035-006|2011-09-30(R1.xml file is configured.3.xml file is configured at server side.1) ZTE Proprietary and Confidential .exe program is running. Requirement of using signaling trace tool: servercfg. Select File Spliting. 5000 for each file. and click Update Configuration button. In Record Setting tab. Select Tools System Setting. select the BSC to be traced.ZXG10 iBSC Emergency Maintenance 4.8 Get tracing signal at interface A Steps 1. as shown in Figure 4-18. Configure in Trace Setting interface. as shown in Figure 4-17. and server. start server program. In M3UA. 4-21 SJ-20110531095035-006|2011-09-30(R1. Select M3UA . select coupling ID. and select Subsystem No. Figure 4-19 Select SCCP 5. as shown in Figure 4-20. After successfully updating configuration. as 254.Chapter 4 Fault Feedback Information Figure 4-18 Trace Setting interface 4. select Module No.1) ZTE Proprietary and Confidential . as shown in Figure 4-19. In SCCP option. corresponding coupling SCCP. select SCCP. and direction. ZXG10 iBSC Emergency Maintenance Figure 4-20 Select M3UA 6.tra. you shall send the both files.tra and .1) ZTE Proprietary and Confidential . After stopping trace. as shown in Figure 4-22. select File > Save all as . 4-22 SJ-20110531095035-006|2011-09-30(R1. saved files contain .idx files. Save all signaling trace result as tra format. as shown in Figure 4-21. Select the path to save in Save window. Figure 4-21 Save Signaling Trace Result 7. If feedback. 3. 3. In configuration resource tree. select NE Management Dynamic Data Management in floating menu. Each trace can't exceed 5 minutes. Login in NM client. in A-Interface Trunk Circuit Management tab. and you can do A-interface PCM. If using IP A-interface. click Query button to query DSP state. 2.9 Query dynamic data at interface A Steps 1. – End of Steps – 4. select and expand management NE node.Chapter 4 Fault Feedback Information Figure 4-22 Signaling Trace Save Window Note: Trace at interface A has great influence on system load. – End of Steps – 4-23 SJ-20110531095035-006|2011-09-30(R1. A-interface trunk management. click Query Timeslot Circuit State button to query the state of timeslot. double-click corresponding dynamic data management node. and IPA resource management. 4. to call Dynamic Data Management interface. enter dynamic data management interface. click All Queries button. in IPA Management tab. click Query button to query PCM state. or select some circuits. In A-Interface PCM tab.1) ZTE Proprietary and Confidential . right-click the NE in physical view of topology management. After successfully updating configuration. Figure 4-23 Parameter Setting interface at Abis 3. Note: Signaling trace tool shall use server/client architecture.exe program is running. Requirement of using signaling trace tool: servercfg. 5000 for each file. select CS and OAM.xml file is configured at server side. 4-24 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential . start and logon signaling trace client. Configure in Trace Setting interface. clientcfg. select the BSC to be traced. 4. 2.10 Get tracing signal at interface Abis Steps 1. Select all traced entries in Tracing Entry of CS.ZXG10 iBSC Emergency Maintenance 4. Select Tools System Setting. Configure server procedure for signaling trace.xml file is configured. and server. In Record Setting tab. as shown in Figure 4-23. start server program. select the site to be traced in CS and OAM interfaces. and access to Parameter Setting interface to configure signaling trace. select a site in OAM. Select File Spliting. Click Save button. and click Update Configuration button.3. as shown in Figure 4-24 and Figure 4-25. configure Capacity of Signal Window as 20000. – End of Steps – 4-25 SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential .Chapter 4 Fault Feedback Information Figure 4-24 CS interface Figure 4-25 OAM interface 5. to enter Dynamic Data Management interface.11 Query dynamic data at site Steps 1. Double-click corresponding dynamic data management node at site.12 Trace PS service signal Steps 1.3. 3.1) ZTE Proprietary and Confidential . Table 4-5 shows dynamic data management function. 4-26 SJ-20110531095035-006|2011-09-30(R1. start and logon signaling trace client. In configuration resource tree. start server program. select and expand BSC management NE node. So you can perform radio resource management and BTS equipment management.3. Configure server procedure for signaling trace. 2. select NE Management > Dynamic Data Management in floating menu. Right-click the NE in physical view of topology management.ZXG10 iBSC Emergency Maintenance 4. Table 4-5 Dynamic Data Management Function Category Function Description Cell management query the status of cell TRX management Query the state of TRX Channel Management Query channel state Query channel statistics on a mod- Radio Resources Management Module Management ule BVC Management Query the BVC status of cell Cell channel management Query channel statistics of a cell Query timeslot state measure- Timeslot management at Abis BTS equipment management operation ment of resource pool at Abis Timeslot resource management at Query timeslot state of resource Abis pool at Abis LAPD state management Query LAPD link state at site Loopback Management Query the loopback state – End of Steps – 4. enter into Dynamic Data Management interface. Click Save button. Select the cell to be traced in PS and RLCMAC.1) ZTE Proprietary and Confidential . 4-27 SJ-20110531095035-006|2011-09-30(R1. select PS and RLCMAC at interface Abis. Save all signaling trace result as tra format. 4. Select File Spliting. and all options at interface Gb. After stopping trace. select the BSC to be traced. NSVC link to be traced in NS. Click OK button. In Record Setting tab. 3.exe program is running. 2. BVCI and BVCIO to be traced in BSSGP and LLC. Requirement of using signaling trace tool: servercfg. 5000 for each file.Chapter 4 Fault Feedback Information Note: Signaling trace tool shall use server/client architecture.tra. and NSVC to be traced in SNS (optional). and server. For Trace Type. and access to Parameter Setting interface to configure signaling trace. clientcfg.xml file is configured. as shown in Figure 4-26. Figure 4-26 Trace Setting of PS service signal 6. Select Tools System Setting. and click Update Configuration button. configure Capacity of Signal Window as 20000. In Trace Setting interface. 5.xml file is configured at server side. select File Save all as . BRCH link to be traced in FR. y.idx files. Where. you shall send the both files. – End of Steps – 4. 6.3.15 Check whether overstocked data exists Steps 1. enter into dynamic data management interface.3. In NSVC Management of Dynamic Data Management interface. You can get it through ftp tools. Solution is as follows: 4-28 SJ-20110531095035-006|2011-09-30(R1. \FTPRoot\nfsDev\iBSC\OMCR. GERAN subnet.14 Get operation log of preset machine Operation log of preset machine is saved in X:\FTPRoot\nfsDev\iBSC\OMS\log. If feedback. enter into dynamic data management interface.tra and . x. to enter Dynamic Data Management interface. 3. double-click corresponding dynamic data management node under management NE node to be queried.par/x-y/err. you can query NSVC state. In Wireless Resource Management tab of Dynamic Data Management interface. and BSC management NE. overstocked in x-y represents Data accumulation is caused by exceptional oracle. Select the path to save in Save window.ZXG10 iBSC Emergency Maintenance 7. full table space in performance library and performance index. For specific information. select and expand management NE node to be queried. Double-click corresponding dynamic data management node.1) ZTE Proprietary and Confidential . In configuration resource tree.3. Check whether OMM server data is $OMCHOME/gsmomcr/ibsc/zxgomcr-emf-pm. select BVC Management to query BVC state. select NE Management > Dynamic Data Management in floating menu. 2. X indicates the disk label of the log. you can get error reasons from server log. saved files contain .13 Query BVC and NSVC state Steps 1. Right-click the NE in physical view of topology management. and \FTPRoot\nfsDev\iBSC\OMSZIP. 4. 5. Meanwhile. In configuration resource tree. you shall display the update date in \FTPRoot\nfsDev\iBSC\OMS\. 4. – End of Steps – 4. You can try to restart ORACLE on site. For the AIX system. 6. – End of Steps – 4-29 SJ-20110531095035-006|2011-09-30(R1. – End of Steps – 4. Check whether backed-up configuration management files under /home/xxxxxxx/ums-svr/backup/sysmanager/cm in OMM server are overstocked. files under the server are 7. Check the space size of performance table and index table.Chapter 4 Fault Feedback Information i. 5. Check whether backed-up alarm management files under /export/home/xxxxxxx/ums-server/backup/sysmanager/fm on the server are overstocked. use the commands df –k and vmstat to query the current disk space. Check whether backed-up log management /export/home/xxxxxxx/ums-server/backup/sysmanager/log on overstocked. Check Whether communication between NM server and preset machine is normal and whether ftp service of preset machine is normal. 3.1) ZTE Proprietary and Confidential . Where. you can expand it based on server disk space. Exceptional operation modes of oracle are diversified. 2. You can try to preset machine through ftp and get performance file under NM directory. Check whether data file is overstocked in X:FTPRoot\nfsDev\iBSC\OMCR of preset machine. Use NETTERM to save operation procedure. and it is complicated to solve it. Check whether backed-up performance management files under /export/home/xxxxxxx/ums-server/backup/sysmanager/pm on the server are overstocked. ii.16 Query disk space Steps 1. step 2 is unnecessary.3. X is the label of data file disk. if it is full. For the AIX system. or delete relevant performance data and re-create index. For the Linux or Solaris system. 2. 3. Check whether backed-up performance configuration files under /export/home/xxxxxxx/ums-server/backup/sysmanager/ueppm on the server are overstocked. It is recommend you shall return server log to ZTE for analysis. 4. use the commands df –k and vmstat to query the current disk space. You can use ftp tools. /export/home/iomcr/iOMCR6. select Query NE Log > Operation Log in floating menu. Use ftp tool.log.par/conf. Required profile is as follows: l l fmmgr.par/conf. 4-30 SJ-20110531095035-006|2011-09-30(R1. 2.log server-20080117-1048-52694. On OMM server.properties Real-time alarm file related with server and NM system is saved in $OMCHOME/ums-svr/minos/minos-naf-rtalarm. this file is saved in $OMCHOME/gsmomcr/ibsc/zxgomcr-naf-rtalarm. consoleagent. bash-3.log 4.18 Get NM profile NM profile is saved in $OMCHOME/deploy.properties 4. to call log management tool at NM client.log.log 5.ZXG10 iBSC Emergency Maintenance 4.lck 6. such as cuteftp.log server-20080117-1436-53392.properties deploy-*. bash-3. If you use command cd $OMCHOME\log.0 server-20080117-0812-56822. you can enter into this directory to get corresponding LOG file. bash-3.02f/ums-svr/log 4. to download it to local client.17 Get NM printing file Steps 1.00$ pwd 7. Required profile is as follows: l l deploy-010muep. Right-click the NE in physical view of topology management.3.3.19 Get operation log at client Steps 1.log server-20080117-1516-54067.log server-20080117-1005-13029.00. boot.3.log server-20080117-0623-28443. – End of Steps – Example 1.00$ ls 3. Process printing file related with NM is located under $OMCHOME\log. as shown in Figure 4-27. The log file is named by its generation time.properties nafproc.00$ cd $OMCHOME/log 2.1) ZTE Proprietary and Confidential . to get log file within NM fault period.0. such as CUTEFTP. consoleagent. Figure 4-28 Query Operation Log window 4-31 SJ-20110531095035-006|2011-09-30(R1.Chapter 4 Fault Feedback Information Figure 4-27 Select Query Operation Log 2. In Query Operation Log window. or query all operation log. as shown in Figure 4-28. customize operation time to query. and click OK button.1) ZTE Proprietary and Confidential . 4.3.21 View NM version On client interface of NM system. After successfully querying. click Help > About.3. – End of Steps – 4. View time zone at server side by using command echo $TZ.22. export the log to excel.1 Emergency Maintenance Record List ReFeed- ceived back by Feedback time Contact by Contact person Phone No.20 View system time zone Steps 1. e-mail Source unit Fault Model Network capacity Version time.3. you can find current time zone in the option of region setting.1) ZTE Proprietary and Confidential . 2. – End of Steps – 4.ZXG10 iBSC Emergency Maintenance 3.22 Maintenance Record List 4. you can perform as follows: After opening control panel of client computer. symptom. and display NM version information. and description Attached pages 4-32 SJ-20110531095035-006|2011-09-30(R1.3. To view the time zone at client. 1) ZTE Proprietary and Confidential .Chapter 4 Fault Feedback Information Description of field procedure and handling Attached pages Field data feedback Attached pages Analysis and preliminary Attached pages com- Han- ments dled by Day Final comments and conclusion 4-33 SJ-20110531095035-006|2011-09-30(R1. 1) ZTE Proprietary and Confidential . 4-34 SJ-20110531095035-006|2011-09-30(R1.ZXG10 iBSC Emergency Maintenance This page intentionally left blank. .................... 4-15 Figure 4-10 Set the Type of Nofication NE ............................................... 4-12 Figure 4-5 Displaying history alarms of the selected NE...................................................... 4-13 Figure 4-7 Select Quick Search ........................................ 4-22 Figure 4-21 Save Signaling Trace Result . 4-10 Figure 4-3 Set the Type of Alarm NE............................... 4-25 Figure 4-25 OAM interface................................................................................................................................................................ 4-16 Figure 4-11 Notification Save Window ....................................................... 4-12 Figure 4-6 Select View Notifications .................................................................... 2-2 Figure 4-1 Select View History Alarms...................... 1-4 Figure 2-1 Data Backup Interface ...................................................... 4-18 Figure 4-14 Set Query Time of Performance Data ....................................................................................................................................................................................................................................................... 4-21 Figure 4-20 Select M3UA ............................................................................................. 4-14 Figure 4-9 Set query time of notification ...................................... 4-17 Figure 4-12 Select Performance Management and Performance Data Query ................................................................ 4-11 Figure 4-4 Alarm Save Window ................... 4-9 Figure 4-2 Set query time of alarm ............................... 4-31 I ...................................... 4-19 Figure 4-17 Parameter Setting interface......................................................................... 4-18 Figure 4-15 Set Query Object of Performance Data ............. 4-27 Figure 4-27 Select Query Operation Log ....................................................................................................................................................................................................................................... 2-2 Figure 2-2 Data Backup Result Interface....................................................................................................................................................................... 4-31 Figure 4-28 Query Operation Log window ................ 4-19 Figure 4-16 Select Basic Measurement Data of CS ........................................... 4-24 Figure 4-24 CS interface. 4-22 Figure 4-22 Signaling Trace Save Window ............................................. 4-17 Figure 4-13 Integrated Query Interface............................................................................................................................................ 4-13 Figure 4-8 Query Notification Window ... 4-20 Figure 4-18 Trace Setting interface................................................ 4-23 Figure 4-23 Parameter Setting interface at Abis ........................ 4-21 Figure 4-19 Select SCCP....Figures Figure 1-1 Flow of Emergency Maintenance .................................................................................................................................. 4-25 Figure 4-26 Trace Setting of PS service signal............................................................................... Figures This page intentionally left blank. . . 4-26 III ................................ 1-2 Table 4-1 Field Fault Feedback Report ....................................................................................... 4-3 Table 4-3 Feedback data required by NM faults .................................................... 4-2 Table 4-2 Feedback data required by BSC faults .............................................................. 1-1 Table 1-3 KPI Indicator.................................................................... 4-5 Table 4-4 Feedback data required by site faults . 4-5 Table 4-5 Dynamic Data Management Function............................................................... 1-1 Table 1-2 Alarm report on emergency maintenance ....Tables Table 1-1 User complaint .......................................................................................................................................................... Tables This page intentionally left blank. . Signaling Connection Control Part SDCCH .Stand alone Dedicated Control Channel TCH .Traffic Channel V .Mobile Switching Center NE .Network Element NMS .Operation & Maintenance Module SCCP .Glossary CPU .Network Management System OMM .Internet Protocol MSC .Central Processing Unit IP .