WCDMA RNC Commission

1、DOCUMENTTYPE35 (35)TypeUnitOrDepartmentHereTypeYourNameHereTypeDateHere1 CommissioningRefer to following table for IP information needed to make connection between PC and RNCPreconfigured IP settingsIP addressesMaskDefault gatewayOMU40NEMUOMS255.255.255.

2、240ESA2440DHCP server pool(for Element Manager)040 Devices and tools for commissioning:Wristband, Digital Multimeter, M2.5 allen key (內(nèi)六角扳手), RS232-cable (RJ45 to 9-pol female) 2 pcs, RS232 interface (9-pol male). Computer with te

3、rminal application and NED.2 Inspecting Hardware2.1 Inspect the cablingThere are three following types of cable:· Intrasubrack cables· Intracabinet cables· Intercabinet cablesIntrasubrack cables and intracabinet cables are installed at the factory. However, Intercabinet cables have to

4、 be installed at site according to the Cable list in site documentation2.2 Inspect the location of plug-in unitsRefer to Equipment Lists in site documentationPositionThe slots are denoted with numbers F01-F19 in order from left to right, plus number F38 for the half-height slot below slot F19, on th

5、e far right.IDC numberNameabbreviated name of the plug-in unitFUfunctional unit name and index number for the plug-in unit2.3 Inspect the interchangeability versions of subracks and plug-in unitsRefer to RNC HW Revision list in site documentation. The interchangeability version of a plug-in units is

6、 written in the sticker right after the C number.2.4 Inspect jumper settingsOverviewMost of the plug-in units do not require any alteration of their factory jumper settings. The plug-in units in the following table require specific jumper settings which may have to be modified by the customer:Plug-i

7、n unitJumper blockNoteCCPC2-AJ16If unit is used as OMU, default settings have to be modifiedHDSCN2Factory settings may have to be modifiedHDS9CN2Factory settings may have to be modifiedHDS-ACN2Factory settings may have to be modifiedHDS-BCN2Factory settings may have to be modifiedMDS-A, MDS-BJumpers

8、 and DIP switches Factory settings may have to be modifiedTBUFW1Factory settings may have to be modifiedPresentation of the settingsThe standard and alternative jumpers of the plug-in units are presented in tables except if the plug-in unit has factory settings. The standard settings are illustrated

9、 in the jumper group location maps. For the standard jumpers, the table indicates the jumper group number, the connection required and a note about the connection. For the Alternative settings, the meaning of the connection (like the plug-in unit location), the required connection and a note about t

10、he connection are listed. Each alternative jumper group is preceded by a title describing it. In the column Jumper position, a hyphen (-) is used between the pins of the jumper pair that are to be connected on the plug-in unit. The pins are symbolized by consecutive numbers. If there is only a hyphe

11、n and no numbers in the column, no connection is made. The numbers of the jumper group/s are also given for the Alternative settings.The column Description indicates the alternative selected with the jumper concerned. The alternatives are listed in the Plug-in Unit Descriptions.If the plug-in unit h

12、as a jumper group for setting interchangeability, the setting alternatives are presented in a form that differs from the presentation of the other tables. In the interchangeability table, X = the connection is made, blank = the connection is not made.Selection of settingsSettings are often referred

13、to as jumper settings, or when they can be clearly defined they are divided into two groups:· Standard or default settings· Alternative settingsThe default settings do not depend on external factors so they are always set in the same way regardless of the equipment position. The Alternativ

14、e settings depend on external factors, such as the track position, the parameter to be selected, and the operating environment.2.5 Inspect the power supplyMake sure you have measured the input voltages to the Cabinet Power Distributors (CPDxx) and checked the polarities of the supply lines.· Me

15、asure the input voltages to the cabinet power distribution units. The voltages must be within the range of -40 - -57VDC.· Check that the polarities of the supply lines are correct.· Turn on the power switches in the cabinet power distribution units.3 Monitoring the unit start-up3.1 Connect

16、 a service terminal to OMU and switch the power onEnter correct username and password.3.2 Activate the RCJUUS service terminal extensionZLP:J,RCJ;3.3 Monitor the states of the unitsZJI:ALL;4 Logging into the MMI system for the first time4.1 Log into the MMI system for the first time4.2 Set user prof

