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. guarantees or representations of any kind. 2011. information. all statements. All other trademarks and trade names mentioned in this document are the property of their respective holders.. Ltd..Copyright © Huawei Technologies Co. i . All rights reserved.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. Longgang Shenzhen 518129 People's Republic of China Website: http://www. Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co. services and features are stipulated by the contract made between Huawei and the customer. and recommendations in this document do not constitute the warranty of any kind. services and features described in this document may not be within the purchase scope or the usage scope. Ltd. information. All or part of the products.com Email: support@huawei. express or implied. Ltd. but all statements. The information in this document is subject to change without notice.. Huawei Technologies Co. Ltd. Unless otherwise specified in the contract.. and recommendations in this document are provided "AS IS" without warranties. Notice The purchased products.huawei. 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.. either express or implied.

.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.

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

.

13-1 . Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l You have logged in to the BSC6900 through the LMT. The connection success rate is higher than 90%. l The MSs used for test are functional and are registered in the HLR. A. The basic services consist of speech service and data service. Prerequisite l The verification over the Abis. The voice is clear and without loud noise. The verification over Ater interface is mandatory only in BM/TC separated mode. Procedure Step 1 Table 13-1 lists the procedure for verifying the basic services by testing the MS in the BTS cells.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. and Lb interfaces is successful. The verification over Pb interface is mandatory only if the BSC6900 is configured with an external PCU. 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. location service. The connection success rate is higher than 90%. No call drop occurs and the system resources are released normally after the call is terminated. and AMR service. Ater. The feature services consist of the inter-RAT handover. Gb. Make 20 calls from a fixed-line phone to an 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. The verification over Lb interface is mandatory only if the BSC6900 is configured with an external SMLC. The voice is clear and without loud noise. Pb..

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

The voice is clear and without loud noise. Prerequisite l The standby board for the switchover operates normally. see Table 14-1. see 12 Handling the Alarms Generated During the Commissioning. For details. For details. No call drop occurs and the system resources are released normally after the call is terminated. l The alarms generated before the switchover have been cleared. For details. Procedure Step 1 Switch over the active/standby boards. l All the subracks of the BSC6900 are running normally. see Switching Over the BSC Boards.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. 14-1 . 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. Step 3 Use an MS in a cell under the BTS to perform basic services and verify the services.. l You have logged in to the BSC6900 through the LMT. The connection success rate is higher than 90%. Step 2 Check and handle the alarms generated during the active/standby switchover. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd.

No call drop occurs and the system resources are released normally after the call is terminated. Faxes are sent and received normally. The voice is clear and without loud noise. Send a fax from an electrograph to an MS. The connection success rate is higher than 90%.. Send a fax from an MS to an electrograph. 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.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. Ltd. ----End 14-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Test the General Packet Radio Service (GPRS) or Enhanced Data Rate for GSM Evolution (EDGE) function on the MS. The test data rate is similar to the data rate tested in a lab. Issue 06 (2011-05-19) . No call drop occurs and the system resources are released normally after the call is terminated. The voice is clear and without loud noise.

15-1 . and upper-layer link.. 15. 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. 15. Ltd.3 Unavailable FE/GE Port This section describes how to handle the problem that the FE/GE port is unavailable.8 Setting Maintenance Mode for NE Issue 06 (2011-05-19) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.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. The verification covers E1/T1 port. 15.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. optical port.1 Checking the Transmission Link This section describes how to verify that the terrestrial transmission links of the BSC6900 are functional. FE/GE port.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.4 IP Connection Setup Failure This section describes how to handle the failures during IP connection setup. 15. 15. 15.

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

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

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

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

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