You are on page 1of 42

1/42 Owner: HMS-node update (slave, bridge and master codes)

COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

HMS-node update (slave, bridge and master codes)

Table of contents

1. Purpose.........................................................................................................................................3
2. Scope............................................................................................................................................3
3. Responsibilities .............................................................................................................................3
4. INTRODUCTION ..........................................................................................................................4
4.1 HMS-master node .............................................................................................................5
4.2 HMS-bridge node ..............................................................................................................5
4.3 HMS slave node ................................................................................................................5
4.4 Required tools ...................................................................................................................6
5. Preparation ...................................................................................................................................6
5.1 The following HMS node versions must be in the plug-in unit to proceed with the
update ...............................................................................................................................8
5.2 Check the HMS versions of the codes ..............................................................................8
5.2.1 Master’s code version..........................................................................................9
5.2.2 Bridge’s code version ..........................................................................................10
5.2.3 Slave’s code version............................................................................................12
6. Updating........................................................................................................................................12
6.1 Updating HMS-slave .........................................................................................................13
6.1.1 Set FBAN flags on all units and prevent independent switchovers of HMS ........13
6.1.2 Updating 1st release HMS slave code in all the plug-in units in the subrack .......14
6.1.3 Updating A-variant HMS slave code in all plug-in units in the subrack ...............15
6.1.4 Updating 1st release HMS slave code in one plug-in unit in the subrack.............15
6.1.5 Updating A-variant HMS slave code in one plug-in unit in the subrack...............16
6.1.6 Enable switchovers of HMS and clear FBAN flags..............................................16
6.2 Updating HMS-bridge ........................................................................................................18
6.2.1 Set FBAN flags on all units and prevent independent switchovers of HMS ........18
6.2.2 Updating 1st release HMS bridge code in all TSS3 and TBUF plug-in units........19
6.2.3 Enable switchovers of HMS and clear FBAN flags..............................................21
6.3 Updating HMS-master .......................................................................................................22
6.3.1 Set the RBAN flags on in all units and prevent independent switchovers of
HMS.....................................................................................................................22
6.3.2 Updating 1st release HMS master code in both OMUs (CCPC2-A).....................24
6.3.3 Updating A-variant HMS master code in both OMUs (CCP10, CCP18-A)..........26
6.3.4 Enable switchovers of HMS and clear RBAN flags .............................................28
7. Troubleshooting ............................................................................................................................30
7.1 Reduce the speed of the transmission line........................................................................30
7.2 Check the status/versions of the HMS Flash programmer ................................................30
7.2.1 Slave....................................................................................................................31
7.2.2 Bridge ..................................................................................................................32
7.2.3 Master..................................................................................................................33
Issue 1 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
2/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

8. REFERENCES .............................................................................................................................34
9. Abbreviations ................................................................................................................................34
10. APPENDICES...............................................................................................................................35
10.1 Printouts of the commands................................................................................................35
/1/ System locations ........................................................................................................35
/2/ Check 1st release HMS-master code version: ............................................................35
/3/ Check 1st release HMS-bridge code:..........................................................................36
/4/ Check 1st release HMS-slave code version:...............................................................37
/5/ Updating 1st release HMS slave code in all the plug-in units in subrack: ...................38
/6/ Updating A-variant HMS slave code in all plug-in units in subrack: ...........................38
/7/ Updating 1st release HMS slave code in one plug-in unit in subrack:.........................39
/8/ Updating A-variant HMS slave code in one plug-in unit in subrack:...........................39
/9/ Updating 1st release HMS bridge code in all TSS3 and TBUF plug-in units:..............39
/10/ Updating 1st release HMS master code in both OMUs:............................................40
/11/ Updating A-variant HMS master code in both OMUs: ..............................................40

Issue 2 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
3/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

1. PURPOSE

NOTE! Check to see that this is the latest edition of this publication at
ShareNet directory or contact your Nokia contact person.

This document covers HMS-slave, HMS-bridge and HMS-master node code update
in Nokia IPA2800 hardware in U2, U3A, U3B, U3C and U4 software releases.

These are working instructions on how to update HMS-slave code, HMS-bridge code
and HMS-master code in live Networks elements, and brief instructions on how to
solve problems if updating does not succeed.

More detailed information of the HMS is seen Nokia Online Servive (NOLS) in Nokia.

2. SCOPE

NOTE! You must possess a good knowledge of how to operate and maintain
IPA2800 before this document can be used.

Read the instructions thoroughly before starting.

This document is used in IPA2800, U2, U3A, U3B, U3C and U4 software releases in
the Nokia network elements.

3. RESPONSIBILITIES

This document is maintained in


COO/ConvergedCore/TS/PS/NGVM/MSS/WSE&NE/HWSupport.
Contact HW Support person for further information.

Issue 3 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
4/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

4. INTRODUCTION

HMS is the lowest “intelligent” level of IPA2800 platform. HMS is the first part, which
comes to “life” after switching the power on to network element and is responsible for
switching on the power of the plug-in unit. HMS has a very limited capacity channel
and is the only channel for transfering data before the ATM connections between
plug-in units can be established.

Functionality of HMS is such a crucial part of the network element start-up that it is
advisable not to do HMS flash code update, as part of normal software update to
ensure there are no side effects.

Remote updating is not supported for reason that if something goes wrong and
completion of update is not possible. Make sure that there is a person who has
access to the premises of the network element and has ready programmer flash
chips of HMSS node. This “emergency” person must be aware of the following
instructions.

The sequence of how to update nodes is from least critical to most critical. On an
HMS level this kind of rating means that HMSS is the least critical part because it
prevents only one computer to starting up. On the other hand, this kind of rating is
not so unambiguous on the functional unit side. That’s why it is a good idea to plan
updating so that first the HMSS nodes on the standby computer units are updated.

Because a new flash code is transferred through the HMS master node (HMSM), the
more critical part after HMS slave node (HMSS) is HMS bridge node (HMSB), as
seen in Figure1. The most important thing to understand is that the subnet under the
HMSB node is not usable during the update phase of HMSB node’s code. As long as
HMSB node’s code update is successful, it is impossible to recover current subrack’s
(=subnet) computer units. The most critical part of HMS is HMSM node. It is
duplicated and both HMSM nodes cannot be updated at the same time. You must
update each of these separately, by the last phase.

Issue 4 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
5/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

HMSM

HMSM

subnet 0
HMSB
masternet 0

