Rapport MGC-8 ATCA Install and Upgrade Guide.pdf

7/23/2019 Rapport MGC-8 ATCA Install and Upgrade Guide.pdf

http://slidepdf.com/reader/full/rapport-mgc-8-atca-install-and-upgrade-guidepdf 1/238

Title page

Rapport Media Gateway Controller (MGC-8)

ATCA Install and Upgrade

255-400-022R9.X.X

Issue 12 | July 2015

Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements



Legal notice

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective

owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright © 2015Alcatel-Lucent. All rights reserved.

Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside

Alcatel-Lucent without its written authorization.

Not to be used or disclosed except in accordance with applicable agreements.




Contents

About this document

Purpose .......................................................................................................................................................................................... xiiixiii

What's new ................................................................................................................................................................................... xiiixiii

Intended audience ...................................................................................................................................................................... xivxiv

How to use this document ....................................................................................................................................................... xivxiv

Conventions used ......................................................................................................................................................................... xvxv

Related information ...................................................................................................................................................................

xvixvi

Document support ................................................................................................................................................................... xviiixviii

Technical support ..................................................................................................................................................................... xviiixviii

How to comment ..................................................................................................................................................................... xviiixviii

1 System requirements

Overview ...................................................................................................................................................................................... 1-11-1

MGC-8 hardware requirements ........................................................................................................................................... 1-21-2

Installing the MGC-8 software ............................................................................................................................................ 1-51-5

Firmware and software versions ....................................................................................................................................... 1-101-10

Configuration, administration, and maintenance ........................................................................................................ 1-111-11

2 System configuration

Overview ...................................................................................................................................................................................... 2-12-1

Prerequisite procedure ............................................................................................................................................................. 2-22-2

3 Prepare for the LCP installation

Overview ...................................................................................................................................................................................... 3-13-1

Mandatory prerequisite procedures .................................................................................................................................... 3-13-1

Prepare the flashdrive .............................................................................................................................................................. 3-33-3

....................................................................................................................................................................................................................................

Rapport MGC-8 ATCA255-400-022R9.X.XIssue 12 July 2015


iii



Gather the system configuration information ................................................................................................................. 3-63-6

Complete the configuration worksheets ........................................................................................................................... 3-73-7

Configure the laptop .............................................................................................................................................................. 3-113-11

Power on the shelf ..................................................................................................................................................................

3-153-15

What’s next? ............................................................................................................................................................................. 3-153-15

4 Configure ShMCs and jumpstart the blade with OAM server A functionality

Overview ...................................................................................................................................................................................... 4-14-1

Introduction ................................................................................................................................................................................. 4-14-1

Field re-installed software ..................................................................................................................................................... 4-34-3

ShMC IP configuration ........................................................................................................................................................... 4-44-4

Hub IP configuration procedure .......................................................................................................................................... 4-54-5

Jumpstart the blade with OAM server A functionality ................................................................................................ 4-64-6

What’s next? ............................................................................................................................................................................. 4-104-10

5 Load transfer and pre-installation

Overview ...................................................................................................................................................................................... 5-15-1

Introduction ................................................................................................................................................................................. 5-15-1

Load transfer and field installation procedure ................................................................................................................ 5-25-2

6 Configure blade with OAM server A functionality

Overview ...................................................................................................................................................................................... 6-16-1

Introduction ................................................................................................................................................................................. 6-16-1

Prerequisite procedure ............................................................................................................................................................. 6-26-2

Verify the system configuration ........................................................................................................................................... 6-36-3

What’s next? ...............................................................................................................................................................................

6-46-4

7 Load installation and LCP check

Overview ...................................................................................................................................................................................... 7-17-1

Introduction ................................................................................................................................................................................. 7-17-1

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

iv Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements

Rapport MGC-8 ATCA255-400-022R9.X.X

Issue 12 July 2015



Load installation procedure ................................................................................................................................................... 7-27-2

Changing hub and ShMC login and password ............................................................................................................... 7-37-3

LCP check procedure ............................................................................................................................................................... 7-47-4

8 Growth and de-growth of ALGPv2 blades

Overview ...................................................................................................................................................................................... 8-18-1

Introduction ................................................................................................................................................................................. 8-28-2

Rules and restrictions .............................................................................................................................................................. 8-28-2

Grow in the ACCM Blades for the non-cohost (standalone) MGC-8 ................................................................... 8-48-4

Grow in the ADCM blades ................................................................................................................................................. 8-138-13

Configure and enable CPM ................................................................................................................................................ 8-208-20

Backing up blade configuration ........................................................................................................................................ 8-218-21

De-growth procedure ............................................................................................................................................................ 8-238-23

9 Provisioning of ALGPv2 blades

Overview ...................................................................................................................................................................................... 9-19-1

Provision the ACCM and ADCM blades ......................................................................................................................... 9-29-2

Provisioning AMC SS7 cards ............................................................................................................................................... 9-99-9

Performing DS1 or E1 loopbacks ..................................................................................................................................... 9-119-11

Check the management/signaling interface duplex setting ..................................................................................... 9-159-15

Check the network IP address of the MGC-8 and other NEs with which it communicates ...................... 9-189-18

What’s next ............................................................................................................................................................................... 9-199-19

10 Final activities

Overview ................................................................................................................................................................................... 10-110-1

Introduction ..............................................................................................................................................................................

10-110-1

Final activities .......................................................................................................................................................................... 10-210-2

Graceful shutdown ................................................................................................................................................................. 10-510-5

What’s next? ............................................................................................................................................................................. 10-610-6

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



v



11 Upgrade scenarios and procedures

Overview ................................................................................................................................................................................... 11-111-1

Upgrade scenarios .................................................................................................................................................................. 11-211-2

Upgrade requirements ...........................................................................................................................................................

11-211-2

Downloading and upgrading NE software using the COM GUI .......................................................................... 11-311-3

Provisioning support during upgrade when GR MGC-8s are on different releases ....................................... 11-411-4

Upgrade both the LCP software and the ALGPv2 software ................................................................................... 11-611-6

Upgrade the ALGPv2 software ....................................................................................................................................... 11-1511-15

Cold upgrade LCP and ALGPv2 software .................................................................................................................. 11-2011-20

12 Upgrade working-working GR switches

Overview ................................................................................................................................................................................... 12-112-1

Upgrading working-working GR switches ................................................................................................................... 12-212-2

13 Rollback and backout procedures

Overview ................................................................................................................................................................................... 13-113-1

Rollback of LCP and MGC-8 software .......................................................................................................................... 13-213-2

Backout of LCP and MGC-8 upgrade ............................................................................................................................ 13-713-7

Backout MGC-8 only upgrade ........................................................................................................................................ 13-1213-12

A Hardware illustrations

Overview ..................................................................................................................................................................................... A-1A-1

ATCA Shelf ................................................................................................................................................................................ A-1A-1

Processor blade (FM016JB or FM016JP) ....................................................................................................................... A-3A-3

Ethernet hub ............................................................................................................................................................................... A-4A-4

Ethernet hub RTM ...................................................................................................................................................................

A-5A-5

Shelf manager card .................................................................................................................................................................. A-6A-6

B Worksheets

Overview ..................................................................................................................................................................................... B-1B-1

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

vi Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Worksheet 1 ................................................................................................................................................................................ B-2B-2

Worksheet 2 ................................................................................................................................................................................ B-3B-3

Worksheet 3A ............................................................................................................................................................................ B-6B-6

Worksheet 3B ............................................................................................................................................................................

B-7B-7

C ShMC and ethernet hub commands

Overview ..................................................................................................................................................................................... C-1C-1

ShMC commands ..................................................................................................................................................................... C-1C-1

Ethernet hub commands ........................................................................................................................................................ C-2C-2

D Initiating a SOL session with a processor blade

Overview ..................................................................................................................................................................................... D-1D-1

SOL session for a processor blade procedure ................................................................................................................ D-2D-2

Determining the SOL IP address on a blade .................................................................................................................. D-3D-3

E Changing the SSH/SOL IP of hub 7/8

Overview ..................................................................................................................................................................................... E-1E-1

Prerequisites to change SSH/SOL IPs on Hub 7/8 ....................................................................................................... E-2E-2

Hub and shmc configuration ................................................................................................................................................ E-3E-3

Procedure and useful commands for changing IPs ...................................................................................................... E-6E-6

F Software loads from the factory

Software Loads .......................................................................................................................................................................... F-1F-1

G Software ASLM

Overview ..................................................................................................................................................................................... G-1G-1

Base and session entitlements ............................................................................................................................................. G-2G-2

Accessing the ASLM tool ..................................................................................................................................................... G-5G-5

Generating a license file ........................................................................................................................................................ G-7G-7

H Document issue history

Overview ..................................................................................................................................................................................... H-1H-1

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



vii



Reissue history .......................................................................................................................................................................... H-1H-1

Index

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

viii Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



List of tables

1 Document changes in Issue 12, July 2015 ........................................................................................................ xiiixiii

2 Alcatel-Lucent MGC-8 ATCA documentation .............................................................................................. xviixvii

3 MGC-8 ATCA and COTS common documentation .................................................................................... xviixvii

1-1 Login and passwords ................................................................................................................................................ 1-41-4

1-2 Installation packages, files, and scripts ........................................................................................................... 1-101-10

9-1 Port to physical interface mapping ................................................................................................................... 9-169-16

C-1 ShMC commands ......................................................................................................................................................

C-1C-1

C-2 Ethernet hub commands ......................................................................................................................................... C-2C-2

E-1 Customer values of SSH and SOL ...................................................................................................................... E-3E-3

G-1 Software license names and descriptions ......................................................................................................... G-3G-3

H-1 Issue 11, April 2015, Reason for reissue .......................................................................................................... H-1H-1

H-2 Issue 10, March 2015, Reason for reissue ....................................................................................................... H-2H-2

H-3 Issue 9, January 2015, Reason for reissue ....................................................................................................... H-2H-2

H-4 Issue 8, December 2014, Reason for reissue .................................................................................................. H-2H-2

H-5 Issue 7, November 2014, Reason for reissue ................................................................................................. H-3H-3

H-6 Issue 6, October 2014, Reason for reissue ...................................................................................................... H-3H-3

H-7 Issue 5, June 2014, Reason for reissue ............................................................................................................. H-3H-3

H-8 Issue 4, May 2014, Reason for reissue ............................................................................................................. H-4H-4

H-9 Issue 3, April 2014, Reason for reissue ............................................................................................................ H-4H-4

H-10 Issue 2, April 2014, Reason for reissue ............................................................................................................

H-4H-4

H-11 Issue 1, April 2014, Reason for reissue ............................................................................................................ H-4H-4

....................................................................................................................................................................................................................................



ix



List of tables

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

x Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



List of figures

1-1 Factory hardware placement example ................................................................................................................ 1-31-3

4-1 Response example ..................................................................................................................................................... 4-74-7

8-1 Example ...................................................................................................................................................................... 8-368-36

9-1 Example of a successful response ....................................................................................................................... 9-29-2

9-2 Login example ............................................................................................................................................................ 9-39-3

A-1 ATCA Shelf Example .............................................................................................................................................. A-2A-2

A-2 Processor Blade .........................................................................................................................................................

A-3A-3

A-3 Ethernet hub ............................................................................................................................................................... A-4A-4

A-4 Hub RTM Card Example ....................................................................................................................................... A-5A-5

A-5 Shelf manager card (ShMC) example ............................................................................................................... A-6A-6

G-1 ASLM ........................................................................................................................................................................... G-5G-5

G-2 ASLM Access Page ................................................................................................................................................. G-6G-6

....................................................................................................................................................................................................................................



xi



List of figures

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

xii Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



About this documentAbout this document

Purpose

This guide provides Installers with the instructions needed to successfully complete a

field installation or upgrade of the Linux Control Platform (LCP) and the Alcatel-Lucent

Gateway Platform (ALGPv2) software on MGC-8 Advanced Telecommunications

Computing Architecture (ATCA) hardware.

Note: This document is applicable to R9.4 and later releases.

Product name change

Starting with release 9.5, the 5060 Media Gateway Controller (MGC-8) product is

renamed as Rapport Media Gateway Controller. Any references in the legacy documents,

appendices, text, or images to 5060 MGC-8 or MGC-8, represents Rapport MGC-8.

Throughout the document, Rapport MGC-8 will be hereafter referred to as MGC-8.

Similarly, the COM will be referred as COM and the 7510 MGW will be referred as

MGW.

What's new

This is a reissue of the Rapport MGC-8 ATCA Install and Upgrade Guide, 255-400-022.

This is Issue 12.

The major changes introduced in this issue of the document are described in the following

paragraphs. Changes introduced in prior issues of the document are shown in Appendix

H, “Document issue history”.

The document changes in this issue are shown in the following table.

Table 1 Document changes in Issue 12, July 2015

Document Issue Description Location

12 Added new product name Rapport Front matter

Product name change: updated 5060

MGC-8 to MGC-8, 1360 COM to

COM, and 7510 MGW to MGW.

Global

...................................................................................................................................................................................................................................



xiii



Intended audience

This document is for internal use by Alcatel-Lucent personnel and designated Field

Installers. The Installer should be familiar with the equipment, the component names,

associated names, and their physical location prior to installation.

The information in this document assumes that the Installer has a good understanding of

the following:

• MGC-8 hardware, firmware, architecture/design, and operations

• Red Hat Linux operations (basic commands)

• IP data networking architecture/design

How to use this document

Software evolution key for upgrading

A hot upgrade evolution key is required for an LCP platform software upgrade. This key

is not required for the initial field installation of LCP software. The evolution key is alsonot needed when the first six digits of the LCP platform software version do not change.

For example an upgrade from 24.15.31.05 to 24.15.31.06 will not require an evolution

key.

Evolution key information is available in QDI document 52114. You must know the LCP

version from which you are upgrading and the version to which you are upgrading to in

order to determine the required key.

Use this document in conjunction with the associated release notes and application

specific documents. Upon completion of the installation, the installer will be ready to

provision the system and may need to perform additional steps, as indicated in the release

notes.

This document has been divided into logical parts and sections:

• Part I provides instructions for installing the LCP base platform.

• Part II provides the instructions for installing the ALGPv2 software.

• Part III provides instructions for upgrading the LCP and ALGPv2 software.

Typically, the end of each section can be used as a pause point (you can continue the

following day for example), unless noted otherwise.

Steps that take longer than 5 minutes to complete indicate approximate time lines for

completion. Additionally, time estimates are provided at the start of each new section. Theexecution time of the entire procedure depends largely on previous experience and the

complexity of the configuration.

To minimize procedural errors, it is recommended that the Installer review the entire

document before performing any of the procedures.

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

xiv Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Conventions used

Appearance Description

italicized text • File and directory names

• Emphasized information

• Titles of publications

• A variable that the user supplies

graphical user interface text or key

name• Text that is displayed in a graphical user interface

or in a hardware label

• The name of a key on the keyboard

input text Command names and text that the user types or

selects as input to a system

output text Text that a system displays or prints

Terminology

In this document the following terms are used interchangeably.

• The words cabinet and rack

• The words shelf, sub-rack, and chassis

• The words shelf, sub-rack, and chassis

• The words card and blade

• The words processor card, node, and Ethernet Hub

• The words hub and Processor Blade

• The words IMS service and the ngss

• The fs5k service and the ngfs.

Acronyms

This document uses the following acronyms.

Acronym Meaning

ACCM Advanced Centralized Compute Module

ADCM Advanced Distributed Compute Module

BTS Billing and Traffic System

CNFG Configuration Service

COTS Common Off The Shelf

CP Centralized Processing Server

CPM Centralized Password Management

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



xv



Acronym Meaning

CS Call Server

Fka Formerly known as

FRU Field Replaceable Unit

HDD Hard Disk Drive

iLO Integrated Lights-Out

IMS IP Multimedia Service

LAN Local Area Network

LCP Linux Control Platform

MGC Media Gateway Controller

MI Maintenance Interface Service

OA HP BladeServer Onboard Administrator

OAM&P Operations, Administration, Maintenance, and Provisioning.

OAMSA OAM Server A

PDU Power Distribution Unit

RBSU ROM Based Setup Utility

RCC Reliable Cluster Computing

SD SIP Distributor Server

SIM Software Installation Manager

SNS Shared Network Service

SSH Secure Shell

VM Virtual Machine

VCP Virtualization Control Platform

VMM-HI Virtualization Machine Management and Host Infrastructure

Related information

Refer to the following Alcatel-Lucent MGC-8 ATCA documentation as needed for

additional information.

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

xvi Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



List of documents

Table 2 Alcatel-Lucent MGC-8 ATCA documentation

Product Part number Product description

Rapport MGC-8 ATCA

Operations Guide

255-400-000 Contains platform provisioning procedures.

Rapport MGC-8 ATCA

Maintenance and Diagnostic

Procedures Guide

255-400-001 Describes procedures to maintain and check

switch operation. Also included are detailed

level procedures necessary to replace switch

hardware, retrieve PM data and status,

perform a manual switchover, and recover

after a switch failure.

Rapport MGC-8 ATCA TL1

Commands Reference Guide

255-400-002 Contains TL1 commands to provision the

platform, functional entities and services.

Rapport MGC-8 ATCA

System Software Release

Notes

255-400-006 Describes new features and feature

enhancements, new and modified TL1

commands, hardware and software

limitations, and other important

release-specific information not available

elsewhere.

Rapport MGC-8 ATCA

Alarms and Troubleshooting

Procedures Guide

255-400-019 Describes procedures for obtaining alarm

information and provides references to

trouble analysis procedures for determining

the cause and correction of the problems.

Rapport MGC-8 ATCA Install

and Upgrade Guide

255-400-022 Provides installation and upgrade

instructions for LCP software and ALGPv2

software on the MGC-8 ATCA hardware.

Rapport MGC-8 ATCA SCME

Guide

255-400-023 Contains information for MGC-8 ATCA

switches to be deployed in either a wireline

or Gateway Mobile Switching Center

(GMSC) application.

Rapport MGC-8 ATCA

Hardware Guide

255-400-209 Contains MGC-8 ATCA hardware

information for engineering a site including:

module descriptions, hardware

specifications, cabling as well as

environmental and power requirements.

Table 3 MGC-8 ATCA and COTS common documentation

Rapport MGC-8 ATCA and

COTS BTS User Guide

255-400-403 Contains billing information for the BTS

application.

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



xvii



Table 3 MGC-8 ATCA and COTS common documentation (continued)


COTS BTS Upgrade Guide

255-400-428 Describes the procedures required to

upgrade the BTS application.


COTS BTS Release Notes

255-400-404 Describes new BTS features and feature

enhancements, new and modified TL1commands, hardware and software

limitations, and other important

release-specific information not available

elsewhere.


COTS Security Guide

255-400-020 Describes any security enhancements and

also provides additional information on

security not found in other guides.

Document support

For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at

the following telephone numbers.

From United States

• If you are using a landline, a cellular phone or VOIP, dial this number:

1-888-582-3688

From other countries

• If you are using a cellular phone or VOIP, dial this number: +1-630-224-2485

• If you are using a landline (phone without a plus [+] character), replace the plus sign

with your country's exit code. Dial this number: Exit code for the country of origin:

1-630-224-2485. See the country-specific exit codes listed here.

These numbers apply for document support only. Please see the section “Technical

support” for details about product hardware, software, and technical support.

Technical support

For technical support, contact your local Alcatel-Lucent customer support team. See the

Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact

information.

How to comment

To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-

lucent.com/comments/) or e-mail your comments to the Comments Hotline

([email protected]).

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

xviii Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015

http://www.howtocallabroad.com/codes.html


http://www.alcatel-lucent.com/support/


http://infodoc.alcatel-lucent.com/comments/




mailto:[email protected]












1 1System requirements

Overview

Purpose

This chapter provides an overview of the hardware and software requirements for the

installation of the LCP and the ALGPv2 software on the MGC-8. Additionally, it providesfirmware and password information.

The MGC-8/VSG has two configurations, the non-co-host (standalone) and the co-host.

• In a non-co-host (standalone) configuration, the modules in slots 1 and 2 provide

OAM server functionality and slots 3 and 4 are typically for ACCM modules.

• In a co-host configuration, the modules in slots 1 and 2 provide OAM server

functionality and ACCM functions.

When MI/ACCM is co-hosted,the ACCM is always placed in slots 1/2. ACCM always

have poolId=1 ADCMs can therefore go in slots 3/4, 5/6, 9/10, 11/12 and even 13/14.

However, only a maximum of 4 pairs is supported, not a fully loaded 5 ADCM pair configuration. The allowed slot / poolId combinations are: Slots 3/4: PoolId = 2, Slots

5/6: PoolId = 3, Slots 9/10: PoolId = 4, Slots 11/12: PoolId = 5, and Slots 13/14:

PoolId = 6

Contents

MGC-8 hardware requirements 1-2

Installing the MGC-8 software 1-5

Firmware and software versions 1-10

Configuration, administration, and maintenance 1-11

...................................................................................................................................................................................................................................



1-1



MGC-8 hardware requirements

Purpose

This section describes the supported system hardware and any additional hardware that is

required for the installation.

System hardware

The following hardware is supported with this release:

• Processor blades which are front facing blades for the ATCA chassis.

– Blade without AMC SS7 - FM016JB

– Blade with AMC SS7 - FM016JP

• Rear Transition Module (NASYS)

• Ethernet Hub Blade or Hub Switch (NBMASW1)

• T1/E1 Rear Transition Module (RPCMHDAA)

• Rear Filler (NAFILL)

• Front Filler (NBFILL)

The MGC-8 system operates as a 1-shelf (1CP) configuration. The system can be

rack-mounted in an open rack or mounted inside of a cabinet. Refer to the Rapport

MGC-8 Hardware Guide, 255-400-209 for a complete description of the supported

hardware.

The MGC-8 is a fully-redundant system. Following are some system requirements:

• Each blade has a sister blade that sits next to it.

• The blades are numbered from 1 to 15, left to right.

• Modules with OAM server functionality are always in slots 1 and 2. In a co-host

configuration, the modules in slots 1 and 2 provide OAM server functionality and

ACCM functions. The co-host configuration does not support the OAM Server

(NBRZAL) in slots 1 and 2.

• Shelf Manager Cards (ShMC) are always in slot 15 (half height).

• The active ShMC in a shelf controls the blades within that shelf.

• The Ethernet Hub is a layer 2 blade. There are two hub cards per shelf; one is located

in slot 07 and the other is located in slot 08. The hubs have associated NASYS RTM

in the rear of the chassis.• The LCP internal subnet can only be accessed by the ShMC, Ethernet Hub, and

Processor Blade.

• An external routable subnet is accessible by both LCP and non-LCP elements.

System requirements MGC-8 hardware requirements

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

1-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Shelf layout

Each shelf houses a series of blades that increase numerically from left to right. The left

most slot is assigned number 1 while the right-most slot is assigned number 15. The shelf

itself is numbered from bottom to top. The bottom shelf in cabinet 0 is shelf 0. The ShMC

in a shelf and the AMC blades are numbered numerically from top to bottom.

Figure 1-1, “Factory hardware placement example” (p. 1-3) shows an example of the

factory-installed hardware placement. In a non-co-host (standalone) configuration, the

modules in slots 1 and 2 provide OAM server functionality and slots 3 and 4 are for

ACCM modules. In a co-host configuration, the modules in slots 1 and 2 provide OAM

server functionality and ACCM functions. The co-host configuration does not support the

OAM Server (NBRZAL) in slots 1 and 2.

See Appendix A, “Hardware illustrations” to view graphical depictions of individual

hardware elements.

Figure 1-1 Factory hardware placement example


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



1-3



Passwords

The following table shows the passwords needed to access the various shelf elements and

includes the default passwords provided by the factory.

Table 1-1 Login and passwords

Element Login name Factory

default

password

Default

password

Customer defined

password

ShMC root alatcav2 newsys done by customer

Ethernet Hub root alatcav2 newsys done by customer

Processor Blade root N/A newsys done by customer

SOL connection root N/A newsys done by customer

Communicating with elements

All of the blades within the shelf can communicate using an internal subnet. The internal

subnet is a class B subnet with a value of 169.254.0.0 (255.255.0.0). Although this is the

subnet value that is strongly recommended, sites do have the option of choosing a

different subnet by changing the first two octets. For example: <X.Y>.0.0 where the user

replaces <X.Y>, or 169.254, with different values.

UTC

Universal Time Coordinated (UTC) is equivalent to Greenwich Mean Time (GMT).

