SGW-R5_AT_procedure-26-06-2008

OpenCHECK LIST26 (31)

Prepared (also subject responsible if other)No.

GR/EIL/PI Inderpal SinghEIL/PI-08:0008 Uen

ApprovedCheckedDateRevReference

GR/EIL/PIM Aryan PM DOCPROPERTY "Checked" \* MERGEFORMAT 2008-01-29A DOCPROPERTY "Reference" \* MERGEFORMAT

Acceptance Procedure for, SGw 1 IntroductionThe Ericsson Signalling Gateway (SGw) connects the Core Network to Core networks, PSTN and other Mobile Networks. The purpose of this document is to outline the procedure of how to perform the Network verification for Core Network product SGw.

2PrerequisitesThe following conditions, tools and equipments are necessary for a successful start up and integration of the SGw node.

The user(s) of this document need to have a basic knowledge in the following areas.

Installation and integration procedures for SGw.

Operation of the SGw nodes.

Basic knowledge about trouble shooting2.1 DocumentationThe following documents are necessary for the integration.

_______________________________________________________

The C-Module.

The C-Module contains a description of the site physical layout, i.e. physical position of the SGw node, external power, CCF/DDF connections to and from the SGw node and interconnected network elements.

A Network Plan.

The local Network Plan describes the network and shows the SGw node where to be integrated. It can be a good help during the integration process.

________________________________________________________

2.2 Hardware Installation The cabinet installation must have been performed according to the C-Module.

All nodes interconnected with the SGw must have been prepared with the configuration data necessary for a successful integration towards the SGw node.

The physical connections to the nodes that the SGw is to be integrated with, must have been installed according to the Product Configuration Report.

2.3 Tools and equipment________________________________________________________

At least one PC with required software must be available and include the following:

web browser should be included.

Telnet client

FTP client

Java application for Node Manager.

Window terminal programs used for serial port communication with the SGw (i.e. Windows Hyper Terminal, winfiol ...).

3 Procedure3.1 PreparationIn order to access and control the node during the Start-up and Integration phases, a PC must be connected to the Ethernet Port to enable communication with the node.

Note:

The GPB loader cables slot 2 and 3 in CPM module are internally connected to the O&M positions in ECF1 (Ethernet Connection Field 1). 4 Integration and VerificationThe purpose of this chapter is to integrate the SGw node with all interconnected network elements and perform traffic cases test.

4.1.1 O&M Network IntegrationThe scope of this chapter is to verify the interface between the SGw and the other O&M equipment. The equipment management function in the SGw enables the operator to remotely monitor all hardware modules present in the node and their current status.

Check Ethernet connection between SGW node and PC for O&M connectivity by using Node manager.

Ethernet connection

This chapter verifies the Ethernet connections between the control room and the SGWChange the IP address of the PC to be defined inside the SGw subnet work.

Connect the PC to an O&M Ethernet node connection, and execute ping to the

node IP address. If the ping command is successful, the Ethernet connection is

correct.4.1.2 Hardware checkThis section checks the Cabinet and Subrack Configurations and board types available for the Ericsson Signalling Gateway for Mobile Networks (SGw) product.

The equipment management function in the SGw enables the operator to monitor all hardware modules present in the node and their current status. The function is responsible for keeping an inventory of all hardware present in the node and its administrative and operational states. Included in the inventory information are the hardware identity and revision of all boards.

To do this test case, open Node Manager, check in MO view, and expand the Equipment View. Select the specific subrack, and click on the board with right mouse button. Choose Properties and a window with all the required information will pop up (General, Setting and Product Data).4.1.3 Software check

Check that the SW level of the node is the one expected, according with customer requirements.

Run Node Manager and check in Resource View-:SWManagement -> Upgrade Packages Check that the Upgrade package that is Active (Active value to Yes) is the one expected.

Upgrade package view Besides, you could check in check Resource View-:SWManagement, option Software -> SWManagement -> Configuration Version that the active cv corresponds also to the same expected level.

Configuration version view4.2Alarm Handling

4.2.1.1Transmission Link Alarms

Verify that when the physical line is disconnected from any port defined in any ET-MC1, ET-MF4, ET-C41 and ET-MC41, an alarm: Loss of Signal occurs.

Example