masternet 1

HMSS HMSS HMSS

HMSB
subnet 1

subnet 0
HMSB

HMSS HMSS HMSS

HMSB
subnet 1

Figure 1. Topology of the HMS

4.1 HMS-master node

HMS master node (HMSM) is the head of system. HMSM node resides on OMU
(CCPC2-A, CCP10 or CCP18-A plug-in unit). HMSM controls the system and is
responsible for for example selecting the transfer line and supervision of HMS bridge
nodes.

The HMSM node’s code is updated in both OMUs’ in CCPC2-A, CCP10 or CCP18-A
plug-in unit.

4.2 HMS-bridge node

HMS bridge node (HMSB) divides the subnet from masternet. Physically the subnet
consists of HMS slave nodes of one subrack. HMSB resides in TSS3 and in TBUF
plug-in unit and they are plug-in units of functional unit TBU.

The HMSB node’s code is updated in all TSS3 and TBUF plug-in units.

4.3 HMS slave node

HMS slave node (HMSS) has interfaces with for example plug-in unit’s power and
hardware alarms. HMSS is connected to both transfer lines on the subnet side.
Issue 5 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
6/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

The HMSS resides in all plug-in units. (not NEMU and


ESA12/ESA24 ). The HMS slave node code will be updated in all plug-in units,
excluding NEMU and ESA12/ESA24 plug-in units.

4.4 Required tools

• Holistic Integration Tester HIT, for U2 release, version 2.1-5 or later and for
U3 and U4 releases, version 2.8-0 or later.

Available in:

NET test tool distribution

• HIT-macro HMS_code_version_check.tel. This macro is used to check node


code versions and variants (1st release or A-variant ).

Available in COO/ConvergedCore/TS/PS/NGVM/MSS/WSE&NE/HWSupport

• HIT-macro hms_update.tel.This macro is used to update HMS-nodes.Macro


is recommended to be used instead of updating HMS nodes manually to
avoid human errors during updating.

Macro will be included in SW documentation whenever new HMS versions


are delivered in CD or in new release.

Also available in:


COO/ConvergedCore/TS/PS/NGVM/MSS/WSE&NE/HWSupport

5. PREPARATION

• Updating should be done during low traffic periods

• Remote updating is not supported

• While checking HMS node code versions and updating HMS the UNIT’s
recovery functions are disabled and HMS related alarms are blocked.

• While updating the HMS node, the plug-in units must be in SE-NH, SP-
EX or WO-EX state

NOTE!: The Spare units of the OMU, CACU, SPMU and CM MUST BE in
the SE-NH state while updating slave, bridge and master nodes.

• Do not detach or turn power off from the unit that is being updated

• Slave updating is performed on all plug-in units in one subrack with one
command, or to each plug-in unit one by one

• During the HMS bridge update the subrack is out of HMS services

Issue 6 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
7/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

• Updating and checking HMS slave/bridge/master code


versions is performed by using the HMEXTE Service terminal extension
via OMU

• Ensure that no alarms are on and that the network element is working
properly by for example running diagnostics on all units. (ZAAP,ZUDU)

• In U3C or U4 alarm 2867 HMS in separated state will be active when


HMS independed switchovers are disabled (FB command)

• Update commands must be given in active OMU

• Two variants of HMS nodes exist: 1st release and A-variant. Both of
these have their own code module. Make sure you know which code
you are updating. 5.2 Check the HMS versions of the codes

• New versions of HMS codes are compatible with the older versions

• DO NOT continue if problems occur during the update. Stop and repair
the problem before continuing

• Keep an update-logging file where all given commands and system


responses can be seen

• The software level for U2 has to be U2 8.1-0 or newer. U3A, U3B, U3C
and U4 software levels are valid from first customer release onwards.

• The updating order is: The first is the code’s update in all the slave
nodes, the second is the code’s update in all the bridge node’s and the
third is the code’s update in all the master nodes.

Check that new versions of the software modules are stored on the network
element’s hard disk in W0-LFILES/. See Table 1.

Node SW module
HMS-master, 1st release HMX1MNGX.IMG
HMS-master, A-variant HMXAMNGX.IMG
st
HMS-bridge, 1 release HMX1BNGX.IMG
HMS-slave, 1st release HMX1SNGX.IMG
HMS-slave, A-variant HMXASNGX.IMG
Table 1 the name of the SW module

By using this HME command you are able to see HMS version of the SW module.

HME-command:

Load the HMEXTE Service terminal extension with the ZLP command:

00:MAN>ZLP:H,HME

Example: 00:HME>FH:W0-LFILES/HMXxxxGX.IMG,D

Issue 7 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
8/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

NOTE! The versions of the SW modules are not corresponding


with node code versions.

Example: 00:MAS>XP:W0-LFILES/HMX1SNGX.IMG

This version x.x-x is an SW module version, not an HMS node code version.

5.1 The following HMS node versions must be in the plug-in unit to proceed with the
update

Check the existing versions of node codes (HMS-master, -bridge and -slave) to see
that they are upgradeable on a network element. See Table 2.

Versions in Table 2 are the minimum versions of codes which are updateable by
following these instructions.

Older versions of node code have to be updated by the factory before updating can
be continued. Contact your local Nokia person for further information.

Node version
HMS-master, 1st release 2.1-2
HMS-master, A-variant 2.1-0
HMS-bridge, 1st release 2.1-0
HMS-slave, 1st release 2.1-0
HMS-slave, A-variant 2.1-0

Table 2. HMS updateable versions

5.2 Check the HMS versions of the codes

Load the HMEXTE Service terminal extension with the ZLP command:

00:MAN>ZLP:H,HME

NOTE! HIT-macro HMS_code_version_check.TEL can also be used for checking


node code versions of the plug in units and variant of the HMS node (1st release or
A-variant). See section 4.4.Required tools.

NOTE! Block the alarms and set FBAN flags to all units before checking any HMS
code versions while using HME service terminal command CO or while using HIT-
macro HMS_code_version_check.TEL

1.Block the alarms 1183 HMS LINE CONNECTION LOST, 1186 NO RESPONSE
TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN TBU:

ZAFB:1183::TOT;

ZAFB:1186::TOT;

ZAFB:2689::TOT;
Issue 8 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
9/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Block also the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are defined.

ZAFB:1291::TOT;

ZAFB:3287::TOT;

ZAFB:3290::TOT;

2.Ensure that the alarms are blocked:

ZAFP:;

3.Load the RCJUUS Service terminal extension with ZLP command:

00:MAN>ZLP:J,RCJ

4.Set FBAN flags on all units with command ZJT:

00:RCJ>ZJT:ALL,,,S,FBAN

If HMS updating continues directly after checking HMS codes versions, unblocking of
the alarms and clearing of the FBAN flags are not necessary to be done at this point.
Otherwise unblock the alarms and clear FBAN flags after checking HMS versions of
the codes, see section e.g. 6.2.3 steps 5 and 8.

5.2.1 Master’s code version

1.Check the address of the local HMS master node in OMU 0:

00:HME>CI

NOTE! The address of the master node can be: 00:00:00 or 00:00:01.By giving that
command you are able to see the HMS master node address in the OMU, where you
are connected.

2.Check master code version in both OMU’s:

ZHCO:0,0,<HMSM_ppa_address>

Example:

00:HME> CO:0,0,0 OMU 0 or 1

00:HME> CO:0,0,1 OMU 1 or 0

Issue 9 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
10/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Check that 1st release "hmn sw version" is updateable or newer


in the the CCPC2-A plug-in unit in both OMUs. See Table 2 HMS updateable
versions.

or

Check that A-variant "hmn sw version" is updateable or newer in the CCP10 or


CCP18-A plug-in unit in both OMUs. See Table 2 HMS updateable versions.

See example printouts of the CO-command in APPENDICES/Printouts of the


commands /2/

5.2.2 Bridge’s code version

Check the HMSB code version in all TSS3&TBUF PIUs in both transmission lines.

1.Prevent independent switchovers of HMS with command FB:

00:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY

NOTE! It takes about 20 seconds.

2.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

3. Check the code version in all TSS3&TBUF PIUs in the active transmission line in
every subrack. HMSB’s ppa part of address depends on active transmission line:

ZHCO:<rack>,<subrack>,<HMSB_ppa_address>

Example:

transmission line 0 active:

00:HME> CO:1,2,3D

Check that 1st release "hmn sw version" is updateable or newer. See Table 2 HMS
updateable versions.

Issue 10 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
11/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

See example printouts of the CO-command in


APPENDICES/Printouts of the commands /3/

4.Make HMS transmission line switchover:

ZHFD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:1

5.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

6.Check the code in all TSS3&TBUF PIUs in the active transmission line in every
subrack:

ZHCO:<rack>,<subrack>,<HMSB_ppa_address>

Example:

00:HME> CO:1,2,3E

Check that 1st release "hmn sw version" is updateable or newer. See Table 2 HMS
updateable versions.

See example printouts of the CO-command in APPENDICES/Printouts of the


commands /3/

7. Make HMS transmission line switchover:

ZHFD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

8. Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh


Issue 11 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
12/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

9. Check the active TBU:

ZUSI:TBU; (MML-command)

Check that active transmission line is corresponding with the active TBU-line:

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

9.Enable HMS Independent switchover:

00:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

5.2.3 Slave’s code version

Check HMS slave node version in all plug-in units (not ESA and NEMU):

ZHCO:<rack>,<subrack>,<ppa>

ppa is plug-in unit position in hex format

Example:

00:HME> CO:1,1,A

Check that 1st release or A-variant "hmn sw version" is updateable or newer. See
Table 2 HMS updateable versions.

See example printouts of the CO-command in APPENDICES/Printouts of the


commands /4/

NOTE! If the 1st release version is not 2.1-0 or newer See Technical note 25/02
HWTN HMS slave node update.

6. UPDATING

1.Ensure that no alarms are on (ZAAP).

2.Check the states of the units. Updating the HMS node, the units must be in SE-NH,
SP-EX or WO-EX state.

NOTE!: The spare units of the OMU, CACU, SPMU and CM MUST BE in the SE-
NH state while updating slave, bridge and master nodes.

This prevents interworking between the 2N units (unit 0 and 1) during the HMS-
slave, HMS-bridge and HMS-master update and thus prevents interferences during
the HMS update.

Issue 12 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
13/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

NOTE! DO NOT REMOVE plug-in units from it’s place.

NOTE! The state of the units cannot be changed when the FBAN flag is set.

NOTE! It is recommended that you NOT enable HMS Independent switchover,


unblock the alarms and clear the flags after slave node or brigde node updating if the
updating continues directly from the node type to an other (slave->bridge->master).

3.Load the HMEXTE Service terminal extension with the ZLP command:

00:MAN>ZLP:H,HME

6.1 Updating HMS-slave

6.1.1 Set FBAN flags on all units and prevent independent switchovers of HMS

1.Change OMU-1 and the spare units (SP-EX) of the CACU, SPMU and CM to the
SE-NH state.

See section 6 Updating

2.Block the alarms 1183 HMS LINE CONNECTION LOST, 1186 NO RESPONSE
TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN TBU:

ZAFB:1183::TOT;

ZAFB:1186::TOT;

ZAFB:2689::TOT;

Block also the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are defined.

ZAFB:1291::TOT;

ZAFB:3287::TOT;

ZAFB:3290::TOT;

3.Ensure that the alarms are blocked:

ZAFP:;

4.Load the RCJUUS Service terminal extension with ZLP command:

00:MAN>ZLP:J,RCJ

5.Set FBAN flags on all units with command ZJT:

00:RCJ>ZJT:ALL,,,S,FBAN

Issue 13 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
14/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

6.Prevent independent switchovers of HMS with command FB:

00:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY.

NOTE! It takes about 20 seconds.

7. Get system configuration with DP-command and save the list in LOG-file:

00-HME>DP

NOTE! You must verify the system configuration before and after updating to ensure
that all the necessary PIUs are functional.

See example printouts of the DP-command in APPENDICES/Printouts of the


commands /1/

6.1.2 Updating 1st release HMS slave code in all the plug-in units in the subrack

Start the updating from the lowest subrack. Update each subrack one by one. The
plug-in units must be connected in the subrack:

00:HME> FA:<rack>,<subrack>,3C::<directory/file_name>,<file_format>

3C is multicast address

Example:

00:HME> FA:1,4,3C::W0-LFILES/HMX1SNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /5/

NOTE! Check that all the plug-in units with type 1st release HMS node are listed with
“OK state”. Command shows all nodes in subnet but nodes other than 1st release
nodes will be shown as “10 state” and code versions 00.00-00.