Using Linux, you can obtain this time using the -u option. For example: date -u.The url (http://tycho.usno.navy.mil/simpletime.html) displays the current date/time in

UTC. The MGC-8 blades display their time in UTC. The time zone for the blades is

configurable from the Field Install Graphical User Interface (FI GUI).

Hardware requirements (not shipped with the system)

The following hardware, which is not included with the system, is also required for the

installation:

• A laptop computer

•

A straight CAT-5 Ethernet cable to connect the laptop to the module with OAM server A functionality.

• USB to male DB-9 Serial cable with corresponding drivers loaded on the laptop (not

needed if your laptop has a DB-9 port).

• USB bootable device with a minimum of 1GB capacity. The load to be installed will

NOT be placed in the flashdrive.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

http://tycho.usno.navy.mil/simpletime.html

http://tycho.usno.navy.mil/simpletime.html



Note: The mini-USB to female DB-9 cable is provided with the system.

The pc/laptop/LMT Ethernet interface must have a temporary IP and netmask of

169.254.127.2/16 (255.255.0.0) to communicate with the system. In this document, the

PC is referred to as the laptop. The laptop is assumed to be Windows-based

By default, there is no terminal server thereby making it imperative that the system shipswith the appropriate serial cables.

A Hyper-terminal or hyperterm connection is defined as accessing the shelf through its

serial connection. This connection is needed if IP connectivity between the laptop and the

shelf is lost.

Installing the MGC-8 software

MGC-8

The initial software installation on-site of the non-co-host (standalone) MGC-8 is a

three-step process.

1. Downloading software, as described in “LCP software installation” (p. 1-6) and

“ALGPv2 software installation” (p. 1-8)

in this chapter.

Important: Downloading of the software takes several hours and it should be done as

far in advance as possible.

2. Installation of the LCP control platform of modules with OAM server functionality, as

described in Chapter 3, “Prepare for the LCP installation” through Chapter 7, “Load

installation and LCP check”.

3. Installation of the ALGPv2 software.

*For the non-co-host (standalone) MGC-8, adding in a pair of ACCM blades and any

ADCM blades to the MGC-8 chassis, as described in Chapter 10, “Final activities”.

*For the co-host MGC-8, adding in pairs of ADCM blades to the MGC-8 chassis.

4. Procedures necessary to de-grow blades are provided in Chapter 8, “Growth and

de-growth of ALGPv2 blades”.

5. Procedures necessary to upgrade software are provided in Chapter 11, “Upgrade

scenarios and procedures”.

6. Procedures necessary to downgrade or back out software are provided in Chapter 13,

“Rollback and backout procedures”.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



1-5



LCP software installation

The LCP software is the base platform software that you install on the application server

hosts (OAM Server A and OAM Server B). The LCP software provides the infrastructure

for the system to perform ALGPv2 software installation, growth/de-growth, upgrade,

patch, and restore.

The LCP platform and applications interact through an external interface. For example,

LCP provides the tools for the patch of the OS kernel, while the ALGPv2 services

actually invoke them to patch the OS kernel for the ACCM/ADCM blades.

The LCP software is provided on a monolithic zip file that contains all the necessary

software to configure the chassis. The contents of the monolithic zip file consists of other

individual package zip files that pertain to different services. Additionally, it contains the

necessary software installation tools that enable services to be shipped to the service

hosts.

Deft files may also be required. Deft files provide special data evolve tools developed to

evolve the data from one release or load to another. In order to perform arelease-to-release or patch-to-patch software update, the user must obtain the appropriate

version of the evolve tools. The data evolve tools will be contained in the

deft(C)_Rrr.xx.yy_Rrr.xx.yy.zip file.

The deft or deftC file to be used depends upon the upgrade path. If you are upgrading

from

• One major release to the next one, such as:

– R24.26.XX to R25.15.XX, you will need the . deft_R24.26.XX_R25.15.XX,.zip

file.

– R23.29.XX to R25.15.XX, you will need the deftC_R23.29.XX_R25.15.XX,zipfile.

– R24.15.XX to R25.15.XX, you will need the deftC_R24.15.XX_R25.15.XX,zip

file.

– R24.21.XX to R25.15.XX, you will need the deftC_R24.21.XX_R25.15.XX.zip

file.

• A minor release or patch such as:

– R25.15.XX, to R25.15.XX,, you will need the deft_R25.15.XX,_R25.15.XX,.zip

file.

– R25.10.XX, to R25.15.XX,, you will need the deftC_R25.10.XX,_R25.15.XX,.zip

file.


file.

System requirements Installing the MGC-8 software

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015




file.


file.

Refer to the Rapport MGC-8 ATCA System Software Release Notes 255-400-006, Chapter

3 Test Results, for the LCP version tested with ALGPV2.ATCA.9.X.X.X.

The LCP and deft(C) software can be downloaded from the Alcatel-Lucent OLCS LED

site.

Attention: Software evolution key for upgrading

A hot upgrade evolution key is required for an LCP platform software upgrade. This

key is not required for the initial field installation of LCP software. The evolution key

is also not needed when the first six digits of the LCP platform software version do

not change. For example an upgrade from 24.15.31.05 to 24.15.31.06 will not require

an evolution key.

Evolution key information is available in QDI document 52114. You must know the

LCP version from which you are upgrading and the version to which you are

upgrading to determine the required key.

Perform the following to obtain the LCP software.

1. Go to https://support.alcatel-lucent.com/portal/olcsHome.do.

2. Log in with your User Name and Password.

3. On the left side of the screen, select Technical Content for

4. Select the number 5.

5. Search for and select the MGC-8 (Media Gateway Controller)

6. Select the Downloads: Electronic Delivery and wait for the next menu to load fully

7. Select LCP from “Please navigate through the hierarchy to download”

8. Select the appropriate LCP version for this release from "Please select a Downloadable".

Refer to the MGC-8 system release notes in 255-400-006 for the LCP release number.

9. Click Next.

10. Find the Boot_Image.LCP.LSS.Rxx.xx.iso file to download the same (where Rxx is the LCP

version for this release).

Download both the LCP and the deft(C) software loads. The deft(C) software that you use

on the switch will be determined by your upgrade path.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



1-7



ALGPv2 software installation

ALGPv2 software is an overlay application which you install on top of the base platform

provided by the LCP.

The ALGPv2 software is installed on an ATCA chassis. The ALGP platform is based on

the MGC-8 (and VSG 5025) ported onto an ATCA platform.

Refer to the Rapport MGC-8 ATCA System Software Release Notes, 255-400-006, for

correct version numbers of the MGC-8 files.

The ALGPv2 software can be downloaded from the Alcatel-Lucent OLCS LED site.

Perform the following to obtain the ALGPv2 software downloads.

1. Go to https://support.alcatel-lucent.com/portal/olcsHome.do.

2. Log in with your User Name and Password.

3. On the left side of the screen, select the following:

Technical Content for

4. Select the number 5.

5. Search for and select the following:

MGC-8 (Media Gateway Controller)

+

6. Select the following and wait for the next menu to load fully:

Downloads: Electronic Delivery

7. Select from “Please navigate through the hierarchy to download”

8. Find the ATCA ALGPV2 version of software and download it.

There are two configuration types for ALGPv2 ATCA chassis:

• MGC MGC-8/VSG - This configuration has only ALGPv2 blades in the chassis

(with OAM server functionality, Processor blades, and ShMC blades). It could be a

non-co-host (standalone) configuration or a co-host configuration

• MGC_ICS for ICS + MGC-8/VSG - This configuration supports ALGPv2 blades

with ICS blades.

Be sure to use the ICS LCP software version instead of the MGC-8 LCP software

version, for installation and upgrade.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



The following ALGPv2 installation and upgrade procedures are supported in this release:

• Growth and De-growth of blades — Adding or removing hardware modules to/from

an operational ATCA chassis.

• Upgrade and downgrade — Upgrading or downgrading the ALGPv2 software or a

portion of the ALGPv2 software to a new version.

• Field installation — A new install of an ATCA chassis, which means that no blades

are installed in the chassis. The field installation procedure installs the blade with

OAM server functionality and any other blades needed.

ALGPv2 system software

The ALGPv2 system consists of the installation of ALGPv2 software on ATCA chassis

ALGPv2 that is released as a single zip file, ALGPV2.ATCA.<version>.zip. The zip file

contains other zip files or packages.

ALGPv2 has two packages.

• ALGPV2APPpkg.zip which is used for both ACCM and ADCM

• AMCSS7pkg.zip which is used for the AMC SS7 card

Software installation tools on the blade with OAM server functionality are used to install

the proper application software package on the application service hosts.

ALGPV2 installation files and scripts

The installation zip file contains the packages, files, and scripts needed to complete the

installation. The zip files are shipped to the blade with OAM server functionality first

throug the IP network and then to other blades via the internal IP subnet during

installation.

Currently there is only one package for both ACCM and ADCM zip file(ALGPV2APPpkg.zip). There is a separate package (AMCSS7pkg.zip) which contains

the driver for the AMC SS7 card.

The layout specification of the zip file, ALGPV2.ATCA.xx.yy.zz.zip, is shown below:

• pkgs/ALGPV2APPpkg.zip

– ALGPV2APP.tar.gz (Telica/swCPU/9.X.X.X)

– ALGPV2APPpkg.sh

• pkgs/AMCSS7pkg.zip

– AMCSS7.tar.gz (Telica/swAMCSS7/9.X.X.X)

– AMCSS7pkg.sh

• bin/zip_installer

• bin/patch_setup

• bin/sw_version

• xml/data.xml


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



1-9



The following table briefly describes the packages, files and scripts contained in the

ALGPv2 zip file.

Table 1-2 Installation packages, files, and scripts

Package/file/script name Description

ALGPV2APPpkg.sh A script used to unzip ALGPv2 applications onto

ACCM/ADCM blades.

AMCSS7pkg.sh A script used to install the AMC SS7 package. It unzips

and installs the AMC SS7 card software.

uprev.sh Used to set up and install the ALGPv2 software.

zip_installer Invoked by the LCP script, zipinstall, on the blade with

OAM server functionality to unzip the installation file to

the correct directory on the management interface.

data.xml Feeds the map_loader. LCP needs to collect information

from ALGPv2 so that it knows how to manage the servicetype for ACCM/ADCM.

Note: ALGPPV2APPpkg.sh, AMCss7pkg.sh, and uprev.sh are executed in the

ALGPv2 blades; whereas, zip_install is executed on the blades with OAM server

functionality.

Firmware and software versions

ALGPv2 and LCP

ALGPv2 and LCP platform base software versions must match since some ALGPv2

applications are tightly coupled with services provided by the LCP platform base

software. For example, SS7 card driver is tightly coupled to Linux kernel of LCP

platform base software.

Refer to the Software Release Notes for information on the software version to be

installed and for the location of the software load. The retrieval of the software takes

several hours and should be done as far in advance as possible.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Configuration, administration, and maintenance

Graphical user interfaces

The following graphical user interface programs are used to configure, administer, and

maintain the system:• The Field Install Graphical User Interface (FI GUI) is used to configure the system.

The output is a set of scripts that create the system configuration. The tools referred to

in these scripts are commonly called the System Configuration Data Tools (SCDT).

Throughout this document, these scripts are referred to as the SCDT scripts.

• The Maintenance Interface GUI (MIGUI) is used to administer the system.

System requirements Configuration, administration, and maintenance

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



1-11



System requirements Configuration, administration, and maintenance

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



2 2System configuration

Overview

Purpose

As of the current LCP version for this release, the field install GUI is no longer used

during the guest portion of the field install. The guest configuration worksheet will beused as input to an offline validation tool that is accessed through a web browser. Double

click on the guest worksheet icon to obtain the guest worksheet. This chapter must be

completed in the beginning of Field Install.

Contents

Prerequisite procedure 2-2

...................................................................................................................................................................................................................................



2-1



Prerequisite procedure

Procedure

Complete the following prerequisite procedure.

...................................................................................................................................................................................................

1 Get the worksheet.

If the lab is in work state, you can get one worksheet file named field_config_data.xls

using the command fidata_retrieve (on host MI). The output of fidata_retrieve

is a worksheet that can be saved to the laptop and modified accordingly.

<qd15-s00c02h0:root>/root:

# fidata_retrieve

Retrieving "Basic Information" ...

......

IPv4 Static Routes Information:

IPv6 Static Routes Information

--- complete ---


#1s

field_config_data.xls

Note: The template for the worksheet is also available in QDI 56763, and instructions

on filling out the guest work sheet can be found in guest worksheet in the Usage

Sheet....................................................................................................................................................................................................

2 Check the worksheet.

After the guest worksheet is completed, open a browser and proceed to the url

(http://lssweb2.ih.lucent.com/~umtsbld/cgi-bin/offline_validate.html) to generate an

SCDT metadata zip file. See below:

System configuration Prerequisite procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

http://lssweb2.ih.lucent.com/~umtsbld/cgi-bin/offline_validate.html

http://lssweb2.ih.lucent.com/~umtsbld/cgi-bin/offline_validate.html



...................................................................................................................................................................................................

3 Click browse and select the guest worksheet from the laptop. Enter the release that needs

to be installed. Enter the load to be installed. Click Start Validation Process. If there are

no errors, an offline validation zip file will be created. In case of an error(s), modify the

worksheet and run the offline validation tool again.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-3



Once the offline validate has succeeded, save the zip file on your laptop. You can name

the zip file as you like, but you must maintain the “_olv.zip”.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



3 3Prepare for the LCP

installation

Overview

Purpose

This chapter describes the mandatory prerequisite procedures that must be completed

prior to installing the LCP software.

Contents

Mandatory prerequisite procedures 3-1

Prepare the flashdrive 3-3

Gather the system configuration information 3-6

Complete the configuration worksheets 3-7

Configure the laptop 3-11

Power on the shelf 3-15

What’s next? 3-15

Mandatory prerequisite procedures

Before you begin

Note: All of the procedures in this chapter must be completed prior to proceeding

with the installation.

...................................................................................................................................................................................................................................



3-1



Verify the following:

1. You have obtained the hardware defined in the section "MGC-8 hardware

requirements (not shipped with the system)" in Chapter 1.

2. You have retrieved the software load to be installed in the system and placed it on the

laptop computer. If you have not already downloaded the software, refer to the

Release Notes for the location of the software and instructions for retrieving the load.The load should be located in ALED.

Note: The retrieval of the software takes several hours and should be done as far in

advance as possible.

3. You have compared the md5sum digest to verify the files match what you

downloaded from ALED.

Prepare for the LCP installation Mandatory prerequisite procedures

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Prepare the flashdrive

Hardware requirements

• One USB bootable flashdrive with at least 1GB capacity.

•

Laptop computer running Windows with an available USB port.Important! Be sure to save the contents of your USB drive elsewhere prior to

running this procedure. This procedure will erase the current contents of your USB

drive.

Procedure

...................................................................................................................................................................................................

1 In your web browser type the url (https://support.alcatel-lucent.com/portal/olcsHome.do).

...................................................................................................................................................................................................

2 Log in and on the left, under the Technical Content for tab, select the MGC-8 (Media

Gateway Controller) product.

...................................................................................................................................................................................................

3 With the MGC-8 (Media Gateway Controller) selected, click the link Downloads:

Electronic Delivery under this tab.

...................................................................................................................................................................................................

4 From the Please navigate through the hierarchy to download drop-down, select LCP.

...................................................................................................................................................................................................

5 From the Please select a Downloadable drop-down, select the LCP version for this

release.

Note: Refer to the MGC-8 system release notes 255–400–006) for the LCP release

number.

...................................................................................................................................................................................................

6 Click Next.

...................................................................................................................................................................................................

7 Find the Boot_Image.LCP.LSS.Rxx.xx.xx.xx.iso to download (where Rxx is the LCP

version for this release).

...................................................................................................................................................................................................

8 Save the file to a directory on your PC.

Prepare for the LCP installation Prepare the flashdrive

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-3

https://support.alcatel-lucent.com/portal/olcsHome.do

https://support.alcatel-lucent.com/portal/olcsHome.do



...................................................................................................................................................................................................

9 If you already have the USB image tool on your PC, then proceed to Step 13, else

continue.

...................................................................................................................................................................................................

10 Go to (http://ihgpweb.ih.lucent.com/~umtsbld/cgi-bin/)....................................................................................................................................................................................................

11 Double-click on the usbit.zip link. The File Download screen appears.

...................................................................................................................................................................................................

12 Click Save and save the file to the desktop.

...................................................................................................................................................................................................

13 Double-click on usbit.zip and extract its contents to a folder.

...................................................................................................................................................................................................

14 Double-click on the USB Image Tool.exe file and click Run.

...................................................................................................................................................................................................

15 Insert the USB flash drive into the USB port on your laptop.

...................................................................................................................................................................................................

16 Click on the drop down menu in the upper left corner and select Device Mode. The screen

shows the USB drive that you inserted.

...................................................................................................................................................................................................

17 Click on the device and the Restore button should now be accessible.

...................................................................................................................................................................................................

18 Click Restore and select the Boot_Image.LCP.LSS.Rxx.xx.xx.xx.iso (where Rxx is the

LCP version for this release).

Note: This step erases the previous contents of your USB drive. Ensure to save the

contents before proceeding! If asked to restore contents, answer Yes.

...................................................................................................................................................................................................

19 Use the Safely Remove Hardware tool to stop the USB flash drive.

...................................................................................................................................................................................................

20 Remove and re-insert the USB drive.

...................................................................................................................................................................................................

21 To verify the procedure:

a. Click Start > Settings > Control Panel.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

http://ihgpweb.ih.lucent.com/~umtsbld/cgi-bin/





b. Right-click on Administrative Tools and click Open.

c. Right-click on Computer Management and click Open.

d. Click on the ‘+’ to the left of Storage (maybe expanded already).

e. Double-click on Disk Management.

f. Look at the partitions of the USB drive. They should look similar to the following

display:

g. Verify that there is one healthy section (here the size is the same as

Boot_Image.LCP.LSS.Rxx.xx.xx.xx.iso'size ).

...................................................................................................................................................................................................

22 Use the Safely Remove Hardware tool to stop the USB flashdrive before removing it.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-5



Note: To re-format the USB drive back to its original windows environment after the

installation is complete, refer to “Reformatting the usb drive back to “windows XP

environment”” (p. 10-4) in Chapter 10, “Final activities”.

Gather the system configuration information

Record the information

Work with the customer to obtain and assemble the following information based on the

customer's specifications:

• A list of services to be configured in their respective slot location.

• The number of external subnets to be used, along with their subnet value and range.

For external subnets, the size depends on the elements in the subnet.• The IP address(es) of the customer's device(s) and the IP value(s) to be assigned to the

Alcatel-Lucent switch that the customer’s device(s) will recognize.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Complete the configuration worksheets

Introduction

The configuration worksheets are located in Appendix B. Note that the instructions

provided in this section are specific to installing the LCP software onto the MGC-8system.

Important! You are not allowed to have two gateways on the same subnet in LCP

version R27 and higher. This was allowed in earlier versions, but after an upgrade to

9.X.X. and greater, it is no longer allowed. If you want to use different gateways, use

different subnets.

Complete worksheet 1

...................................................................................................................................................................................................

1 Print out and complete Worksheet 1, which is located in Appendix B, in the following

steps.

...................................................................................................................................................................................................

2 Ensure that the blades with OAM server functionality are located in shelf number 0, slot

numbers 1 and 2.

The non-co-host (standalone) MGC-8 uses MI and CNFG services.

The co-host MGC-8 uses MI, CNFG and ACCM services

...................................................................................................................................................................................................

3 Fill in the default IPv4 Gateway (Subnet #) field as 1. The MGC-8 uses one externalsubnet for management of the blades with OAM server functionality.

Note:This gateway is for the OAM blades. The MGC-8 uses an ACCM/ADCM default

gateway configured using the TL1 command ED-ATCA-CHASSIS. Refer to the Rapport

MGC-8 ATCA TL1 Commands Reference Guide, 255-400-002 for more information.

...................................................................................................................................................................................................

4 Select the disk partition for the diskfull hosts from the following choices. Choose the

300G disk.

• lcp_base_147G for the 147G disks.

• lcp_base_300G for the 300G disks• storage_90_147G for the 147G disks that certain applications have requested.

• storage_175_300G for the 300G disks that certain applications have requested

Prepare for the LCP installation Complete the configuration worksheets

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-7

E N D O F S T E P S...................................................................................................................................................................................................



Complete worksheet 2

...................................................................................................................................................................................................

1 Print out and complete Worksheet 2, located in Appendix B.

...................................................................................................................................................................................................

2 Determine and fill in a name for the System Name. The System Name is a string with amaximum length of 40 characters consisting of alphanumeric characters, dashes,

underscores, and spaces; for example, Westford_ATCA_02.

...................................................................................................................................................................................................

3 Select 5060_MGC for Application(s).

...................................................................................................................................................................................................

4 Determine and fill in the System Prefix. The prefix name is a string having the value of up

to five (5) lowercase alphanumerical characters with the first character being an

alphabetical character; for example, atca2.

...................................................................................................................................................................................................

5 Fill in the Internal Subnet as the default value of 169.254.0.0.

...................................................................................................................................................................................................

6 Determine the Time Zone for the location where the switch will be physically located. If

the system is being staged at a location other than the actual customer location, remember

to use the time zone that corresponds to the customer location. UTC is recommended for

the time zone.

...................................................................................................................................................................................................

7 Define one Externally Routable IPv4 Subnet by filling in the subnet name, subnet, and

netmask for one Externally Routable Subnet according to the following guidelines:

• The subnet name is a string of up to 16 alphanumerical characters, underscores,

dashes and spaces with the first character being an alphanumerical character.

• Determine the value for the gateway and the ports to be used in the hub for each

external subnet. The gateway refers to the destination IP address on the customer

equipment.

Place each external subnet on separate pairs of transport interfaces or place all the

external subnets on one pair of transport interfaces, or something in between. Fields

are provided for four external subnets.

Example:

mgmt, 152.148.184.0, 255,255,252,0, 1, Both Transport Rear

Interface -0.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Note: See Worksheet 2 in Appendix B for a listing of the valid ports. The first three

interfaces (indicated below) are reserved ports. Consequently, they are not listed in

the configuration worksheet.

• Front Interface “2”: reserved for the APDU

• Front Interface “3”: reserved for port mirroring

• Rear Interface “7”: reserved for port mirroring

• Rear Interface “12”: reserved in ROETHAA rtm for port mirroring

...................................................................................................................................................................................................

8 Note: The Hub SOL and SSH IP addresses cannot be in the internal subnet; but they

do not have to be in different external subnets. One recommendation is to have a

“secured” OAM subnet for them.

Both SOL and SSH IP configuration is optional.

Determine the shelf 0 hub 7 SOL IP address.

...................................................................................................................................................................................................

9 Determine the shelf 0 hub 7 SSH IP address, netmask, and gateway.

...................................................................................................................................................................................................

10 Determine the shelf 0 hub 8 SOL IP address.

...................................................................................................................................................................................................

11 Determine the shelf 0 hub 8 SSH IP address, netmask, and gateway.

...................................................................................................................................................................................................

12 Determine and fill in the NTP Server IPs....................................................................................................................................................................................................

13 Leave the Solution Domain blank.

...................................................................................................................................................................................................

14 Leave the Local Zone/LCP Domain blank.

...................................................................................................................................................................................................

15 Leave the ENUM Domain blank.

...................................................................................................................................................................................................

16 Leave the IPv4 address of the external DNS servers blank.

...................................................................................................................................................................................................

17 Leave the IPv4 IP address of the external ENUM server blank.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-9



...................................................................................................................................................................................................

18 Leave the IPv4 static routes field (needed for different services) and the external subnet

(to be used as the gateway) blank regardless of co-host or non-co-host.

Complete worksheet 3A

...................................................................................................................................................................................................

1 Print out and complete Worksheet 3A, which is located in Appendix B.

...................................................................................................................................................................................................

2 Use the default NI type for both CNFG and MI. For each network interface (NI) type, fill

in the external subnet number. Whenever using default or NotConfigured value, leave the

IP Address column blank.

...................................................................................................................................................................................................

3 Provide the appropriate IP address . Use the external management IPv4 subnet (Subnet

#1) for CNFG and MI.

* Fill in the floating IP for CNFG.

* Fill in the floating IP and each member’s fixed IP for MI.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................

E N D O F S T E P S...................................................................................................................................................................................................



Configure the laptop

Before you begin

You will complete the following sections to configure the laptop computer to be used for

the software installation procedure.Laptop requirements

The laptop computer must meet the following requirements:

• The laptop must be electrically plugged into a wall socket (AC power supply). It

cannot run on battery power alone.

• The laptop must have services that enable it to ping and ftp to external entities.

• The pc/laptop/LMT Ethernet interface must have a temporary IP and netmask of

169.254.127.2/16 (255.255.0.0) for communication to the system.

• The user must have “Administrator” privilege access to the laptop.

Cabling requirements

The system includes a mini-USB to female db-9 cable. Verify that you have also obtained

the following two temporary cables (defined as requirements in Chapter 1):

• Male db-9 to USB serial cable (this cable is not needed if your laptop already has a

db-9 port).

• Cat-5 ethernet cable

The installation procedure indicates where and when the temporary cables are used and

how to connect them.

Cable the laptop

...................................................................................................................................................................................................

1 Load the appropriate drivers for the USB to male db-9 cable to the laptop and cable the

system.

...................................................................................................................................................................................................

2 Connect the USB-to-male db-9 cable to the mini-USB-to-female db-9 cable. The USB

end connects to the laptop, while the mini-USB end connects to the faceplate.

...................................................................................................................................................................................................

3 Note: It is advisable to label the cables and note the cable-port information beforedisconnecting the cables.

Unplug all of the 1Gb ethernet cables that are connected to the blades.

There may be connections to RTM ports and to front face-plate connections.

Prepare for the LCP installation Configure the laptop

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-11



...................................................................................................................................................................................................

4 The inter-shelf cables (where applicable) are 10Gb and need to remain connected. The

connectors, UPL0 and UPL1, are on Hub front panel module.

Determine the serial port configured on the laptop

Loading the USB-to-male db-9 cable drivers on the laptop automatically configures a

port. Complete the following steps to determine which port was configured

...................................................................................................................................................................................................

1 Click on Start > Settings > Control Panel.

...................................................................................................................................................................................................

2 Right click on System and click Open....................................................................................................................................................................................................

3 Select the Hardware tab from the System Properties window and click on Device

Manager.

...................................................................................................................................................................................................

4 Click on the “+” to the left of Ports (COM & LPT) in the Device Manager window.

...................................................................................................................................................................................................

5 Plug in the USB-to-male db-9 cable, or plug in the mini-USB-to-female db-9 cable.

An entry appears with the words USB-to-Serial, and a port associated with it. For example, COM4. If connecting the mini-USB-to-female db-9 cable, it will be COM1.

Make a note of the port used as it will be used in the following subsection.

Configuring the laptop for a serial connection running Windows XP

The following steps provide an example of how to configure the laptop for a serial

connection running Windows XP.

...................................................................................................................................................................................................

1 Click Start > Programs > Accessories > Communications > HyperTerminal.

...................................................................................................................................................................................................

2 Type in any name and click on OK from the Connection Description window.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................

E N D O F S T E P S...................................................................................................................................................................................................



...................................................................................................................................................................................................

3 Select (from the dropdown list) the serial com port that you determined in the previous

section (COM1 if the laptop has a db-9 port) from the Connect window.

...................................................................................................................................................................................................

4 Click on OK....................................................................................................................................................................................................

5 Complete the following fields as indicated below:

a. Bits per second: 115200

b. Data bits: 8

c. Parity: None

d. Stop bits: 1

e. Flow control: None

...................................................................................................................................................................................................

6 Click on OK .

...................................................................................................................................................................................................

7 Save the file...from File, select Save As ...

...................................................................................................................................................................................................

8 Enter a file name and click on Save.

Configuring the laptop for an ethernet connection

...................................................................................................................................................................................................

1 Configure the laptop with the IP address as indicated, regardless of the internal network to

be used in the system.

Note: Configure the laptop IP address using the following subsection that matches

your PC’s operating system (Windows 2000 or Windows XP).

Configuring the laptop IP address for systems running Windows 2000

...................................................................................................................................................................................................

1 Click Start > Settings > Network and Dial-up Connections.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-13

E N D O F S T E P S...................................................................................................................................................................................................

E N D O F S T E P S...................................................................................................................................................................................................



...................................................................................................................................................................................................

2 Right click on Local Area Connection and then click on Properties.

...................................................................................................................................................................................................

3 Click on Internet Protocol (TCP/IP) and then click on Properties.

...................................................................................................................................................................................................

4 Click on Use the following IP address button.

...................................................................................................................................................................................................


IP address: 169.254.127.2

Subnet mask: 255.255.0.0

Default Gateway: leave blank

...................................................................................................................................................................................................

6 Click on OK to accept the field entries.

...................................................................................................................................................................................................

7 Click on OK from the Internet Protocol Properties window.

Configuring the laptop IP address for systems running Windows XP

...................................................................................................................................................................................................

1 Click Start > Settings > Network Connections.

...................................................................................................................................................................................................

2 On the Network Connections window, right click on Local Area Connection and then

click on Properties.

...................................................................................................................................................................................................

3 On the Local Area Connection Properties window, click on Internet Protocol (TCP/IP)

and then click on Properties.

...................................................................................................................................................................................................

4 On the Internet Protocol (TCP/IP) Properties window, click on Use the following IP

address button.

...................................................................................................................................................................................................



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



IP address: 169.254.127.2

Subnet mask: 255.255.0.0

Default Gateway: leave blank

...................................................................................................................................................................................................

6 Click on OK to accept the field entries.

...................................................................................................................................................................................................

7 On the Internet Protocol Properties window, click on OK .

Power on the shelf

Begin the installation

Verify that all of the necessary blades are installed in the shelf and that the shelf is

powered on. You are now ready to begin the installation process, proceed to Chapter 4,

“Configure ShMCs and jumpstart the blade with OAM server A functionality”to continue.

Note: Do not connect the system to the customer network until directed to do so in

Chapter 10, “Final activities”.

What’s next?

Proceed to the next chapter

Now that the preparation procedures are complete, proceed to Chapter 4, “Configure

ShMCs and jumpstart the blade with OAM server A functionality” for instructions on

how to configure the Shelf Manager Cards (ShMCs) and jumpstart OAM Server A.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



3-15

E N D O F S T E P S...................................................................................................................................................................................................



Prepare for the LCP installation What’s next?

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



4 4Configure ShMCs and

jumpstart the blade with

OAM server A functionality

Overview

Purpose

This chapter provides instructions for configuring the Shelf Manager Cards (ShMCs) and

for jumpstarting the blade with OAM server A functionality.

Contents

Introduction 4-1

Field re-installed software 4-3

ShMC IP configuration 4-4

Hub IP configuration procedure 4-5

Jumpstart the blade with OAM server A functionality 4-6

What’s next? 4-10

Introduction

Initial configuration

The procedures in this chapter take approximately 10-20 minutes to execute.

Important! DO NOT CONNECT the system to the customer network until directed

to do so in Chapter 10, “Final activities”.

Note: Once you initiate the procedures in this chapter, you must also complete the

procedures in Chapter 5, “Load transfer and pre-installation” prior to reaching a safe

break point in the installation process.

...................................................................................................................................................................................................................................



4-1



Before you begin

Before you begin, isolate the system. Label and disconnect any ethernet cables that are

connected to the system.

You will need the following to complete these procedures:

•

The USB flash drive.• The load to be installed (downloaded as a zip file on the laptop).

• Access to the internal subnet that will be configured for this system. The default is

169.254.0.0/16 (255.255.0.0).

• Software Release Notes associated with the load. Ensure that the application specific

documents are available for reference.

Configure ShMCs and jumpstart the blade with OAM server A functionality

Introduction

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Field re-installed software

Important! This section is for a field re-install only. If this is the first field installation

performed on the switch, skip this section and proceed directly to the “ShMC IP

configuration” (p. 4-4).

Procedure

Complete the following steps to re-install the LCP software:

...................................................................................................................................................................................................

1 Verify that the shelf 0 top ShMC is active. Log into the ShMC and run the following

command.

clia shmstatus

...................................................................................................................................................................................................

2 Insert the serial cable between the laptop and the CP port of the blade with OAM server Afunctionality (shelf 0, slot 1 blade).

...................................................................................................................................................................................................

3 Login as root.

...................................................................................................................................................................................................

4 Set up the system for re-Field Install (you can ignore errors if there are any) as follows:

/opt/LSS/share/basecfg/factory/bin/prepReFieldInstall

...................................................................................................................................................................................................

5 If there are no issues, the following message displays:

prepReFieldInstall executed successfully


Field re-installed software

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



4-3

E N D O F S T E P S...................................................................................................................................................................................................



ShMC IP configuration

Procedure

Complete the following steps to configure the IP address for the ShMC

...................................................................................................................................................................................................

1 Connect the serial cable on the shelf (top ShMC) to the RS port.

...................................................................................................................................................................................................

2 Log into the shelf (top ShMC) as root.

...................................................................................................................................................................................................

3 Verify that the ShMC you logged into is active.

clia shmstatus

If the top ShMC is not active, run the following command.

clia switchover

...................................................................................................................................................................................................

4 Is this a reinstallation without a subnet change?

IF . . . THEN . . .

YES STOP. You have completed this procedure.

NO Continue to the next step.

...................................................................................................................................................................................................

5 Manually configure the shelf (top ShMC) IP address as follows:

a. If you are using the default internal subnet of 169.254.0.0, type the following:

ifconfig eth0:8 169.254.32.241 netmask 255.255.240.0

b. If you are NOT using the default internal subnet, replace <X.Y> in the following

command with your choice:

ifconfig eth0:8 <X.Y>.32.241 netmask 255.255.240.0

...................................................................................................................................................................................................

6 Verify that the procedure completed successfully as follows:

a. If you used the default internal subnet of 169.254.0.0, type the following:

ping -c 2 169.254.32.241

b. If you did not use the default internal subnet, type the following:



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



ping -c 2 <X.Y>.32.241

Hub IP configuration procedure

Automatic retrieval

Hubs automatically retrieve their IP addresses from the blade with OAM server A

functionality.



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



4-5

E N D O F S T E P S...................................................................................................................................................................................................



Jumpstart the blade with OAM server A functionality

Note: Complete the following steps to jumpstart the blade with OAM server A

functionality.

Prepare the shelf, first blade (slot 1) for jumpstart...................................................................................................................................................................................................

1 Verify that you are still connected to the ShMC serial window.

...................................................................................................................................................................................................

2 Verify that the shelf (slot 1 blade) is a diskfull blade by checking for the following:

• It has a FM016JB or a FM016JP label.

• It has one disk.

...................................................................................................................................................................................................

3 Insert the USB flash drive into the USB port of the blade with OAM server Afunctionality (slot 1 blade).

...................................................................................................................................................................................................

4 From the ShMC window, reboot the slot 1 blade so that it recognizes the USB flash drive

as follows: .

clia boardreset 1

...................................................................................................................................................................................................

5 Move the serial cable from the ShMC to the CP port of the blade with OAM server A

functionality.

Procedure to jumpstart

...................................................................................................................................................................................................

1 Verify that the serial cable is connected to blade 1.

...................................................................................................................................................................................................

2 Determine the current time in UTC as follows: Goto https://tycho.usno.navy.mil/simpletime.html

...................................................................................................................................................................................................

3 Once the blade has been rebooted (Step 4 of the previous procedure), login as root (no

password needed).

The following prompt appears:



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



<fctry-s15c01h0:JUMPSTART ENVIRONMENT (USB)>/root:

Set the date and time in UTC as shown in the following example:

date -s “Fri, Jan 8 2010 12:08:08 UTC”

(replace the data within quotes with the actual date and time where the system will be

physically located).

...................................................................................................................................................................................................

4 Jumpstart as follows:

a. If you used the default internal subnet of 169.254.0.0, type the following:

jumpstart

b. If you did NOT use the default internal subnet, replace <X.Y> with your choice and

type the following:

jumpstart --network <X.Y>.0.0

Note: Do not select accm or adcm service although they are shown in the selection

list. You will go to the growth procedures later in Chapter 9, “Provisioning of

ALGPv2 blades”.

Figure 4-1 Response example

<fctry-s15c01h0:JUMPSTART ENVIRONMENT (USB)>/root:

> jumpstart

Starting jumpstart of fctry-s15c01h0 at Fri Jan 4 08:39:44UTC 2013

Version=5.0

Hardware Clock updated to Fri Jan 4 08:39:46 UTC 2013.

Choose the applications for this office:

1) 0000 N4E

2) Standalone MGC-8/VSG-5025

3) 5060 IP Call Server

4) 5420 Converged Telephony Server

5) 5420 Service Continuity Gateway

6) 5450 IP Resource Controller

7) 5450 IP Session Controller

8) 9290 MMSI

9) 9380 WCS

10) 9471 MME

11) 9471 SGSN



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



4-7



98) Start over

99) Finished selecting values

Enter the number to select a value ('*' denotes selected entries): 2

Choose the applications for this office:

1) 0000 N4E

*2) Standalone MGC-8/VSG-5025

3) 5060 IP Call Server

