31-OrM500003 UMG8900 System Commissioning ISSUE1.0

OWG500213 MSOFTX3000 System CommissioningUMG8900 System Commissioning
Foreword
System commissioning refers to a series of debugging and testing on a system after hardware and software installation to make sure that the system can run stably, reliably and securely online with its design requirements.
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.
References
Objectives
Upon completion of this course, you will be able to:
Understand the basic concept of the UMG8900 System Commissioning
Perform the process and methods for the UMG8900 commissioning, such as local office, interconnection and service commissioning.
Contents
2. Local Office Commissioning
Steps of Commissioning Preparation
Checking version and running status of the software
Checking communication between LMT and BAM
Checking Software Version
Checking host software
Checking communication between LMT and BAM
Notes:
The BAM works as the server and LMT works as the client. The BAM sits on the OMU board of the host .
The LMT connects to the OMC port on the NET or TNC board in the main control frame . The address of the OMC port is defined in mml.txt .
To check the network connectivity between the LMT and OMC port by using the PING command in the Windows command line.
Data Configuration Methods
Method 1:
Using the MML commands. This is the most common method and can apply to all data configuration.
Method 2:
Using the graphic interface provided by Device Management on the LMT. It applies only to part of data configuration, such as hardware.
Method 3:
Executing data configuration scripts. Data scripts are *.txt files that contain MML commands and notes. To run the script file, click System > Batch Commands > Go…
Contents
Contents
Boards Commissioning
Checking the Board Running Status
On the LMT, click the Device Panel tab and click Device Management.
Checking the Board Software Version
Method 1: LST BRDVER
Method 2: to right-click a board on Device Management to select Board Version Info.
Contents
Description of Clock State
Fast tracking
Indicates the CLK board is quick locking the reference source clock. Usually, it occurs in the moment when the system is accessing the reference source.
Locked
Indicates the CLK board has locked the reference source and outputs the clock corrected by the reference source.
Holdover
Indicates the CLK board lost the reference source traced and outputs clock based on phase-lock parameter saved during tracing.
Commissioning Procedure for Clock
Be sure that clock cables are tightly fixed.
Step2: DSP E1PORT (optional)
Only be used when the UMG8900 locks the peer E1 line clock. Check the status of the E1 port that extracts line clock.
Step3: DSP SLIP (optional)
Only be used when the UMG8900 locks the peer E1 line clock. Check the slip statistics of the E1 port that extracts line clock. It can make slip statistics for the latest 15 minutes or 24 hours.
Commissioning Procedure for Clock
Step4: DSP CLK
To check the status of clock phase-locked loop on the CLK board and status of other reference sources. Locked indicates the clock phase-locked loop works.
It takes about 30 minutes for the CLK board to complete clock locking.
Step5: DSP NETCLKSIG
To check the status of phase-locked loop on the NET board in other frames. Locked is the normal state.
Contents
Cascading Commissioning
Step1: Checking physical cables in the cascading system and check if the LINK indicators are on.
Step2: Checking if the cascading board No. configured in ADD FRM is the same with that of the BLU physically connected.
Step3: Checking if the value of the parameter TDM Cascade Port 0configured in the ADD FRM command is the same with the No. of the optical port physically connected.
Step4: Checking if the cascading boards running well.
Step5: Checking if there is any cascading alarm.
The boards involved in the cascading include the TNU, BLU, FLU and NET.
Contents
Contents
3.3 Connecting with MGW
H.248 Interface Modes
Note: Use the PING command to check the H.248 interface address!
Mode
Remark
The PPU interface
Refers to the FE interface on the PPU. This mode is usually applied to the single-frame networking.
The OMU interface
Refers to the OMC interface on the NET in the SSM-256 main control frame, or the Mc or OMC interface on the TNC in the SSM-32 main control frame. This mode often applies to the single-frame networking where H.248 messages and network management packets share a physical port.
The MPU interface
Refers to the OMC interface on the NET in an SSM-256 frame other than the main control frame, or the Mc or OMC interface on the TNC in an SSM-32 service frame. This mode usually applies to the multi-frame networking
H.248 Interface Commissioning
The indicator being on shows the physical layers are through.
Step 2: DSP IPIF
To check the status of the FE interface, the physical and link layers shall be UP at both.
In the case of an UP physical layer but a DOWN link layer, check if the local configurations of FE interface rate, duplex mode and maximum transmission unit are matched with the interconnected router. If not, use MOD IPIF to set them.
Step3: DSP ROUTE To check the routing status.
Gateway Registration Commissioning
Step1: ACT VMGW To activate the gateway
Step2: DSP VMGW To check the VMGW status. The state of In Service indicates successful registration.
If in other states, take the following steps:
Command
Remark
DSP H248LNK
Checking the status of H.248 signaling links. The link status should be UP if the transport layer is SCTP and TCP.
LST H248LNK
LST SCTPINIT
Checking if SCTP parameters of the PPU match those of the MGC.
LST H248PARA
LST VMGW
Checking if VMGW ID of the UMG8900 matches that of the MGC
H248 message tracing: The MSOFTX3000 receives the service change request message, and then sends the service change reply message.
SCTP message tracing: The MSOFTX3000 receives the INIT message and returns the INIT ACK message. And then it receives the COOKIE message and returns the COOKIE ACK message,
Contents
E1 Interfaces Commissioning
Step
Remark
1
Take out all E1 connectors of an E32/T32 from the DDF. Make self-loop on the E1 interface.
2
DSP E1PORT to display status of the E32/T32 interface. The E1 port should be in the OK state.
3
To further examine E1 port, use LOP E1 to conduct software loopback with loopback mode set to local loop. The E1 port status should be OK.
4
To further examine E1 cable, measure the E1 connector resistance between the copper sheet and the core with a multi-meter
5
After test, restore normal connection of all connectors. Run LOP E1 with loopback mode set to Non-loopback to release interface self loopback.
6
DSP E1LOP: to check if self loopback of all interfaces is released.
Step
Remark
1
LOP E1: the loopback mode is set to OUTLOP (Remote). Ask the peer side to check status of the peer E1 interface. The peer E1 interface should be in the OK state. If the links are normal, go to step 3; if abnormal, continue with step 2.
2
Make loopback tests section by section to determine the very section with transport problems.
3
The loopback tests prove interfaces are OK, but they become FAULT again after loopbacks. In this case, run DSP E1PORT to check if the frame structure and line coding scheme of the UMG8900 match those of the peer device.
When E1 cables are used to link the UMG8900 and other devices such as an MSC, check these E1 links before call test. If the links are faulty or there is much noise during conversation, the most common way is to make loopback test and bit error rate test. The most efficient way is to connect the UMG8900 with the peer device such as a BSC or an MSC through the E1 trunk and then make dial test over this trunk on the MGC. Check if the call can be set up normally and observe the quality of voice.
Step
Remark
4
5
LOP E1: the loopback mode is set to Non-loopback to release all the local loopback after test. DSP E1LOP: to check if self loopback of all interfaces is released
6
Make dial test over a trunk designated by the MGC to check if calls can be set up over the trunk and conversation quality is satisfied. Check other E1 trunks in the same way.
When E1 cables are used to link the UMG8900 and other devices such as an MSC, check these E1 links before call test. If the links are faulty or there is much noise during conversation, the most common way is to make loopback test and bit error rate test. The most efficient way is to connect the UMG8900 with the peer device such as a BSC or an MSC through the E1 trunk and then make dial test over this trunk on the MGC. Check if the call can be set up normally and observe the quality of voice.
The OK status indicates the port has no lines crossed.
If a port is followed with a number ranging from 0 to 31, the port has lines crossed.
Note:
Set the peer device in remote loopback mode and the UMG8900 with no loopback before running this command !
Lines cross means that the receive or send line of an E1 system connects the send or receive line of another E1 system.
SDH Interfaces Commissioning
Step1: Checking if the LINK indicator of the SDH interface is on.
Step2: To conduct loopback test with a flange at the ODF for both sides, and check the SDH interface indicators of both sides.
Step3: If the LINK indicator is on during loopback test but off after the test, check if the receive and send cables are inserted to interfaces reversely.
DSP S2LPORT: to check if the configurations of the local frame structure and type match those of the peer device.
Step4: LST SDHFLAG
Checking Overhead Byte Configuration Of SDH. The overhead bytes of the S2L that must be consistent with the peer device include C2, J1 and J2.
Step5: Enable the performance monitoring function to check if there are error codes on transport channels.
Contents
IP Bearer Commissioning
LST IPIF
To check if the IP address of the back board opposite to the HRB can be used to bear services
DSP GWADDR
To check if the MAC address of the gateway is valid.
PING
To check the IP connections between the local UMG8900 and other MGWs
Check the IP bearer network quality
To check if there are alarms about monitoring the quality of the IP bearer network .
Make a test call
If abnormity occurs in the test call, start an H.248 application trace task to check the message interaction.
Contents
Contents
MTP2-M2UA Protocol Stack
MTP2-M2UA Commissioning Steps
Step 1: Checking Status of M2UA Links
DSP L2UALNK : normal state should be ACTIVE.
Step 2: Checking Configuration of M2UA Links
The UNESTABLISH state means that SCTP links fail to be set up to bear M2UA links. In this case, do as follows:
LST L2UALNK : to check the local/remote IP address and local/remote SCTP port No. Check if the M2UA link work mode of the UMG8900 is Server, and that of the MSOFTX3000 is Client.
LST SCTPINIT: to display SCTP parameters, and check if the UMG8900 and MGC adopt the same checksum algorithm.
Step 3: Creating M2UA Interface Tracing Tasks to further examination.
Contents
MTP3-M3UA Protocol Stack
Step 1: Checking Status of MTP3 Links
DSP N7LNK: to check the status of MTP3 links. The link should activated, no failed and so on. Especially the SLS code is a specific numeric string.
Step 2: Creating MTP3 Interface Tracing Tasks
To further locate reason for failure to set up MTP3 links, create the MTP3 interface tracing task, and then analyze the traced messages.
Note:
SLS is NULL indicates that MTP3 link setup fails !
DSP SPFSUBRD to check the subboard handling the MTP2 links for any fault !
Before checking status of MTP3 links, use ACT N7LNK to activate MTP3 links of both the UMG8900 and the peer device !
DSP M3DLNK : to check the status of M3UA links.
The normal status of links is ACTIVE.
Step 4: Checking Configuration of M3UA Links
LST M3LNK: to check the local/remote IP address and local/remote SCTP port No. Check if the M2UA link work mode of the UMG8900 is Server, and that of the MSOFTX3000 is Client.
LST SCTPINIT: to display SCTP parameters, and check if the UMG8900 and MGC adopt the same checksum algorithm.
STPE 5: Creating M3UA Interface Tracing Tasks
To further locate reason for failure to set up MTP3 links.
Note: To make changed SCTP parameters valid, you have to restart the SPF first !!
Contents
Service Commissioning
The most direct and efficient way for service commissioning is to make test calls. In different networking applications, the steps for service debugging are different. The following steps are just for reference.
Debugging Voice Services
Voice service
Use a MS to dial a local fixed-line phone 50 times, and use a local fixed-line phone to dial a MS 50 times too.
Of the 100 times of calls, over 90% are set up with clear voice (no obvious noises).
Use a MS to call another MS 50 times.
Of the 50 times of calls, over 90% are set up with clear voice (no obvious noises).
In the following situations, make different test calls to check if over 90% are set up with clear voice (no obvious noises).
Debugging Supplementary Services
CFU \ CFNRY \ CFB
Make calls 10 times from a MS to another MS, which are forwarded to a local fixed-line phone in some case.
Make calls 10 times from a fixed-line phone to a MS, which are forwarded to a local fixed-line phone in some case.
Make calls 10 times from a MS to another MS, which are forwarded to the third MS in some case.
Use MS A to call MS B.
During the conversation between MS A and MS B, MS C calls MS A and then waits the end of the conversation between MS A and MS B.
MS B hangs up, and MS A begins to talk with MS C.
CH
Use MS A to call MS B.
During the conversation between MS A and MS B, MS C calls MS A and begins to talk with MS A. MS B remains in the call holding state.
When MS C hangs up, MS A resumes conversation with MS B.
MPTY service
Hold MPTY conference 10 times involving two parties, five parties and eight parties respectively. The parties include fixed-line phones and MS.
Of the 30 times of test, over 90% are successful. Conversation is clear with no obvious noises, and a new party can join the conversation.
Service
Data service
Fax a single page and multiple pages of files (for example, fax 20 pages in succession) from a MS to the PSTN, as well as from the PSTN to a MS..
Fax is received and sent.
Start video services from a MS to another MS.
Conversation is clear, image is uninterrupted.
Summary
Procedures and methods for system commissioning.
Thank you

31-OrM500003 UMG8900 System Commissioning ISSUE1.0

Documents

Transcript of 31-OrM500003 UMG8900 System Commissioning ISSUE1.0