You are on page 1of 338

Use pursuant to applicable agreements

Title page

Alcatel-Lucent 5400
Linux Control Platform | Release 4.0
Supports 5450 ISC R20.1, 5420 CTS R7.1, 5420 SCG 7.x, 5060 ICS R2.1, 5060
MGC8 8.1, 9290 MM-SI R22, 9471 MME LM2.1
Configuration Management

CONFIGURATION MANAGEMENT
270-702-014R4.0
Alcatel-Lucent – Proprietary
Use pursuant to applicable agreements
ISSUE 4
MARCH 2011
Use 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 © 2011 Alcatel-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.

Notice

Every effort has been made to ensure that the information contained in this information product was accurate at the time of printing. However, information is
subject to change.

The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide
basis.
PICMG, the AdvancedTCA name and logos, the ATCA name and logo, and the PICMG logo are registered trademarks of the PCI Industrial Computers
Manufacturers Group.
The AdvancedMC name and logo are trademarks of the PCI Industrial Computers Manufacturers Group.

Conformance statements

Refer to Appendix B, “Conformance statements”

Security statement

In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event,
applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any
allowance or give any credit for charges that result from unauthorized access.

Limited warranty

For terms and conditions of sale, contact your Alcatel-Lucent Account Team.

Licences

Refer to Alcatel-Lucent 5400 Linux Control Platform Free and Open Source Software Copyright Notice and Licenses, 270-702-028.

Developed by Alcatel-Lucent.

Alcatel-Lucent – Proprietary
Use pursuant to applicable agreements
Contents

About this document


Purpose .......................................................................................................................................................................................... xiii
xiii

Reason for revision ................................................................................................................................................................... xiii


xiii

Safety information ..................................................................................................................................................................... xvi


xvi

Intended audience ...................................................................................................................................................................... xvi


xvi

How to use this document ....................................................................................................................................................... xvi


xvi

Conventions used ...................................................................................................................................................................... xvii


xvii

Systems supported .................................................................................................................................................................... xvii


xvii

Related documentation ........................................................................................................................................................... xvii


xvii

How to order ............................................................................................................................................................................. xviii


xviii

Technical support ..................................................................................................................................................................... xviii


xviii

Document support ................................................................................................................................................................... xviii


xviii

How to comment ..................................................................................................................................................................... xviii


xviii

1 5400 Linux CP configuration

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


1-1

The 5400 Linux CP characteristics ..................................................................................................................................... 1-2


1-2

2 Required 5400 Linux CP Services

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


2-1

Introduction ................................................................................................................................................................................. 2-2


2-2

CNFG service ............................................................................................................................................................................. 2-3


2-3

MI service .................................................................................................................................................................................... 2-5


2-5

3 Manage system configuration - MI-GUI procedures

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


3-1
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary iii
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Contents

....................................................................................................................................................................................................................................
Provision the MI-GUI

Overview ...................................................................................................................................................................................... 3-3


3-3

To add, modify, or delete the SNE(s) for MI-GUI discovery ................................................................................... 3-4
3-4

To display or change the local title on the MI-GUI ...................................................................................................... 3-8


3-8

Configure MI-GUI as SNMP-based NBI to monitor alarms

Overview ...................................................................................................................................................................................... 3-9


3-9

Northbound Interface task flow ........................................................................................................................................ 3-10


3-10

To load Northbound Interface MIB at the MI-GUI ................................................................................................... 3-12


3-12

To select MIB version ........................................................................................................................................................... 3-14


3-14

To configure Northbound Interface manager ............................................................................................................... 3-15


3-15

To reconstruct lost traps ....................................................................................................................................................... 3-18


3-18

Supported NBI traps/notifications (MIB version 2) .................................................................................................. 3-21


3-21

To configure the MIB browser for NBI access via SNMPv3 ................................................................................. 3-28
3-28

To clone a user for SNMPv3 from MI CLI ................................................................................................................... 3-30


3-30

Discovery and growth using the MI-GUI

Overview ................................................................................................................................................................................... 3-32


3-32

Description of discovery, growth/degrowth ................................................................................................................. 3-33


3-33

Global rediscovery using the MI-GUI ........................................................................................................................... 3-37


3-37

Global rediscovery using the MI-GUI's CLI ................................................................................................................ 3-38


3-38

Explicit rediscovery using the MI-GUI .......................................................................................................................... 3-40


3-40

Explicit rediscovery using the MI-GUI's CLI .............................................................................................................. 3-41


3-41

To enable the auto-delete option during discovery .................................................................................................... 3-42


3-42

Discovery degrowth using the MI-GUI ........................................................................................................................ 3-43


3-43

Discovery degrowth using the MI-Agents CLI ........................................................................................................... 3-44


3-44

Inventory management

Overview ................................................................................................................................................................................... 3-46


3-46

....................................................................................................................................................................................................................................
iv Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Contents

....................................................................................................................................................................................................................................
MI-GUI inventory management ....................................................................................................................................... 3-47
3-47

4 Manage system configuration - view or control the operational state

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


4-1

View or control the operational state

Overview ...................................................................................................................................................................................... 4-2


4-2

To display the current state of the MI Virtual Cluster ................................................................................................. 4-3


4-3

To display the current state of a MI Virtual Machine .................................................................................................. 4-4


4-4

To start the MI Virtual Cluster ............................................................................................................................................. 4-5


4-5

To start a MI Virtual Machine .............................................................................................................................................. 4-6


4-6

To stop the MI Virtual Cluster .............................................................................................................................................. 4-7


4-7

To stop a MI Virtual Machine .............................................................................................................................................. 4-8


4-8

To switch states of MI Virtual Machines in Virtual Cluster ...................................................................................... 4-9


4-9

To modify the state of a diskless host ............................................................................................................................. 4-10


4-10

5 Manage system configuration - hardware growth

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


5-1

Growth

Overview ...................................................................................................................................................................................... 5-3


5-3

Growth introduction ................................................................................................................................................................. 5-4


5-4

Growth process stages ............................................................................................................................................................. 5-5


5-5

Growth planning

Overview ...................................................................................................................................................................................... 5-6


5-6

Growth planning process ....................................................................................................................................................... 5-7


5-7

To verify minimal system requirements ........................................................................................................................... 5-8


5-8

To verify hardware version and test acceptance ............................................................................................................ 5-9


5-9

Growth system preparation

Overview ................................................................................................................................................................................... 5-10


5-10

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary v
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Contents

....................................................................................................................................................................................................................................
Growth system preparation process ................................................................................................................................. 5-11
5-11

To install new hardware ....................................................................................................................................................... 5-12


5-12

To cable new hardware ......................................................................................................................................................... 5-13


5-13

To verify growth system stability ..................................................................................................................................... 5-15


5-15

To install Ethernet transport connections between HSPP4 face plate and the external network
equipment .......................................................................................................................................................................... 5-17
5-17

Growth setup

Overview ................................................................................................................................................................................... 5-19


5-19

Growth setup process ............................................................................................................................................................ 5-20


5-20

To verify disk space availability for backup ................................................................................................................. 5-21


5-21

To perform full system backup .......................................................................................................................................... 5-22


5-22

To verify the success of backup ........................................................................................................................................ 5-23


5-23

Growth implementation

Overview ................................................................................................................................................................................... 5-24


5-24

Growth implementation process ....................................................................................................................................... 5-25


5-25

To grow hardware and service on diskless hosts ........................................................................................................ 5-27


5-27

To grow hardware and service on diskful hosts .......................................................................................................... 5-39


5-39

To jumpstart diskful card ..................................................................................................................................................... 5-51


5-51

To establish a processor card SOL session .................................................................................................................... 5-53


5-53

To grow service of diskless hosts for multiple services ........................................................................................... 5-54


5-54

To grow RTM with disk on an existing diskful host ................................................................................................. 5-60


5-60

Serial port setup through faceplate

Overview ................................................................................................................................................................................... 5-63


5-63

To determine the serial port configured in laptop ....................................................................................................... 5-64


5-64

To configure laptop for serial connection on Windows XP .................................................................................... 5-66


5-66

To establish serial port connection on the laptop ........................................................................................................ 5-68


5-68

....................................................................................................................................................................................................................................
vi Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Contents

....................................................................................................................................................................................................................................
6 Manage system configuration - hardware de-growth

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


6-1

Degrowth implementation

Overview ...................................................................................................................................................................................... 6-2


6-2

De-growth implementation flow ......................................................................................................................................... 6-3


6-3

To de-grow service of multiple services on diskless hosts ........................................................................................ 6-4


6-4

To de-grow hardware and service on diskless/diskful hosts .................................................................................... 6-9


6-9

7 Platform hardware conversion

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


7-1

To convert Rouzic OAM server to Molene2 OAM server ........................................................................................ 7-2


7-2

To convert Malban with HSPP4 to Malban without HSPP4 ................................................................................. 7-16


7-16

To convert Hub without HSPP4 to Hub with HSPP4 ............................................................................................... 7-25


7-25

To convert Disk Schema ...................................................................................................................................................... 7-37


7-37

8 Manage system configuration - IP configuration

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


8-1

Internal IP addresses and subnets

Overview ...................................................................................................................................................................................... 8-3


8-3

Internal IP subnetworks ......................................................................................................................................................... 8-4


8-4

Hardware-related subnetworks and IP addressing ........................................................................................................ 8-7


8-7

Service-related subnetwork and IP addressing ............................................................................................................ 8-15


8-15

DNS and ENUM in the 5400 Linux CP

Overview ................................................................................................................................................................................... 8-17


8-17

Domain Name System (DNS) ........................................................................................................................................... 8-18


8-18

To add a 5400 Linux CP DNS domain or server ........................................................................................................ 8-24


8-24

5400 Linux CP DNS administration ................................................................................................................................ 8-26


8-26

Telephone Numbering Mapping (ENUM) .................................................................................................................... 8-28


8-28

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary vii
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Contents

....................................................................................................................................................................................................................................
To add a 5400 Linux CP ENUM remote or local server .......................................................................................... 8-30
8-30

To add or delete 5400 Linux CP ENUM domain and server .................................................................................. 8-32
8-32

To verify 5400 Linux CP DNS local query ................................................................................................................... 8-34


8-34

To check the status of 5400 Linux CP DNS processes ............................................................................................. 8-36


8-36

IP address and route configuration

Overview ................................................................................................................................................................................... 8-37


8-37

To add a new external IPv4 subnet .................................................................................................................................. 8-38


8-38

To delete an external IPv4 subnet ..................................................................................................................................... 8-40


8-40

To add a new external IPv6 subnet .................................................................................................................................. 8-42


8-42

To delete an external IPv6 subnet ..................................................................................................................................... 8-44


8-44

To add a new external fixed IPv4 address ..................................................................................................................... 8-46


8-46

To delete an external fixed IPv4 address ....................................................................................................................... 8-48


8-48

To add a new external floating IPv4 address ................................................................................................................ 8-50


8-50

To delete an external floating IPv4 address .................................................................................................................. 8-52


8-52

To add a new external fixed IPv6 address ..................................................................................................................... 8-54


8-54

To delete an external fixed IPv6 address ....................................................................................................................... 8-56


8-56

To add a new external floating IPv6 address ................................................................................................................ 8-58


8-58

To delete an external floating IPv6 address .................................................................................................................. 8-60


8-60

To add or delete static routes for a service .................................................................................................................... 8-62


8-62

To modify the IP addresses of a Network Interface ................................................................................................... 8-67


8-67

To modify the Default Gateway data for a service ..................................................................................................... 8-71


8-71

To set port speeds of hub-based transport interfaces ................................................................................................. 8-75


8-75

NTP servers and time zone

Overview ................................................................................................................................................................................... 8-76


8-76

To add or delete remote NTP servers IP addresses .................................................................................................... 8-77


8-77

To change the time zone ...................................................................................................................................................... 8-79


8-79

....................................................................................................................................................................................................................................
viii Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Contents

....................................................................................................................................................................................................................................
A Command descriptions

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


A-1

Hazard statements

Structure of safety statements ............................................................................................................................................. A-2


A-2

Common cautions and warnings ........................................................................................................................................ A-4


A-4

Command descriptions

lss_adm ........................................................................................................................................................................................ A-6


A-6

su_health ..................................................................................................................................................................................... A-8


A-8

create_ht .................................................................................................................................................................................... A-10


A-10

sim ............................................................................................................................................................................................... A-11


A-11

grow ............................................................................................................................................................................................ A-13


A-13

degrow ....................................................................................................................................................................................... A-14


A-14

dns_adm .................................................................................................................................................................................... A-15


A-15

ip_adm ....................................................................................................................................................................................... A-18


A-18

ntp_adm .................................................................................................................................................................................... A-20


A-20

tz_adm ....................................................................................................................................................................................... A-21


A-21

enum_adm ................................................................................................................................................................................ A-22


A-22

B Conformance statements

5400 Linux CP compliance summary ............................................................................................................................... B-1


B-1

Eco-environmental statements ............................................................................................................................................ B-2


B-2

Glossary

Index

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary ix
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Contents

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

....................................................................................................................................................................................................................................
x Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
List of figures

3-1 Node Discovery .......................................................................................................................................................... 3-7


3-7

3-2 MIB Manager .......................................................................................................................................................... 3-13


3-13

3-3 Inventory Report ...................................................................................................................................................... 3-49


3-49

3-4 Generate Inventory Report .................................................................................................................................. 3-50

3-5 View Inventory Report .......................................................................................................................................... 3-51

3-6 Display Inventory Report ..................................................................................................................................... 3-52

5-1 HSPP4 Ethernet connections to the router ..................................................................................................... 5-17

8-1 Add a IPv4 static route: ........................................................................................................................................ 8-66

8-2 Add a IPv6 static route .......................................................................................................................................... 8-66

8-3 Network Interface ................................................................................................................................................... 8-70


8-70

8-4 Default Gateway ...................................................................................................................................................... 8-73


8-73

8-5 Modify Default Gateway ...................................................................................................................................... 8-74

B-1 Electronic products symbol ................................................................................................................................... B-3

B-2 Batteries symbol ........................................................................................................................................................ B-3


B-3

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary xi
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
List of figures

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

....................................................................................................................................................................................................................................
xii Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
About this document
About this document

Purpose
The purpose of this document is to:
• Give a conceptual background on configuration management functionality provided
by the 5400 Linux CP.
• Present an overview of how configuration management is performed for the 5400
Linux CP.

Reason for revision


Information that is added, deleted, or changed in this release is summarized in this notice.

Issue Month Reason for Topics impacted


reissue
Issue 1 June 2010 Initial version for The following chapter has been added:
Release 4.0 • Chapter 7, “Platform hardware
conversion”
The following topics have been updated:
• “To grow hardware and service on
diskless hosts” (p. 5-27)
• “To grow hardware and service on
diskful hosts” (p. 5-39)
• “To grow RTM with disk on an
existing diskful host” (p. 5-60)
• “To de-grow service of multiple
services on diskless hosts” (p. 6-4)
• “To de-grow hardware and service on
diskless/diskful hosts ” (p. 6-9)

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary xiii
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
About this document

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

Issue Month Reason for Topics impacted


reissue

• “To add or delete static routes for a


service” (p. 8-62)
• “To display or change the local title
on the MI-GUI” (p. 3-8)
• “To start the MI Virtual Cluster”
(p. 4-5)

Issue 2 October 2010 Updated for The following topics have been added:
corrections and • “To delete an external IPv4 subnet”
addition of (p. 8-40)
information.
• “To delete an external IPv6 subnet”
(p. 8-44)
• “To delete an external fixed IPv4
address” (p. 8-48)
• “To delete an external fixed IPv6
address” (p. 8-56)
• “To delete an external floating IPv4
address” (p. 8-52)
• “To delete an external floating IPv6
address” (p. 8-60)

The following topics have been updated:


• “Global rediscovery using the
MI-GUI ” (p. 3-37)
• “To add a new external fixed IPv4
address” (p. 8-46)
• “To add a new external floating IPv4
address” (p. 8-50)

• “To add a new external IPv4 subnet”


(p. 8-38)
• “To add a new external fixed IPv6
address” (p. 8-54)
• “To add a new external floating IPv6
address” (p. 8-58)

....................................................................................................................................................................................................................................
xiv Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
About this document

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

Issue Month Reason for Topics impacted


reissue

• “To add a new external IPv6 subnet”


(p. 8-42)
• “To delete an external IPv4 subnet”
(p. 8-40)
• “To delete an external IPv6 subnet”
(p. 8-44)

• “To delete an external fixed IPv4


address” (p. 8-48)
• “To delete an external fixed IPv6
address” (p. 8-56)
• “To delete an external floating IPv4
address” (p. 8-52)
• “To delete an external floating IPv6
address” (p. 8-60)

The following topics have been added:


• “To install Ethernet transport
connections between HSPP4 face
plate and the external network
equipment” (p. 5-17)
• “To convert Malban with HSPP4 to
Malban without HSPP4 ” (p. 7-16)
• “To convert Hub without HSPP4 to
Hub with HSPP4” (p. 7-25)

The following topic has been updated:


• “To install Ethernet transport
connections between HSPP4 face
plate and the external network
equipment” (p. 5-17)
• “To configure Northbound Interface
manager” (p. 3-15)

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary xv
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
About this document

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

Issue Month Reason for Topics impacted


reissue
Issue 3 December Updated for Updated the following topics:
2010 corrections and • “To grow hardware and service on
addition of diskful hosts” (p. 5-39)
information.
• “To de-grow hardware and service on
diskless/diskful hosts ” (p. 6-9)
• “To convert Disk Schema” (p. 7-37)

Issue 4 March 2011 Updated for The following topics have been updated:
corrections and • “To establish a processor card SOL
addition of new session” (p. 5-53)
information
• “To convert Rouzic OAM server to
Molene2 OAM server” (p. 7-2)
• “To de-grow hardware and service on
diskless/diskful hosts ” (p. 6-9)

Safety information
For your safety, this document contains safety statements. Safety statements are given at
points where risks of damage to personnel, equipment, and operation may exist. Failure to
follow the directions in a safety statement may result in serious consequences.

Intended audience
The audience for this document is:
• 5400 Linux CP maintenance technician
• 5400 Linux CP maintenance specialist
• 5400 Linux CP operator
• 5400 Linux CP administrator

How to use this document


This document is intended to be used:
• as the first reference for all 5400 Linux CP (FCAPS) tasks
• in conjunction with the Alcatel-Lucent application documentation.
To solve these tasks may require the access to specific vendor documents, which are
referred in the different procedures.

....................................................................................................................................................................................................................................
xvi Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
About this document

....................................................................................................................................................................................................................................
Conventions used
The following summarizes presentation conventions.

Convention Information Type


output A system output message
cd /bin A command entered by the user
Enter Keyboard entries
<IP Address> Variable parameters
filename File name
Tools->Discovery User interface string

Systems supported
This version of the document applies to 5400 Linux CPind Release 4.0.

Related documentation
• Alcatel-Lucent 5400 Linux Control Platform System Guide, 270-702-011
• Alcatel-Lucent 5400 Linux Control Platform Hardware Description, 270-702-012
• Alcatel-Lucent 5400 Linux Control Platform User Interface, 270-702-013
• Alcatel-Lucent 5400 Linux Control Platform Configuration Management,
270-702-014
• Alcatel-Lucent 5400 Linux Control Platform Security Management, 270-702-015
• Alcatel-Lucent 5400 Linux Control Platform Performance Management, 270-702-016
• Alcatel-Lucent 5400 Linux Control Platform Observation Counters Dictionary,
270-702-017
• Alcatel-Lucent 5400 Linux Control Platform Log Management, 270-702-018
• Alcatel-Lucent 5400 Linux Control Platform Alarm Management, 270-702-020
• Alcatel-Lucent 5400 Linux Control Platform Alarm Dictionary, 270-702-021
• Alcatel-Lucent 5400 Linux Control Platform Software Corrective Maintenance,
270-702-022
• Alcatel-Lucent 5400 Linux Control Platform Hardware Corrective Maintenance,
270-702-023
• Alcatel-Lucent 5400 Linux Control Platform Software Preventive Maintenance,
270-702-024
• Alcatel-Lucent 5400 Linux Control Platform Hardware Preventive Maintenance,
270-702-025
• Alcatel-Lucent 5400 Linux Control Platform Free and Open Source Software
Copyright Notice and Licenses, 270-702-028
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary xvii
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
About this document

....................................................................................................................................................................................................................................
How to order
To order Alcatel-Lucent documents contact your local sales representative or use Online
Customer Support (OLCS) (https://support.alcatel-lucent.com).

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.

Document support
For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
one of the following telephone numbers:
1-888-582-3688 (for all United States)
1-317-377-8618 (for all other countries)

How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/enus/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).

....................................................................................................................................................................................................................................
xviii Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
1 1400 Linux CP
5
configuration

Overview
Purpose
This chapter provides an introduction to the 5400 Linux CP. This information can be used
as a selection criteria to determine which kind of configuration procedures are included in
this documentation part.

Contents

The 5400 Linux CP characteristics 1-2

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 1-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
5400 Linux CP configuration The 5400 Linux CP characteristics

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

The 5400 Linux CP characteristics


Supported solutions
The 5400 Linux CP is supported in the following Alcatel-Lucent solutions:
• The 5450 ISC/IRC, CTS used in IP Multimedia Sub-system (IMS).
• The Voice over IP (VoIP) / Internet Call Diversion (ICD) solution.

The 5400 Linux CP configuration


The 5400 Linux CP hardware has a single 44U cabinet configuration for the CP 2.1
applications (e.g., 5450 ISC/IRC, 5420 CTS, 5060 ICS). It supports one or two ATCA ®
shelves with side-by-side blade redundancy. For a multi-shelf configuration, shelf 0 is the
bottom most shelf.

1-Shelf CP (1CP) configuration


The 1-Shelf CP (1CP) configuration consists of a minimally-configured shelf within a
cabinet containing the Fixed Items shown in the table below. Fixed items are groups as a
single Orderable Item, with Variable Items added to support an application and customer
specific engineered capacity. The Variable Items are installed on-site. Node processor
blades are grown in pairs, but ordered individually. The Alcatel-Lucent OmniSwitch 6850
with 48 ports OS-6850-48 is grown in pairs and can only be installed at the time of initial
site installation.

Fixed Items Quantity

SHMC Board (NBSHMC) 2


Hub-Switch 1G (NBMASW1) 2
OAM Server (NBRZAL) 2
Traffic Blades (NBRZAL) 0
Rear Filler (NAFILL) 12

Variable/Loose-Ship Items Quantity

Traffic Blades (NBRZAM) 2-10

Database Server (NBRZAL) 0-2

Front Filler (NBFILL) 0-8


OS-6850-48 0-2

....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
5400 Linux CP configuration The 5400 Linux CP characteristics

....................................................................................................................................................................................................................................
2-Shelf CP (2CP) configuration
The 2-Shelf CP (2CP) configuration consists of two shelves within a cabinet with
side-by-side blade redundancy. It consists of a 1CP configuration plus a minimally
configured second shelf which has a pair of Hub-Switch 1G cards, a pair of SHMC
boards, and a pair of Hub RTMs.

Fixed Items Quantity

SHMC Board (NBSHMC) 4

Hub-Switch 1G (NBMASW1) 4
Hub RTM (NASYS) 4

OAM Server (NBRZAL) 2


Traffic Blades (NBRZAL) 0

Rear Filler (NAFILL) 24

Variable/Loose-Ship Items Quantity

Traffic Blades (NBRZAM) 2-22


Database Server (NBRZAL) 0-4
Front Filler (NBFILL) 0-20
OS-6850-48 0-2

Hardware description
For a detailed description of the 5400 Linux CP hardware, refer to: Alcatel-Lucent 5400
Linux Control Platform Hardware Description, 270-702-012.

Covered topics
In this documentation part all procedures are included that are directly related to
performing Configuration Management tasks on the 5400 Linux CP hardware.
These procedures include the following types of tasks:
• Growing and de-growing 5400 Linux CP hardware
• Adding or deleting hardware under the control of the Configuration Server
• Performing software management
• Control the operational state of the 5400 Linux CP hardware.
Note: For all the procedures that are related to configuring the 5400 Linux CP to create a
certain solution, refer to the relevant Configuration Management documentation parts.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 1-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
5400 Linux CP configuration The 5400 Linux CP characteristics

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

....................................................................................................................................................................................................................................
1-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
2 2equired 5400 Linux CP
R
Services

Overview
Purpose
This section describes the services that are required as the basic building blocks in order
to have an operational 5400 Linux CP.
These services are application-independent and should be available for all of the 5400
Linux CP-related products.

Contents

Introduction 2-2
CNFG service 2-3
MI service 2-5

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 2-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Required 5400 Linux CP Services Introduction

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

Introduction
Required services
The following services need to be available in order to create an operational 5400 Linux
CP:
• Configuration (CNFG) service
• Management Interface service.

....................................................................................................................................................................................................................................
2-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Required 5400 Linux CP Services CNFG service

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

CNFG service
Introduction
When a redundant pair of hosts are associated with the Configuration (CNFG) service the
following services are provided:
• Provides the configuration database(s) and Provisioning GUI interfaces
• Collects alarms from all diskless/diskful servers and forwards them to the MI Server
• Collects Performance Management data from all the 5400 Linux CP servers
• Provides services for diskful and diskless servers
• Operates as a LogServer
• Provides the REM system monitor function

Provisioning GUI
The Provisioning GUI provides access to Windows-based clients to perform
Configuration Management on the 5400 Linux CP.
Examples of Configuration Management tasks that can be performed using the
Provisioning GUI are:
• Configuring hardware
• Setting up dialing plans
• Configuring routing information

Alarm forwarding to the MI host


The CNFG host collects all alarms that are generated on the diskful and diskless servers
and forwards these alarms as SNMP messages to the MI host.

Performance measurement forwarding to the MI host


The CNFG host collects all performance measurements that are generated on the 5400
Linux CP applications and allows these collected measurements to be downloaded by the
MI host.

Additional services
Examples of other services that are provided by the CNFG host are:
• Provides the interface for XML bulk provisioning
• Provides CALEA / Lawful Intercept interface
• Streams a subset of the log messages to the MI for the call trace capability
• Provides the SIP trace capability
• Performs system audits
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 2-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Required 5400 Linux CP Services CNFG service

....................................................................................................................................................................................................................................
Logserver function
The CNFG host will function as the logfile server for the other 5400 Linux CP
applications.

REM System monitor function


The system monitor function of the Redundancy Manager (REM) is in control of the
operational states (active/standby) of all the diskless Processor cards.

Characteristics
The following characteristics are applicable for the hosts providing the CNFG service:
• Runs under RCC reliability control
• Requires a 1 + 1 redundancy

....................................................................................................................................................................................................................................
2-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Required 5400 Linux CP Services MI service

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

MI service
Introduction
The Management Interface (MI) service provides the main maintenance interface to
perform Operations, Administration, Maintenance and Provisioning tasks on the 5400
Linux CP and its related sub-network elements.

MI Server functions
When a redundant pair of hosts are associated with the MI service the following services
are provided:
• An SNMP manager function
• An HTTP-based webserver to maintain the 5400 Linux CP and its related
sub-network elements
• The Northbound interface to other Element or Network Sub Systems
• Provides the network timing
• Provides the service DNS.

SNMP Manager function


The Simple Network Management Protocol (SNMP) manager function allows the MI
host to collect fault and performance management information about the 5400 Linux CP
and the related sub-network elements.
Depending on the system configuration SNMP information can be collected for the
following elements:
• The 5400 Linux CP
• Other external elements

Management interface
The MI host provides a web browser interface to http based clients, which is referred to as
the MI-GUI.
Examples of tasks that can be performed on the MI-GUI are:
• Monitor the alarms of the 5400 Linux CP and the related sub-network elements
• Collect and analyze performance management data from the 5400 Linux CP and the
related sub-network elements

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 2-5
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Required 5400 Linux CP Services MI service

....................................................................................................................................................................................................................................
• Provide a “cut-through” option to the following user interfaces:
– The Provisioning GUI
– Command Line (CLI) access (to access to the 5400 Linux CP and the related
sub-network elements).
• Provides backup and restore functions for the 5400 Linux CP and related sub-network
elements.