Alarm ID: SubNetwork=ONRM_ROOT_MO,MeContext=SGW-1_25

Perceived Severity: MAJOR

Specific Problem: Loss of Signal

Probable Cause: Loss of Signal

Event Time: 1970-01-01 02:58:14

Event Type: Communications Alarm

MO Instance: OS155 SPI Trail TP 2211

MO LDN: ManagedElement=1,Equipment=1,Subrack=2,Slot=21,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=2211

MO User Label: Os155SpiTtp 2211 Subrack 2 Slot 21

Notification ID: 25

4.2.1.2 Restart Tests

This test describes the kind of restart and the impact in the node.

(A) Board RestartFrom Node Manager or Ethernet connection, reload a board and observe how the LEDs change

state while the software loading is ongoing. The LED will blink (0,5 Hz) for a while, then it

gets steady.

Verify from Node Manager, after the restart, the state of the board, the administrative state:

Unlocked and the operational state Enabled.

(B) Node RestartFrom NODE MANAGER it is possible to restart the node.Right click on the Managed Element and select the MO actions

The system ask the type of restart: warm, refresh, cold or cold w test. Select warm restart and Restart Info. Then Press Execute and close the window

Result: node will be rebooted, contact is lost for a while.4.2.1.3 ET-MFG board tests

Restart ET-MFG Board

This test demonstrates how to restart an ET-MFG board. The element manager must be

running prior performing this test. The expected result will be the board is restarted

successfully.

-In the application Element manager window, expand the relevant node subrack folder..i.e

SGw MOD1 subrack.

The slots of the subrack are displayed.

Click, with right mouse button, on the ET-MFG board to restart and select Restart from the

pop-up menu.

Select Warm then Restart.

Note: The board is restarted.

4.2.1.4 ET-C41 pair redundancy

This test will prove the redundancy between the ET-C41 pair in SGw Module subracks

(A) Switch link manually by NODE MANAGER (GUI)1. Check which board has the link active.

NODE MANAGER-> Equipment-> Protection Groups, select the group that is under test

2. Click on .Switch Link. button. The .Working board. remains without changes but

.Working link. change to the other board.

Example result: initial state: Working Board 2/25, Working link 2/25

final state: Working Board 2/25, Working link 2/26

(B) Switch due to simulated board fault.

1. Check which board has the link active

NODE MANAGER-> Equipment-> Protection Groups, select the group that is under test.

2. To simulate a board fault, we lock the board; so, block the active ET-C41 board (for

example, if we suppose initial state above, board 2/25, subrack 2, slot 25)

NODE MANAGER-> Equipment->, select the board you want to block, click right button, select Lock

3. And verify that the standby (from example below: board 2/26, subrack 2, slot 26) will

become the .Working Board. and .Working Link..

NODE MANAGER-> Equipment-> Protection Groups, select the group that is under test and

Example result : initial state: Working Board 2/21, Working link 2/21

final state: Working Board 2/23, Working link 2/23

Note: Active calls will be dropped due to locking of working board

4.2.2Clock SynchronizationThe scope of this chapter is to verify the synchronization for the Ericsson Signalling Gateway for Mobile Networks (SGw).

In the SGw, the system clock is locked to the primary reference clock and distributed to all boards via the backplane. If the primary reference input becomes faulty, the system clock will automatically be locked to the secondary reference input or to the next input in the priority list.

Synchronization TestThe purpose of this test is to verify that the Active reference synchronization signal is

distributed in all the boards in the node, and the clock of the system is stable.

In case there are synchronization references defined and connected follow the procedure.

1. Check in Resource View and click on Synchronization References: Resource View-> Synchronization. These should be in status OK and ACTIVE to continue.

Plug out the cable of the first reference (transmission cable if ET-MF4 or ET-MC1

references; or external GPS signal cable if TUB reference). Check in NODE MANAGER that this

reference changes to .INACTIVE-fail. and that the next reference with status .ok.

takes over.

4.2.3Backup and Restore Test The purpose of this test is to perform a backup and restore it back.

Backup Test To make a backup, use NODE MANAGER.

From Managed Element expand the SWManagement View, select: Configuration Versions - click right button -> Create CV

- Write a name for the backup in the box: CV name.

