Generic MO for HW Upgrade From MkVI to MkVI+ 2011 SGSN

Generic MOP for HW Upgrade from MkVI to MkVI+

Contents

1 WORK OVERVIEW.................................................................................................................................................................3

2 INTRODUCTION......................................................................................................................................................................3

2.1 Scope....................................................................................................................................................................................32.2 Target Group........................................................................................................................................................................3

3 PREREQUISITES......................................................................................................................................................................3

3.1 Planning...............................................................................................................................................................................33.2 User......................................................................................................................................................................................33.3 Safety Precautions...............................................................................................................................................................33.4 Software Baseline................................................................................................................................................................33.5 Hardware..............................................................................................................................................................................33.6 Tools and Auxiliary Equipment...........................................................................................................................................3

4 PREPARATION.........................................................................................................................................................................3

4.1 Access (1 week before upgrade)..........................................................................................................................................34.2 Pre upgrade health Check (1 week before upgrade and again on the night).......................................................................34.3 Checkpointing and Setting the Default Configuration (night of the upgrade)....................................................................34.4 Performing a Pre-Upgrade Backup (night of the upgrade)..................................................................................................34.5 Preparing the MkVI+ Upgrade Kit (night of the upgrade)..................................................................................................3

5 INSTALLING THE NEW PEBV5 HARDWARE..................................................................................................................3

6 INSTALLING THE NEW IBACV4 PIUS...............................................................................................................................3

7 POST-UPGRADE OPERATIONS...........................................................................................................................................3

7.1 Post Health Check................................................................................................................................................................37.2 Secure cables and PUI.........................................................................................................................................................37.3 Dispatch of old MKVI PIU to VODAFONE......................................................................................................................3

8 FALLBACK................................................................................................................................................................................3

8.1 Full HW Fallback from MKVI+ to MKVI..........................................................................................................................38.2 PEB replacement.................................................................................................................................................................38.3 IBAC Replacement..............................................................................................................................................................3

9 FIGURES AND DIAGRAMS...................................................................................................................................................3

9.1 Power Unit Switch position model BMG 663 014/31.........................................................................................................39.2 Power Unit Switch position model BMG 663 014/31.........................................................................................................39.3 MKVI Hardware Configuration..........................................................................................................................................39.4 Hardware Replacement order..............................................................................................................................................39.5 MKVI+ Hardware Configuration........................................................................................................................................39.6 Configuring the MagID.......................................................................................................................................................3

10 REFERENCES.......................................................................................................................................................................3

1 WORK OVERVIEW

This document describes how to perform a hardware upgrade from MkVI hardware to MkVI+ hardware on a SGSN WCDMA Systems.

The MkVI+ hardware configuration introduces the new Power and Ethernet Board version 5 (PEBv5) which replaces the PEBv4

The purpose of this document is to guide the site personnel through the steps of a hardware upgrade from MkVI to MkVI+ hardware on an SGSN 2011A

A successful rollout of this upgrade procedure is dependent upon careful planning, proper training, tools and software being in place, and a mindset to always maintain a safe operation.

To provide all the necessary information about preparations, required equipment, and upgrade instructions, this document is split into descriptions and procedural instructions, both equally important.

Ericsson InternalIMPLEMENTAION GUIDE 5 (27)

Prepared (also subject responsible if other) No.

EMC/QSU/QWC Philippe Le Toquin 1/1531-FCP 121 8661 UenApproved Checked Date Rev Reference

2011-08-25 PA11

2 Introduction

2.1 Scope

This document covers the following issues:

Prerequisites for the upgrade procedure

Hardware upgrade of the SGSN

Post-upgrade operations on the SGSN

2.2 Target Group

This document is intended for site personnel performing a hardware upgrade from MkVI hardware to MkVI+ hardware on an SGSN 2011A

3 Prerequisites

This section outlines the necessary prerequisites to perform an upgrade.

3.1 Planning

It is possible to perform the upgrade procedure without taking the SGSN out of service.

For a successful upgrade, all PEBv4 PIUs must be replaced with PEBv5 PIUs. It is not possible to have a combination of PEBv4 PIUs and PEBv5 PIUs.

3.2 User

The person performing configuration and planning should have a solid knowledge of and training in the following areas:

How to work in UNIX®

Operation of the SGSN

Operation of the GSS server

Operation of the GSN Support Application (GSA)




2011-08-25 PA11

3.3 Safety Precautions

To ensure personal safety and product safety while working with Ericsson products, carefully read the following CPI documents before starting work:

Personal Health and Safety Information (ref 1)

System Safety Information (ref 2)

3.4 Software Baseline

This procedure is only valid for an SGSN with the following software requirement:

SGSN 2011A

3.5 Hardware

The following upgrade kit is needed to perform a hardware upgrade from MkVI to MkVI+:

A) for 3 Magzine

1- RPM 1136439/30m - 4 no's

2- TSR 491641/30m - 6 no's

3- NTM 1011045/18 - 1 set

B) for 2 Magzine

1- RPM 1136439/30m - 4 no's

2- TSR 491641/30m - 4 no's

3- NTM 1011045/17 - 1 set

3.6 Tools and Auxiliary Equipment

The following tools and equipment, not included in the delivery package, are needed to perform the hardware upgrade:




2011-08-25 PA11

Torx 5 screwdriver

Torx 8 screwdriver

Flat end screwdriver

An Electrostatic Discharge (ESD) wrist strap

ESD secured container to store the removed PEBv4s and IBASv4s.

4 Preparation

This section describes the preparations needed to perform the hardware upgrade.

Some sections needs to be done on the night of the upgrade while other will need to be done in advance.

4.1 Access (1 week before upgrade)

In order to get access to the SGSN several groups inside VODAFONE needs to be informed (ATS and GNO mainly). This must be done sufficiently early to make sure that all procedure are followed

The following access information is needed:

The O&M IP address of the SGSN

The root password of the SGSN

The user name and password of an Operation and Maintenance user with configuration rights

The root password of the GSS server

The user name and password of a GSS user

4.2 Pre upgrade health Check (1 week before upgrade and again on the night)

Perform a pre-installation health check according to the instructions in the standard VODAFONE Health Check, to ensure that the SGSN is functioning correctly.




2011-08-25 PA11

If some hardware is found to be faulty it must be investigated and a decision must be take to replace the faulty equipment or not

4.3 Checkpointing and Setting the Default Configuration (night of the upgrade)

Make the current active checkpoint default then create a new checkpoint to realize the situation where the most current checkpoint is “Next,LastActivated” and the previous checkpoint is “Permanent”.

Step Timing Duration Step DescriptionEffect on

TrafficResponsible

1. 22:00 1 min

Set the current active SC to default

# gsh set_default_scNo

downtimeEricsson and VODAFONE

2. 22:01 1 min

Print the list of SC and the state must now looks like below.

# listSCs

cxr1010721_8r1a01_S780FP01CP01ECA15, 2008-10-23 02:50:43,PatchedCompletedjhimsiAMMultiDT82009, 2009-08-20 04:42:16, CheckpointCompletedPreR8FP01CP05, 2009-08-25 16:43:18, CheckpointCompleted (LastBooted)cxr1010676_5r8a05_S80FP01CP05C, 2009-08-26 11:11:26, PatchedCompletedPostR8FP01CP05, 2009-08-26 11:53:11, CheckpointCompletedjhimsiD43404M30DT10809, 2009-10-08 04:58:34, CheckpointCompleted current, 2009-10-13 18:08:02,CheckpointActive(Next,LastActivated,Permanent)

3. 22:03 5 min

Create Checkpoint:




2011-08-25 PA11


TrafficResponsible

# gsh checkpoint { -cpn BeforeMKVIplus }

4. 22:08 5 min

Print the list of SC and the state must now looks like below.

# listSCs

cxr1010721_8r1a01_S780FP01CP01ECA15, 2008-10-23 02:50:43,PatchedCompletedjhimsiAMMultiDT82009, 2009-08-20 04:42:16, CheckpointCompletedPreR8FP01CP05, 2009-08-25 16:43:18, CheckpointCompleted (LastBooted)cxr1010676_5r8a05_S80FP01CP05C, 2009-08-26 11:11:26, PatchedCompletedPostR8FP01CP05, 2009-08-26 11:53:11, CheckpointCompletedjhimsiD43404M30DT10809, 2009-10-08 04:58:34, CheckpointCompletedcurrent, 2009-10-13 18:08:02, CheckpointActive(Permanent)BeforeMKVIplus 2011-03-17 14:00:0 (Next,LastActivated)