Northbound Interface
The Northbound interface allows the OAM server to exchange network information with
the network management systems in the Network Management Layer.

Network Time Protocol


Network Time Protocol (NTP) is an Internet standard protocol that is used to synchronize
computer clock times in a network of computers. In common with similar protocols, NTP
uses Coordinated Universal Time (UTC) to synchronize computer clock times to a
millisecond, and sometimes to a fraction of a millisecond.

NTP configuration
All timing for the diskful and diskless hosts in 5400 Linux CP is derived from the OAM
server. OAM server derives its timing from the external NTP server located in the
customer's network.

MI-GUI as NTP server


Benefits of pointing to the MI host as NTP server:
• Timestamps applied to events are synchronized among the MI-GUI and the individual
components. For example, in case of the TAS, the timestamps of the MI host recorded
events (via the SNMP interface to the TAS) can be used to help correlate to events
recorded in the TAS logs.
• If, for some reason, the primary NTP server needs to be changed, only the MI host
would need to be re-configured to move it to the new NTP server instead of having to
re-configure every 5400 Linux CP component.

Characteristics
The following characteristics are applicable for a hosts providing the MI service:
• Runs under RCC reliability control
• Requires a 1 + 1 redundancy.

....................................................................................................................................................................................................................................
2-6 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
3 3 anage system
M
configuration - MI-GUI
procedures

Overview
Purpose
This chapter contains the Configuration Management related procedures that can be
performed on the 5400 Linux CP using the MI-GUI.

Contents

Provision the MI-GUI 3-3


To add, modify, or delete the SNE(s) for MI-GUI discovery 3-4
To display or change the local title on the MI-GUI 3-8
Configure MI-GUI as SNMP-based NBI to monitor alarms 3-9
Northbound Interface task flow 3-10
To load Northbound Interface MIB at the MI-GUI 3-12
To select MIB version 3-14
To configure Northbound Interface manager 3-15
To reconstruct lost traps 3-18
Supported NBI traps/notifications (MIB version 2) 3-21
To configure the MIB browser for NBI access via SNMPv3 3-28
To clone a user for SNMPv3 from MI CLI 3-30
Discovery and growth using the MI-GUI 3-32
Description of discovery, growth/degrowth 3-33
Global rediscovery using the MI-GUI 3-37
Global rediscovery using the MI-GUI's CLI 3-38
Explicit rediscovery using the MI-GUI 3-40
Explicit rediscovery using the MI-GUI's CLI 3-41

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Overview

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

To enable the auto-delete option during discovery 3-42


Discovery degrowth using the MI-GUI 3-43
Discovery degrowth using the MI-Agents CLI 3-44
Inventory management 3-46
MI-GUI inventory management 3-47

....................................................................................................................................................................................................................................
3-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Overview
Provision the MI-GUI
....................................................................................................................................................................................................................................

Provision the MI-GUI

Overview
Purpose
This section provides an overview of the role the MI-GUI plays in configuration
management, and provides guidelines for provisioning the MI-GUI to ensure it can
communicate with other sub network elements.

Contents

To add, modify, or delete the SNE(s) for MI-GUI discovery 3-4


To display or change the local title on the MI-GUI 3-8

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To add, modify, or delete the SNE(s) for MI-GUI discovery
Provision the MI-GUI
....................................................................................................................................................................................................................................

To add, modify, or delete the SNE(s) for MI-GUI discovery


Purpose
Use this procedure to provision a Sub Network Element (SNE) in the MI-GUI before the
MI-GUI can communicate with the SNEs and show the status of these SNEs.
Note: This procedure can be performed by a user with sysadmin role.
This procedure does not cover the initial configuration of the discovery file.

Before you begin


Observe the following:
Frequency
This procedure must be carried out every time SNE(s) need to be added to the MI-GUI to
discover.
The initial MI-GUI discovery is in most cases provisioned by Alcatel-Lucent.
Required information
This procedure is performed at the MI-GUI's web-based user interface.
The following information must be known:
• The (virtual) OAM&P IP address of the SNE to add, modify or delete. This is the IP
address that the MI will use to manage the SNE.
System requirements
The SNE needs to be provisioned and active using an MI-GUI IP address as SNMP
manager. The MI-GUI IP address used will be determined by the IP architecture.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 On the MI-GUI open the runtime discovery configuration using Tools → Runtime
Administration.
...................................................................................................................................................................................................

2 On the left hand navigation panel, expand the Topology tree and select Discovery
Configurator.

....................................................................................................................................................................................................................................
3-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To add, modify, or delete the SNE(s) for MI-GUI discovery
Provision the MI-GUI
....................................................................................................................................................................................................................................
Result: The Discovery Configuration window opens in the right side of the screen.
Additional information: Important! Do not click the Apply button until all changes
have been made.
...................................................................................................................................................................................................

3 Select the Node Discovery tab.


Result: The Node Discovery tab is displayed.
...................................................................................................................................................................................................

4 This table must contain an entry for each SNE (including the 5400 Linux CP) to be
discovered from the MI-GUI.
Use the following settings:

Discover Check
IP address The (virtual) OAM&P IP address of the node.
NOTE: For the 5400 Linux CP shelf the virtual IP of the ShMC card
need to be specified.
NetMask The netmask of the node IP address.
SNMP version Set SNMP version to V1 for V1 SNMP devices and V2 for SNMP
V2 devices (e.g. the ShMC communicates via SNMP V2 with the
MI-GUI).
Discover Parent Net Do not check
Community Enter the SNMP community used by the device. In most cases, it
will be public.
Agent port Enter the SNMP port used by the SNMP agent on the SNE. This will
almost always be the default SNMP port of 161.

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

5 Depending on the action, click the Add, Delete or Modify button.


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

6 When all modifications have been completed click the Apply button and close the runtime
administration window. These changes are applied to the seed.file on the MI host.
Result: The SNE will be discovered right away and automatically with the next
automatic discovery.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-5
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To add, modify, or delete the SNE(s) for MI-GUI discovery
Provision the MI-GUI
....................................................................................................................................................................................................................................
When the SNE is not discovered
If for some reason the SNE is not discovered you can use the following steps:
1. Make sure the SNE's IP address has been properly configured. Important for LSS
hosts, the IP address specified must be the same IP address used to access the
MI-GUI.
2. From the MI server, try to ping the SNE's IP address as specified in the MI discovery
conifgurator using the command:ping <ipaddress> . If that fails, there is a
connectivity problem between the MI and the SNE that must be resolved.
3. From the MI server, try to query the system data via the SNMP deamon on the SNE
by using: snmpwalk <ipaddress> <SNMP password> system.
Example: snmpwalk 10.10.10.100 public system
If this fails, there is a problem with the SNMP daemon on the SNE that must be
resolved. It may be dead, or need to be restarted.
4. If any of the above issues are encountered and resolved, run Tools → Global
Discovery from the MI-GUI to discover the SNE.
5. If the problem is still not resolved, contact the next level of support.

....................................................................................................................................................................................................................................
3-6 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To add, modify, or delete the SNE(s) for MI-GUI discovery
Provision the MI-GUI
....................................................................................................................................................................................................................................
Discovery Configurator window
The Discovery Configurator window, with Node Discovery tab selected:

Figure 3-1 Node Discovery

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-7
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To display or change the local title on the MI-GUI
Provision the MI-GUI
....................................................................................................................................................................................................................................

To display or change the local title on the MI-GUI


Purpose
Use this procedure to change the MI-GUI title.

Before you begin


The MI-GUI title consists of
• the product title
• local title such as a switch name

Procedure
From MI server
...................................................................................................................................................................................................

1 Login as root
...................................................................................................................................................................................................

2 After the GUI displayed, observe the title bar contains the following elements:
• the product title
• local title such as a switch name
...................................................................................................................................................................................................

3 Enter:
cd /opt/AdventNet/WebNMS/bin
...................................................................................................................................................................................................

4 Display the current title by entering:


sysidconf_adm --action show_system_name
Result: Current title displayed.
...................................................................................................................................................................................................

5 To update the MI-GUI title enter:


sysidconf_adm --action set_system_name --systemname <name>
Where: <name> = the new title of the MI-GUI showing the new switch name.
Result: The title has been changed and every window instance in the platform
displays the updated title.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
3-8 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Overview
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Configure MI-GUI as SNMP-based NBI to monitor


alarms

Overview
Purpose
This section provides procedures to configure the MI-GUI for an SNMP-based
Northbound Interface.

Contents

Northbound Interface task flow 3-10


To load Northbound Interface MIB at the MI-GUI 3-12
To select MIB version 3-14
To configure Northbound Interface manager 3-15
To reconstruct lost traps 3-18
Supported NBI traps/notifications (MIB version 2) 3-21
To configure the MIB browser for NBI access via SNMPv3 3-28
To clone a user for SNMPv3 from MI CLI 3-30

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-9
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Northbound Interface task flow
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Northbound Interface task flow


Overview
Use this procedure to configure the MI-GUI to send SNMP traps to a northbound system
via the northbound Interface (NBI). This allows to remotely monitor managed objects and
alarms by a network element manager.

System requirements
In order to use the SNMP northbound interface, your manager must support v1, v2, or v3
formats. SNMPv3 provides security enhancements like privacy, authentication, and
access control.

Northbound interface provisioning task flow


The flow diagram:

Begin

1 Load northbound
interface MIB

Select MIB
2
version

Configure northbound
3 interface manager

Reconstruct Reconstruct
lost traps? lost trap(s) 4

Yes
No

Configure the MIB browser


5 for NBI via SNMPv3

6 Add user for SNMPv3

End

....................................................................................................................................................................................................................................
3-10 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Northbound Interface task flow
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Northbound Interface provisioning tasks
Important! In the following procedures a MIB browser is used to simulate an SNMP
manager.
Use the following procedure to setup SNMP traps:
...................................................................................................................................................................................................

1 To load the MIB on the MI-GUI, use: “To load Northbound Interface MIB at the
MI-GUI” (p. 3-12).
...................................................................................................................................................................................................

2 Verify MIB version


Refer to: “To select MIB version” (p. 3-14).
...................................................................................................................................................................................................

3 To configure the NBI on the MI-GUI, use: “To configure Northbound Interface manager”
(p. 3-15).
...................................................................................................................................................................................................

4 To solve SNMP problems, use: “To reconstruct lost traps” (p. 3-18).
...................................................................................................................................................................................................

5 To configure the MIB browser for the NBI via SNMPv3, use: “To configure the MIB
browser for NBI access via SNMPv3” (p. 3-28).
...................................................................................................................................................................................................

6 To add a user for SNMPv3, use: “To clone a user for SNMPv3 from MI CLI” (p. 3-30).

Additional references
For more information about northbound interface notifications of MIB version two, refer
to:
“Supported NBI traps/notifications (MIB version 2)” (p. 3-21)

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-11
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To load Northbound Interface MIB at the MI-GUI
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

To load Northbound Interface MIB at the MI-GUI


Purpose
Use this procedure at the MI-GUI to load the MIB, Lucent-WebNMS-MIB, used with a
northbound interface (NBI). In addition, it also defines how to set the SNMP port for
listening.

Before you begin


Observe the following:
Required skills
Users should have a general knowledge of SNMP and MIBs.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 In the tree view area of the MI-GUI, navigate to Tools → SNMP tools → Mib Manager
Result: The Mib Manager loads in the topological view of the MI-GUI.
...................................................................................................................................................................................................

2 From the Mib Manager window, select File → Load MIB.


Result: The Load a MIB File screen displays.
...................................................................................................................................................................................................

3 In the Load a Mib File dialog box, select the Lucent-WebNMS-MIB (located in the
right-hand column). Click Open.
Result: The Lucent-WebNMS-MIB loads.
...................................................................................................................................................................................................

4 Use the Host filed to select the virtual IP address of the MI (same IP used to bring up the
MI-GUI).
...................................................................................................................................................................................................

5 To set the SNMP port for listening, in the Mib Manager window, use the Port field to
define the port: 8001.
Result: At this point, you are ready to get/set SNMP MIB variables exposed on the
SNMP NBI.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
3-12 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To load Northbound Interface MIB at the MI-GUI
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
MIB Manager window
The MIB Manager initial window:

Figure 3-2 MIB Manager

Note: Use of this interface is mainly for debugging purpose. Whenever necessary,
Alcatel-Lucent support provides specific instructions on the usage of this interface for
specific issues.
The component CPSB MIB in this screen is not applicable to 5400 Linux CP .
However, it exists as we have common software supporting multiple platforms.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-13
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To select MIB version
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

To select MIB version


Purpose
Use this procedure at the MI-GUI to verify the MIB version.

Description
The MIB version used should always be 2. Version 1 of the MIB is obsolete.

Before you begin


Observe the following:
Required information
The northbound interface MIB Lucent-WebNMS-MIB is loaded.
Required skills
Users must have a general knowledge of SNMP and MIBs.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MI-Agents Tree View, select Tools > SNMP Tools > Mib Manager.
...................................................................................................................................................................................................

2 From the MI-Agent's Mib Manager window, from Loaded MibModules, select
Lucent-WebNMS-MIB > enterprises > lucent > lucentMibs > threeGmscMIB > webNMS
> webNMSSystem > miSNMPAgentConfiguration.
...................................................................................................................................................................................................

3 In the Set Value field, enter the version of the MIB.


For example, for version 2 enter 2.
From the Mib Manager menu list, enter Operations > Set.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
3-14 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To configure Northbound Interface manager
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

To configure Northbound Interface manager


Purpose
Use this procedure to configure the MI-GUI to send SNMP traps to a northbound system
manager.
This procedure defines how to configure a single SNMP manager. Two managers are
easily supported. Although additional mangers may be configured, degrading
performance may be experienced.

Before you begin


Observe the following:
Required information
This procedure is performed at the MI-GUI's web-based user interface.
It is assumed that the following is performed:
• Loaded the Lucent-WebNMS-MIB.
• Set the SNMP port to listen.
• Previously customized any managed object and/or alarm variables.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MI-GUI's Tree View, select Tools > SNMP Tools > Mib Manager.
...................................................................................................................................................................................................

2 From the MI-GUI's Mib Manager window, from Loaded MibModules, select
Lucent-WebNMS-MIB > enterprises > lucent > lucentMibs > threeGmscMIB > webNMS
> trapForwardingModule.
...................................................................................................................................................................................................

3 Highlight the v3TrapForwardingTable. Set Port to 8001, type it in if not in pull-down


menu.
Note: v3TrapForwardingTable is used for both SNMPv2 and SNMPv3.
...................................................................................................................................................................................................

4 Use the Host field to set the IP address of the MI.


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

5 From the menu bar, select Operations, Get, to check what entries exist. The existing
entries will print in the window showing current settings.
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-15
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To configure Northbound Interface manager
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Note: The internal loopback entry should not be deleted (usually 127.0.0.1:8003).
...................................................................................................................................................................................................

6 From the menu bar, select View, SNMP Table, the Trapviewer window will open.
...................................................................................................................................................................................................

7 Click Start from the SNMP Table window, to see what entries exist.
...................................................................................................................................................................................................

8 Click Add from the SNMP Table window, to add to create a new trap forwarding entry.
SNMPv2 example:
• v3ManagerHostType = 2 (for IPv6 IP address) or 1 (for IPv4 IP address)
• v3ManagerHost = <manager IP address>
• v3ManagerPort = <manager port>
• v3ManagerVersion = 2
• v3ManagerCommunity = public
• v3ManagerUsername = NA
• v3ManagerUserSecModel = 0
• v3ManagerUserSecLevel = 0
• v3ManagerContextName = NA
• v3ManagerTimeOut = 0
• v3ManagerRetries = 0
• v3ManagerStatus = 4
SNMPv3 example:
• v3ManagerHostType = 2 (for IPv6 IP address) or 1 (for IPv4 IP address)
• v3ManagerHost = <manager IP address>
• v3ManagerPort = <manager port>
• v3ManagerVersion = 3
• v3ManagerCommunity = public
• v3ManagerUsername = noAuthUser
• v3ManagerUserSecModel = 3
• v3ManagerUserSecLevel = 0
• v3ManagerContextName = noAuth
• v3ManagerTimeOut = 5000
• v3ManagerRetries = 0
• v3ManagerStatus = 4

....................................................................................................................................................................................................................................
3-16 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To configure Northbound Interface manager
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Select OK. A new row will appear in the table.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-17
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To reconstruct lost traps
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

To reconstruct lost traps


Purpose
This procedure defines how you can reconstruct a trap if you believe one has been lost.
Because SNMP does not provide notification that a trap has been received, this procedure
provides a method to reconstruct the type/values of a missing trap, to recreate the trap.
Each trap that is generated has a unique sequence number. This sequence number is stored
in a notification log table (notiLogTable). Because the numbers in the log table are
sequential, you can determine if a trap was missed by looking at this table (and verifying
that a number is missing in the sequence). Once you know the missing sequence number,
you can reconstruct the trap using this number as an index.
The maximum number of rows stored in the notiLogTable is defined in the maxRows
variable. Two hundred entries are stored by default.

Definitions/descriptions
The following are MIB tables/variables discussed in this topic. All are located in the
persistentTrapsMib folder.
notiLogTable This table contains the general information about the logged notifications.
varbindLogTable This table contains the information of the variable bindings sent
during a notification. All the variable bindings to the notifications are logged in this
table except for the sequence number of the notification which serves as an index for
this table.
maxRows This variable defines the maximum number of rows that can be stored in the
notiLogTable of the database. Once the limit is exceeded, the oldest row will be
deleted and a new row will be added.

Procedures
The following sub-steps are used to reconstruct a trap:
• Determine missing sequence number.
• Reconstruct trap using sequence number.

Before you begin


Observe the following:
Required information
It is assumed that the following procedure has been performed: “To load Northbound
Interface MIB at the MI-GUI” (p. 3-12)

....................................................................................................................................................................................................................................
3-18 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To reconstruct lost traps
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Determine missing sequence number(s)
This defines how to find a missing sequence number.
...................................................................................................................................................................................................

1 In the tree view of the MI-GUI, select SNMP tools → Mib Manager.
...................................................................................................................................................................................................

2 Click the Lucent-WebNMS-MIB.


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

3 Expand the MIB so that the contents of the persistentTrapsMib displays.


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

4 In the Mib Manager tree directory, click notiLogTable.


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

5 From the Mib Manager window, select View → Snmp Table.


Result: The notiLogTable displays.
...................................................................................................................................................................................................

6 Click Start to view the entries.


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

7 The notiLogIndex column displays the unique trap sequence number. If a number is
missing in the sequence, this is an indication of a lost trap.
Result: For example, suppose the sequence number 3886 was missing. That is, the
sequence numbers that displays would jump from 3885 to 3887. This would indicate
that 3886 is a missing trap. The sequence number 3886 would be the index for
reconstructing the lost trap.
E...................................................................................................................................................................................................
N D O F S T E P S

Reconstruct trap using sequence number


This defines how to reconstruct the trap using the sequence number you determined in the
following: “Determine missing sequence number(s)” (p. 3-19)
...................................................................................................................................................................................................

1 In the Mib Manager tree directory, click varbindLogTable.


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

2 From the Mib Manager window, select View → Snmp Table.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-19
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To reconstruct lost traps
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Result: The varbindLogTable displays.
...................................................................................................................................................................................................

3 Click Start to view the entries.


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

4 Using the Next and Prev keys, search this table to find the sequence number.
Result: From the previous example, sequence number 3886 was missing. Sequence
number 3886 should be found in this table and the details of this trap can be viewed.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
3-20 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Supported NBI traps/notifications (MIB version 2)


Overview
This topic provides descriptions of the supported northbound interface traps, also known
as notifications.

Alarm-related traps (notifications)


The following table defines alarm-related traps, their definition, and the fields or objects
supported for each trap:

Trap Definition Supported Fields or Objects


cesAlarmNew Indicates that a new alarm is cesAlarmId
generated and stored in the cesSystemDN
alarm table.
cesAlarmNotificationSource
cesNotiSequenceNum
cesAlarmManagedObjectInstance
cesAlarmType
cesAlarmProbableCause
cesAlarmSpecificProblem
cesAlarmPerceivedSeverity
cesAlarmTime
cesAlarmAdditionalText
cesAlarmName
cesAlarmServiceUser
cesAlarmServiceProvider
cesAlarmSecurityAlarmDetector

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-21
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Trap Definition Supported Fields or Objects


cesAlarmChanged Notification is generated when cesSystemDN
the severity of an alarm has cesAlarmNotification
changed.
Source:
cesNotiSequenceNum
cesAlarmManagedObjectInstance
cesAlarmType
cesAlarmProbableCause
cesAlarmSpecificProblem
cesAlarmPerceivedSeverity
cesAlarmTime
cesAlarmAdditionalText
cesAlarmName
cesAlarmServiceUser
cesAlarmServiceProvider
cesAlarmSecurityAlarmDetector
cesAlarmCleared Notification is generated when cesAlarmId
an alarm is cleared. cesSystemDN
cesAlarmNotificationSource
cesNotiSequenceNum
cesAlarmManagedObjectInstance
cesAlarmType
cesAlarmProbableCause
cesAlarmSpecificProblem
cesAlarmPerceivedSeverity
cesAlarmTime
cesAlarmAdditionalText
cesAlarmName
cesAlarmServiceUser
cesAlarmServiceProvider
cesAlarmSecurityAlarmDetector

....................................................................................................................................................................................................................................
3-22 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Trap Definition Supported Fields or Objects


cesAlarmListRebuiltNotifica- This notification is send to the cesNotiSequenceNum
tion manager indicating that the cesAlarmType
alarm list has been rebuilt.
cesAlarmNotificationSource
cesAlarmManagedObjectInstance
cesSystemDN
cesAlarmTime
cesAlarmListReason
cesObjectCreateNotification This notification is send to the cesNotiSequenceNum
manager when a Managed cesEventType
Object has been enrolled/added
cesEventNotificationSource
into the management domain
cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesObjectDeleteNotification This notification is send to the cesNotiSequenceNum
manager when a managed cesEventType
object has been deenrolled or
cesEventNotificationSource
deleted from the management
domain cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesMOAttrChangeNotifica- The MI sends a cesNotiSequenceNum
tion cesMOAttrChangeNotification cesEventType
to the manager when any
cesEventNotificationSource
discovered MOs one or more
attributes are changed. cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesEventAttributeIdentifier
cesEventAttributeType
cesAttributeOldValue
cesAttributeNewValue

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-23
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Trap Definition Supported Fields or Objects


cesMOStateChangeNotifica- The MI sends a cesNotiSequenceNum
tion cesMOStateChangeNotification cesEventType
to the manager when any
cesEventNotificationSource
discovered X.731 state or status
attributes of the MOs are cesEventManagedObjectInstance
changed. cesSystemDN
cesEventTime
cesEventAttributeIdentifier
cesEventAttributeType
cesAttributeOldValue
cesAttributeNewValue
cesMIAgentColdStart The MI sends an cesNotiSequenceNum
cesMIAgentColdStart when the cesEventType
management application starts.
cesEventNotificationSource
This is in addition to any
MIB-2 coldstart traps. cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesEventAdditionalText

The following defines each Alarm-related field/object:

Field Definition
cesAlarmId Uniquely identifies an entry in the alarm table. It increases every
time a new alarm occurs.
cesSystemDN This object carries the Distinguished Name (DN) of the system
that detects the network event and generates the notification.
cesAlarmNotificationSource The object to which this notification applies.
cesAlarmManagedObjectInstance Refers to the Managed Object Instance on MI for the alarmed
object.
cesAlarmType Type assigned by the device that generated the alarm.
cesAlarmProbableCause A high level qualification as to the cause of the alarm.
cesAlarmSpecificProblem Identifies a Specific Problem.
cesAlarmPerceivedSeverity Severity of an alarm.
cesAlarmTime This variable is the time of this alarm object.
cesAlarmAdditionalText Additional Text.

....................................................................................................................................................................................................................................
3-24 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Field Definition
cesAlarmName Alarm Name.
cesNotiSequenceNum This variable represents the index number of the last transmitted
notification and is incremented by 1 whenever a notification is
emitted from the agent. This would be included as a variable
binding for all notifications.
cesAlarmListReason This variable states the reason why the alarm list was rebuilt.
cesEventType Type assigned by the device that generated the alarm.
cesEventNotificationSource The object to which this notification applies.
cesEventManagedObjectInstance Managed Object Instance.
cesEventAttributeIdentifier This variable indicates OID of the MOs state/status/inventory that
has changed.
cesEventAttributeType This variable indicates AttributeType of the MO's X.731
state/status/inventory that has changed.
cesAttributeOldValue This variable indicates the old value of the MO's X.731
state/status/inventory that has changed.
cesAttributeNewValue This variable indicates the new value of the MO's X.731
state/status/inventory that has changed.
cesEventAdditionalText This variable is a message that provides addition information
about the event.
cesAlarmServiceUser If serviceUser is not null, then it carries the identity of the
service-user, whose request for service provided by the
serviceProvider h led to the generation of this security event.
cesAlarmServiceProvider If serviceProvider is not null, then it carries the identity of the
service-provider whose service is requested by the serviceUser
which led to the generation of this security event.
cesAlarmSecurityAlarmDetector If securityAlarmDetector is not null then it carries the identity of
the detector of this security event.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-25
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
SNMP traps (notifications)
The following table defines SNMP traps, their definition, and the fields or objects
supported for each trap:

Trap Definition Supported Fields or Objects


cesPMfileAvailable This notification indicates cesNotiSequenceNum
that a Performance cesEventType
Measurements file has
cesEventNotificationSource
been created and may be
retrieved by the Element cesEventManagedObjectInstance
Management System. cesSystemDN
cesEventTime
cesEventAdditionalText
cesAppNotification This notification is a cesNotiSequenceNum
generic event notification. cesEventType
cesEventNotificationSource
cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesEventAdditionalText
cesSoftwareVersion This is the software —
version of the active MI.
The intent of this software
version is to give an
overall software version
for the entire application.
cesApplicationVersion This is the application —
version. This is the version
of the application running
on the platform.

The following table defines each SNMP trap field or object:

Field Definition
cesNotiSequenceNum This variable notifies the trap sequence number sent with
all traps for trap recovery.
cesEventType This variable notifies the event type.
cesEventNotificationSource This variable notifies the OID of the object reporting the
event.
....................................................................................................................................................................................................................................
3-26 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

Field Definition
cesEventManagedObjectInstance This variable notifies the name of the object reporting the
event. This will be one of the Managed Element objects.
cesSystemDN This variable notifies the systemDN that as been
configured.
cesEventTime This variable notifies the time of event.
cesEventAdditionalText This variable notifies the absolute path name to the PM
file.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-27
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To configure the MIB browser for NBI access via SNMPv3
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

To configure the MIB browser for NBI access via SNMPv3


Overview
Use this procedure to configure the MIB on the MI-GUI to enable the access of the
northbound interface (NBI) via SNMPv3.
Note: This procedure is restricted to users with security administration permissions.

Before you begin


Observe the following:
Required skills
Users should have a general knowledge of SNMPv3 and MIBs.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 Log on MI-GUI with secadm role.


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

2 In the tree view area of the MI-GUI, navigate to Tools → SNMP tools → Mib Manager
Result: The Mib Manager screen is displayed on the topological view of the MI-GUI.
...................................................................................................................................................................................................

3 Use the menu bar to select Edit → Settings


Result: The MibBrowser Settings screen appears.
...................................................................................................................................................................................................

4 Use the field SNMP version to select v3.


Result: The field V3 Settings is applicable.
...................................................................................................................................................................................................

5 Click Add to open the SnmpParameterPanel screen.


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

6 Define the following V3 Parameter:


• The virtual IP address of the MI in field Target Host
• Port 8001 in field Target Port
• User Name
• Security Level (NoAuth,NoPriv or Auth,NoPriv or Auth, Priv).

....................................................................................................................................................................................................................................
3-28 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To configure the MIB browser for NBI access via SNMPv3
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Note: The fields Auth Protocol (MD5 or SHA), Auth Password, Priv Protocol
(CBC-DES), Priv Password are applicable depending on the selected Security Level.
...................................................................................................................................................................................................