17、ileThe default profile (PROFILE) does not have rights for FTP.4.3 Create new administarator ID (IAH)ZIAH:<user id>:<profile>4.4 Log outZ;4.5 Establish a new MML session with the administrative user ID5 Creating Telnet or HTTP connection to print alarmsThe logical file ALARMS is predefine

18、d to VPP-99. When opening a connection with a web browser to port 11111 for the first time, the connection is opened to VPP-99. The second connection will be to VPP-98. The thirs is VPP-97. A connection made to port 11111 connects to the free VPP device with the highest index within range 95 to 99.5

19、.1 Establsih a Telnet or HTTP connection to OMU IP address, port 111115.2 Check the state of VPP-99ZIHI:VPP;6 Inspecting the Hardware Management SystemThe purpose of this test is to ensure that all Hardware Management System (HMS) nodes respond and have the same level of firmware version.6.1 HMS ove

20、rviewThe Hardware Management System (HMS/HMS-A) provides a duplicated serial bus between the master node (located in OMU) and every plug-in unit in the system (See figure Physical connections of HMS/HMS-A). The HMS/HMS-A is used in supporting auto-configuration, collecting fault data from plug-in un

21、its and auxiliary equipment, carrying messages in boot phase to PIUs, and setting hardware control signals like restart and state control in plug-in units.The Hardware Management System is robust, for instance, it is independent of system timing, and it is able to read hardware alarms even from a pl

22、ug-in unit without power feed in order to allow power alarms and remote power on/off switching function. It forms a hierarchical network and has three hierarchical layers (Figure Logincal structure of of the Hardware Management System):· Hardware Management System Master nodes (HMSMs)· Har

23、dware Management System Bridge nodes (HMSBs)· Hardware Management System Slave nodes (HMSSs)The Hardware Management System Master Nodes (HMSMs), one in each OMU, control the whole subsystem. The TSS3s and TBUFs in the subracks have separate Hardware Management System Bridge nodes (HMSBs) that s

24、erve as bridges, which connect HMSMs to the lowest level blocks in the hierarchy. Hardware management System Slave Nodes are implemented as dedicated hardware blocks in all plug-in units, these are independent from the other blocks of the plug-in unit (e.g. in terms of the power supply). The HMS nod

25、es consist of 8 bit (HMS) or 16 bit (HMS-A) microcontrollers and communicate using the CAN protocol.HMS addresses plug-in units according to their location in the system. The location is defined in terms of three location components:1. According to rack location in the system (e.g. rack number)2. Ac

26、cording to subrack location in a particular rack (e.g. subrack number)3. According to PIU location in the subrack (e.g. PPA)Subrack number and rack number are defined during equipping phase of IPA2800 Platform and they are programmed to backplane serial EEPROM.HMS itself will start if following cond

27、itions are met (assuming hardware is working):1. Correct SW version in all nodes (Same version in all nodes.)2. Masternet connecting HMSM and HMSBs correctly cabled and terminated.3. Subnet connection between HMSB and HMS Slave Nodes OK (Implemented as backplane traces -> should always be OK).4.

28、HMSS and HMSM PIU EEPROMs programmed.5. Backplane EEPROMs programmed with correct configuration data. EEPROM used by HMSB to get rack & subrack part of HMS address.The version of the HMS software version can be checked by using the HMEXTE service terminal extension. Normally, all slave nodes sho

29、uld use the same software version.6.2 HMS inspection procedure1. Activate the HMEXTE service terminal extension from service terminal main menu0000-MAN>ZLP:2,HME;2. List the system configuration:0000-HME>DP;The outcome is a list of HMS nodes in the following format: <rack>:<subrack>

30、;:<PPA >. In the example above only the first subrack is shown. HMS master nodes have the addresses 00:00:00 and 00:00:01. Addresses <rack>:<subrack>:3D or <rack>:<subrack>:3E are for bridge nodes. The rest of the addresses are for HMS slave nodes. Note:The list of HMS