4) 5420 Converged Telephony Server

5) 5420 Service Continuity Gateway

6) 5450 IP Resource Controller

7) 5450 IP Session Controller

8) 9290 MMSI

9) 9380 WCS

10) 9471 MME

11) 9471 SGSN

98) Start over



Note: For services of the co-host MGC-8, you will select accm, cnfg and mi.

For services of the stand alone MGC-8, you will select cnfg and mi.

Choose the services for this slot:

1) accm

2) adcm3) cnfg

4) gjs

5) gos

6) mi

98) Start over




*1) accm2) adcm

3) cnfg

4) gjs

5) gos

6) mi

98) Start over



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015






*1) accm

2) adcm*3) cnfg

4) gjs

5) gos

6) mi

98) Start over




*1) accm

2) adcm

*3) cnfg

4) gjs

5) gos

*6) mi

98) Start over



Choose one disk scheme

1) LCP_base_147G - Default LCP Scheme for 147GB disk


3) indapp_20_300G - 20GB indapp scheme for 300GB disk

4) storage_175_300G - 175GB storage scheme for 300GB disk

98) Start over



Choose one disk scheme


2) storage_175_300G - 175GB storage scheme for 300GB disk

98) Start over




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



4-9




Starting disk preparation using disk scheme 'LCP_base_300G'

Started...

...................................................................................................................................................................................................

5 Once the blade is successfully jumpstarted, login as root/newsys. The following prompt

displays.

<fctry-s15c01h0:root>/root:

What’s next?

Load transfer

Now that you have completed all of the procedures in this chapter, proceed to Chapter 5,

“Load transfer and pre-installation” and complete the load transfer and pre-installation

procedure prior to reaching a safe break point in the process.



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



5 5Load transfer and

pre-installation

Overview

Purpose

This chapter provides instructions for completing the load transfer and pre-installation

procedure.

Contents

Introduction 5-1

Load transfer and field installation procedure 5-2

Introduction

Complete all prior procedures

Prior to executing the procedures in this chapter, make sure that you have read and

completed all of the necessary procedures in the chapters leading up to this one. It is

important that the installation process is completed in the proper sequence.

The following procedure takes approximately 10-20 minutes to execute.

...................................................................................................................................................................................................................................



5-1



Load transfer and field installation procedure

Procedure

Note: Slot 1 and 2 blades are configured as OAM servers.

Complete the following steps to execute the load transfer and pre-installation procedure:

...................................................................................................................................................................................................

1 Verify that the load zip file is on the laptop.

...................................................................................................................................................................................................

2 Connect an Ethernet cable to the laptop and to port ge0 on the blade in slot 1 with OAM

server A functionality (FM016JB/FM016JP). If OAM server was an NBRZAL, the port

should be ge4. At this point, you should still be connected to the OAM Server A serial

window.

...................................................................................................................................................................................................

3 From OAM Server A, verify IP connectivity to the laptop as follows:

ping -c2 169.254.127.1

...................................................................................................................................................................................................

4 From the laptop, FTP the zip file into the system.

As root, FTP the zip file to /data0 on the OAM Server A.

ftp -i 169.254.127.1

root

newsys

cd /data0

bin

hash

mput <ATCA.LCPXX.XX.XX.XX.zip>

mput <ALGPV2.ATCA.9.X.X.X.X.X.X.zip>

mput <XX_olv.zip>

bye...................................................................................................................................................................................................

5 You will now return to the OAM Server A serial window.

...................................................................................................................................................................................................

6 Execute the following script, which is found in the /usb directory:

Load transfer and pre-installation Load transfer and field installation procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



/usb/lcp_starter

The following message will appear:

<fctry-s15c01h0:root>/root:

> /usb/lcp_starter

***** Running lcp_starter at *****Mon Jan 14 14:22:584 UTC 2013

...

lcp_starter executed successfully.

Mon Jan 14 14:22:58 UTC 2013

...................................................................................................................................................................................................

7 Connect the serial cable on the shelf (top ShMC) to the RS port. Log into the shelf (top

ShMC) as root.

Note: If the top shmc status is not active, prepOSA will fail. You must check statusand switch over if required

...................................................................................................................................................................................................

8 Verify that the ShMC you logged into is active.

clia shmstatus

If the top ShMC is not active, run the following command.

clia switchover

...................................................................................................................................................................................................

9 Ensure to remove the USB flash driver from the blade with OAM server A functionality

(slot 1 blade) prior to performing the next step.

...................................................................................................................................................................................................

10 Prepare OAM Server A and begin the final field install script. You are prompted to enter

the ShMC password and Hub password. See Table 1–1, Login and Passwords to obtain

the appropriate password.

Note: If an error occurs during field install, you can use command

/data0/fi --action resume to rectify the error.

/data0/fi -n 1

The following is an output example:

<fctry-s15c01h0:root>/data0

>/data0/fi -n 1

***Executing: cat /usb/usb_version

cat /usb/usb_version

CP8.0 -- 03 Jan, 2013.

***Executing: find_shmc_ip()


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



5-3



***Executing: redefine_shmc_ip()

...

...................................................................................................................................................................................................

11 Enter the SHMC password (it will assume the same for all SHMC).

...................................................................................................................................................................................................

12 Re-enter the SHMC password (it will assume the same for all SHMC).

Example:

14-11-04 10:55:05 :[fi_enable]: Command executed successfully!

***Executing: do_cleanup(install_lib.local_boot_host_list)

ssh qd25-s00c02h0 rm -rf /var/tmp/suinstall





ssh qd25-s00c11h0 rm -rf /var/tmp/suinstallssh qd25-s00c12h0 rm -rf /var/tmp/suinstall


***Executing: update_status("fi_completed")

remote_shell root qd25-s00c02h0 "rm -rf /data0/ATCA*.zip"

remote_shell root qd25-s00c02h0 "rm -rf /data0/*_LCP_*.zip"

fi has been completed successfully!


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



6 6Configure blade with OAM

server A functionality

Overview

Purpose

This chapter provides instructions to configure the blade with OAM server A

functionality.

Contents

Introduction 6-1

Prerequisite procedure 6-2

Verify the system configuration 6-3

What’s next? 6-4

Introduction

Configuration prerequisite

Prior to executing the procedures in this chapter, make sure that you have read and

completed all of the procedures in the chapters leading up to this one. It is important that

the installation process is completed in the proper sequence.

The procedures in this chapter take approximately 30 - 70 minutes to execute.

...................................................................................................................................................................................................................................



6-1



Prerequisite procedure

Procedure

Complete the following prerequisite procedures.

...................................................................................................................................................................................................

1 Verify that you are still connected to the serial window of the blade with OAM server A

functionality.

...................................................................................................................................................................................................

2 Refer to Table 1-1, “Login and passwords” (p. 1-4) to obtain the password for the blade

(OAMSA).

Configure blade with OAM server A functionality Prerequisite procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................





hubconf_adm --action show_ssh_address4

...................................................................................................................................................................................................

2 If the information retrieved does not match what you have defined in the Configuration

Worksheets, DO NOT continue with the installation until the information is corrected.

Please contact the next level of technical support for assistance.

What’s next?

Load installation and LCP check

Once you have confirmed the configuration of the blade with OAM server A functionality

as described in this chapter, you have reached a safe place in the installation to take a break if desired. When you are ready to proceed, continue to the next chapter.

Configure blade with OAM server A functionality Verify the system configuration

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



7 7Load installation and LCP

check

Overview

Purpose

This chapter provides the procedures to follow for the load installation and LCP check.

Contents

Introduction 7-1

Load installation procedure 7-2

Changing hub and ShMC login and password 7-3

LCP check procedure 7-4

IntroductionLCP installation sequence

Prior to executing the procedures in this chapter, be sure that you have read and

completed all of the procedures defined in the chapters leading up to this one. For a

successful installation, it is important that the LCP installation process is completed in the

proper sequence.

...................................................................................................................................................................................................................................



7-1



Load installation procedure

Prerequisites

Verify the following.

1. Blade with OAM server A functionality has been successfully jumpstarted. (Note:OAM-B jumpstart is merged to aInstall.)

2. Verify that all blades are powered on.

The procedure in this section takes approximately 60 - 180 minutes to execute.

Procedure

Complete the following procedure for the load installation.

...................................................................................................................................................................................................

1 Move the serial cable back to the CP port of the blade with OAM server A functionality.

...................................................................................................................................................................................................

2 If the Hub SOL capabilities are going to be utilized, enter the following command,

otherwise continue to the next step.

Note: The following is one command. There is no space before hubUPG.log.

hub_adm -a config_all --enable_sol 2>&1|tee -a /data0/FLD/

hubUPG.log

...................................................................................................................................................................................................

3 Retrieve the software version of the hub cards as follows.

hub_adm -a check_all

...................................................................................................................................................................................................

4 Refer to the Software Release Notes to verify that the software version matches.

For software versions refer to the Rapport MGC-8 ATCA System Software Release Notes,

255-400-006

• Chapter 1 Release components for the MGC-8 ALGPV2.ATCA.9.X.X.X version

• Chapter 4 Test results, for the LCP version tested with ALGPV2.ATCA.9.X.X.X

...................................................................................................................................................................................................

5 Plug the cable into the suitable port on HUB. Field Install is done now.

Load installation and LCP check Load installation procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Changing hub and ShMC login and password

Procedure

Complete the following procedure to change the factory-defined hub login and password

and the ShMC login and password from root/alatcav2 to the following new login and password: root/newsys.

...................................................................................................................................................................................................

1 Log into the shelf slot 7 hub (ssh <x.y>.0.112 where x.y=169.254 by default),

change the login and password to root/newsys, and exit.

passwd

...................................................................................................................................................................................................

2 Log into the shelf slot 8 hub (ssh <x.y>.0.128 where x.y=169.254 by default),

change the login and password to root/newsys, and exit.

passwd

...................................................................................................................................................................................................

3 Verify that you are now back on blade 1.

...................................................................................................................................................................................................

4 Log into the first shelf top ShMC (telnet <x.y>.32.241 where x.y=169.254 if

using the default), change the login and password to root/newsys, and exit.

passwd

...................................................................................................................................................................................................

5 Log into the first shelf bottom ShMC (telnet <x.y>.32.242 where x.y=169.254 if

using the default), change the login and password to root/newsys, and exit.

passwd

...................................................................................................................................................................................................

6 Verify that you are now back on blade 1.

Load installation and LCP check Changing hub and ShMC login and password

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



7-3

E N D O F S T E P S...................................................................................................................................................................................................



LCP check procedure

Prerequisites

Verify the that you are still connected to the OAM Server A window

Important! Please see technical support if any of the commands executed in thissection do not show the expected result.

Procedure

Complete the following steps for the LCP check. This procedure takes approximately

10-15 minutes to execute.

...................................................................................................................................................................................................

1 Verify that RCC and VM are up and running as follows.

rcc_srv_state --action display --set ALL

Output should look similar to the following example.

> rcc_srv_state --action display --set ALL

Displaying host rcc status for set all hosts

Host Side Degrade Status

cnfg_0 pri No leadactive-none

mi_0 pri No leadactive-none

cnfg_0 alt No active-none

mi_0 alt No active-none

Displaying host vm status for set all hosts

Host Side Degrade Status

cnfg_0 pri No active-none

mi_0 pri No active-none

cnfg_0 alt No standby-hot

mi_0 alt No standby-hot

...................................................................................................................................................................................................

2 Verify the health of the system as follows.

health --test field_install

Everything should be successful. The absence of failures indicates a healthy system.

Output should look similar to the following example.

> health --test field_install

Running all applicable tests ....

SKIPPING CPM TEST BECAUSE OF 'field_install' TEST SPECIFIED ...

SKIPPING CONNECTIVITY TEST BECAUSE OF 'field_install' TEST SPECIFIED...

SKIPPING REM STATE TEST BECAUSE OF 'field_install' TEST SPECIFIED...

Load installation and LCP check LCP check procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015





Load installation and LCP check LCP check procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



8 8Growth and de-growth of

ALGPv2 blades

Overview

Purpose

This chapter provides instructions for growing and degrowing ALGPv2 (AxCM) blades

into the chassis. For the co-host MGC-8, only ADCM blades need to be grown anddegrown.

Contents

Introduction 8-2

Rules and restrictions 8-2

Grow in the ACCM Blades for the non-cohost (standalone) MGC-8 8-4

Grow in the ADCM blades 8-13

Configure and enable CPM 8-20Backing up blade configuration 8-21

De-growth procedure 8-23

...................................................................................................................................................................................................................................



8-1





• Only one ACCM pair can be grown in on a MGC-8 ATCA chassis.

• For the non-cohost (standalone) MGC-8, the ACCM pair can exist in the following

range of slots (3-6) or (9-14).

ADCM growth rules

•

ADCM blades can be grown in duplex pairs (for example (pool size = 2).• An ALGPv2 configuration can have anywhere from zero to four pairs of ADCM

blades for non-cohost (standalone) MGC-8, and from zero to five pairs of ADCM

blades for co-host MGC-8.

• ADCM pairs are grown after ACCMs, so they can be grown into the following range

of slots: 3-6 or 9-14.

• The ADCM service will be the only service configured in the host. For example,

ADCM cannot coexist with any other service.

Growth and de-growth of ALGPv2 blades Rules and restrictions

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-3





...................................................................................................................................................................................................

6 Run the following command to re-generate and install configuration.

svcconf_adm --action generate_host_all && applconf_adm --action

generate_host_all

...................................................................................................................................................................................................

7 Run the following command to re-generate and install configuration.

svcconf_adm --action install_host_all && applconf_adm --action

install_host_all

...................................................................................................................................................................................................

8 Run the following commands to generate SCDT data and sync the configDB after the

application name change.

syncConfigDB -f -l

scdm_adm --action sync_config

...................................................................................................................................................................................................

9 On MI-B (OAM-B, blade 2), run the following commands.

applconf_adm --action generate_host_all

svcconf_adm --action generate_host_all

...................................................................................................................................................................................................

10 Connect the console cable to active OAM.

...................................................................................................................................................................................................

11 Check to see whether the MI is running.

MIvmstate

The MIvmstate result should be “A”\ (active)

If the MI is running, login as lss to stop and restart the MI as follows.

>su -l lss

>stopMI

>startMI

...................................................................................................................................................................................................

12 Enter the following command to exit.

exit

Growth and de-growth of ALGPv2 blades Grow in the ACCM Blades for the non-cohost (standalone)MGC-8

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-5

E N D O F S T E P S...................................................................................................................................................................................................



ACCM growth procedure

Complete the following steps to grow in the host pair of ACCM blades.

...................................................................................................................................................................................................

1 Login to the blade with OAM server A functionality as root.

...................................................................................................................................................................................................

2 Verify that the blade with OAM server A functionality is the active MI as follows.

MIcmd state vc

• state of MI virtual cluster is A - Active

• state of MI host primary virtual machine is A - Active

• state of MI host alternate virtual machine is S - Standby

If the primary VM is standby, call MIcmd switch vc to switchover and then

call MIcmd state vc again to verify.

...................................................................................................................................................................................................

3 Run the following command to save the backup files.

create_ht

...................................................................................................................................................................................................

4 Disable MI switchover by executing the following command.

rcc_adm --action set_inhibit --host $(hostname)

Check the result as follows:

rcc_adm --action disp_inhibit --host $(hostname)...................................................................................................................................................................................................

5 For each of the blades to be grown in, run

isolate_card -s <shelf number> -c <card number>

For example:

>isolate_card -s 0 -c 3

SHELF=0 HUB=169.254.32.112 PORT=17 OID=9

interfaces,ifTable.ifEntry.ifAdminStatus.9 = 0


interfaces.ifTable.ifEntry.ifAdminStatus.9 = 0>isolate_card -s 0 -c 4




interfaces.ifTable.ifEntry.ifAdminStatus.7 = 0


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

6 If the blade to be grown in is not seated in the shelf yet, plug the blades into the shelf

now.

...................................................................................................................................................................................................

7 Run lcp_hostgrow and fill in the card type, service type, redundancy type, shelf and slotnumbers for the blades that are grown in.

lcp_hostgrow

Example:


# lcp_hostgrow

lcp_hostgrow is a tool used to prepare SIM host files

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_host.data

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_srv.data

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_system.data

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_tim.data

for growing one or more service(s) on the existing

card(s). Enter the shelf, card and host number for

the card pair, then enter the service type(s) for

the card pair.

You can use ^C (CTRL + C) at any time to

safely abort this interactive script.

******************************************************************

* Interactive Mode *

******************************************************************

Side A: Enter the SHELF number [ 0 ]: 0


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-7



Side A: Enter the CARD number [ 1-6, 9-14 ]: 5

Side B: Enter the SHELF number [ 0 ]: 0

Side B: Enter the CARD number [ 1-6, 9-14 ]: 6

The allowed service types are as follows:

accm

adcm

gjs

gos

Enter the service(s) (seperated by space) for host growth: accm

Below are the disk scheme and ID for target host:

1) LCP_base_147G,rear:1


3) indapp_20_300G,rear:1

4) storage_175_300G,rear:1

Please input number associated with the valid disk scheme: 2

You are now ready to begin SIM.

The SIM log is /storage/sim/log/lcp_hostgrow/sim.log

You could manually tail sim.log after SIM begins by:

tail -f /storage/sim/log/lcp_hostgrow/sim.log

Type 'y' to begin host growth; type 'n' to exit host growth: y

SIM began successfully.


...................................................................................................................................................................................................

8 Run tail sim.log until the following message is seen in the SIM log.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015




01/01/13 19:48:02 SIM053 PAUSE_REQUEST: (PROCEDURE) [PAUSE

!!! STOP !!!

Both the growth blades need to be booted from network.

Look for memory check on console or on SOL window

and type 'n' during the memory check to force network boot.

If the memory check is not seen, login to the growth

hosts and type 'reboot'. Now during reboot, type 'n'.

After the host comes up and the login prompt is seen,

resume SIM by typing on the MI,

sim --proc lcp_hostgrow --action resume

Type 'y'.

]

13/02/01 19:48:02

13/02/01 19:48:02************************************************************

13/02/01 19:48:02 SIM PROGRESS (lcp_hostgrow apply):

13/02/01 19:48:02************************************************************

13/02/01 19:48:02 53 of 111 sim steps executed (47%)

13/02/01 19:48:02************************************************************

13/02/01 19:48:02

13/02/01 19:48:02 PAUSED: (PROCEDURE) Dispatched commands are

complete.13/02/01 19:48:02

...................................................................................................................................................................................................

9 Log in to the active ShMC as root. Execute the following command to verify that the

ShMC is active and to determine the status of the blades.

clia shmstatus

Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter

Host: "Active"

# clia board 3


Physical Slot # 3

92: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x02

PICMG Version 2.2


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-9



Hot Swap State: M4 (Active), Previous: M3 (Activation InProcess), Last

State Change Cause: Normal State Change (0x0)

92: FRU # 0

Entity: (0xa0, 0x60)



Device ID String: "BMR-H8S MOLENE"

92: FRU # 1

Entity: (0xc0, 0x60)



Device ID String: "RTM"

#...................................................................................................................................................................................................

10 Ensure that the hot swap state of the cards was shown as active in the previous step.

...................................................................................................................................................................................................

11 Was the hot swap state inactive?

IF . . . THEN . . .

YES The blades must be powered on

Execute the following command from the active ShMC.

clia activate board 3


...................................................................................................................................................................................................

12 Note: To complete this step, you must be logged in through the console port, a

terminal server hosting the console port of the blades, or through a SOL console

session.

Log into each blade to be grown. Open the terminal server session and the SOL console

session for the blades. If the blade is at login prompt, log into the blade as root and rebooteach blade from network. This is done during the memory check and pressing n for each

blade.

You may see the output of bios (memory check and so forth) whether in terminal server

session or SOL console session during host boot up.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

13 Wait for the login prompt and log in as root. If the Jumpstart prompt is seen, execute the

following command on OAM to resume SIM.


Output example:

> sim --proc lcp_hostgrow --action resume

***********************************************************************

* Software Installation Manager(SIM) *

***********************************************************************

rules file: /opt/LSS/share/sim/rules/lcp_hostgrow/lcp_hostgrow.xml

data directory: /storage/sim/data/lcp_hostgrow

log file: /storage/sim/log/lcp_hostgrow/sim.log

The current 'apply' of the sim 'lcp_hostgrow' procedure is notfinished.

47 of 99 sim steps completed (47%)

Ready to 'resume' the sim 'lcp_hostgrow' procedure 'apply':

Continue? (y/n) y

Executing ' sim --proc lcp_hostgrow --action resume '...

...................................................................................................................................................................................................

14 To monitor the sim lcp_hostgrow procedure's log file use the following command.:

tail -f /storage/sim/log/lcp_hostgrow/sim.logOutput example:

13/02/01 01:00:39 SIM096 The sim 'update' procedure currently has

no 'rollback' to reset.

13/02/01 01:00:39 SIM096

13/02/01 01:00:39 SIM096_end (SUCCESS)

13/02/01 01:00:39 SIM097_begin [seclogger 'GROWTH COMPLETEDSUCCESSFULLY!']

[pid=8618] (lcp_hostgrow:906)

13/02/01 01:00:39 SIM097_end (SUCCESS)

13/02/01 01:00:39 SIM098 [GROWTH SIM RULES COMPLETED!!!!!] (lcp_hostgrow:909)

13/02/01 01:00:39

13/02/01 01:00:39 COMPLETED SIM PROCEDURE 'lcp_hostgrow apply'

13/02/01 01:00:39 99 of 99 sim steps completed (100%)

...................................................................................................................................................................................................

15 Reboot each ACCM card using the following command on each card:


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-11



reboot.

...................................................................................................................................................................................................

16 Run the following command for the health check.

health --test all

Because CPM was disabled previously, chk_cpm will fail. Ignore chk_connectivity errors.

If cables are not connected to the HUB, chk_connectivitymay also fail. Do not

continue if there are other errors.

...................................................................................................................................................................................................

17 Execute the following command.

create_ht

...................................................................................................................................................................................................

18 Execute the following command to allow MI switchover.

rcc_adm --action clr_inhibit --host $(hostname)

...................................................................................................................................................................................................

19 Execute the following command to check status.

rcc_adm --action disp_inhibit --host $(hostname)


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Grow in the ADCM blades

Procedure

If you have ADCM blades to be grown in, complete the following steps; otherwise,

continue to the next section to synchronize the database....................................................................................................................................................................................................


...................................................................................................................................................................................................


MIcmd state vc




If the primary VM is standby, call MIcmd switch vc to switchover and then

call MIcmd state vc again to verify.

...................................................................................................................................................................................................


create_ht

...................................................................................................................................................................................................



Check the result as follows.


...................................................................................................................................................................................................

5 For each of the blades to be grown in, run

isolate_card -s <shelf number> -c <card number>

For example:

>isolate_card -s 0 -c 5SHELF=0 HUB=169.254.32.112 PORT=17 OID=9




>isolate_card -s 0 -c 6



Growth and de-growth of ALGPv2 blades Grow in the ADCM blades

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-13





...................................................................................................................................................................................................

6 If the blade to be grown in is not seated in the shelf yet, plug the blades into the shelf

now.

...................................................................................................................................................................................................

7 Run lcp_hostgrow and fill in the card type, service type, redundancy type, shelf and slot

numbers for the blades that are grown in.

lcp_hostgrow

Example:


# lcp_hostgrow

lcp_hostgrow is a tool used to prepare SIM host files

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_host.data

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_srv.data

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_system.data

/var/opt/tmp/lcp_hostgrow/var/opt/lib/mtce/data/mtce_tim.data

for growing one or more service(s) on the existing

card(s). Enter the shelf, card and host number for

the card pair, then enter the service type(s) for

the card pair.

You can use ^C (CTRL + C) at any time to


******************************************************************

* Interactive Mode *

******************************************************************


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Side A: Enter the SHELF number [ 0 ]: 0

Side A: Enter the CARD number [ 1-6, 9-14 ]: 5

Side B: Enter the SHELF number [ 0 ]: 0

Side B: Enter the CARD number [ 1-6, 9-14 ]: 6

The allowed service types are as follows:

accm

adcm

gjs

gos

Enter the service(s) (seperated by space) for host growth: adcm

Below are the disk scheme and ID for target host:



3) indapp_20_300G,rear:1

4) storage_175_300G,rear:1

Please input number associated with the valid disk scheme: 2


The SIM log is /storage/sim/log/lcp_hostgrow/sim.log



Type 'y' to begin host growth; type 'n' to exit host growth: y

SIM began successfully.



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-15





# clia board 5


Physical Slot # 5

92: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x02PICMG Version 2.2



92: FRU # 0

Entity: (0xa0, 0x60)



Device ID String: "BMR-H8S MOLENE"

92: FRU # 1

Entity: (0xc0, 0x60)



Device ID String: "RTM"

#

...................................................................................................................................................................................................

10 Ensure that the hot swap state of the cards was shown as active in the previous step.

...................................................................................................................................................................................................

11 Was the hot swap state inactive?

IF . . . THEN . . .

YES The blades must be powered on

Execute the following command from the active ShMC.

clia activate board 5


...................................................................................................................................................................................................

12 Note: To complete this step, you must be logged in through the console port, a

terminal server hosting the console port of the blades or through a SOL console

session.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-17



Log into each blade to be grown. Open the terminal server session and the SOL console

session for the blades. If the blade is at login prompt, log into the blade as root and reboot

each blade from network. This is done during the memory check and pressing n for each

blade.

You may see the output of bios (memory check and so forth) whether in terminal server

session or SOL console session during host boot up.

...................................................................................................................................................................................................

13 Wait for the login prompt and log in as root. If the Jumpstart prompt is seen, execute the

following command on OAM to resume SIM.


Output example:

> sim --proc lcp_hostgrow --action resume

**************************************************************************


**************************************************************************

rules file: /opt/LSS/share/sim/rules/lcp_hostgrow/lcp_hostgrow.xml

data directory: /storage/sim/data/lcp_hostgrow

log file: /storage/sim/log/lcp_hostgrow/sim.log

The current 'apply' of the sim 'lcp_hostgrow' procedure is notfinished.


Ready to 'resume' the sim 'lcp_hostgrow' procedure 'apply':Continue? (y/n) y

Executing ' sim --proc lcp_hostgrow --action resume '...

...................................................................................................................................................................................................

14 To monitor the sim lcp_hostgrow procedure's log file use the following command.:


Output example:

13/02/01 01:00:39 SIM096 The sim 'update' procedure currently hasno 'rollback' to reset.

13/02/01 01:00:39 SIM096

13/02/01 01:00:39 SIM096_end (SUCCESS)

13/02/01 01:00:39 SIM097_begin [seclogger 'GROWTH COMPLETEDSUCCESSFULLY!']

[pid=8618] (lcp_hostgrow:906)

13/02/01 01:00:39 SIM097_end (SUCCESS)


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015







Backing up blade configuration

Note: Telneting for TL1 access is denied from anywhere outside the local board

unless the SYS-SECU command parameter telnetAccess is set to Y . It is N by default.

The user must first SSH (ssh <hostname>) to the ACCM blade and then run “telnet

localhost 2361" or “telnet 0 2361” to access TL1. Then the user can log on using the ACT-USER command.

Procedure

You should back up the blade before degrow because all provisioning may be lost.

...................................................................................................................................................................................................

1 Are you logged into the blade?

IF . . . THEN . . .

YES Continue to the next step.

NO From the OS of the active ACCM blade and enter the following:

telnet localhost 2361 or telnet 0 2361 to telnet to the ACCM blades for

TL1.

Then log on using the ACT-USER command.

...................................................................................................................................................................................................

2 Retrieve chassis provisioning using the RTRV-ATCA-CHASSIS TL1 command and make

note of provisioning.

Command RTRV-ATCA-CHASSIS;

...................................................................................................................................................................................................

3 Retrieve blade provisioning using the RTRV-ATCA-EQPT TL1 command and make note

of provisioning.

Command RTRV-ATCA-EQPT;

...................................................................................................................................................................................................

4 Are you going to use TL1 or OMC-P?

IF . . . THEN . . .

TL1 Then continue to the next step.

Growth and de-growth of ALGPv2 blades Backing up blade configuration

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-21



IF . . . THEN . . .

OMC-P Refer to the Alcatel-Lucent Gateway Platform Switch Upgrade/Backup/Restore

Overview chapter in the COM User Guide, 255-400-400 and follow instructions.

When you finish, return to “De-growth procedure” (p. 8-23).

...................................................................................................................................................................................................

5 Save the current configuration before the blade de-growth.

Syntax: EXEC-BACKUP-CFG:[TID]:[<src>]:[CTAG]::<desthost>,

<username>,<password>,<destdir>,[<suppressoutput>

],[<tmout>],[<xferprtcl>];

Command Example: EXEC-BACKUP-CFG:::::192.168.xxx.xxx,root,newsys,/

home,,,ftp;

The above is an example. You should use the correct values for your application.

...................................................................................................................................................................................................

6 Wait for a response that the backup completed.

...................................................................................................................................................................................................

7 Did the backup fail?

IF . . . THEN . . .

YES Contact Technical Support.

NO You have completed this procedure.

Growth and de-growth of ALGPv2 blades Backing up blade configuration

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



De-growth procedure

Introduction

These procedures provide the steps to de-grow or remove blades.

For a duplex pair, the de-growth must be executed for both blades in the pair. You cannotde-grow a single blade in a pair.

If you are going to de-grow ACCMs, ADCMs must be removed first.

Attention: Removal of blades can disrupt service.

Traffic should be disabled on blades before they are removed.

Preparing for ADCM degrowth

...................................................................................................................................................................................................

1 Has the ADCM been provisioned?

IF . . . THEN . . .


NO Go to “De-growing ADCMs” (p. 8-34).

...................................................................................................................................................................................................

2 If you are not logged in to use TL1, from the OS of the active ACCM blade and enter the

following:

telnet localhost 2361 or telnet 0 2361 to telnet to the active or working ACCM blade for TL1.


...................................................................................................................................................................................................

3 Determine the chassis type using the RTRV-ATCA-CHASSIS command.

RTRV-ATCA-CHASSIS;

...................................................................................................................................................................................................

4 Determine the slots and the blades they contain type using the RTRV-ATCA-EQPTSTATE

command.

RTRV-ATCA-EQPTSTATE;

Make note of the slot or slots where ADCMs are installed and the associated poolId. In

the following example, ADCM blades are installed in slots 5 and 6 and the poolId is 3..

Telica> RTRV-ATCA-EQPTSTATE;

Growth and de-growth of ALGPv2 blades De-growth procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-23



telica 2010-07-11 00:22:10

M 0 RTRV

"SHELF-0-ACM-3:CARDTYPE=ACCM,POOLID=1,SWVERSION=8.2.1.0.0.37:IS,ACT"