7 Click OK to close the SnmpParameterPanel screen.


Result: The new user is displayed in the V3 Settings field in the MibBrowser Settings
screen.
...................................................................................................................................................................................................

8 Click OK to close the MibBrowser Settings screen.


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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-29
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To clone a user for SNMPv3 from MI CLI
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................

To clone a user for SNMPv3 from MI CLI


Overview
Use this procedure at the MI CLI only if you require a user other than the default user.
New users must be cloned, they cannot be created using the MI-GUI interface.
There is one default user for each level of security.
Following are the default users and their security levels:
• privUser - authentication, privacy (DES)
• privUser1 - authentication, privacy (AES)
• authUser - authentication, no privacy
• noAuthUser - no authentication, no privacy
Note: DO NOT use the MI-GUI interface to create a new user.

Before you begin


Observe the following:
• Ensure the default user exists
• Connect to the MI-GUI via CLI access to execute commands.
Refer to User Interface, 270-702-013.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 Login at the MI CLI as root.


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

2 Change directory to /opt/AdventNet/WebNMS/bin/admintools by typing:


cd /opt/AdventNet/WebNMS/bin/admintools
...................................................................................................................................................................................................

3 Clone the existing default user to a new user using the snmpUSMRemoteConfigure.sh
command.
The commands for cloning all users is the same only the arguments change.
The usage for the command is:
[-d] [-p <port>] [-a <auth_protocol>] [-w <auth_password>] [-s <priv_
password>] [-pp <priv_protocol>] [-y <new_auth_password>] [-z <new_
priv_password>] [userName] [newUserName host]

....................................................................................................................................................................................................................................
3-30 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures To clone a user for SNMPv3 from MI CLI
Configure MI-GUI as SNMP-based NBI to monitor alarms
....................................................................................................................................................................................................................................
Example to clone privUser1: In the following example, a clone user named
myAESUser is created from the existing privUser1 user:
./snmpUSMRemoteConfigure.sh -d -p 8001 -a MD5 -w authUser -s
privUser1 -pp AES -y authUser -z myAESUser privUser1
myAESUser 172.123.121.4
Example to clone privUser: In the following example, a clone user named
myDESUser is created from the existing privUser user:
./snmpUSMRemoteConfigure.sh -d -p 8001 -a MD5 -w authUser -s
privUser -y authUser -z myDESUser privUser myDESUser
172.123.121.4
Example to clone noAuthUser: In the following example, a clone user named
mynoAuthUser is created from the existing noAuthUser user:
./snmpUSMRemoteConfigure.sh -d -p 8001 noAuthUser
mynoAuthUser 135.2.116.13
Example to clone authUser: In the following example, a clone user named
myauthUser is created from the existing authUser user:
./snmpUSMRemoteConfigure.sh -d -p 8001 -a MD5 -w authUser -y
myauthUser authUser myauthUser 172.123.121.4

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-31
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Overview
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Discovery and growth using the MI-GUI

Overview
Purpose
This section provides procedures for using the MI-GUI to assist in the discovery, growth,
and degrowth of Sub-Network Elements (SNEs). You will need to consult product
documentation for the specified SNE for detailed growth/de-growth procedures.

Contents

Description of discovery, growth/degrowth 3-33


Global rediscovery using the MI-GUI 3-37
Global rediscovery using the MI-GUI's CLI 3-38
Explicit rediscovery using the MI-GUI 3-40
Explicit rediscovery using the MI-GUI's CLI 3-41
To enable the auto-delete option during discovery 3-42
Discovery degrowth using the MI-GUI 3-43
Discovery degrowth using the MI-Agents CLI 3-44

....................................................................................................................................................................................................................................
3-32 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Description of discovery, growth/degrowth
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Description of discovery, growth/degrowth


Discovery
Discovery is the process of adding information for a card or sub network element in the
MI-GUI database such that the MI-GUI can manage an SNE down to the field replaceable
unit (FRU) level.

Types of discovery
The following types of discovery exist for the MI-GUI:
• Initial Discovery
• Rediscovery
– Periodic
– On-demand (explicit and global)
• Dynamic Discovery.

Initial discovery
After the installation of MI-GUI software and the initial start of the MI-GUI application,
the MI-GUI automatically discovers all sub network elements that are connected to the
OA&M network and properly configured in the MI-GUI’s seed file. This occurs down to
the FRU level. Initial discovery also occurs when the MI-GUI application is restarted
with a database reinitialization.

Rediscovery — periodic
Automatic rediscovery of the entire system (global) occurs periodically based on a
user-configurable interval. This interval is defined in the MI-GUI's seed file. The default
value is 24 hours. This value is provisionable via the MI-GUI's web-based user interface.

Rediscovery — on-demand
Users can invoke rediscovery on-demand (at any time) by using the MI-GUI's web-based
user interface or Command Line Interface (CLI) commands. This can be performed for a
specific SNE (known as explicit rediscovery) or globally (for the entire system). Global
rediscovery will also occur when the MI-GUI application is restarted without a database
reinitialization.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-33
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Description of discovery, growth/degrowth
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................
Explicit on-demand rediscovery
Explicit rediscovery occurs at the device level (SNE, shelf, card, etc.). When on-demand
commands are issued at the device level, the MI-GUI performs the following:
• Discovers new child devices down to the field replaceable unit
• Detects existing child devices that are no longer physically present, and marks them
as “uninstalled” by default. You can optionally provision the MI-GUI to automatically
degrow child devices that meet this condition
• Detects existing child devices that are currently marked “uninstalled” (but physically
present and of the same type) and marks them as “installed”
• Detects existing child devices that are physically replaced with a different type of
device (for example, swapping a card with one of a different type). It automatically
degrows the old card, and discovers the new card
• Updates physical properties of the device itself according to current MIB variables (if
any have changed)
• Rediscovers all existing devices that have not been uninstalled or swapped, down to
the FRU level. This in effect performs all of the above functions on each of the
descendants of the selected device.
If explicit rediscovery is invoked on an SNE when a communication failure exists
between the MI-GUI and SNE, an error is logged and displayed to the user and no action
is taken.
Global on-demand rediscovery
When on-demand Global Rediscovery is invoked, the MI-GUI discovers all new sub
network elements that are connected to the OA&M network down to the field replaceable
unit. It also rediscovers existing SNEs that have previously been discovered.
Global Rediscovery will not uninstall or degrow an SNE if a communication failure exists
between the MI-GUI and the SNE; these units are skipped. If a communication failure
exists between the MI-GUI and an SNE at the time global rediscovery is invoked,
rediscovery of that particular SNE will not be invoked.

Dynamic discovery
Dynamic discovery refers to the handling of traps from SNEs such as system cold-start,
card-insert and card-removed traps. These types of traps will interact with the MI-GUI
discovery code and allow the MI-GUI to react dynamically to changes in the hardware
configuration.

....................................................................................................................................................................................................................................
3-34 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Description of discovery, growth/degrowth
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................
Growth/degrowth
The following types of growth/degrowth exist for the MI-GUI:
• Growth/Degrowth
– Manual
– Dynamic.

Manual growth
Manual growth is performed using either global rediscovery or explicit rediscovery. For
example, a new card that has been inserted into an existing SNE can be discovered by
invoking on-demand rediscovery of the SNE.

Manual degrowth
Manual degrowth is performed using the MI-GUI's web-based user interface or CLI.
Degrowth can also take place as part of global or explicit rediscovery if the auto-delete
user-configurable option is enabled. See “To enable the auto-delete option during
discovery” (p. 3-42) for more details.
When degrowth is initiated, it degrows the selected device (and all of its descendants)
from the MI-GUI database. It also deletes all alarms currently associated with the deleted
devices. Events associated with these devices remain in the database for historical
purposes.

Dynamic growth
For SNEs that support cold-start or card-inserted traps, the MI-GUI reacts as follows:
• When a cold-start trap is received from an SNE that has not yet been discovered, the
MI-GUI automatically discovers it down to the field replaceable unit
• When a cold-start trap is received from an SNE that has already been discovered, no
action is taken. Rediscovery of an SNE in this case is handled by the clearing of the
communication alarm that resulted in the machine being rebooted
• When a card-inserted trap is received for a card that is not currently discovered, the
card is automatically discovered
• When a card-inserted trap is received for a card that is currently discovered but
marked as uninstalled, the card is reinstalled and its physical properties are
rediscovered.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-35
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Description of discovery, growth/degrowth
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................
Dynamic degrowth
For SNEs that support card-removed traps, the MI-GUI reacts as follows:
• When a card-removed trap is received for a card that is currently installed, the card is
uninstalled (marked as uninstalled or degrown if the AUTO_DELETE option is
enabled)
• When a card-removed trap is received for a card that is not currently discovered, or is
currently discovered and marked as uninstalled, no action is taken
• There is no form of dynamic degrowth at the SNE level.

....................................................................................................................................................................................................................................
3-36 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Global rediscovery using the MI-GUI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Global rediscovery using the MI-GUI


Purpose
This topic describes how to manually invoke global rediscovery using the MI-GUI's
web-based user interface. When invoked, it will discover new SNEs that have not yet
been discovered and rediscover existing SNEs that have already been discovered. In both
cases, the action is performed down to the field replaceable unit.

Before you begin


Observe the following:
• The MI-GUI must be able to reach the SNEs that discovery is being performed on
• It is assumed that any new SNEs, shelfs and cards are properly provisioned
• You must connect to the MI-GUI via the web-based user interface.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the MI-GUI, on the menu bar select Tools → Global Discovery.


Result: A confirmation window displays asking if you want to continue.
...................................................................................................................................................................................................

2 Click OK.
Result: Global discovery is invoked for each network in the background and may take
several minutes to complete for all networks. To track progress, you can use the Tools
→ Discovery Status menu item on the menu bar. This will provide you with the
discovery status of each network in the system.
...................................................................................................................................................................................................

3 Any equipment changes detected will be automatically updated in the MI-GUI’s database
and reflected in the equipment views of the MI-GUI web-based user interface.
Note: The Network Interface, Static Route, and Default Gateway pages of the MI
GUI must be re-opened to show or eliminate the services newly grown or de-grown
after global discovery.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-37
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Global rediscovery using the MI-GUI's CLI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Global rediscovery using the MI-GUI's CLI


Purpose
This topic describes how to manually invoke global rediscovery using the MI-GUI's
Command Line Interface (CLI). When invoked, it will discover new SNEs that have not
yet been discovered and rediscover existing SNEs that have already been discovered. In
both cases, the action is performed down to the field replaceable unit.

Before you begin


Observe the following:
• The MI-GUI must be able to reach the SNE that discovery is being performed on
• It is assumed that any new SNEs, shelfs and cards are properly provisioned
• You must connect to the MI-GUI via CLI access to execute CLI commands.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the MI-GUI's CLI, enter the following:


discovery_cli cmd=discover_all
Result:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Discovery started successfully for network 10.1.1.0.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Discovery started successfully for network 10.1.2.0.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Global discovery is invoked in the background and may take several minutes to
complete for all networks.
...................................................................................................................................................................................................

2 To check the current status of global discovery, the user can optionally enter the
following:
discovery_cli cmd=check_status

....................................................................................................................................................................................................................................
3-38 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Global rediscovery using the MI-GUI's CLI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................
Result:

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Discovery status for network 10.1.1.0: FINISHED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Discovery status for network 10.1.2.0: IN_PROGRESS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The AUTO_DELETE option is currently disabled
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-39
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Explicit rediscovery using the MI-GUI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Explicit rediscovery using the MI-GUI


Purpose
This topic describes how to manually rediscover a specific Sub Network Element (SNE),
shelf, or card using the MI-GUI's web-based user interface.

Before you begin


Observe the following:
• The MI-GUI must be able to reach the SNE that discovery is being performed on
• It is assumed that any new SNEs, shelfs and cards are properly provisioned
• You must connect to the MI-GUI via the web-based user interface.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the MI-GUI, navigate (using the Tree View or Map View) to the specific element and
select Rediscover.
Result: A confirmation window displays asking if you want to continue.
...................................................................................................................................................................................................

2 Click OK to continue.
Result: Rediscovery may take several seconds to complete for some SNEs, depending
on how fully configured they are. The results are displayed when complete.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
3-40 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Explicit rediscovery using the MI-GUI's CLI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Explicit rediscovery using the MI-GUI's CLI


Purpose
This topic describes how to manually discover a specific Sub Network Element (SNE),
shelf or card using the MI-GUI's Command Line Interface (CLI). This is known as
explicit rediscovery.

Before you begin


Observe the following:
• The MI-GUI must be able to reach the SNE that discovery is being performed on
• It is assumed that any new SNEs, shelfs and cards are properly provisioned
• You must connect to the MI-GUI via CLI access to execute CLI commands.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the MI-GUI's CLI, enter the following:


discovery_cli cmd=rediscover name=<object name>
Where <object name> is the name of the managed object.
Example: discovery_cli cmd=rediscover name=LSS-2_CAB-1_ATCA-1
...................................................................................................................................................................................................

2 When complete, the results will be displayed indicating any equipment changes that were
detected. In addition, these changes will automatically be reflected in the MI-GUI's
web-based user interface (Map View).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-41
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures To enable the auto-delete option during discovery
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

To enable the auto-delete option during discovery


Purpose
During global rediscovery or explicit rediscovery, a device that is no longer physically
present is marked “uninstalled” and left in the MI-GUI database by default. The user has
the option to change this default behavior and automatically degrow the device, which
will remove it from the MI-GUI database.

Before you begin


Observe the following:
• Changing the default value can only be performed at the MI-GUI's CLI
• You must connect to the MI-GUI via CLI access to execute CLI commands.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the MI-GUI's CLI, execute the following:


discovery_cli cmd=set auto_delete=on
...................................................................................................................................................................................................

2 This command will take up to 30 seconds to be reflected on the MI-GUI's web-based user
interface. Execute the following to verify the update:
discovery_cli cmd=check_status
The update can also be verified using the Tools → Discovery Status menu item on the
MI-GUI's UI to verify that the update of the auto-delete option has been recognized by
the system.
...................................................................................................................................................................................................

3 To revert back to the default option, execute the following:


discovery_cli cmd=set auto_delete=off
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
3-42 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Discovery degrowth using the MI-GUI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Discovery degrowth using the MI-GUI


Purpose
This topic describes how to degrow a Sub Network Element (SNE), shelf or card from the
MI-GUI database using the MI-GUI web-based user interface.
Note: This procedure only removes the element from the network map. After a Global
Discovery or initialization of the discovery database an attempt will be made to discover
the element again. To permanently remove the element, the particular entry (in case of an
SNE) needs to be removed using the Discovery Configurator using procedure “To add,
modify, or delete the SNE(s) for MI-GUI discovery” (p. 3-4). After that, the element
needs to be degrown, or the discovery database needs to be initialized.

Before you begin


Observe the following:
• The MI-GUI must be able to reach the SNE that degrowth is being performed on
• You must connect to the MI-GUI via its web-based user interface.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the SNE, physically remove the device following the degrowth procedures for the
specific SNE.
...................................................................................................................................................................................................

2 At the MI-GUI, navigate (using the Tree View or Map View) to the specific element to be
degrown and select Degrow.
Result: A confirmation window displays asking if you want to continue.
...................................................................................................................................................................................................

3 Click OK.
Result: A window confirming the deletion displays.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-43
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Discovery degrowth using the MI-Agents CLI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

Discovery degrowth using the MI-Agents CLI


Purpose
This topic describes how to degrow a Sub Network Element (SNE), shelf or card from the
MI-GUI database using the MI-GUI's Command Line Interface (CLI).
Note: This procedure only removes the element from the network map. After a Global
Discovery or initialization of the discovery database an attempt will be made to discover
the element again. To permanently remove the element, the particular entry (in case of an
SNE) needs to be removed using the Discovery Configurator using procedure “To add,
modify, or delete the SNE(s) for MI-GUI discovery” (p. 3-4). After that, the element
needs to be degrown, or the discovery database needs to be initialized.

Before you begin


Observe the following:
• The MI-GUI must be able to reach the SNE that degrowth is being performed on
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to
User Interface, 270-702-013.

Procedure
Perform the following steps:
...................................................................................................................................................................................................

1 At the SNE, physically remove the SNE or card following the degrowth procedures for
the specific SNE.
...................................................................................................................................................................................................

2 At the MI-GUI CLI, enter the following:


discovery_cli cmd=degrow name=<object name>
Where <object name> is the name of the managed object.
Example: discovery_cli cmd=degrow name=LSS-2_CAB-1_ATCA-1
...................................................................................................................................................................................................

3 Click OK.
Result:
The device is removed from the MI-GUI database.

1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ManagedObject LSS-2_CAB-1_ATCA-1 deleted.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
....................................................................................................................................................................................................................................
3-44 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures Discovery degrowth using the MI-Agents CLI
Discovery and growth using the MI-GUI
....................................................................................................................................................................................................................................

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-45
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures Overview
Inventory management
....................................................................................................................................................................................................................................

Inventory management

Overview
Purpose
This section contains the procedure that is related to performing inventory management
on the 5400 Linux CP using the MI-GUI.

Contents

MI-GUI inventory management 3-47

....................................................................................................................................................................................................................................
3-46 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures MI-GUI inventory management
Inventory management
....................................................................................................................................................................................................................................

MI-GUI inventory management


Purpose
This procedure uses the MI-GUI to provide inventory generation and display capability
for users to view the component specific inventory information on GUI.

Before you begin


Observe the following:
Requirements
In order to display log files, the user must be logged on to the MI-GUI's web-based user
interface and be at the MI-GUI's Main MI screen.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 In the Tree View portion of the screen, click on Configuration Management and select
Inventory to open the Inventory screen.
Result: The Inventory window opens.
...................................................................................................................................................................................................

2 Select Generate Inventory ReportWhen the confirmation pop-up window opens, select
OK. Wait while the inventory report is generated. This may take a few minutes.
Result: While the report is being generated a status message is displayed in the
Results of Generate Inventory Report Action window. When the Generating Tree
View of Inventory file is completed is displayed the report is completed.
...................................................................................................................................................................................................

3 To view inventory report, select “View Inventory Report”.


Results: The List of Inventory Reports window displays the last 5 reports that have
been generated sorted by date..
...................................................................................................................................................................................................

4 Select the inventory report to be viewed. When the confirmation pop-up window opens,
select OK.
Result The left side of the Inventory Report window now shows a tree strcture
representing the hardware components of this configuration
...................................................................................................................................................................................................

5 Select the (+) to expand the components and display subcomponents.


....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-47
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures MI-GUI inventory management
Inventory management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

6 Select either components or sub-components in the left side tree view.


Result: The inventory information for the selected item is displayed.
...................................................................................................................................................................................................

7 Select Exit to close the Inventory Report window.


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

....................................................................................................................................................................................................................................
3-48 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures MI-GUI inventory management
Inventory management
....................................................................................................................................................................................................................................
Inventory Report window
The Inventory Report window displays:

Figure 3-3 Inventory Report

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-49
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures MI-GUI inventory management
Inventory management
....................................................................................................................................................................................................................................
Generate Inventory Report
The window used to generate an inventory report:

Figure 3-4 Generate Inventory Report

....................................................................................................................................................................................................................................
3-50 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - MI-GUI procedures MI-GUI inventory management
Inventory management
....................................................................................................................................................................................................................................
View Inventory Report
The window used to view inventory reports with collapsed folders:

Figure 3-5 View Inventory Report

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 3-51
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - MI-GUI procedures MI-GUI inventory management
Inventory management
....................................................................................................................................................................................................................................
The window used to display the inventory data with a selected item:

Figure 3-6 Display Inventory Report

....................................................................................................................................................................................................................................
3-52 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
4 4 anage system
M
configuration - view or
control the operational
state
Overview
Purpose
This chapter contains the Configuration Management related procedures that can be
performed on the 5400 Linux CP.

Contents

View or control the operational state 4-2


To display the current state of the MI Virtual Cluster 4-3
To display the current state of a MI Virtual Machine 4-4
To start the MI Virtual Cluster 4-5
To start a MI Virtual Machine 4-6
To stop the MI Virtual Cluster 4-7
To stop a MI Virtual Machine 4-8
To switch states of MI Virtual Machines in Virtual Cluster 4-9
To modify the state of a diskless host 4-10

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 4-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - view or control the Overview
operational state
View or control the operational state
....................................................................................................................................................................................................................................

View or control the operational state

Overview
Purpose
This section provides the procedures that can be used to view and control the operational
state of the 5400 Linux CP hardware.

Contents

To display the current state of the MI Virtual Cluster 4-3


To display the current state of a MI Virtual Machine 4-4
To start the MI Virtual Cluster 4-5
To start a MI Virtual Machine 4-6
To stop the MI Virtual Cluster 4-7
To stop a MI Virtual Machine 4-8
To switch states of MI Virtual Machines in Virtual Cluster 4-9
To modify the state of a diskless host 4-10

....................................................................................................................................................................................................................................
4-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - view or control the To display the current state of the MI Virtual Cluster
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To display the current state of the MI Virtual Cluster


Purpose
Use this procedure to display the current state of the MI Virtual Cluster.

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to
User Interface, 270-702-013.
• You must be able to log in as 'lss'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example, if a switch-over command is entered and
switch-over has already begun, the RCC generates a message and continues with the
switch-over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss.
...................................................................................................................................................................................................

2 Chose editor and enter


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

3 If you want to Enter


Display the current state of the MIcmd state vc
Virtual Cluster

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 4-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - view or control the To display the current state of a MI Virtual Machine
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To display the current state of a MI Virtual Machine


Purpose
Use this procedure to display the current state of a primary or alternate MI Virtual
Machine (on host 1 or 2).

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to
User Interface, 270-702-013.
• You must be able to log in as 'lss'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example if a switch-over command is entered and
switch-over has already begun, the RCC generates a message and continues with the
switch-over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss.
...................................................................................................................................................................................................

2 Chose editor and enter


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

3 If you want to Enter


Display the current state of the MIcmd state pri
primary Virtual Machine (host 1)
Display the current state of the MIcmd state alt
alternate Virtual Machine (host 2)

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

....................................................................................................................................................................................................................................
4-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - view or control the To start the MI Virtual Cluster
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To start the MI Virtual Cluster


Purpose
Use this procedure to start the MI Virtual Cluster.

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to :
User Interface, 270-702-013.
• You must be able to log in as 'root'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example if a switch-over command is entered and
switch-over has already begun, the RCC generates a message and continues with the
switch-over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss
...................................................................................................................................................................................................

2 Choose editor and enter


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

3 If you want to Enter


Start the Virtual Cluster startMI (this command is an alias forMIcmd
start vc)

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 4-5
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - view or control the To start a MI Virtual Machine
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To start a MI Virtual Machine


Purpose
Use this procedure to start a primary or alternate MI Virtual Machine (on host 1 or 2).

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to
User Inteface Guide, 270-702-013.
• You must be able to log in as 'lss'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example if a switch over command is entered and
switch over has already begun, the RCC generates a message and continues with the
switch over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss.
...................................................................................................................................................................................................

2 If you want to Enter


Start the primary Virtual Machine MIcmd start pri
(host 1)
Start the alternate Virtual Machine MIcmd start alt
(host 2)

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

....................................................................................................................................................................................................................................
4-6 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - view or control the To stop the MI Virtual Cluster
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To stop the MI Virtual Cluster


Purpose
Use this procedure to stop the MI Virtual Cluster.

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to
User Interface, 270-702-013.
• You must be able to log in as 'lss'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example if a switch-over command is entered and
switch-over has already begun, the RCC generates a message and continues with the
switch-over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss.
...................................................................................................................................................................................................

2 Chose editor and enter


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

3 If you want to Enter


Stop the Virtual Cluster stopMI (this command is an alias for MIcmd stop vc
)

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 4-7
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - view or control the To stop a MI Virtual Machine
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To stop a MI Virtual Machine


Purpose
Use this procedure to stop a primary or alternate MI Virtual Machine (on host 1 or 2).

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to
User Interface, 270-702-013.
• You must be able to log in as 'lss'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example if a switch over command is entered and
switch over has already begun, the RCC generates a message and continues with the
switch over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss.
...................................................................................................................................................................................................

2 Chose editor and enter


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

3 If you want to Enter


Stop the primary Virtual Machine MIcmd stop pri
(host 1)
Stop the alternate Virtual Machine MIcmd stop alt
(host 2)

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

....................................................................................................................................................................................................................................
4-8 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - view or control the To switch states of MI Virtual Machines in Virtual Cluster
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To switch states of MI Virtual Machines in Virtual Cluster


Purpose
Use this procedure to switch states of the MI Virtual Machines in a Virtual Cluster.

Before you begin


Observe the following:
• You must connect to the MI-GUI via CLI access to execute CLI commands.
Refer to User Interface, 270-702-013.
• You must be able to log in as 'lss'.
Important! Notice that commands to the virtual clusters and machines are actually
performed by the RCC. The RCC controls the start up and shutdown of MI service
processes and monitors the health of the process. This means that the RCC may not
allow requested commands (for example if a switch-over command is entered and
switch-over has already begun, the RCC generates a message and continues with the
switch-over).

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI-GUI host and log in as lss.
...................................................................................................................................................................................................

2 Choose editor and enter


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

3 If you want to Enter


Switch states of Virtual Machines in MIcmd switch
a Virtual Cluster

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 4-9
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - view or control the To modify the state of a diskless host
operational state
View or control the operational state
....................................................................................................................................................................................................................................

To modify the state of a diskless host


Purpose
Use this procedure to modify the state of a specific diskless host.

Before you begin


Observe the following:
Requirements
State control from the MI-GUI is currently supported for the following diskless hosts:
• H.248 DS
• IMS Server
Configuration
To modify states on a diskless host, the user must be logged on to the MI-GUI's
web-based user interface.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MI-GUI's Tree View, select the Services Members.


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

2 Highlight the diskless host you want to change the state of and right-click.
...................................................................................................................................................................................................

3 Select State Control.


Result: The State control window appears showing options for selection to send.
...................................................................................................................................................................................................

4 Click a control option:

Option Definition
Switchover Switch between the specified card and its mate. The pair
must be active/hot standby.
Force OOS Moves a card to the Out Of Service (OOS) state. In this
state all application level processes are stopped and the
only process running on the card is the local monitor. If
the mate is not active, the request is denied. Otherwise
the specified card is taken to the Out Of Service state.

....................................................................................................................................................................................................................................
4-10 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - view or control the To modify the state of a diskless host
operational state
View or control the operational state
....................................................................................................................................................................................................................................

Option Definition
Unconditional Force OOS Forcibly make the specified card OOS. This may cause
loss of service if the mate is not in a state from which it
can take over processing (hot standby, or cold standby).
If the mate is in the cold standby state when the host is
forced OOS, then the mate will be transitioned to the
active state, but there may be some impact on stable
processing that was not up-to-date on the mate.
Restore Restore the specified card to the hot standby state. If the
card is already in the hot standby state, no action is
taken. Otherwise the card is returned to service if
possible.

Note The selectable options will vary depending on whether the card is active,
standby, and so on.
Non-valid options will be greyed out on the State Control screen.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 4-11
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - view or control the To modify the state of a diskless host
operational state
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
4-12 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
5 5 anage system
M
configuration - hardware
growth

Overview
Purpose
This chapter provides procedures that the user must carry out to grow new 5400 Linux CP
hardware.

Contents

Growth 5-3
Growth introduction 5-4
Growth process stages 5-5
Growth planning 5-6
Growth planning process 5-7
To verify minimal system requirements 5-8
To verify hardware version and test acceptance 5-9
Growth system preparation 5-10
Growth system preparation process 5-11
To install new hardware 5-12
To cable new hardware 5-13
To verify growth system stability 5-15
To install Ethernet transport connections between HSPP4 face plate and the 5-17
external network equipment
Growth setup 5-19
Growth setup process 5-20
To verify disk space availability for backup 5-21
To perform full system backup 5-22

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Overview

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

To verify the success of backup 5-23


