You are on page 1of 37

22

Debugging with gdb

3.3 Getting Help
You can always ask gdb itself for information on its commands, using the command help.
help
h

You can use help (abbreviated h) with no arguments to display a short list of
named classes of commands:
(gdb) help
List of classes of commands:
aliases -- Aliases of other commands
breakpoints -- Making program stop at certain points
data -- Examining data
files -- Specifying and examining files
internals -- Maintenance commands
obscure -- Obscure features
running -- Running the program
stack -- Examining the stack
status -- Status inquiries
support -- Support facilities
tracepoints -- Tracing of program execution without
stopping the program
user-defined -- User-defined commands
Type "help" followed by a class name for a list of
commands in that class.
Type "help" followed by command name for full
documentation.
Command name abbreviations are allowed if unambiguous.
(gdb)

help class
Using one of the general help classes as an argument, you can get a list of the
individual commands in that class. For example, here is the help display for
the class status:
(gdb) help status
Status inquiries.
List of commands:
info -- Generic command for showing things
about the program being debugged
show -- Generic command for showing things
about the debugger
Type "help" followed by command name for full
documentation.
Command name abbreviations are allowed if unambiguous.
(gdb)

help command
With a command name as help argument, gdb displays a short paragraph on
how to use that command.

BSC6900 GSM
V900R012C01

Commissioning Guide
Issue

06

Date

2011-05-19

HUAWEI TECHNOLOGIES CO., LTD.

Debugging with gdb
The gnu Source-Level Debugger
Tenth Edition, for gdb version 7.10.50.20151203-cvs
(GDB)

Richard Stallman, Roland Pesch, Stan Shebs, et al.

.

Address: Huawei Industrial Base Bantian. either express or implied. Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co. Huawei Technologies Co. 2011. The information in this document is subject to change without notice.Copyright © Huawei Technologies Co.com Email: support@huawei. Unless otherwise specified in the contract. and recommendations in this document are provided "AS IS" without warranties. guarantees or representations of any kind.. i . information.. information. All other trademarks and trade names mentioned in this document are the property of their respective holders. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co. Notice The purchased products. services and features described in this document may not be within the purchase scope or the usage scope.com Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Every effort has been made in the preparation of this document to ensure accuracy of the contents. services and features are stipulated by the contract made between Huawei and the customer. express or implied... Ltd. all statements. All or part of the products.huawei. Ltd. Longgang Shenzhen 518129 People's Republic of China Website: http://www. Ltd. All rights reserved. but all statements.. Ltd. and recommendations in this document do not constitute the warranty of any kind.

.

Ltd. It includes the following contents: Verifying the Operation and Maintenance Unit (OMU). Organization 1 Changes in the BSC6900 GSM Commissioning Guide This chapter describes the changes in the BSC6900 GSM Commissioning Guide. and MML command scripts required for commissioning must be ready. and Verifying the Interfaces and Services. Connecting the BSC6900 to the M2000. BSC6900 board software and data file loading. 3 Commissioning Process Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.BSC6900 GSM Commissioning Guide About This Document About This Document Overview BSC6900 commissioning is performed after the hardware is installed and before the services are provided. Product Name Product Version BSC6900 V900R012C01 Intended Audience This document is intended for field engineers. Activating and Verifying the License. 2 Prerequisites for Commissioning Before the BSC6900 commissioning. The software installation package. and services.. Product Version The following table lists the product version related to this document. the status of the equipment and the network to be commissioned must meet the conditions required. It aims to ensure that the BSC6900 can work properly by performing verification tasks related to equipment. iii . interfaces. license. This document provides guidelines for commissioning the BSC6900. Loading the BSC6900 Board Software and Data Files.

6 Logging in to the BSC6900 Through the LMT This section describes how to log in to the BSC6900 through the LMT and enable the normal communication. Ltd. 13 Verifying the GSM Services This chapter describes how to verify that the GSM basic services and the feature services that are enabled are normal. 5 Verifying the OMU This section describes how to verify the OMU to enable the normal communication between the LMT and the BSC6900. The feature services consist of the inter-RAT handover. Issue 06 (2011-05-19) . thus preventing the alarms from affecting the verification of services. ensure that the cabinet is powered on and operates normally. The OMU verification involves installing the OMU operating system and OMU application. 8 Activating and Verifying the License This chapter describes how to activate the license and verify the licensed configuration information to enable service checking. A. location service. LMT verification ensures the BSC6900 commissioning through the LMT. Gb. checking the OMU operation status. the Lb interface verification is mandatory when the external SMLC is used on the BSC6900. 4 Checking Operating Status of Hardware Before verifying the equipment. which is performed by both the remote engineer and the site engineer. and AMR service. The interfaces to be verified are Abis. 10 Connecting the BSC6900 to the M2000 This chapter describes how to connect the BSC6900 to the M2000 for the centralized management. and Lb interfaces. 12 Handling the Alarms Generated During the Commissioning This chapter describes how to handle the alarms generated during the commissioning. 11 Verifying Interfaces This section describes how to verify interfaces. the Pb interface verification is mandatory when the external PCU is used on the BSC6900. There is also another commissioning mode: remote commissioning through local assistance.. The basic services consist of speech service and data service. Pb. Remote commissioning is performed by the remote engineer (technical owner of the BSC) and multiple BSCs can be commissioned simultaneously in the central equipment room. Ater.BSC6900 GSM Commissioning Guide About This Document The BSC6900 commissioning can be performed remotely or locally. 9 Loading BSC6900 Board Software and Data Files This chapter describes how to load the BSC6900 board software and data files to enable the normal operation of the BSC6900. The Ater interface verification is mandatory in BM/TC separated mode. Local commissioning is performed by the site engineer (commissioning owner in the BSC equipment room) who connects a PC to the BSC and performs the commissioning through the LMT. iv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. and changing the external fixed IP address and external virtual IP address of the OMU on site. 7 Updating the OMU Database This describes how to update configuration data in the OMU database by running MML commands.