"SHELF-0-ACM-4:CARDTYPE=ACCM,POOLID=1,SWVERSION=8.2.1.0.0.37:IS,

STBYH""SHELF-0-ACM-5:CARDTYPE=ADCM,POOLID=3,SWVERSION=8.2.1.0.0.37:IS,

ACT"

"SHELF-0-ACM-6:CARDTYPE=ADCM,POOLID=3,SWVERSION=8.2.1.0.0.37:IS,STBYH"

"SHELF-0-ACM-9:CARDTYPE=NULL,POOLID=NULL,SWVERSION=NULL:OOS,UAS"

"SHELF-0-ACM-10:CARDTYPE=NULL,POOLID=NULL,SWVERSION=NULL:OOS,UAS"

"SHELF-0-ACM-11:CARDTYPE=NULL,POOLID=NULL,SWVERSION=NULL:OOS,UEQ&UAS"




/* RTRV-ATCA-EQPTSTATE */

...................................................................................................................................................................................................

5 What is the chassis type?

IF . . . THEN . . .

ATCA_MGC “Unprovisioning the ADCM of an ATCA_MGC”

(p. 8-28)

ATCA_VSG_MGC Continue to “Unprovisioning the ADCM of anATCA_VSG_MGC” (p. 8-24).

Unprovisioning the ADCM of an ATCA_VSG_MGC

...................................................................................................................................................................................................

1 Retrieve signaling links of SLKL2 using the RTRV-STG-SLKL2 command.

RTRV-STG-SLKL2;

Make note of the signaling link IDs of the ADCMs that you are going to remove.

In the following example signaling links for the ADCM in slot 5 are, 51, 111, 121, 122,

313 and 323.

RTRV-STG-SLKL2


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



"51:SIGTYPE=LOWSPEED,TERMID=SHELF-0-ACM-5-AMCSS7-1-T1-1-DS0-17,M2UAIID=51,M2PAASSOCID=NULL,SLKL2PRFLID=3,MTP2DRVRPRTCL=CHINA,LNKSPEED=64K,LSSULEN=1"

"111:SIGTYPE=LOWSPEED,TERMID=SHELF-0-ACM-5-AMCSS7-1-T1-1-DS0-16,

M2UAIID=111,M2PAASSOCID=NULL,SLKL2PRFLID=1,MTP2DRVRPRTCL=ANSI,LNKSPEED=64K,LSSULEN=2"

"121:SIGTYPE=LOWSPEED,TERMID=SHELF-0-ACM-5-AMCSS7-1-T1-3-DS0-5,M2UAIID=121,M2PAASSOCID=NULL,SLKL2PRFLID=1,MTP2DRVRPRTCL=ANSI,LNKSPEED=64K,LSSULEN=2"

"122:SIGTYPE=LOWSPEED,TERMID=SHELF-0-ACM-5-AMCSS7-1-T1-7-DS0-6,M2UAIID=122,M2PAASSOCID=NULL,SLKL2PRFLID=1,MTP2DRVRPRTCL=ANSI,LNKSPEED=64K,LSSULEN=2"

"313:SIGTYPE=LOWSPEED,TERMID=SHELF-0-ACM-5-AMCSS7-1-T1-1-DS0-23,M2UAIID=313,M2PAASSOCID=NULL,SLKL2PRFLID=2,MTP2DRVRPRTCL=ITU,

LNKSPEED=64K,LSSULEN=1"

"323:SIGTYPE=LOWSPEED,TERMID=SHELF-0-ACM-5-AMCSS7-1-T1-1-DS0-15,M2UAIID=323,M2PAASSOCID=NULL,SLKL2PRFLID=2,MTP2DRVRPRTCL=ITU,LNKSPEED=64K,LSSULEN=1"

/* RTRV-STG-SLKL2 */

...................................................................................................................................................................................................

2 Retrieve signaling links of SLKL3 using the RTRV-STG-SLKL3 command.

RTRV-STG-SLKL3;

Make note of the signaling link IDs of the ADCMs that you are going to remove and thestate. Also note if there are any M2PAASSOCIDs.

In the following example signaling links for the ADCM in slot 5 are, 51, 111, 121, 122,

313 and 323 and they are all IS. All M2PAASSOCIDs are NULL

RTRV-STG-SLKL3

"51:SIGTYPE=NARROWBAND,PRIM2UAASSOCID=NULL,M2PAASSOCID=NULL,M2UAIID=51,LSETID=51,MTP3PRFLID=1,SLC=1,SECM2UAASSOCID=NULL,ENABLEMTP3T31=Y,RESETMTP3T31=Y:IS,"




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-25






/* RTRV-STG-SLKL3 */

...................................................................................................................................................................................................

3 Place each IS signaling link ID to OOS using the ED-STG-SLKL3 command.

ED-STG-SLKL3::51::::oos;

Repeat the command for every IS signaling link ID.

...................................................................................................................................................................................................

4 Delete each OOS signaling link ID using the DLT-STG-SLKL3 command.

DLT-STG-SLKL3::51;

Repeat the command for every OOS signaling link ID identified previously.

...................................................................................................................................................................................................

5 Delete each L2 signaling link ID using the DLT-STG-SLKL2 command.

DLT-STG-SLKL2::51;

Repeat the command for every L2 signaling link ID identified previously.

...................................................................................................................................................................................................

6 Retrieve signaling links of SLKAAL5 using the RTRV-STG-SLKAAL5 command.

RTRV-STG-SLKAAL5;

Make note of the signaling link IDs of the ADCMs that you are going to remove.

...................................................................................................................................................................................................

7 Were there any SLKAAL5 signaling links?

IF . . . THEN . . .


NO Go to Step 9.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015





...................................................................................................................................................................................................

15 Are there any M3UA associations of the ADCM?

IF . . . THEN . . .


NO Go to Step 18.

...................................................................................................................................................................................................

16 Place all M3UA associations of the ADCM to OOS using the ED-MGC-M3UAASSOC

command.

ED-MGC-M3UAASSOC::1-1:::OOS;

...................................................................................................................................................................................................

17 Delete all M3UA associations using the DLT-MGC-M3UAASSOC command.

DLT-MGC-M3UAASSOC::1-1;

...................................................................................................................................................................................................

18 Continue to “Unprovisioning the ADCM of an ATCA_MGC” (p. 8-28).

Unprovisioning the ADCM of an ATCA_MGC

...................................................................................................................................................................................................

1 Retrieve the properties of the association between a MGC-8 and a media gateways using

the RTRV-MGC-MGASSOC command.

RTRV-MGC-MGASSOC;

Locate the responses in which the poolId is the same as the poolId of the ADCM to be

de-grown. Note the mgName values associated with the poolId of the ADCM to be

de-grown.

...................................................................................................................................................................................................

2 Retrieve the identities of the media gateways associated with a configured realm using the

RTRV-REALM-MGASSOC command.

RTRV-REALM-MGASSOC;

Locate the responses in which the mgName of realmMgAssoc is an MG identified in the

previous step. Note the value of the realmId .


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



...................................................................................................................................................................................................

3 Delete all realms associated with MGs identified in the previous step using the

DLT-REALM-MGASSOC command.

DLT-REALM-MGASSOC::REALM-"realm16"-MGNAME-a751014bgw18;

...................................................................................................................................................................................................

4 Retrieve lists of media gateways using the RTRV-LIST-MG command.

RTRV-LIST-MG;

Note the mgListName that is applicable to the ADCM to be de-grown. The first part is the

mgList and the second part is index. The MG name should be an MG you identified in

Step 1.

...................................................................................................................................................................................................

5 Retrieve lists of SIP servers using the RTRV-LIST-SIPSRVR command.

RTRV-LIST-SIPSRVR;

Note the sipSrvrListAid that is applicable to the ADCM to be de-grown. The first part is

the sipSrvrList and the second part is index.

...................................................................................................................................................................................................

6 Retrieve the mapping rules that govern how the SIP redirect server maps incoming SIP

calls to a list of media gateways using the RTRV-SIP-SRVRMAPADDR command.

RTRV-SIP-SRVRMAPADDR;

Note the sipSrvrMapAddrAid and the ACTION, which is an MG name that you identified

in Step 1....................................................................................................................................................................................................

7 Delete the mapping rules that govern how the SIP redirect server maps incoming SIP calls

to a list of media gateways using the DLT-SIP-SRVRMAPADDR command.

DLT-SIP-SRVRMAPADDR::SDPCON-10.84.2.70;

Use the sipSrvrMapAddrAid that you identified previously.

...................................................................................................................................................................................................

8 Retrieve the properties of a route using the RTRV-ROUTE command.

RTRV-ROUTE;

Note the mgList that you identified in Step 4 and the associated rtId .

...................................................................................................................................................................................................

9 Delete a route using the DLT-ROUTE command.

Use the rtIds that you identified in the previous step.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-29



DLT-ROUTE::SIPP9062-0;

...................................................................................................................................................................................................

10 Retrieve the mapping of specific connection and origin addresses using the

RTRV-MGC-MGMAPADDR command.

RTRV-MGC-MGMAPADDR;

Note the tgn that is associated with the mgList that you identified in Step 4.

...................................................................................................................................................................................................

11 Delete the mapping of specific connection and origin addresses using the

DLT-MGC-MGMAPADDR command.

DLT-MGC-MGMAPADDR::TGN-8310-SDPCON-DEFAULT-SDPORIG-DEFAULT;

...................................................................................................................................................................................................

12 Delete the sipSrvrList identified in Step 5 using the DLT-LIST-SIPSRVR command.

DLT-LIST-SIPSRVR::SIPSRVRLIST1;

...................................................................................................................................................................................................

13 Delete the MG lists identified in Step 4 using the DLT-LIST-MG command.

DLT-LIST-MG::MGLIST1-x;

...................................................................................................................................................................................................

14 Delete the CAS lines associated with the MGs identified in Step 1 using the

DLT-CAS-LINE command.

DLT-CAS-LINE::WF1_BGW4;...................................................................................................................................................................................................

15 Retrieve the properties of an ISDN interface using the RTRV-ISDN-IF command.

RTRV-ISDN-IF;

Note the ifnum that is associated with the mgName that you identified in Step 1.

...................................................................................................................................................................................................

16 Retrieve the properties of an ISDN link using the RTRV-ISDN-LINK command and the

ifnum that you identified in the previous step

RTRV-ISDN-LINK::3031;

...................................................................................................................................................................................................

17 Retrieve the properties of an ISDN B channel using the RTRV-ISDN-BCHAN command.

RTRV-ISDN-BCHAN::3031;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

18 Delete the properties of an ISDN B channel using the DLT-ISDN-BCHAN command.

DLT-ISDN-BCHAN::3031-1&&-31;

...................................................................................................................................................................................................

19 Delete the properties of an ISDN link using the DLT-ISDN-LINK command

DLT-ISDN-LINK::3031-1;

...................................................................................................................................................................................................

20 Delete the properties of an ISDN interface using the DLT-ISDN-IF command.

DLT-ISDN-IF::3031;

...................................................................................................................................................................................................

21 Delete each association between the IUA subsystem in a MGC-8 and a remote media

gateway using the DLT-MGC-MGIUA command.

DLT-MGC-MGIUA::a751013tgw19;

...................................................................................................................................................................................................

22 Retrieve the properties for an IVT trunk using the RTRV-IVT-TRK command.

RTRV-IVT-TRK;

Note the ivtTrkAid that is associated with the mgName that you identified in Step 1.

...................................................................................................................................................................................................

23 Delete each IVT trunk identified in the previous step using the DLT-IVT-TRK command.

DLT-IVT-TRK::4022-1;

...................................................................................................................................................................................................

24 Note: You must know the tgn of the trunk.

Retrieve information about an SS7 trunk using the RTRV-SS7-TRK command.

RTRV-SS7-TRK::<SS7 TRUNK AID>;

Note the SS7 trunks that are associated with mgNames that you identified in Step 1 and

the primary state.

...................................................................................................................................................................................................

25 Change the primary state of the SS7 trunks to OOS using the ED-SS7-TRK command.

ED-SS7-TRK::9013-25:::MGNAME=a751013tgw01:OOS;

...................................................................................................................................................................................................

26 Delete the SS7 trunks using the DLT-SS7-TRK command.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-31



DLT-SS7-TRK::9013-25;

...................................................................................................................................................................................................


Retrieve information about a CAS SS7 trunk using the RTRV-CAS-TRK command.

RTRV-CAS-TRK::3303;

Note the CAS trunks that are associated with mgNames that you identified in Step 1 and

the primary state.

...................................................................................................................................................................................................

28 Change the primary state of the CAS trunks to OOS using the ED-CAS-TRK command.

ED-CAS-TRK::3301-1:::MGNAME=a751013tgw01:OOS;

...................................................................................................................................................................................................

29 Delete the CAS trunks using the DLT-CAS-TRK command.DLT-CAS-TRK::3301-1;

...................................................................................................................................................................................................


Retrieve information about a BICC trunk using the RTRV-BICC-TRK command.

RTRV-BICC-TRK::8000;

Note the BICC trunks that are associated with mgNames that you identified in Step 1 and

the primary state.

...................................................................................................................................................................................................

31 Change the primary state of the BICC trunks to OOS using the ED-BICC-TRK command.

ED-BICC-TRK::8001-1397:::MGNAME=bgw80:OOS;

...................................................................................................................................................................................................

32 Delete the BICC trunks using the DLT-BICC-TRK command.

DLT-BICC-TRK::8001-1397;

...................................................................................................................................................................................................

33 Place each association identified in Step 1 OOS using the ED-MGC-MGASSOC command.ED-MGC-MGASSOC::a751014bgw18::::OOS;

...................................................................................................................................................................................................

34 Delete each association identified in Step 1 using the DLT-MGC-MGASSOC command.

DLT-MGC-MGASSOC::a751014bgw18;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

35 Continue to “Unprovisioning common features of the ADCM ” (p. 8-33).

Unprovisioning common features of the ADCM

...................................................................................................................................................................................................

1 Delete IP routes of the ADCM blade using the DLT-IPROUTE command.

DLT-IPROUTE::SHELF-0-ACM-5-<destIpAddr>-<subnetMask>;

Substitute the correct value for destIpAddr and subnetMask .

...................................................................................................................................................................................................

2 Is the chassis type equal to ATCA_MGC?

IF . . . THEN . . .

YES Go to “De-growing ADCMs” (p. 8-34).


...................................................................................................................................................................................................

3 Retrieve parameters for E1 and T1 ports using the RTRV-E1 or RTRV-T1command.

RTRV-E1::SHELF-0-ACM-5-AMCSS7-1;

RTRV-E1::SHELF-0-ACM-5-AMCSS7-2;

RTRV-T1::SHELF-0-ACM-5-AMCSS7-1;

RTRV-T1::SHELF-0-ACM-5-AMCSS7-2;

...................................................................................................................................................................................................

4 Place all ports OOS using the ED-E1 or ED-T1command. command.

ED-E1::SHELF-0-ACM-5-AMCSS7-1-E1-<port>::::OOS;

ED-E1::SHELF-0-ACM-5-AMCSS7-2-E1-<port>::::OOS;

ED-T1::SHELF-0-ACM-5-AMCSS7-1-T1-<port>::::OOS;

ED-T1::SHELF-0-ACM-5-AMCSS7-2-T1-<port>::::OOS;

Substitute the correct value, 1-8, for port .

...................................................................................................................................................................................................

5 Delete all OOS ports using the DLT-E1 or DLT-T1command. command.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-33

E N D O F S T E P S...................................................................................................................................................................................................



DLT-E1::SHELF-0-ACM-5-AMCSS7-1-E1-<port>;

DLT-E1::SHELF-0-ACM-5-AMCSS7-2-E1-<port>;

DLT-T1::SHELF-0-ACM-5-AMCSS7-1-T1-<port>;

DLT-T1::SHELF-0-ACM-5-AMCSS7-2-T1-<port>;

Substitute the correct value, 1-8, for port .

...................................................................................................................................................................................................

6 Using the following TL1 commands, remove the AMCSS7.

RMV-EQPT::SHELF-0-ACM-5-AMCSS7-1;




...................................................................................................................................................................................................

7 Using the following TL1 command, delete the AMCSS7.

DLT-ATCA-EQPT::SHELF-0-ACM-5-AMCSS7-1;




...................................................................................................................................................................................................

8 Continue to “De-growing ADCMs” (p. 8-34).

De-growing ADCMs

To de-grow (remove) ADCM blades from the MGC-8 chassis, complete the following

steps.

...................................................................................................................................................................................................

1 Note: Ignore the expected error messages when you run the following commands.

Using the following TL1 command, remove the standby ADCM to shutdown the

ALGPv2 applications on the ADCM to be removed.

RMV-EQPT::<STBY-ADCM>;

...................................................................................................................................................................................................

2 Using the following TL1 command, delete the standby ADCM.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



DLT-ATCA-EQPT::<STBY-ADCM>;

...................................................................................................................................................................................................

3 Using the following TL1 command, remove the active ADCM to shutdown the ALGPv2

applications on the ADCM to be removed.

RMV-EQPT::<ACT-ADCM>;

...................................................................................................................................................................................................

4 Using the following TL1 command, delete the active ADCM.

DLT-ATCA-EQPT::<ACT-ADCM>;

...................................................................................................................................................................................................


...................................................................................................................................................................................................


MIcmd state vc

Verify:




...................................................................................................................................................................................................

7 Was the primary VM standby?

IF . . . THEN . . .

YES Run the following command to switchover.

MIcmd switch vc

NO Go to Step 9

...................................................................................................................................................................................................

8 Then run the following command again to verify.

MIcmd state vc

...................................................................................................................................................................................................


create_ht

...................................................................................................................................................................................................



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-35



health --test all

...................................................................................................................................................................................................



...................................................................................................................................................................................................

12 Check the result using the following command.


...................................................................................................................................................................................................

13 Run the following LCP tool on the OS of the blade with OAM server functionality.

lcp_hostdegrow

Figure 8-1 Example

Run the following LCP tool on the OS of the the blade with OAM

server functionality.

# lcp_hostdegrow

lcp_hostdegrow is a tool used to prepare sim host files

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_host.data

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_tim.data

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_srv.data

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_system.data

for de-growing one card pair. Enter the shelf and card number forone

side (A or B) for the host pair.

You can use ^C (control-C) at any time to safely abort thisinteractive script.

Enter the SHELF number [0-1]: 0

Enter the CARD number [1..6,9..14]: 5

Removing the following line(s) from MTCE data:

qd05-s00c05h0;10.25.64.80;0;5;0;node;A;qd05-

s00c06h0;FMO16JB;RPCMHDDA;local;NA;NA;NA

qd05-s00c06h0;10.25.64.96;0;6;0;node;B;qd05-

s00c05h0;FMO16JB;RPCMHDDA;local;NA;NA;NA

servicetype=adcm shelf1=0 card1=5 shelf2=0 card2=6

ALGPv2 start de-growth rule checksALGPv2 de-growth rule checks successfully


The SIM log is /storage/sim/log/lcp_hostdegrow/sim.log


tail -f /storage/sim/log/lcp_hostdegrow/sim.log

Type 'y' to begin host degrowth; type 'n' to exit host degrowth:y


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



***********************************************************************


**********************************************************************

*********

rules file: /opt/LSS/share/sim/rules/lcp_hostdegrow/lcp_hostdegrow.xml

source data directory:

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data

data directory: /storage/sim/data/lcp_hostdegrow log file:

/storage/sim/log/lcp_hostdegrow/sim.log

*** WARNING ***

The sim 'lcp_hostdegrow' procedure will be '(re)applied' from thebeginning.

If you continue, no further actions will be allowed based on the

procedure's current state.

Ready to 'apply' the sim 'lcp_hostdegrow' procedure from thebeginning:

Continue? (y/n) y

Executing ' sim --proc lcp_hostdegrow --action apply --no_prompt'...

To monitor the sim 'lcp_hostdegrow' procedure's log file use:


...................................................................................................................................................................................................

14 Tail the sim.log to verify that the de-growth procedure succeeded until you seeCOMPLETED SIM PROCEDURE 'lcp_hostdegrow apply'.


...................................................................................................................................................................................................

15 Re-run the following command to save the backup files.

create_ht

...................................................................................................................................................................................................

16 Enable MI switchover as follows.

rcc_adm --action clr_inhibit --host $(hostname)

...................................................................................................................................................................................................

17 Now the LED on the de-grown blades has turned blue and it is safe to remove the blades.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-37

E N D O F S T E P S...................................................................................................................................................................................................



De-growing ACCMs

Note: This procedure is not applicable for a co-host MGC-8 chassis.

To de-grow (remove) ACCM blades from the non-co-host (standalone) MGC-8 chassis,

complete the following steps.

...................................................................................................................................................................................................

1 Have you already removed the ADCM blades?

IF . . . THEN . . .


NO Go to “De-growing ADCMs” (p. 8-34) and complete procedure before

continuing with the following steps.

...................................................................................................................................................................................................

2 Using the following TL1 command, remove the standby ACCM to shutdown the ALGPv2

applications on the ACCM to be removed.

RMV-EQPT::<STBY-ACCM>;

...................................................................................................................................................................................................

3 Run the following command to shutdown the ALGPv2 applications on the active ACCM

to be removed:

pkill -9 emf

...................................................................................................................................................................................................


...................................................................................................................................................................................................


MIcmd state vc

Verify:




...................................................................................................................................................................................................

6 Was the primary VM standby?

IF . . . THEN . . .


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



YES Run the following command to switchover.

MIcmd switch vc

NO Go to Step 8

...................................................................................................................................................................................................

7 Then run the following command again to verify.

MIcmd state vc

...................................................................................................................................................................................................


create_ht

...................................................................................................................................................................................................


health --test all

...................................................................................................................................................................................................



...................................................................................................................................................................................................

11 Check the result using the following command.


...................................................................................................................................................................................................

12 Run the following LCP tool on the OS of the blade with OAM server functionality.

# lcp_hostdegrow

lcp_hostdegrow is a tool used to prepare sim host files

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_host.data

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_tim.data

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_srv.data

/var/opt/tmp/lcp_hostdegrow/var/opt/lib/mtce/data/mtce_system.data

for de-growing one card pair. Enter the shelfand card number for one side (A or B) for the host pair.

You can use ^C (control-C) at any time to


Enter the SHELF number [0-1]: 0

Enter the CARD number [1..6,9..14]: 5

Removing the following line(s) from MTCE data:


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-39





...................................................................................................................................................................................................

16 Now the LED on the de-grown blades has turned blue and it is safe to remove the blades.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



8-41

E N D O F S T E P S...................................................................................................................................................................................................





9 9Provisioning of ALGPv2

blades

Overview

Purpose

This chapter provides instructions for provisioning (initial) the AxCM blades, configuring

the AMC SS7 cards for signaling functionality, and also provides information on how to perform some tests.

Contents

Provision the ACCM and ADCM blades 9-2

Provisioning AMC SS7 cards 9-9

Performing DS1 or E1 loopbacks 9-11

Check the management/signaling interface duplex setting 9-15

Check the network IP address of the MGC-8 and other NEs with which itcommunicates

9-18

What’s next 9-19

...................................................................................................................................................................................................................................



9-1



Provision the ACCM and ADCM blades

Introduction

Complete the following sections to provision the ACCM and ADCM blades.

Procedure




localhost 2361" or “telnet 0 2361” to access TL1. Then the user can log on using the

ACT-USER command.

Complete the following procedure to provision the ACCM blades.

...................................................................................................................................................................................................

1 Execute the following command on blade 1, in order to enable ACCM/ADCM services.

/opt/ALGPV2/sbin/mtce_mgc8 --action enable_service

...................................................................................................................................................................................................

2 Is the MGC-8 a non-cohost (standalone) or co-host configuration?

IF . . . THEN . . .

non-cohost

(standalone)

Log into blade 1 or 2. Then SSH to the active and standby ACCM blades.

co-host Log into blade 1 or 2.

...................................................................................................................................................................................................

3 Enter the following command to reboot each blade.

reboot

...................................................................................................................................................................................................

4 If the blade was rebooted, wait until it comes up to complete this step.

Verify that emf is up in each blade as follows.

pidof emfFigure 9-1 Example of a successful response

<mh52-s00c04h0:root>/root:

< pidof emf

11461<mh52-s00c04h0:root>/root:

Provisioning of ALGPv2 blades Provision the ACCM and ADCM blades

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

5 Did you receive a successful response message from each blade?

IF . . . THEN . . .


NO Contact Technical Support.

...................................................................................................................................................................................................

6 From the OS of the odd ACCM blade, enter the following:

telnet localhost 2361 or telnet 0 2361 to establish a TL1 session with the odd

ACCM blade.

Once the dialogue starts, hit escape key once to get the Telica prompt.

1999-2014 Alcatel-Lucent Inc.

Telica>

...................................................................................................................................................................................................

7 In the TL1 session, enter the command act-user::uid:::pid; substituting the user

or login name for uid and the password for pid . The default uid is telica and the default

pid is telica.

ACT-USER::telica:::telica;

The pid will display as asterisks (*).

Figure 9-2 Login example

Telica> act-user::telica:::******;

telica 2012-07-31 23:01:23

* 0 REPT EVT SESSION

"telica:N,,

/* NOTICE: This is a private computer system.

Unauthorized access or use may lead to prosecution.

Last login: Wed Aug 31 22:52:21 2011

Session Identifier: [telica-19]Total number of active sessions for user telica is 1

This is the WORKING System Processor */"

/* REPT-EVT-SESSION */

;

telica 2012-07-31 23:01:23

M 0 COMPLD


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-3



;

Telica>

...................................................................................................................................................................................................

8 Is the ACCM identified as WORKING or PROTECTION?

IF . . . THEN . . .

WORKING Go to Step 13

PROTECTION Continue to the next step.

...................................................................................................................................................................................................

9 Execute the CANC-USER command to terminate the TL1 session.

CANC-USER;

...................................................................................................................................................................................................

10 Is the MGC-8 a non-co-host (standalone) or co-host configuration?

IF . . . THEN . . .

non-co-host

(standalone)

From the OAM-server, SSH to the even ACCM blades.

co-host Log into blade 2.

...................................................................................................................................................................................................

11 From the OS of the even ACCM blade, enter the following:

telnet localhost 2361 or telnet 0 2361 to establish a TL1 session with the

even ACCM blade.

Once the dialogue starts, hit escape key once to get the Telica prompt.

...................................................................................................................................................................................................

12 In the TL1 session, enter the command ACT-USER::uid:::pid; substituting the user


pid is telica.


The pid will display as asterisks (*).

The login screen should identify the ACCM as WORKING.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

13 Do you want to enable telnetAccess? By default telnetAccess is disabled

IF . . . THEN . . .

YES Enter the following command to enable telnetAccess.

ED-SYS-SECU:::::TELNETACCESS=Y;


...................................................................................................................................................................................................

14 Enter the RTRV-ATCA-EQPT TL1 command to verify that the ACCM blades are coming

up IS, UAS&ACT/STBYH

RTRV-ATCA-EQPT;

telica 2012-12-28 14:54:03

M 0 RTRV

"SHELF-0-ACM-3:VIRTUALSLOT=NULL,MODULETYPE=NULL,SWVERSION=NULL,

CARDTYPE=NULL,REDUNDANCY=NULL,POOLID=NULL,MEMTHRESHOLD=NULL,

NVMEMTHRESHOLD=NULL,BUSYTHRESHOLD=NULL,EMIPV4FIXED=NULL,

EMIPV4FLOATING=NULL,EMIPV4NTWKMASK=NULL,EMFAILOVERTMR=NULL,

SIGAIPV4FIXED=NULL,SIGAIPV4FLOATING=NULL,SIGAIPV4NTWKMASK=NULL,

SIGAFAILOVERTMR=NULL,SIGBIPV4FIXED=NULL,SIGBIPV4FLOATING=NULL,

SIGBIPV4NTWKMASK=NULL,SIGBFAILOVERTMR=NULL:IS,UAS&ACT"

"SHELF-0-ACM-4:VIRTUALSLOT=NULL,MODULETYPE=NULL,SWVERSION=NULL,

CARDTYPE=NULL,REDUNDANCY=NULL,POOLID=NULL,MEMTHRESHOLD=NULL,

NVMEMTHRESHOLD=NULL,BUSYTHRESHOLD=NULL,EMIPV4FIXED=NULL,

EMIPV4FLOATING=NULL,EMIPV4NTWKMASK=NULL,EMFAILOVERTMR=NULL,SIGAIPV4FIXED=NULL,SIGAIPV4FLOATING=NULL,SIGAIPV4NTWKMASK=NULL,

SIGAFAILOVERTMR=NULL,SIGBIPV4FIXED=NULL,SIGBIPV4FLOATING=NULL,

SIGBIPV4NTWKMASK=NULL,SIGBFAILOVERTMR=NULL:IS,UAS&STBYH"

...................................................................................................................................................................................................

15 Note: The recommended installation is to use the rear ports, however, the front ports

can also be used.

Enter the TL1 command ED-ATCA-CHASSIS to assign the port for mgt0, siga, and sigb

interface if necessary.

Example:ED-ATCA-CHASSIS:telica::100::CHASSISTYPE=ATCA_VSG_MGC, SIGAPORT=

REAR_GE0,SIGBPORT=REAR_GE1,EMPORT=REAR_GE2;

The ACCM/ADCM mgt0 must use the same transport that the OAM Server uses as its

management subnet (and must be in the same subnet). For example, if on Worksheet 2,

the transport interface is designated as “Both Front Interface-0” the EMPORT must be

“FRONT_GE0”.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-5



...................................................................................................................................................................................................

16 Run the ENT-ATCA-EQPT TL1 command (twice) for each of the ACCM blades to be

provisioned.

Note: If you do not know the MODULETYPE run the ipmitool fru command to

retrieve the Board or Product Part Number for the ACCM card. Because the part

number is twelve characters and the MODULETYPE must be ten characters, ignore

the last two characters.

Example:

ENT-ATCA-EQPT::shelf-0-acm-3:::MODULETYPE=3CM02859BB, SWVERSION=

9.X.X.X.X.X.,CARDTYPE=ACCM,REDUNDANCY=DX,POOLID =1,EMIPV4FIXED=

152.148.185.196,EMIPV4FLOATING=152.148.187.196,EM IPV4NTWKMASK=

22,SIGAIPV4FIXED=152.148.169.196,SIGAIPV4FLOATIN G=

152.148.171.196,SIGAIPV4NTWKMASK=22,SIGBIPV4FIXED=152.148.173.

196,SIGBIPV4FLOATING=152.148.175.196,SIGBIPV4NTWKMASK=22;

Example:ENT-ATCA-EQPT::shelf-0-acm-4:::MODULETYPE=3CM02859BB, SWVERSION=

9.X.X.X.X.X.,CARDTYPE=ACCM,REDUNDANCY=DX,POOLID =1,EMIPV4FIXED=