4.4 Performing a Pre-Upgrade Backup (night of the upgrade)

Ensure that there is enough available disk space on the GSS. One backup requires approximately 3 GB of disk space.




2011-08-25 PA11


TrafficResponsible

1. 22:15 1minLog on to the GSS server as a GSS user.

No downtime

Ericsson and VODAFONE

2. 22:16 1 min

Show disk storage information for the gsn partition with the following command:

df –k

The disk space is listed as shown below. Search for the :

Filesystem kbytes used avail capacity Mounted on/dev/dsk/c0t0d0s0 1492975 235833 1197423 17% /gsn

No downtime


3. 22:21 5 min

If there is not enough space on the SGSN it is possible to remove the old backup to make some space. List them first and select oldest

# gsa list

# gsa delete <name of old backup>

No downtime


4. 22:26 40 minLog on to the SGSN as the root user and perform a pre-upgrade backup of the SGSN on MkVI.

# gsa backup -t PreMKVI+_upgrade

No downtime


4.5 Preparing the MkVI+ Upgrade Kit (night of the upgrade)

Always use an approved ESD wrist strap when working with sensitive equipment. Damage to components mounted on printed board assemblies can occur if an ESD wrist strap is not used.

Note: This chapter can be executed while the backup is ongoing


TrafficResponsible

1. 23:00 1 min

Put on the antistatic wrist strap. Connect it to the No

downtimeEricsson and VODAFONE




2011-08-25 PA11


TrafficResponsible

ground connector in the cabinet

2. 23:01 1 minSecure space for the PIUs that will be removed from the SGSN by arranging an extra magazine or extra antistatic bags.

3. 23:02 5 min Unpack the upgrade kit. Report missing or damaged parts to the supplier.

4. 23:07 5 min

Identify the PEBv4s to replace. They are marked in grey in Figure 1 chapter 8.1.

The new PEBv5s that replace the PEBv4s are marked in grey in Figure 2 chapter Error: Reference source not found.

5. 23:17 10 min

Loosen the screws holding the PIUs that are to be removed from the SGSN. Also, loosen the screws on the cables that will be moved or removed.

Do not remove the PIUs or cables at this stage

Do label all cables connected to the PIUs that will be removed

6. 23:27 10 min

Examine the backplane connectors on the PEBv5 to make sure they have not been damaged during shipping and handling. If the connectors are damaged, they may in turn damage the cabinet backplane and a replacement will be required for the damaged cards

7.

Refer to chapter 8.1 and chapter 8.2 to identifty the corresponding PDU used for the SGSN.

Make sure you are familiar with their functioning but do not switch off any breaker at the moment




2011-08-25 PA11


TrafficResponsible

8. 23:37 5 min

You can also use the following command to see some statis on each interface:

getAll_ip_if

5 Installing the New PEBv5 Hardware

This section describes how to replace the PEBv4 PIUs with the PEBv5 PIUs contained in the SGSN MKVI+ upgrade kit.

The PEBv4 PIUs are replaced one by one, starting with the PEBv4 PIU in the lowest magazine on the right side of the SGSN and then continuing with the left side. Replace the PEBv4 PIUs in the order given in the instructions below.

Be careful when replacing PIUs. Check that the metal gasket on the left side of the front panel is properly fixed. Otherwise, it can tear off when replacing the PIU and cause a short circuit.


TrafficResponsible

1. 00:00 1 minAlways use an approved ESD wrist strap when working with sensitive equipment. Damage to components mounted on printed board assemblies can occur if an ESD wrist strap is not used.

No downtime


2. 00:01 1 min

The PEBv4 will be replaced in 2 stages. First the right side then once it is completed the left side will be replaced.

Locate the PEBv4 in the lowest magazine on the right side of the SGSN.

On a three magazine node it is located in position 3.213. 00:02 1 min

Do a long Press of 2 to 3 second on the REP REQ button of the PEBv4.




2011-08-25 PA11


TrafficResponsible