31、nodes only displays the HMS bridge nodes on the active HMS transmission line. The PPA of the HMS bridge nodes depends on the transmission line: The PPA of the HMS bridge nodes on the transmission line 00 is 3D. The PPA of the HMS bridge nodes on the transmission line 01 is 3E.3. Compare the list of

32、HMS nodes to plug-in units in the network element.Each plugin unit (including OMU, TSS3 and TBUF) has one slave node.Each plug-in unit in the RNC must have a HMS slave node listed in the list of HMS nodes. The only exception is compact OMS, which does not have an HMS node at all.4. Ensure the compat

33、ibility of HMS nodes.a. Block the following alarms: 1183, 1186, 1291, 2689, 3287, and 3290.ZAFB:<alarm number>:TOT;b. Ensure that all HMS slave nodes have the same level of firmware version.Z2CO:<rack>,<subrack>,<PPA>The HMN SW version shows the firmware version. The followin

34、g example shows the information of the plug-in unit located in the rack 1, sub rack 1 and plug-in unit address 10.All HMS slave nodes should have the same level of firmware version. Repeat the command until you have tested every HMS node of the configuration.c. Disable HMS independent switchover.Z2F

35、B; Note: Disabling HMS independent switchover takes about 20 seconds.d. Checked the active HMS transmission line.Z2CM; Note: If TSS3 0 & TBUF0 are WO-EX, The expected outcome is Active HMS transmission line = 00.e. Interrogate the firmware version numbers of the HMS bridge nodes.In this case, th

36、e active transmission line is 00. The PPA of the HMS bridge nodes is 3D.Z2CO:<rack>,<subrack>,3D;f. Perform a switchover of the HMS transmission line.In this case, perform a switchover to the transmission line 01.· Activate the RCBUGG service terminal extension.ZLP:U,RCB;· Chan

37、ge the TBU 1 to working state.ZUCP:TBU,1,WOEXg. Check that the transmission line switchover is successful.Z2CM;When the active transmission line is 01, the expected outcomeis Active HMS transmission line = 01.h. Interrogate the firmware version numbers of the HMS bridge nodes.In this case, the activ

38、e transmission line is 01. The PPA of theHMS bridge nodes is 3E.Z2CO:<rack>,<subrack>,3E;i. Enable HMS independent switchover.Z2FC;j. Check that the status of HMS independent switchover is ENABLED.Z2FF;k. Interrogate the firmware version numbers of the HMS master nodes.CO:0,0,<0,1>

39、l. Unblock the following alarms: 1183, 1186, 1291, 2689, 3287,and 3290.ZAFU:<alarm number>7 Setting the calendar time and date for RNC7.1 PurposeThe external time source which gives a consistent time for all the network elements in the network, can be defined only after the TCP/IP connections

40、are created. When you have defined the external time source, in 15 minutes all the clocks in the RNC will have the same time as the external time source has. The external time source is located in the NSN NetAct time server. IPA2800-based network elements check the time and date every 15 minutes, pr

41、eferably against the OMS time server, using NTP messages.7.2 Steps1. Display date, time and time zone of the network element (DCD)ZDCD;2. Set the correct date and time for the network element (DCS)ZDCS:<date>,<time>:ST=<summer time>As a result, the internal clock located in the net

42、work element gives a time stamp, which is in a correct time, for all the functions that the computer unit does.3. Interrogate NTP server IP address (DCI)ZDCI;4. Set IP address for NTP server if needed (DCM)8 Interrogating equipment database8.1 PurposeIt is recommended to interrogate information on c

43、abinets, subracks, functional units, plug-in units, and connections between plug-in units (ports). The correct hardware configuration description data is displayed in the site-specific documents.8.2 Steps1. Check the state and integrity of the equipment database and copy database files to diskThe eq

44、uipment database must be in the normal state to ensure the inquired information is correcta. Check EQDATA state (DBS)ZDBS:EQDATA,0;b. Save EQDATA database log to disk (DBO)ZDBO:EQDATA,0;c. Empty EQDATA database disk updating log (DBX)ZDBX:EQDATA,0;d. Prevent EQDATA updates to disk (DBP)ZDBP:EQDATA,0