152.148.186.196,EMIPV4FLOATING=152.148.188.196,EM IPV4NTWKMASK=

22,SIGAIPV4FIXED=152.148.170.196,SIGAIPV4FLOATIN G=

152.148.172.196,SIGAIPV4NTWKMASK=22,SIGBIPV4FIXED=152.148.174.

196,SIGBIPV4FLOATING=152.148.176.196,SIGBIPV4NTWKMASK=22;

Comment: Substitute the correct version for 9.X.X.X.X.X.

...................................................................................................................................................................................................

17 Run the following TL1 command to reset the blades for the provisioning to take affect.

INIT-ATCA-SYS::1:::10;

Note: Observe the following.

1. The INIT-ATCA-SYS; command will terminate all dialogues with the ACCMs.

2. Although you are required to run the ENT-ATCA-EQPT command twice; once for

each of the ACCM blades to be provisioned, you only need to run the

INIT-ATCA-SYS command one time to reset both blades.

...................................................................................................................................................................................................

18 You must open a TL1 session.• If you enabled telnetAccess in Step 13, you can Telnet using the EMIPV4FLOATING

address provisioned in Step 16. Then continue to the next step.

• If you did not enable telnetAccess in Step 13, you must execute Step 6 to Step 12 and

then return to Step 20


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

19 In the TL1 session, enter the command act-user::uid:::pid; substituting the user


pid is telica.


...................................................................................................................................................................................................

20 Do you need to provision ADCM blades?

IF . . . THEN . . .


NO Go to Step 22.

...................................................................................................................................................................................................

21 Note: If the switch is a VSG_MGC and already has M3UA or external M2UA

provisioned, then the ADCM(s) should be place OOS so the M3UA and external

M2UA can be provisioned before the ADCM(s) is placed IS.

Run ENT-ATCA-EQPT TL1 command for each of the ADCM blades to be provisioned.

The blades will automatically reboot.

To provision the ADCM blades, you use the same TL1 command (ENT-ATCA-EQPT)

with the following changes:

• CARDTYPE=ADCM

• POOLID=<value greater than 1>

Example:

ENT-ATCA-EQPT::SHELF-0-ACM-5:::MODULETYPE=3CM02859BB,SWVERSION=

9.X.X.X.X.X,CARDTYPE=ADCM,REDUNDANCY=dx,POOLID=3,EMIPV4FIXED=

192.168.xxx.xxx,EMIPV4NTWKMASK=24,SIGAIPV4FIXED=10.11.27.4,

SIGAIPV4FLOATING=10.11.27.6,SIGAIPV4NTWKMASK=24,SIGBIPV4FIXED=

10.175.21.4,SIGBIPV4FLOATING=10.175.21.6,SIGBIPV4NTWKMASK=24;

Comment: Substitute the correct version for 9.X.X.X.X.X.

Repeat this step for other ADCM blades.

...................................................................................................................................................................................................

22 Verify the status of the blades using the following TL1 command.

RTRV-ATCA-EQPTSTATE;

Verify that the final status of the ACCM blades are shown as IS,ACT and IS,STBYH.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-7



Repeat this step until the blades show a status of IS,ACT and IS,STBYH and then

continue.

...................................................................................................................................................................................................

23 Verify the properties of the chassis using the following TL1 command.

RTRV-ATCA-CHASSIS;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Provisioning AMC SS7 cards

Before you begin

The AMC SS7 cards provide the signaling functionality and can be provisioned on both

ACCM and ADCM blades.• For the processor blade (FM016JB or FM016JP), the AMC SS7 iSPAN3640 AMC

product part number is H03640001A0X

Procedure





ACT-USER command.

...................................................................................................................................................................................................

1 Do you know the moduleType of the card?

IF . . . THEN . . .

YES Go to Step 4


...................................................................................................................................................................................................

2 Connect the cable to the CP port of the card for which you need to know the moduleTypeand then enter the following command.

ipmitool fru

...................................................................................................................................................................................................

3 If DS1s or E1s will be used, ensure the cables are connected correctly

...................................................................................................................................................................................................

4 From the OS of the active ACCM blade and enter the following:

telnet localhost 2361 or telnet 0 2361 to telnet to the ACCM blades for TL1.


...................................................................................................................................................................................................

5 Using TL1, provision the AMC SS7 card for Release 9.X.X, by entering the following

TL1 commands

Provisioning of ALGPv2 blades Provisioning AMC SS7 cards

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-9



Example:

ENT-ATCA-EQPT::SHELF-0-ACM-3-AMCSS7-1:::MODULETYPE=H03639011C,

CARDTYPE=AMCSS7,REDUNDANCY=SX:IS;

Example:

ENT-ATCA-EQPT::SHELF-0-ACM-4-AMCSS7-1:::MODULETYPE=H03639011C,


...................................................................................................................................................................................................

6 Do you want to test the T1s or E1s using loopbacks?

IF . . . THEN . . .

YES Go to “Performing DS1 or E1 loopbacks” (p. 9-11).


...................................................................................................................................................................................................

7 Do you want to provision the T1s or E1s?

IF . . . THEN . . .

YES Go to Rapport MGC-8 ATCA Operations Guide, 255-400-000, Part IX:

Provisioning a MGC-8/VSG, Chapter 75, Provisioning Modules of a MGC-8.

NO Go to “What’s next” (p. 9-19).

Provisioning of ALGPv2 blades Provisioning AMC SS7 cards

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Performing DS1 or E1 loopbacks

Summary

This procedure provides the steps to test a non-traffic carrying switch equipped with DS1s

or E1s. Unit level testing of connections verifies wiring and installation and test theintegrity of the looped ports of modules. This procedures assume that the chassis and

modules have been properly installed and that power, signaling and alarm cabling have

been connected.

These procedures should be completed before the modules are provisioned for service.

Before you begin

You should have knowledge of entering TL1 commands and of their usage. You can find

more information about TL1 command syntax, system responses in the Rapport MGC-8

ATCA TL1 Commands Reference Guide, 255-400-002.

You must have the following equipment.

• Laptop or PC

• ESD wrist strap

• Test set for loop testing

The following must be true.

• Blades to be tested must not be provisioned

• You know the distance from the equipment to the cross-connects.

• You know the default line parameters. You can determine these by retrieving the line

parameters, for example, using the RTRV-T1::SHELF-0–ACM-5–AMCSS7–1; or RTRV-E1::SHELF-0–ACM-5–AMCSS7–1; command or you can reference the

Rapport MGC-8 ATCA TL1 Commands Reference Guide, 255-400-002.

Executing loopbacks

...................................................................................................................................................................................................

1 Ensure you have logged into a TL1 session.

...................................................................................................................................................................................................

2 Enter the RTRV-INFO-EQPT command

Example: RTRV-INFO-EQPT::SHELF-0–ACM-2–AMCSS7–1;

...................................................................................................................................................................................................

3 Enter the blade to be tested using loopbacks with the ENT-ATCA-EQPT command.

Provisioning of ALGPv2 blades Performing DS1 or E1 loopbacks

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-11



Example:

ENT-ATCA-EQPT::SHELF-0-ACM-3-AMCSS7-1:::MODULETYPE=H03640001A00 ,


...................................................................................................................................................................................................

4 Configure the T1 or E1 facility line out of service using the ENT-T1 or ED-T1 commandor the ENT-E1 or ED-E1 command.

Note: Observe the following.

• IFTYPE should be set to USER since the MGC-8 ATCA chassis does not support

a Building Integrated Timing Supply (BITS) source. NETWORK should only be

used if there is no timing provided by the T1/E1 (DS1) line.

• OMODE should be set to NORM during a loopback operation to avoid injecting

AIS when the T1/E1 is OOS.

Syntax: ENT-T1:[TID]:<ds_id>:[CTAG]::[EQLZ=<eqlz>],[FMT=<fmt>],

[LINECDE=<linecde>],[OMODE=<omode>],[TMGREF=<tmgref>],

[IFTYPE=<iftype>]:[<pst>],[<sst>];

Example: ENT-T1::SHELF-0-ACM-3-AMCSS7-1-T1-1:::EQLZ=0,FMT=SF,LINECDE=

B8ZS,OMODE=NORM,IFTYPE=USER:OOS;

Syntax: ENT-E1:[TID]:<ds_id>:[CTAG]::[EQLZ=<eqlz>],[FMT=<fmt>],

[LINECDE=<linecde>],[OMODE=<omode>],[TMGREF=<tmgref>],

[IFTYPE=<iftype>]:[<pst>],[<sst>];

Example: ENT-E1::SHELF-0-ACM-3-AMCSS7-1-E1-2:::FMT=DF,LINECDE=HDB3,

OMODE=NORM,IFTYPE=NETWORK:OOS;

...................................................................................................................................................................................................

5 Verify the line entry by using the RTRV-T1 command.

Example RTRV-T1::SHELF-0-ACM-3-AMCSS7-1-T1-1;

Example: RTRV-E1::SHELF-0-ACM-3-AMCSS7-1-E1-2;

...................................................................................................................................................................................................

6 Put the port in loopback by issuing the OPR-LPBK-T1 or OPR-LPBK-E1 command with

the parameters for your loopback.

Syntax: OPR-LPBK-T1/E1:[TID]:<lpbk_id>:[CTAG]::[<locn>],[<orgn>],

[<intext>],[<lpbktype>];

Example: OPR-LPBK-T1::SHELF-0-ACM-3-AMCSS7-1-T1-1;

Example: OPR-LPBK-E1::SHELF-0-ACM-3-AMCSS7-2-E1-1;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

7 Connect the test patch cables at the test set and at the cross-connect for the port to be

tested.

• Connect the test set transmit (TX) output jack to the channel IN jack at the

cross-connect.

• Connect the test set receive (RX) input jack to the channel OUT jack at the

cross-connect.

...................................................................................................................................................................................................

8 Configure the test set transmission controls according to the customer's policy for testing

T1 or E1 ports. Reference the test set's manual.

...................................................................................................................................................................................................

9 Did the test set run error free for the time specified by the customer's policy for the T1 or

E1 line?

IF . . . THEN . . .


NO Verify port settings and cabling and go to Step 7.

...................................................................................................................................................................................................

10 Note: You can only release a loopback with the same locn and lpbktype as the

loopback that was initiated with the OPR command. If you issue the

OPR-LPBK-T1::XX:::FEND,,,LINE; command, you must use the

RLS-LPBK-T1::XX:::FEND,,,LINE; command to release the loopback, notRLS-LPBK-T1::XX:::NEND,,,LINE;.

Release the T1 or E1 loopback using the RLS-LPBK command.

Syntax: RLS-LPBK-T1/E1:[TID]:<lpbk_id>:[CTAG]::[<locn>],[<orgn>],

[<intext>],[<lpbktype>];

Example: RLS-LPBK-T1::SHELF-0-ACM-3-AMCSS7-1-T1-1;

Example: RLS-LPBK-E1::SHELF-0-ACM-3-AMCSS7-2-E1-1;

...................................................................................................................................................................................................

11 Do you want to loop another port?

IF . . . THEN . . .

YES Go to Step 6.



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-13



...................................................................................................................................................................................................

12 Do you want to provision the T1s or E1s?

IF . . . THEN . . .

YES Go to the Rapport MGC-8 ATCA Operations Guide, 255-400-000, Part IX:

Provisioning a MGC-8/VSG, Chapter 75, Provisioning Modules of a MGC-8.

NO Go to “What’s next” (p. 9-19).


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Check the management/signaling interface duplex setting

Before you begin

Use this procedure after the ATCA is connected to the network.

Check the MGC-8 management and/or signaling interface

Note: Management and signaling interfaces are defined by ED-ATCA-CHASSIS in

the section "Growth and provisioning of ALGPv2 blades."

Use the following procedure to verify that the MGC-8 management or signaling interface

is set to full duplex mode.

...................................................................................................................................................................................................

1 Log in to the interface.

Example:

<mgc8-s00c01h0:root>/root:# ssh mgc8-s00c07h0-1

Last login: Tue Apr 10 07:21:30 2012 from 169.254.32.16

Linux 2.6.10_mvlcge401-pc_target-x86_pentium3 #7 SMP Mon Oct 17 10:54:12

Welcome to MontaVista(R) Linux(R) Carrier Grade Edition 4.0 (0600995)

root@mgc8-s00c07h0:~#

...................................................................................................................................................................................................

2 Telnet to port 2000 of the interface. Only one telnet session to port 2000 is allowed at one

time.

Example:

root@mgc8-s00c07h0:~# telnet localhost 2000

Trying 127.0.0.1...

Connected to localhost.localdomain.

Escape character is '^]'.

expander>

...................................................................................................................................................................................................

3 If FRONT_GEX is used as the management or signaling interface, switch to the “base>”

prompt. If REAR_GEX is used, switch to the “expander>” prompt.

Note: The “expander>” prompt is the default prompt for “telnet localhost 2000.” The

prompt does not need to be changed if the management and signaling interfaces are on

REAR_GEX.Example1:

expander>2:

base>

Example2:

base>0:

expander>

Provisioning of ALGPv2 blades Check the management/signaling interface duplex setting

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-15



...................................................................................................................................................................................................

4 Use “ps” to list the interfaces' status, then check the “speed/duplex” column of the

management and signaling interfaces. If any of them are set to half duplex mode, please

contact Technical Support. If not, go to Step 1 to check another interface. If both

interfaces have been checked, go to Step 6.

The ps command output is as follows:

Table 9-1 Port to physical interface mapping

Port Physical interface

ge11 FRONT_GE0

ge10 FRONT_GE1

ge8 FRONT_GE3

ge0 REAR_GE0

ge1 REAR_GE1

ge2 REAR_GE2

ge3 REAR_GE3

ge6 REAR_GE4

Example:

expander>ps

ena/ speed/ link auto STP lrn inter max

port link duplex scan neg? state pause discrd ops faceframe

ge0 up 100M FD SW Yes Forward TX RX None FA SGMII 1518

ge1 down - SW Yes Forward TX RX None FA SGMII 1518

ge2 up 100M HD SW Yes Forward None FA SGMII 1518






ge8 down 1G FD SW Yes Forward TX RX None FA GMII 1518





ge13 !ena 1G FD SW Yes Forward TX RX None FA GMII 1518





....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015









ge23 !ena 1G FD SW Yes Forward TX RX None FA GMII 1518xe0 up 10G FD SW No Forward None FA XGMII 16356

xe1 !ena 10G FD SW No Forward None FA XGMII 16356

Note: ge2 (REAR_GE2) is in half duplex (HD) mode in the previous example.

...................................................................................................................................................................................................

5 Exit from telnet and ssh.

Example:

expander>exit

Connection closed by foreign host.

root@mgc8-s00c07h0:~#

root@mgc8-s00c07h0:~# exitlogout

Connection to mgc8-s00c07h0-1 closed.

<mgc8-s00c01h0:root>/root:


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-17

E N D O F S T E P S...................................................................................................................................................................................................



Check the network IP address of the MGC-8 and other NEswith which it communicates

Before you begin

Note: Telneting for TL1 access is denied from anywhere outside the local boardunless the SYS-SECUcommand parameter telnetAccess is set to Y. It is set to N by

default. The user must first SSH ( ssh <hostname> ) to the ACCM blade, and then

run “telnet localhost 2361" or “telnet 0 2361” to access TL1. Then the user can log on

using the ACT-USER command.

Check the network IP address(s)

...................................................................................................................................................................................................

1 Check the IP address and network mask of the management/signaling interface on each

ACCM and ADCM with RTRV-ATCA-EQPT.

...................................................................................................................................................................................................

2 Check the IP address of other NEs with which MGC-8 communicates.

...................................................................................................................................................................................................

3 Does the NE stay in the same subnet with the management or signaling interface?

IF . . . THEN . . .


NO Continue to theWhat's Next? section that follows.

...................................................................................................................................................................................................

4 Use TL1 to provision an extra route for each pair of ACCM and ADCM using

theENT-IPROUTEcommand.

For example, if the ACCM has the following output,:

SHELF-0-ACM- 2:VIRTUALSLOT=2,MODULETYPE=3CM03285JB,SWVERSION=

9.1.0.1.SP.2,CARDTYPE=ACCM,REDUNDANCY=DX,POOLID=1,MEMTHRESHOLD=

90,NVMEMTHRESHOLD=70,DISKMAJORTHRESHOLD=85,DISKCRITICALTHRESHOLD=

95,BUSYTHRESHOLD=85,EMIPV4FIXED=192.168.xxx.xxx,EMIPV4FLOATING=192.168.xxx.xxx,EMIPV4NTWKMASK=28,EMFAILOVERTMR=180,

SIGAIPV4FIXED=10.84.17.130,SIGAIPV4FLOATING=10.84.17.131,

SIGAIPV4NTWKMASK=27,SIGAFAILOVERTMR=180,SIGBIPV4FIXED=

10.84.17.162,SIGBIPV4FLOATING=10.84.17.163,SIGBIPV4NTWKMASK=27,

SIGBFAILOVERTMR=180,SIGCIPV4FIXED=10.84.16.114,SIGCIPV4FLOATING=

10.84.16.115,SIGCIPV4NTWKMASK=28,SIGCFAILOVERTMR=180,

Provisioning of ALGPv2 blades Check the network IP address of the MGC-8 and other NEswith which it communicates

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



SIGDIPV4FIXED=NULL,SIGDIPV4FLOATING=NULL,SIGDIPV4NTWKMASK=0,

SIGDFAILOVERTMR=180,SIGAIPV6FIXED=NULL,SIGAIPV6FLOATING=NULL,

SIGAIPV6NTWKPREFIX=0,SIGBIPV6FIXED=NULL,SIGBIPV6FLOATIN G=NULL,

SIGBIPV6NTWKPREFIX=0:IS,ACT

And, the NE stays in the same subnet with the management interface, which is

192.168.xxx.xxx/xxx, then the following command is

needed:ENT-IPROUTE::SHELF-0-ACM-1-192.x.x.x- 8:::GATEWAY=

192.168.xxx.xxx,GATEWAYPING=ENABLED;

Note: The Gateway IP address should be in the same subnet as MGC-8 management

interface and must be accessible.

...................................................................................................................................................................................................

5 Exit from telnet and ssh.

Example:

expander>exit

Connection closed by foreign host.root@mgc8-s00c07h0:~#

root@mgc8-s00c07h0:~# exit

logout

Connection to mgc8-s00c07h0-1 closed.

<mgc8-s00c01h0:root>/root:

What’s next

Final activities

Proceed to the next chapter to complete the final activities required for the field

installation.

Provisioning of ALGPv2 blades Check the network IP address of the MGC-8 and other NEswith which it communicates

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



9-19

E N D O F S T E P S...................................................................................................................................................................................................



Provisioning of ALGPv2 blades What’s next

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



10 10Final activities

Overview

Purpose

This chapter provides the procedures to follow for the final activities and graceful

shutdown.

Contents

Introduction 10-1

Final activities 10-2

Graceful shutdown 10-5

What’s next? 10-6

Introduction

Installation sequence

Prior to executing the procedures in this chapter, be sure that you have read and

completed all of the procedures defined in the chapters leading up to this one. For a

successful installation, it is important that the installation process is completed in the

proper sequence.

...................................................................................................................................................................................................................................



10-1



Final activities

Important! The spanning tree feature is not supported in the current ALGPv2

product. Using this type of protocol will cause port failure. Therefore, the ports on the

equipment that connects to the hub cards must have the spanning tree protocol

disabled!

Complete the field installation

The procedures in this section take approximately 5-10 minutes to execute.

...................................................................................................................................................................................................

1 Complete the following steps to complete the field installation.

...................................................................................................................................................................................................

2 Disconnect the Ethernet and serial cable from blade 1.

...................................................................................................................................................................................................

3 Connect the cables from the customer network to the appropriate ports in the hubs.

...................................................................................................................................................................................................

4 Connect the cables to the Base T port on the hubs (port x10) for SOL and SSH.

...................................................................................................................................................................................................

5 Congratulations! You have successfully field-installed the LCP and ALGPv2 software.

Please note the following:

• The SOL for the blades with OAM server functionality have been configured and

activated as part of this procedure. Refer to Appendix D for usage information.• Refer to the Release Notes to see if any additional steps are needed.

Resetting the laptop and removing the exception from the browser

This section provides instructions that will enable you to reset the laptop back to its

original settings.

...................................................................................................................................................................................................

1 Open an IE browser window.

...................................................................................................................................................................................................

2 Go to Tools > Internet Options ....

Final activities Final activities

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



...................................................................................................................................................................................................

3 Select the Connections tab on the Internet Options window, and click on the LAN

Settings ... button.

...................................................................................................................................................................................................

4 Click on the Advanced button on the Local Area Network (LAN) Settings window....................................................................................................................................................................................................

5 Locate the Exceptions section at the bottom of the screen on the Proxy Settings window

and remove the 169* entry, then click on OK.

...................................................................................................................................................................................................

6 Click on OK on the Local Area Network (LAN) Settings window.

...................................................................................................................................................................................................

7 Click on OK on the Internet Options window.

Removing static IP from the laptop

The following procedure will undo the setting changes that you performed in the

“Mandatory prerequisite procedures” (p. 3-1) of Chapter 3, “Prepare for the LCP

installation” and will enable you to reset the laptop back to its original settings.

...................................................................................................................................................................................................

1 Click on Start > Settings > Network Connections....................................................................................................................................................................................................

2 On the Network Connections window, right click on Local Area Connection and then

click on Properties.

...................................................................................................................................................................................................

3 On the Local Area Connection Properties window, scroll down and click on Internet

Protocol (TCP/IP) Properties and then click on Properties.

...................................................................................................................................................................................................