- Write any comment regarding the dump in the box: Comment.

Backup name Then, press Execute . Result : wait a small time until this windows disappear; in this moment the new backup has been created. You can check it looking in the SWManagment View, select: Configuration Versions. In right section, you could see the new cv created, with the state Executing Latest. Restore Test. Follow this procedure to restore a node with a backup made previously.

In Managed Element, SWManagement menu select Configuration Versions. Then the Contents window will show all the backups available.

Then choose any backup from the list, and set Startable, you can see the state of the CV is startable. Then right lick on the Managed Element and select the MO actions

The system ask the type of restart: warm, refresh, cold or cold w test. Select warm restart and Restart Info. Then Press Execute and close the window

Choosing type of restart

Result: node will be rebooted, contact is lost for a while.

Once that node is recovered, you can check that the system has been reloaded with the selected CV, looking in the SWManagement View, select: Configuration Versions. In right window, you could see the selected reloaded CV state is now Executing, loaded and Latest startable.4.3 Core Network IntegrationThe purpose of this chapter is to integrate the node with the circuit switched

network (CS).

This chapter describes how to verify vital parameters and data, in order to

ensure that the circuit switched voice and data is up and running between the

SGw and the interconnected Nodes as MSC Server and PSTN.

4.3.1 Mc Interface Integration (SGw MSC Server)

Mc Interface is the connection point between SGw and the MSC Server.

4.3.1.1 Verification of IP Layer towards MSC Server Interface

4.3.1.1.1 Verification of IP GPB Hosts Status

This sub chapter will verify that the IP GPB Hosts (General purpose Processor

Board) are correctly defined.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, expand IP

folder and select IP GPB Hosts folder.

Result: The current IP GPB Hosts are displayed in the right pane of the

window.

______________________________________________________________

2. Verify that the Operational State is Enabled.

______________________________________________________________

3. In the SGw Node Manager Tools folder, select Shell folder and give the

UserName and Password to access the node command prompt.

______________________________________________________________

4. Verify with ipac_ping command that ping is successful for all necessary

destination IP addresses.

Note: This command triggers an action of sending Internet Control

Message Protocol (ICMP) echo request (ping) from the

IpAccessHostGpb towards the defined destination IP address.

The result of each ICMP echo request is displayed in the terminal.

At the end the summary of the ping statistics is displayed.

______________________________________________________________

5. Select File and Exit to close the Shell window.

______________________________________________________________

4.3.1.1.2 Verification of SCTP Status

This sub chapter will verify that the SCTP are correctly defined.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, expand

Signalling folder and expand SCTP folder.

Result: The current SCTPs are displayed in the right pane of the window.

______________________________________________________________


______________________________________________________________

4.3.1.1.3 Verification of M3U Associations Status

This sub chapter will verify that the M3UA Associations are correctly defined.

______________________________________________________________


Signalling folder and expand MTP3b folder.

______________________________________________________________

2. Expand correct MTP3bSp folder and select M3U Associations folder

Result: The M3U Associations are displayed in the right pane of the

window.

______________________________________________________________


______________________________________________________________

4.4 POI Interface Integration (SGw-PSTN/PLMN)

Verification of TDM Layer towards PSTN/PLMN Interface4.4.1 Verification of Os155SpiTtp Physical Port Status (ET-C41/ET-MC41)

This sub chapter will verify that the Os155SpiTtp physical path Termination

Points are correctly define.

______________________________________________________________

1. In the SGw Node Manager double click Resource View and expand

the Equipment folder.

Result: The node subracks are displayed.

______________________________________________________________

2. Expand the subrack folder containing the ET-C41/ET-MC41 board with

the Os155 physical path TP to view.Result: The subrack boards are displayed.

______________________________________________________________

3. Select the relevant ET-C41/ET-MC41 board folder.

Result: The board TPs are displayed in the right pane of the window.

______________________________________________________________

4. Verify that the administrative state is set to Unlocked.

If any administrative state is set to Locked, Unlock the administrative state.

______________________________________________________________


______________________________________________________________

6. Select the relevant Termination Point (TPs).

Result: The relevant E1/T1/J1 TPs are displayed in the right pane of the

window.

______________________________________________________________

7. Verify that the Operational State for the relevant TPs is set to Enabled.

