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.

.

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

.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

11-15 .. Ltd. ----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. re-install the inter-SCUa cables by referring to Installing the Inter-SCUa Cables Between Different Subracks.

.

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

.

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

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

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

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

and upper-layer link.1 Checking the Transmission Link This section describes how to verify that the terrestrial transmission links of the BSC6900 are functional. FE/GE 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. optical port. 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.2 Unavailable E1/T1 Port This section describes how to handle the problem that the E1/T1 port is unavailable. 15. 15.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.5 Board Data Loading Failure This section describes how to handle the failures that occur during data loading to the BSC6900 board.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. 15.4 IP Connection Setup Failure This section describes how to handle the failures during IP connection setup. The verification covers E1/T1 port. 15. 15-1 . 15. Ltd. 15.

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

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

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

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

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