If all the 1st release plug-in units are not updated, then you must continue to the
section 6.1.4 Updating 1st release HMS slave code in one plug-in unit in the subrack.

Issue 14 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
15/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

6.1.3 Updating A-variant HMS slave code in all plug-in units in the subrack

1.Start the updating from the lowest subrack. Update each subrack one by one. The
plug-in units must be connected in subrack:

00:HME> FA:<rack>,<subrack>,3C::<directory/file_name>,<file_format>

3C is multicast address

Example:

00:HME> FA:1,2,3C::W0-LFILES/HMXASNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /6/

NOTE! Check that all plug-in units with type A-variant HMS are listed with OK state.
Command shows all nodes in subnet but nodes other than A-variant type nodes will
be shown as “10 state” and code versions 00.00-00.

If all A-variant plug-in units are not updated, then you must continue to the section
6.1.5 Updating A-variant HMS slave code in one plug-in unit in subrack.

6.1.4 Updating 1st release HMS slave code in one plug-in unit in the subrack

1.Update one plug-in unit. The plug-in unit must be connected in the subrack:

00:HME> FA:<rack>,<subrack>,<ppa>::< directory/file_name >,<file_format>

ppa is plug-in unit position in hex format

Example:

00:HME> FA:1,2,5::W0-LFILES/HMX1SNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /7/

2. Check that the plug-in units with type 1st release HMS node are listed with “OK
state”.

NOTE! If updating was not successful (for example write flash failed: ec =
0x00003D82), See the section 7.Troubleshooting.

Issue 15 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
16/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

6.1.5 Updating A-variant HMS slave code in one plug-in unit in the subrack

1.Update one plug-in unit. The plug-in unit must be connected in the subrack:

00:HME>FA:<rack>,<subrack>,<ppa>::<directory/file_name >,<file_format>

ppa is plug-in unit position in hex format

Example:

00:HME> FA:1,2,10::W0-LFILES/HMXASNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /8/

2. Check that the plug-in units with type A release HMS node is listed with “OK
state”.

NOTE! If updating was not successful (for example write flash failed: ec =
0x00003D82), see the section 7.Troubleshooting.

6.1.6 Enable switchovers of HMS and clear FBAN flags

NOTE! If the updating continues directly with the HMS Bridge Node, do only step 10
in section 6.1.6 and continue to section 6.2.2 Updating 1st release HMS bridge code
in all TSS3 and TBUF plug-in units. See section 6.Updating. Otherwise follow the
instructions.

1.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

2. Check the active TBU:

ZUSI:TBU; (MML-command)

3.Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Issue 16 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
17/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Make HMS transmission line switchover, IF needed:

00:HME>FD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

4.When the transmission line is corresponding with TBU, you can enable HMS
Independent switchover:

00:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

5.Clear FBAN flags:

00:HME> ZJT:ALL,,,C,FBAN

6.Change OMU-1 and the spare units of the CACU, SPMU and CM from SE-NH
state back to the SP-EX state.

See section 6 Updating

7.Change the states of the other units back to their original state, if they are changed
during update.

8.Unblock the alarms 1183 HMS LINE CONNECTION LOST, 1186 NO RESPONSE
TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN TBU:

ZAFU:1183;

ZAFU:1186;

ZAFU:2689;

Unblock the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are blocked.

ZAFU:1291;

ZAFU:3287;

ZAFU:3290;

9.Ensure that the alarms are unblocked:

ZAFP:;

10. Get system configuration with DP-command and take the list in LOG-file:

00-HME>DP

Issue 17 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
18/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Make sure the configuration is exactly the same as before code


update.

6.2 Updating HMS-bridge

6.2.1 Set FBAN flags on all units and prevent independent switchovers of HMS

1.Change OMU-1 and the spare units (SP-EX) of the CACU, SPMU and CM to the
SE-NH state.

See section 6 Updating

2.Block the alarms 1183 HMS LINE CONNECTION LOST, 1186 NO RESPONSE
TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN TBU:

ZAFB:1183::TOT;

ZAFB:1186::TOT;

ZAFB:2689::TOT;

Block also the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are defined.

ZAFB:1291::TOT;

ZAFB:3287::TOT;

ZAFB:3290::TOT;

3.Ensure that the alarms are blocked:

ZAFP:;

4.Load the RCJUUS Service terminal extension with ZLP command:

00:MAN>ZLP:J,RCJ

5.Set FBAN flags on all units with command ZJT:

00:RCJ>ZJT:ALL,,,S,FBAN

6.Prevent independent switchovers of HMS with command FB:

00:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY.

NOTE! It takes about 20 seconds.

Issue 18 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
19/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

6.2.2 Updating 1st release HMS bridge code in all TSS3 and TBUF plug-in units

1.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

2.Get system configuration with DP-command and save the list in LOG-file:

00-HME>DP

NOTE! You must verify the system configuration before and after updating to ensure
that all the necessary PIUs are functional.

See example printouts of the DP-command in APPENDICES/Printouts of the


commands /1/

3.Update all the TSS3 and TBUF PIUs in the active transmission line in all
subracks. Start the updating from the lowest equipped subrack in the last rack. The
plug-in units have to be connected in the subrack.

00:HME> FA:<rack>,<subrack>,<HMSB_ppa_address>::< directory/file_name


>,<file_format>

Example:

00:HME> FA:1,4,3D::W0-LFILES/HMX1BNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /9/

4.Check that TSS3/TBUF plug-in unit (type with 1st release) is listed with “OK state”.

If plug-in unit is not updated, try with the same command at least two more times.

If the updating does not succeed, see the section 7. Troubleshooting.

5.When all TBUFs and TSS3 in the first transmission line are successfully updated
you can continue to step 6.

6.Get system configuration with DP-command and take the list in LOG-file:

00-HME>DP

Issue 19 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
20/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Make sure the configuration is exactly the same as before code


update.

7. Make HMS transmission line switchover:

ZHFD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:1

8.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

9. Get system configuration with DP-command and save the list in LOG-file:

00-HME>DP

NOTE! You must verify the system configuration before and after updating to ensure
that all the necessary PIUs are functional.

10.Update all the TSS3 and TBUF PIUs in the active transmission line in all
subracks. Start the updating from the lowest equipped subrack in the last rack. The
plug-in units have to be connected in the subrack.

00:HME> FA:<rack>,<subrack>,<HMSB_ppa_address>::< directory/file_name


>,<file_format>