The REP ALL Light Emitting Diode (LED) will shine with a steady orange light.

If the PEBv4 power supply is faulty, the REP ALL LED will never start flashing

Check PEB is blocked.

=== sysadm@eqm01s14p2 ANCB ~ # gsh get_eq_info -eq { 1 21 }

Eq Class = CBType = PEBv4AdminState = BlockedOperState = UpRevision = R2CBootROM = R3SProdNo = ROJ 208 138/1ProdName = PEBv4ManWeek = 20080825SerialNo = A063730734

4. 00:03 1 min

Refer to chapter 8.1 and chapter 8.2 to identifty the corresponding switches, or circuit breakers, on the Power Distribution Unit (PDU) of the relevant PEBv4.

Switch off the power to the PEBv4.

5. 00:04 1 min

Make sure that the correct circuit has been cut by checking that the four green POWER LEDs on the PEBv4 (marked -48 V 1–4) are off.

Note: Normally, the red ERROR LEDs on the other PIUs in the magazine will light up.

6. 00:05 1 minDisconnect the power cables, the inter magazine connection cables and the fan alarm cable on the PEBv4 that is to be replaced.

7. 00:06 1 minPull the PEBv4, by the handles, straight out of the slot.

8. 00:07 1 min

Note the setting of the MagID configuration switch on the PEBv4, see Figure 3 for the location of the configuration switch. The setting will be needed in a




2011-08-25 PA11


TrafficResponsible

later step.

9. 00:08 1 minPlace the PEBv4 in an ESD-secure container.

10. 00:09 1 minBefore the PEBv5 is inserted check once more that its MagID corresponds to the MagID configured on the PEBv4 that was just removed.

11. 00:10 1 minInsert the PEBv5. Make sure it slides correctly into the guides in the slot and the handles are positioned up and out. To lock, fold the handles towards the middle and push the PEBv5 into place.

12. 00:11 1 min

Reconnect the power cables and the fan alarm cable to the PEBv5.

Do not connect the inter-magazine cables TSR 491 602 yet.

13. 00:12 1 min Use the relevant switch, or circuit breaker, on the PDU, to switch the PEBv5 on.

14. 00:13 13 min *2

Repeat the instructions from Step 3 for each remaining PEBv4, until all PEBv4 PIUs are replaced with PEBv5 PIUs on one side of the SGSN then proceed with next step before replacing the other side

Note: Always replace the next PEBv4 working from the bottom upwards.

The order is as follow for the right side:

PEBv4 located in position 3.21



And as follow for the left side :






2011-08-25 PA11


TrafficResponsible


See Diagram in chapter Error: Reference source not found for a detail of the order

15. 00:40 1 minOnce the PEB have all been swapped on one side of the cabinet, log on as O&M configuration operator to the active NCB.

16. 00:41 3 min

Wait for at least two minutes after replacement of the PIU. Then check the status of the PEBv5 in magazine 1, by using the following command:

gsh get_eq_info -eq { 1 21 }

An output similar to the following appears:

Eq Class = CB Type = PEBv5 AdminState = Blocked OperState = Up or Down(see below)Revision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210

Note the card on the top Magazine will be in state Blocked and Up and the REP ALL LED will have a steady orange light

while the other PEB in the lower magazines will be Blocked and Down. The ERR LED will be flashing red

17. 00:44 1 min




2011-08-25 PA11


TrafficResponsible

Do not proceed connecting the connection cable to the PEBv5 located in magazine 1 until the

PEBv5 has booted

Reconnect the inter-magazine cable for the PEBv5 located in the lowest magazine first. That is, If the lowest PEBv5 is located in magazine 3, connect the cable between NLS 2 in magazine 2 and NLS 1 in magazine 3 first.

18. 00:45 1 minReconnect the connection cable for the PEBv5 located in magazine 1 between NLS 2 in magazine 1 and NLS 1 in magazine 2.

19. 00:46 10 min

Wait for at least 5 minutes after reconnecting the cables. Then check the status of the PEBv5 PIUs by using the following command:



Eq Class = CB Type = PEBv5 AdminState = Blocked OperState = Up Revision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210

Make sure all PEB have a similar printout and that all REP ALL LED have a steady Orange light before continuing.

20. 00:49 5 min