4 On the Internet Protocol (TCP/IP Properties window, click on the Use an IP addressautomatically radio button, then click on OK.

...................................................................................................................................................................................................

5 Back on the Local Area Connection Properties window, click on OK.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



10-3

E N D O F S T E P S...................................................................................................................................................................................................

E N D O F S T E P S...................................................................................................................................................................................................





g. Remove the two “Primary Partitions.”: Place the cursor on the either of the “Primary

Partition” and then right-click. Select “Delete Partition…” and answer Yes.

h. Right-click on remaining partition (Unallocated) and select “New Partition …” A new

“New Partition Wizard” window appears.

i. Accept all defaults by clicking “Next” (5 times) and then “Finish”. The USB drive will

now be reformatted back to the earlier format.

Graceful shutdown

Power management

If you need to power down the system (for example, because you staged the customer

system in a different location and you now need to power it off for shipment to the

customer), it must be done in a graceful and orderly manner. Please refer to the Power

Management chapter of the Alcatel-Lucent 5400 Linux Control Platform Hardware

Maintenance, 270-702-030 manual for instructions on how to perform this operation.

Please refer to the related customer documentation for instructions on how to perform this

operation.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



10-5

E N D O F S T E P S...................................................................................................................................................................................................



What’s next?

Upgrade scenarios

If you need to remove blades from the chassis, refer to Chapter 8, “Growth and de-growth

of ALGPv2 blades”. If you need to upgrade or patch the software, refer to Chapter 11,“Upgrade scenarios and procedures”.

Final activities What’s next?

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



11 11Upgrade scenarios and

procedures

Overview

Purpose

This chapter describes the various upgrade scenarios applicable to upgrading LCP and

ALGPv2 software on the MGC-8. Additionally, it provides the procedures necessary tocomplete each type of upgrade.

If you are upgrading both LCP and ALGPv2, software, you will perform the “Upgrade

both the LCP software and the ALGPv2 software” (p. 11-6) procedure. If you are

upgrading ALGPv2 only, refer to the "Upgrade the ALGPv2 software" section.

If you are upgrading only the ALGPv2, software, you will perform the “Upgrade the

ALGPv2 software” (p. 11-15) procedure.

If you are performing a cold upgrade, you will use an offline database conversion tool to

perform the cold upgrade. Refer to the “Cold upgrade LCP and ALGPv2 software”

(p. 11-20) procedure.

Upgrade notes

Note: When performing a hot upgrade from R8.3.0 and higher, stop supervision for

the MGC-8 Network Element from the COM prior to the upgrade. Once the upgrade

is complete and before restarting supervision, check that the correct versions of LCP

and MGC-8 are selected, and supervision.

Note: This chapter contains a number of Software Installation Manager (SIM) step

examples. The actual number of SIM steps required may vary depending on the

configuration.

Contents

Upgrade scenarios 11-2

Upgrade requirements 11-2

...................................................................................................................................................................................................................................



11-1



Downloading and upgrading NE software using the COM GUI 11-3

Provisioning support during upgrade when GR MGC-8s are on different

releases

11-4

Upgrade both the LCP software and the A LGPv2 software 11-6

Upgrade the ALGPv2 software 11-15

Cold upgrade LCP and ALGPv2 software 11-20

Upgrade scenarios

LCP and ALGPv2 upgrade scenarios

The MGC-8 software comprises both the LCP base platform and the ALGPv2 software.

Depending on how the LCP software is to be upgraded, the following upgrade scenarios

are possible.• Scenario 1 — Both the LCP base platform software and the ALGPv2 software

require upgrade. Complete “Upgrade both the LCP software and the ALGPv2

software” (p. 11-6).

• Scenario 2 — Only the ALGPv2 software requires an upgrade. Complete “Upgrade

the ALGPv2 software” (p. 11-15) procedure.

• Scenario 3 — Both software releases requires a cold upgrade. Complete “Cold

upgrade LCP and ALGPv2 software” (p. 11-20) procedure.

Upgrade requirements

Upgrade sequence and LCP software format

Blade with OAM server functionality must be updated prior to performing an upgrade of

ALGPv2 blades. The LCP side provides the script or API to update the LCP base platform

software on the application service hosts. All scripts will be run on the blade with OAM

server B functionality.

The LCP software versions follow the format of Rrr.xx.yy.zz where:

• rr is the Release number

• xx is the Major number

• yy is the Minor or Maintenance number

• zz is the Patch or Sub number

The upgrade procedures in this chapter assume that you are upgrading to the LCP version

for this release and ALGPV2.ATCA.9.X.X.X or greater. Refer to the MGC-8 System

Release Notes for the LCP release number.

Upgrade scenarios and procedures Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Downloading and upgrading NE software using the COM GUI

Prerequisites

The COM GUI can be used to download the LCP and ALGPv2 software. Refer to the

COM NE Software and Data Management User Guide part number 255-400-462 for information.

Before performing a software upgrade from the COM GUI, the following tasks must be

performed and verified:

1. Verify that the rmtadm account was created successfully on the MGC-8 OAM Server

B.

2. Verify that the SSH configuration task was performed successfully. Refer to Appendix

D in the COM NE Software and Data Management User Guide for information on

how to configure SSH to support communication between the following accounts

without a password: COM:root -> OAM Server B:rmtadm and

OAM Server B:rmtadm -> COM:sxmcftp

Download software from the COM repository server

Procedures for downloading the LCP and ALGPv2 software using the COM GUI can be

found in the COM NE Software and Data Management User Guide.

Once the download is complete, go to the /storage/loads directory on OAM Server

B to verify that the software was downloaded.

Upgrade the software using the COM cut through window

Perform the following tasks to upgrade the LCP and ALGPv2 software:1. From the COM cut-through window, log in as rootto OAM Server B.

2. Unmanage or stop supervision for the MGC-8 network element from the COM before

upgrading LCP and ALGPv2.

3. Use the upgrade procedures described in the following paragraphs to upgrade your

software.

Upgrade scenarios and procedures Downloading and upgrading NE software using the COM GUI

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-3





Provisioning through the TL1 Craft interface

TL1 commands not in DNR list

• When provisioning TL1 commands on the active side through the TL1 craft interface

in active-active GR or active-standby GR mode, the TL1 must be replicated to the

peer switch.

– Provisioning TL1 commands through the TL1 craft interface while the peer switch

is unreachable, causes replication to fail. Provisioning is successful on one side by

default. Run the GR difference to resolve the difference after the peer switch is

reachable.

Note: When the GR pair is on a different release, the replication fails if the TL1

entered on the switch is not accepted by its peer switch. Roll back does not occur

when replication fails.

– Provisioning TL1 commands through the TL1 craft interface while the switch is

not synchronized on COM , results in provisioning operations not reflecting on

COM, even if the operations are successful on the TL1 craft interface. The

replication will not occur either.

– Provisioning TL1 commands through the TL1 craft interface while the switch is

synchronized, results in the provisioning operations reflecting on COM and the

replication is also successful.

• The TL1s are not replicated to the peer side when provisioning on the standby switch

in the active-standby GR is through the TL1 craft interface.

TL1s in the DNR list

• The TL1s are not replicated to the peer side.

Scenarios that do not support Rollback

• TL1 is entered through the TL1 craft interface

• Bulk-download operation

– When the GR pair is on a different release, it is not recommended to do a

bulk-download on COM. Using a lower release TL1 format in bulk-download

script may result in a successful replication. When doing bulk-download on the

active switch in active-active GR mode or active-standby GR mode, if the TL1s in

the script are not accepted by the peer switch, the replication fails.

• Special TL1 commands. Large data with bulk operation on COM does not support roll

back.

– ED/DLT-SS7-TRK, ED/DLT-CAS-TRK, ED/DLT-BICC-TRK, ED/DLT-IVT

with more than 1 record

Upgrade scenarios and procedures Provisioning support during upgrade when GR MGC-8s are ondifferent releases

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-5



Upgrade both the LCP software and the ALGPv2 software

Upgrade Scenario 1

Complete the following procedures to upgrade both the LCP base platform software and

the ALGPv2 software (Scenario 1).Note: Telneting for TL1 access is denied from anywhere outside the local board




ACT-USER command.

An acceptance test plan should have been created. An acceptance test plan contains tests

required to validate a successful update. The scope and/or capabilities covered by the test

are left to the discretion of the user. The test plan should be broad enough to ensure that

all functions will work prior to and after the update.

Stage the server

Attention: Software Evolution Key for Upgrading the LCP Platform Software

A hot upgrade evolution key is required for an LCP platform software upgrade. This

key is not required for the initial field installation of LCP software. The evolution key

is also not needed when the first six digits of the LCP platform software version do

not change. For example an upgrade from 25.15.31.05 to 25.15.31.06 will not require

an evolution key.

Evolution key information is available in QDI document 52114. You must know the

LCP version from which you are upgrading and the version to which you areupgrading to determine the required key.

Attention: Software License for the ALGPV2 Software

A software license is required to use the ALGPV2 software. Information on how to

obtain a software license is described in Appendix G: Software License Key Delivery

Infrastructure (LKDI).

Complete the following steps to stage the server for the upgrade.

...................................................................................................................................................................................................

1 As root, FTP the LCP/ALGPV2/DEFT zip files to the /storage/loads directory on theMI-B (OAM Server B). Use the latest version.

If you need to download the files, refer to Chapter 1, “System requirements”, “Installing

the MGC-8 software” (p. 1-5) for directions.

Upgrade scenarios and procedures Upgrade both the LCP software and the ALGPv2 software

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Note: The LCP software upgrade tool requests that only the files listed below for the

current upgrade be present in the /storage/loads directory on MI-B. If multiple

monolithic zip files are found for either LCP or ALGPv2, the LCP software upgrade

script will fail and request a clean up of the extra files.

Files to download:

• 9-X-X-X for MGC-8 , (ALGP9XXXX.tar.zip which must be unzipped to obtain

ALGPV2.ATCA.9.X.X.X.X.zip)

• ATCA.RXX.XX.XX.XX (ATCA.LCPXX.XX.XX.XX.zip)

• ATCA.DEFT.RXX.XX.XX.XX (See following.)

• The MGC-8 Software License file (MGC8LicenseFile.txt), which is optional at this

stage but recommended.

The deft or deftC file to be used depends upon the upgrade path. If you are upgrading

from

• One major release to the next one, such as:

– R24.26.XX to R25.15.XX, you will need the . deft_R24.26.XX_R25.15.XX,.zip

file.


file.


file.

– R24.21.XX to R25.15.XX, you will need the deftC_R24.21.XX_R25.15.XX.zip

file.

• A minor release or patch such as:

– R25.15.XX, to R25.15.XX,, you will need the deft_R25.15.XX,_R25.15.XX,.zipfile.


file.


file.


file.


file.

– The MGC-8 Software License file (MGC8LicenseFile.txt), which is optional at

this stage but recommended.

...................................................................................................................................................................................................

2 Verify the blade with OAM server B functionality is standby by entering the following

command.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-7



MIcmd state vc

> MIcmd state vc

state of MI virtual cluster is A - Active

state of MI host primary virtual machine is A - Active

state of MI host alternate virtual machine is S - Standby

...................................................................................................................................................................................................

3 Is the blade with OAM server B functionality in Standby?

IF . . . THEN . . .


NO Enable an MI switchover by entering the following.

MIcmd switch vc

...................................................................................................................................................................................................

4 Log into MI-B (the blade with OAM server B functionality) as root.

...................................................................................................................................................................................................

5 Verify the health of the system.

health --test all

...................................................................................................................................................................................................

6 Backup the LCP system on MI-B as follows.

bkup_system

...................................................................................................................................................................................................

7 Are you logged in to use TL1?

IF . . . THEN . . .


NO In a second window, log into MI-B as root.

Then from the OS of the active ACCM blade and enter the following:


TL1.Then log on using the ACT-USER command.

...................................................................................................................................................................................................

8 Verify the chassis type is ATCA_VSG_MGC or ATCA_MGC, as follows:

rtrv-atca-chASSIS;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



M 0 COMPLD

"COM:CHASSISTYPE=ATCA_VSG_MGC,CLLI=NULL,LOC=NULL,SIGAPORT=REAR_GE1,SIGBPORT=REAR_GE2,SIGCPORT=REAR_GE3,SIGDPORT=REAR_GE4,EMPORT=FRONT_ GE0,DNSIP1=NULL,DNSIP2=NULL,DNSNAME=NULL,EMTOS=NULL,SIGATOS=NULL,SIGBTOS=NULL,SIGCTOS=NULL,SIGDTOS=NULL,UPGRADESTATE=NORMAL,INTERNALBTS=N,SIGAIPV4DFLTGW=NULL,SIGAIPV4GWPING=DISABLED,SIGAIPV6DFLTGW=NULL,SIGAIPV6GWPING=DISABLED,SIGBIPV4DFLTGW=NULL,

SIGBIPV4GWPING=DISABLED,SIGBIPV6DFLTGW=NULL,SIGBIPV6GWPING=DISABLED,SIGCIPV4DFLTGW=NULL,SIGCIPV4GWPING=DISABLED,SIGDIPV4DFLTGW=NULL,SIGDIPV4GWPING=DISABLED,EMIPV4DFLTGW=NULL,EMIPV4GWPING=DISABLED,SYSTEMID=BS0915U09SU,SIGCIPV6DFLTGW=NULL,SIGCIPV6GWPING=DISABLED,SIGDIPV6DFLTGW=NULL,SIGDIPV6GWPING=DISABLED,EMIPV6DFLTGW=NULL,EMIPV6GWPING=DISABLED"

/* RTRV-ATCA-CHASSIS */

If the chassis type is not ATCA_VSG_MGC or ATCA_MGC, stop the HUG procedure

and change your chassis type.

...................................................................................................................................................................................................

9 Verify that the IP filter is disabled.

rtrv-sys-seCU

M 0 COMPLD

"COM:MAXINV=5,DURAL=0-0-30,TMOUT=30,PRELOGINTIMEOUT=2,PASSWDEXPALERT=7,PASSWDCHGFREQ=20-HR,HEARTBEAT=0,TCPCONNENABLED=Y,ALMQPORT=2363,

ALMQTMO=0,EMPORT=2362,EM1IP=NULL,EM2IP=NULL,IPFLTRENABLED=N,EVENTINTERVAL=150,XFERPRTCL=SFTP,TL1INTRUSIONPOLICY=BLOCK&FREEZE,TL1PASSWDMAXREUSE=6,TL1PASSWDCOMPLX=ENHANCED,TELNETACCESS=N,ACTTMOUT=0,INACTIVELOG=60,PASSWDMAXCHARREPEAT=1,PASSWDMAXCHARUID=2,PASSWDMAXCHARPREVPWD=3,PASSWDMAXCHARSEQ=2,PASSWDMINLEN=8,PASSWDMINLOWERCASE=1,PASSWDMINUPPERCASE=1,PASSWDMINDGTS=1,PASSWDMINSPECIAL=1,AUTHPOLICY=LOCAL-LOCAL,IPFLTRCONNTRACK=Y,MAXSES=1"

/* RTRV-SYS-SECU */

If the IPFLTRENABLED parameter is not N, use TL1 to change it to N.ed-sys-seCU:qd08::100:: IPFLTRENABLED=N;

...................................................................................................................................................................................................

10 Verify prompt mode for TL1 is enabled. Verify that ED-SYS-TL1 PROMPTMODE=Y. To

ensure the upgrade completes successfully, the SIM tool needs to have PROMPTMODE=Y

(ESC key required to invoke the telnet session).

Telica> RTRV-SYS-TL1; 5060mgc8_2 2014-03-28 09:24:44

M 0 COMPLD

"COM:TLNTCNTRLOPT=Y,PROMPTMODE=Y"

/* RTRV-SYS-TL1 */ ;;

If the PROMPTMODE=N, enter the following command to set PROMPTMODE=Y:ED-SYS-TL1:::::PROMPTMODE=Y;

...................................................................................................................................................................................................

11 Verify any scheduled backup is disabled.

RTRV-BKUPSCHED-EQPT

M 0 COMPLD


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-9



"COM:24-HR,09-23,22-30,30"

/* RTRV-BKUPSCHED-EQPT */

;

Telica> SCHED-BKUP-EQPT:::::::24-HR,0-1,22-30,30;

If a scheduled backup is not disabled, use TL1 to disable it

SCHED-BKUP-EQPT:::::::24-HR,0-1,0-0,30;...................................................................................................................................................................................................

12 Verify there are no outstanding alarms.

rtrv-alm-ALL;

If there are outstanding alarm, evaluate and clear them as necessary. Refer to the Rapport

MGC-8 ATCA Alarms and Troubleshooting Procedures Guide , 255-400-019 for alarm

clearing information.

...................................................................................................................................................................................................

13 Verify there are no outstanding conditions.

rtrv-conD-ALL;

If there are outstanding conditions, evaluate and clear them as necessary. Refer to the

Rapport MGC-8 ATCA Alarms and Troubleshooting Procedures Guide, 255-400-019 for

condition clearing information.

...................................................................................................................................................................................................

14 Verify if a scheduled exercise is inhibited.

RTRV-EXSCHED-EQPT:qd08:shelf-0-acm-3;

M 0 COMPLD

"SHELF-0-ACM-3:0-HR,0-0,0-0,,ALL,SWTOPROTN,ALW"

/* RTRV-EXSCHED-EQPT */

If a scheduled exercise is allowed, use TL1 to change it to inhibited.

inh-ex-EQPT:qd08:shelf-0-acm-3;

...................................................................................................................................................................................................

15 Run the following TL1 command to back up the ALGPv2 data.

Syntax: EXEC-BACKUP-CFG:[<TID>]:[<src>]:[CTAG]::<desthost>,

<username>,<password>,<destdir>,[<suppressoutput>],

[<tmout>],[<xferPrtcl>];

Note: The following is an example. You should use the correct values for your application.

Example: EXEC-BACKUP-CFG:::::192.168.xxx.xxx,root,newsys,/home,,,

ftp;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

16 Note: This step should be executed on MI-B while logged in as root.

Determine if CPM is enabled by entering the following command.

cpmconf_adm --action show_activated

...................................................................................................................................................................................................

17 Was 'CPM activated = 1' displayed?

IF . . . THEN . . .

YES Continue to the next step,

NO On the active the blade with OAM server functionality, enable cpm by entering

the following commands.

scdw_adm --action pre_enable_cpm

scdw_adm --action enable_cpm

...................................................................................................................................................................................................

18 Run the LCP pre-install procedure under /storage/loads on MI-B.

zipinstall /storage/loads/ATCA.LCPXX.XX.XX.XX.zip --action

update_setup

Update the server

Update the blade with OAM server B functionality (MI-B) as follows:

...................................................................................................................................................................................................

1 Run the disk procedure as follows.

sim --proc update --action apply

The following message appears.

Ready to 'apply' the sim 'update' procedure from the beginning:

Continue? (y/n)Press y to continue

...................................................................................................................................................................................................

2 Follow the sim log for progress. The sim has a manual pause point for verify start.

Run the following.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-11

E N D O F S T E P S...................................................................................................................................................................................................



tail -f /storage/sim/log/update/sim.log

During this step, MI will reboot. Re-login to MI-B and continue to tail the sim log.

Open a second window for MI-B.

Note: The log might show that SIM aborted due to a MGC-8 health check failure. In

such cases customers need to evaluate the failure carefully. If a customer decides to goahead with the software upgrade despite the health check failure, they should run the

following command and then resume SIM.

/storage/su_backup/LSS/Rxxxx/su/ALGPV2/sbin/mtce_mgc8 --

action ignore_alarm (Rxxxx is higher version of LCP which you

upgrade to)

...................................................................................................................................................................................................

3 Follow the sim log for progress. Refer to the following table for pause points. Where

noted, in the second window, enter sim --proc update --action resume. This

command needs to be entered twice for there will be two pause message for resume.

Pause messages Action

MI-B rebooting SIM will automatically resume.

PAUSE_REQUEST: (PROCEDURE)

[PAUSE(CP_WARNING): Use 'sim --

proc update --action resume'

to continue...]

Resume SIM,

type:sim --proc update --action resume

in the SIM ProcessWindow

PAUSE_REQUEST: (PROCEDURE)

[PAUSE(VERIFY_SOFTWARE): Use

'sim --proc update --actionresume' to continue...]

Perform the following steps.

1. SOAK TESTING: SIDE-B service hosts.

Perform any soak/sanity tests contained in theAcceptance Test Plan to verify that the

capabilities provided by the components

running on the new release function as

expected.

2. When the above manual procedures are done,

resume SIM by entering

sim --proc update --action resume

in the SIM ProcessWindow

Firmware Update triggering MI-

B rebooting

SIM will automatically resume.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Pause messages Action

PAUSE_REQUEST: (COMMIT) *

Ready to Commit the 'Update'

and update the ShMC and Hubs!

Perform the following steps.

1. SOAK TESTING: All service hosts and

duplex network boot hosts.

Perform any soak or sanity tests contained in

the Acceptance Test Plan to verify that the

capabilities provided by the components

running on the new release function as

expected. If, after acceptance testing, it is

desired to back out of the Software Update,

proceed immediately to the Software Backout

section.

2. When acceptance testing is complete, the

Software Update can be permanently installed

(made official). To make the Software Update

official, continue with the commit.

Commit the server update

Complete the following steps to commit the upgrade (make the software upgrade official).

...................................................................................................................................................................................................

1 Continue to follow the sim log in the first window till the following pause message

appears.

SIM328 PAUSE_REQUEST: (COMMIT) [PAUSE(COMMIT): Use 'sim --procupdate --action

commit' to continue...]

PAUSED: (COMMIT) Dispatched commands are complete.


...................................................................................................................................................................................................

2 Then run get_version to verify that MI-B (the blade with OAM server B functionality) is

on the new LCP load.

get_version --display mi_b


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-13

E N D O F S T E P S...................................................................................................................................................................................................



...................................................................................................................................................................................................

3 Is the new version correct?

IF . . . THEN . . .

YES Continue to the next step,

NO Contact Technical Support.

...................................................................................................................................................................................................

4 In the second window, run sim --proc update --action commit

This will boot MI-A (the blade with OAM server A functionality) to the new LCP load.


Ready to 'commit' the sim 'update' procedure:

Continue? (y/n)...................................................................................................................................................................................................

5 Continue to follow the sim log in the first window till the following pause message

appears.

SIM342 [ALL SIM update STEPS HAVE COMPLETED!] (update:1996)

COMPLETED SIM PROCEDURE 'update commit' type=hot


...................................................................................................................................................................................................

6 Stop. You have completed upgrading both the LCP software and the ALGPv2 software.

Refer to the COM and MGC-8 Configuration Management User Guide, 255-400-400 the“Manage an Element after Upgrade” section for additional configuration information.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Upgrade the ALGPv2 software

Introduction

Note: Upgrades

• If you upgraded both the LCP and ALGPv2 software, you can stop here, because both the LCP and ALGPv2 software were upgraded in the “Upgrade both the LCP

software and the ALGPv2 software” (p. 11-6) procedures.

• If you are upgrading ALGPv2 software only, you need to complete the following

procedures.

Preparing for the upgrade

...................................................................................................................................................................................................


...................................................................................................................................................................................................

2 Verify that MI-B is in standby mode, as follows.

MIcmd state vc

> MIcmd state vc




If not, perform a switchover by entering the following command:

MIcmd switch vc

...................................................................................................................................................................................................

3 FTP the MGC-8 Software License file MGC8LicenseFile.txtto the /storage/loads

directory on MI-B. This step is optional but highly recommended.

...................................................................................................................................................................................................

4 FTP the monolithic zip file ALGPV2.ATCA.x.x.x.x.zip to the /storage/loads directory on

MI-B and complete the following procedure.

...................................................................................................................................................................................................

5 Run the following procedure to zip install the ALGPV2 load onto both MIs.

appl_setup --action pre_install

Upgrade scenarios and procedures Upgrade the ALGPv2 software

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-15



...................................................................................................................................................................................................

6 Are you logged in to use TL1?

IF . . . THEN . . .


NO From the OS of the active ACCM blade and enter the following:


TL1.


...................................................................................................................................................................................................

7 Verify the chassis type is ATCA_VSG_MGC or ATCA_MGC, as follows:

rtrv-atca-chASSIS;

M 0 COMPLD

"COM:CHASSISTYPE=ATCA_VSG_MGC,CLLI=NULL,LOC=NULL,SIGAPORT=REAR_GE1,SIGBPORT=REAR_GE2,SIGCPORT=REAR_GE3,SIGDPORT=REAR_GE4,EMPORT=FRONT_ GE0,DNSIP1=NULL,DNSIP2=NULL,DNSNAME=NULL,EMTOS=NULL,SIGATOS=NULL,SIGBTOS=NULL,SIGCTOS=NULL,SIGDTOS=NULL,UPGRADESTATE=NORMAL,INTERNALBTS=N,SIGAIPV4DFLTGW=NULL,SIGAIPV4GWPING=DISABLED,SIGAIPV6DFLTGW=NULL,SIGAIPV6GWPING=DISABLED,SIGBIPV4DFLTGW=NULL,SIGBIPV4GWPING=DISABLED,SIGBIPV6DFLTGW=NULL,SIGBIPV6GWPING=DISABLED,SIGCIPV4DFLTGW=NULL,SIGCIPV4GWPING=DISABLED,SIGDIPV4DFLTGW=NULL,SIGDIPV4GWPING=DISABLED,EMIPV4DFLTGW=NULL,EMIPV4GWPING=DISABLED,SYSTEMID=BS0915U09SU,SIGCIPV6DFLTGW=NULL,SIGCIPV6GWPING=DISABLED,SIGDIPV6DFLTGW=NULL,SIGDIPV6GWPING=DISABLED,EMIPV6DFLTGW=NULL,EMIPV6GWPING=DISABLED"

/* RTRV-ATCA-CHASSIS */

If the chassis type is not ATCA_VSG_MGC or ATCA_MGC, stop the HUG procedureand change your chassis type.

...................................................................................................................................................................................................

8 Verify IP filter is disabled.

rtrv-sys-seCU

M 0 COMPLD

"COM:MAXINV=5,DURAL=0-0-30,TMOUT=30,PRELOGINTIMEOUT=2,PASSWDEXPALERT=7,PASSWDCHGFREQ=20-HR,HEARTBEAT=0,TCPCONNENABLED=Y,ALMQPORT=2363,

ALMQTMO=0,EMPORT=2362,EM1IP=NULL,EM2IP=NULL,IPFLTRENABLED=N,EVENTINTERVAL=150,XFERPRTCL=SFTP,TL1INTRUSIONPOLICY=BLOCK&FREEZE,TL1PASSWDMAXREUSE=6,TL1PASSWDCOMPLX=ENHANCED,TELNETACCESS=N,ACTTMOUT=0,INACTIVELOG=60,PASSWDMAXCHARREPEAT=1,PASSWDMAXCHARUID=2,PASSWDMAXCHARPREVPWD=3,PASSWDMAXCHARSEQ=2,PASSWDMINLEN=8,PASSWDMINLOWERCASE=1,PASSWDMINUPPERCASE=1,PASSWDMINDGTS=1,PASSWDMINSPECIAL=1,AUTHPOLICY=LOCAL-LOCAL,IPFLTRCONNTRACK=Y,MAXSES=1"

/* RTRV-SYS-SECU */

If the IPFLTRENABLED parameter is not set to N, use TL1 to set it to N.

ed-sys-seCU:qd08::100:: IPFLTRENABLED=N;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

9 Verify prompt mode for TL1 is enabled. Verify that ED-SYS-TL1 PROMPTMODE=Y. To

ensure the upgrade completes successfully, the SIM tool needs to have PROMPTMODE=Y

(ESC key required to invoke the telnet session).

Telica> RTRV-SYS-TL1; 5060mgc8_2 2014-03-28 09:24:44

M 0 COMPLD"COM:TLNTCNTRLOPT=Y,PROMPTMODE=Y"

/* RTRV-SYS-TL1 */ ;;

If the PROMPTMODE=N, enter the following command to set PROMPTMODE=Y:

ED-SYS-TL1:::::PROMPTMODE=Y;

...................................................................................................................................................................................................

10 Verify a scheduled backup is disabled.

RTRV-BKUPSCHED-EQPT

M 0 COMPLD

"COM:24-HR,09-23,22-30,30"

/* RTRV-BKUPSCHED-EQPT */;

Telica> SCHED-BKUP-EQPT:::::::24-HR,0-1,22-30,30;

If a scheduled backup is not disabled, use TL1 to disable it

SCHED-BKUP-EQPT:::::::24-HR,0-1,0-0,30;

...................................................................................................................................................................................................

11 Verify there are no outstanding alarms.

rtrv-alm-ALL;

If there are outstanding alarm, evaluate and clear them as necessary. Refer to the Rapport

MGC-8 ATCA Alarms and Troubleshooting Procedures Guide 255–400–019 for alarmclearing information.

...................................................................................................................................................................................................

12 Verify there are no outstanding conditions.

rtrv-conD-ALL;

If there are outstanding conditions, evaluate and clear them as necessary. Refer to the

Rapport MGC-8 ATCA Alarms and Troubleshooting Procedures Guide 255–400–019 for

condition clearing information.

...................................................................................................................................................................................................

13 Verify if a scheduled exercise is inhibited.RTRV-EXSCHED-EQPT:qd08:shelf-0-acm-3;

M 0 COMPLD

"SHELF-0-ACM-3:0-HR,0-0,0-0,,ALL,SWTOPROTN,ALW"

/* RTRV-EXSCHED-EQPT */

If a scheduled exercise is not allowed, use TL1 to change it to inhibited.

inh-ex-EQPT:qd08:shelf-0-acm-3;


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-17



...................................................................................................................................................................................................

14 Run the following TL1 command to back up the ALGPv2 data.

Syntax: EXEC-BACKUP-CFG:[<TID>]:[<src>]:[CTAG]::<desthost>,

<username>,<password>,<destdir>,[<suppressoutput>],


Note: The following is an example. You should use the correct values for your

application.

Example: EXEC-BACKUP-CFG:::::192.168.xxx.xxx,root,newsys,/home,,,

ftp;

Upgrading ALGPv2 only software from 9.X.X.X to higher software

You will perform this procedure if you only do an ALGPv2 upgrade (no LCP software

change) from 9.X.X.X to higher software

...................................................................................................................................................................................................

1 Log in to the SIDE-B MI services host as root.

...................................................................................................................................................................................................

2 Enter the following command.

sim --proc mgc8_update --action apply


Ready to 'apply' the sim 'mgc8_update' procedure from the beginning:

Continue? (y/n)

Press y to continue.

...................................................................................................................................................................................................

3 Monitor the update by tailing the sim.log file with the following command.

tail -f /storage/sim/log/mgc8_update/sim.logNote: The log may show that SIM aborted due to a MGC-8 health check failure. In

such cases customers need to evaluate the failure carefully. If a customer decides to go

ahead with the software upgrade despite the health check failure, they should run the

following command.

/opt/ALGPV2/sbin/mtce_mgc8 --action ignore_alarm


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



...................................................................................................................................................................................................

4 If resume SIM is needed, enter the following command.

sim --proc mgc8_update --action resume

...................................................................................................................................................................................................

5 Note: For co-host, during this step, MI-B will reboot. Re-login in MI-B and continue

to tail the sim log for the progress.

Continue to follow the sim log till the following pause message appears.

SIM104 [ALL SIM mgc8_update STEPS HAVE COMPLETED!] (mgc8_update:614)

************************************************************

SIM PROGRESS (mgc8_update apply):

************************************************************

105 of 105 sim steps executed (100%)

************************************************************

COMPLETED SIM PROCEDURE 'mgc8_update apply'

...................................................................................................................................................................................................

6 You have completed ALGPv2 upgrade from 9.1.X.X to higher software.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-19

E N D O F S T E P S...................................................................................................................................................................................................



Cold upgrade LCP and ALGPv2 software

Introduction

This procedure uses an offline database backup tool to perform a cold upgrade of LCP

and ALGPv2 software.Note: For a cold upgrade of both LCP and ALGPv2, follow the LCP upgrade

procedure. Refer to QDI#52114 for the LCP upgrade path and corresponding

evolution key.

Performing the cold upgrade

...................................................................................................................................................................................................


...................................................................................................................................................................................................

2 Verify that MI-B is in standby mode, as follows.

MIcmd state vc

> MIcmd state vc




If not, perform a switchover by entering the following command.

MIcmd switch vc

...................................................................................................................................................................................................

3 FTP the MGC-8 Software License file MGC8LicenseFile.txt to the /storage/loads

directory on MI-B. This step is optional but highly recommended.

...................................................................................................................................................................................................

4 FTP the LCP/ALGPV2/DEFT zip files to the /storage/loads directory on MI-B.

Follow the LCP upgrade procedure to upgrade the LCP software.

...................................................................................................................................................................................................

5 Run the following LCP pre-install procedure under /storage/loads on MI-B to zip install

the load.

zipinstall /storage/loads/ATCA.LCPXX.xx.xx.xx.zip --action

update_setup

...................................................................................................................................................................................................

6 Change directory to: /storage/su_backup/ALGPV2/9.x.xxx/sbin

Upgrade scenarios and procedures Cold upgrade LCP and ALGPv2 software

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

7 Stop MGC–8 service on all blades. This is needed to make sure MGC–8 will not reboot

the ACCM/ADCM cards during the LCP software upgrade. Enter the following

command:

./mtce_mgc8 --action disable_service

...................................................................................................................................................................................................

8 Cold upgrade LCP base platform software.

1. Start SIM to upgrade LCP and wait, it will pause (fail)

at mtce_mgc health check

sim --proc update --action apply

SIM will evoke mtce_mgc to:

a. Clean up the configuration of mtce_mgc8

b. Health check mgc8

Since mgc8 service is already disabled, the health check will fail. This failure is

expected.

2. Set flag "skip_all" to tell mtce_mgc8 to do nothing. Note:"config" should always be

enabled. Otherwise, there will be no way to change the config back. For example:

#+BEGIN_EXAMPLE

<qd11-s00c02h0:root>/storage/su_backup/ALGPV2/9.x.xxx/sbin:

# ./mtce_mgc8 --action config --var skip_all --value 1

LOG:mtce_mgc::config set skip_all to 1

#+END_EXAMPLE

3. Resume SU using the following command:


Follow the sim log for progress using the following command:


Follow the sim log for instructions, Use the following command to commit the LCP

update:

sim --proc update --action commit

4. Clear the flag using the following command:

#+BEGIN_EXAMPLE

<qd11-s00c02h0:root>/storage/su_backup/ALGPV2/9.x.xxx/sbin:

# ./mtce_mgc8 --action config --var skip_all

LOG:mtce_mgc::config set skip_all to 0


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



11-21



#+END_EXAMPLE

...................................................................................................................................................................................................

9 Cold upgrade the ALGPv2 software:

#+BEGIN_EXAMPLE

qd11-<s00c02h0:root>/storage/su_backup/ALGPV2/9.3.xxx/sbin:

# ./coldupgrade /storage/loads/ALGPV2.ATCA.9.3.xxx.zip

#+END_EXAMPLE


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



12 12Upgrade working-working

GR switches

Overview

Purpose

This procedure provides steps to upgrade the working-working geographic redundant

(GR) MGC-8 or MGC-8/VSG switches to version 9.X.X or higher.This is a high level procedure that will direct you to detailed level procedures (DLPs).

Once you complete a specific DLP, you must return back to the procedure that directed

you to the DLP to continue.

Important! This procedure may require multiple maintenance windows to complete.

Note: In this procedure, the two working-working geographically redundant MGC-8 or

MGC-8/VSG are referred to as MGC-1 and MGC-2.

Note: While MGC-8's in a GR pair are being upgraded and are on different releases,

provisioning is supported through COM. Some provisioning commands that are normally

replicated cannot be supported while the MGC-8s are on different releases. Thecommands that are not supported for provisioning between any two releases are

documented in the releases notes.

Perform the following steps:

• Upgrade MGC-1

• Test calls and allow MGC-1 to operate for a specified length of time

• If the MGC-1 is operating normally, upgrade the peer working-working GR MGC-8

or MGC-8/VSGs (MGC-2).

• If a failure occurs and you want to revert back to the previous software version,

perform an administrative failover by executing the SW-TOPROTN-MGC command onMGC-1. This command forces control of all MGWs, independent of the MGW group,

over to the peer MGC-2. The MGC-1, where the command is executed, enters the

PROTECTION role.

...................................................................................................................................................................................................................................



12-1



Reverting to a previous software version:

– Perform an out-of-service software change on the MGC-1 to change it to the

original software version.

– Execute DLP-896 - Administrative Failback of a working-working geographically

redundant MGC-8 or MGC-8/VSG. This DLP forces control of all the MGWs in

the peer MGW group on MGC2 over to the peer MGC1 (Failback), where thesoftware was backed out.

NOTICE—Service-disruption hazard! Service outages can occur if provisioning

activities, using TL1 commands or the COM, are performed during the execution of this

procedure. During this procedure, you must only use the TL1 commands indicated in this

procedure.

Contents

Upgrading working-working GR switches 12-2

Upgrading working-working GR switches

Before you begin

This procedure assumes some basic understanding of the operation of the Alcatel-Lucent

Gateway Platform switches.

This procedure assumes that the geographic redundant switch information job aid for

MGC-8 or MGC-8/VSG has been completed with the IP information and Provisioning

information for the switch tables labeled Working-1 and Working-2 .

The following statements must be true:

• Your UNIX/Linux workstation, PC or laptop has Ethernet connectivity to the

switches.

• Your UNIX/Linux workstation, PC or laptop can act as an FTP server.

• Your UNIX/Linux workstation, PC or laptop has an IP address.

• The IP addresses of the MGC-8 or MGC-8/VSG are known. (Obtain IP addresses

from the system administrator or by entering the RTRV-ATCA-EQPT command.)

• If retrieving or setting IP addresses for the MGC-8 or MGC-8/VSG you must know a

valid administrative account and password.

Upgrade working-working GR switches Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



If you have questions regarding this procedure or are directed to contact Technical

Support, please contact the technical support team for your country. If you are unsure of

who that is, you can locate the correct number by going to https://www.alcatel-

lucent.com/support and selecting Lucent Global Support. Ensure you are logged in. Go

to Technical support phone numbers on the lower right of the screen and select your

country and then click Go.

Completing the procedure

This procedure has the following parts which should be completed in order:

1. Upgrade working-working geographically redundant MGC-8 or MGC-8/VSGs

(MGC-1).

2. Check status and test calls on MGC-1.

3. Upgrade working-working geographically redundant MGC-8 or MGC-8/VSGs

(MGC-2).

4. Check status and test calls on MGC-2.5. Verify configuration data on MGC-1 and MGC-2 are synchronized.

Upgrade working-working GR MGC-8 or MGC-8/VSGs (MGC-1)

1. Follow MGC-8 software upgrade procedures as per Rapport MGC-8 ATCA Install

and Upgrade Guide , “Upgrade scenarios and procedures.”

2. Once this procedure is complete, continue to the next procedure “Checking status and

testing calls.”

Check status and test calls

Verify configuration states:

1. Execute “DLP-887: Verify configuration states for MGC-8 or MGC-8/VSG

working-working GR” to verify the configuration states (this DLP checks

configuration states on both MGC-1 and MGC-2).

2. Are the configuration states ok?

• Yes: Continue to the next step.

• No: Try to resolve configuration states discrepancies. If they can be resolved, go

to Step 3 otherwise go to Step 6.

3. Make test calls of different types and then execute the RTRV-PM-CC command to

verify that the number of answered calls increments.

Note: Pick originating CIC’s that are controlled by MGC-1 such that MGC-1 handles

the call.

Command Example: RTRV-PM-CC;

4. Is the number of answered calls incrementing?

Upgrade working-working GR switches Upgrading working-working GR switches

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



12-3



Is the switch operating satisfactorily?

• Yes: Continue to the next step.

• No: Go to Step 6.

5. Is it your company’s policy to allow the switches to operate under newly upgraded

software for a specified period of time before continuing?

• Yes: Wait that specified time period before continuing to step 6.

• No: Go to step 11, you are finished with MGC-1.

6. Is the switch operating satisfactorily?

• Yes: The switch is operating satisfactorily, You are done with MGC-1, Continue to

step 11.

• No: The switch is not operating satisfactorily. Continue to step 7

7. Do you want to failover to the peer MGC-8 or MGC-8/VSG (MGC-2) that is still

running the starting version of software and rollback to the previous version of the

software on MGC-1?

• Yes: Continue to step 8.

• No: Contact Technical Support for help.

8. Execute administrative failover on MGC-1 (SW-TOPROTN-MGC) using “DLP 897 -

Administrative Failover of a Working/Working geographically redundant

MGC-8/VSG or MGC-8 switch.” This DLP forces control of all MGWs on the

MGC-8 over to the peer MGC-8 (Failover).

9. Perform an out-of-service software change on the MGC-1 MGC-8 or MGC-8/VSG, to

change it to the original software version, as per Rapport MGC-8 Install and Upgrade

Guide “Rollback of LCP and MGC-8 software.”

10. Execute “DLP-896 - Administrative Failback of a Working/Working GeographicallyRedundant MGC-8 or MGC-8/VSG.” This DLP forces control of all MGWs in the

peer MGW group on MGC–2 over to the peer MGC–1 (Failback), where the software

was backed out. You have completed this procedure. Contact Technical Support if you

need help.

11. This procedure is complete. Continue to the next procedure, “Upgrade

working-working geographically redundant MGC-8 or MGC-8/VSGs (MGC-2).”

Upgrade working-working GR MGC-8 or MGC-8/VSGs (MGC-2)

1. Follow Step 1 in “Upgrade working-working geographically redundant MGC-8 or

MGC-8/VSGs (MGC-1)” to perform an upgrade on MGC-2.

2. You have completed this procedure part. Continue to the next part “Check status and

test calls on MGC-2.”


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Check status and test calls on MGC-2

1. Follow Step 1 through Step 11 “Check status and test calls, substituting references of

MGC-1 for MGC-2 and MGC-2 for MGC-1

2. You have completed this procedure part for MGC-2.

Verify configuration data on MGC-1 and MGC-2 is synchronized

1. Verify configuration data on MGC-1 and MGC-2 is synchronized by executing DLP

889, “Synchronizing the configuration data of a working-working geographic

redundant MGC-8 or MGC-8/VSG”

Note: MGC-1 and MGC-2 should be running the same software version when

DLP-889 is executed.

2. You have completed this part of the procedure.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



12-5




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



13 13Rollback and backout

procedures

Overview

Purpose

This chapter provides procedures to roll back or back out of an upgrade.

Rollback is different from backout. Rollback is used to back out a committed update and backout is used to back out an uncommitted update.

The rollback and backout procedures are similar only for the MGC-8.

Note the following.

• To perform a back out or roll back, contact the next level of Technical Support.

• The backout or rollback process does not require a data evolution because the data

from the previous release is already stored on the local boot service hosts.

• Certain backout and rollback scenarios result in the loss of call processing.

• Ensure to complete the backout or rollback process. After a rollback or backout

process begins, it is not possible to go forward until it completes.

Contents

Rollback of LCP and MGC-8 software 13-2

Backout of LCP and MGC-8 upgrade 13-7

Backout MGC-8 only upgrade 13-12

...................................................................................................................................................................................................................................



13-1



Rollback of LCP and MGC-8 software

Introduction

This topic describes the procedure to roll back to the previous release. Perform this

procedure, if you want to return to the previous release, after completing the softwareupgrade successfully.

Before you begin

Perform a database backup before the upgrade. If any blade replace or FRU is done after

an upgrade, you cannot rollback the software.

If you save the database backup to an external server, the ACCMs IP address need to be

restored prior to restoring the MGC-8 from the backup on the external server.

Procedure

Perform the following steps to roll back to the previous release:

...................................................................................................................................................................................................

1 Log in to the MI-B (OAM Server B).

...................................................................................................................................................................................................

2 Unlock the rollback function with the following command:

mtce_platform --action rollback_unlock

...................................................................................................................................................................................................

3 Run the Software Installation Manager (SIM) tool to rollback using the followingcommand:

sim --proc update --action rollback

...................................................................................................................................................................................................

4 Run tail sim.log until the PAUSED message is seen in the SIM log.


Output example:

13/07/01 21:18:45 SIM081[********************************************************] (update_rlbk:385)

13/07/01 21:18:45 SIM082 [* WARNING: Ready to Activate the PreviousSoftware!] (update_rlbk:388)

13/07/01 21:18:45 SIM083 [* Call Processing will be Affected beyondthis point!!!!] (update_rlbk:391)

Rollback and backout procedures Rollback of LCP and MGC-8 software

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



13/07/01 21:18:45 SIM084[********************************************************] (update_rlbk:394)

13/07/01 21:18:45

13/07/01 21:18:45 SIM085 PAUSE_REQUEST: (PROCEDURE) [PAUSE(CP_WARNING): Use 'sim --proc update --action resume' to continue...]

13/07/01 21:18:4513/07/01 21:18:45************************************************************

13/07/01 21:18:45 SIM PROGRESS (update rollback):

13/07/01 21:18:45************************************************************


13/07/01 21:18:45************************************************************

13/07/01 21:18:45

13/07/01 21:18:45 PAUSED: (PROCEDURE) Dispatched commands arecomplete.

...................................................................................................................................................................................................

5 Resume the rollback action with the following command:


...................................................................................................................................................................................................



Output example:

13/07/01 21:29:14 SIM113[********************************************************] (update_rlbk:530)

13/07/01 21:29:14 SIM114 [* Verify call-processing beforecontinuing.] (update_rlbk:533)

13/07/01 21:29:14 SIM115[********************************************************] (update_rlbk:536)

13/07/01 21:29:14

13/07/01 21:29:14 SIM116 PAUSE_REQUEST: (PROCEDURE) [PAUSE(VERIFY_SOFTWARE): Use 'sim --proc update --action resume' to continue...]

13/07/01 21:29:14

13/07/01 21:29:14

************************************************************13/07/01 21:29:14 SIM PROGRESS (update rollback):

13/07/01 21:29:14************************************************************


13/07/01 21:29:14************************************************************

13/07/01 21:29:14


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-3




...................................................................................................................................................................................................

7 Resume the rollback action with the following command:


...................................................................................................................................................................................................

8 Run tail sim.log again. During rollback, MI-B will be rebooted. After reboot, log in again

to MI-B to tail sim.log until the message indicates that the rollback is completed.


13/07/01 21:58:52************************************************************ 13/07/01 21:58:52 SIM PROGRESS (update rollback): 13/07/01 21:58:52************************************************************ 13/07/01 21:58:52 207 of 207 sim steps executed (100%) 13/07/01 21:58:52

************************************************************

...................................................................................................................................................................................................

9 Reboot the ACCMs.

...................................................................................................................................................................................................

10 When the ACCMs and ADCMs have rebooted, enter the following from the OS of the

active ACCM blade to access TL1 commands:


Log in using the ACT-USER command.

Note: Since the IP addresses of MGC-8 are deleted after a rollback, you need to SSHto an ACCM blade from the OAM blade (for non-co-host (standalone)) or through the

OAM MI or CNFG IP (for co-host).

Note: For non-cohost, the DB backup file must be on the OAM1/2 cards.

...................................................................................................................................................................................................

11 Run the following TL1 command to restore MGC-8 database.

Syntax: EXEC-RESTORE-CFG:<TID>:[<src>]:[CTAG]::<srchost>,

<username>,<password>,<srcpath>,[<suppressoutput>],


Example: EXEC-RESTORE-CFG:telica::::169.254.64.64,root,newsys,/

home/backup/telica_SW8.2.1.2.0.20_SCHEMA8.2.1.0_20110802_

1556

Note: You must replace the parameters with those applicable to your switch.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

12 Is internal BTS being used?

Note: This means that the DLP-551: Accessing and configuring BTS on a MGC-8

(ATCA) blade in the Rapport MGC-8 ATCA & COTS Billing and Traffic System

(BTS) Users Guide, 255-400-403 is executed to configure and enable internal BTS.

IF... THEN...

Yes Continue to the next step.

No Go to step 16.

...................................................................................................................................................................................................

13 Do you roll back LCP and MGC-8 from R9.3 or later releases to releases prior to R9.3?

IF... THEN...


No Go to step 16.

...................................................................................................................................................................................................

14 On one ACCM, remove the IPv6 configuration in /storage/PlexDC/BTS_IP , if any, and

change the format of the IPv4 address in /storage/PlexDC/BTS_IP as shown below:

xxx.xxx.xxx.xxx

For example, if the file content of /storage/PlexDC/BTS_IP is:

IPV4 10.84.16.156IPV6 2620:0:60:4011:0:0:0:5010

Change it to:

10.84.16.156

...................................................................................................................................................................................................

15 Have you run step 14 on both ACCMs?

IF... THEN...


No Run from Step 14 on the remaining ACCM.

...................................................................................................................................................................................................

16 When the database has been restored, you must reboot the MGC-8 using the INIT-SYS

command.

INIT-ATCA-SYS:<tid>:1:::10


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-5



Replace <tid> with the tid for the switch.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Backout of LCP and MGC-8 upgrade

Introduction

This topic describes the procedure to back out to the previous release. Perform this

procedure, if a failure occurs during the software upgrade and if you want to return to the previous release.

Before you begin

Perform a database backup before the upgrade.

Procedure

Perform the following steps to back out to the previous release:

...................................................................................................................................................................................................


...................................................................................................................................................................................................

2 Run the Software Installation Manager (sim) tool to backout using the following

command.

sim --proc update --action backout

...................................................................................................................................................................................................



Output example:

13/07/01 14:03:19 SIM088[********************************************************] (update_rlbk:385)

13/07/01 14:03:19 SIM089 [* WARNING: Ready to Activate the PreviousSoftware!] (update_rlbk:388)

13/07/01 14:03:19 SIM090 [* Call Processing will be Affected beyondthis point!!!!] (update_rlbk:391)

13/07/01 14:03:19 SIM091[********************************************************] (update_rlbk:394)

13/07/01 14:03:1913/07/01 14:03:19 SIM092 PAUSE_REQUEST: (PROCEDURE) [PAUSE(CP_

WARNING): Use 'sim --proc update --action resume' to continue...]

13/07/01 14:03:19

13/07/01 14:03:19************************************************************

13/07/01 14:03:19 SIM PROGRESS (update backout):

Rollback and backout procedures Backout of LCP and MGC-8 upgrade

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-7



13/07/01 14:03:19************************************************************


13/07/01 14:03:19************************************************************

13/07/01 14:03:19


...................................................................................................................................................................................................

4 Resume the backout action with the following command.


...................................................................................................................................................................................................



Output example:

Run tail sim.log until the PAUSED message is seen in the SIM log.


13/07/01 14:14:52 SIM120[********************************************************] (update_rlbk:530)

13/07/01 14:14:52 SIM121 [* Verify call-processing beforecontinuing.] (update_rlbk:533)

13/07/01 14:14:52 SIM122[********************************************************] (update_rlbk:536)

13/07/01 14:14:52

13/07/01 14:14:52 SIM123 PAUSE_REQUEST: (PROCEDURE) [PAUSE(VERIFY_SOFTWARE): Use 'sim --proc update --action resume' to continue...]

13/07/01 14:14:52

13/07/01 14:14:52************************************************************


13/07/01 14:14:52************************************************************


13/07/01 14:14:52************************************************************

13/07/01 14:14:52


13/07/01 14:14:52


...................................................................................................................................................................................................



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015




...................................................................................................................................................................................................

7 Run tail sim.log again.

During backout, MI-B will be rebooted. After reboot, log in again to MI-B to tail sim.log

until the message indicates that the backout is completed.

For co-host, during backout, MI-B will be rebooted. After reboot, log in again to MI-B to

tail sim.log for the progress.


13/07/01 07:47:24************************************************************


13/07/01 07:47:24************************************************************


13/07/01 07:47:24************************************************************

13/07/01 07:47:24

13/07/01 07:47:24 COMPLETED SIM PROCEDURE 'update backout' type=hotlevel=60

...................................................................................................................................................................................................

8 Reboot the ACCMs.

...................................................................................................................................................................................................


active ACCM blade to access TL1 commands:telnet localhost 2361 or telnet 0 2361 to telnet to the ACCM blades for TL1.


Note: Since the IP addresses of MGC-8 are deleted after a backout, you need to SSH

to an ACCM blade from the OAM blade (for non-co-host (standalone)) or through

OAM MI or CNFG IP (for co-host).

...................................................................................................................................................................................................







1556


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-9




...................................................................................................................................................................................................





IF... THEN...


No Go to step 15.

...................................................................................................................................................................................................

12 Do you back out LCP and MGC-8 from R9.3 or later releases to releases prior to R9.3?

IF... THEN...


No Go to step 15.

...................................................................................................................................................................................................



xxx.xxx.xxx.xxx


IPV4 10.84.16.156

IPV6 2620:0:60:4011:0:0:0:5010

Change it to:

10.84.16.156

...................................................................................................................................................................................................


IF... THEN...




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



...................................................................................................................................................................................................

15 When the database has been restored, you must reboot the MGC-8 using the INIT-SYS

command.

INIT-ATCA-SYS:<tid>:1:::10



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-11

E N D O F S T E P S...................................................................................................................................................................................................



Backout MGC-8 only upgrade

Introduction

This topic describes the procedure to back out to the previous release. Perform this

procedure, if you want to return to the previous release, after completing the softwareupgrade successfully.

Before you begin

Perform a database backup before the upgrade.

Procedure

Perform the following steps to back out to the previous release:

...................................................................................................................................................................................................


...................................................................................................................................................................................................

2 Run the Software Installation Manager (sim) tool to backout using the following

command.

sim --proc mgc8_update --action backout

...................................................................................................................................................................................................


tail -f /storage/sim/log/mgc8_update/sim.log

Output example:

13/07/01 03:13:37 SIM006[************************************************************](mgc8_update_bk:54)

13/07/01 03:13:37 SIM007 [* Ready to Backout the 8.3.0.0.0.178Software Upgrade!] (mgc8_update_bk:57)

13/07/01 03:13:37 SIM008[************************************************************](mgc8_update_bk:60)

13/07/01 03:13:37

13/07/01 03:13:37 SIM009 PAUSE_REQUEST: (PROCEDURE) [PAUSE(BACKOUT):Use 'sim --proc mgc8_update --action resume' to continue...]

13/07/01 03:13:37

Rollback and backout procedures Backout MGC-8 only upgrade

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



13/07/01 03:13:37************************************************************

13/07/01 03:13:37 SIM PROGRESS (mgc8_update backout):

13/07/01 03:13:37

************************************************************


13/07/01 03:13:37************************************************************

...................................................................................................................................................................................................


sim --proc mgc8_update --action resume

...................................................................................................................................................................................................

5 Run tail sim.log again until the message indicates that the backout was completed.

For co-host, during backout, MI-B will be rebooted. After reboot, you need to log in again

to MI-B to tail sim.log for the progress.

tail -f /storage/sim/log/mgc8_update/sim.log

13/07/01 05:09:19************************************************************

13/07/01 05:09:19 SIM PROGRESS (mgc8_update backout):

13/07/01 05:09:19************************************************************


13/07/01 05:09:19************************************************************

13/07/01 05:09:19

13/07/01 05:09:19 COMPLETED SIM PROCEDURE 'mgc8_update backout'level=100

...................................................................................................................................................................................................

6 Reboot the ACCMs.

...................................................................................................................................................................................................


active ACCM blade to access TL1 commands:


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-13





Note: Since the IP addresses of MGC-8 are deleted after a backout, you need to SSH

to an ACCM blade from the OAM blade (for non-co-host (standalone)) or through the

OAM MI or CNFG IP (for co-host)....................................................................................................................................................................................................







1556


...................................................................................................................................................................................................





IF... THEN...


No Go to step 13.

...................................................................................................................................................................................................

10 Do you back out MGC-8 from R9.3 or later releases to releases prior to R9.3?

IF... THEN...


No Go to step 13.

...................................................................................................................................................................................................



xxx.xxx.xxx.xxx


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015




IPV4 10.84.16.156

IPV6 2620:0:60:4011:0:0:0:5010

Change it to:

10.84.16.156

...................................................................................................................................................................................................


IF... THEN...



...................................................................................................................................................................................................

13 When the database is restored, reboot the MGC-8 using the INIT-SYS command.INIT-ATCA-SYS:<tid>:1:::10



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



13-15

E N D O F S T E P S...................................................................................................................................................................................................




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Appendix A: Hardware

illustrations

Overview

Purpose

This appendix provides illustrations of the supported hardware.

Contents

ATCA Shelf A-1

Processor blade (FM016JB or FM016JP) A-3

Ethernet hub A-4

Ethernet hub RTM A-5

Shelf manager card A-6

ATCA Shelf

Introduction

Figure A-1, “ATCA Shelf Example” (p. A-2) depicts an example of an ATCA Shelf. Slots

1-6 and slots 9-14 are populated with nodes or blank boards, slots 7 and 8 contain hub

boards, and Slot 15 contains two Shelf Managers (ShMC).

...................................................................................................................................................................................................................................



A-1



Figure A-1 ATCA Shelf Example

Hardware illustrations ATCA Shelf

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

A-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Processor blade (FM016JB or FM016JP)

Introduction

Figure A-2 Processor Blade

Hardware illustrations Processor blade (FM016JB or FM016JP)

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



A-3



Ethernet hub

Introduction

Figure A-3 Ethernet hub

Hardware illustrations Ethernet hub

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Ethernet hub RTM

Introduction

Figure A-4 Hub RTM Card Example

Hardware illustrations Ethernet hub

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



A-5



Shelf manager card

Introduction

Figure A-5 Shelf manager card (ShMC) example

Hardware illustrations Shelf manager card

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Appendix B: Worksheets

Overview

Purpose

This Appendix provides the configuration worksheets that must be completed prior to

performing the LCP installation. For instructions on how to complete the worksheets,refer to Chapter 3, “Prepare for the LCP installation”.

Contents

Worksheet 1 B-2

Worksheet 2 B-3

Worksheet 3A B-6

Worksheet 3B B-7

...................................................................................................................................................................................................................................



B-1



Worksheet 1

Summary

Worksheet 1

Cabinet/Shelf

Slot 1,2 3,4 5,6 7,8 9,10 11,12 13,14 15

0/1 Ser-

vice(s)

HUB SHMC

IPV4

Default

Gateway

(Subnet

#)

N/A N/A

IPV6

Default

Gateway

(Subnet

#)

Disk

Partition

N/A N/A N/A N/A N/A N/A

Worksheets Worksheet 1

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

B-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Worksheet 1

Cabinet/Shelf

Slot 1,2 3,4 5,6 7,8 9,10 11,12 13,14 15

0/0 Ser-

vice(s)

stand-

alone=CNFG

/MI

co-host=

CNFG

/MI

/ACCM

HUB/ SHMC

IPV4

Default

Gateway

(Subnet

#)

co-host=

default

gateway

N/A

IPV6

Default

Gateway

(Subnet

#)

Disk

Partition

N/A N/A N/A N/A N/A N/A N/A

Worksheet 2

Summary

Worksheet 2

System Name: Application(s): System Prefix:

Internal Subnet: Time Zone: Alarm Shelf

Association:

None

IPV4 Subnet 1 Name:

Subnet: Netmask:

Gateway IP: Transport

Interface:

Both HSPP4

Faceplate

Interfaces -0,1

Shelf Number: 0


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



B-3



Worksheet 2

IPV4 Subnet 2

Name:

Subnet: Netmask:


Interface:

Both Front

Interface -0

Shelf Number: 0

IPV4 Subnet 3

Name:

Subnet: Netmask:


Interface:

Both Rear

Interface -0

Shelf Number: 0

IPV4 Subnet 4

Name:

Subnet: Netmask:


Interface:

MME Port 1-3

with future LAG

support

Shelf Number: 0

IPV6 Subnet 1

Name:

Subnet Prefix: Subnet Prefix

Length:


Interface:

Both HSPP4

Faceplate

Interfaces -0,1

Shelf Number: 0

IPV6 Subnet 2

Name:


Length:


Interface:

Both HSPP4

Faceplate

Interfaces -0,1

Shelf Number: 0

IPV6 Subnet 3

Name:


Length:


Interface:

Both HSPP4

Faceplate

Interfaces -0,1

Shelf Number: 0

IPV6 Subnet 4

Name:


Length:


Interface:

Both HSPP4

Faceplate

Interfaces -0,1

Shelf Number: 0

Shelf 0 HUB 7

SSH IP:

Shelf 0 HUB 7

SSH Netmask:

Shelf 0 HUB 7

SSH Gateway:

Shelf 0 HUB 8

SSH IP:

Shelf 0 HUB 8

SSH Netmask:

Shelf 0 HUB 8

SSH Gateway:


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Worksheet 2

Shelf 1 HUB 7

SSH IP:

Shelf 1 HUB 7

SSH Netmask:

Shelf 1 HUB 7

SSH Gateway:

Shelf 1 HUB 8

SSH IP:

Shelf 1 HUB 8

SSH Netmask:

Shelf 1 HUB 8

SSH Gateway:Shelf 0 HUB 7

SOL IP:

Shelf 0 HUB 8

SOL IP:

Shelf 1 HUB 7

SOL IP:

Shelf 1 HUB 8

SOL IP:

Hub Ports with

Auto speed:

Hub Ports with

100M speed:

Hub Ports with

10M speed:

NTP Server 1

IP:

NTP Server 2

IP:

NTP Server 3

IP:

Solutiondomain:

Local

Zone/LCP

Domain:

Enum Domain: e164.arpa

DNS Server 1

IPv4 IP:

DNS Server 2

IPv4 IP:

DNS Server 3

Ipv4 IP:

ENUM Server

1 IP:

ENUM Server 2

IP:

ENUM Server

3 IP:

IPV4 Static

Routes:

Subnet 1: Netmask:

Gateway: Service(s):

Subnet 2: Netmask:

Gateway: Service(s):

IPV6 Static

Routes:

Subnet Prefix 1: Subnet Prefix

Length:

Subnet for

Source IP:

Service(s):

Subnet Prefix 2: Subnet Prefix

Length:


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



B-5



Worksheet 2

Subnet for

Source IP:

Subnet for

Source IP:

Worksheet 3A

Summary

Worksheet 3A

NI-type IPV4Subnet ID(subnet #)

IPV4 IP IPV6Subnet ID(subnet #)

IPV6 IP

CDR pool-0 IP-floating NI-default

CDR pool-0 IP-floating NI-diam_rf default

CDR pool-0 IP-floating NI-dns default

CNFG pool-0 IP-floating NI-default N/A N/A

FSDB pool-0 IP-floating NI-default N/A N/A

FSDB pool-0 IP-floating NI-diam_sh default NotConfig-

ured

FSDB pool-0 IP-floating NI-dns default NotConfig-

ured

FSDB pool-0 IP-floating NI-fsdb_geosync N/A N/A N/A N/A

GLS pool-0 IP-floating NI-default

GLS pool-0 IP-floating NI-diam_gls default

GLS pool-0 IP-floating NI-dns default

MI pool-0 IP-floating NI-default N/A N/A

MI pool-0 member-0 IP-fixed NI-default N/A N/A

MI pool-0 member-1 IP-fixed NI-default N/A N/A

MI pool-0 IP-floating NI-mi_access default N/A N/A N/A

MI pool-0 IP-floating NI-mi_media N/A N/A N/A

MI pool-0 member-0 IP-fixed NI-ntp default N/A N/A

MI pool-0 member-1 IP-fixed NI-ntp N/A N/A

sns pool-0 member-0 IP-fixed NI-default

sns pool-0 member-1 IP-fixed NI-default


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Worksheet 3A

NI-type IPV4Subnet ID(subnet #)


IPV6 IP

sns pool-0 member-0 IP-fixed NI-dns default default

sns pool-0 member-1 IP-fixed NI-dns

Worksheet 3B

Summary

Worksheet 3B

NI-type IPV4 subnetID (subnet

#)


IPV6 IP

AMMS pool-0 member 0 IP-fixed

NI-default

AMMS pool- member 0 IP-fixed

NI-default


NI-signtwrk1


NI-signtwrk2

FEPH pool-0 IP-floating NI-published default

FS5K pool-0 IP-floating NI-default

FS5K pool-0 IP-floating NI-diam_gls default default

FS5K pool-0 IP-floating NI-diam_rf default default

FS5K pool-0 IP-floating NI-diam_ro default default

FS5K pool-0 IP-floating NI-dns default default

FS5K pool-0 IP-floating NI-enum N/A N/A

FS5K pool-0 IP-floating NI-web_portal default N/A N/A

H248 pool-0 member-0 IP-fixed

NI-default

H248 pool-0 member-1 IP-fixed

NI-default

NotConfig-

ured

Worksheets Worksheet 3A

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



B-7



Worksheet 3B


#)


IPV6 IP

H248 pool-0 member-0 IP-float

NI-diam_rf

NotConfig-

ured

NotConfig-

ured

H248 pool-0 member-0 IP-float NI-dns default default

H248 pool-0 member-0 IP-float NI-enum default default


NI-h248sig

default N/A N/A


NI-h248sig1

default N/A N/A


NI-h248sig2

default N/A N/A

IMS pool-0 IP-floating NI-default

IMS pool-0 IP-floating NI-diam_cx default

IMS pool-0 IP-floating NI-diam_e2

IMS pool-0 IP-floating NI-diam_gqp

IMS pool-0 IP-floating NI-diam_rf default default

IMS pool-0 IP-floating NI-diam_ro default default

IMS pool-0 IP-floating NI-diam_rx

IMS pool-0 IP-floating NI-diam_sh default default

IMS pool-0 IP-floating NI-diam_tx

IMS pool-0 IP-floating NI-dns default default

IMS pool-0 IP-floating NI-enum default default

IMS pool-0 IP-floating NI-pdf default default

IMS pool-0 IP-floating NI-published NotConfig-

ured

NotConfig-

ured

IMS pool-0 IP-floating NI-signtwrk1 NotConfig-

ured

NotConfig-

ured

IMS pool-0 IP-floating NI-signtwrk2 NotConfig-ured

NotConfig-ured

mif pool-0 IP-floating NI-default N/A N/A

pool-0 IP-floating NI-gnsig default

mif pool-0 IP-floating NI-mif_s10 default N/A N/A

Worksheets Worksheet 3B

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Worksheet 3B


#)


IPV6 IP



mif pool-0 IP-floating NI-mif_s1mme default N/A N/A

mif pool-0 IP-floating NI-mif_s6a default

mif pool-0 IP-floating NI-svsig default

mif pool-0 IP-floating NI-sgsig default

mif pool-0 IP-floating NI-x2sig default

PCRV pool-0 IP-floating NI-default N/A N/A

PCRV pool-0 IP-floating NI-oamp default N/A N/A

PCRV pool-0 IP-floating NI-h248sig1 default N/A N/A

PCRV pool-0 IP-floating NI-h248sig2 default N/A N/A

SS7 pool-0 member-0 IP-fixed NI-default N/A N/A

SS7 pool-0 member-1 IP-fixed NI-default N/A N/A

SS7 pool-0 member-0 IP-fixed NI-ss7sig1 NotConfig-

ured

N/A N/A


ured

N/A N/A

SS7 pool-0 member-0 IP-fixed NI-ss7sig2 NotConfig-ured

N/A N/A


ured

N/A N/A


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



B-9




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Appendix C: ShMC and ethernet

hub commands

Overview

Purpose

This appendix provides a listing of useful commands for obtaining ShMC or Hub

information.

Contents

ShMC commands C-1

Ethernet hub commands C-2

ShMC commands

Summary

Table C-1 ShMC commands

Execute this command To do this ...

clia shmstatus Find the active Shmc

clia switchover Switchover to the other Shmc

clia version Find the firmware version

clia board Find the populated slots

clia board <slot-number

> Find the board state in slots 1 through 14clia boardreset <slot-number > Reset a board in slots 1 through 14

clia deactivate board <slot-number > Remove power to a board in slots 1

through 14

...................................................................................................................................................................................................................................



C-1



Table C-1 ShMC commands (continued)


clia activate board <slot-number > Restore power to a board in slots 1

through 14 (check that the board state

shows inactive first)clia shelfaddress Find the shelf number (fourth field in

hex notation)

clia shelfaddrss To find the cabinet number (eighth field

in hex notation)

clia fruinfo -s 20 254 | egrep

“Chassis Serial Number”

Find the serial number of the chassis

clia fruinfo -v 10 0 | egrep “Board

Serial Number”

Retrieve the top Shmc serial number

clia fruinfo -v 12 0 | egrep “Board Serial Number” Retrieve the bottom Shmc serial number

clia fruinfo shm 1 | egrep “Board

Product Name”

Find the fruname of the top Shmc

clia fruinfo shm 2 | egrep “Board

Product Name”

Find the fruname of the bottom Shmc

clia fruinfo board <slot-number > |

egrep “Board Product Name”

Find the fruname of blades in slots 1

through 14

clia board <slot-number> | egrep -c

“AMC HDD”

Find out the number of disks in a blade

in slots 1 through 14

clia setextracted board <x> To clear ghosts

Ethernet hub commands

Summary

Table C-2 Ethernet hub commands


printenv | egrep REL View version

printenv | egrep RTM Determine if the hub has detected its RTM

tcpdump -i <interface>

tcpdump -i eth0

Look at traffic

ShMC and ethernet hub commands ShMC commands

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

C-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Appendix D: Initiating a SOL

session with a processor blade

Overview

Purpose

This appendix provides instructions about how to initiate a SOL session for a processor

blade.

Contents

SOL session for a processor blade procedure D-2

Determining the SOL IP address on a blade D-3

...................................................................................................................................................................................................................................



D-1



SOL session for a processor blade procedure

Procedure

Complete the following steps to initiate a SOL session for a processor blade.

...................................................................................................................................................................................................

1 First establish an SSH session to one of the hub cards by logging in as root.

...................................................................................................................................................................................................

2 Use the following syntax (you may have to hit CR a few times to get a login prompt).

console -s <shelfnum> -c <slotnum>

where <shelfnum> and <slotnum> represent the shelf and slot number where the

processor blade resides.

...................................................................................................................................................................................................

3 To exit from the session, type “~.” (tilde dot)

If there was a SOL session that was not terminated in a graceful manner, you can

gracefully terminate it using the following syntax; however, be advised that this command

will disconnect the active SOL session. Verify that the session is not in use by another

user prior to deactivating it.

console -s <shelfnum> - c <slotnum> -a deactivate

where < shelfnum> and < slotnum> represent the shelf and slot number of the Ethernet Hub

“dangling” session.

Initiating a SOL session with a processor blade SOL session for a processor blade procedure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

D-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Determining the SOL IP address on a blade

Procedure

To determine the SOL IP address on a blade, complete the following steps.

...................................................................................................................................................................................................

1 Login to the blade.

...................................................................................................................................................................................................

2 Run the following command.

ipmitool lan print <channel>

where <channel >= 1 or 2. (For hubs, only channel=2 is configured.)

Initiating a SOL session with a processor blade Determining the SOL IP address on a blade

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



D-3

E N D O F S T E P S...................................................................................................................................................................................................



Initiating a SOL session with a processor blade Determining the SOL IP address on a blade

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

D-4 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Appendix E: Changing the

SSH/SOL IP of hub 7/8

Overview

Purpose

This appendix provides instructions for changing the SSH/SOL IP of Hub 7/8.

Contents

Prerequisites to change SSH/SOL IPs on Hub 7/8 E-2

Hub and shmc configuration E-3

Procedure and useful commands for changing IPs E-6

...................................................................................................................................................................................................................................



E-1



Prerequisites to change SSH/SOL IPs on Hub 7/8

Prerequisites

Complete the following.

...................................................................................................................................................................................................

1 Determine the shelf 0 hostname of blade 1.

...................................................................................................................................................................................................

2 Determine the shelf 0 hostname of blade 2.

...................................................................................................................................................................................................

3 Determine the shelf 0 hub 7 SOL ip address.

...................................................................................................................................................................................................

4 Determine the shelf 0 hub 7 ssh ip address, netmask, and gateway.

...................................................................................................................................................................................................

5 Determine the shelf 0 hub 8 SOL ip address.

...................................................................................................................................................................................................

6 Determine the shelf 0 hub 8 ssh ip address, netmask, and gateway.

Hostname

Blade 1

Blade 2

SOL IP SSH IP SSH Netmask SSH Gateway

HUB 7

HUB 8

Changing the SSH/SOL IP of hub 7/8 Prerequisites to change SSH/SOL IPs on Hub 7/8

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

E-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Hub and shmc configuration

Procedure

...................................................................................................................................................................................................

1 Determine SSH and SOL IP addresses of shelf 0 hub 7 and shelf 0 hub 8.

Table E-1 Customer values of SSH and SOL

SOL IP SSH IP SSH Netmask SSH Gateway

HUB 7

HUB 8

...................................................................................................................................................................................................

2 Login as root to the blade 1.

...................................................................................................................................................................................................

3 Verify health of the system.


Do not continue to the next step if this step is unsuccessful.

...................................................................................................................................................................................................

4 Clear inhibit on blade 2.

rcc_adm --action clr_inhibit --host <hostname of blade 2>

...................................................................................................................................................................................................

5 Align all virtual machines on blade 2.

vm_adm --action switch --desired_state ACT --host <hostname of

blade 2>

...................................................................................................................................................................................................

6 Wait for all virtual machines to go active on blade 2.

rcc_srv_state --action wait_state --set host --state_type VM --

vstate ACT --host <hostname of blade 2>

...................................................................................................................................................................................................

7 Inhibit RCC on blade 1.

rcc_adm --action set_inhibit --host <hostname of blade 1>

...................................................................................................................................................................................................

8 Configure the SSH IP of hub 7.

Changing the SSH/SOL IP of hub 7/8 Hub and shmc configuration

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



E-3



hubconf_adm --action set_ssh_address4 --shelfnum 0 --cardnum 7 --

hostnum 0 --address4 < hub 7 SSH IP > --netmask4 < hub 7 SSH

netmask > --gateway4 < hub 7 SSH gateway >

...................................................................................................................................................................................................

9 Configure the SSH IP of hub 8.hubconf_adm --action set_ssh_address4 --shelfnum 0 --cardnum 8 --

hostnum 0 --address4 < hub 8 SSH IP > --netmask4 --< hub 7 SSH

netmask > --gateway4 < hub 8 SSH gateway >

...................................................................................................................................................................................................

10 Configure SOL IP of hub 7.

shmcconf_adm --action set_sol_address4 --shelfnum 0 --cardnum

7 --hostnum 0 --address4 < hub 7 SOL IP >

...................................................................................................................................................................................................

11 Configure SOL IP of hub 8.

shmcconf_adm --action set_sol_address4 --shelfnum 0 --cardnum

8 --hostnum 0 --address4 < hub 8 SOL IP >

...................................................................................................................................................................................................

12 Generate hub configuration files.

hubconf_adm --action generate_host_all

...................................................................................................................................................................................................

13 Generate shmc configuration files.shmcconf_adm --action generate_host_all

...................................................................................................................................................................................................

14 Install the hub configuration files on both OAM servers.

hubconf_adm --action install_host_all

...................................................................................................................................................................................................

15 Install the shmc configuration files on both OAM servers.

shmcconf_adm --action install_host_all

...................................................................................................................................................................................................

16 Synchronize metadata to the other OAM server.

scdm_adm --action sync_config

...................................................................................................................................................................................................

17 Clear inhibit on blade 1.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015




...................................................................................................................................................................................................

18 Align all virtual machines on blade 1.

vm_adm --action switch --desired_state ACT --host <hostname of

blade 1>

...................................................................................................................................................................................................

19 Wait for all virtual machines to go active on blade 1.

rcc_srv_state --action wait_state --set host --state_type VM --

vstate ACT --host <hostname of blade 1>

...................................................................................................................................................................................................

20 Inhibit RCC on blade 2.

rcc_adm --action set_inhibit --host <hostname of blade 2>

...................................................................................................................................................................................................

21 SSH to blade 2 as root.

...................................................................................................................................................................................................

22 On blade 2, generate hub configuration files.

hubconf_adm --action generate_host_all

...................................................................................................................................................................................................

23 On blade 2, generate shmc configuration files

shmcconf_adm --action generate_host_all

...................................................................................................................................................................................................

24 Exit from blade 2.

exit

...................................................................................................................................................................................................

25 Install the hub configuration files on the hub. The HUB will reboot. So direct screen print

to log file, and check the log file to make sure hub update is finished successfully before

take next action.

hub_adm -a config_all 2>&1|tee -a /data0/FLD/hubUPG.log

...................................................................................................................................................................................................

26 Install the shmc configuration files on the shmc.

shmc_adm -a config_all


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



E-5



...................................................................................................................................................................................................

27 Allow RCC on blade 1.


...................................................................................................................................................................................................

28 Allow RCC on blade 2.


...................................................................................................................................................................................................

29 Verify health of the system.


...................................................................................................................................................................................................

30 If no errors are reported, the procedure is now complete.

Procedure and useful commands for changing IPs

Manage IP configuraiton

Note: You can also refer to the Manage system configuration - IP configuration

chapter in the LCP Configuration Management, 270-702-014 manual for additional

information.

CNFG floating, MI floating, MI-A fixed, MI-B fixed IP

Change from

10.20.30.5, 6, 7, 8

to

192.1.104.201, 202, 203, 204

Prep work:

Check MI state:

> MIcmd state vc

Check service type:

> svcconf_adm --action list_service_type

Check host type:> svcconf_adm --action show_host

check network interface type:

> svcconf_adm --action list_ni_type

check external subnet:

> net4conf_adm --action show_external_subnet

check external transport:

> net4conf_adm --action show_external_transport


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S

...................................................................................................................................................................................................



check gateway:

> net4conf_adm --action show_subnet_gatewayDelete cnfg & MI floatingIPs:

ip_adm -a del_floating_ip -t <Service Type> -i <Pool ID> -s

<Subnet Number> -o <Offset>

ip_adm -a del_fixed_ip -t <Service Type> -i <Pool ID> -s

<Subnet Number> -o <Offset><<< ISSUE:

LCP ip_adm tool for delete is not list in the customer doc,

so it was not offically "supported".

with cnfg floating IP offset as 5

> ip_adm -a del_floating_ip -t cnfg -i 0 -s 1 -n default -o 5

> ip_adm -a commit

with mi floating IP offset as 6

> ip_adm -a del_floating_ip -t mi -i 0 -s 1 -n default -o 6

> ip_adm -a commit

with mi fixed IP offset as 7&8

> ip_adm -a del_fixed_ip -t mi -i 0 -s 1 -n default -o 7,8> ip_adm -a commit

Delete external subnet:

ip_adm -a del_subnet -b <subnet base> -s <subnet number>

<<< ISSUE:

"ip_adm -a del_subnet -b 10.20.30.0 -s 1" failed b/c the

gateway is being deleted but the script was still looking for

it.

WORKAROUND:

O N O A M A & B , d o

> net4conf_adm --action del_external_subnet --subnetnum 1

Check to make sure no entry for the following:> net4conf_adm --action show_external_subnet

> net4conf_adm --action show_external_transport

> net4conf_adm --action show_subnet_gateway

Add the external subnet first, then the floating & fixed IPs:

ip_adm -a add_subnet -b <Subnet Base> -m <Subnet Mask> -n

<Subnet Name> -s <Subnet Number> -o <V4 Gateway> -t

<Transport ID 1,Transport ID2>

ip_adm -a del_floating_ip -t <Service Type> -i <Pool ID> -s

<Subnet Number> -o <Offset>

ip_adm -a del_fixed_ip -t <Service Type> -i <Pool ID> -s

<Subnet Number> -o

<Offset>

> ip_adm -a add_subnet -b 192.168.104.0 -m 255.255.255.0 -n

mgmt -s 1 -o 254 -t ltf0,rtf0

> ip_adm -a commit

> ip_adm -a add_floating_ip -t cnfg -i 0 -s 1 -n default -o

Changing the SSH/SOL IP of hub 7/8 Procedure and useful commands for changing IPs

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



E-7



201

> ip_adm -a commit

> ip_adm -a add_floating_ip -t mi -i 0 -s 1 -n default -o

202

> ip_adm -a commit

> ip_adm -a add_fixed_ip -t mi -i 0 -s 1 -n default -o

203,204> ip_adm -a commit

Check /etc/hosts file to verify IP has changed.

Check network connectivity

Add NTP server

ntp_adm -a add -i < IP list with comma separated >

ntp_adm -a add -i 192.168.1.111,192.168.70.11

It will wait 10 min to sync the server(s).

Commit changes

ntp_adm –a commit

Check

> ntpconf_adm --action show_server

NTP server 192.168.1.111

NTP server 192.168.70.11

Make sure that MIs is working:

Need to stop & start MI to access MI

stopMI & startMI needed to run as lss (password lss)

Following the offical procedure to change/set Processor

Blade SOL/SSH IP.

DONE!

Grow 1 pair of ACCM on slot 5/6

Grow 1 ADCM on slot 4

Provision ed-atca-eqpt:

emf is up and running.

ACCM can't be accessible via EM IP.

DONE.

Changing the SSH/SOL IP of hub 7/8 Procedure and useful commands for changing IPs

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Appendix F: Software loads

from the factory

Software Loads

Summary

The following table shows the software loads from the factory for ShMC and Hub cards.

Card Version (or later)

ShMC 1.3.4-01_03_04_INT_02_LN 1.4.0

Hub 8BA504009018_Processor Blade_01_03_00_INT_FS_01 1.3.0/1

...................................................................................................................................................................................................................................



F-1



Software loads from the factory Software Loads

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

F-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Appendix G: Software ASLM

Overview

Purpose

This chapter describes how to use the Alcatel-Lucent Software License Management

(ASLM) tool to fulfill the license key requirements. ASLM provides the ability to activatefeature licenses and raise appropriate events when an entitlement violation takes place. A

license file is required to activate the new features or increase system capacity. Be sure to

complete the following tasks before using the ASLM tool:

• Purchase a software license(s) entitlement from Alcatel-Lucent through a purchase

order.

• Confirm with Alcatel-Lucent that the entitlements specified in your purchase order are

added/activated in the ASLM tool.

Contents

Base and session entitlements G-2

Accessing the ASLM tool G-5

Generating a license file G-7

...................................................................................................................................................................................................................................



G-1



Base and session entitlements

Overview

Base entitlement packages are available for both MGCF and IBCF calls, each of which

contains a limited number of sessions. An enhanced base entitlement package is availablefor MGCF. Growth packages are also available for both MGCF and IBCF to increase the

session capacity.

The following entitlements are available for MGC-8 software:

• Base software entitlement

Includes the right to use the MGC-8 Software. The license provides basic software

license support. This entitlement OR/AND base virtualization software entitlement is

mandatory.

• Base virtualization software entitlement

Includes the right to use the MGC-8 Virtualization Software. The license provides basic virtualization software license support. This entitlement OR/AND base software

entitlement is mandatory.

• MGCF base entitlement

The license provides support for the base MGCF license which supports up to 10000

sessions. This entitlement requires the Base Software Entitlement.

• MGCF enhanced base entitlement

The license provides support for the enhanced base MGCF license which supports up

to 10000 sessions. This entitlement requires the Base Software Entitlement

• IBCF base entitlement

The license provides support for the base IBCF license which supports up to 500

sessions. This entitlement requires the Base Software Entitlement.

By default, the MGC-8 operates as an MGCF. When purchasing this license, the

associated IBCF provisioning must also be done before IBCF sessions will be

allowed.

• MGCF session growth entitlement

The license provides support for an additional 1000 MGCF sessions. Up to 1000

MGCF growth packages may be purchased. This entitlement requires the MGCF Base

Entitlement.

• IBCF session growth entitlement

The license provides support for an additional 1000 IBCF sessions. Up to 1000

MGCF growth packages may be purchased. This entitlement requires the IBCF Base

Entitlement.

Software ASLM Base and session entitlements

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

G-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



• Optional packages

The following MGC-8 add-on packages are optional:

– Additional SS7 variant

– CDMA GMSC application package

– Class 4 Lawful Interception application package

– Enhanced ENUM-enabled services

– Enhanced IP exchange (IPX) routing

– External BICC

– FEMTO feature package

– Geo Redundancy Active/Active

– Geo Redundancy Active/Standby

– GSM GMSC application package

– IPv6 support package

– MGC-8 STP package

– SIP front end distributor

– Transcoding support and policy enforcement

– SIP Header/Messaging package

– TCAP based MWI package

– STP CIC Migration and PC Offload package

– 3RD Party Signalling Gateway support package

– ISDN PRA NNI services

– AUTO CALL BACK/CCBS/RBWF

Software license names and descriptions

The following table contains a list of the available software licenses:

Table G-1 Software license names and descriptions

Software license name Description

MGC8_base_sw Base software package

MGC8_base_ibcf Base IBCF package

MGC8_base_mgcf Base MGCF packageMGC8_enh_base_mgcf Enhanced Base MGCF package

MGC8_active_georedundancy Geo Redundancy Active/Active


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



G-3



Table G-1 Software license names and descriptions (continued)

MGC8_c4_lawful_int Class 4 Lawful Interception application

package

Note: This application package is applicable

to the MGC8 located outside of U.S.

MGC8_enh_ipx_routing Enhanced IP Exchange (IPX) Routing

MGC8_enum Enhanced ENUM-enabled services

MGC8_ext_bicc External BICC

MGC8_femto FEMTO feature package

MGC8_georedundancy Geo Redundancy Active/Standby

MGC8_gmsc_cdma CDMA GMSC application package

MGC8_gmsc_gsm GSM GMSC application package

MGC8_ipv6 IPv6 supportMGC8_sip_fed SIP Front End Distributor

MGC8_ss7_variant_addon Additional SS7 variant

MGC8_stp STP Functionality

MGC8_transcode Transcoding support and policy enforcement

MGC8_base_sw_virtual Base virtualization base software package

MGC8_sip_hdr_msg SIP Header Message package

MGC8_3rdparty_sg 3RD Party Signalling Gateway Support

package

MGC8_srvcs_isdn ISDN PRA NNI services

MGC8_tcap_mwi TCAP based MWI package

MGC8_stp_cic STP CIC Migration and PC Offload package

MGC8_auto_callback Automatic callback / CCBS / RBWF


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Accessing the ASLM tool

Procedure

...................................................................................................................................................................................................

1 Go to the ASLM home page. The URL is: (http://aslm.app.alcatel-lucent.com)

...................................................................................................................................................................................................

2 Note: If you already have a user name and password, skip Steps 2 and 3.

If you don't have access to ASLM, you will be directed to the ASLM home page:

...................................................................................................................................................................................................

3 In the ASLM homepage, click the link Click here .

Figure G-1 ASLM

Software ASLM Accessing the ASLM tool

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



G-5

http://aslm.app.alcatel-lucent.com/

http://aslm.app.alcatel-lucent.com/



Result: The Access Page appears as shown below:

...................................................................................................................................................................................................

4 Click the ASLM Access Request Guide, to request the access to the ASLM as per your role.

Figure G-2 ASLM Access Page

Software ASLM Accessing the ASLM tool

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015

E N D O F S T E P S...................................................................................................................................................................................................



Generating a license file

Procedure

Note: When an MGC-8 user performs an upgrade from a pre-9.0 release to a 9.0

release, a license must be installed. The license is required only when the newfunctionality added in a release needs to be activated. In release 9.0, MGC-8 had only

3 feature licenses (mgc8 base functionality, mgcf base functionality, and ibcf

functionality). In Release 9.1, many license types were added. As a result, an upgrade

from pre-9.1 to a 9.1 release requires installation of a new license to activate the new

features. For release 9.0 and later, the ATCA install/upgrade procedure always looks

for a license file. In the case of the 9.x to 9.x upgrade, the license would be auto

installed. This is the reason you see the SIM tool searching for a license file

There should be no alarms triggered that pertain to license installation after hot

upgrade completion. A license enforcement alarm will appear for any feature that is

invoked without an installed license. A new license may need to be installed if thedowngrade was done by installing an older release as opposed to downgrading the

MGC-8 from a backup. Downgrading is done by applying the backup saved prior to

the upgrade.

Note: Prior to upgrading to release 9.X.X or greater, the system identifier must be

obtained for each ATCA MGC-8 chassis for license generation. The retrieval method

varies based on the software release as follows:

• For releases prior to Release 8.3.0.3:

From the OS shell use hpi_util 169.254.64.240 get_serial_num

• For Release 8.3.0.3 and greater and Release 8.3.1:From TL1 use RTRV-INFO-CHASSIS parameter SERIALNUMBER

From MI

use/opt/LSS/sbin/sysidconf_adm --action show_system_id

parameter system ID

• For Release 9.0 and greater:

From TL1 use RTRV-ATCA-CHASSIS parameter SYSTEMID

...................................................................................................................................................................................................

1 The ASLM License Requestor Guide will guide you to generate a license key on theASLM platform. Download the document from the following link:

(http://libra.app.alcatel-lucent.com/PublicWorking/FileCard.aspx?Code=SWSC-ENT-L4-

27&MainModuleId=02DD8C9E-6542-4149-B36C-C7BCAC087E00&ProcessId=

d2bf14f0-d317-4500-8c6e-bff8ce830aa1)

Software ASLM Generating a license file

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



G-7

http://libra.app.alcatel-lucent.com/PublicWorking/FileCard.aspx?Code=SWSC-ENT-L4-27&MainModuleId=02DD8C9E-6542-4149-B36C-C7BCAC087E00&ProcessId=d2bf14f0-d317-4500-8c6e-bff8ce830aa1








...................................................................................................................................................................................................

2 Note: To avoid service interruption, install the license BEFORE the upgrade. The

license key can be automatically installed prior to the hot upgrade by placing the

license file MGC8LicenseFile.txt in the /storage/loads directory along with

the ALGPV2.ATCA.9.X.X.X.X.xxx.zip, ATCA.LCPXX.XX.xx.xx.zip, and

deftC_RXX.xx.xx_RXX.xx.xx.zip files (where RXX is the LCP version for thisrelease).

The license key can be manually installed prior to a hot upgrade (or a new install)

using the EXEC-SWLIC-INSTALL command. If a feature license key is not installed,

any provisioning relating to that feature is blocked. Refer to the following table for

examples:.

Required license

key name

Description Type of

enforce-

ment

TL1 command(s) affected

MGC8_active_

georedundancy

Geo

redundancy

active/active

Enforced at

provision

time

Reject ED-MGC-PROTN when

grMode is set to WORK_WORK,

protnType is DUPLEX, and the

feature license key is not installed.

MGC8_base_sw MGC-8 base

software

This

entitlement is

not enforced.

(This is a

mandatory

base license

to beordered).

None


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



MGC8_base_mgcf MGC-8

license for

base MGCF

call

capability

Note: This

entitlement

can no

longer be

ordered

through the

ASLM tool

and has been

replaced in

R9.1.0.1 and

onwards by

MGC8_enh_

base_mgcf

This

entitlement is

not enforced.

None

MGC8_enh_base_

mgcf

MGC-8

license for

base MGCF

call

capability

Enforced at

run-time

None

MGC8_base_ibcf MGC-8

license for

base IBCF

callcapability.

Enforced at

run-time

None

MGC8_session_ibcf Upper limit

for number

of standing

IBCF calls

through

MGC-8.

Enforced at

run-time

None

MGC8_session_

mgcf

Upper limit

for number

of standingMGCF calls

through

MGC-8.

Enforced at

run-time

None


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



G-9



MGC8_c4_lawful_

int

Class 4

lawful

interception

application

package

Enforced at

provision

Reject ENT-LI-TARGET/ED-LI-

TARGET/ENT-PRFL-CDCIP/ENT-

PRFL-CCCIP/ED-LIST-YGW/ENT-

LIST-YGW/ED-USER-LISECU/

ENT-USER-LISECU/STA-LI-X3/

STP-LI-X3/ED-LI-SYS when thefeature license key is not installed.

MGC8_enh_ipx_

routing

Enhanced IP

exchange

routing

support

Enforced at

provision

Reject ENT-PRFL-SIP/ED-PRFL-

SIP/ENT-PRFL-SIPT/ED-PRFL-

SIPT when 3xxhandling is set to

ADVANCED and the feature license

key is not installed.

MGC8_enum Enhanced

ENUM-

enabled

services

Enforced at

provision

Reject ED-ENUM-SYS when

PriEnumIP is set to a non-NULL

value and the feature license key is

not installed.MGC8_ext_bicc External

BICC

support

Enforced at

provision

Reject ENT/ED-BICC-TRK when

the feature license key is not

installed.

MGC8_femto FEMTO

feature

package

Enforced at

provision

Reject ENT/ED-TRKGRP When

sigType = IVT and the feature

license key is not installed.

MGC8_

georedundancy

Geo

redundancy

active/

standby

Enforced at

provision

Reject ED-MGC-PROTN when

grMode is set to WORK_PROTN,

protnType is DUPLEX and the


MGC8_gmsc_cdma CDMA

GMSC

application

package

Enforced at

provision

Reject ED-GMSC-ANSISYS when

slhrId is set to non-NULL value and


installed.

MGC8_gmsc_gsm GSM GMSC

application

package

Enforced at

provision

Reject ED-GMSC-GSMSYS when

slhrId is set to a non-NULL value

and the feature license key is not

installed.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



MGC8_ipv6 IPV6 support Enforced at

provision

Reject ENT/ED-ATCA-EQPT when


installed and the user specifies any

of the following parameters to be

non-NULL, including

sigAIPv6Fixed, sigAIPv6Floating,sigAIPv6NtwkPrefix,

sigBIPv6Fixed, sigBIPv6Floating

and sigBIPv6NtwkPrefix.

MGC8_sip_fed SIP front end

distributor

support

Enforced at

provision

Reject ENT/ED-SIP-FED when the


MGC8_ss7_variant_

addon

Additional

SS7 variant

support

Enforced at

provision

Reject ENT/ED-TRKGRP when the

user specifies sigType as ISUP and

with the execution of the current

TL1 command the total number of unique ISUP variants exceeds the

limit specified by the capacity

license key. Note: The first ISUP

variant is included with the purchase

of MGC8_base_sw. Therefore, the

enforcement of this entitlement is not

triggered when user provisions

TRKGRP with only one unique

ISUP variant across the whole

MGC-8.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



G-11



MGC8_stp STP

functionality

Enforced at

run-time

If the feature license key is not

installed, reject ED-STG-SYS when

a user specifies NODETYPE=STP,

and reject ED/ENT-STG-SCREENLSET,

ED/ENT-STG-SCREENPC,

ED/ENT-STG-SCREENALWSIO,

ED/ENT-STG-SCREENALCGPA,

ED/ENT-STG-SCREENALCDPA,

ED/ENT-STG-SCREENALWGTT,

ED/ENT-STG-SCREENAFPCSN,

ED/ENT-STG-SCREENAFFDST,

ENT-STG-GTTDEST,

ENT-STG-GTTMASK,

ENT-STG-GTTFIXED,

ENT-STG-GTTGTI,

ED/ENT-STG-MAPTTM,

ED/ENT-STG-MAPLSI,

ED/ENT-STG-MAPPCOFFLD, and

ED/ENT-STG-MAPGTLIST.

MGC8_transcode Transcoding

support and

policy

enforcement

Enforced at

run-time

Reject ENT-PRFL-SIP/ED-PRFL-

SIP/ENT-PRFL-SIPT/ED-PRFL-

SIPT when preferredCodec != ANY

or transCodePolicy=any value

except ANY or DIRECTCODEC and


installed.

MGC8_enh_base_

mgcf

Enhanced

MGC–8

license for

MGCF call

capability

Enforced at

run-time

None

MGC8_sip_hdr_

msg

SIP

Header/

Messaging

Package

This

entitlement is

not enforced.

None

MGC8_3rdparty_sg 3RD Party

SG support

package

This

entitlement is

not enforced.

None


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



MGC8_srvcs_isdn ISDN PRA

NNI services

Enforced at

run-time

None

MGC8_tcap_mwi TCAP based

MWI

package

Enforced at

provision

Reject ENT/ED-TREATMENT

when triggertype is 150 and the

feature license key is not installed

MGC8_stp_cic STP CIC

Migration

and PC

offload

Enforced at

provision

Reject ED-STG-SYS when

nodetype=stp and the feature license

key is not installed

MGC8_auto_

callback

Automatic

callback/

CCBS/

RBWF

Enforced at

provision.

Reject

ED-SERVICEACCESSCODE when

serviceID is set to CCBSIW and the


Note: If a violation of a software license occurs, an event is generated. The eventreturns the message “Software License Violation - Feature key update required to

enable entitlement <name>” where <name> is the name of the license. A violation

will occur when trying to use a feature that requires a license and the license has not

been purchased. A violation will occur when a user is upgrading from a release that

did not require a license key and is going to a release that now requires a license key

for a particular feature(s). A violation will also occur if the capacity that was

purchased for a particular feature(s) has been used/exceeded. If an event is generated,

confirm with Alcatel-Lucent that the entitlements specified in your purchase order are

added/activated in the ASLM tool.

When a call of type MGCF or IBCF is attempted, it is rejected with a correspondingfailure condition. For a list of failure conditions, use the TL1 command

RTRV-FAILCND.


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



G-13

E N D O F S T E P S...................................................................................................................................................................................................




....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



Issue 12 July 2015



Appendix H: Document issue

history

Overview

Purpose

This appendix provides the reference material for this document.

Reason for reissue

This appendix has been updated with the changes from previous issues of the document.

Contents

Reissue history H-1

Reissue history

Purpose

The reissue history of this document is described in the following paragraphs.

Issue 11

The reissue history for Issue 11 is shown in the following table.

Table H-1 Issue 11, April 2015, Reason for reissue


11 Added note for BTS upgrade Chapter 11, Upgrade scenarios

and procedures

Updated procedures in Rollback of LCP

and MGC-8 software, Backout of LCP

and MGC-8 upgrade, and Backout

MGC-8 only upgrade

Chapter 13, Rollback and

backout procedures

...................................................................................................................................................................................................................................



H-1



Issue 10


Table H-2 Issue 10, March 2015, Reason for reissue


10 Added the topic Provisioning support

during upgrade when GR MGC-8s are

on different releases

Chapter 11, Upgrade scenarios

and procedures

Updated the Note for Provisioning

support during upgrade when GR

MGC-8s are on different releases

Chapter 12, Upgrade

working-working geographic

redundant switches

Issue 9


Table H-3 Issue 9, January 2015, Reason for reissue


9 Updated the document to remove the

specific LCP version.

Global

Added step 8 under the Load transfer

and field install procedure which

indicates to remove the usb flash drive.

Chapter 5

Issue 8


Table H-4 Issue 8, December 2014, Reason for reissue


8 Updated the Upgrade both the LCP

software and the ALGPv2 software and

the Upgrade the ALGPv2 software

procedure.

Chapter 11, Upgrade scenarios

and procedures

Updated the Backout of LCP and

MGC-8 upgrade and Backout MGC-8

only upgrade procedures

Chapter 13, Rollback and

backout procedures

Document issue history Reissue history

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

H-2 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Issue 7


Table H-5 Issue 7, November 2014, Reason for reissue


7 Updated the field installation procedure Chapter 4, Load transfer and

field installation procedure

Added new chapter System

Configuration

Chapter 2, System

configuration

Updated the front matter as per the

content standards

Global

Issue 6


Table H-6 Issue 6, October 2014, Reason for reissue


6 Removed the re-login comment Chapter 11, under the Update

the server section

Added step 10 to verify the prompt mode

for TL1

Chapter 11, under the Upgrade

the ALGPv2 software section.

Replaced LKDI with ASLM and added

the software license names in Table G-1and the license enforcement table on

page G-16.

Appendix G

Issue 5


Table H-7 Issue 5, June 2014, Reason for reissue


5 Revised license key table to include the

“type of enforcement.”

Appendix G


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



H-3



Issue 4


Table H-8 Issue 4, May 2014, Reason for reissue


4 Minor content corrections. Global

Issue 3




3 Removed empty tags Global

Issue 2




2 Bundled three 5400 Linux Control

Platform documents with this document.

The LCP documents are cross referencedfrom this document.

Global

Issue 1




1 First issue of the document Global


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

H-4 Alcatel-Lucent – ProprietaryUse pursuant to applicable agreements


Issue 12 July 2015



Index

A ACCM and ADCM blades, 9-2

ALGPv2 and LCP

upgrading procedures, 11-1

ALGPv2 blades

growth and de-growth procedures, 8-1

provisioning procedures, 9-1

AMC SS7 cards

provisioning procedures, 9-9

ASLM

See: Alcatel-Lucent Software

License Management

access, G-5

entitlements, G-2

license files, G-7

.............................................................

C configure blade

OAM server A functionality,

6-1

.............................................................

L LCP installation

configuration worksheets, B-1

procedures, 3-1

load installation and LCP check

procedures, 7-1

load transfer and pre-installation,

5-1

.............................................................

M MGC-8

rollback and backout

procedures, 13-1

MGC-8 ATCA

ATCA, 1-1

hardware and software

requirements, 1-2

upgrade working-working GR

switches, 12-1

.............................................................

S system configuration, 2-1

....................................................................................................................................................................................................................................



IN-1



Index

....................................................................................................................................................................................................................................

Rapport MGC-8 ATCA Install and Upgrade Guide.pdf

Documents