Example:

00:HME> FA:1,4,3E::W0-LFILES/HMX1BNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /9/

11.Check that TSS3/TBUF plug-in unit (type with 1st release) is listed with “OK state”.

If plug-in unit is not updated, try with the same command at least two more times.

If the updating does not succeed, see the section 7. Troubleshooting.

12.When all TBUFs and TSS3 plug-in units in the second transmission line are
successfully updated you can continue to step 13.

13.Get system configuration with DP-command and take the list in LOG-file:

Issue 20 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
21/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

00-HME>DP

Make sure the configuration is exactly the same as before code update.

14.Make HMS transmission line switchover:

ZHFD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

6.2.3 Enable switchovers of HMS and clear FBAN flags

NOTE! If the updating continues directly with the HMS Master Node, skip section
6.2.3 and continue with section 6.3.1 beginning step 5;skip step 6 and go to step 7.
After these steps continue to section 6.3.2 Updating 1st release HMS master code in
both OMUs (CCPC2-A). or 6.3.3 Updating A-variant HMS master code in both OMUs
(CCP10, CCP18-A or CCP18-C). See section 6.Updating. Otherwise follow the
instructions.

1. Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

2. Check the active TBU:

ZUSI:TBU; (MML-command)

3. Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Make HMS transmission line switchover, IF needed:

00:HME>FD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

Issue 21 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
22/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

4. When the transmission line is corresponding with TBU, you can


enable HMS Independent switchover:

00:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

5. Clear FBAN flags:

00:HME> ZJT:ALL,,,C,FBAN

6. Change OMU-1 and the spare units of the CACU, SPMU and CM from the SE-NH
state back to the SP-EX state.

See section 6 Updating

7. Change the states of the other units back to their original state, if they are
changed during update.

8. Unblock the alarms 1183 HMS LINE CONNECTION LOST, 1186 NO RESPONSE
TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN TBU:

ZAFU:1183;

ZAFU:1186;

ZAFU:2689;

Unblock the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are blocked.

ZAFU:1291;

ZAFU:3287;

ZAFU:3290;

9. Ensure that the alarms are unblocked:

ZAFP:;

6.3 Updating HMS-master

6.3.1 Set the RBAN flags on in all units and prevent independent switchovers of HMS

1. Change OMU-1 and the spare units (SP-EX) of the CACU, SPMU and CM to the
SE-NH state.

Issue 22 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
23/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

2. Block the alarms 1183 HMS LINE CONNECTION LOST, 1186


NO RESPONSE TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN
TBU:

ZAFB:1183::TOT;

ZAFB:1186::TOT;

ZAFB:2689::TOT;

Block also the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are defined.

ZAFB:1291::TOT;

ZAFB:3287::TOT;

ZAFB:3290::TOT;

3. Ensure that the alarms are blocked:

ZAFP:;

4. Load the RCJUUS Service terminal extension with ZLP command:

ZLP:J,RCJ

5. Set the RBAN flag on in all units and clear FBAN flags from all units with the
command ZJT:

00:RCJ>ZJT:ALL,,,S,RBAN
00:RCJ>ZJT:ALL,,,C,FBAN

6. Prevent independent switchovers of HMS with command FB:

00:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY

NOTE! It takes about 20 seconds.

7. Get system configuration with DP-command and save the list in LOG-file:

00-HME>DP

NOTE! You must verify the system configuration before and after updating to ensure
that all the necessary PIUs are functional.

See example printouts of the DP-command in APPENDICES/Printouts of the


commands /1/

Issue 23 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
24/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

6.3.2 Updating 1st release HMS master code in both OMUs (CCPC2-A)

1. Update first the master code in OMU 1. Give the following command in OMU 0 to
update the master code in OMU 1:

00:HME> FA:0,0,2::W0-LFILES/HMX1MNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /10/

2. Check that the plug-in unit with type 1st release HMS node is listed with “OK
state”.

3. If the updating of the master code in OMU 1 was successful continue to step 4,
otherwise see the section 7.Troubleshooting.

4. Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

5. Check the active TBU:

ZUSI:TBU; (MML-command)

6. Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Make HMS transmission line switchover, IF needed:

00:HME>FD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

7. When the transmission line is corresponding with TBU, you can enable HMS
Independent switchover:

00:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

Issue 24 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
25/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

8. Change the OMU 1 to SP-EX state and make OMU


switchover.

9. Move the service terminal cable from the OMU 0 to the OMU 1 (SER 1).

10. Change the OMU 0 from the SP-EX state to the SE-NH state.

11. Prevent independent switchovers of HMS with command FB:

00:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY

NOTE! It takes about 20 seconds

12. Give the following command in OMU 1 to update the master code in OMU 0:

01:HME> FA:0,0,2::W0-LFILES/HMX1MNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /10/

13. Check that the plug-in unit with type 1st release HMS node is listed with “OK
state”.

14. If the updating of the master code in OMU 0 was successful continue to step 15,
otherwise see the section 7.Troubleshooting.

15. Check the active HMS transmission line:

01:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

16. Check the active TBU:

ZUSI:TBU; (MML-command)

17. Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Make HMS transmission line switchover, IF needed:


Issue 25 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
26/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

01:HME>FD:<line> (FORCED TRANSMISSION LINE


SWITCHOVER)

Example:

01:HME> FD:0

18. When the transmission line is corresponding with TBU, you can enable HMS
Independent switchover:

01:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

19. Change the OMU 0 back to the SP-EX state and then to the WO-EX state
(ZUSC).

20. Move the Service terminal cable from the OMU 1 to the OMU 0 (SER 1).

21. Continue to the section 6.3.4 Enable switchovers of HMS and clear RBAN flags.

6.3.3 Updating A-variant HMS master code in both OMUs (CCP10, CCP18-A)

1. Update first the master code in OMU 1. Give the following command in OMU 0 to
update the master code in OMU 1:

00:HME> FA:0,0,2::W0-LFILES/HMXAMNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /11/

2. Check that the plug-in unit with type A-variant HMS node is listed with “OK state”.

3. If the updating of the master code in OMU 1 was successful continue to step 4,
otherwise see the section 7.Troubleshooting.

4. Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

5. Check the active TBU:

Issue 26 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
27/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

ZUSI:TBU; (MML-command)

6. Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Make HMS transmission line switchover, IF needed:

00:HME>FD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

7. When the transmission line is corresponding with TBU, you can enable HMS
Independent switchover:

00:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

8. Change the OMU 1 to the SP-EX state and make OMU switchover (ZUSC).

9. Move the service terminal cable from the OMU 0 to the OMU 1 (SER 1).

10. Change OMU 0 from the SP-EX state to the SE-NH state.

11. Prevent independent switchover of HMS with command FB:

01:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY

NOTE! It takes about 20 seconds

12. Give the following command in the OMU 1 to update the master code in OMU 0:

01:HME> FA:0,0,2::W0-LFILES/HMXAMNGX.IMG,D

NOTE! It takes about 3 minutes.

See example printouts of the FA-command in APPENDICES/Printouts of the


commands /10/

13. Check that the plug-in unit with type A-variant HMS node is listed with “OK state”.

14. If the updating of the master code in OMU 0 was successful continue to step 15,
otherwise see the section 7. Troubleshooting.

15. Check the active HMS transmission line:

01:HME>CM

Issue 27 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
28/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

16. Check the active TBU:

ZUSI:TBU; (MML-command)

17.Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Make HMS transmission line switchover, IF needed:

01:HME>FD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

01:HME> FD:0

18. When the transmission line is corresponding with TBU, you can enable HMS
Independent switchover:

01:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

19. Change the OMU 0 back to the SP-EX state and then to the WO-EX state
(ZUSC).

20. Move the Service terminal cable from the OMU 1 to the OMU 0 (SER 1).

21. Continue to the section 6.3.4 Enable switchovers of HMS and clear RBAN flags.

6.3.4 Enable switchovers of HMS and clear RBAN flags

1.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

Issue 28 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
29/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

2. Check the active TBU:

ZUSI:TBU; (MML-command)

3.Change the transmission line corresponding with the active TBU-line, IF needed.

TBU 0 WO-EX => Transmission line 0 active

TBU 1 WO-EX => Transmission line 1 active

Make HMS transmission line switchover, IF needed:

00:HME>FD:<line> (FORCED TRANSMISSION LINE SWITCHOVER)

Example:

00:HME> FD:0

4.When the transmission line is corresponding with TBU you can enable HMS
Independent switchover:

00:HME>FC

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY

5.Load the RCJUUS Service terminal extension with the ZLP command:

ZLP:J,RCJ

6.Clear RBAN flags:

00:HME> ZJT:ALL,,,C,RBAN

7.Change the spare units of the CACU, SPMU and CM from the SE-NH state back
to the SP-EX state.

8.Change the states of the units back to their original state, if they are changed
during update.

9.Unblock the alarms 1183 HMS LINE CONNECTION LOST, 1186 NO RESPONSE
TO HMN SUPERVISION and 2689 FUNCTIONAL FAILURE IN TBU:

ZAFU:1183;

ZAFU:1186;

ZAFU:2689;

Unblock the alarms 1291 SUBRACK CONNECTIVITY FAILURE,


3287 PLUG-IN UNIT HMS CONNECTIVITY LOST and
3290 I/O DEVICE HMS CONNECTIVITY LOST if they are blocked.

ZAFU:1291;

Issue 29 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
30/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

ZAFU:3287;

ZAFU:3290;

10.Ensure that the alarms are unblocked:

ZAFP:;

11. Get system configuration with DP-command:

00-HME>DP

Make sure the configuration is exactly the same as before code update.

7. TROUBLESHOOTING

This section covers correction actions if HMS-slave, HMS-bridge or HMS-master


updating is not successful.

7.1 Reduce the speed of the transmission line

Reduce the speed of the transmission line to 75 msg/s or even 50 msg/s. Default
transmission line is 100 msg/s.

00:HME>

FA:<rack>,<subrack>,<ppa>:,,<transmission_line_speed>,:<directory/file_nam
e>,<file_format>

Example:

FA:1,1,6:,,<transmission_line_speed>,:W0-LFILES/HMX1SNGX.IMG,D

If the updating does not succeed continue to the section 7.2 Check the
status/versions of the HMS Flash programmer

7.2 Check the status/versions of the HMS Flash programmer

Issue 30 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
31/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

Nodel Flash programmer version


HMS-master, 1st release 1.1-0
HMS-master, A-variant 1.1-0
HMS-bridge 1.1-4
HMS-slave, 1st release 1.1-2
HMS-slave, A-variant 1.1-0
Table 3 Minimum versions of the flash programmers

7.2.1 Slave

NOTE! The spare units of the OMU, CACU, SPMU and CM MUST BE in the SE-NH
state, FBAN flags must be set on, alarms blocked and independent switchover
prevented when checking the HMS-slave flash programmer code version.
See the section 6.1.1 Set FBAN flags on all units and prevent independent
switchovers of HMS .

Check the status of the HMS-slave flash programmer code version:


ZHFG:<rack>,<subrack>,<ppa>

ppa is plug-in unit position in hex format

Example:

00:HME> FG:1,1,A

The command resets the target node.

00:HME> FG:1,2,A

The command will reset the target node.

Still want to proceed? (Y/N): Y

flprog sw version ...... 1.1-3

Check that 1st release flprog "flprog hmn sw version" is correct/newer in Table 3

and

Check that A-variant flprog "flprog hmn sw version" is correct/newer in Table 3.

IF it is not correct contact your local Nokia contact person.

NOTE! If you are not able to see the version of the flash programmer code (for
example write flash failed: ec = 0x00003D82)

See HMS slave node update

Issue 31 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
32/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

HW TECHNICAL NOTE

No. 25/02

NOTE! After checking flprog status continue updating or to the section 6.1.6 Enable
switchovers of HMS and clear FBAN flags

7.2.2 Bridge

NOTE! The spare units of the OMU, CACU, SPMU and CM MUST BE in the SE-NH
state, FBAN flags must be set on, alarms blocked and independent switchover
prevented when checking the HMS-bridge flash programmer code version.

See the section 6.2.1 Set FBAN flags on all units and prevent independent
switchovers of HMS

Check the status of the HMS-Bridge flash programmer code version in the
TSS3/TBUF PIU in active transmission line.

1.Prevent independent switchovers of HMS with command FB if not prevented yet:

00:HME> FB

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY.

NOTE! It takes about 20 seconds.

2.Check the active HMS transmission line:

00:HME>CM

Active HMS transmission line = <active_transmission_line>

Active transmission line 00 HMSB ppa address 3Dh

Active transmission line 01 HMSB ppa address 3Eh