______________________________________________________________

4.4.2 Verification of E1 Physical Path Termination Point Status (ET-MC1)

This sub chapter will verify that the E1 physical path Termination Points are

correctly defined.

Important The same procedure is applicable for T1 Physical Path

Termination Point.

______________________________________________________________




______________________________________________________________

2. Expand the subrack folder containing the ET-MC1 board with the E1

physical path TP to view.

Result: The subrack boards are displayed.

______________________________________________________________

3. Select the relevant ET-MC1 board folder.


______________________________________________________________



______________________________________________________________


______________________________________________________________

4.4.3 Verification of DS0 Bundle Status

This sub chapter will verify that the DS0 Bundle are correctly defined.

______________________________________________________________


the TDM folder.

______________________________________________________________

2. Select the DS0 Bundles folder.

Result: The DS0 Bundles are displayed in the right pane of the window.

______________________________________________________________

3. Verify that theTDM Mode and Operational State are Enabled.

______________________________________________________________

4.4.4 Signalling Links

Signalling Interface in SGw can have 3 different types of C7 signalling links.

Select the correct signalling link type as per network design Narrowband Signalling Links, SS7 over TDM Section 4.5.6.1.

High Speed Signalling over TDM, MTP2 Based HSL Section 4.5.6.2

High Speed Signalling over ATM, NNI-SAAL Based HSLSection 4.5.6.3 4.4.4.1 Verification of MTP2 Termination Point Status

This sub chapter will verify that the MTP2 termination point data are correctly

defined.

______________________________________________________________


Signalling folder and expand MTP2 folder.

______________________________________________________________

2. Select MTP2 Terminations view.

Result: The MTP2 Terminations are displayed in the right pane of the

window.

______________________________________________________________


______________________________________________________________

4. Step to Section 4.5.7______________________________________________________________

4.4.4.2 Verification of MTP2 HSL Termination Point Status

This sub chapter will verify that the MTP2 termination point data are correctly

defined.

______________________________________________________________


Signalling folder and expand MTP2 HSL folder.

______________________________________________________________

2. Select MTP2 Terminations view.

Result: The MTP2 Terminations are displayed in the right pane of the

window.

______________________________________________________________


______________________________________________________________

4. Step to Section 4.5.7______________________________________________________________

4.4.4.3 Verification of AAL5 Termination Point StatusThis sub chapter will verify that the AAL5 Termination Point Status is correct.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, expand ATM

folder and select the AAL5 TPs folder.

Result: The current AAL5 termination points are displayed in the right

pane of the window.

______________________________________________________________


______________________________________________________________

4.4.4.4 Verification of NNI-SAAL Layer Status

Comment: This is an access point for a user where an NNI-SAAL

connection is terminated. The access point depends on

an AAL5 connection termination located on the same

processor.

This sub chapter will verify that the NNI-SAAL Termination Point (TP) are

correctly defined.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, select ATM

view and select the NNI-SAAL Terminations folder under NNI-SAAL.

Result: The current Termination Points are displayed in the right pane of

the window.

______________________________________________________________


______________________________________________________________

4.4.5 Verification of MTP3b Signalling Links Status

This sub chapter will verify that the MTP3b Signalling Links towards the BSC

is in operational state.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, select

Signalling view and expand the MTP3b folder.

______________________________________________________________

2. Expand the relevant Signalling Point folder.

______________________________________________________________

3. Expand MTP3b Signalling Links folder.

______________________________________________________________

4. Select MTP3b Signalling Links Set folder.

Result: The Signalling Links are displayed in the right pane of the window.

______________________________________________________________

5. Verify that the Signalling Links are Enabled

______________________________________________________________

6. Expand MTP3b Signalling Routes folder. Select theSignalling Route Set

folder.

Result: The Signalling Routes are displayed in the right pane of the

window.

______________________________________________________________

7. Verify that the Signalling Routes are Enabled.

______________________________________________________________

8. The job is completed. Sign the integration report.

______________________________________________________________

4.5 Verification of ATM Layer (User Part)4.5.1.1 Verification of Os155 Physical Port Status (ET-M4/ET-MF4)

This sub chapter will verify that the Os155 physical path Termination Points

are correctly defined.

______________________________________________________________




______________________________________________________________