45、:DISK;e. Prevent EQDATA updates to memory (DBP)ZDBP:EQDATA,0:MEM;f. Check the integrity of EQDATA on disk (DBV)ZDBV:EQDATA,0:DISK;g. Resume EQDATA updates to disk (DBR)ZDBR:EQDATA,0:DISK;h. Resume EQDATA updates to memory (DBR)ZDBR:EQDATA,0:MEM;i. Dump EQDATA database files to disk (DBC)ZDBC:EQDATA,

46、0;j. Check EQDATA stateZDBS:EQDATA,0;2. Interrogate cabinet information (WFI)ZWFI:J:<cabinet type>,<cabinet HMS number>,<cabinet location>3. Interrogate subrack information (WFI)ZWFI:C:<subrack type>,<cabinet HMS number>,<subrack HMS number>4. Interrogate plug-in

47、unit information (WFI)ZWFI:P:<plug-in unit type>,<plug-in unit index>:<cabinet HMS number>,<subrack HMS number>,<PPA>:<subrack location>:<unit type>,<unitindex>,<unit group index>:<master unit type>,<master unit group index>5. Interro

48、gate connection information on plug-in unit ports (WFI)ZWFI:S:<cabinet HMS number>,<subrack HMS number>,<PPA>,<port type>,<port index>6. Interrogate functional unit information (WFI)a. Interrogate functional unit's description data.ZWFI:U:<unit type>,<unit

49、index>,<unit group index>:<master unit type>,<master unit group index>:<cabinet HMS number>,<subrack HMS number>,<PPA>b. Interrogate which plug-in units the functional unit is attached to.ZWFI:P:<unit type>,<unit index>8.3 Examples9 Interrogating ha

50、rdware data9.1 Purposeinterrogate the HW data that is stored in the EEPROMs of hardware components.9.2 Steps1. Select one of the following three alternatives· Interrogate all hardware data. (WFL)ZWFL:P;Note: This alternative is not Recommended, As it takes very long time.· Interrogate data

51、 from all plug-in units in a cabinet. (WFL)ZWFL: P:<cabinet HMS number>· Interrogate data from one subrack in a defined location. (WFL)ZWFL: S:<cabinet HMS number>,<subrack HMS number>9.3 Examples10 Interrogating software build information10.1 Steps1. Verify that the correct s

52、oftware build is on the hard disk andalso loaded for every unit needed (WQO) ZWQO:CR; ZWQO:RUN; ZWQO;2. Check the versions of the software build (WQB) ZWQB:NAME=<SW build name>:FORM=FAILED; The command compares the versions of the software build against the versions in the master file. The sys

53、tem outputs the erroneousversions. The command also calculates a check sum for each software module and compares it to the check sum in the moduleheader. Erroneous modules are output.The command does not calculate the checksum for XML (eXtensible Markup Language), TXT (text) and DTD (document type d

54、efinition) files. There is no total version control, for example, for GIF (Graphics Interchange Format) files. The command does not check the versions of files nor calculate the checksums; it only checks that the files exist.3. Check the version of the flash memory boot package of the unitagainst th

55、e SW package (WDI) ZWDI:UT=<unit type> If the flash memory boot packages are not compatible, you must update the boot package. ZWDR:UT=<unit type>,UI=<unit index> Take new boot package into use. ZUSU:<unit type>,<unit index>11 Inspecting I/O system11.1 Steps1. Display t

56、he physical I/O devices and check their operating states (IHI)ZIHI:<computer type>|<generated by the system> def,<pair number or computer index>,<computer index>:<io unit type>|<all> def,<io unit index>|<all> def;In normal condition, the disk drives ar

57、e in the WO-EX working state. Display units change their state to WO-EX after a connection has been established to them. For VPP devices connected to LPD (line printer daemon: service provided by the UNIX operating system, employed in TCP/IP networks as a mechanism for using remote printers ) devices (VPP devices with index under 50), the state changes according to the state of the LPD device. The LPD device is in the WO-EX state after the unit startup. LPD devices change their state to WO-EX when functional state of the device changes to NORMAL or FLUSH. The operatin