3. Check the programmer version node in all TSS3/TBUF PIUs in the active HMS
transmission line.

ZHFG:<rack>,<subrack>,<HMSB_ppa_address>

For example HMS transmission line 0 active :

00:HME> FG:1,2,3D

Issue 32 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
33/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

00:HME> FG:1,2,3D

The command will reset the target node.

Still want to proceed? (Y/N): Y

flprog sw version ...... 1.1-4

Check that flprog "flprog hmn sw version" is correct/newer in Table 3.

IF it is not correct contact your local Nokia contact person.

NOTE! After checking flprog status continue updating or to the section 6.2.3 Enable
switchovers of HMS and clear FBAN flags

7.2.3 Master

NOTE! The spare units of the OMU, CACU, SPMU and CM MUST BE in the SE-NH
state, RBAN flags must be set on, alarms blocked and independent switchover
prevented when checking the HMS-master flash programmer code version.

See the section 6.3.1 Set the RBAN flags on in all units and prevent independent
switchovers of HMS

Check the status of the HMS-master flash programmer code version.

The flash programmer version in the OMU 0 is seen by giving the command in the
OMU 1.

The flash programmer version in the OMU 1 is seen by giving the command in the
OMU 0.

The address is always 0,0,2 independently which OMU’s flash programmer has been
checked:

ZHFG:0,0,2
00:HME> FG:0,0,2

The command will reset the target node.

Still want to proceed? (Y/N): Y

flprog sw version ...... 1.1-2

Check that 1st release flprog "flprog hmn sw version" is correct/newer in Table 3.

and

Check that A-variant flprog "flprog hmn sw version" is correct/newer in Table 3.

IF it is not correct contact your local Nokia contact person.

NOTE! After checking flprog status continue updating or to the section 6.3.4 Enable
switchovers of HMS and clear RBAN flags
Issue 33 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
34/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

8. REFERENCES

[1] NED U2, NED U3, NED U4, Nokia Online Services (NOLs)
Nokia Online Services (NOLs)
[2]

9. ABBREVIATIONS

HIT Holistic Integration Tester


HMSS Hardware Management System slave
HMSM Hardware Management System master
HMSB Hardware Management System bridge
PPA This parameter indicates the PPA number value of the
plug-in unit. Plug-in unit position address (PPA) is a
specific value used to identify each plug-in unit individually

Issue 34 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
35/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

10. APPENDICES

10.1 Printouts of the commands

These are example printouts of fhe commands:

/1/ System locations

00-HME>DP System configuration: PIU location


00:00:00
00:00:01
01:01:3D
01:01:01
01:01:04
01:01:05
01:01:06
01:01:07
01:01:08
01:01:09
01:01:0A
01:01:0B
01:01:0E
01:01:10
01:01:11
01:01:13
01:01:26
01:02:3D
01:02:01
01:02:03
01:02:04
01:02:05
01:02:06
01:02:07
01:02:08
01:02:09
01:02:0A
01:02:0B
01:02:0E
01:02:10
01:02:11

/2/ Check 1st release HMS-master code version:

00:HME> CO:0,0,1
Node status:
power on ............... status not used
ATM separated .......... status not used
Issue 35 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
36/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

independent switchover
disabled .............. yes
red led on ............. status not used
green led on ........... status not used
led blink .............. status not used
fan control ............ status not used
active HMS master node
on this computer. Valid
only on A variant node. no
fan rotation speed ..... 00
hmn sw version ......... 2.1-4
node type .............. 02 = master node

Check A-variant HMS-master code version:


00:HME> CO:0,0,1
Node status:
power on ............... status not used
ATM separated .......... status not used
independent switchover
disabled .............. no
red led on ............. status not used
green led on ........... status not used
led blink .............. status not used
fan control ............ status not used
active HMS master node
on this computer. Valid
only on A variant node. yes
fan rotation speed ..... 00
hmn sw version ......... 2.1-3
node type .............. 06 = A variant master node

/3/ Check 1st release HMS-bridge code:


00:HME> CM
Active HMS transmission line = 00

00:HME> CO:1,2,3D
Node status:
power on ............... status not used
ATM separated .......... status not used
independent switchover
disabled .............. yes
red led on ............. status not used
green led on ........... status not used
led blink .............. status not used
fan control ............ status not used
active HMS master node
on this computer. Valid
only on A variant node. no
fan rotation speed ..... 00
hmn sw version ......... 2.1-6
node type .............. 04 = tbuf bridge

00:HME> CM
Active HMS transmission line = 01

00:HME> CO:1,2,3E
Node status:
power on ............... status not used
ATM separated .......... status not used
Issue 36 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
37/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

independent switchover
disabled .............. yes
red led on ............. status not used
green led on ........... status not used
led blink .............. status not used
fan control ............ status not used
active HMS master node
on this computer. Valid
only on A variant node. no
fan rotation speed ..... 00
hmn sw version ......... 2.1-6
node type .............. 03 = tss3 bridge

/4/ Check 1st release HMS-slave code version:

00:HME> CO:1,1,A
Node status:
power on ............... yes
ATM separated .......... no
independent switchover
disabled .............. yes
red led on ............. no
green led on ........... yes
led blink .............. no
fan control ............ yes
active HMS master node
on this computer. Valid
only on A variant node. no
fan rotation speed ..... 02
hmn sw version ......... 2.1-11
node type .............. 01 = slave node

Check A-variant HMS-slave code version:

00:HME> CO:1,1,10
Node status:
power on ............... yes
ATM separated .......... no
independent switchover
disabled .............. yes
red led on ............. no
green led on ........... yes
led blink .............. no
fan control ............ no
active HMS master node
on this computer. Valid
only on A variant node. yes
fan rotation speed ..... 00
hmn sw version ......... 2.1-6
node type .............. 05 = A variant slave node

Issue 37 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
38/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

/5/ Updating 1st release HMS slave code in all the plug-in units in subrack:

00:HME> FA:1,3,3C::W0-LFILES/HMX1SNGX.IMG,D
code type: normal code
node type: slave bin length: 00009BFE CRC: EF77C616
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC codeVers pgmVers state


-------- ----------- -------- ------- ------

0F 07 01 EF77C616-01 02.01-12 01.01-03 OK