After the replacement, the PEBv5 PIUs are initially




2011-08-25 PA11


TrafficResponsible

blocked and must be unblocked. Unblock the PEBv5 PIUs, starting with the PEBv5 located in magazine 1 and continue downwards to the next magazine, by using the following command:

gsh deblock_eq -eq { 1 21 }

Verify that all of the PEBv5 PIUs are detected by reading the In-Service Performance (ISP) log:

tail -f /tmp/DPE_COMMONLOG/isp.log

Wait until a printout similar to the following appears:

2011-07-02 00:35:35 UTC+0200;pm_detected;ncl;1.21.2.1;CXS101289_R24A03(11B-00-00)2011-07-02 00:35:35 UTC+0200;hw_detected;ncl;1.21,PEBv5;CXS101289_R24A03(11B-00-00)2011-07-02 00:35:35 UTC+0200;deblock_eqm;ncl;1.21;CXS101289_R24A03(11B-00-00)

The REP ALL LED will be off after deblocking

21. 00:54 1 min

Verify that the PEBv5 PIUs are unblocked by using the following command:



Eq Class = CB Type = PEBv5 AdminState = Unblocked OperState = Up Revision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210




2011-08-25 PA11


TrafficResponsible

22. 01:00 54 minLocate the PEBv4 in the lowest magazine on the left side of the SGSN and repeat Step 3 to Step 21 , for all PEBv4 PIUs located on the left side of the SGSN.

6 Post-Upgrade Operations

This section describes the operations to be performed after the upgrade.

6.1 Post Health Check

Perform health check according to the instructions in the standard VODAFONE Health Check, to ensure that the SGSN is functioning correctly.

6.2 Secure cables and PUI

After the upgrade is completed it is important that the nodes is inspected to make sure that all cables and PIU are securely attached

Adjust all the cables and tighten the cable clamps.

Tighten all screws holding the PIUs and the cables.

6.3 Dispatch of old MKVI PIU to VODAFONE

The old MKVI cards (6 PEBv4 and 10 IBASv4) must be securely inserted in ESD container. It is recommended to insert them in the container that were holding the MKVI+ kit and clearly label the container according to the PIU they contain.

Once this step is done they must be handed over to VODAFONE for storage. They will need to be affected to the spare kits.

7 Fallback




2011-08-25 PA11

7.1 Full HW Fallback from MKVI+ to MKVI

If the upgrade is unsuccessful, it is possible to fallback to MKVI hardware by replacing all PEBv5 PIUs with the PEBv4 PIUs and resume normal operation.

1. Collect as much logging data as possible for troubleshooting purposes.

2. Report the failed upgrade to Ericsson Support.

3. Follow the procedures described in Section 5, but replace the PEBv5 PIUs with the old PEBv4 PIUs.

Note: For PEB v4 the inter-magazine connection is as following:

Reconnect NLS2 of MAG3 to NLS2 of MAG2

Reconnect NLS1 of MAG2 to NLS3 of MAG1

7.2 PEB replacement

If after inserting a PEB v5 the card is not coming up it is recommended to replace it.


TrafficResponsible

1. 00:00 1 minAlways use an approved ESD wrist strap when working with sensitive equipment. Damage to components mounted on printed board assemblies can occur if an ESD wrist strap is not used.

No downtime


2. 00:02 1 min

Do a long Press of 2 to 3 second on the REP REQ button of the PEBv5 to be replaced

The REP ALL Light Emitting Diode (LED) will shine with a steady orange light.

If the PEBv4 power supply is faulty, the REP ALL LED will never start flashing

Check PEB is blocked.

=== sysadm@eqm01s14p2 ANCB ~ # gsh get_eq_info -eq { 1 21 }




2011-08-25 PA11


TrafficResponsible

Eq Class = CB Type = PEBv5 AdminState = Blocked OperState = UpRevision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210

3. 00:03 1 min

Refer to chapter 8.1 and chapter 8.2 to identify the corresponding switches, or circuit breakers, on the Power Distribution Unit (PDU) of the relevant PEBv5.

Switch off the power to the PEBv5.

4. 00:04 1 min

Make sure that the correct circuit has been cut by checking that the four green POWER LEDs on the PEBv5 (marked -48 V 1–4) are off.