(Send bugs and comments on gdb to http://www. Permission is granted to copy. Fifth Floor. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom.11 Published by the Free Software Foundation 51 Franklin Street. MA 02110-1301. USA ISBN 978-0-9831592-3-0 Copyright c 1988-2015 Free Software Foundation. with the Invariant Sections being “Free Software” and “Free Software Needs Free Documentation”.org/software/gdb/bugs/. distribute and/or modify this document under the terms of the GNU Free Documentation License. Inc.gnu. Boston.” and with the Back-Cover Texts as in (a) below. with the Front-Cover Texts being “A GNU Manual. Version 1.) Debugging with gdb TEXinfo 2011-02-14.3 or any later version published by the Free Software Foundation.” . (a) The FSF’s Back-Cover Text is: “You are free to copy and modify this GNU Manual.

Context Select a verification method according to the actual scenario.1 Verifying Interfaces Through M2000 This section describes how to verify interfaces through the maintenance mode and the NE health check function of the M2000. Ater. Pb.. The Ater interface verification is mandatory in BM/TC separated mode. Gb. the Pb interface verification is mandatory when the external PCU is used on the BSC6900. 11. Ater.2 Verifying Interfaces Through LMT This chapter describes how to verify interfaces on the BSC6900 through MML commands or GUI on the LMT. Gb. the Pb interface verification is mandatory when the external PCU is used on the BSC6900. 11-1 . The Ater interface verification is mandatory in BM/TC separated mode. the Lb interface verification is mandatory when the external SMLC is used on the BSC6900. Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The interfaces to be verified are Abis. the Lb interface verification is mandatory when the external SMLC is used on the BSC6900. and Lb interfaces. A. The interfaces to be verified are Abis. and Lb interfaces. 11. Pb. Ltd.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces 11 Verifying Interfaces About This Chapter This section describes how to verify interfaces. A.

11. the NE enters the normal mode automatically. l The maintenance modes are effective for the UE during Start Time and End Time.1.2 Verifying Interfaces Automatically This section describes how to verify the BSC6900 interfaces automatically through NE health check on the M2000. four maintenance modes are provided on the M2000: Install. ----End 11. Upgrade. the alarms that are not cleared when the NE is in the Install mode are reported to the M2000 as common alarms. set the maintenance mode to Install. For details. Issue 06 (2011-05-19) . and the hardware installation acceptance is passed. Prerequisite l The BSC6900 and the peer equipment are physically connected.1. the NE may report many alarms that require no attention.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces 11.1 Setting Maintenance Mode of NE to Install During the commissioning. you can set the UE mode to Normal manually.1.1 Verifying Interfaces Through M2000 This section describes how to verify interfaces through the maintenance mode and the NE health check function of the M2000. 11. In addition. When NEs are in the Normal mode. and Testing. Before Start Time and after End Time. l All the subracks of the BSC6900 are running normally.8 Setting Maintenance Mode for NE. Context Procedure Step 1 Set the maintenance mode of the NE to Install on the M2000 client. In the BSC6900 commissioning scenario. see 15. Ltd.. 11. see 10 Connecting the BSC6900 to the M2000). 11-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Expand. alarms are reported normally.1. 11. NEs are in the Normal mode. l When the NE is restored to the Normal mode.2 Verifying Interfaces Automatically This section describes how to verify the BSC6900 interfaces automatically through NE health check on the M2000.1 Setting Maintenance Mode of NE to Install During the commissioning. l Currently.3 Setting the Maintenance Mode of the NE to Normal After the End Time of the maintenance mode. the NE may report many alarms that require no attention. You can shield these alarms by setting the maintenance mode of the NE to be in Install mode.1. l The BSC6900 is connected to the M2000 (for details. You can shield these alarms by setting the maintenance mode of the NE to be in Install mode.

3. The Create Task dialog box is displayed. 4.2.2. Click OK. Select the NEs for health check (deselect those not for health check) in the Interface Check under Check Items. Select the NE for health check in under Select NE. Click Scenario Management on the displayed tab page. The Time Setting dialog box is displayed. 2. Select the option to kick off the task in under Time Setting. A dialog box is displayed. 2. The Name text box is automatically filled in with the text consisting of the application scenario and the specific time (the time is accurate to the second) on which the task is created. Select the application scenario corresponding to the task that is currently created from the Scenario drop-down list. 5. Step 2 Create the NE health check task. NOTE The setting of Time Setting is not required during commissioning. Click OK to complete the setup of the NE health check scenario. l All the subracks of the BSC6900 are running normally. Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Context The Lb interface and the internal interface should be verified through MML commands or GUI on the LMT. Enter the scenario name in the Scenario Name text box on the right of the dialog box. The options are as follows: Operation Mode Description Instant Click Next. Procedure Step 1 Set the scenario for NE health check. 7. 3. Ltd. prompting that the NE health check scenario is set up successfully. Click New in the displayed dialog box.7 Verifying the Internal Interfaces for details. click New. 1. that is BSC6900 GSM. and the hardware installation acceptance is passed. On the M2000 client. Click the type of the NE for health check in NE Types.6 Verifying Lb Interface and 11. l The BSC6900 is connected to the M2000 (see 10 Connecting the BSC6900 to the M2000 for details). 11-3 .BSC6900 GSM Commissioning Guide 11 Verifying Interfaces Prerequisite l The BSC6900 and the peer equipment are physically connected. NOTE The scenario name must be different from existing scenario names. see 11. Click Finish. choose Maintenance > NE Health Check. 4. 6. 1. On the NE Health Check tab page..

Click Save As.. Right-click the corresponding task on the right and then click View Report from the shortcut menu. If. you can set the UE mode to Normal manually. the corresponding interface is faulty. and then select the path for saving the report in the displayed Save dialog box to save the report in HTML format. Periodic Click Next.zip file.html” in the zip file browser. and then click Finish..1. Period. and then click Finish. Issue 06 (2011-05-19) .. l Click Save As. Under the Finished Tasks node of the navigation tree. Ltd. ----End 11. In the displayed Health Check Report dialog box. Set Start Time. To view the report. and then double-click the report file “index. In addition. NOTE The health check report is compressed to a zip file. Set Health Check Period in the displayed dialog box. Then.. 2. 1. and then select the path for saving the report in the displayed Save dialog box to save the report in Word format. click the HTML Format tab or DOC Format tab to view the report. You selected DOC Format. and then view the report in one of the following ways: l Click Open to directly open the report in HTML format. the NE enters the normal mode automatically. Select the report from the report list. Rectify the fault by referring to the health check report. Step 3 View the result of the NE health check. Click Next. click the executed task.3 Setting the Maintenance Mode of the NE to Normal After the End Time of the maintenance mode. You selected the HTML Format.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces Operation Mode Description Scheduled Set the time for kicking off the task in the Scheduled spin box. double-click the . 11-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. NOTE The executed health check tasks are listed under the Finished Tasks node on the navigation tree on the left of the NE Health Check tab page. and Run Times. If some items in the health check report are in red..

and Lb interfaces. l The BSC6900 has passed the commissioning. The interfaces to be verified are Abis. Procedure Step 1 Set the maintenance mode of the NE to Normal on the M2000 client.3 Verifying the Gb Interface This section describes how to verify the Gb interface. 11.2. 11. 11. The A interface verification varies according to the transmission mode of the A interface. 11.1 Setting Maintenance Mode of NE to Install. the Pb interface verification is mandatory when the external PCU is used on the BSC6900.2 Verifying the A Interface This section describes how to verify the control plane and the user plane of the A interface. see 15. When E1/T1 transmission is applied. ----End 11. Pb.1 Verifying the Abis Interface This section describes how to verify the control plane and the user plane of the Abis interface. before running the MML command DSP ADJNODE. l Before verifying interfaces. Pb interface verification is needed. The Ater interface verification is mandatory in BM/TC separated mode. Ater.2. the Lb interface verification is mandatory when the external SMLC is used on the BSC6900. The Abis interface verification varies according to the transmission mode over the Abis interface. Context During the interface verification. For example. 11. the data link layer adopts TDM transmission. Gb. When FE/GE transmission is applied. set the maintenance mode for the NE by referring to 11. The Gb interface verification varies according to the transmission mode over the Gb interface.7 Verifying the Internal Interfaces Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2. you can run the LST command to view the configuration information. 11.5 Verifying the Pb Interface If the BSC6900 is configured with an external PCU.1. you can run the MML command LST ADJNODE to check the parameter Adjacent Node ID. the data link layer adopts IP transmission. Ltd.8 Setting Maintenance Mode for NE. 11-5 .2 Verifying Interfaces Through LMT This chapter describes how to verify interfaces on the BSC6900 through MML commands or GUI on the LMT.4 Verifying the Ater Interface This section describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces Prerequisite l The BSC6900 is connected to the M2000 (see 10 Connecting the BSC6900 to the M2000 for details).2. 11.6 Verifying Lb Interface This section describes how to verify the Lb interface. Both E1/T1 transmission and FE/GE transmission can be applied on the Lb interface..2. A.2.2. For details.

2. There are two ways to verify the Abis interface (Abis over TDM): through GUI or through MML. and Port No. Prerequisite l The BSC6900 and the base stations are physically connected. see Verifying the Abis Interface (Abis over TDM) Through GUI. and there is no timeslot with the State of Failure. Expected result: The State of many timeslots is Idle.2. Expected result: The value of UsageStatus is Normal. If the status of LAPD links on the Abis interface is abnormal. Run the MML command DSP LAPDLNK to check whether the Link Access Protocol on the D channel (LAPD) link on the Abis interface is normal. check the transmission link by referring to 15. l All the subracks of the BSC6900 are running normally. Ltd. Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces This describes how to verify the link status of the ports on the TNUa and SCUa boards. Context For the commissioning of the base station. l Verifying the Abis interface (Abis over TDM) through MML 1. check the transmission link by referring to 15. 11. Run the MML command DSP BTSSTAT to query the status of cells and channels.1 Checking the Transmission Link. Procedure l To verify the Abis interface (Abis over TDM) through GUI. and the hardware installation acceptance is passed. run the MML command LST BTSCONNECT.1 Verifying the Abis Interface This section describes how to verify the control plane and the user plane of the Abis interface. The following takes one base station as an example to describe the commissioning process on the Abis interface.. see the commissioning guide of the base station. 3.1 Checking the Transmission Link. repeat the operations. If the status of timeslots on the Abis interface is abnormal. You can choose either way according to your convenience. Slot No.. l You have logged in to the BSC6900 through the LMT. Issue 06 (2011-05-19) . Run the MML command DSP ABISTS to query the timeslot status of the Abis interface. l The base stations used to verify the Abis interface are commissioned and the cell configuration is complete.. NOTE To query the Subrack No. 11-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. If multiple base stations are connected. The Abis interface verification varies according to the transmission mode over the Abis interface. of the timeslots to be verified.

If the status of LAPD links on the Abis interface is abnormal. NOTE To query the number of the HDLC link to be verified. If the values of available bandwidth are all 0. see 15. check the transmission link by referring to 15. If the value of Cell Initialized is No. see ALM-21801 GSM Cell out of Service for troubleshooting. see ALM-21801 GSM Cell out of Service for troubleshooting. Ltd. Expected result: The values of available bandwidth are not all 0. Run the MML command DSP ADJNODE to query the status of the adjacent node. run the MML command LST BTSABISHDLCPATH. Run the MML command DSP LAPDLNK to check whether the LAPD link on the Abis interface is normal. Expected result: The value of UsageStatus is Normal. Expected result: The value of Operation state is Available. If the value of Operation state is Unavailable. Issue 06 (2011-05-19) Run the MML command DSP BTSSTAT to query the status of the cells and channels. 3. Run the MML command DSP IPPATH to query the status of the IP path on the Abis interface. check the alarms related to the TRX and rectify the fault according to the alarm handling suggestion. 2. Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No. 11-7 . l Verifying the Abis interface (Abis over HDLC) 1. check the transmission link by referring to 15. If the status of LAPD links on the Abis interface is abnormal. Run the MML command DSP HDLCLNK to query the status of the HDLC link.1 Checking the Transmission Link. see EVT-22918 Change of Transport Resource State for Adjacent Node User Plane for troubleshooting. check the transmission link by referring to 15.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces If the value of Cell Initialized is No. check the alarms related to the TRX and rectify the fault according to the alarm handling suggestion. if the value of Cell Initialized is Yes but the value of Channel Fault is Yes. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Run the MML command DSP BTSSTAT to query the status of the cells and channels. if the value of Cell Initialized is Yes but the value of Channel Fault is Yes.. 3. 2.1 Checking the Transmission Link. Expected result: The value of operation state is Available and the value of Available Tx Bandwidth or Available Rx Bandwidth is not 0.1 Checking the Transmission Link. l Verifying the Abis interface (Abis over IP) 1. If the status of LAPD links on the Abis interface is abnormal. Run the MML command DSP LAPDLNK to check whether the LAPD link on the Abis interface is normal. 4.4 IP Connection Setup Failure for troubleshooting. Expected result: The value of UsageStatus is Normal.

check the alarms related to the TRX and rectify the fault according to the alarm handling suggestion. Issue 06 (2011-05-19) . If the value of Operation state is Unavailable.1 Checking the Transmission Link. Ltd. check the transmission links by referring to 15.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces Expected result: The value of Cell Initialized is Yes and the value of Channel Fault is No. if the value of Cell Initialized is Yes but the value of Channel Fault is Yes. Procedure l To verify the A interface (A over TDM) through GUI..2. see Verifying the A Interface (A over TDM) Through GUI. Expected result: The value of Link State is IN SERVICE. You can choose either way according to your convenience. Run the MML command DSP MTP2LNK to query the status of the Message Transfer Part Level 2 (MTP2) signaling link. l The Ater interface has been verified when the BSC6900 is in BM/TC separated mode. 3. If the value of SSN state is Prohibited. l All the subracks of the BSC6900 are running normally. Run the MML command DSP SSN to query the status of the SCCP SSN. ----End 11. l You have logged in to the BSC6900 through the LMT. The A interface verification varies according to the transmission mode of the A interface. l The MSC used to verify the A interface operates normally. l Verifying the A interface (A over TDM) through MML 1. Expected result: The value of SSN state is Allowed. Context There are two ways to verify the A interface (A over TDM): through GUI or through MML. Run the MML command DSP MTP3LNK to query the status of the Message Transfer Part Level 3 (MTP3) signaling link. If the value of Link State is OUT OF SERVICE. 11-8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2 Verifying the A Interface This section describes how to verify the control plane and the user plane of the A interface. 2. If the value of Cell Initialized is No. see ALM-21506 MTP3 Signaling Link Faulty for troubleshooting. see ALM-21801 GSM Cell out of Service for troubleshooting. Prerequisite l The BSC6900 and the MSC are physically connected. see ALM-21521 SCCP Subsystem Prohibited for troubleshooting. Expected result: The value of Operation state is Available.

5. If the value of Operation state is Unavailable. check the transmission links by referring to 15. see ALM-21521 SCCP Subsystem Prohibited for troubleshooting.1 Checking the Transmission Link. 4. Run the MML command DSP SCTPLNK to query the status of the Stream Control Transmission Protocol (SCTP) link. 5. If the value of CIC State is Failure. l Verifying the A interface (A over IP) 1. If the value of Operation state is not normal. check the transmission links by referring to 15. Ltd. Run the MML command DSP ACIC to query the status of A interface circuits. Run the MML command DSP SSN to query the status of the SCCP SSN. Expected result: The value of Operation state is Activated state. see ALM-21506 MTP3 Signaling Link Faulty for troubleshooting. Expected result: The value of SCCP DSP state is Accessible. Run the MML command DSP ADJNODE to query the status of the adjacent node. Expected result: The value of SCCP DSP state is Accessible. If the value of SSN state is Prohibited. and there is no CIC with the CIC State of Failure. Expected result: The value of SCTP link Operation state is Normal. If the value of SCCP DSP state is not normal. 11-9 . NOTE To query the OPC Index and DPC Group Index of the E1/T1 to be verified on the A interface. Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. NOTE Run the MML command DSP SCTPLNK for two or three times. Expected result: The CIC State of many CICs is Idle.1 Checking the Transmission Link. Run the MML command DSP N7DPC to query the status of the SS7 destination signaling point. Expected result: The values of available bandwidth are not all 0.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces 4. Run the MML command DSP M3LNK to query the status of the MTP3 User Adaption Layer (M3UA) signaling link.. you can infer that the SCTP link is normal without intermittent disconnection. see ALM-21521 SCCP Subsystem Prohibited for troubleshooting. see ALM-21521 SCCP Subsystem Prohibited for troubleshooting. 3. Expected result: The value of SSN state is Allowed. Run the MML command DSP N7DPC to query the status of the SS7 destination signaling point. If the value of SCCP DSP state is not normal. 2. if the value of Operation state is always Normal and the value of State Changed Time does not change. run the MML command LST AE1T1.

Run the MML command DSP IPPATH to query the status of the IP path. l All the subracks of the BSC6900 are running normally. ----End 11. Prerequisite l The BSC6900 and the SGSN are physically connected. and the hardware installation acceptance is passed. Issue 06 (2011-05-19) . Run the MML command DSP NSVC to query the status of the Network Service Virtual Connection (NSVC) to be verified. 2.. 3. l Verifying the Gb interface links (Gb over FR) Procedure 1.2. 11-10 Run the MML command DSP PTPBVC to query the status of the PTP BSSGP Virtual Connection (PTPBVC) of the NSE to be verified.3 Verifying the Gb Interface This section describes how to verify the Gb interface. Expected result: The value of SIG BVC State is Normal. Expected result: The value of BC Service State is available. The Gb interface verification varies according to the transmission mode over the Gb interface. run the MML command LST NSE. l The SGSN equipment used to verify the Gb interface operates normally. 4. If the value of BC Administration State is Blocked. NOTE To query the configuration of the NSE to be verified. If the status remains abnormal. the SGSN may be configured with an NSE that has a different NSE ID. see EVT-22918 Change of Transport Resource State for Adjacent Node User Plane for troubleshooting. If the value of SIG BVC State is Fault. Run the MML command DSP BC to query the status of the Bearer Channel (BC) to be verified. l You have logged in to the BSC6900 through the LMT. Run the MML command DSP SIGBVC to query the SIG BSSGP Virtual Connection (SIGBVC) status of the Network Service Entity (NSE) to be verified.4 IP Connection Setup Failure for troubleshooting. see the "Follow-up procedure" for troubleshooting.1 Checking the Transmission Link. 6. If the value of Operation state is Unavailable.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces If the values of available bandwidth are all 0. If the value of Service State is not normal. check the transmission links by referring to 15. run the MML command UBL BC to unblock the BC. Expected result: The value of NSVC Service State is Active Unblock. and then run the MML command DSP BC to check whether the BC status is normal. Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. see 15. Expected result: The value of Operation state is Available.

see the Postrequisites below for troubleshooting. 3. Run the MML command DSP PTPBVC to query the PTPBVC status of the NSE to be verified. If the value of NSVL State is Fault. 11-11 . If the value of Service State is not normal.1 Checking the Transmission Link. Run the MML command DSP GBIPROUTE to query the status of the IP connection to be verified on the Gb interface. If the value of State is Faulty. Expected result: The value of Service State is Normal. l Verifying the Gb interface links (Gb over IP) 1. NOTE To query the configuration of the local or remote NSVL to be verified.. run the MML command LST NSVLLOCAL or LST NSVLREMOTE. NOTE To query the configuration of the NSE to be verified. Expected result: The value of NSVL State is Normal. Run the MML command DSP NSVL to query the status of the Network Service Virtual Link (NSVL) to be verified. ----End Follow-up Procedure Handling Suggestions to Exceptional NSVC Status l If the value of NSVC Manage State is Unblock and the NSVC Service State is Active Block. check the transmission links by referring to 15. Expected result: The value of SIG BVC State is Normal. run the MML command DSP IPRT to check whether the route configuration on the Gb interface is correct. 4. 1.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces Expected result: The value of Service State is Normal. you can infer that the FR link that bears the NSVC is functional and that the NSVC is blocked by the SGSN. you can infer that the FR link that bears the NSVC is functional and that the NSVC is blocked by the BSC6900 or by both the BSC6900 and the SGSN. l If the value of NSVC Manage State is Block and the NSVC Service State is Active Block. Run the MML command DSP SIGBVC to query the SIGBVC status of the NSE to be verified. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. run the MML command LST NSE. If the value of SIG BVC State is Fault. Expected result: The value of State is Normal . Ltd. Issue 06 (2011-05-19) Run the MML command UBL NSVC to unblock the BSC6900. 2. If the value of Service State is not normal. see the Postrequisites below for troubleshooting. the SGSN may be configured with an NSE that has a different NSE ID.

If the status remains abnormal. Context There are two ways to verify the Ater interface: through GUI or through MML. 4. l The data configuration on the Ater interface is complete. If the value of PTPBVC Manage State is Block. Run the MML command DSP ATERTS to query the status of timeslots on the Ater interface. go to step 2. If the status remains abnormal. 11. If the value of NSVC Service State is still Active Block. l You have logged in to the BSC6900 through the LMT. – The NSVC configured on the same BC at the SGSN is not the required one. Run the MML command RST PTPBVC to reset the PTPBVC.2. Issue 06 (2011-05-19) . l Verifying the Ater Interface through MML 1. and then run the MML command DSP PTPBVC to query the status of the PTPBVC. Procedure l To verify the Ater interface through GUI.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces 2. Handling Suggestions to Exceptional PTPBVC Service Status 1. If the status remains abnormal. You can choose either way according to your convenience. Expected result: The State of many timeslots is Idle. l Run the MML command DSP NSVC to query the status of the NSVC. and there is no timeslot with the State of Failure. If the value of NSVC Service State is Deactive Block. 11-12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd. the possible causes are as follows: – The NSVC ID and NSE ID of the NSVC on the BSC6900 are inconsistent with that on the SGSN. 3. If the status remains abnormal. and then run the MML command DSP PTPBVC to query the status of the PTPBVC. run the MML command UBL PTPBVC to unblock the PTPBVC. go to step 3. and then run the MML command DSP PTPBVC to query the status of the PTPBVC. and then run the MML command DSP PTPBVC to query the status of the PTPBVC. l The TCS is loaded and started. Run the MML command RST PSCELL to reset the cell corresponding to the exceptional PTPBVC. 2.4 Verifying the Ater Interface This section describes how to verify the Ater interface when the BSC6900 is in BM/TC separated mode. contact the Huawei Customer Service Center by referring to Contact the Huawei Customer Service Center. see Verifying the Ater Interface Through GUI. go to step 4. Run the MML command RST SIGBVC to reset the SIGBVC corresponding to the exceptional PTPBVC.. Prerequisite l The MPS/EPS and the TCS are physically connected. you can infer that the NSVC is blocked by the SGSN.

run the MML command LST ATERE1T1. the data Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Prerequisite l The PCU used to verify the Pb interface operates normally. ----End 11. 11-13 . run the MML command LST PBE1T1.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces If the State of a timeslot is Failure. If the status of a CIC is Failure. Expected result: The status of many circuit identity codes (CICs) is Idle. Procedure Step 1 Run the MML command DSP LAPDLNK to check whether the LAPD link on the Pb interface is normal. l All the subracks of the BSC6900 are running normally. l The BSC6900 and the PCU are physically connected. Ltd. run the MML command DSP ATERSL to query whether the Ater signaling link is normal. check the transmission links by referring to 15. check the transmission links by referring to 15. NOTE To query the Ater connection path index and ID of BSC in TC Pool of the E1/T1 to be verified on the Ater interface. ----End 11.5 Verifying the Pb Interface If the BSC6900 is configured with an external PCU. and the hardware installation acceptance is passed. check the transmission links by referring to 15.1 Checking the Transmission Link. NOTE To query the E1/T1 configuration information to be verified on the Pb interface. If the value of UsageStatus is Faulty. and there is no CIC with the status of Failure. Step 2 Run the MML command DSP PBCIC to query the status of the circuit on the Pb interface.6 Verifying Lb Interface This section describes how to verify the Lb interface.1 Checking the Transmission Link. check the transmission link by referring to 15.2. Pb interface verification is needed. Expected result: The value of UsageStatus is Normal. When E1/T1 transmission is applied.1 Checking the Transmission Link.1 Checking the Transmission Link. l You have logged in to the BSC6900 through the LMT. 2.. Both E1/T1 transmission and FE/GE transmission can be applied on the Lb interface. Optional: If the TCS is configured remotely. Expected result: The value of UsageStatus is Normal. If the status of LAPD links on the Pb interface is abnormal.2.

the data link layer adopts IP transmission. see 11.2. Context There is no dedicated interface board for the Lb interface. l You have logged in to the BSC6900 through the LMT.2. l When the data link layer of the Lb interface is carried on the Ater interface board. or Ater interface board. Procedure l When the data link layer of the Lb interface is carried on the Abis interface board. Step 2 Run the MML command DSP PANELPORT to query the link status of the ports on the SCUa boards. l When the data link layer of the Lb interface is carried on the A interface board. l All the subracks of the BSC6900 are running normally. A interface board.2 Verifying the A Interface.4 Verifying the Ater Interface. Prerequisite l The BSC and the Serving Mobile Location Center (SMLC) are physically connected. For details.2.. see 11. If the value of Link Status is Failure. Ltd.7 Verifying the Internal Interfaces This describes how to verify the link status of the ports on the TNUa and SCUa boards. Issue 06 (2011-05-19) . The data link layer of the Lb interface can be carried on the Abis interface board.2. For details. ----End 11. l The SMLC that is used to verify the Lb interface operates normally. verify the Lb interface in the same way as for the Abis interface.1 Verifying the Abis Interface. Procedure Step 1 Run the MML command DSP LINKBTNUTNU to query the link status of the ports on the TNUa boards. Expected result: The value of Link Status is Normal. see 11. l You have logged in to the BSC6900 through the LMT. 11-14 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. verify the Lb interface in the same way as for the A interface. Expected result: The actual link status of the ports on the SCUa boards are displayed in the returned result.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces link layer adopts TDM transmission. For details. verify the Lb interface in the same way as for the Lb interface. When FE/GE transmission is applied. re-install the inter-TNUa cables as required in the returned result by referring to Installing the Inter-TNUa Cables. Prerequisite l The inter-TNUa cables and inter-SCUa cables of the BSC6900 are installed. l All the subracks of the BSC6900 are running normally.

Ltd.BSC6900 GSM Commissioning Guide 11 Verifying Interfaces If the link status in the returned result does not meet the installation requirements.. ----End Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 11-15 . re-install the inter-SCUa cables by referring to Installing the Inter-SCUa Cables Between Different Subracks.

.

Go to step Step 3... Step 2 Check whether alarms are listed on the Fault tab page. No alarm is listed.BSC6900 GSM Commissioning Guide 12 12 Handling the Alarms Generated During the Commissioning Handling the Alarms Generated During the Commissioning This chapter describes how to handle the alarms generated during the commissioning. Step 4 Click Solution. Ltd.. The Detail dialog box is displayed. End this task. The LMT Online Help interface is displayed. One or more alarms are listed.. Step 5 Follow the suggestions to handle the alarm. Procedure Step 1 Click the Alarm on the LMT main page. thus preventing the alarms from affecting the verification of services. 12-1 .. ----End Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Step 3 Double-click the alarm to be handled in the fault tab page. Prerequisite l The communication between the BSC6900 and the OMU is normal.. l You have logged in to the BSC6900 through the LMT. Then. If.. Step 6 Repeat Step 3 to Step 5 to handle other alarms.. The Alarm tab page is displayed.

.

The verification over Ater interface is mandatory only in BM/TC separated mode. The connection success rate is higher than 90%.BSC6900 GSM Commissioning Guide 13 Verifying the GSM Services 13 Verifying the GSM Services This chapter describes how to verify that the GSM basic services and the feature services that are enabled are normal. The verification over Lb interface is mandatory only if the BSC6900 is configured with an external SMLC. Gb. Make 20 calls from a fixed-line phone to an MS and hold on each call for 60 seconds. The voice is clear and without loud noise. No call drop occurs and the system resources are released normally after the call is terminated. Ltd. and Lb interfaces is successful. The verification over Pb interface is mandatory only if the BSC6900 is configured with an external PCU. A. Prerequisite l The verification over the Abis. 13-1 . No call drop occurs and the system resources are released normally after the call is terminated. The connection success rate is higher than 90%. The basic services consist of speech service and data service. The voice is clear and without loud noise. The feature services consist of the inter-RAT handover. l The MSs used for test are functional and are registered in the HLR. and AMR service. Pb.. Table 13-1 Performing dialing tests on the basic services Issue 06 (2011-05-19) Basic Services Procedure for Conducting the Dialing Test Expected Result Speech service Make 20 calls from an MS to a fixed-line phone and hold on each call for 60 seconds. Procedure Step 1 Table 13-1 lists the procedure for verifying the basic services by testing the MS in the BTS cells. l You have logged in to the BSC6900 through the LMT. location service. Ater. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

start message tracing on the LMT over the Um. No call drop occurs and the system resources are released normally after the call is terminated. Step 2 Table 13-2 lists the procedure for verifying the feature services by testing the MS in the BTS cells. Abis. The location of the MS conforms to the precision requirements. Hand over a dual-mode MS from the UMTS to the GSM for 20 times. Where the message tracing over the Pb interface is mandatory only when the BSC6900 is configured with an external PCU. ----End 13-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Pb. Then.. Test the General Packet Radio Service (GPRS) or Enhanced Data Rate for GSM Evolution (EDGE) function on the MS. Adaptive Multi Rate (AMR) service Make 50 calls from an MS to a fixed-line phone and select voice version to AMR. The connection success rate is higher than 90%. NOTE If the result of service verification cannot meet the expected results. Ltd. Gb. The voice is clear and without loud noise. The connection success rate is higher than 90%. Table 13-2 Performing dialing tests on the feature services Feature Services Procedure for Conducting the Dialing Test Expected Result Inter-RAT handover Hand over a dual-mode MS from the GSM to the UMTS for 20 times. locate the MS. Send a fax from an MS to an electrograph.BSC6900 GSM Commissioning Guide 13 Verifying the GSM Services Basic Services Data service Procedure for Conducting the Dialing Test Expected Result Make 20 calls from an MS to another MS and hold on each call for 60 seconds. Issue 06 (2011-05-19) . Send a fax from an electrograph to an MS. and the message tracing over the Ater interface is mandatory only in BM/TC separated mode. Faxes are sent and received normally. and Ater interfaces. Location service Make a call from the MS and hold on the call. The voice is clear and without loud noise. A. The connection success rate is higher than 90%. The test data rate is similar to the data rate tested in a lab. The voice is clear and without loud noise.

. l The alarms generated before the switchover have been cleared. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. For details. The voice is clear and without loud noise.BSC6900 GSM Commissioning Guide 14 Verifying Network Reliability 14 Verifying Network Reliability The network reliability is verified by alarm checks and dialing tests after the active/standby switchover of boards. see Table 14-1. 14-1 . Step 3 Use an MS in a cell under the BTS to perform basic services and verify the services. The connection success rate is higher than 90%. see 12 Handling the Alarms Generated During the Commissioning. Step 2 Check and handle the alarms generated during the active/standby switchover. For details. For details. l You have logged in to the BSC6900 through the LMT. Procedure Step 1 Switch over the active/standby boards. Prerequisite l The standby board for the switchover operates normally. Table 14-1 Performing dialing tests on the basic services Issue 06 (2011-05-19) Basic Services Procedure for Conducting the Dialing Test Expected Result Speech service Make 20 calls from an MS to a fixed-line phone and hold on each call for 60 seconds. No call drop occurs and the system resources are released normally after the call is terminated. see Switching Over the BSC Boards. Ltd. l All the subracks of the BSC6900 are running normally.

Send a fax from an MS to an electrograph. The voice is clear and without loud noise. ----End 14-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.BSC6900 GSM Commissioning Guide 14 Verifying Network Reliability Basic Services Data service Procedure for Conducting the Dialing Test Expected Result Make 20 calls from a fixed-line phone to an MS and hold on each call for 60 seconds. The connection success rate is higher than 90%.. Faxes are sent and received normally. Issue 06 (2011-05-19) . The connection success rate is higher than 90%. Make 20 calls from an MS to another MS and hold on each call for 60 seconds. No call drop occurs and the system resources are released normally after the call is terminated. Ltd. No call drop occurs and the system resources are released normally after the call is terminated. Test the General Packet Radio Service (GPRS) or Enhanced Data Rate for GSM Evolution (EDGE) function on the MS. Send a fax from an electrograph to an MS. The voice is clear and without loud noise. The test data rate is similar to the data rate tested in a lab.

6 Performing the Loopback Test on the E1/T1 Port This section describes how to perform the loopback test to check whether the E1/T1 port is functional. optical port. 15. 15. 15.2 Unavailable E1/T1 Port This section describes how to handle the problem that the E1/T1 port is unavailable.5 Board Data Loading Failure This section describes how to handle the failures that occur during data loading to the BSC6900 board. 15.1 Checking the Transmission Link This section describes how to verify that the terrestrial transmission links of the BSC6900 are functional.8 Setting Maintenance Mode for NE Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 15.7 Performing the Loopback Test on the Optical Port This section describes how to perform the group loopback test to check whether the optical port is functional.3 Unavailable FE/GE Port This section describes how to handle the problem that the FE/GE port is unavailable. and upper-layer link. 15. Ltd. 15.. 15-1 . The verification covers E1/T1 port.BSC6900 GSM Commissioning Guide 15 FAQ 15 FAQ About This Chapter This chapter describes how to handle the common problems encountered during the commissioning. 15. FE/GE port.4 IP Connection Setup Failure This section describes how to handle the failures during IP connection setup.

NOTE If the upper-layer link is not functional. Procedure Table 15-1 Methods for checking the status of transmission link in different transmission modes If the transmission on the interface is over. 3. PPP/MLPPP transmission mode 2. run the MML command DSP PPPLNK to check the status of the PPP link. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l You have logged in to the BSC6900 through the LMT. check the status of the optical port.. Issue 06 (2011-05-19) . E1/T1 transmission mode Check the status of the E1/T1 port. FE/GE port. IP 1. If the channelized STM-1 transmission is used on the interface.BSC6900 GSM Commissioning Guide 15 FAQ 15. l For the PPP transmission mode. The verification covers E1/T1 port. Then. Check the status of the E1/T1 port. and upper-layer link. Prerequisite l All the subracks of the BSC6900 are running normally. Check the status of the upperlayer link. l For the MLPPP transmission mode. run the MML command LST PPPLNK/LST MPGRP accordingly to check whether the data configuration on the interface is correct. l Check the status of the transmission link based on the transmission mode. run the MML command DSP MPGRP to check the status of the MLPPP group. TD M 15-2 IP over Ethernet transmission mode Check the status of the FE/GE port. Ltd. optical port..1 Checking the Transmission Link This section describes how to verify that the terrestrial transmission links of the BSC6900 are functional....

. .2 Target Description Format . . . . . . . . . . . G. . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . G. . . . . . .2 ARM Features . . . . . 699 Appendix I Trace File Format .4. . . . . . . . . . . . . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 M68K Features . . . .xiv Debugging with gdb Appendix F The GDB Agent Expression Mechanism . . . . . . . .3 OS ABI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . .7 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Nios II Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Varying Target Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 PowerPC Features . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . . .5 General Bytecode Design . . . . . . G. .1 F. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Predefined Target Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . .4 MicroBlaze Features . . . . . . . . . . . . . . . . 703 Appendix K Manual pages . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . .1 Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G. . . .9 S/390 and System z Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . G. . .4. . . 707 Appendix L GNU GENERAL PUBLIC LICENSE . . . . . . . . . . . . . G. . Appendix G 677 679 684 685 685 Target Descriptions . . . . . . . . . . Rationale . .1 Process list .4. . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . .2. . G. Using Agent Expressions . . . . .2 Architecture . . .3 F. . . . . . .4. . . . . . . . . . . 713 . . . . . . . . . . .10 TMS320C6x Features. . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .gdb_index section format. . . . . .1 Retrieving Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 i386 Features . . . . . . . . . . . . . . . . . . . .1 AArch64 Features . . . .2. . . . . . . . . . . . . . . . . . . . . . . . .6 Types . . . . . . . . . 701 Appendix J . . . . . . .4. . . .2. . . . . . . . . 689 689 690 690 691 691 691 691 692 693 694 694 694 695 696 696 696 696 696 697 697 Appendix H Operating System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . .4. . . . . G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677 F. . . . . . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . .4 Standard Target Features. . . . . . . . . . . . . . . . . . . . . . . .5 Features . . . . . . . . . . . .4. . . . . . . . .5 MIPS Features . . G. .2. . . . G. . . . . . . . . . 699 H. . . . . . . Bytecode Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 F. . . . . . . . . . . . . . . .4. . . . . . . . . .2 F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Compatible Architecture. . . . . . 689 G. . . G. .

Command name abbreviations are allowed if unambiguous.Generic command for showing things about the debugger Type "help" followed by command name for full documentation. For example.Maintenance commands obscure -. Type "help" followed by command name for full documentation.User-defined commands Type "help" followed by a class name for a list of commands in that class. Command name abbreviations are allowed if unambiguous. (gdb) help class Using one of the general help classes as an argument.22 Debugging with gdb 3. using the command help.Running the program stack -.Specifying and examining files internals -.3 Getting Help You can always ask gdb itself for information on its commands. (gdb) help command With a command name as help argument.Status inquiries support -. . you can get a list of the individual commands in that class.Examining data files -.Tracing of program execution without stopping the program user-defined -. List of commands: info -.Obscure features running -.Examining the stack status -.Aliases of other commands breakpoints -. here is the help display for the class status: (gdb) help status Status inquiries.Making program stop at certain points data -.Support facilities tracepoints -. help h You can use help (abbreviated h) with no arguments to display a short list of named classes of commands: (gdb) help List of classes of commands: aliases -.Generic command for showing things about the program being debugged show -. gdb displays a short paragraph on how to use that command.

50.20151203-cvs (GDB) Richard Stallman. Roland Pesch. .10. for gdb version 7. et al.Debugging with gdb The gnu Source-Level Debugger Tenth Edition. Stan Shebs.

. clear the alarm as suggested. check whether the ALM-21346 IP Connectivity Check Failure alarm is reported. l Checking the status of the FE/GE port 1. If the value of the Port running state is Port is down. l Checking the status of the optical port 1. (1) Run the MML command LST IPCHK to query the configuration of the gateway connectivity check. FR Check the status of the E1/T1 port. Run the MML command DSP ETHPORT to query the status of the Ethernet port. – The value of Link Availability Status is Unavailable. otherwise. If yes.. set it to ARP. see 15. Run the MML command DSP OPT to query the status of the optical port. Ltd. NOTE If the BFD function is supported by and enabled at the peer router. If the value of Optical port state is not normal. HDLC Check the status of the E1/T1 port. (3) In the alarm tab page of the LMT. check the alarms related to the optical port and rectify the fault according to the alarm handling suggestion. Check the status of the optical port. run the MML command STP IPCHK to stop the gateway connectivity check. – The value of Port state is Deactivated. Expected result: The Port running state of the associated E1/T1 port is Port available.3 Unavailable FE/GE Port for troubleshooting. ----End Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 2. Channelized STM-1 transmission mode l Then. Expected result: The value of Link Availability Status is Available. Optional: Check the connectivity of the gateway (mandatory in three-layer networking). end this task. set Check type to SBFD. Run the MML command DSP E1T1 to query the status of the E1/T1 ports. If either of the following cases occurs. 15-3 .. (2) Run the MML command STR IPCHK to start the gateway connectivity check. Expected result: The value of Optical port state is Available.2 Unavailable E1/ T1 Port for troubleshooting.. see the 15. (4) To keep the gateway connectivity check. Otherwise..BSC6900 GSM Commissioning Guide 15 FAQ If the transmission on the interface is over. Checking the status of the E1/T1 port 1.