Growth implementation 5-24
Growth implementation process 5-25
To grow hardware and service on diskless hosts 5-27
To grow hardware and service on diskful hosts 5-39
To jumpstart diskful card 5-51
To establish a processor card SOL session 5-53
To grow service of diskless hosts for multiple services 5-54
To grow RTM with disk on an existing diskful host 5-60
Serial port setup through faceplate 5-63
To determine the serial port configured in laptop 5-64
To configure laptop for serial connection on Windows XP 5-66
To establish serial port connection on the laptop 5-68

....................................................................................................................................................................................................................................
5-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Overview
Growth
....................................................................................................................................................................................................................................

Growth

Overview
Purpose
This section describes the growth functionality that is available to support the 5400 Linux
CP applications.

Contents

Growth introduction 5-4


Growth process stages 5-5

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Growth introduction
Growth
....................................................................................................................................................................................................................................

Growth introduction
Overview
Office growth is the systematic modification of central office equipment to provide
increased call-handling capacity and improved service.
Growth is used to evolve the office economically over a wide range of services and traffic
needs.
The two distinct phases of growth are as follows:
• Switch growth
• Terminal growth

Switch growth
Switch growth is the addition of hosts and components or component pairs to the office.

Terminal growth
Terminal growth is the provisioning of lines and trunks in the office to accommodate the
traffic growth.

Office impact
Since growth takes places in an operational office, the impact should be minimized. One
objective of growth procedures is to maintain the reliability and availability of the office.
Reliability dictates that growth does not interfere with normal office maintenance
programs.
The integrity of growth units must be ensured before these units are made available to the
operational office.
Transient and stable calls are maintained throughout growth procedures.

....................................................................................................................................................................................................................................
5-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Growth process stages
Growth
....................................................................................................................................................................................................................................

Growth process stages


Process stages
The growth process is to be distinct in the following stages:
• Planning
• System preparation
• Setup
• Implementation

Planning
Here we perform the actions needed to guarantee that all growth-related site activities are
performed prior to the start.
We determine the minimal system requirements, hardware requirements, check for the
correct growth procedure and check the test plan.

System preparation
Here we perform the actions needed to guarantee that all installation activities are
performed prior to the start. Also a sanity check of the system is done to be assured that
the continuation does not affect the system.

Setup
Here we perform the actions needed to guarantee that the system files are backed up prior
to the start. If needed during the implementation stage the backup is used to restore the
system to its previous configuration.

Implementation
Here we perform the actions needed to start the integration of the elements in the system
and perform acceptance tests if required.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-5
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Overview
Growth planning
....................................................................................................................................................................................................................................

Growth planning

Overview
Purpose
This section describes the process flow and the procedures to perform the planning
actions required for system growth

Contents

Growth planning process 5-7


To verify minimal system requirements 5-8
To verify hardware version and test acceptance 5-9

....................................................................................................................................................................................................................................
5-6 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Growth planning process
Growth planning
....................................................................................................................................................................................................................................

Growth planning process


Overview
This topic describes the process to plan for growth.
Here we perform the actions needed to guarantee that all growth-related site activities are
performed prior to the start.

Growth planning process flow


The process flow for growth planning:

Growth planning process


Stages that should be performed:
...................................................................................................................................................................................................

1 Determine the minimal system requirements. See “To verify minimal system
requirements” (p. 5-8)
...................................................................................................................................................................................................

2 Determine if the hardware is supported by the software.


See “To verify hardware version and test acceptance” (p. 5-9)
...................................................................................................................................................................................................

3 Go to system preparation section.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-7
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To verify minimal system requirements
Growth planning
....................................................................................................................................................................................................................................

To verify minimal system requirements


Purpose
Use this procedure to verify the minimal system requirements that are needed to grow the
system.

Before you begin


Observe the following:
Required information
Release notes, capacity figures from System Guide, traffic expectation model.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Check the required minimum hardware configuration.


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

2 Calculate required hardware for expected traffic.


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

3 Check if required hardware is available in the system.


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

4 Check the required license files.


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

....................................................................................................................................................................................................................................
5-8 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To verify hardware version and test acceptance
Growth planning
....................................................................................................................................................................................................................................

To verify hardware version and test acceptance


Purpose
Use this procedure to verify the hardware version that is allowed for the running software
release, the availability of a growth procedure, and the availability of an acceptance test
plan.

Before you begin


Observe the following:
Required information
Release notes, OAM&P manual, LWS acceptance test plan, customer test guideline.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Check which hardware version is mentioned in the release notes.


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

2 Check if hardware version to be used matches release notes.


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

3 Check if a growth procedure exists for the required hardware.


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

4 Check if an acceptance test is required by the customer.


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

5 Check if an acceptance test procedure is available.


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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-9
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Overview
Growth system preparation
....................................................................................................................................................................................................................................

Growth system preparation

Overview
Purpose
This section describes the process flow and the procedures to perform the system
preparation actions required for system growth.

Contents

Growth system preparation process 5-11


To install new hardware 5-12
To cable new hardware 5-13
To verify growth system stability 5-15
To install Ethernet transport connections between HSPP4 face plate and the 5-17
external network equipment

....................................................................................................................................................................................................................................
5-10 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Growth system preparation process
Growth system preparation
....................................................................................................................................................................................................................................

Growth system preparation process


This topic describes the process to prepare the system for growth.
Here we perform the actions needed to guarantee that all installation activities are
performed prior to the start. Also a sanity check of the system is done to be assured that
the continuation does not affect the system.

Growth system preparation process flow


The process flow for system preparation:

Begin

Install new
1 hardware

Cabling to
2
hardware

3 Verify growth
system stability

End

Growth system preparation process


Stages that should be performed:
...................................................................................................................................................................................................

1 Physically install the new hardware in the system using: “To install new hardware”
(p. 5-12)
Responsibility: Installation personnel
...................................................................................................................................................................................................

2 Physically install new cabling in the system using: “To cable new hardware” (p. 5-13)
Responsibility: Installation personnel
...................................................................................................................................................................................................

3 Verify if the system is stable to continue with the actual growth procedure using: “To
verify growth system stability” (p. 5-15)
...................................................................................................................................................................................................

4 Go to growth setup section.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-11
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To install new hardware
Growth system preparation
....................................................................................................................................................................................................................................

To install new hardware


Purpose
Use this procedure to prepare the system for growth by installing the required new
hardware.
The intention here is to direct the user to the related required procedures.

Before you begin


Observe the following:
Required user skills
The person performing the installation should be familiar with the installation guidelines.
Required information
The following information is needed:
• Office Data Manual (ODM)
• Installation procedure
• Site preparation manual checklists.
Personnel
Depending on the hardware one or more persons are needed.
Important! When a cabinet is installed the physical placement requires more persons.
Refer to the installation procedure for exact details.
System requirements
The system should be sane and not reporting errors.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Using the site preparation manual checklists verify if all necessary preparation has been
completed.
...................................................................................................................................................................................................

2 Using the ODM determine the required position for the new hardware.
...................................................................................................................................................................................................

3 Using the installation procedure equip the new hardware at the required position.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-12 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To cable new hardware
Growth system preparation
....................................................................................................................................................................................................................................

To cable new hardware


Use this procedure to install and connect internal and external cabling to grow the system
with the new hardware.

Purpose
This procedure provides the steps to prepare the system for growth by cabling the
required new hardware.
The intention here is to direct the user to the related required procedures.

Before you begin


Observe the following:
Required user skills
The person performing the installation should be familiar with the installation guidelines.
Required information
The following information is needed:
• Office Data Manual (ODM)
• Installation procedure
• Site preparation manual checklists.
Personnel
Depending on the cabling one or more persons are needed.
Important! When cables are installed the work could require more persons. Refer to
the installation procedure for exact details.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Check if the following cables are installed or required:


• Power to the shelf/unit
• Internal Ethernet cabling to Router/Switch
• Cabling to Digital Distribution Frame (DDF)
• Cabling to Main Distribution Frame (MDF)
• Cabling to Optical Distribution Frame (ODF)
• Internal serial cabling for alarms

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-13
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To cable new hardware
Growth system preparation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

2 Using the site preparation manual checklists verify if all necessary preparation has been
completed.
...................................................................................................................................................................................................

3 Using the ODM determine the required position for the new cabling.
...................................................................................................................................................................................................

4 Using the installation procedure equip the new hardware with the cabling.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-14 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To verify growth system stability
Growth system preparation
....................................................................................................................................................................................................................................

To verify growth system stability


Purpose
Use this procedure to verify the stability of a growth system before the start of the growth
procedures.

Before you begin


Observe the following:
Required user skills
The person performing the installation should be familiar with the installation guidelines.
The person should have knowledge to determine the sanity of the system that allows the
growth procedures to execute.
Duration
This procedure should take about 15 minutes to complete.
Frequency
This procedure has to be performed before the start of a growth procedure.
Required information
The following information is needed:
• Logfiles
• Alarm history.
System requirements
The user should be logged on the MI-GUI as root.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Access the alarm information on the MI-GUI, gather the information from the last 24
hours.
...................................................................................................................................................................................................

2 Determine if intermittent errors or anomalies have occurred that interfere with the
equipment that is to be added.
Important! If irregularities are found, contact technical support to fix the problem.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-15
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To verify growth system stability
Growth system preparation
....................................................................................................................................................................................................................................
Result: Based on the findings continue with the next step.
...................................................................................................................................................................................................

3 Access the master log file information on the MI-GUI, gather the information from the
last 24 hours.
...................................................................................................................................................................................................

4 Determine if intermittent errors or anomalies have occurred that interfere with the
equipment that is to be added.
Important! If irregularities are found, contact technical support to fix the problem.
Result: Based on the findings continue with the next step.
...................................................................................................................................................................................................

5 Continue your growth procedure if no errors are found.


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

....................................................................................................................................................................................................................................
5-16 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To install Ethernet transport connections between HSPP4
Growth system preparation face plate and the external network equipment
....................................................................................................................................................................................................................................

To install Ethernet transport connections between HSPP4 face


plate and the external network equipment
Prerequisites
• Stable system.
• Ensure that four cables are available to connect.

Procedure
...................................................................................................................................................................................................

1 Install the four cables. Two cables go from ge0 and ge1 of primary HSPP4 to the router.
The other two cables go from ge0 and ge1 of secondary HSPP4 to the router.
For more information on Ethernet connections between HSPP4 and the router, see Figure
5-1, “HSPP4 Ethernet connections to the router” (p. 5-17).

Figure 5-1 HSPP4 Ethernet connections to the router

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-17
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To install Ethernet transport connections between HSPP4
Growth system preparation face plate and the external network equipment
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

2 There must be only one uplink. If both IPv4 and IPv6 access networks are used, they must
be placed on the same set of cables. All the four cables can carry at most one IPv4
network and at most one IPv6 network depending on the redundancy scheme.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-18 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Overview
Growth setup
....................................................................................................................................................................................................................................

Growth setup

Overview
Purpose
This section describes the process flow and the procedures to perform the setup actions
required for system growth.

Contents

Growth setup process 5-20


To verify disk space availability for backup 5-21
To perform full system backup 5-22
To verify the success of backup 5-23

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-19
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Growth setup process
Growth setup
....................................................................................................................................................................................................................................

Growth setup process


Overview
This topic describes the process to prepare the system for growth.

Growth setup process flow


The process flow for growth setup:

Begin

Verify disk
1 space

Perform full
2 system backup

Verify backup
3
succes

End

Growth setup process


Stages that should be performed:
...................................................................................................................................................................................................

1 Make sure enough disk space is available, use: “To verify disk space availability for
backup” (p. 5-21)
...................................................................................................................................................................................................

2 Backup the system files, both configuration and database, use: “To perform full system
backup” (p. 5-22)
...................................................................................................................................................................................................

3 Make sure the backup was successful, use “To verify the success of backup” (p. 5-23)
...................................................................................................................................................................................................

4 Continue with the implementation section.

....................................................................................................................................................................................................................................
5-20 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To verify disk space availability for backup
Growth setup
....................................................................................................................................................................................................................................

To verify disk space availability for backup


Purpose
Use this procedure to verify the disk space availability before the start of the backup.

Before you begin


Observe the following:
Required user skills
The user should have basic knowledge of UNIX commands and interpretation of the
output.
Frequency
This procedure should be performed before the start of the backup.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Log on as root on the MI-GUI.


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

2 At the prompt type: df —k /export/home


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

3 Verify that at least 1.5 GB of disk space is available.


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

4 If enough disk space is available continue with the system backup procedure.
If not enough disk space is available determine if files can be deleted or contact technical
support.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-21
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To perform full system backup
Growth setup
....................................................................................................................................................................................................................................

To perform full system backup


Purpose
Use this procedure to backup the configuration servers.
This is done in the event recovery action becomes necessary.

Before you begin


Observe the following:
Required information
This procedure is performed at the MI command line interface.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 From the MT, telnet/ssh to the MI using the physical IP address and log on as root.
telnet [physical IP address of MI]
...................................................................................................................................................................................................

2 To perform the backup:


lcp_adm -v -a backup
Result: The system will ask you if you wish to delete all but the last three backups (1
being the new update you will be creating).
Select 'y' to proceed.
Select 'n' to keep all previous backups.
Note: Keeping too many backups may cause disk space issues during the upgrade
process.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-22 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To verify the success of backup
Growth setup
....................................................................................................................................................................................................................................

To verify the success of backup


Purpose
Use this procedure to verify the success of a backup after completion of the backup.

Before you begin


Observe the following:
Required user skills
The user should have basic knowledge of UNIX commands and interpretation of the
output.
Duration
This procedure should take about 2 minutes to complete.
Frequency
This procedure should be performed after the completion of the backup.
System requirements
The user should be logged on the MI-GUI as root.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 At the prompt type: lss_adm -v –a list_backup


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

2 Determine the correct date and time of the backup and note the file name.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-23
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Overview
Growth implementation
....................................................................................................................................................................................................................................

Growth implementation

Overview
Purpose
This section describes the process flow and the procedures to perform the implementation
actions required for system growth.

Contents

Growth implementation process 5-25


To grow hardware and service on diskless hosts 5-27
To grow hardware and service on diskful hosts 5-39
To jumpstart diskful card 5-51
To establish a processor card SOL session 5-53
To grow service of diskless hosts for multiple services 5-54
To grow RTM with disk on an existing diskful host 5-60

....................................................................................................................................................................................................................................
5-24 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Growth implementation process
Growth implementation
....................................................................................................................................................................................................................................

Growth implementation process


Purpose
This topic describes the process to execute the growth procedures.
Here we perform the actions needed to start the integration of the elements in the system
and perform acceptance tests if required.

Growth implementation process flow


The process flow for growth of the system:

Begin

Grow Y
1 diskful hosts? Growth of diskful hosts

Grow
2 Y
diskless hosts? Growth of diskless hosts

Grow
service on
diskless host(s) on Y Service growth on
3 ATCA / for diskless host(s)/ for
multiple multiple hosts
hosts?

End

Growth implementation process


Stages that should be performed:
...................................................................................................................................................................................................

1 If you grow diskful hosts, use: “To grow hardware and service on diskful hosts” (p. 5-39).
Responsibility: Growth engineer
...................................................................................................................................................................................................

2 If you grow diskless hosts, use: “To grow hardware and service on diskless hosts”
(p. 5-27).
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-25
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth Growth implementation process
Growth implementation
....................................................................................................................................................................................................................................
Responsibility: Growth engineer
...................................................................................................................................................................................................

3 If you grow service on diskless hosts (on ATCA), use: “To grow service of diskless hosts
for multiple services” (p. 5-54).
Responsibility: Growth engineer

....................................................................................................................................................................................................................................
5-26 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................

To grow hardware and service on diskless hosts


Purpose
This topic provides a procedure to grow one pair of diskless hosts using the Software
Installation Manager (SIM) tool.
The following hardware type is supported
• ATCA
The following diskless services are supported:
• ims
• fs5k
• h248
• ss7

Before you begin


Observe the following:
During the process, you need to open two windows on the active MI:
• A SIM process window to enter SIM commands. Call this window 1.
• A SIM log window to monitor SIM progress. Call this window 2.
Make sure of the following:
• The system is stable
• Perform a system backup
• The information required to grow in a new pair of cards should be kept ready:
For example:
– Hardware type (Advanced TCA)
– Service type
– Subnets
– Default gateway subnet
– Shelf number
– Card number
– IPsec type (for IMS service type only)
– NI types assigned to a particular IP address
– Offset (if required)
– IPv6 addresses and subnet numbers (if required)

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-27
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open two windows and from both windows, log into MI-1 as root.
...................................................................................................................................................................................................

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active, then switch by using the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command to create the host table, which will be used by the SIM
tool.
create_ht
Result:
> create_ht
Fri Apr 23 14:14:54 CDT 2010 create_ht
Fri Apr 23 14:14:54 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Fri Apr 23 14:14:54 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Fri Apr 23 14:14:54 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Fri Apr 23 14:14:54 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

5 Execute the following command as root.

....................................................................................................................................................................................................................................
5-28 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
su_health -a
Note: Proceed further only if this command reports success.
...................................................................................................................................................................................................

6 To inhibit RCC on the MI-1, type the following command and press Enter:
rccInhibit -a SET <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 For each card that is to be grown, execute:


isolateCard -s shelf# -c card#
> isolateCard -s 1 -c 11
SHELF=1 HUB=10.31.32.112 PORT=18 OID=8
interfaces.ifTable.ifEntry.ifAdminStatus.8 = 0
SHELF=1 HUB=10.31.32.128 PORT=18 OID=8
interfaces.ifTable.ifEntry.ifAdminStatus.8 = 0
...................................................................................................................................................................................................

8 Plug in the blades that need to be grown.


Note: Make sure they are diskless and are completely seated.
...................................................................................................................................................................................................

9 The status of the blade can be found by logging in to the active ShMC and execute the
following commands:
# clia shmstatus
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Host: "Active"
# clia board 11
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Physical Slot # 11
90: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x03
PICMG Version 2.2
Hot Swap State: M4 (Active), Previous: M3 (Activation In
Process), Last State Change Cause: Normal State Change (0x0)

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-29
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
90: FRU # 0
Entity: (0xa0, 0x60)
Hot Swap State: M4 (Active), Previous: M3 (Activation In
Process), Last State Change Cause: Normal State Change (0x0)
Device ID String: "BMR-H8S NBRZAA"
...................................................................................................................................................................................................

10 The Hot Swap State of the cards need to be active as shown above.
...................................................................................................................................................................................................

11 If the state is Inactive, then the blade needs to be powered on. It can be done from the
active ShMC as shown in the following command:
# clia activate board 11
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Command issued via IPMB, status = 0 (0x0)
Command executed successfully
...................................................................................................................................................................................................

12 Here is another way to power on the blade from the MI:


resetCard -s shelf# -c card# -v poweron
resetCard -s 1 -c 12 -v poweron
ShMC_IP=10.31.64.240 SHELF=1 CARD=12
...................................................................................................................................................................................................

13 Execute:
hwgrow
Note: If more than one service is grown, enter space separated service types when
prompted for the service type. The subnet information will be prompted for each
service. Multiple instances (pools) of the same service type can be grown in.
Example of valid multiple services combination is:
ims fs5k h248 ims
Note: If internal subnet is chosen, then offsets are not needed.
Examples of hwgrow command:
> hwgrow
hwgrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/hwgrow/hosts.dat
for growing one card pair. Enter the service
type for the pair, and then enter the shelf and card

....................................................................................................................................................................................................................................
5-30 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
number for both side A and side B of the host pair.
The allowed service types are as follows:
cdr
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the SERVICE TYPE for pair 1 HostID 0: ims
Are you using offsets for “ims” (y/n) ?n
Enter the IPSEC TYPE for ims service pair 1 (none|small|medium|large):
none
Do you config IPv4 for ims Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing
Enter IPv4 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :1
Enter IPv4 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 2
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv4 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for ims Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 ims service: 2500:0:0:0202:0:0:0:10
check ipaddress 2500:0:0:0202:0:0:0:10 on subnet 4

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-31
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
Enter IPv6 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 ims service: 2500:0:0:0203:0:0:0:10
check ipaddress 2500:0:0:0203:0:0:0:10 on subnet 5
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv6 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Enter the SUBNET ID for the IPv4 default gateway: 2
Enter the SUBNET ID for the IPv6 default gateway: 5
side A of pair 1 HostID 0: Enter the SHELF number [0..1]: 0
side A of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 13
side B of pair 1 HostID 0: Enter the SHELF number [0..1]: 0
side B of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 14
You are now ready to begin sim. For example:
in window 1: sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
in window 2: tail -f /var/opt/log/sim/hwgrow/sim.log
Example of HW growth with “ims ims fs5k h248”
>hwgrow
hwgrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/hwgrow/hosts.dat
for growing one card pair. Enter the service
type for the pair, and then enter the shelf and card
number for both side A and side B of the host pair.
The allowed service types are as follows:
cdr
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the SERVICE TYPE for pair 1 HostID 0: ims ims fs5k h248
Are you using offsets for "ims ims fs5k h248" (y/n) ?y
Enter the IPSEC TYPE for ims service pair 1 (none|small|medium|large):
none
Do you config IPv4 for ims Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
....................................................................................................................................................................................................................................
5-32 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing
Enter IPv4 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :1
Please enter offset for ims: 10
Enter IPv4 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 2
Please enter offset for ims: 10
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv4 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for ims Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 ims service: 2500:0:0:0202:0:0:0:10
check ipaddress 2500:0:0:0202:0:0:0:10 on subnet 4
Enter IPv6 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 ims service: 2500:0:0:0203:0:0:0:10
check ipaddress 2500:0:0:0203:0:0:0:10 on subnet 5
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv6 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Enter the IPSEC TYPE for ims service pair 2 (none|small|medium|large):
none
Do you config IPv4 for ims Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing
Enter IPv4 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :1
Please enter offset for ims: 9

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-33
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
Enter IPv4 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 2
Please enter offset for ims: 12
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv4 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for ims Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 ims service: 2500:0:0:0202:0:0:0:13
check ipaddress 2500:0:0:0202:0:0:0:13 on subnet 4
Enter IPv6 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 ims service: 2500:0:0:0203:0:0:0:13
check ipaddress 2500:0:0:0203:0:0:0:13 on subnet 5
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv6 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv4 for fs5k Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing
Enter IPv4 SUBNET ID for 1 fs5k Service with NI-default (IP 0), enter
return for skip :1
Please enter offset for fs5k: 8
Enter IPv4 SUBNET ID for fs5k Service IP 1, enter return for skip or (n/
N) for no more: 2
Please enter offset for fs5k: 14
Valid NI_Type for fs5k Service IP 1:
diam_rf,diam_ro,diam_gls,dns,enum,web_portal
Enter comma separated IP 1 NI Types for fs5k,enter return for
unassigned : diam_rf

....................................................................................................................................................................................................................................
5-34 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
Enter IPv4 SUBNET ID for fs5k Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for fs5k Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for 1 fs5k Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 fs5k service: 2500:0:0:0202:0:0:0:14
check ipaddress 2500:0:0:0202:0:0:0:14 on subnet 4
Enter IPv6 SUBNET ID for fs5k Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 fs5k service: 2500:0:0:0203:0:0:0:14
check ipaddress 2500:0:0:0203:0:0:0:14 on subnet 5
Valid NI_Type for fs5k Service IP 1:
diam_rf,diam_ro,diam_gls,dns,enum
Enter comma separated IP 1 NI Types for fs5k,enter return for
unassigned : diam_rf
Enter IPv6 SUBNET ID for fs5k Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv4 for h248 Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing
Enter IPv4 SUBNET ID for 1 h248 Service with NI-default (IP 0), enter
return for skip :1
Please enter offset for h248: 6
Enter IPv4 SUBNET ID for h248 Service IP 1, enter return for skip or (n/
N) for no more: 2
Please enter offset for h248: 15
Valid NI_Type for h248 Service IP 1:
diam_rf,dns,enum,h248sig,h248sig1,h248sig2
Enter comma separated IP 1 NI Types for h248,enter return for
unassigned : diam_rf
Enter IPv4 SUBNET ID for h248 Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for h248 Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-35
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for 1 h248 Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 h248 service: 2500:0:0:0202:0:0:0:15
check ipaddress 2500:0:0:0202:0:0:0:15 on subnet 4
Enter IPv6 SUBNET ID for h248 Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 h248 service: 2500:0:0:0203:0:0:0:15
check ipaddress 2500:0:0:0203:0:0:0:15 on subnet 5
Valid NI_Type for h248 Service IP 1:
diam_rf,dns,enum
Enter comma separated IP 1 NI Types for h248,enter return for
unassigned : diam_rf
Enter IPv6 SUBNET ID for h248 Service IP 2, enter return for skip or (n/
N) for no more: n
Enter the SUBNET ID for the IPv4 default gateway: 2
Enter the SUBNET ID for the IPv6 default gateway: 5
side A of pair 1 HostID 0: Enter the SHELF number [0..1]: 0
side A of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 13
side B of pair 1 HostID 0: Enter the SHELF number [0..1]: 0
side B of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 14
Please enter offset for h248:1 Side B on subnet 1: 5
Please enter h248 IPv6 address for Side B on subnet 4: 2500:0:0:0202:0:
0:0:16
check ipaddress 2500:0:0:0202:0:0:0:16 on subnet 4
You are now ready to begin sim. For example:
in window 1: sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
in window 2: tail -f /var/opt/log/sim/hwgrow/sim.log
...................................................................................................................................................................................................

14 On the first Active MI window, execute the following command:


sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
> sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwgrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwgrow/hwgrow.xml
Writing to log file: /var/opt/log/sim/hwgrow/sim.log
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM hwgrow start was successfully launched!
...................................................................................................................................................................................................

15 On the second active MI window, execute the following command:


tail -f /var/opt/log/sim/hwgrow/sim.log

....................................................................................................................................................................................................................................
5-36 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
Note: The second window is used to monitor SIM’s progress. If a failure occurs
during the execution of SIM, SIM initiates a ‘pause’ and reports the failure to the user
through the log file. When this occurs, the user should correct the root cause of the
error and resume the growth by typing sim hwgrow resume.
The example of a failure:
05/16/08 09:43:49 SIM025_end *** FAILURE [RC=255] ***
05/16/08 09:43:49 SIM will Pause for *** FAILURE *** after all
dispatched commands complete execution!
05/16/08 09:43:49 PAUSED: for *** FAILURE *** after all dispatched
commands completed execution!
Example of resume:
> sim hwgrow resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwgrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwgrow/hwgrow.xml
Writing to log file: /var/opt/log/sim/hwgrow/sim.log
SIM will resume applying rules from the previous pause/abort. Continue?
[y/n] y
SIM hwgrow resume will be resumed!
Note: During the execution of the growth procedures additional transient alarm
conditions may be observed. The alarms will clear without manual intervention. If the
alarms do not resolve after 10 minutes, contact your next level of support.
Note: If SIM pauses due to the failure of the service state of InService (it stays in
OOSUnavailable), then execute the following command for each blade in the pair:
resetCard -s shelf# -c card#
If failure occurs again, contact technical support.
...................................................................................................................................................................................................

16 Growth is completed successfully when log file displays:


Result
GROWTH IS COMPLETE!!!!!
All Steps Completed!
Example:
05/16/08 10:01:21 SIM069_begin [seclogger 'GROWTH IS COMPLETE
SUCCESSFULLY!'] (hwgrow:874)
05/16/08 10:01:21 SIM069_end ... Success ...
05/16/08 10:01:21 SIM070 [GROWTH IS COMPLETE!!!!!] (hwgrow:877)
05/16/08 10:01:21 All Steps Completed!

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-37
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
Growth implementation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

17 After the growth process is completed, execute the following command to update the SIM
host table.
create_ht
...................................................................................................................................................................................................

18 To perform RCC switchover, type the following command and press Enter:
rccInhibit -a CLEAR <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
...................................................................................................................................................................................................

19 Perform the global rediscovery on the MI GUI. Please refer “Global rediscovery using the
MI-GUI ” (p. 3-37).
Result: The newly grown in blades are ready to be provisioned on the Provisioning
GUI.
For more details on the Provisioning GUI refer to:
• 5450 IP Session Control Application User Guide, 275-900-361 for provisioning
IMS and H.248 services
• 5420 Converged Telephony Server (CTS) Application User Guide for provisioning
5420 CTS services
...................................................................................................................................................................................................

20 If the service has presence on multiple subnets, then static routes must be provisioned for
every subnet other than the default gateway subnet. Please refer “To add or delete static
routes for a service” (p. 8-62).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-38 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................

To grow hardware and service on diskful hosts


Purpose
Use this procedure to grow one pair of diskful hosts using the Software Installation
Manager (SIM) tool.
The following hardware type is supported
• ATCA
The following diskful services are supported
• fsdb
• cdr
• vlr (FS2500 application)
• gos
• gjs
• gls
Example of a valid service combination is as follows:
• fsdb cdr

Before you begin


Observe the following:
During the process, you need to open two windows on the active MI:
• A SIM process window to enter SIM commands. Call this window 1.
• A SIM log window to monitor SIM progress. Call this window 2.
Make sure of the following:
• The system is stable.
• Perform a system backup
• The information relevant to the new host should be kept ready.
For example:
– Card type (Advanced TCA)
– Service type
– Subnets
– Default Gateway subnet IP
– Shelf number
– Card number
– Offsets (if required)

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-39
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
– IPv6 addresses and subnet numbers (if required)
– NI types

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open two windows and from both log into MI-1 as root.
...................................................................................................................................................................................................

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active then switch by using the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command to create the host table, which will be used by the SIM
tool.
create_ht
> create_ht
Fri Apr 23 15:51:26 CDT 2010 create_ht
Fri Apr 23 15:51:26 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Fri Apr 23 15:51:26 CDT 2010 Wrote new /var/opt/lib/sim/data/hosts.dat
Fri Apr 23 15:51:26 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Fri Apr 23 15:51:26 CDT 2010 Wrote new /var/opt/lib/sim/data/hostdat.ksh
...................................................................................................................................................................................................

5 On window 1, execute the following command as root.

....................................................................................................................................................................................................................................
5-40 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
su_health -a
Note: Proceed further only if this command reports success.
...................................................................................................................................................................................................

6 To inhibit RCC on the MI-1, type the following command and press Enter:
rccInhibit -a SET <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 For each card that is to be grown, type the following command with the appropriate
<shelf number> and <card number>
isolateCard -s shelf# -c card#
> isolateCard -s 0 -c 3
SHELF=0 HUB=10.31.32.112 PORT=17 OID=9
interfaces.ifTable.ifEntry.ifAdminStatus.9 = 0
SHELF=0 HUB=10.31.32.128 PORT=17 OID=9
interfaces.ifTable.ifEntry.ifAdminStatus.9 = 0
...................................................................................................................................................................................................

8 Make sure the cards are plugged in. If not plugged in, install the blades in the slots and
connect them.
...................................................................................................................................................................................................

9 Start the tool to prepare the SIM host file.


Type the following command :
hwgrow
Note: If more than one service is grown, enter space separated service types when
prompted for the service type. The subnet information will be prompted for each
service.
Examples of hwgrow command:
> hwgrow
hwgrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/hwgrow/hosts.dat
for growing one card pair. Enter the service
type for the pair, and then enter the shelf and card
number for both side A and side B of the host pair.
The allowed service types are as follows:
cdr
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-41
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the SERVICE TYPE for pair 1 HostID 0: fsdb cdr
Are you using offsets for fsdb (y/n) ?y
Do you config IPv4 for fsdb Service (y/n) ?
n
Do you config IPv6 for fsdb Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:01f2:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:01f3:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:01f4:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for fsdb Service IP 1 : 4
Enter IPv6 address for pair 1 fsdb service: 2500:0:0:01f2:0:0:0:4
check ipaddress 2500:0:0:01f2:0:0:0:4 on subnet 4
Valid NI_Type for fsdb Service IP 1:
diam_sh,dns
Enter comma separated IP 1 NI Types for fsdb,enter return for
unassigned : diam_sh
Enter IPv6 SUBNET ID for fsdb Service IP 2, enter return for skip or (n/
N) for no more: n
Are you using offsets for cdr (y/n) ?y
Do you config IPv4 for cdr Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.31.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.160, subnet name campus
IPv4 subnet number 2, subnet base 10.241.31.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.31.64, subnet name billing
Enter IPv4 SUBNET ID for 1 cdr Service with NI-default (IP 0), enter
return for skip :1
Please enter offset for cdr: 6
Enter IPv4 SUBNET ID for cdr Service IP 1, enter return for skip or (n/
N) for no more: 3
Please enter offset for cdr: 6
Bad offset. Choose again.
7
....................................................................................................................................................................................................................................
5-42 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
Valid NI_Type for cdr Service IP 1:
diam_rf,dns
Enter comma separated IP 1 NI Types for cdr,enter return for
unassigned : dns
Enter IPv4 SUBNET ID for cdr Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for cdr Service (y/n) ?
n
Enter the SUBNET ID for the IPv4 default gateway: 1
Enter the SUBNET ID for the IPv6 default gateway: 4
side A of pair 1 HostID 0: Enter the SHELF number [0..3]: 0
side A of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 3
side B of pair 1 HostID 0: Enter the SHELF number [0..3]: 0
side B of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 4
You are now ready to begin sim. For example:
in window 1: sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
in window 2: tail -f /var/opt/log/sim/hwgrow/sim.log
> hwgrow
hwgrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/hwgrow/hosts.dat
for growing one card pair. Enter the service
type for the pair, and then enter the shelf and card
number for both side A and side B of the host pair.
The allowed service types are as follows:
cdr
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the SERVICE TYPE for pair 1 HostID 0: fsdb
Are you using offsets for fsdb (y/n) ?n
Do you config IPv4 for fsdb Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.31.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.160, subnet name campus
IPv4 subnet number 2, subnet base 10.241.31.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.31.64, subnet name billing
Enter IPv4 SUBNET ID for 1 fsdb Service with NI-default (IP 0), enter
return for skip :1
Enter IPv4 SUBNET ID for fsdb Service IP 1, enter return for skip or (n/
N) for no more: 7
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-43
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
net4conf_adm: error: IPv4 external subnet 7 does not exist
No available IP on subnet 7 now, try other subnet
2
Valid NI_Type for fsdb Service IP 1:
diam_sh,dns,fsdb_geosync
Enter comma separated IP 1 NI Types for fsdb,enter return for
unassigned : diam_sh
Enter IPv4 SUBNET ID for fsdb Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for fsdb Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:01f2:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:01f3:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:01f4:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for fsdb Service IP 1 : 4
Enter IPv6 address for pair 1 fsdb service: 2500:0:0:01f2:0:0:0:5
check ipaddress 2500:0:0:01f2:0:0:0:5 on subnet 4
Valid NI_Type for fsdb Service IP 1:
diam_sh,dns
Enter comma separated IP 1 NI Types for fsdb,enter return for
unassigned : diam_sh
Enter IPv6 SUBNET ID for fsdb Service IP 2, enter return for skip or (n/
N) for no more: n
Enter the SUBNET ID for the IPv4 default gateway: 1
Enter the SUBNET ID for the IPv6 default gateway: 4
side A of pair 1 HostID 0: Enter the SHELF number [0..3]: 0
side A of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 9
side B of pair 1 HostID 0: Enter the SHELF number [0..3]: 0
side B of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 10
You are now ready to begin sim. For example:
in window 1: sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
in window 2: tail -f /var/opt/log/sim/hwgrow/sim.log
> hwgrow
hwgrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/hwgrow/hosts.dat
for growing one card pair. Enter the service
type for the pair, and then enter the shelf and card
number for both side A and side B of the host pair.
The allowed service types are as follows:
cdr
cs
ss7
h248
vlr
ims
fsdb
....................................................................................................................................................................................................................................
5-44 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
fs5k
gls
gjs
gos
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the SERVICE TYPE for pair 1 HostID 0: fsdb cdr
Are you using offsets for "fsdb cdr" (y/n) ?n
Do you config IPv4 for fsdb Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing
Enter IPv4 SUBNET ID for 1 fsdb Service with NI-default (IP 0), enter
return for skip :1
Enter IPv4 SUBNET ID for fsdb Service IP 1, enter return for skip or (n/
N) for no more: 2
Valid NI_Type for fsdb Service IP 1:
diam_sh,dns,fsdb_geosync
Enter comma separated IP 1 NI Types for fsdb,enter return for
unassigned : diam_sh
Enter IPv4 SUBNET ID for fsdb Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for fsdb Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for fsdb Service IP 1 : 4
Enter IPv6 address for pair 1 fsdb service: 2500:0:0:0202:0:0:0:12
check ipaddress 2500:0:0:0202:0:0:0:12 on subnet 4
Valid NI_Type for fsdb Service IP 1:
diam_sh,dns
Enter comma separated IP 1 NI Types for fsdb,enter return for
unassigned : diam_sh
Enter IPv6 SUBNET ID for fsdb Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv4 for cdr Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 10.32.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.192, subnet name campus
IPv4 subnet number 2, subnet base 10.241.32.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.32.64, subnet name billing

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-45
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
Enter IPv4 SUBNET ID for 1 cdr Service with NI-default (IP 0), enter
return for skip :1
Enter IPv4 SUBNET ID for cdr Service IP 1, enter return for skip or (n/
N) for no more: 2
Valid NI_Type for cdr Service IP 1:
diam_rf,dns
Enter comma separated IP 1 NI Types for cdr,enter return for
unassigned : diam_rf
Enter IPv4 SUBNET ID for cdr Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for cdr Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:0203:0:0:0:0, prefix
length 64, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:0204:0:0:0:0, prefix
length 64, subnet name billing6
Enter IPv6 SUBNET ID for 1 cdr Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 cdr service: 2500:0:0:0202:0:0:0:13
check ipaddress 2500:0:0:0202:0:0:0:13 on subnet 4
Enter IPv6 SUBNET ID for cdr Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 cdr service: 2500:0:0:0203:0:0:0:13
check ipaddress 2500:0:0:0203:0:0:0:13 on subnet 5
Valid NI_Type for cdr Service IP 1:
diam_rf,dns
Enter comma separated IP 1 NI Types for cdr,enter return for
unassigned : diam_rf
Enter IPv6 SUBNET ID for cdr Service IP 2, enter return for skip or (n/
N) for no more: n
Enter the SUBNET ID for the IPv4 default gateway: 2
Enter the SUBNET ID for the IPv6 default gateway: 5
side A of pair 1 HostID 0: Enter the SHELF number [0..1]: 0
side A of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 3
side B of pair 1 HostID 0: Enter the SHELF number [0..1]: 0
side B of pair 1 HostID 0: Enter the CARD number [1..6,9..14]: 4
You are now ready to begin sim. For example:
in window 1: sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
in window 2: tail -f /var/opt/log/sim/hwgrow/sim.log
...................................................................................................................................................................................................

10 On the first Active MI window, execute the following command:


sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
> sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
....................................................................................................................................................................................................................................
5-46 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwgrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwgrow/hwgrow.xml
Writing to log file: /var/opt/log/sim/hwgrow/sim.log
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM hwgrow start was successfully launched!
...................................................................................................................................................................................................

11 On the second active MI window, execute the following command:


tail -f /var/opt/log/sim/hwgrow/sim.log
Note: The second window is used to monitor SIM’s progress. If a failure occurs
during the execution of SIM, SIM will initiate a ‘pause’ and report the failure to the
user via the log file. When this occurs, the user should correct the root cause of the
error and resume the growth by typing sim hwgrow resume.
The example of a failure:
11/16/09 14:43:49 SIM025_end *** FAILURE [RC=255] ***
11/16/09 14:43:49 SIM will Pause for *** FAILURE *** after all
dispatched commands complete execution!
11/16/09 14:43:49 PAUSED: for *** FAILURE *** after all dispatched
commands completed execution!
Example of resume:
> sim hwgrow resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwgrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwgrow/hwgrow.xml
Writing to log file: /var/opt/log/sim/hwgrow/sim.log
SIM will resume applying rules from the previous pause/abort. Continue?
[y/n] y
SIM hwgrow resume will be resumed!
...................................................................................................................................................................................................

12 The SIM log will PAUSE MANUALLY for jumpstarting the new blades.
...................................................................................................................................................................................................

13 When the pause happens for jumpstart, make sure the cards are plugged in and wired. If
not plugged in, install the blades in the slots and connect them.
...................................................................................................................................................................................................

14 The status of the blades can be found by logging in to the active ShMC and executing the
following commands for each blade:
# clia shmstatus
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-47
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
Host: "Active"
# clia board <card#>
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Physical Slot # 3
90: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x03
PICMG Version 2.2
Hot Swap State: M4 (Active), Previous: M3 (Activation In
Process), Last State Change Cause: Normal State Change (0x0)
96: FRU # 2 (AMC # 5)
Entity: (0xc1, 0x65)
Hot Swap State: M4 (Active), Previous: M3 (Activation In
Process), Last State Change Cause: Normal State Change (0x0)
Device ID String: "AMC HDD"
...................................................................................................................................................................................................

15 Verify that all the Hot Swap statuses of the card are active.
...................................................................................................................................................................................................

16 If the state is Inactive, then the blade needs to be powered on. It can be done from the
active ShMC as shown in the following command:
# clia activate board <board#>
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Command issued via IPMB, status = 0 (0x0)
Command executed successfully
...................................................................................................................................................................................................

17 Here is another way of powering on the blades from the MI:


resetCard -s shelf# -c card# -v poweron
resetCard -s 0 -c 4 -v poweron
ShMC_IP=10.31.64.240 SHELF=0 CARD=4
...................................................................................................................................................................................................

18 Execute for each blade:


isolateCard -s shelf# -c card# -E
> isolateCard -s 0 -c 3 -E
SHELF=0 HUB=10.31.32.112 PORT=17 OID=9
....................................................................................................................................................................................................................................
5-48 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
interfaces.ifTable.ifEntry.ifAdminStatus.9 = up(1)
SHELF=0 HUB=10.31.32.128 PORT=17 OID=9
interfaces.ifTable.ifEntry.ifAdminStatus.9 = up(1)
...................................................................................................................................................................................................

19 To jumpstart the diskful card, follow the procedure in the following topic: “To jumpstart
diskful card” (p. 5-51)
...................................................................................................................................................................................................

20 Once both blades come up, resume SIM by executing the following command:
sim hwgrow resume
> sim hwgrow resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwgrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwgrow/hwgrow.xml
Writing to log file: /var/opt/log/sim/hwgrow/sim.log
SIM will resume applying rules from the previous pause/abort. Continue?
[y/n] y
SIM hwgrow resume will be resumed!
Note: During the execution of the growth procedures additional transient alarm
conditions may be observed. The alarms will clear without manual intervention. If the
alarms do not resolve after 10 minutes, contact your next level of support.
...................................................................................................................................................................................................

21 Growth is completed successfully when log file displays:


Result
GROWTH IS COMPLETE!!!!!
All Steps Completed!
Example:
11/16/09 14:46:59 SIM096_begin [seclogger 'GROWTH IS COMPLETE
SUCCESSFULLY!'] (hwgrow:861)
11/16/09 14:46:59 SIM096_end ... Success ...
11/16/09 14:46:59 SIM097 [GROWTH IS COMPLETE!!!!!] (hwgrow:864)
11/16/09 14:46:59 All Steps Completed!
...................................................................................................................................................................................................

22 After the growth process is completed, execute the following command to update the
hosts.dat file:
create_ht

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-49
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
Growth implementation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

23 To perform RCC switchover, type the following command and press Enter:
rccInhibit -a CLEAR <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
...................................................................................................................................................................................................

24 Perform the global rediscovery on the MI GUI. Please refer “Global rediscovery using the
MI-GUI ” (p. 3-37).
...................................................................................................................................................................................................

25
Result: The newly grown in blades are ready to be provisioned on the Provisioning
GUI.
For more details on the Provisioning GUI refer to:
• 5450 IP Session Control Application User Guide, 275-900-361 for provisioning
IMS and H.248 services
• 5420 Converged Telephony Server (CTS) Application User Guide for provisioning
5420 CTS services
...................................................................................................................................................................................................

26 If the service has presence on multiple subnets, then static routes must be provisioned for
every subnet other than the default gateway subnet. Please refer “To add or delete static
routes for a service” (p. 8-62).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-50 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To jumpstart diskful card
Growth implementation
....................................................................................................................................................................................................................................

To jumpstart diskful card


Purpose
Use this procedure to jumpstart a diskful processor/application card on the 5400 Linux
CP .

Procedure
Perform the following steps to jumpstart a diskful processor card.
...................................................................................................................................................................................................

1 Open the serial port connection using SOL on the diskful blade to be jumpstarted.
Refer to “To establish a processor card SOL session” (p. 5-53).
Note: After inserting the card and starting the FRU activation procedure, it may take
up to five minutes before any output is seen on the SOL window.
If no output seen on the SOL window after 5 minutes, it is likely that the newly
inserted card had been previously used in a system and it did not have the SOL
capabilities activated. In this case, establish the serial port connection using the
faceplate (CP port) of the card. Refer to the section “Serial port setup through
faceplate” (p. 5-63) .
...................................................................................................................................................................................................

2 On the console window of the card, wait for the login prompt.
...................................................................................................................................................................................................

3 Perform the following on the console window:


1. Log in as root
If logged in without password, the card should be logged into the jumpstart
environment. Skip to Step 4. The jumpstart prompt is JUMPSTART ENVIRONMENT>/
root.
2. If prompted for password, enter the correct password and log in.
Type reboot
In the serial port window on the replacement card, type n quickly when the memory
check is performed. This is to get the replacement card to the Jumpstart prompt. The
following window is displayed when the memory check is performed.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-51
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To jumpstart diskful card
Growth implementation
....................................................................................................................................................................................................................................

3. In the serial port window on the replacement card, observe the login prompt. Login to
the card as root. No password is required to login in the jumpstart environment.
After the login, jumpstart prompt is displayed. If the jumpstart prompt is not
displayed, it means that forcing the jumpstart was not successful. If jumpstart was not
successful, perform Step 2 again.
...................................................................................................................................................................................................

4 In the serial port window on the replacement card, at the jumpstart prompt, type
jumpstart.
...................................................................................................................................................................................................

5 Wait for the jumpstart procedure to complete. When the jumpstart is completed, login
prompt is displayed on the serial port window. If jumpstart is successfully completed, you
can login to the card as root using newsys password
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-52 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To establish a processor card SOL session
Growth implementation
....................................................................................................................................................................................................................................

To establish a processor card SOL session


Purpose
Use this procedure to establish a processor card SOL session.

Before you begin


Following information is required to establish the processor card SOL session:
• External IP of the Hub
• Root password for Hub
• SOL password

Procedure
Perform the following steps to establish a processor card SOL session:
...................................................................................................................................................................................................

1 From the Linux MT, run the following command:


ssh -l root <external IP of Hub>.
...................................................................................................................................................................................................

2 Enter the root password when prompted.


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

3 Run the following command from the Hub:


console –s <shelf number> -c <card number>
...................................................................................................................................................................................................

4 Enter the SOL password when prompted.


Note: The default password is newsys. To change the password run the command:
shmc_adm –a solpassword
...................................................................................................................................................................................................

5 To terminate the session, enter the following sequence character sequence:


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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-53
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
Growth implementation
....................................................................................................................................................................................................................................

To grow service of diskless hosts for multiple services


Purpose
Use this procedure to grow additional services on the hosts of the ATCA card using the
Software Installation Manager (SIM) tool.
Note: Multiple instances (pools) of the same service type are allowed to be on the
same host.
Service growth is supported for growing a service on an existing host with one or
more services. The same service type that already exists on the host can also be
grown.
The following hardware type is supported:
• ATCA
The following diskless services are supported
• ims
• h248
• fs5k

Before you begin


Observe the following:
During the process, you need to open two windows on the lead (active) MI to observe the
status of the growth procedure:
• A SIM process window to enter SIM commands. Call this window 1.
• A SIM log window to monitor SIM progress. Call this window 2.
Make sure of the following:
• The “Hardware and service growth of diskless hosts” procedure is executed first.
• The system is stable.
• The existing service is provisioned before a new service is grown on the same
processor
• A system backup is performed.
• The information pertaining to the new host is kept ready.
For example:
– Service type
– Subnets
– Shelf number
– Card number
– IPsec type (only for IMS service type)
....................................................................................................................................................................................................................................
5-54 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
Growth implementation
....................................................................................................................................................................................................................................
– NI types assigned to a particular IP address
– Offset (if required)
– IPv6 addresses and subnet numbers (if required)

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open two windows and from both log in to MI-1 as root.


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

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active then switch by using the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command to generate hosts.dat file to be used by SIM.


create_ht
> create_ht
Tue Nov 17 15:24:14 CST 2009 create_ht
Tue Nov 17 15:24:14 CST 2009 Saving backup files to /var/opt/lib/sim/
data
Tue Nov 17 15:24:14 CST 2009 Wrote new /var/opt/lib/sim/data/hosts.dat
Tue Nov 17 15:24:14 CST 2009 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Tue Nov 17 15:24:14 CST 2009 Wrote new /var/opt/lib/sim/data/hostdat.ksh
...................................................................................................................................................................................................

5 On window 1, execute the following command as root .


su_health -a

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-55
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
Growth implementation
....................................................................................................................................................................................................................................
Note: Proceed further only if this command reports success.
...................................................................................................................................................................................................

6 To inhibit RCC on the MI-1, type the following command and press Enter:
rccInhibit -a SET <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 Start the tool to prepare the sim host file.


Type the following command :
svcgrow
Note: If internal subnet is chosen, then offsets are not needed.
Example of svcgrow command:
> svcgrow
svcgrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/svcgrow/hosts.dat
for growing one service pair on the existing
cards. Enter the service type for the pair, and then
enter the shelf, card and host number for one of the
card pair.
The allowed service types are as follows:
cs
ss7
h248
ims
fs5k
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the SERVICE TYPE for pair 1: ims
Are you using offsets for "ims" (y/n) ?n
Do you config IPv4 for ims Service (y/n) ?
y
Here are the current IPv4 subnets:
IPv4 subnet number 0, subnet base 169.254.0.0, subnet name internal
IPv4 subnet number 1, subnet base 135.1.60.64, subnet name campus
IPv4 subnet number 2, subnet base 10.241.11.0, subnet name signal
IPv4 subnet number 3, subnet base 10.241.11.64, subnet name billing
Enter 1 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :1
Enter IPv4 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 2
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
....................................................................................................................................................................................................................................
5-56 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
Growth implementation
....................................................................................................................................................................................................................................
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : diam_cx
Enter IPv4 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n
Do you config IPv6 for ims Service (y/n) ?
y
Here are the current IPv6 subnets:
IPv6 subnet number 4, subnet prefix 2500:0:0:00b4:0:0:0:0, prefix
length 63, subnet name campus6
IPv6 subnet number 5, subnet prefix 2500:0:0:00b6:0:0:0:0, prefix
length 63, subnet name signal6
IPv6 subnet number 6, subnet prefix 2500:0:0:00b8:0:0:0:0, prefix
length 63, subnet name billing6
Enter 1 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :4
Enter IPv6 address for pair 1 ims service: 2500:0:0:00b4:0:0:0:11
check ipaddress 2500:0:0:00b4:0:0:0:11 on subnet 4
Enter IPv6 SUBNET ID for ims Service IP 1, enter return for skip or (n/
N) for no more: 5
Enter IPv6 address for pair 1 ims service: 2500:0:0:00b6:0:0:0:12
check ipaddress 2500:0:0:00b6:0:0:0:12 on subnet 5
Valid NI_Type for ims Service IP 1:
pdf,diam_cx,diam_sh,diam_rf,published,signtwrk1,signtwrk2,diam_ro,diam_
e2,diam_gqp,diam_rx,diam_tx,dns,enum
Enter comma separated IP 1 NI Types for ims,enter return for
unassigned : pdf
Enter IPv6 SUBNET ID for ims Service IP 2, enter return for skip or (n/
N) for no more: n

side A of pair 1: Enter the SHELF number [0..1]: 0


side A of pair 1: Enter the CARD number [1..6,9..14]: 6
HOST_A at011-s00c06h0 ...
Enter the IPSEC TYPE for ims service pair 1 (none|small|medium|large):
none

You are now ready to begin sim. For example:


in window 1: sim svcgrow start -x svcgrow.xml -d rules/svcgrow/hosts.dat
in window 2: tail -f /var/opt/log/sim/svcgrow/sim.log
Note: At times when the IPV6 address is already in use, the following error message
can be expected:
ERROR: the IPV6 address 2500:0:0:0203:0:0:0:7 is already in use.
...................................................................................................................................................................................................

8 On the first Active MI window, execute the following command:


sim svcgrow start -x svcgrow.xml -d rules/svcgrow/hosts.dat
> sim svcgrow start -x svcgrow.xml -d rules/svcgrow/hosts.dat
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-57
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
Growth implementation
....................................................................................................................................................................................................................................
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/svcgrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/svcgrow/svcgrow.xml
Writing to log file: /var/opt/log/sim/svcgrow/sim.log
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM svcgrow start was successfully launched!
...................................................................................................................................................................................................

9 On the second active MI window, execute the following command:


tail -f /var/opt/log/sim/svcgrow/sim.log
Note: The second window is used to monitor SIM’s progress. If a failure occurs
during the execution of SIM, SIM will initiate a ‘pause’ and report the failure to the
user via the log file. When this occurs, the user should correct the root cause of the
error and resume the growth by typing sim svcgrow resume. If SIM initiates a pause
due to FAIL (this happens if the provisioning is not done for diskless service that
already exists on that blade) then the user will not be able to resume and needs to do
sim svcgrow start -x svcgrow.xml -d rules/svcgrow/hosts.dat command again.
Note: During the execution of the growth procedures additional transient alarm
conditions may be observed. The alarms will clear without manual intervention. If the
alarms do not resolve after 10 minutes, contact your next level of support.
...................................................................................................................................................................................................

10 Service Growth is completed successfully when log file displays:


Result
GROWTH IS COMPLETE!!!!!
All Steps Completed!
Example:
11/17/09 15:46:12 SIM058_begin [seclogger 'SERVICE GROWTH IS COMPLETE
SUCCESSFULLY!']
11/17/09 15:46:12 SIM058_end ... Success ...
11/17/09 15:46:12 SIM059 [GROWTH IS COMPLETE!!!!!]
11/17/09 15:46:12 All Steps Completed!
...................................................................................................................................................................................................

11 After the grow process is completed, execute the following command to update the SIM
host table.
create_ht
...................................................................................................................................................................................................

12 To perform RCC switchover, type the following command and press Enter:
rccInhibit -a CLEAR <MI-1hostname>
To check the status, type the following command and press Enter:

....................................................................................................................................................................................................................................
5-58 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
Growth implementation
....................................................................................................................................................................................................................................
rccInhibit -d <MI-1hostname>
...................................................................................................................................................................................................

13 Perform the global rediscovery on the MI GUI. Please refer “Global rediscovery using the
MI-GUI ” (p. 3-37).
...................................................................................................................................................................................................

14
Result: The newly grown in blades are ready to be provisioned on the Provisioning
GUI.
For more details on the Provisioning GUI refer to:
• 5450 IP Session Control Application User Guide for provisioning IMS and H.248
services
• 5420 Converged Telephony Server (CTS) Application User Guide for provisioning
5420 CTS services
...................................................................................................................................................................................................

15 If the service has presence on multiple subnets, then static routes must be provisioned for
every subnet other than the default gateway subnet. Please refer “To add or delete static
routes for a service” (p. 8-62).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-59
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow RTM with disk on an existing diskful host
Growth implementation
....................................................................................................................................................................................................................................

To grow RTM with disk on an existing diskful host


Purpose
Use this procedure to grow RTM with disk on an existing diskful host.

Before you begin


Observe the following:
During the process, you need to open two windows on the active MI:
• A SIM process window to enter SIM commands. Call this window 1.
• A SIM log window to monitor SIM progress. Call this window 2.
Make sure of the following:
• The system is stable.
• Perform a system backup
• The following information required to grow an RTM with disk are kept ready:
For example:
– Shelf number
– Card number

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open a window and log in to MI-1 host as root.


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

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active then switch by using the following command:
MIcmd switch vc

....................................................................................................................................................................................................................................
5-60 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To grow RTM with disk on an existing diskful host
Growth implementation
....................................................................................................................................................................................................................................
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command to create the host table, which will be used by the SIM
tool.
create_ht
> create_ht
Tue Nov 17 16:50:55 CST 2009 create_ht
Tue Nov 17 16:50:55 CST 2009 Saving backup files to /var/opt/lib/sim/
data
Tue Nov 17 16:50:55 CST 2009 Wrote new /var/opt/lib/sim/data/hosts.dat
Tue Nov 17 16:50:55 CST 2009 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Tue Nov 17 16:50:55 CST 2009 Wrote new /var/opt/lib/sim/data/hostdat.ksh
...................................................................................................................................................................................................

5 Execute the following command as root.


su_health -a
Note: Proceed further only if this command reports success.
...................................................................................................................................................................................................

6 To inhibit RCC on the MI-1, type the following command and press Enter:
rccInhibit -a SET <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 Execute the following command:


RTMgrow
> RTMgrow
RTMgrow is a tool used to grow RTM with disk
on a diskfull blade. Enter the shelf and card
number for the blade.
Log locates:
/var/opt/log/sim/RTMgrow/RTMgrow.log
Executing command: scdm_adm --action commit_config
No backup key directory found. Skipping command.
No backup directory found. Skipping command.
Executing command: scdm_adm --action backup_config

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-61
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To grow RTM with disk on an existing diskful host
Growth implementation
....................................................................................................................................................................................................................................
Enter the SHELF number [0..1] for sideA: 0
Enter the CARD number [1..14] for sideA: 3
Enter the SHELF number [0..1] for sideB: 0
Enter the CARD number [1..14] for sideB: 4
Executing command: hwconf_adm --action del_card_instance --shelfnum 0 --
cardnum 3
Executing command: hwconf_adm --action del_card_instance --shelfnum 0 --
cardnum 4

...............................................
...............................................
Wed Apr 21 05:52:05 CDT 2010 Wrote new /var/opt/lib/sim/data/hostdat.ksh
RTMGROWTH IS COMPLETE!!!!!
...................................................................................................................................................................................................

8 After the growth process is completed, execute the following command to update the
hosts.dat file:
create_ht
...................................................................................................................................................................................................

9 To perform RCC switchover, type the following command and press Enter:
rccInhibit -a CLEAR <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
...................................................................................................................................................................................................

10 Perform the global rediscovery on the MI GUI. Please refer “Global rediscovery using the
MI-GUI ” (p. 3-37).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-62 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth Overview
Serial port setup through faceplate
....................................................................................................................................................................................................................................

Serial port setup through faceplate

Overview
Purpose
This section provides the steps involved in setting up a serial port.

Materials required
Following materials are required to set up a serial port:
• A laptop
• USB-to-male DB-9 serial cable with corresponding drivers loaded on the laptop
Note: Not needed if your laptop has a DB-9 port.
• Mini-USB-to-female DB-9 cable
Important! The system must have a mini-USB-to-female DB-9 cable
• Appropriate drivers of the USB-to-male DB-9 cable loaded on the laptop
– The USB-to-male DB-9 cable is connected with the mini-USB-to-female DB-9
cable.
– The USB end connects to the laptop while the mini-USB end connects to the
faceplate.

Contents

To determine the serial port configured in laptop 5-64


To configure laptop for serial connection on Windows XP 5-66
To establish serial port connection on the laptop 5-68

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-63
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To determine the serial port configured in laptop
Serial port setup through faceplate
....................................................................................................................................................................................................................................

To determine the serial port configured in laptop


Overview
After the drivers of the USB-to-male DB-9 cable have been loaded to the laptop, a port is
configured for it. Follow the procedure below to determine which port was configured.

Materials Required
Following materials are required to set up a serial port:
• A laptop
• USB-to-male DB-9 serial cable with corresponding drivers loaded on the laptop
Note: Not needed if your laptop has a DB-9 port.
• Mini-USB-to-female DB-9 cable
Important! The system must have a mini-USB-to-female DB-9 cable
• Appropriate drivers of the USB-to-male DB-9 cable loaded on the laptop
– The USB-to-male DB-9 cable is connected with the mini-USB-to-female DB-9
cable.
– The USB end connects to the laptop while the mini-USB end connects to the
faceplate.

Procedure
...................................................................................................................................................................................................

1 Select Start ⇒ Settings ⇒ Control Panel.


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

2 Right click System and then click Open.


The System Properties window appears.
...................................................................................................................................................................................................

3 Select the Hardware tab and click Device Manager.


The Device Manager window appears.
...................................................................................................................................................................................................

4 Click “+” to the left of Ports (COM & LPT).


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

5 Plug in USB-to-male DB-9 cable or plug in mini-USB-to-female DB-9 cable.


You will find entry with the words USB to Serial and a port associated with it.
Example: (COM4).
It is COM1 if connecting the mini-USB-to-female DB-9 cable.
....................................................................................................................................................................................................................................
5-64 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To determine the serial port configured in laptop
Serial port setup through faceplate
....................................................................................................................................................................................................................................
You will use this port in the sub-section.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-65
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To configure laptop for serial connection on Windows XP
Serial port setup through faceplate
....................................................................................................................................................................................................................................

To configure laptop for serial connection on Windows XP


Overview
This procedure provides steps to configure a laptop for serial connection that runs on
Windows XP.

Materials Required
Following materials are required to set up a serial port:
• A laptop
• USB-to-male DB-9 serial cable with corresponding drivers loaded on the laptop
Note: Not needed if your laptop has a DB-9 port.
• Mini-USB-to-female DB-9 cable
Important! The system must have a mini-USB-to-female DB-9 cable
• Appropriate drivers of the USB-to-male DB-9 cable loaded on the laptop
– The USB-to-male DB-9 cable is connected with the mini-USB-to-female DB-9
cable.
– The USB end connects to the laptop while the mini-USB end connects to the
faceplate.

Procedure
...................................................................................................................................................................................................

1 Select Start ⇒ Programs ⇒ Accessories ⇒ Communications ⇒ HyperTerminal.


The Connection Description window appears.
...................................................................................................................................................................................................

2 Type a name and click OK.


The Connect to window appears.
...................................................................................................................................................................................................

3 Select the COM port from the drop-down list that you determined in the previous
sub-section.
Note: Select COM1 if laptop has a DB-9 port and click OK.
...................................................................................................................................................................................................

4 Fill in the details as given in the table for other fields:


Fields Select
Bits per second 115200
Data bits 8
....................................................................................................................................................................................................................................
5-66 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware growth To configure laptop for serial connection on Windows XP
Serial port setup through faceplate
....................................................................................................................................................................................................................................

Fields Select
Parity None
Stop bits 1
Flow control None

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

5 Click OK.
...................................................................................................................................................................................................

6 Select Save As in the File Popup window.


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

7 Give an appropriate file name.


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

8 Click Save.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 5-67
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware growth To establish serial port connection on the laptop
Serial port setup through faceplate
....................................................................................................................................................................................................................................

To establish serial port connection on the laptop


Overview
This procedure provides steps to establish serial port connection on the laptop.

Materials Required
Following materials are required to set up a serial port:
• A laptop
• USB-to-male DB-9 serial cable with corresponding drivers loaded on the laptop
Note: Not needed if your laptop has a DB-9 port.
• Mini-USB-to-female DB-9 cable
Important! The system must have a mini-USB-to-female DB-9 cable
• Appropriate drivers of the USB-to-male DB-9 cable loaded on the laptop
– The USB-to-male DB-9 cable is connected with the mini-USB-to-female DB-9
cable.
– The USB end connects to the laptop while the mini-USB end connects to the
faceplate.

Procedure
...................................................................................................................................................................................................

1 Insert serial cable between the laptop and the CP port of the blade that is monitored.
...................................................................................................................................................................................................

2 Monitor the serial port window (Refer to: “To configure laptop for serial connection on
Windows XP” (p. 5-66))
Note: Enter Return Key on the laptop if the serial port window appears blank.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5-68 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
6 6 anage system
M
configuration - hardware
de-growth

Overview
Purpose
This chapter provides procedures that the user must carry out to degrow 5400 Linux CP
hardware.

Contents

Degrowth implementation 6-2


De-growth implementation flow 6-3
To de-grow service of multiple services on diskless hosts 6-4
To de-grow hardware and service on diskless/diskful hosts 6-9

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth Overview
Degrowth implementation
....................................................................................................................................................................................................................................

Degrowth implementation

Overview
Purpose
This section describes the process flow and the procedures to perform the implementation
actions required for system degrowth.

Contents

De-growth implementation flow 6-3


To de-grow service of multiple services on diskless hosts 6-4
To de-grow hardware and service on diskless/diskful hosts 6-9

....................................................................................................................................................................................................................................
6-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware de-growth De-growth implementation flow
Degrowth implementation
....................................................................................................................................................................................................................................

De-growth implementation flow


Process flow
The process flow for degrowth the Processor cards:

Begin

Y Degrowth service on
Degrow diskless host(s) on ATCA/
1 service? for multiple services
N

Degrow Y Degrowth HW and service


2 Hardware and on diskless/diskful hosts
service?
N

End

Degrowth implementation process


Stages that should be performed:
...................................................................................................................................................................................................

1 If you de-grow service on diskless hosts (on ATCA card), use: “To de-grow service of
multiple services on diskless hosts” (p. 6-4).
Responsibility: Growth engineer
...................................................................................................................................................................................................

2 If you de-grow diskless/diskful hosts, use: “To de-grow hardware and service on
diskless/diskful hosts ” (p. 6-9).
Responsibility: Growth engineer

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth To de-grow service of multiple services on diskless hosts
Degrowth implementation
....................................................................................................................................................................................................................................

To de-grow service of multiple services on diskless hosts


Purpose
Use this procedure for de-growing one service pair of diskless hosts using the Software
Installation Manager (SIM) tool.
The following hardware type is supported
• ATCA
The following diskless services are supported
• ims
• fs5k
• h248
Note: Multiple instances (pools) of the same service type are allowed to be on the
same host.
The following combinations are valid:
• ims fs5k h248
Note: Service de-growth is only supported on a host with two or more services and
one of them needs to be de-grown.

Before you begin


Observe the following:
During the process, you need to open two windows on the lead (active) MI to observe the
status of the de-growth procedure:
• A SIM process window to enter SIM commands. Call this window 1.
• A SIM log window to monitor SIM progress. Call this window 2.
Make sure of the following:
• The system is stable.
• Perform a system backup
• The service to be de-grown is de-provisioned.
• The existing service is provisioned to avoid de-grow failure.
• Hold ready the information required for the service to be de-grown.

....................................................................................................................................................................................................................................
6-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware de-growth To de-grow service of multiple services on diskless hosts
Degrowth implementation
....................................................................................................................................................................................................................................
For example:
– Shelf number
– Card number
– Service type with pool number
• Static routes for the services being de-grown are deleted. Please refer “To add or
delete static routes for a service” (p. 8-62) for more information.

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open two windows and from both windows, log into MI-1 as root.
...................................................................................................................................................................................................

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active then switch by using the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command to create the host table, which will be used by the SIM
tool.
create_ht
> create_ht
Fri Apr 23 16:35:08 CDT 2010 create_ht
Fri Apr 23 16:35:08 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Fri Apr 23 16:35:08 CDT 2010 Wrote new /var/opt/lib/sim/data/hosts.dat
Fri Apr 23 16:35:08 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Fri Apr 23 16:35:08 CDT 2010 Wrote new /var/opt/lib/sim/data/hostdat.ksh
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-5
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth To de-grow service of multiple services on diskless hosts
Degrowth implementation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

5 On window 1, execute the following command as root.


su_health -a
Note: It is possible to receive an error regarding services that are not STBY-HOT but
are instead STBY-COLD or OOSUnavailable. It must be verified that the services
listed as being STBY-COLD/OOSUnavailable are the ones that are being de-grown. If
they are, then this error can be safely ignored.
ALL OTHER ERRORS MUST be resolved before you can proceed with this
procedure. For further assistance on this tool, please contact your technical support
representative.
...................................................................................................................................................................................................

6 To inhibit RCC on the MI-1, type the following command and press Enter:
rccInhibit -a SET <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 Execute
svcdegrow
Example of svcdegrow command:
> svcdegrow
svcdegrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/svcdegrow/hosts.dat
for de-growing one service pair. Enter the shelf
and card number for one side (A or B) for the service pair.
This tool is mainly used for the degrowth the second service on same
host.
You can use ^C (control-C) at any time to
safely abort this interactive script.
1. Enter the SHELF number [0..1]: 0
1. Enter the CARD number [1..14]: 14
Which service do you want to degrow? (h248:0 ims:0 ims:3): ims:3
You are now ready to begin sim. For example:
in window 1: sim svcdegrow start -x svcdegrow.xml -d rules/svcdegrow/
hosts.dat
in window 2: tail -f /var/opt/log/sim/svcdegrow/sim.log
...................................................................................................................................................................................................

8 On the first active MI window, execute the following command:


sim svcdegrow start -x svcdegrow.xml -d rules/svcdegrow/hosts.dat
> sim svcdegrow start -x svcdegrow.xml -d rules/svcdegrow/hosts.dat
....................................................................................................................................................................................................................................
6-6 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware de-growth To de-grow service of multiple services on diskless hosts
Degrowth implementation
....................................................................................................................................................................................................................................
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/svcdegrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/svcdegrow/svcdegrow.xml
Writing to log file: /var/opt/log/sim/svcdegrow/sim.log
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM svcdegrow start was successfully launched!
...................................................................................................................................................................................................

9 On the second active MI window, execute the following command:


tail -f /var/opt/log/sim/svcdegrow/sim.log
Note: The second window is used to monitor SIM’s progress. If a failure occurs
during the execution of SIM, SIM will initiate a ‘pause’ and report the failure to the
user via the log file. When this occurs, the user should correct the root cause of the
error and resume the de-growth by typing sim svcdegrow resume. If SIM initiates a
pause due to FAIL(this happens if the de-provisioning is not done for diskless
services) then the user will not be able to resume and needs to do sim svcdegrow start
-x svcdegrow.xml -d rules/svcdegrow/hosts.dat command again.
The example of pause due to FAIL(de-provisioning for the svc that is
being degrown is not done or the service that will remain is not
provisioned):
11/17/09 14:30:38 SIM021_begin [seclogger 'SVC DE-GROWTH IS FAILED DUE
TO NOT DE-PROVISIONING THE SERVICES!']
11/17/09 14:30:38 SIM021_end ... Success ...
11/17/09 14:30:38 Pausing: Manual Step SIM022 Found [FAIL: Please de-
provision the services before doing the de-growth.]
11/17/09 14:30:38 PAUSED: after all dispatched commands completed
execution!
> sim svcdegrow resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/svcdegrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/svcdegrow/svcdegrow.xml
Writing to log file: /var/opt/log/sim/svcdegrow/sim.log
SIM will resume applying rules from the previous pause/abort. Continue?
[y/n] y
*** Cannot resume from a previous SIM failure. ***
> sim svcdegrow start -x svcdegrow.xml -d rules/svcdegrow/hosts.dat
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/svcdegrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/svcdegrow/svcdegrow.xml

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-7
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth To de-grow service of multiple services on diskless hosts
Degrowth implementation
....................................................................................................................................................................................................................................
Writing to log file: /var/opt/log/sim/svcdegrow/sim.log
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM svcdegrow start was successfully launched!
Note: During the execution of the de-growth procedures additional transient alarm
conditions may be observed. The alarms will clear without manual intervention. If the
alarms do not resolve after 10 minutes, contact your next level of support.
...................................................................................................................................................................................................

10 Service de-growth is completed successfully when log file displays:


Result
DE-GROWTH IS COMPLETE!!!!!
All Steps Completed!
Example:
11/17/09 16:15:42 SIM063_begin [seclogger 'SVC DE-GROWTH IS COMPLETE
SUCCESSFULLY!']
11/17/09 16:15:42 SIM063_end ... Success ...
11/17/09 16:15:42 SIM064 [DE-GROWTH IS COMPLETE!!!!!]
11/17/09 16:15:42 All Steps Completed!
...................................................................................................................................................................................................

11 After the de-grow process is completed, execute the following command to update the
SIM host table.
create_ht
...................................................................................................................................................................................................

12 To perform RCC switchover, type the following command and press Enter:
rccInhibit -a CLEAR <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
...................................................................................................................................................................................................

13 Perform the global rediscovery on the MI GUI. Please refer “Global rediscovery using the
MI-GUI ” (p. 3-37).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
6-8 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
Degrowth implementation
....................................................................................................................................................................................................................................

To de-grow hardware and service on diskless/diskful hosts


Purpose
This topic provides the procedure to de-grow one pair of diskless or diskful hosts using
the Software Installation Manager (SIM) tool.
The following hardware type is supported
• ATCA
The following diskless services are supported
• ims
• fs5k
• h248
• ss7
The following diskful service is supported
• fsdb
• cdr
• vlr
• gos
• gjs
• gls

Before you begin


Observe the following:
During the process, you need to open two windows on the lead (active) MI to observe the
status of the de-growth procedure:
• A SIM process window to enter SIM commands. Call this window 1.
• A SIM log window to monitor SIM progress. Call this window 2.
Make sure of the following:
• The system is stable.
• Clean up related provisioning data on the Provisioning GUI.
• Perform a system backup.
• The shelf number and the card number should be kept ready.
• The service that will be de-grown should be de-provisioned from the Provisioning
GUI.
• Static routes for the services being de-grown are deleted. Please refer “To add or
delete static routes for a service” (p. 8-62) for more details.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-9
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
Degrowth implementation
....................................................................................................................................................................................................................................
Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open two windows and from both windows, log into MI-1 as root.
...................................................................................................................................................................................................

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active then switch by using the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command to create the host table, which will be used by the SIM
tool.
create_ht
Result:
> create_ht
Fri Apr 23 16:22:54 CDT 2010 create_ht
Fri Apr 23 16:22:54 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Fri Apr 23 16:22:54 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Fri Apr 23 16:22:54 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Fri Apr 23 16:22:54 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

5 On window 1, execute the following command as root.


su_health -a

....................................................................................................................................................................................................................................
6-10 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
Degrowth implementation
....................................................................................................................................................................................................................................
Note: It is possible to receive an error regarding services that are not STBY-HOT but
are instead STBY-COLD or OOSUnavailable. It must be verified that the services
listed as being STBY-COLD/OOSUnavailable are the ones that are being de-grown. If
they are, then this error can be safely ignored.
ALL OTHER ERRORS MUST be resolved before you can proceed with this
procedure. For futher assistance on this tool, please contact your technical support
representative.
...................................................................................................................................................................................................

6 To inhibit RCC on the MI-1, type the following command and press Enter:
rccInhibit -a SET <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 Execute
hwdegrow
Example of hwdegrow command:
> hwdegrow
hwdegrow is a tool used to prepare sim host file
/var/opt/lib/sim/data/rules/hwdegrow/hosts.dat
for de-growing one card pair. Enter the shelf
and card number for one side (A or B) for the host pair.
You can use ^C (control-C) at any time to
safely abort this interactive script.
1. Enter the SHELF number [0-1]: 0
1. Enter the CARD number [1..6,9..14]: 5
Removing the following line(s) from hosts.dat:
at032-s00c05h0 10.32.64.80 0 5 0 node A NA rem duplex diskless at032-
s00c06h0 10.32.64.96 no_patch fs5k,28,0,0,10.32.156.0;ims,26,1,0,
10.32.154.0 NA NA NBRZAM NONE
at032-s00c06h0 10.32.64.96 0 6 0 node B NA rem duplex diskless at032-
s00c05h0 10.32.64.80 no_patch fs5k,28,0,1,10.32.156.1;ims,26,1,1,
10.32.154.1 NA NA NBRZAM NONE
You are now ready to begin sim. For example:
in window 1: sim hwdegrow start -x hwdegrow.xml -d rules/hwdegrow/
hosts.dat
in window 2: tail -f /var/opt/log/sim/hwdegrow/sim.log
...................................................................................................................................................................................................

8 On the first Active MI window, execute the following command:


sim hwdegrow start -x hwdegrow.xml -d rules/hwdegrow/hosts.dat
> sim hwdegrow start -x hwdegrow.xml -d rules/hwdegrow/hosts.dat
**************************************************************

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-11
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
Degrowth implementation
....................................................................................................................................................................................................................................
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwdegrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwdegrow/hwdegrow.xml
Writing to log file: /var/opt/log/sim/hwdegrow/sim.log
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM hwdegrow start was successfully launched!
...................................................................................................................................................................................................

9 On the second active MI window, execute the following command:


tail -f /var/opt/log/sim/hwdegrow/sim.log
Note: The second window is used to monitor SIM’s progress. If a failure occurs
during the execution of SIM, SIM initiates a ‘pause’ and reports the failure to the user
through the log file. When this occurs, the user should correct the root cause of the
error and resume the de-growth by typing sim hwdegrow resume. If SIM initiates a
pause due to FAIL(this happens if the de-provisioning is not done for diskless
services) then the user will not be able to resume and needs to do sim hwdegrow start
-x hwdegrow.xml -d rules/hwdegrow/hosts.dat command again.
The example pause due to a command failure:
11/17/09 14:43:49 SIM025_end *** FAILURE [RC=255] ***
11/17/09 14:43:49 SIM will Pause for *** FAILURE *** after all
dispatched commands complete execution!
11/17/09 14:43:49 PAUSED: for *** FAILURE *** after all dispatched
commands completed execution!
When this occurs,
> sim hwdegrow resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/rules/hwdegrow/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/hwdegrow/hwdegrow.xml
Writing to log file: /var/opt/log/sim/hwdegrow/sim.log
SIM will resume applying rules from the previous pause/abort.
Continue? [y/n] y
SIM hwdegrow resume will be resumed!
The example of pause due to FAIL(de-provisioning not done):
11/17/09 15:01:11 Pausing: Manual Step SIM022 Found [FAIL: Please de-
provision the services before doing the de-growth.]
11/17/09 15:01:11 PAUSED: after all dispatched commands completed
execution!
After this failure SIM cannot be resumed as explained in the above
note. The services need to be de-provisioned and then run the sim
hwdegrow start command again.
Note: During the execution of the de-growth procedures additional transient alarm
conditions may be observed. The alarms will clear without manual intervention. If
the alarms do not resolve after 10 minutes, contact your next level of support.
....................................................................................................................................................................................................................................
6-12 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
Degrowth implementation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

10 De-growth is completed successfully when log file displays:


Result
DE-GROWTH IS COMPLETE!!!!!
All Steps Completed!
...................................................................................................................................................................................................

11 After the de-grow process is completed, execute the following command to update the
SIM host table.
create_ht
...................................................................................................................................................................................................

12 To perform RCC switchover, type the following command and press Enter:
rccInhibit -a CLEAR <MI-1hostname>
To check the status, type the following command and press Enter:
rccInhibit -d <MI-1hostname>
...................................................................................................................................................................................................

13 Unplug the blades physically once the Blue LED comes on and pull them out.
...................................................................................................................................................................................................

14 De-grow the host from the MI-GUI. For detailed steps, see “Discovery degrowth using
the MI-GUI ” (p. 3-43).
...................................................................................................................................................................................................

15 In order to de-grow from MI GUI perform the following:


1. Login to MI GUI.
2. At the MI-Agent tree view, select Office ⇒ Network Maps ⇒ <Sub-Network
Element> ⇒ LCP-(x).
3. Double click on the Shelf - (x) to access the shelf view.
4. Right click on the blade (For example: ShMC, Hub, RTM) and select the “Degrow”
option.
...................................................................................................................................................................................................

16 The “Degrow” option will remove the selected device and all of its descendants from the
MI database. During hardware de-growth, the Ethernet ports connecting to the de-grown
blades on HUB blades will be disabled. All alarms currently associated with the deleted
devices are also cleared. The alarms can also be cleared manually.

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 6-13
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
Degrowth implementation
....................................................................................................................................................................................................................................
Example of a “SYS_LinkDown” alarm to be cleared when Shelf 1 Card 14 is de-grown:
• LCP-1_CAB-0_SHELF-1_HUB-7_PORT-12:315:Link Down
• LCP-1_CAB-0_SHELF-1_HUB-8_PORT-12:315:Link Down

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

....................................................................................................................................................................................................................................
6-14 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
7 7 latform hardware
P
conversion

Overview
Purpose
This chapter contains procedures to convert platform hardware to satisfy specific
requirements.

Contents

To convert Rouzic OAM server to Molene2 OAM server 7-2


To convert Malban with HSPP4 to Malban without HSPP4 7-16
To convert Hub without HSPP4 to Hub with HSPP4 7-25
To convert Disk Schema 7-37

...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-1
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

To convert Rouzic OAM server to Molene2 OAM server


Purpose
This topic contains the procedure to convert a Rouzic OAM server to a Molene2 OAM
server.

Before you begin


Make sure of the following:
• The system is stable
• Perform a system backup
• The following information needed to convert a pair of cards:
– Shelf number
– Card number

Procedure
Perform the following:
...................................................................................................................................................................................................

1 Open two windows and from both windows, log in to MI-1 host as root.
...................................................................................................................................................................................................

2 Execute the following command to find the MI with active VM:


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 If the primary VM is not active, then switch by using the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change. .............................. MI virtual cluster
switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc

....................................................................................................................................................................................................................................
7-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

4 Execute the following command to create the host table, which will be used by the SIM
tool.
create_ht
Result:
> create_ht
Thu Mar 25 09:02:52 CDT 2010 create_ht
Thu Mar 25 09:02:52 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Thu Mar 25 09:02:52 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Thu Mar 25 09:02:52 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Thu Mar 25 09:02:52 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

5 Execute the following command as root.


su_health -a
Note: Proceed further only if this command reports success. Errors must be resolved
before proceeding with this procedure. For further assistance on this tool, please
contact next level of support.
...................................................................................................................................................................................................

6 Execute the following command to stop synchronization with OMC-CN and to turn on
the MI Maintenance flag:
mi_maint on
Example:
> mi_maint on
MI maintenance flag is now on
...................................................................................................................................................................................................

7 Execute the following command to perform MI backup:


mi_adm -v -a backup
Example:
> mi_adm -v -a backup
Backing up MI host "at072-s00c01h0":
*** Starting LSSbackup Thu Mar 25 09:16:08 CDT 2010 ***
Saving WebNMS config files to /var/opt/lib/webnms/nmsconf.zip.
Getting approximate size of backup data.
Getting miscellaneous data files.
Getting node identity files.
Getting database backup.
*** LSSbackup successful Thu Mar 25 09:16:11 CDT 2010 ***

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-3
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
*** View /var/opt/log/lss/mibackup.log ***
*** on at072-s00c01h0 for detail ***
Backing up MI host "at072-s00c02h0":
*** Starting LSSbackup Thu Mar 25 09:16:14 CDT 2010 ***
Saving WebNMS config files to /var/opt/lib/webnms/nmsconf.zip.
Getting approximate size of backup data.
Getting miscellaneous data files.
Getting node identity files.
*** LSSbackup successful Thu Mar 25 09:16:15 CDT 2010 ***
*** View /var/opt/log/lss/mibackup.log ***
*** on at072-s00c02h0 for detail ***
'backup' on MI-Agent SUCCEEDED
...................................................................................................................................................................................................

8 Execute the following command to verify successful backup:


mi_adm -v -a list_backup
Example:
> mi_adm -v -a list_backup
-----CONFIG DATA AND DATABASE BACKUPS-----
/storage/conf_backup/MI/1269526568/ :
R22.08.00 (Thu Mar 25 09:16:08 CDT 2010) 7552KB
complete
at072-s00c01h0/ R22.08.00 config backup
at072-s00c02h0/ R22.08.00 config backup
'list_backup' SUCCEEDED
...................................................................................................................................................................................................

9 From MI-1, execute the following command to stop the MI VM service on the standby
MI:
MIcmd stop alt
Example:
> MIcmd stop alt
RCCvmOffline: Offline (MIVM1A) in progress. Wait for the State Change.
...
state of MI host alternate virtual machine is O - Offline
...................................................................................................................................................................................................

10 Execute the following command to verify that the standby VM is offline:


MIcmd state vc
...................................................................................................................................................................................................

11 Log in to the MI-2 host as root. On MI-2, execute the following commands to synchronize
the files:
cd /data0
StandbyAgent cycleOnce 2>&1 | tee StandbyAgent?.log.txt

....................................................................................................................................................................................................................................
7-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
Note: The StandbyAgent? command MUST be executed on MI-2, which is standby
MI.
...................................................................................................................................................................................................

12 Exit from MI-2.


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

13 On MI-1, execute the following command to start the alternate VM:


MIcmd start alt
Example:
> MIcmd start alt
RCCvmOnline: Online (MIVM1A) in progress. Wait for the State Change.
state of MI host alternate virtual machine is S - Standby
(transitioning to Standby)
...................................................................................................................................................................................................

14 Execute the following command to verify that the standby VM is Standby:


MIcmd state vc
...................................................................................................................................................................................................

15 Continue only after it shows the alternate VM as Standby.


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

16 On MI-1, execute the following command to deactivate MI-2 with fru_cli:


fru_cli
Example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|7|8|9|10|11|12|15 ]: 2
Enter the location [ front ]: front
VM list: cnfg mi
check_mate_rcc_vm_state vm = cnfg
check_mate_rcc_vm_state vm = mi
1 of 2 services are up on the mate
WARNING: You may be trying to deactivate a card that has ACTIVE
services.
The mate of the card to be deactivated is NOT active with all the
services.
An OUTAGE may occur if you continue without switching all ACTIVE
services
from this card to the mate card.
Are you sure you want to proceed? [y|n]y

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-5
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
You are about to deactivate Shelf-Card: 00-02
Type 'y' to proceed [y|n]y
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/deactivate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 02 R22.08.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

17 On the second active MI window, execute the following command:


tail -f /var/opt/log/sim/fru/sim.log
Note: The second window is used to monitor SIM’s progress. If a failure occurs
during the execution of SIM, SIM initiates a ‘pause’ and reports the failure to the user
through the log file. When this occurs, the user should correct the root cause of the
error and resume the growth by typing sim fru resume.
The example of a failure:
11/16/09 14:43:49 SIM025_end *** FAILURE [RC=255] ***
11/16/09 14:43:49 SIM will Pause for *** FAILURE *** after all
dispatched commands complete execution!
11/16/09 14:43:49 PAUSED: for *** FAILURE *** after all dispatched
commands completed execution!
...................................................................................................................................................................................................

18 When the SIM rules are completed, wait until the blade is completely powered down.
...................................................................................................................................................................................................

19 Once the blade is completely powered down, remove the card.


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

20 Replace it with the Molene2 diskful hardware.


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

21 Execute the following command to remove the old hardware from data:
hwconf_adm --action del_card_instance --shelfnum <shelf number> --
cardnum <card number>
Example:
> hwconf_adm --action del_card_instance --shelfnum 0 --cardnum 2
...................................................................................................................................................................................................

22 Execute the following command to get the front and rear mnemonics of the new card:
getMnemonic -s <shelf number> -c <card number>
....................................................................................................................................................................................................................................
7-6 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
Example:
> getMnemonic -s 0 -c 2
FMO16JD;NONE
...................................................................................................................................................................................................

23 Execute the following command to add the card information:


hwconf_adm --action add_card_instance --shelfnum <shelf number> --
cardnum <card number> --frontmnemonic <front mnemonic> --
rearmnemonic <rear mnemonic>
Example:
hwconf_adm --action add_card_instance --shelfnum 0 --cardnum 2 --
frontmnemonic FMO16JD --rearmnemonic NONE
...................................................................................................................................................................................................

24 Execute the following command to set the disk scheme:


hwconf_adm --action set_disk_scheme --shelfnum <shelf number> --cardnum
<card number> --hostnum <host number> --diskid <disk id> --
schemename <scheme name>
Example:
hwconf_adm --action set_disk_scheme --shelfnum 0 --cardnum 2 --
hostnum 0 --diskid front:1 --schemename LCP_base_300
...................................................................................................................................................................................................

25 Execute the following command to generate the system configuration data:


scdf_adm --action generate_host_all
...................................................................................................................................................................................................

26 Execute the following command to install the system configuration data:


scdf_adm --action install_host_local --growth
...................................................................................................................................................................................................

27 Execute the following command to synchronize the database:


syncConfigDB -l
When prompted, enter y.
Example:
> syncConfigDB -l
Synchronization is necessary, the following changes
are required:
delete from cfg.ipcfg_hosts where
(shelf_id = 0 and card_id = 2 and host_id = 0)
insert into cfg.ipcfg_hosts (shelf_id, card_id,
host_id, cpu_type, host_ip, host_name, pmc1, pmc2,
maint_cond, software_version, load_ind, lsn0_iface,
lsn0_ip, lsn1_iface, lsn1_ip, iface_l, iface_r,
dhcp0_ip, dhcp1_ip, function_type, mnemonic)
values (0, 2, 0, -1,

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-7
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
'000A484020000000000000000000000000000000',
'at072-s00c02h0', 2, -1, 1, 'R22.08.00', 1,
'eth0.800:0', '000A482020000000000000000000000000000000', 'eth1.801:0',
'000A483020000000000000000000000000000000',
'eth0.800:1', 'eth1.801:1',
'0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'node',
'FMO16JD')
Do you want to make the changes listed above ? (y/n) y
Synchronization complete.
Command completed successfully.
...................................................................................................................................................................................................

28 Execute the following command to activate the new Molene2 card in Slot 2:
fru_cli
Example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
Enter the CARD number [ 2 ]: 2
CARD number = 2
Enter the location [ front ]: front
Warning: Newly inserted card doesn't match with previous card type.
If this procedure is executed as part of the card conversion procedure,
type 'y' to proceed. Otherwise, type 'n' to exit [y|n]: y
You are about to activate Shelf-Card: 00-02
Type 'y' to proceed [y|n]y
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 02 R22.08.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

29 On the second active MI-1 window, execute the following command to tail the SIM log:
tail -f /var/opt/log/sim/fru/sim.log

....................................................................................................................................................................................................................................
7-8 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

30 SIM will pause for jumpstart of Blade 2.


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

31 To jumpstart the diskful card, follow the procedure in the following topic: “To jumpstart
diskful card” (p. 5-51)
...................................................................................................................................................................................................

32 Once jumpstart is completed successfully, execute the following command to resume:


sim fru resume
Example:
> sim fru resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 02 R22.08.00 front local_disk
SIM will resume applying rules from the previous pause/abort. Continue?
[y/n] y
SIM fru resume will be resumed!
...................................................................................................................................................................................................

33 Wait until the SIM rules are completed successfully in the SIM log.
...................................................................................................................................................................................................

34 Execute the following commands on MI-1:


scdf_adm --action install_host_all --growth
dhcpconf_adm --action control_host_all --command reload
scdm_adm --action sync_config
create_ht
...................................................................................................................................................................................................

35 Log into MI-2 as root and execute the following commands:


scdf_adm --action generate_host_all
create_ht
...................................................................................................................................................................................................

36 Exit from MI-1 window.


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

37 Log in to MI-2 window as root.


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

38 Execute the following command to switch the MI to make the new Molene2 blade active:
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-9
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
MIcmd switch vc
...................................................................................................................................................................................................

39 Execute the following command to verify that MI-2 is active:


MIcmd state vc
...................................................................................................................................................................................................

40 On MI-2, execute the following command to deactivate Blade 1 with fru_cli:


fru_cli
Example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|7|8|9|10|11|12|15 ]: 1
Enter the location [ front ]: front
VM list: cnfg mi
check_mate_rcc_vm_state vm = cnfg
check_mate_rcc_vm_state vm = mi
1 of 2 services are up on the mate
WARNING: You may be trying to deactivate a card that has ACTIVE
services.
The mate of the card to be deactivated is NOT active with all the
services.
An OUTAGE may occur if you continue without switching all ACTIVE
services
from this card to the mate card.
Are you sure you want to proceed? [y|n]y
You are about to deactivate Shelf-Card: 00-01
Type 'y' to proceed [y|n]y
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/deactivate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 01 R22.08.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

41 Execute the following command to tail the SIM log:


tail -f /var/opt/log/sim/fru/sim.log

....................................................................................................................................................................................................................................
7-10 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

42 When SIM rules are done, wait until the blade is completely powered down.
...................................................................................................................................................................................................

43 Once the blade is completely powered down, remove the card.


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

44 Replace the blade with a new Molene2 diskful blade.


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

45 Execute the following command to remove the old hardware from data:
hwconf_adm --action del_card_instance --shelfnum <shelf number> --
cardnum <card number>
Example:
> hwconf_adm --action del_card_instance --shelfnum 0 --cardnum 1
...................................................................................................................................................................................................

46 Execute the following command to get the front and rear mnemonics of the new card:
getMnemonic -s <shelf number> -c <card number>
Example:
> getMnemonic -s 0 -c 1
FMO16JD;NONE
...................................................................................................................................................................................................

47 Execute the following command to add the card information:


hwconf_adm --action add_card_instance --shelfnum <shelf number> --
cardnum <card number> --frontmnemonic <front mnemonic> --
rearmnemonic <rear mnemonic>
Example:
hwconf_adm --action add_card_instance --shelfnum 0 --cardnum 1 --
frontmnemonic FMO16JD --rearmnemonic NONE
...................................................................................................................................................................................................

48 Execute the following command to set the disk scheme:


hwconf_adm --action set_disk_scheme --shelfnum <shelf number> --cardnum
<card number> --hostnum <host number> --diskid <disk id> --
schemename <scheme name>
Example:
hwconf_adm --action set_disk_scheme --shelfnum 0 --cardnum 1 --
hostnum 0 --diskid front:1 --schemename LCP_base_300
...................................................................................................................................................................................................

49 Execute the following command to generate system configuration data:


scdf_adm --action generate_host_all

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-11
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

50 Execute the following command to install the system configuration data:


scdf_adm --action install_host_local --growth
...................................................................................................................................................................................................

51 Execute the following command to synchronize the database:


syncConfigDB -l
When prompted, enter y.
Example:
> syncConfigDB -l
Synchronization is necessary, the following changes
are required:
delete from cfg.ipcfg_hosts where (shelf_id = 0 and
card_id = 1 and host_id = 0)
insert into cfg.ipcfg_hosts (shelf_id, card_id,
host_id, cpu_type, host_ip, host_name, pmc1, pmc2,
maint_cond, software_version, load_ind, lsn0_iface,
lsn0_ip, lsn1_iface, lsn1_ip, iface_l, iface_r,
dhcp0_ip, dhcp1_ip, function_type, mnemonic)
values (0, 1, 0, -1,
'000A484010000000000000000000000000000000',
'at072-s00c01h0', 2, -1, 1, 'R22.08.00', 1,
'eth0.800:0',
'000A482010000000000000000000000000000000',
'eth1.801:0',
'000A483010000000000000000000000000000000',
'eth0.800:1', 'eth1.801:1',
'0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'node',
'FMO16JD')
Do you want to make the changes listed above ? (y/n) y
Synchronization complete.
Command completed successfully.
...................................................................................................................................................................................................

52 Execute the following command to activate the new Molene2 card in Slot 1:
fru_cli
Example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0

....................................................................................................................................................................................................................................
7-12 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

....................................................................................................................................................................................................................................
Enter the CARD number [ 1 ]: 1
CARD number = 1
Enter the location [ front ]: front
Warning: Newly inserted card doesn't match with previous card type.
If this procedure is executed as part of the card conversion procedure,
type 'y' to proceed. Otherwise, type 'n' to exit [y|n]: y
You are about to activate Shelf-Card: 00-01
Type 'y' to proceed [y|n]y
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 01 R22.08.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

53 On the second active MI-2 window, execute the following command to tail the SIM log:
tail -f /var/opt/log/sim/fru/sim.log
...................................................................................................................................................................................................

54 SIM will pause for jumpstart of Blade 1.


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

55 To jumpstart the diskful card, follow the procedure in the following topic: “To jumpstart
diskful card” (p. 5-51)
...................................................................................................................................................................................................

56 Once the jumpstart is completed successfully, execute the following command to resume:
sim fru resume
Example:
> sim fru resume
**************************************************************
* Lucent SoftSwitch (LSS) *
* Software Installation Manager (SIM) *
**************************************************************
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 02 R22.08.00 front local_disk
SIM will resume applying rules from the previous pause/abort. Continue?
[y/n] y
SIM fru resume will be resumed!

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-13
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

57 Wait until the SIM rules are completed successfully in the SIM log.
...................................................................................................................................................................................................

58 On MI-2, execute the following commands:


scdf_adm --action install_host_all --growth
dhcpconf_adm --action control_host_all --command reload
tzconf_adm --action set_all
scdm_adm --action sync_config
create_ht
...................................................................................................................................................................................................

59 On MI-1, Execute the following commands:


scdf_adm --action generate_host_all
create_ht
...................................................................................................................................................................................................

60 Execute the following command to perform a switchover:


MIcmd switch vc
...................................................................................................................................................................................................

61 Execute the following command to verify that the switchover is complete:


MIcmd state vc
...................................................................................................................................................................................................

62 Perform the global rediscovery on the MI GUI. Please refer “Global rediscovery using the
MI-GUI ” (p. 3-37).
Result: The newly grown in blades are ready to be provisioned on the Provisioning
GUI.
For more details on the Provisioning GUI refer to:
• 5450 IP Session Control Application User Guide, 275-900-361 for provisioning
IMS and H.248 services
• 5420 Converged Telephony Server (CTS) Application User Guide for provisioning
5420 CTS services
...................................................................................................................................................................................................

63 Execute the following command to turn off the MI maintenance flag:


mi_maint off
Example:
> mi_maint off
Purging cleared alarms. This may take a minute or two if there
is a large quantity of cleared alarms in the MI database.
...alarms deleted: 119
MI maintenance flag is now off

....................................................................................................................................................................................................................................
7-14 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Rouzic OAM server to Molene2 OAM server

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

64 Execute the following command to verify the MI maintenance flag:


mi_maint status
Example:
> mi_maint status
off
...................................................................................................................................................................................................

65 Log in to the OMC-CN Primary GUI as a user with administrative privileges and verify
the blades.
Note: It might take some time before the synchronization happens and the correct
hardware type is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-15
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

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

To convert Malban with HSPP4 to Malban without HSPP4


Prerequisites
• Stable system.
• Perform a system backup.
• Ensure there is no service presence on HSPP4.
• Information required to convert a pair of cards - Shelf number and card number.

Procedure
...................................................................................................................................................................................................

1 Open a window and log into MI-1 host as root.


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

2 To find out the MI with active VM , execute the following command:


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 If the second MI is active, switch to the active MI by executing the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change.
.............................
MI virtual cluster switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command:


create_ht
> create_ht
Wed Mar 24 11:58:50 CDT 2010 create_ht
Wed Mar 24 11:58:50 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Wed Mar 24 11:58:50 CDT 2010 Wrote new /var/opt/lib/sim/data/hosts.dat
Wed Mar 24 11:58:50 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Wed Mar 24 11:58:50 CDT 2010 Wrote new /var/opt/lib/sim/data/hostdat.ksh

....................................................................................................................................................................................................................................
7-16 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

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

5 On the MI window, execute the following command as root:


su_health -a
Note: Errors must be resolved before you can proceed with this procedure. For futher
assistance on this tool, contact Alcatel-Lucent technical support representative.
...................................................................................................................................................................................................

6 Inhibit the switchover of MI by executing the following command:


rccInhibit -a SET MI-1hostname
Check the status by executing the following command:
rccInhibit -d MI-1hostname
For example:
rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 Deactivate hub 8 by executing the following command:


fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|5|6|7|8|11|12|15 ]: 8
Enter the location [ front|rear ]: front
You are about to deactivate Shelf-Card: 00-08
Type 'y' to proceed [y|n]y
Hub Card 00-08 deactivation SUCCESSFUL
...................................................................................................................................................................................................

8 Once the blade is completely powered down, remove the card.


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

9 Remove the old hardware from the data by executing the following command on the MI:
hwconf_adm --action del_card_instance --shelfnum <shelf number> --
cardnum <card number>
For example:
> hwconf_adm --action del_card_instance --shelfnum 0 --
cardnum 8
...................................................................................................................................................................................................

10 Replace it with a hub with no HSPP4.


....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-17
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

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

11 Get the front and rear mnemonics of the new card by executing the following command:
getMnemonic -s <shelf number> -c <card number>
For example:
> getMnemonic -s 0 -c 8
NBMASW1;NONE
...................................................................................................................................................................................................

12 Add the card information by executing the following command:


hwconf_adm --action add_card_instance --shelfnum <shelf number> --
cardnum <card number> --frontmnemonic front mnemonic --rearmnemonic
rear mnemonic
For example:
hwconf_adm --action add_card_instance --shelfnum 0 --cardnum
8 --frontmnemonic NBMASW1 --rearmnemonic NONE
...................................................................................................................................................................................................

13 Generate SSH keys using the following command:


sshconf_adm --action key_host_instance --shelfnum <shelf
number> --cardnum <card number> --hostnum host number
For example:
sshconf_adm --action key_host_instance --shelfnum 0 --cardnum 8 --
hostnum 4
...................................................................................................................................................................................................

14 Generate System Configuration data by executing the following command:


scdf_adm --action generate_host_all
...................................................................................................................................................................................................

15 Install System Configuration data by executing the following command:


scdf_adm --action install_host_all --growth
...................................................................................................................................................................................................

16 Synchronize the database by executing the following command:


syncConfigDB -l
When prompted, enter y.
For example:
> syncConfigDB -l
Synchronization is necessary, the following changes are required:
delete from cfg.ipcfg_hosts where (shelf_id = 0 and card_id = 8 and
host_id = 0)
delete from cfg.ipcfg_hosts where (shelf_id = 0 and card_id = 8 and
host_id = 4)

....................................................................................................................................................................................................................................
7-18 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

....................................................................................................................................................................................................................................
insert into cfg.ipcfg_hosts (shelf_id, card_id, host_id, cpu_type,
host_ip, host_name, pmc1, pmc2, maint_cond, software_version,
load_ind, lsn0_iface, lsn0_ip, lsn1_iface, lsn1_ip, iface_l,
iface_r, dhcp0_ip, dhcp1_ip, function_type, mnemonic) values (0,
8, 0, -1, '000A474080000000000000000000000000000000', 'at071-
s00c08h0', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472080000000000000000000000000000000', 'eth1.801:0',
'000A473080000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'hub', 'NBMASW1')
Do you want to make the changes listed above ? (y/n) y
Synchronization complete.
Command completed successfully.
...................................................................................................................................................................................................

17 Execute the following command:


create_ht
For example:
> create_ht
Wed Mar 24 13:01:34 CDT 2010 create_ht
Wed Mar 24 13:01:34 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Wed Mar 24 13:01:34 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Wed Mar 24 13:01:34 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Wed Mar 24 13:01:34 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

18 Activate the new hub card in slot 8 by executing the following command:
fru_cli
Note: A root password is required for the blade. When prompted for factory blade,
enter alatcav2.
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
Enter the CARD number [ 8 ]: 8
CARD number = 8
Enter the location [ front ]: front
You are about to activate Shelf-Card: 00-08
Type 'y' to proceed [y|n]y
Please wait. Activation in progress ...
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-19
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

....................................................................................................................................................................................................................................
... Mac address updated successfully.
... Metadata updated successfully.
... DHCP configuration generated successfully.
... DHCP configuration installed successfully.
... DHCP configuration restarted successfully.
... Hub card entries in known_hosts file updated successfully.
... Card is up.
... Checking SOL configuration on the mate Hub.
If prompted, enter the password for Hub Card's root login below.
Enter password for the "root" login:
Starting SSH session to at071-s00c08h0
Running hub configuration data audit on hub at071-s00c08h0...
Generated hub configuration files are up-to-date for at071-s00c08h0
Hub configuration files need updated on at071-s00c08h0
Checking payload version on at071-s00c08h0...
Payload package version == 2.4.1/1, Payload hub version == 2.4.1/1
Payload version is up-to-date on at071-s00c08h0
Configuration data update required.
Copying files to at071-s00c08h0...
Running SOL 'enable' action on at071-s00c08h0
Configuration complete... rebooting at071-s00c08h0
Resetting hub at071-s00c08h0...
..................................
Sleeping 30 seconds while hub finishes booting...
Connecting to at071-s00c08h0...
Starting SSH session to at071-s00c08h0
Checking watchdog status
The reset of hub at071-s00c08h0 completed successfully
Waiting for 2 minutes -- Checking for unexpected reboots
Checking IPMC versions on at071-s00c08h0...
IPMC package version == 3.1.12, IPMC card version == 3.1.12
IPMC version is up-to-date
Checking MMC versions on at071-s00c08h0...
No AMC slots populated
Checking BIOS version on at071-s00c08h0...
BIOS package version == 2.2.0/2, BIOS card version == 2.2.0/2
BIOS version is up-to-date
'update' on at071-s00c08h0 SUCCEEDED
... Hub configuration updated successfully.
at071-s00c01h0: generating SSH keys... done
at071-s00c02h0: generating SSH keys... done
at071-s00c03h0: generating SSH keys... done
at071-s00c04h0: generating SSH keys... done
at071-s00c05h0: generating SSH keys... done
at071-s00c06h0: generating SSH keys... done
at071-s00c07h0: aquiring SSH keys... done
at071-s00c07h4: generating SSH keys... done
at071-s00c08h0: aquiring SSH keys... done
at071-s00c11h0: generating SSH keys... done
....................................................................................................................................................................................................................................
7-20 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

....................................................................................................................................................................................................................................
at071-s00c12h0: generating SSH keys... done
at071-s00c15h0: aquiring SSH keys... done
at071-s00c01h0: generating SSH daemon configuration... done
at071-s00c02h0: generating SSH daemon configuration... done
at071-s00c03h0: generating SSH daemon configuration... done
at071-s00c04h0: generating SSH daemon configuration... done
at071-s00c05h0: generating SSH daemon configuration... done
at071-s00c06h0: generating SSH daemon configuration... done
at071-s00c11h0: generating SSH daemon configuration... done
at071-s00c12h0: generating SSH daemon configuration... done
at071-s00c01h0: installing SSH daemon configuration... done
at071-s00c02h0: installing SSH daemon configuration... done
at071-s00c03h0: installing SSH daemon configuration... done
at071-s00c04h0: installing SSH daemon configuration... done
at071-s00c05h0: installing SSH daemon configuration... done
at071-s00c06h0: installing SSH daemon configuration... done
syncing RADIUS badwords file... done
syncing RADIUS license file... done
syncing RADIUS key file... done
... SSH configuration updated successfully.
... All Services are active.
Hub Card 00-08 activation SUCCESSFUL.
...................................................................................................................................................................................................

19 Deactivate hub 7 by executing the following command:


fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|5|6|7|8|11|12|15 ]: 7
Enter the location [ front|rear ]: front
You are about to deactivate Shelf-Card: 00-07
Type 'y' to proceed [y|n]y
Hub Card 00-08 deactivation SUCCESSFUL
...................................................................................................................................................................................................

20 Once the blade is completely powered down, remove the card.


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

21 Remove the old hardware from data by executing the following command on the MI:
hwconf_adm --action del_card_instance --shelfnum <shelf number> --
cardnum <card number>

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-21
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

....................................................................................................................................................................................................................................
For example:
hwconf_adm --action del_card_instance --shelfnum 0 --cardnum 8
...................................................................................................................................................................................................

22 Replace it with a hub with no HSPP4.


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

23 Get the front and rear mnemonics of the new card by executing the following command:
getMnemonic -s <shelf number> -c <card number>
For example:
> getMnemonic -s 0 -c 7
NBMASW1;NONE
...................................................................................................................................................................................................

24 Add the card information by executing the following command:


hwconf_adm --action add_card_instance --shelfnum <shelf number> --
cardnum <card number> --frontmnemonic front mnemonic --rearmnemonic
rear mnemonic
For example:
hwconf_adm --action add_card_instance --shelfnum 0 --cardnum
7 --frontmnemonic NBMASW1 --rearmnemonic NONE
...................................................................................................................................................................................................

25 Generate SSH keys using the following command:


sshconf_adm --action key_host_instance --shelfnum <shelf
number> --cardnum <card number> --hostnum <host number>
For example:
sshconf_adm --action key_host_instance --shelfnum 0 --cardnum 7 --
hostnum 4
...................................................................................................................................................................................................

26 Generate System Configuration data by executing the following command:


scdf_adm --action generate_host_all
...................................................................................................................................................................................................

27 Install System Configuration data by executing the following command:


scdf_adm --action install_host_all --growth
...................................................................................................................................................................................................

28 Synchronize the database by executing the following command:


syncConfigDB -l
When prompted, enter y.

....................................................................................................................................................................................................................................
7-22 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

....................................................................................................................................................................................................................................
For example:
> syncConfigDB -l
Synchronization is necessary, the following changes are required:
delete from cfg.ipcfg_hosts where (shelf_id = 0 and card_id = 7 and
host_id = 0)
delete from cfg.ipcfg_hosts where (shelf_id = 0 and card_id = 7 and
host_id = 4)
insert into cfg.ipcfg_hosts (shelf_id, card_id, host_id, cpu_type,
host_ip, host_name, pmc1, pmc2, maint_cond, software_version,
load_ind, lsn0_iface, lsn0_ip, lsn1_iface, lsn1_ip, iface_l,
iface_r, dhcp0_ip, dhcp1_ip, function_type, mnemonic) values (0,
7, 0, -1, '000A474070000000000000000000000000000000', 'at071-
s00c07h0', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472070000000000000000000000000000000', 'eth1.801:0',
'000A473070000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'hub', 'NBMASW1')
Do you want to make the changes listed above ? (y/n) y
Synchronization complete.
Command completed successfully.
...................................................................................................................................................................................................

29 Execute the following command:


create_ht
For example:
> create_ht
Wed Mar 24 13:34:08 CDT 2010 create_ht
Wed Mar 24 13:34:08 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Wed Mar 24 13:34:08 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Wed Mar 24 13:34:08 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Wed Mar 24 13:34:08 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

30 Activate the new hub card in slot 7 by executing the following command:
fru_cli
A root password is required for the blade. If prompted for a factory blade, enter alatcav2.
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-23
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Malban with HSPP4 to Malban without HSPP4

....................................................................................................................................................................................................................................
Enter the CARD number [ 7 ]: 7
CARD number = 7
Enter the location [ front ]: front
You are about to activate Shelf-Card: 00-07
Type 'y' to proceed [y|n]y
Please wait. Activation in progress ...
... Mac address updated successfully.
... Metadata updated successfully.
... DHCP configuration generated successfully.
... DHCP configuration installed successfully.
... DHCP configuration restarted successfully.
... Hub card entries in known_hosts file updated successfully.
... Card is up.
... Checking SOL configuration on the mate Hub.
If prompted, enter the password for Hub Card's root login below.
Enter password for the "root" login:
Starting SSH session to at071-s00c07h0
..
..
..
..
..
Hub Card 00-07 activation SUCCESSFUL.
...................................................................................................................................................................................................

31 Synchronize the meta data by executing the following command:


scdm_adm --action sync_config
...................................................................................................................................................................................................

32 Allow MI switchover by executing the following command:


rccInhibit -a CLEAR MI-1hostname
Check the status by executing the following command:
rccInhibit -d MI-1hostname
...................................................................................................................................................................................................

33 On MI-2 execute the following commands:


scdf_adm --action generate_host_all
create_ht
...................................................................................................................................................................................................

34 MI GUI rediscovery must be triggered.


For information on MI GUI rediscovery procedures, see “Global rediscovery using the
MI-GUI ” (p. 3-37).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
7-24 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

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

To convert Hub without HSPP4 to Hub with HSPP4


Prerequisites
• Stable system.
• Perform a system backup.
• The information needed to convert a pair of cards - shelf number and card number.

Procedure
...................................................................................................................................................................................................

1 Open a window and log into MI-1 host as root.


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

2 To find out the MI with active VM, execute the following command:
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 If the second MI is active, they can be switched using the following command:
MIcmd switch vc
> MIcmd switch vc
Complete RCCvcswitch successfully: Wait for State Change.
..............................
MI virtual cluster switched over successfully.
Verify that the primary VM is active by typing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Execute the following command:


create_ht
> create_ht
Wed Mar 24 14:08:45 CDT 2010 create_ht
Wed Mar 24 14:08:45 CDT 2010 Saving backup files to /var/opt/lib/
sim/data
Wed Mar 24 14:08:45 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-25
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
Wed Mar 24 14:08:45 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Wed Mar 24 14:08:45 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

5 On first window, execute the commands as root:


su_health -a
Note: Errors must be resolved before you proceed with this procedure. For further
assistance on this tool, contact the Alcatel-Lucent technical support representative.
...................................................................................................................................................................................................

6 Execute the following command to Inhibit switchover of MI:


rccInhibit -a SET MI-1hostname
Check the status by typing the command:
rccInhibit -d MI-1hostname
Example: rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................

7 Deactivate hub 8 by typing the command:


fru_cli
Example of fru_cli command:
fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to safely abort this
interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|5|6|7|8|11|12|15 ]: 8
Enter the location [ front|rear ]: front
You are about to deactivate Shelf-Card: 00-08
Type 'y' to proceed [y|n]y
Hub Card 00-08 deactivation SUCCESSFUL
...................................................................................................................................................................................................

8 Once the blade is completely powered down, remove the card.

....................................................................................................................................................................................................................................
7-26 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

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

9 Remove the old hardware from data by executing the following command on the MI:
hwconf_adm --action del_card_instance --shelfnum <shelf number> --
cardnum <card number>
Example:
> hwconf_adm --action del_card_instance --shelfnum 0 --cardnum 8
...................................................................................................................................................................................................

10 Replace it with a hub with HSPP4.


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

11 Get the front and rear mnemonics of the new card by typing the following command:
getMnemonic -s <shelf number> -c <card number>
Example: getMnemonic -s 0 -c 8
FMA1AD;NONE
...................................................................................................................................................................................................

12 Execute the following command to add the card information:


hwconf_adm --action add_card_instance --shelfnum <shelf number> --
cardnum <card number> --frontmnemonic front mnemonic --rearmnemonic
rear mnemonic
Example:
hwconf_adm --action add_card_instance --shelfnum 0 --cardnum 8 --
frontmnemonic FMA1AD --rearmnemonic NONE
...................................................................................................................................................................................................

13 Generate SSH keys


sshconf_adm --action key_host_instance --shelfnum <shelf number> --
cardnum <card number> --hostnum host number
Example:
sshconf_adm --action key_host_instance --shelfnum 0 --cardnum
8 --hostnum 4
...................................................................................................................................................................................................

14 Generate System Configuration data by executing the following command:


scdf_adm --action generate_host_all
...................................................................................................................................................................................................

15 Install System Configuration data by executing the following command:


scdf_adm --action install_host_all --growth
...................................................................................................................................................................................................

16 Synchronize the database by executing the following command:


syncConfigDB -l
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-27
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
When prompted, enter y.
Example:
> syncConfigDB -l
Synchronization is necessary, the following changes are required:
delete from cfg.ipcfg_hosts where (shelf_id = 0 and card_id = 8
and host_id = 0)
insert into cfg.ipcfg_hosts (shelf_id, card_id, host_id, cpu_
type, host_ip, host_name, pmc1, pmc2, maint_cond, software_
version, load_ind, lsn0_iface, lsn0_ip, lsn1_iface, lsn1_ip,
iface_l, iface_r, dhcp0_ip, dhcp1_ip, function_type, mnemonic)
values (0, 8, 0, -1, '000A474080000000000000000000000000000000',
'at071-s00c08h0', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472080000000000000000000000000000000', 'eth1.801:0',
'000A473080000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'hub', 'FMA1AD')
insert into cfg.ipcfg_hosts (shelf_id, card_id, host_id, cpu_
type, host_ip, host_name, pmc1, pmc2, maint_cond, software_
version, load_ind, lsn0_iface, lsn0_ip, lsn1_iface, lsn1_ip,
iface_l, iface_r, dhcp0_ip, dhcp1_ip, function_type, mnemonic)
values (0, 8, 4, -1, '000A474084000000000000000000000000000000',
'at071-s00c08h4', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472084000000000000000000000000000000', 'eth1.801:0',
'000A473084000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'node', 'FMA1AD')
Do you want to make the changes listed above ? (y/n) y
Synchronization complete. Command completed successfully.
...................................................................................................................................................................................................

17 Execute the following command:


create_ht
Example:
> create_ht
Wed Mar 24 14:40:25 CDT 2010 create_ht
Wed Mar 24 14:40:25 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Wed Mar 24 14:40:25 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat

....................................................................................................................................................................................................................................
7-28 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
Wed Mar 24 14:40:25 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Wed Mar 24 14:40:25 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

18 Activate the new hub card in slot 8 by executing the following command:
fru_cli
Note: A root password for the blade is required. If prompted for factory blade, enter
alatcav2.
For example: (the output may vary depending on the blade)
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to safely abort this
interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
Enter the CARD number [ 8 ]: 8
CARD number = 8
Enter the location [ front ]: front
You are about to activate Shelf-Card: 00-08
Type 'y' to proceed [y|n]y
Please wait. Activation in progress ...
... Mac address updated successfully.
... Metadata updated successfully.
... DHCP configuration generated successfully.
... DHCP configuration installed successfully.
... DHCP configuration restarted successfully.
... Hub card entries in known_hosts file updated successfully.
... Card is up.
... Checking SOL configuration on the mate Hub.
If prompted, enter the password for Hub Card's root login below.
Enter password for the "root" login:
Starting SSH session to at071-s00c08h0
Running hub configuration data audit on hub at071-s00c08h0...
Generated hub configuration files are up-to-date for at071-s00c08h0
Hub configuration files need updated on at071-s00c08h0
Checking payload version on at071-s00c08h0...
Payload package version == 2.4.1/1, Payload hub version == 2.4.1/1
Payload version is up-to-date on at071-s00c08h0
Configuration data update required.
Copying files to at071-s00c08h0...
Running SOL 'enable' action on at071-s00c08h0
Configuration complete... rebooting at071-s00c08h0
Resetting hub at071-s00c08h0...
..................................
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-29
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
Sleeping 30 seconds while hub finishes booting...
Connecting to at071-s00c08h0...
Starting SSH session to at071-s00c08h0
Checking watchdog status
The reset of hub at071-s00c08h0 completed successfully
Waiting for 2 minutes -- Checking for unexpected reboots
Checking IPMC versions on at071-s00c08h0...
IPMC package version == 3.1.12, IPMC card version == 3.1.12
IPMC version is up-to-date
Checking MMC versions on at071-s00c08h0...
No AMC slots populated
Checking BIOS version on at071-s00c08h0...
BIOS package version == 2.2.0/2, BIOS card version == 2.2.0/2
BIOS version is up-to-date
'update' on at071-s00c08h0 SUCCEEDED
... Hub configuration updated successfully.
at071-s00c01h0: generating SSH keys... done
at071-s00c02h0: generating SSH keys... done
at071-s00c03h0: generating SSH keys... done
at071-s00c04h0: generating SSH keys... done
at071-s00c05h0: generating SSH keys... done
at071-s00c06h0: generating SSH keys... done
at071-s00c07h0: aquiring SSH keys... done
at071-s00c07h4: generating SSH keys... done
at071-s00c08h0: aquiring SSH keys... done
at071-s00c11h0: generating SSH keys... done
at071-s00c12h0: generating SSH keys... done
at071-s00c15h0: aquiring SSH keys... done
at071-s00c01h0: generating SSH daemon configuration... done
at071-s00c02h0: generating SSH daemon configuration... done
at071-s00c03h0: generating SSH daemon configuration... done
at071-s00c04h0: generating SSH daemon configuration... done
at071-s00c05h0: generating SSH daemon configuration... done
at071-s00c06h0: generating SSH daemon configuration... done
at071-s00c11h0: generating SSH daemon configuration... done
at071-s00c12h0: generating SSH daemon configuration... done
at071-s00c01h0: installing SSH daemon configuration... done
at071-s00c02h0: installing SSH daemon configuration... done
at071-s00c03h0: installing SSH daemon configuration... done
at071-s00c04h0: installing SSH daemon configuration... done
at071-s00c05h0: installing SSH daemon configuration... done
at071-s00c06h0: installing SSH daemon configuration... done
syncing RADIUS badwords file... done
syncing RADIUS license file... done
syncing RADIUS key file... done
... SSH configuration updated successfully.
... All Services are active.
Hub Card 00-08 activation SUCCESSFUL.

....................................................................................................................................................................................................................................
7-30 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

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

19 Deactivate hub 7 by executing the following command:


fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|5|6|7|8|11|12|15 ]: 7
Enter the location [ front|rear ]: front
You are about to deactivate Shelf-Card: 00-07
Type 'y' to proceed [y|n]y
Hub Card 00-07 deactivation SUCCESSFUL
...................................................................................................................................................................................................

20 Once the blade is completely powered down, remove the card.


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

21 Remove the old hardware from data by executing the following command on the MI:
hwconf_adm --action del_card_instance --shelfnum <shelf number> --
cardnum <card number>
For example:
> hwconf_adm --action del_card_instance --shelfnum 0 --
cardnum 7
...................................................................................................................................................................................................

22 Replace it with a hub with HSPP4.


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

23 Get the front and rear mnemonics of the new card by executing the following command:
getMnemonic -s <shelf number> -c <card number>
For example:
> getMnemonic -s 0 -c 7
Result:
FMA1AD;NONE
...................................................................................................................................................................................................

24 Add the card information by executing the following command:


hwconf_adm --action add_card_instance --shelfnum <shelf number> --
cardnum <card number> --frontmnemonic front mnemonic --rearmnemonic
rear mnemonic

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-31
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
For example:
hwconf_adm --action add_card_instance --shelfnum 0 --cardnum
7 --frontmnemonic FMA1AD --rearmnemonic NONE
...................................................................................................................................................................................................

25 Generate SSH keys by executing the following command:


sshconf_adm --action key_host_instance --shelfnum <shelf number> --
cardnum <card number> --hostnum host number
For example:
sshconf_adm --action key_host_instance --shelfnum 0 --cardnum
7 --hostnum 4
...................................................................................................................................................................................................

26 Generate System Configuration data by executing the following command:


scdf_adm --action generate_host_all
...................................................................................................................................................................................................

27 Install System Configuration data by executing the following command:


scdf_adm --action install_host_all --growth
...................................................................................................................................................................................................

28 Synchronize the database by executing the following command:


syncConfigDB -l
When prompted, enter y.
For example:
> syncConfigDB -l
Synchronization is necessary, the following changes are required:
delete from cfg.ipcfg_hosts where (shelf_id = 0 and card_id = 7 and
host_id = 0)
insert into cfg.ipcfg_hosts (shelf_id, card_id, host_id, cpu_type,
host_ip, host_name, pmc1, pmc2, maint_cond, software_version,
load_ind, lsn0_iface, lsn0_ip, lsn1_iface, lsn1_ip, iface_l,
iface_r, dhcp0_ip, dhcp1_ip, function_type, mnemonic) values (0,
7, 0, -1, '000A474070000000000000000000000000000000', 'at071-
s00c07h0', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472070000000000000000000000000000000', 'eth1.801:0',
'000A473070000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'hub', 'FMA1AD')
insert into cfg.ipcfg_hosts (shelf_id, card_id, host_id, cpu_type,
host_ip, host_name, pmc1, pmc2, maint_cond, software_version,
load_ind, lsn0_iface, lsn0_ip, lsn1_iface, lsn1_ip, iface_l,
iface_r, dhcp0_ip, dhcp1_ip, function_type, mnemonic) values (0,
7, 4, -1, '000A474074000000000000000000000000000000', 'at071-
s00c07h4', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472074000000000000000000000000000000', 'eth1.801:0',

....................................................................................................................................................................................................................................
7-32 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
'000A473074000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'node', 'FMA1AD')
Do you want to make the changes listed above ? (y/n) y
Synchronization complete.
Command completed successfully.
...................................................................................................................................................................................................

29 Execute the following command:


create_ht
For example:
> create_ht
Wed Mar 24 14:54:19 CDT 2010 create_ht
Wed Mar 24 14:54:19 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Wed Mar 24 14:54:19 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Wed Mar 24 14:54:19 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Wed Mar 24 14:54:19 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
...................................................................................................................................................................................................

30 Activate the new hub card in slot 7 by executing the following command:
fru_cli
Note: A root password for the blade is required. If prompted for factory blade, enter
alatcav2.
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
Enter the CARD number [ 7 ]: 7
CARD number = 7
Enter the location [ front ]: front
You are about to activate Shelf-Card: 00-07
Type 'y' to proceed [y|n]y
Please wait. Activation in progress ...
... Mac address updated successfully.
... Metadata updated successfully.
... DHCP configuration generated successfully.
... DHCP configuration installed successfully.
... DHCP configuration restarted successfully.
... Hub card entries in known_hosts file updated successfully.
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-33
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

....................................................................................................................................................................................................................................
... Card is up.
... Checking SOL configuration on the mate Hub.
..
..
..
..
..
Hub Card 00-07 activation SUCCESSFUL.
...................................................................................................................................................................................................

31 Synchronize the meta data by executing the following command:


scdm_adm --action sync_config
...................................................................................................................................................................................................

32 Allow MI switchover by executing the following command:


rccInhibit -a CLEAR MI-1hostname
Check the status by executing the following command:
rccInhibit -d MI-1hostname
...................................................................................................................................................................................................

33 On MI-2 execute the following commands:


scdf_adm --action generate_host_all
create_ht
...................................................................................................................................................................................................

34 Plug in the 10G cross connect cable between the two hubs into UPLF/UPL0 ports.

....................................................................................................................................................................................................................................
7-34 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

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

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-35
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Hub without HSPP4 to Hub with HSPP4

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

35 Plug in the HSPP4 network connections.


For information on how to plug in the HSPP4 network connections, see “To install
Ethernet transport connections between HSPP4 face plate and the external network
equipment” (p. 5-17).
...................................................................................................................................................................................................

36 MI GUI rediscovery must be triggered.


For information on MI GUI rediscovery procedures, see “Global rediscovery using the
MI-GUI ” (p. 3-37).
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
7-36 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Disk Schema

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

To convert Disk Schema


Prerequisites
Ensure the following:
• Stable system.
• Perform a system backup.
• Ensure files are backed up.
• Information required to convert a pair of cards - Shelf number, card number, and the
new schema name.

To convert disk scheme


Perform the following steps to convert disk scheme:
...................................................................................................................................................................................................

1 Open two windows and log in to MI-1 host as root on both the windows.
...................................................................................................................................................................................................

2 To find out the MI with active VM , execute the following command:


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 If the second MI is active, switch to the active MI by executing the following command:
MIcmd switch vc
> MIcmd switch vc Complete RCCvcswitch successfully: Wait for
State Change.
.............................
MI virtual cluster switched over successfully
Verify that the primary VM is active by executing the following command:
MIcmd state vc
...................................................................................................................................................................................................

4 Back up all the files required from the disk being converted.
...................................................................................................................................................................................................

5 Execute the following command:


create_ht
> create_ht

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-37
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
Mon Aug 9 15:30:14 CDT 2010 create_ht
Mon Aug 9 15:30:14 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Mon Aug 9 15:30:14 CDT 2010 Wrote new /var/opt/lib/sim/data/hosts.dat
Mon Aug 9 15:30:14 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Mon Aug 9 15:30:14 CDT 2010 Wrote new /var/opt/lib/sim/data/hostdat.ksh
...................................................................................................................................................................................................

6 On the first MI window, execute the following command as root:


su_health -a
Note: Errors must be resolved before proceeding with this procedure. For further
assistance on this tool, contact Alcatel-Lucent technical support representative.
...................................................................................................................................................................................................

7 Execute the following command on MI-1 to deactivate Side B blade for which the scheme
needs to be changed:
fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|5|6|7|8|11|12|15 ]: 4
Enter the location [ front|rear ]: front
VM list: fsdb
Warning: You are about to deactivate a card that has ACTIVE services.
The mate of the card to be deactivated is NOT active with all the
services.
An OUTAGE may occur if you continue without switching all ACTIVE
services
from this card to the mate card.
Are you sure you want to proceed? [y|n]y
You are about to deactivate Shelf-Card: 00-04
Type 'y' to proceed [y|n]y
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/deactivate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 04 R22.18.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

8 Execute the following command on the second active MI-1 window and to tail the SIM
log:
....................................................................................................................................................................................................................................
7-38 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
tail -f /var/opt/log/sim/fru/sim.log
Note: The second window is used to monitor the progress of the SIM. In case of a
failure during the execution of SIM, it initiates a “pause” and reports the failure to the
user through the log file. When this occurs, correct the root cause of the error and
resume the disk conversion by executing sim fru resume.
For
example:11/16/09 14:43:49 SIM025_end *** FAILURE [RC=255] ***
11/16/09 14:43:49 SIM will Pause for *** FAILURE *** after
all dispatched commands complete execution!
11/16/09 14:43:49 PAUSED: for *** FAILURE *** after all
dispatched commands completed execution!
...................................................................................................................................................................................................

9 When the SIM rules are completed, wait till the blade is completely powered down. To
check the status of the blade, log in to the active ShMC and execute the following
commands for each blade:
# clia shmstatus
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Host: "Active"
# clia board <card#>
For example:
# clia board 5
Alcatel-Lucent NSAV2 Shelf Manager Command Line Interpreter
Physical Slot # 5
8a: FRU # 0
Entity: (0x0, 0x0)
Hot Swap State: M1 (Inactive), Previous: M6 (Deactivation In Progress),
Last State Change Cause: Normal State Change (0x0)
Device ID String: ""
Note: The Inactive state in the output confirms that the card is powered down.
...................................................................................................................................................................................................

10 Execute the following command to convert the disk scheme:


disk_scheme_conv -c
For example:
> disk_scheme_conv -c
disk_scheme_conv is a tool used to convert disk scheme
on a diskfull blade.
Log location:
/var/opt/log/disk_scheme_conv/disk_scheme_conv.log
SHELF number = 00, CARD number = 04
Please choose below scheme name:
storage_90_147G - 90GB storage scheme for 147GB disk
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-39
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
LCP_base_300 - Default LCP Scheme for 300GB disk
LCP_base_147 - Default LCP Scheme for 147GB disk
for disk front:1, press return to skip: storage_90_147G
Executing command: hwconf_adm --action set_disk_scheme --shelfnum
00 --cardnum 04 --hostnum 0 --schemename storage_90_147G --diskid
front:1
Executing command: svcconf_adm --action generate_host_all
at001-s00c01h0: generating service configuration... done
at001-s00c02h0: generating service configuration... done
at001-s00c03h0: generating service configuration... done
at001-s00c04h0: generating service configuration... done
Executing command: hwconf_adm --action generate_host_all
at001-s00c01h0: generating hardware configuration... done
at001-s00c02h0: generating hardware configuration... done
at001-s00c03h0: generating hardware configuration... done
at001-s00c04h0: generating hardware configuration... done
at001-s00c07h4: generating hardware configuration... done
at001-s00c08h4: generating hardware configuration... done
at001-s00c09h0: generating hardware configuration... done
at001-s00c10h0: generating hardware configuration... done
at001-s00c11h0: generating hardware configuration... done
at001-s00c12h0: generating hardware configuration... done
Executing command: svcconf_adm --action install_host_local
at001-s00c01h0: installing service configuration... done
Executing command: hwconf_adm --action install_host_local
at001-s00c01h0: installing hardware configuration... done
Executing command: svcconf_adm --action install_host_instance --
shelfnum 0 --cardnum 2 --hostnum 0
at001-s00c02h0: installing service configuration... done
Executing command: hwconf_adm --action install_host_instance --
shelfnum 0 --cardnum 2 --hostnum 0
at001-s00c02h0: installing hardware configuration... done
...................................................................................................................................................................................................

11 Execute the following command to power on the blade:


resetCard -s <shelf> -c <slot> -v poweron
For example:
resetCard -s 0 -c 4 -v poweron
...................................................................................................................................................................................................

12 Execute the following command to activate the new card:


fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to

....................................................................................................................................................................................................................................
7-40 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
Enter the CARD number [ 2 ]: 4
CARD number = 4
Enter the location [ front ]: front
You are about to activate Shelf-Card: 00-04
Type 'y' to proceed [y|n]y
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 04 R22.18.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

13 Execute the following command on the second active MI-1 window and tail the SIM log:
tail -f /var/opt/log/sim/fru/sim.log
...................................................................................................................................................................................................

14 SIM will pause for jumpstart of the above mentioned blade. Follow the jumpstart
procedure.
...................................................................................................................................................................................................

15 Execute the following command once the jumpstart is completed successfully:


sim fru resume
For example:
> sim fru resume
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 04 R22.18.00 front local_disk
SIM will resume applying rules from the previous pause/abort.
Continue? [y/n] y
SIM fru resume will be resumed!
...................................................................................................................................................................................................

16 Wait until the SIM rules are completed successfully in the SIM log. Execute the following
command on MI-1:
disk_scheme_conv -s
For example:
> disk_scheme_conv -s
disk_scheme_conv is a tool used to convert disk scheme
on a diskfull blade.
Log location:
/var/opt/log/disk_scheme_conv/disk_scheme_conv.log
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-41
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
Executing command: svcconf_adm --action install_host_all
at001-s00c01h0: installing service configuration... done
at001-s00c02h0: installing service configuration... done
at001-s00c03h0: installing service configuration... done
at001-s00c04h0: installing service configuration... done
Executing command: hwconf_adm --action install_host_all
at001-s00c01h0: installing hardware configuration... done
at001-s00c02h0: installing hardware configuration... done
at001-s00c03h0: installing hardware configuration... done
at001-s00c04h0: installing hardware configuration... done
Executing command: tzconf_adm --action set_all
at001-s00c01h0: setting timezone... done
at001-s00c02h0: setting timezone... done
at001-s00c03h0: setting timezone... done
at001-s00c04h0: setting timezone... done
Executing command: scdm_adm --action sync_config
Executing command: create_ht
Mon Aug 9 16:41:27 CDT 2010 create_ht
Mon Aug 9 16:41:27 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Mon Aug 9 16:41:27 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Mon Aug 9 16:41:27 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout
Mon Aug 9 16:41:27 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
Executing command: remote_shell root at001-s00c02h0 export PERL5LIB=/
opt/LSS/share/perl5:/opt/LU3P/lib/perl5:/opt/LU3P/perl5; /opt/LSS/
sbin/scdf_adm --action generate_host_all
at001-s00c02h0: generating application configuration... done
at001-s00c02h0: generating CPM daemon configuration... done
at001-s00c02h0: generating DHCP daemon configuration... done
at001-s00c02h0: generating DNS configuration... done
at001-s00c02h0: generating FTP configuration... done
.
.
.
.
Executing command: remote_shell root at001-s00c02h0 export PATH=/opt/
LSS/bin:/opt/LU3P/bin:/opt/LSS/sbin:/usr/bin:/bin:/usr/sbin:/
sbin:/opt/RCC/bin:/opt/LSS/sbin:/usr/sbin:/sbin:/usr/bin:/bin:/
opt/LSS/bin:/opt/LU3P/bin:/opt/LU3P/sbin:/root/bin:/usr/java/
bin; /opt/LSS/sbin/create_ht
Mon Aug 9 16:41:43 CDT 2010 create_ht
Mon Aug 9 16:41:43 CDT 2010 Saving backup files to /var/opt/lib/sim/
data
Mon Aug 9 16:41:43 CDT 2010 Wrote new /var/opt/lib/sim/data/
hosts.dat
Mon Aug 9 16:41:43 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.layout

....................................................................................................................................................................................................................................
7-42 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
Mon Aug 9 16:41:43 CDT 2010 Wrote new /var/opt/lib/sim/data/
hostdat.ksh
Scheme conversion is completed!
...................................................................................................................................................................................................

17 If changing scheme on the MI, then perform the following:


• Exit out of the MI-1 window.
• Log in to MI-2 window as root.
• Switch the MI to make the other MI active. Execute MIcmd switch vc
• Verify the MI-2 is active by executing MIcmd state vc
...................................................................................................................................................................................................

18 Execute the following command on the active MI, to deactivate side A of the blade:
fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:d
Enter the SHELF number [ 0 ]: 0
Enter the CARD number [ 1|2|3|4|7|8|9|10|11|12|15 ]: 3
Enter the location [ front ]: front
VM list: fsdb
WARNING: You may be trying to deactivate a card that has ACTIVE
services.
The mate of the card to be deactivated is NOT active with all the
services.
An OUTAGE may occur if you continue without switching all ACTIVE
services
from this card to the mate card.
Are you sure you want to proceed? [y|n]y
You are about to deactivate Shelf-Card: 00-03
Type 'y' to proceed [y|n]y
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/deactivate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 03 R22.18.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

19 Execute the following command to tail the SIM log:


tail -f /var/opt/log/sim/fru/sim.log

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-43
270-702-014R4.0 Issue 4 Use pursuant to applicable agreements
March 2011
Platform hardware conversion To convert Disk Schema

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

20 When the SIM rules are completed, wait till the blade is completely powered down. See
Step 9 on how to confirm that the blade is powered down. Execute the following
command to change the scheme name:
disk_scheme_conv -c
...................................................................................................................................................................................................

21 Execute the following command to power on the blade:


resetCard -s <shelf> -c <slot> -v poweron
For example:
resetCard -s 0 -c 3 -v poweron
...................................................................................................................................................................................................

22 Execute the following command to activate the new card in slot above:
fru_cli
For example:
> fru_cli
fru_cli provides the mechanism to execute FRU procedure
(Deactivate or Activate) on a diskless or diskfull card.
You can use ^C (control-C) at any time to
safely abort this interactive script.
Enter the Action [[d]eactivate or [a]ctivate]:a
Enter the SHELF number [ 0 ]: 0
SHELF number = 0
Enter the CARD number [ 1 ]: 3
CARD number = 1
Enter the location [ front ]: front
You are about to activate Shelf-Card: 00-03
Type 'y' to proceed [y|n]y
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 03 R22.18.00 front local_disk
SIM will apply rules from the BEGINNING! Continue? [y/n] y
SIM fru start was successfully launched!
...................................................................................................................................................................................................

23 Execute the following command on the second active MI-2 window and tail the SIM log:
tail -f /var/opt/log/sim/fru/sim.log
...................................................................................................................................................................................................

24 SIM will pause for jumpstart of the above blade. Follow the jumpstart procedures. Upon
successful completion execute the following command:
sim fru resume

....................................................................................................................................................................................................................................
7-44 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
Use pursuant to applicable agreements 270-702-014R4.0 Issue 4
March 2011
Platform hardware conversion To convert Disk Schema

....................................................................................................................................................................................................................................
For example:
> sim fru resume
Using hosts file: /var/opt/lib/sim/data/hosts.dat
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
Writing to log file: /var/opt/log/sim/fru/sim.log
User level: 00 03 R22.18.00 front local_disk
SIM will resume applying rules from the previous pause/abort.
Continue? [y/n] y
SIM fru resume will be resumed!
...................................................................................................................................................................................................

25 Wait until the SIM rules are completed successfully in the SIM log and execute the
following command:
disk_scheme_conv -s
...................................................................................................................................................................................................

26 To check system health after the disk conversion execute the following command on the
first MI window as root:
su_health -a
Note: In case of any errors, contact Alcatel-Lucent technical support representative.
E...................................................................................................................................................................................................
N D O F S T E P S

....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary 7-45
270-702-014R4.0 Issue 4 Use pursuant