Note: Normally, the red ERROR LEDs on the other PIUs in the magazine will light up.

5. 00:05 1 minDisconnect the power cables, the inter magazine connection cables and the fan alarm cable on the PEBv4 that is to be replaced.

6. 00:06 1 minPull the PEBv5, by the handles, straight out of the slot.

7. 00:07 1 minNote the setting of the MagID configuration switch on the PEBv5, see Figure 3 for the location of the configuration switch. The setting will be needed in a later step.

8. 00:08 1 minPlace the PEBv5 in an ESD-secure container.

9. 00:09 1 minBefore the PEBv5 is inserted check once more that its MagID corresponds to the MagID configured on the PEBv5 that was just removed.

10. 00:10 1 min

Insert the PEBv5. Make sure it slides correctly into the guides in the slot and the handles are positioned up and out. To lock, fold the handles towards the middle




2011-08-25 PA11


TrafficResponsible

and push the PEBv5 into place.

11. 00:11 1 min

Reconnect the power cables and the fan alarm cable to the PEBv5.

Do not connect the inter-magazine cables TSR 491 602 yet.

12. 00:12 1 min Use the relevant switch, or circuit breaker, on the PDU, to switch the PEBv5 on.

13. 00:41 3 min

Wait for at least two minutes after replacement of the PIU. Then check the status of the PEBv5 in magazine 1, by using the following command:



Eq Class = CB Type = PEBv5 AdminState = Blocked OperState = Up or Down(see below)Revision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210

Note the card on the top Magazine will be in state Blocked and Up and the REP ALL LED will have a steady orange light

while the other PEB in the lower magazines will be Blocked and Down. The ERR LED will be flashing red

14. 00:44 1 min




2011-08-25 PA11


TrafficResponsible

Do not proceed connecting the connection cable to the PEBv5 located in magazine 1 until the

PEBv5 has booted

Reconnect the inter-magazine cable for the PEBv5

15. 00:46 10 min

Wait for at least 5 minutes after reconnecting the cables. Then check the status of the PEBv5 PIUs by using the following command:



Eq Class = CB Type = PEBv5 AdminState = Blocked OperState = Up Revision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210

Make sure the PEB has a similar printout and that the REP ALL LED has a steady Orange light before continuing.

16. 00:49 5 min

After the replacement, the PEBv5 PIU is initially blocked and must be unblocked. Unblock the PEBv5 PIUs, starting with the PEBv5 located in magazine 1 and continue downwards to the next magazine, by using the following command:

gsh deblock_eq -eq { 1 21 }




2011-08-25 PA11


TrafficResponsible

Verify that all of the PEBv5 PIUs are detected by reading the In-Service Performance (ISP) log:

tail -f /tmp/DPE_COMMONLOG/isp.log

Wait until a printout similar to the following appears:

2011-07-02 00:35:35 UTC+0200;pm_detected;ncl;1.21.2.1;CXS101289_R24A03(11B-00-00)2011-07-02 00:35:35 UTC+0200;hw_detected;ncl;1.21,PEBv5;CXS101289_R24A03(11B-00-00)2011-07-02 00:35:35 UTC+0200;deblock_eqm;ncl;1.21;CXS101289_R24A03(11B-00-00)

The REP ALL LED will be off after deblocking

17. 00:54 1 min

Verify that the PEBv5 PIUs are unblocked by using the following command:



Eq Class = CB Type = PEBv5 AdminState = Unblocked OperState = Up Revision = R2D BootROM = R3H ProdNo = ROJ 208 1312/1 ProdName = PEBv5 ManWeek = 20081203 SerialNo = A063789210




2011-08-25 PA11

8 Figures and Diagrams

8.1 Power Unit Switch position model BMG 663 014/31




2011-08-25 PA11

8.2 Power Unit Switch position model BMG 663 014/31




2011-08-25 PA11

8.3 Configuring the MagID

Figure Configuring the MagID




2011-08-25 PA11

9 References

Ref 1 CPI: Personal Health and Safety Information (24 46-2885)

Ref 2 CPI: System Safety Information (124 46-2886)

Documents

Generic MO for HW Upgrade From MkVI to MkVI+ 2011 SGSN