0F 07 04 EF77C616-01 02.01-12 01.01-03 OK
0F 07 05 EF77C616-01 02.01-12 01.01-03 OK
0F 07 06 EF77C616-01 02.01-12 01.01-03 OK
0F 07 09 EF77C616-01 02.01-12 01.01-03 OK
0F 07 0A EF77C616-01 02.01-12 01.01-03 OK
0F 07 10 00000000-00 00.00-00 00.00-00 10
0F 07 11 00000000-00 00.00-00 00.00-00 10
0F 07 13 EF77C616-01 02.01-12 01.01-03 OK
0F 07 26 EF77C616-01 02.01-12 01.01-03 OK

/6/ Updating A-variant HMS slave code in all plug-in units in subrack:

00:HME> FA:1,3,3C::W0-LFILES/HMXASNGX.IMG,D
code type: normal code
node type: slave bin length: 0000B450 CRC: F6AA9FAD
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC codeVers pgmVers state


-------- ----------- -------- ------- ------

0F 07 01 00000000-00 00.00-00 00.00-00 10


0F 07 04 00000000-00 00.00-00 00.00-00 10
0F 07 05 00000000-00 00.00-00 00.00-00 10
0F 07 06 00000000-00 00.00-00 00.00-00 10
0F 07 09 00000000-00 00.00-00 00.00-00 10
Issue 38 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
39/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

0F 07 0A 00000000-00 00.00-00 00.00-00 10


0F 07 10 F6AA9FAD-01 02.01-08 01.01-00 OK
0F 07 11 F6AA9FAD-01 02.01-08 01.01-00 OK
0F 07 13 00000000-00 00.00-00 00.00-00 10
0F 07 26 00000000-00 00.00-00 00.00-00 10

/7/ Updating 1st release HMS slave code in one plug-in unit in subrack:

00:HME> FA:1,2,5::W0-LFILES/HMX1SNGX.IMG,D
code type: normal code
node type: slave bin length: 00009BFE CRC: EF77C616
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC pacCnt codeVers pgmVers state


-------- ----------- ------ -------- ------- ------

0F 07 05 EF77C616-01 2700 02.01-12 01.01-03 OK

/8/ Updating A-variant HMS slave code in one plug-in unit in subrack:

00:HME> FA:1,2,10::W0-LFILES/HMXASNGX.IMG,D
code type: normal code
node type: slave bin length: 0000B450 CRC: F6AA9FAD
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC pacCnt codeVers pgmVers state


-------- ----------- ------ -------- ------- ------

0F 07 10 F6AA9FAD-01 2D14 02.01-08 01.01-00 OK

/9/ Updating 1st release HMS bridge code in all TSS3 and TBUF plug-in units:
00:HME> FA:1,4,3D::W0-LFILES/HMX1BNGX.IMG,D
code type: normal code
node type: bridge bin length: 00007AF0 CRC: ED0F096F
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version
Issue 39 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
40/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

address CRC pacCnt codeVers pgmVers state


-------- ----------- ------ -------- ------- ------

01 04 3D ED0F096F-01 1EBC 02.01-06 01.01-04 OK

00:HME> FA:1,4,3E::W0-LFILES/HMX1BNGX.IMG,D
code type: normal code
node type: bridge bin length: 00007AF0 CRC: ED0F096F
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC pacCnt codeVers pgmVers state


-------- ----------- ------ -------- ------- ------

01 04 3E ED0F096F-01 1EBC 02.01-06 01.01-04 OK

/10/ Updating 1st release HMS master code in both OMUs:


00:HME> FA:0,0,2::W0-LFILES/HMX1MNGX.IMG,D
code type: normal code
node type: master bin length: 0000C580 CRC: 11023BE3
Reset HMS nodes
Init HMS nodes
Send data packets->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC pacCnt codeVers pgmVers state


-------- ----------- ------ -------- ------- ------

00 00 02 11023BE3-01 3160 02.01-04 01.01-02 OK

/11/ Updating A-variant HMS master code in both OMUs:


01:HME> FA:0,0,2::W0-LFILES/HMXAMNGX.IMG,D
code type: normal code
node type: master bin length: 0000E8D0 CRC: FF7802E7
Reset HMS nodes
Init HMS nodes
Send data packets-
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>-
Verify node CRC
Get nodes pgm versions
- reset nodes
- ask programmer version
- ask code version

address CRC pacCnt codeVers pgmVers state


-------- ----------- ------ -------- ------- ------

Issue 40 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
41/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

00 00 02 FF7802E7-01 3A34 02.01-04 01.01-01 OK

Issue 41 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö
42/42 Owner: HMS-node update (slave, bridge and master codes)
COO/ConvergedCore/TS/PS/NGVM/
MSS/WSE&NE/HWSupport
©Nokia Siemens Networks

DOCUMENT REVISION HISTORY.

DATE ISSUE AUTHOR SUMMARY OF MAIN CHANGES


19.11.2003 1.0 A.Viitanen The first version
3.3.2004 2.0 A.Viitanen REMOVED: Section 6.4 and 6.5
1.9.2004 3.0 Markku Ojaniemi/ INSERTED: Note: 5.Preparation;
A.Viitanen INSERTED:Note: 6.Updating
INSERTED:Note: 7.Troubleshooting

22.9.2004 4.0 Markku Ojaniemi INSERTED: Section 6.1.1, 6.1.6, 6.2.1,


6.2.3, 6.3.1 and 6.3.4: Inserted block and
unblock alarms 1291, 3287 and 3290
INSERTED: Section 6., 6.1.6, 6.2.3:
NOTE Recommendation
CHANGES: Section 6.1.1, 6.1.6, 6.2.1,
6.2.3, 6.3.1 Change OMU-1
07.11.2005 5.0 Markku Ojaniemi INSERTED: Section 1., 2. ,5. ,8. Issue 5.0
also for U3A and U3B releases
INSERTED: Section 5.2, block alarms
and set fban flags
14.6.2006 6.0 Markku Ojaniemi INSERTED: Section 4.4: hms_update.tel
macro available for updating HMS nodes

13.03.2008 7.0 Jaana Turku New NSN format.


UPDATED: the name of the group;
COO/ConvergedCore/TS/PS/NGVM/MSS
/WSE&NE/HWSupport
INSERTED: CCP18-A and CCP18-C plug
in units, U3C and U4 releases.
UPDATED: Section 5 Preparation.
REMOVED: In section 4.4: old links.

Issue 42 (42)
7.0
Dn 03513957
Checked by 13/03 J Turku Approved by 13/03 J Pyykkö