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.

.

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

.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.

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

.

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

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

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

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

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

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

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

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

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

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