2. Expand the subrack folder containing the ET-M4/ET-MF4 board with the

Os155 physical path TP to view.


______________________________________________________________

3. Select the relevant ET-M4/ET-MF4 board folder.


______________________________________________________________



______________________________________________________________


______________________________________________________________

4.5.1.2 Verification of AAL2 Access Point Status

This sub chapter will verify that the access Point status is correct.

Note: The AAL2 connections are set up in the SGw using Q.2630.2

signalling.

______________________________________________________________


folder and expand AAL2 folder.

______________________________________________________________

2. Select Aal2Sp folder.

Result: The Aal2Aps are displayed in the right pane of the window.

______________________________________________________________


______________________________________________________________

4.5.1.3 Verification of AAL2 Path Status

This sub chapter describes how to verify the status of an AAL2 path.

Comment: An AAL2 Path is an ATM VC connection that carries

multiplexed AAL2 links.

______________________________________________________________


folder and expand AAL2 folder.

______________________________________________________________

2. Select Aal2Paths folder.

Result: The Aal2Paths are displayed in the right pane of the window.

______________________________________________________________


If the administrative state is set to Locked, unlock the administrative state.

______________________________________________________________


______________________________________________________________

4.5.2 Verification of ATM Layer (Signalling Part)

4.5.2.1 Verification of Os155 Physical Port Status (ET-M4/ET-MF4)

This sub chapter will verify that the Os155 physical path Termination Points

are correctly defined.

______________________________________________________________




______________________________________________________________

2. Expand the subrack folder containing the ET-M4/ET-MF4 board with the

Os155 physical path TP to view.


______________________________________________________________

3. Select the relevant ET-M4/ET-MF4 board folder.


______________________________________________________________



______________________________________________________________


______________________________________________________________

4.5.2.2 Verification of AAL5 Termination Point Status

This sub chapter will verify that the AAL5 Termination Point Status is correct.

______________________________________________________________


folder and select the AAL5 TPs folder.

Result: The current AAL5 termination points are displayed in the right

pane of the window.

______________________________________________________________


______________________________________________________________

4.5.2.3 Verification of NNI-SAAL Layer Status

Comment: This is an access point for a user where an NNI-SAAL

connection is terminated. The access point depends on

an AAL5 connection termination located on the same

processor.

This sub chapter will verify that the NNI-SAAL Termination Point (TP) are

correctly defined.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, select ATM

view and select the NNI-SAAL Terminations folder under NNI-SAAL.

Result: The current Termination Points are displayed in the right pane of

the window.

______________________________________________________________


______________________________________________________________

4.5.2.4 Verification of MTP3b Signalling Links Status

This sub chapter will verify that the MTP3b Signalling Links towards the MSC

Server is in operational state.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, select

Signalling view and expand the MTP3b folder.

______________________________________________________________

2. Expand the relevant Signalling Point folder.

______________________________________________________________

3. Expand MTP3b Signalling Links folder.

______________________________________________________________

4. Select MTP3b Signalling Links Set folder.

Result: The Signalling Links are displayed in the right pane of the window.

______________________________________________________________

5. Verify that the Signalling Links are Enabled

______________________________________________________________

6. Expand MTP3b Signalling Routes folder. Select theSignalling Route Set

folder.

Result: The Signalling Routes are displayed in the right pane of the

window.

______________________________________________________________

7. Verify that the Signalling Routes are Enabled.

______________________________________________________________

4.3.3 Verification of IP Layer (SIGTRAN)4.5.3.1 Verification of IP GPB Hosts Status

This sub chapter will verify that the IP GPB Hosts (General purpose Processor

Board) are correctly defined.

______________________________________________________________

1. In the SGw Node Manager double click Resource View, expand IP

folder and select IP GPB Hosts folder.

Result: The current IP GPB Hosts are displayed in the right pane of the

window.

______________________________________________________________


______________________________________________________________

3. In the SGw Node Manager Tools folder, select Shell folder and give the

UserName and Password to access the node command prompt.

______________________________________________________________

4. Verify with ipac_ping command that ping is successful for all necessary

destination IP addresses.

Note: This command triggers an action of sending Internet Control

Message Protocol (ICMP) echo request (ping) from the

IpAccessHostGpb towards the defined destination IP address.

The result of each ICMP echo request is displayed in the terminal.

At the end the summary of the ping statistics is displayed.

______________________________________________________________

5. Select File and Exit to close the Shell window.

______________________________________________________________

4.5.3.2 Verification of SCTP Status

This sub chapter will verify that the SCTP are correctly defined.

______________________________________________________________


Signalling folder and select SCTP folder.

Result: The current SCTPs are displayed in the right pane of the window.

______________________________________________________________


______________________________________________________________

4.5.3.3 Verification of M3U Associations Status

This sub chapter will verify that the M3UA Associations are correctly defined.

______________________________________________________________


Signalling folder and expand MTP3b folder.

______________________________________________________________

2. Expand correct MTP3bSp folder and select M3U Associations folder

Result: The M3U Associations are displayed in the right pane of the

window.

______________________________________________________________


______________________________________________________________


______________________________________________________________4.5.4 Verification of IP Layer (User Part)

4.5.4.1 Verification of Gigabit Ethernet Status

This instruction describes how to verify a Gigabit Ethernet.

______________________________________________________________


Equipment Folder.

______________________________________________________________

2. Expand the subrack folder containing EtMfg boards.

Result: The EtMfg are displayed.

______________________________________________________________

3. Select the relevant EtMfg board

Result: The GigaBitEthernet are displayed in the right pane of the window.

______________________________________________________________


If the administrative state is set to Locked, unlock the administrative state.

______________________________________________________________


______________________________________________________________

4.5.4.2 Verification of IP Interface Status

This instruction describes how to verify an IP Interface over GigaBitEthernet.

______________________________________________________________


Equipment Folder.

______________________________________________________________

2. Expand the subrack folder containingEtMfg boards.

Result: The EtMfg are displayed.

______________________________________________________________

3. Expand the EtMfg Folder.

______________________________________________________________

4. Select the GigabitEthernet where the IP Interface is located.

Result: The IP Interface are displayed in the right pane of the window.

______________________________________________________________


______________________________________________________________

4.6 Common Interfaces Status Integration4.6.1 Verification of Media Stream Device Pool Status

This sub chapter will verify that the Media Stream Device Pool data is correctly

defined.

The Media Stream Function provides the basic functions needed to support the

circuit switched speech services in the UMTS and GSM networks. The MSC

server remotely controls all functions.

All Media Stream devices are pooled to enable more efficient usage of the

network resources.

______________________________________________________________


Devices folder and select Device Pools folder.

Result: The Device Pools are displayed in the right pane of the window.

______________________________________________________________

2. For each individual Device Pool, verify that there are no capacity Failed ,

capacity DependencyFailed or capacityDependencyLocked Devices.

______________________________________________________________


______________________________________________________________4.7 Network verification

The scope of this section is to describe the procedure of performing traffic test

cases through the SGw and make sure that the node is operational into the

network towards other nodes.

Important Its mandatory to check the Devices, Links, Paths, ... in the

MSC server.

4.7.1 Traffic Cases

For a successful node operation, the signaling links with all the nodes should be enabledand the result should be OK.

______________________________________________________________

Acceptance Report, SGw

Network Element IdentitiesThis Integration Report is unique for the Network Element.Table 1 Network Element information

Network Element information

Type: SGw

IPB no.Site/node name:

Ericsson personnel

name (block letters):Name (block letters):

Customer personnel

name (block letters):Name (block letters):

The steps performed during the integration procedure are specified in this integration reportNumber of Outstanding Items: _____ pages: ______

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

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

Ericsson Personal

Customer Personal

Signature

Signature

Outstanding Item ListThis Outstanding Item List is unique for the Network Element specified in the Network Element Identities on the first page of this document.

An action plan for each outstanding item should be prepared between Ericsson and the customer.

______________________________________________________________

______________________________________________________________

Outstanding Item Number: _______

Reason/ Comment___________________________________________________

___________________________________________________

___________________________________________________

___________________________________________________

Outstanding Item Number: _______

C:\Documents and Settings\eilhhmi\Desktop\SGW-R5_AT procedure-26-06-2008.doc

Date post:	08-Apr-2015
Category:	Documents
Upload:	vipin-singh
View:	156 times
Download:	0 times